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

forward-only

concept
depth 3/3 − deeper + surface

Finished work stays finished; a mistake is answered with a new document, never by editing the old one.

Closed hos stay closed; closed decisions stay on the record. The response to superseded work is a new document that names what it supersedes—never a reopening, rewrite, or retroactive edit. Typographical fixes are the only exception. Governs the frozen and sealed mutability regimes; living is the declared exception.

The Forward-Only Principle. Closed hos stay closed. When evidence surfaces that an earlier ho's work was incomplete, wrong, or has been overtaken by what the project now knows, the response is a new ho in the current build slot—not a reopening, rewrite, or retroactive edit of the earlier one.

The earlier ho is a historical record of what was known and decided at the time. The new ho is the response to what is known now. Both are kept. The timeline reads as a sequence of honest positions, each correct for its moment, with later hos visibly responding to earlier ones.

This is the same logic as Rule 1 ("Numbers are permanent") applied to content rather than addresses. Rule 1 protects the address space; forward-only protects the record. Together they make the arc trustworthy as history: numbers don't get recycled, and conclusions don't get silently revised.

What forward-only rules out:

  • Editing a closed ho's findings, scope, or deliverables to reflect later understanding.
  • "Reopening" a ho to do additional work under its old number.
  • Marking closed hos as failed or invalid in retrospect—they were correct given what was known.

What forward-only enables: […]