A blueprint is not a habit tracker

Most habit apps optimize for one thing: did you check the box today. That's a fine question, but it's the wrong first question. It skips the part that actually determines whether a habit survives contact with a bad week — why you're doing it, and whether the method itself is any good.

A blueprint starts one level up. Before any checkbox exists, there's a concept — a stated belief about how a part of life works, inherited from someone who tested it publicly: an athlete's training log, a scientist's morning routine, a philosopher's evening review. The habits in a Dojang blueprint aren't the goal; they're the smallest observable actions that would tell you whether the concept is holding up in your own life.

This changes what "progress" means. A habit tracker's success metric is streak length. A blueprint's success metric is REV count — how many times the underlying design has been revised in response to evidence. A long streak on a bad concept isn't success; it's a slow way to find out the concept was wrong.

Practically, this shows up in three places. Every blueprint carries its principles, not just its habit list, so you can read why before you read what. Checking a habit produces a data point, not applause — the weekly review looks at completion rate, not motivation. And forking someone else's blueprint is explicitly framed as starting an experiment, not adopting a lifestyle: the fork gate compares your evidence against theirs, and either keeps the method, revises it, or drops it.

None of this claims structure beats willpower, or that measurement substitutes for actually doing the thing. It's a narrower claim: if you're going to repeat an action for weeks, it's worth spending thirty seconds first on whether the reasoning behind it would survive being written down.