REV, not streaks: how evidence changes a life design

Every blueprint in Dojang has a version number — REV.0, REV.1, REV.2 — and that number, not the streak counter, is the one the product treats as the real measure of progress.

REV.0 is a hypothesis. It's usually adopted from someone else's documented method — a marathoner's training diary, a physicist's morning ritual — restated as a set of principles and a short list of daily practices. Nothing about REV.0 is proven yet; it's just a specific, falsifiable starting point instead of a vague intention.

The version increments only when there's evidence to justify a change. A completion rate that holds steady for two weeks is evidence to keep a habit. A completion rate that never recovers after a schedule change is evidence to drop it, reduce its difficulty, or swap it for a different habit serving the same principle. Either way, the change is written down as a new REV with the reasoning attached, so the history of a life design stays legible — you can look back at REV.3 and see exactly what evidence led to REV.4.

This is deliberately unlike a streak, which collapses at the first missed day and tells you nothing about why. A missed day inside a REV is just a data point. What matters is what the next two weeks of data say about whether the concept survives.

The same logic extends to the weekly review: instead of a coach cheering you on, the review reads like a lab notebook entry — completion percentages, a specific suggestion tied to a specific pattern in the data, and a decision to accept or reject it. Accepting a suggestion creates the next REV. Rejecting one is also useful data — it tells the system your actual constraints, not just your stated ones.

The point of versioning a life design instead of just logging it is that a design you can revise on evidence is one you can actually trust over years, not just over a good month.