Ho System, Actually Build the software. Develop the judgment.

Reflect

definition
depth 3/3 − deeper + surface

The honest look back after the work: did the plan hold, what changed, what the next session carries.

The post-execution phase of a ha ho (and by extension the reflective close of any session): did the design hold, which decisions were revised on what evidence, what changes for the next ho. The durable record of discoveries that crossed back from execution.

Discoveries Crossing Back. When a child task's execution reveals that a parent ho's decision needs revision, the revision is recorded in the parent, not the child. The Shodō ho-02 pattern: the Think phase committed to a cap of 4; AT-03's real-data inspection showed the cap forced false splits in 75% of threads; the cap was raised to 50; the revision lives in ho-02's Decision 3 (marked as revised post-execution) and Reflect (full evidence); AT-03 carries only the executable result.

The principle: the ho is the durable architectural record. A reader returning two years later reads the ho to understand the architecture, including changes execution surfaced; they read the tasks only to know exactly what shipped.

This section and §3.3 are the same loop seen from two ends: the escalation clause is how a discovery gets out of the AT; this rule is where the resolution gets recorded.