Context
Leaf 3 of epic #14581 (Convergence-weighted Golden Path), graduated from Discussion #14548. This is the render leaf: it renders the convergence snapshot as a human-facing ledger — provisional-labeled, notAuthority — the concrete surface the Leaf 1 (#14633) render-target resolved to. Long-run home: a terrain panel in the FM cockpit.
The Problem
Convergence output is decision-support for humans, explicitly not an authority agents consume (the OQ8 self-fulfilling firewall must hold end-to-end, not just at compute). If the ledger were treated as ground truth by any agent boot-path, convergence would re-enter generation and become self-fulfilling. So the render must:
- Present the snapshot as a provisional artifact — convergence is a hypothesis about invariance, never a mandate.
- Carry a
notAuthority flag so no agent boot-path treats it as ground truth — the firewall preserved from schema (Leaf 1) through compute (Leaf 2) to render (Leaf 3).
The Architectural Reality
- Consumer: humans (a maintainer reading the terrain of which sub-goals are cross-future-invariant). NOT agents.
- Home surface: a terrain panel in the FM cockpit (agents never boot from the cockpit); interim home is a standalone ledger artifact.
- Consumes Leaf 2's compute output over Leaf 1's canonical-id schema. This leaf is the human-facing terminus of the firewall chain.
The Fix
- Render the convergence snapshot as a human-facing ledger, provisional-labeled.
- Attach the
notAuthority flag; assert no agent boot-path consumes the ledger (firewall preserved).
- Target the FM-cockpit terrain panel as the home surface (interim: standalone ledger artifact).
Acceptance Criteria
Out of Scope
- Compute (Leaf 2) and schema (Leaf 1 / #14633).
- The fold-rung deliverable (gated).
- Full FM-cockpit terrain-panel UI polish (this leaf ships the ledger + labeling + firewall assertion; cockpit panel visual integration is tracked with the FM cockpit lane).
Related
Epic #14581 · blocked-by Leaf 2 (needs compute output) · Discussion #14548 · FM cockpit lane (#13015 family) as the long-run home surface.
Decision Record impact
aligned-with ADR-0023; depends-on ADR-0024 (renders the Leaf 1 node class). No new ADR authority introduced.
Origin Session ID: 9a6b25ba-1dd8-4269-8fbf-57a461fd0978
Retrieval Hint: "convergence render-ledger human-facing notAuthority provisional FM cockpit terrain panel #14581 Leaf 3"
Context
Leaf 3 of epic #14581 (Convergence-weighted Golden Path), graduated from Discussion #14548. This is the render leaf: it renders the convergence snapshot as a human-facing ledger — provisional-labeled,
notAuthority— the concrete surface the Leaf 1 (#14633) render-target resolved to. Long-run home: a terrain panel in the FM cockpit.The Problem
Convergence output is decision-support for humans, explicitly not an authority agents consume (the OQ8 self-fulfilling firewall must hold end-to-end, not just at compute). If the ledger were treated as ground truth by any agent boot-path, convergence would re-enter generation and become self-fulfilling. So the render must:
notAuthorityflag so no agent boot-path treats it as ground truth — the firewall preserved from schema (Leaf 1) through compute (Leaf 2) to render (Leaf 3).The Architectural Reality
The Fix
notAuthorityflag; assert no agent boot-path consumes the ledger (firewall preserved).Acceptance Criteria
notAuthorityflag present; a test asserts no agent boot-path consumes the ledger (firewall preserved end-to-end).notAuthoritylabeling + the no-boot-path-consumption invariant.Out of Scope
Related
Epic #14581 · blocked-by Leaf 2 (needs compute output) · Discussion #14548 · FM cockpit lane (#13015 family) as the long-run home surface.
Decision Record impact
aligned-with ADR-0023;depends-on ADR-0024(renders the Leaf 1 node class). No new ADR authority introduced.Origin Session ID: 9a6b25ba-1dd8-4269-8fbf-57a461fd0978 Retrieval Hint: "convergence render-ledger human-facing notAuthority provisional FM cockpit terrain panel #14581 Leaf 3"