No Terminal State

"A journey ends. A body does not. The single most likely mistake in Forge is treating health like a trip."

The One Divergence That Reshapes Everything

Forge inherited most of its shape from Waystone, which makes this the section to read most carefully. Waystone's Journey has a departure, a return, and a three-phase arc: plan, execute, reflect. A journey completes — its baseline freezes at departure, and the retrospective is written against that frozen record. Copy that onto health and you have made the defining error, because health does not complete. There is no departure and no homecoming. The body just keeps going.

The Loop That Replaces the Arc

So Forge swaps the arc for a loop:

baseline → trend → intervention → new baseline — a loop, not an arc. Analysis is continuous and available at any moment, not a post-completion ritual. Baselines version rather than being singular; each intervention resets the reference the next trend is read against.

The consequences fall out immediately. There is no "reflection" phase, because there is no end to reflect from — reading the record is something you do continuously, not once at a finish line. And interventions are not modeled as ceremonies with their own entity and workflow. A new prescription, a changed training block, a procedure — each simply arrives as an ordinary dated crumb, and analysis reads the timeline against it.

Baseline Is Not an Entity in v1

Here is the disciplined part: even though the loop talks about "baselines," Forge does not build a Baseline entity in v1. The check-up documents in the Medical tab are the natural anchors the timeline is read against — their dates and their analysis artifacts give trend work its reference points. Promoting Baseline to a first-class thing waits until real trend analysis proves the need for explicit markers beyond that. This is concrete-first in action: name the loop as a principle, but do not manufacture the machinery before the data asks for it.

Code

The arc (Waystone) vs the loop (Forge)·text

WAYSTONE - an arc that completes:

  plan ----> execute ----> reflect ----> [DONE]
  (baseline frozen at departure; retrospective is final)


FORGE - a loop that never terminates:

     baseline ---> trend ---> intervention
        ^                          |
        |                          v
        +------- new baseline <-----+

  (analysis is continuous; baselines version;
   an intervention is just an ordinary dated crumb)

Exercise

Take a health goal you would normally frame as a journey — 'get fit for summer,' 'recover from this injury.' Re-frame it as a loop: baseline, trend, intervention, new baseline. What does the loop framing let you keep noticing that the journey framing quietly ends and forgets?

Hint

The journey framing stops paying attention the moment you 'arrive.' The loop keeps reading the trend past every milestone, so the thing that comes back after summer, or after recovery, is still in view.

The One Divergence That Reshapes Everything

The Loop That Replaces the Arc

Baseline Is Not an Entity in v1

Code

External links

Exercise

Progress

Comments 0