Skip to content
2 changes: 1 addition & 1 deletion dag/gunbc/design_document.dag
Original file line number Diff line number Diff line change
Expand Up @@ -70,7 +70,7 @@ fn section_3_blocks() -> List<MarkdownBlock> {
p(text: "**§3 standing rule — cite the symbol, not the position.** A `file:line` pointer is a second, positional naming scheme for something the containment tree already names, and it decays in a way a nickname does not: any edit *above* the cited line silently invalidates it. Name the module and symbol; add a position only where no symbol exists to name — a generated artifact, a data row, a line inside a blob — and where a position is carried, it is a convenience beside the symbol, never the citation itself. Grep-verifying a symbol is the same `Node`-tree read the namespace authority already performs, so a stale name is decidable and enforceable; a line is not reachable from that tree at all."),
h3(text: "§3 standing rule — replacement migrations cut over at the root"),
p(text: "When two structures answer the same semantic question and one is intended to disappear, the change is a **replacement migration**, not a refinement. §2 prices an intermediate representation destined to be discarded as redundant work, and §3 forbids X and Y both answering for one fact. Editing X from its leaves upward preserves its root while every intermediate state becomes observable and load-bearing, so the migration creates more authority before it removes any. The deeper cost is that a surviving X is an **attractor**: while it stands, every nearby question is answered in its vocabulary, so decisions keep being premised on an assumption already scheduled for death — and A3 grounds agreement only on what stays stable across time, which a dead assumption by definition does not."),
p(text: "So the default is **delete-first**: uproot the root as early as you can, then fix forward minimally with the new solution, solving each surfaced problem from first principles rather than restoring it to its old binding. In a fail-closed substrate **the deletion is the census** — every real dependent refuses loudly, so what breaks is exactly what was load-bearing. What cannot break loudly is covered by a declared, bounded §4b rung-drop, never by silence. Two carve-outs: a gap-intolerant boundary keeps the staged form — Y built in shadow, then one transition that switches the root and deletes X together — and where no Y can hold the boundary at all, X stays but stays **frozen**: no new investment, no new rows on its growth surfaces."),
p(text: "So the default is **delete-first**: uproot the root as early as you can, then fix forward minimally with the new solution, solving each surfaced problem from first principles rather than restoring it to its old binding. In a fail-closed substrate **the deletion is the census over the population something compiles** — every real dependent refuses loudly, so what breaks is exactly what was load-bearing. The required gate is a static roster the operator signed, the compiler floor and nothing else (`v2.workflow.required_floor` `required_gate_prefixes`), so outside it the substrate still refuses and nothing asks it to: a product-layer dependent can stop resolving, stay broken, and let every required lane report SUCCESS. **For a root outside the gate the census is yours to take — enumerate the consumers by name before you delete.** What cannot break loudly is covered by a declared, bounded §4b rung-drop, never by silence. Two carve-outs: a gap-intolerant boundary keeps the staged form — Y built in shadow, then one transition that switches the root and deletes X together — and where no Y can hold the boundary at all, X stays but stays **frozen**: no new investment, no new rows on its growth surfaces."),

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Base the manual census on consumer coverage

The manual-census obligation is incorrectly conditioned on the replacement root being “outside the gate.” required_gate_prefixes selects witness modules, while required_floor_runner compiles a forward import closure; compiling or admitting the root does not pull in reverse dependents, so an admitted root can still have an unchanged product-layer consumer outside the prepared closure that remains broken while every required lane succeeds. Conversely, an outside-prefix module may be compiled when another closure seed reaches it. Scope this obligation to whether every consumer is proven present in the prepared closure, rather than to the root's gate membership, or this retains the same unsafe migration path the paragraph is intended to close.

Useful? React with 👍 / 👎.

p(text: "**\"Atomic\" describes the authority transition, not the amount of implementation work.** Y has one coherent root, ordinary production never accumulates consumers that understand both representations, and X's authority ends in one motion. Y may freely reuse stable primitives, and X may serve from history as an offline differential oracle — but Y never falls back to X, resolves through it, or derives its answer from it. And the minimum Y is not the smallest thing that executes the happy path: it must preserve every required refusal, or it has erased a correctness distinction rather than completed the replacement."),
p(text: concat("The frozen-X carve-out is the wrong state for a production-critical X whose replacement was paused indefinitely, which is the v1 seed's situation. v1 is therefore reclassified — semantics frozen, maintenance active — under a PURPOSE admission test: a change is admitted when it serves the v2 self-host program, and v1 stays closed to growth for its own sake. The authority is ",
concat(documentary_ref_symbol_text(reference: v1_maintenance_standing_ref),
Expand Down
Loading