foundryside-dev · tachyon-beep · Aug 9, 2026 · Aug 9, 2026 · Aug 9, 2026 · Aug 9, 2026
diff --git a/AGENTS.md b/AGENTS.md
@@ -60,8 +60,10 @@ in Tolaria's matched common-future branches and certifies evidence → Isperia
 adjudicates provider-blind against no-op and issues warrants → Wrenn
 germinates/blends/commits under an admission warrant → Emrakul later
 sedates/decays/lyses under maintenance warrants → Urborg records everything →
-Tamiyo reveals it. The newsroom rule (`appendices/newsroom.md`): **Nissa sends
-the photograph; Aurelia sends only the assignment brief.**
+Tamiyo reveals it. The evidence-routing rule (INV-07/INV-09): **Nissa sends
+the evidence directly; Aurelia sends only the assignment brief**
+(`appendices/newsroom.md` retells the authority model as a newsroom — an
+alternative lens, ADR-0009).
 
 ## Non-negotiable invariants (`02-constitution.md` has all 45; these are the spine)
 

diff --git a/ARCHITECTURE.md b/ARCHITECTURE.md
@@ -59,10 +59,9 @@ Tamiyo; those edges are omitted above for legibility. Two details in the
 diagram are load-bearing:
 
 - **Nissa publishes the same observation identity independently to Aurelia
-  and Momir.** Aurelia is not a telemetry proxy; the newsroom formulation is
-  "Nissa sends the photograph; Aurelia sends only the assignment brief." A
-  `GrowthIntent` carries scope and operational constraints only — diagnosis,
-  topology and ancestry hints are schema-invalid (INV-07, INV-09).
+  and Momir.** Aurelia is not a telemetry proxy: a `GrowthIntent` carries
+  scope and operational constraints only — diagnosis, topology and ancestry
+  hints are schema-invalid (INV-07, INV-09).
 - **The request resolver is not a fifteenth agent.** It is a pure Leyline
   service that combines `GrowthIntent` + `StrategicEnvelope` + Wrenn's
   `RegionContract` + the active `GrammarProfile` into one canonical

diff --git a/README.md b/README.md
@@ -47,13 +47,13 @@ The other eleven are agents, summarised by the canonical sentence
 > Tolaria, Isperia judges, Wrenn embodies, Emrakul destroys, and Tamiyo
 > reveals; every precedent is kept in Urborg.
 
-The architecture deliberately resembles a newsroom
-([`docs/design/appendices/newsroom.md`](docs/design/appendices/newsroom.md)):
-observation, assignment, authorship, standards, production, fact-checking,
-publication judgement, and archive are separate desks, because letting one
-desk control the whole chain corrupts both evidence and accountability. The
-load-bearing routing rule: **Nissa sends the photograph directly to the
-designer; the assignments editor sends only the assignment brief.**
+The load-bearing routing rule: **Nissa publishes the evidence directly to
+the designer; Aurelia sends only the assignment brief** — evidence never
+arrives pre-captioned by the desk that commissioned it (INV-07, INV-09).
+And for readers who would rather picture an institution than learn a
+mythology, [`docs/design/appendices/newsroom.md`](docs/design/appendices/newsroom.md)
+retells the whole authority model as a newsroom — the same separations, no
+new vocabulary.
 
 ## Guarantees
 

diff --git a/docs/adr/0009-newsroom-demotion.md b/docs/adr/0009-newsroom-demotion.md
@@ -0,0 +1,88 @@
+# ADR-0009 — Demote the newsroom analogy to a single appendix rendering
+
+Date: 2026-08-09 · Status: accepted
+Deciders: John (owner-directed, product session 11) · Tracker: simic-7e2683f3cd
+
+## Context
+
+Namespec 2.0 (ADR-0008) locked the codename grammar as the design's operating
+frame: the canonical sentence, the faction layer, and the sentence lint in
+`../design/02-constitution.md` are how authority is stated, checked, and
+smelled. The newsroom analogy, however, still operates as a second co-primary
+frame: the constitution carries a full fourteen-role newsroom sidebar
+(§5.5), `../design/04-architecture.md#76-the-newsroom-authority-model`
+repeats the complete mapping, the README and public site introduce the
+architecture as "deliberately resembling a newsroom", and several Tier-0
+constraint lists cite "the newsroom rule" as if the metaphor were the rule's
+identity.
+
+Two parallel operating analogies split the design's voice. Every authority
+change must be narrated twice; the metaphor reads as normative when the
+enforcement was always contractual — INV-07 (direct evidence publication),
+INV-09 (assignment-brief boundary), blinding by schema absence, and the
+authority tests. One frame must own the design; the other must serve it.
+
+## Decision
+
+The Namespec 2.0 codename grammar is the sole operating frame. The newsroom
+becomes exactly one thing: **Appendix E**
+(`../design/appendices/newsroom.md`), reframed as an alternative rendering
+of the authority model — a deliberate second way in for readers to whom the
+codenames do not speak. It stays tightly coupled to the design: any change
+to an authority boundary must update the rendering in the same change set.
+It is no longer given primacy anywhere else.
+
+Mechanics:
+
+- Normative statements formerly cited as "the newsroom rule" are cited by
+  their invariants: **INV-07** and **INV-09** (with INV-08, INV-10, INV-11,
+  INV-12 supporting). The rule was never the metaphor.
+- Chapters keep at most a one-line pointer to Appendix E; no chapter carries
+  a parallel role mapping. The §5.5 sidebar and the §7.6 mapping collapse to
+  native statements of the routing rule plus the pointer.
+- Appendix-tier and implementation-surface couplings are retained: the
+  glossary's newsroom column, the package-README "Newsroom analogue, where
+  useful" line, Tamiyo's optional newsroom projection (`newsroom_view.py`),
+  and the good/bad-sentences translation aid.
+- Historical records (the archived monolith, ADR bodies 0001–0008, PDRs,
+  peer reviews) are never rewritten (INV-36).
+
+## Displaced constraints
+
+None. INV-07, INV-08, INV-09, INV-10, INV-11 and INV-12 are unchanged in
+wording and force. The Tier-0 constraint lists that named "the newsroom
+rule" (`README.md` in `docs/adr/`, `../design/ops/repo-structure.md`
+§30, and the repo-discipline line of the authority grant) now name **the
+evidence-routing rule (INV-07/INV-09)** — a citation rename, not a
+constraint change.
+
+## Options considered
+
+- **Keep both frames co-primary (status quo).** Rejected: two operating
+  analogies split the voice, double the narration cost of every authority
+  change, and let the metaphor masquerade as the enforcement mechanism.
+- **Delete the newsroom entirely.** Rejected: it is genuinely useful to
+  readers outside the codename idiom, and live design surface couples to it
+  (Tamiyo projection, glossary column, package-README line); deletion would
+  orphan those and discard a good teaching instrument.
+- **Move it outside the HLD (site/marketing only).** Rejected: outside
+  design custody it would drift from the authority model it renders; the
+  appendix keeps it under the ADR discipline and the same-change-set
+  coupling duty.
+
+## Consequences
+
+The constitution gets shorter and speaks with one voice; Appendix E becomes
+the only complete mapping and explicitly carries the duty to track authority
+changes. Updated in this change set: `02-constitution.md` §5.5,
+`04-architecture.md` §7.6 and the Tamiyo view line, `01-claim.md`,
+`03-principles.md` 6.9, `appendices/newsroom.md` (reframed),
+`00-INDEX.md`, `appendices/good-bad-sentences.md`, `ops/migration.md`,
+`ops/repo-structure.md` §30, `assets/model.dsl`, `AGENTS.md`,
+`ARCHITECTURE.md`, `README.md`, `docs/adr/README.md`, the vision
+repo-discipline citation (mechanical; flagged for grant review), and the
+public site pages. Wiki and site gates re-run.
+
+Reversal trigger: if new contributors or publication reviewers repeatedly
+fail to grasp the authority model from the codenames alone, re-promote a
+condensed mapping into `04-architecture.md` — by ADR, never silently.
diff --git a/docs/adr/0010-containment-accountability.md b/docs/adr/0010-containment-accountability.md
@@ -0,0 +1,97 @@
+# ADR-0010 — Name the owner of emergency containment: rollbacks are Isperia's accountability
+
+Date: 2026-08-09 · Status: accepted
+Deciders: John (wave:1 resume, product session 11) · Tracker: simic-d6ea02f9a9
+Source: peer review §24
+(`../concept/reviews/2026-08-08-esper-pivot-peer-review.md`)
+
+## Context
+
+INV-28 records emergency containment as distinct from economic judgement but
+gives it no owner: "logged and reviewed" with no named authority means in
+practice nobody owns it — a real hole in a constitution built on named
+authorities. A rollback is evidence that a warrant was issued wrongly, and
+warrants are Isperia's sole output (INV-26, INV-27); nothing else in the
+system could have prevented the admission. Aurelia answers only "is there a
+problem"; Momir only "here, try this".
+
+## Decision
+
+Emergency containment gets a named owner and a route back to the decision.
+
+1. **Detection and the rollback stay mechanical, in Tolaria.** Waiting for
+   adjudication while the host produces NaNs would be absurd. On a declared
+   safety-invariant breach Tolaria contains immediately, then reports.
+   Detect-and-contain is mechanical; accountability is judicial. The report
+   is an account of the breach, never an opinion about the candidate —
+   Tolaria's neutrality (INV-03) is preserved, which matters because
+   "Tolaria decides when to roll back on safety grounds" is a shorter step
+   to "Tolaria has opinions about candidates" than it looks.
+2. **Accountability is Isperia's.** Every containment event routes back to
+   the decision, not just to the log. `AdmissionDecision` already carries
+   `evidence_digest`, `selected_semantic_hash`,
+   `adjudication_policy_version` and the per-candidate eligibility and veto
+   results, so the containment record names the warrant that authorised the
+   growth, the policy version in force, and the specific checks that passed
+   and should not have. A containment is thereby a defect report against a
+   policy — actionable in a way "candidate X was bad" is not.
+3. **Blame attaches to the policy version, never to
+   Isperia-the-component.** With the initial rule-driven adjudicator this is
+   literally true: a rollback means the declared thresholds were wrong, and
+   the fix is an ADR and a version bump. Retrospective re-adjudication can
+   then ask directly: *under the revised policy, would this warrant have
+   issued?* — a regression test for judgement (first-class capability
+   tracked as simic-43f5e2264a).
+4. **Cost and veto failure never share a code.** The §15.3 failure taxonomy
+   (`../design/domains/urborg.md`) gains `CONTAINMENT_CATASTROPHE`,
+   distinct from `INTEGRATION_SHOCK`: one is a cost, the other is a veto
+   failure.
+
+## Displaced constraints
+
+INV-28 amended.
+
+- Old: "**Containment distinction:** emergency safety reduction is recorded
+  as containment, not disguised as economic judgement."
+- New: "**Containment accountability:** emergency safety reduction is
+  recorded as containment, never disguised as economic judgement; Tolaria
+  detects and contains mechanically, and every containment is adjudicated by
+  Isperia back to the admitting warrant and the `adjudication_policy_version`
+  in force — a rollback is a defect report against that policy version.
+  (ADR-0010)"
+
+No other invariant changes. INV-03 (Tolaria neutrality), INV-26/27
+(warrants), and INV-29 (authority separation) are load-bearing context and
+unchanged.
+
+## Options considered
+
+- **No named owner (status quo).** Rejected: an unowned review is no
+  review; the constitution names authorities everywhere else.
+- **Tolaria owns accountability.** Rejected: collapses detection into
+  judgement and erodes INV-03 — the substrate acquires opinions about
+  candidates.
+- **Aurelia owns it (it commissioned the growth).** Rejected: Aurelia's
+  authority is pre-commit only (INV-29) and its question is "is there a
+  problem", not "should this have been admitted"; the preventable act was
+  the warrant.
+- **Emrakul owns it (it removes structure).** Rejected: Emrakul executes
+  maintenance verdicts post-commit; containment is precisely the case that
+  bypasses ordinary maintenance adjudication, and the accountability
+  question concerns the admission, not the removal.
+
+## Consequences
+
+Isperia's chapter carries the accountability subsection and invariant;
+Tolaria's chapter pins the detect-and-contain boundary; the growth-model
+transition rules and Wrenn's removal exception cite the split; the Urborg
+taxonomy gains `CONTAINMENT_CATASTROPHE` with an explicit never-share-a-code
+note. The `ContainmentEvent` record shape lands with the §9 Warrant record
+definitions (simic-0bf2c40dec), binding warrant id, policy version and the
+passed-check list. Rollbacks are rare by construction, so this channel alone
+under-feeds the veto; near-miss recording is tracked separately (the
+tail-veto training-signal wave:1 issue).
+
+Reversal trigger: if the rule-driven adjudicator is replaced by a learned
+one such that "the declared thresholds were wrong" stops being literally
+true, revisit where policy-defect blame attaches — by ADR, never silently.
diff --git a/docs/adr/README.md b/docs/adr/README.md
@@ -5,7 +5,7 @@ Design-doc tiering (PDR-0002, `docs/product/decisions/0002-design-doc-tiering.md
 - **Tier 0 — Constitution.** The HLD chapters under `docs/design/` (entry:
   `00-INDEX.md`; the locked core is `02-constitution.md`). Constitutional
   constraints — Namespec 2.0, the INV-01..45 invariants, authority boundaries,
-  the newsroom rule, the no-op requirement, scaffold withdrawal — change only
+  the evidence-routing rule (INV-07/INV-09), the no-op requirement, scaffold withdrawal — change only
   through an ADR that **names the displaced invariant**
   (`../design/ops/repo-structure.md#30-repository-handoff-and-custody` / repo
   discipline in the authority grant).

diff --git a/docs/design/00-INDEX.md b/docs/design/00-INDEX.md
@@ -1,6 +1,6 @@
 # Simic HLD — Index
 
-**Architecture version:** 4.1 · **Namespec:** 1.0 — locked · **Status:** canonical
+**Architecture version:** 4.1 · **Namespec:** 2.0 — locked (ADR-0008) · **Status:** canonical
 design authority (decomposed from the v4.1 monolith per [ADR-0001](../adr/0001-hld-decomposition-structure.md);
 the monolith is archived, content-identical, at
 [`../concept/archive/simic-v4.1-monolith.md`](../concept/archive/simic-v4.1-monolith.md)).
@@ -33,7 +33,7 @@ load the chapters your task names; do not load the rest.
 | `ops/observability.md` | Live/investigation/audit views and the naming-smell view |
 | `ops/repo-structure.md` | Target codebase layout, dependency direction, repository handoff |
 | `ops/migration.md` | Current-to-target migration |
-| `appendices/` | Newsroom principle, scaffold-withdrawal pattern, glossary, good/bad sentences |
+| `appendices/` | Newsroom rendering (alternative lens), scaffold-withdrawal pattern, glossary, good/bad sentences |
 | `TEMPLATE-lld.md` | Header template for Tier 2 LLDs; LLDs land just-in-time under `lld/` (reserved, empty until Phase A) |
 
 ## Reading paths
@@ -42,7 +42,7 @@ load the chapters your task names; do not load the rest.
 - **Admission / adjudication work:** `02` + `domains/isperia.md` + `domains/jin-gitaxias.md` + `07-counterfactual-engine.md`.
 - **Contract / schema work:** `02` + `05-leyline-contracts.md` + `04-architecture.md` (flow).
 - **Experiment / curriculum design:** `02` + `01-claim.md` + `programme/*`.
-- **New here:** `01` → `04` → `02`, then `appendices/newsroom.md` for the authority model.
+- **New here:** `01` → `04` → `02`; if the codenames aren't carrying the authority model for you, `appendices/newsroom.md` retells it as a newsroom.
 
 ## Citation convention
 

diff --git a/docs/design/01-claim.md b/docs/design/01-claim.md
@@ -78,11 +78,11 @@ The locked narrative grammar is:
 
 The deliberately goofy names are not decorative aliases. They encode which parts of the system are allowed to exercise agency, which parts must remain neutral infrastructure, and which sentences should sound architecturally wrong. The naming layer therefore acts as a lightweight responsibility and dependency lint.
 
-The architecture also resembles a newsroom for a non-coincidental reason: both systems must keep source observation, commissioning, authorship, standards review, production, fact-checking, publication judgement, integration, correction, archival memory, and presentation distinct. The central newsroom rule is load-bearing here:
+At the centre of the authority model sits one load-bearing routing rule:
 
-> **Nissa sends the photograph directly. Aurelia sends only the assignment brief. Momir must never receive reality through Aurelia's caption.**
+> **Nissa publishes the evidence directly to Aurelia and Momir (INV-07). Aurelia sends only the assignment brief (INV-09). Momir must never receive reality through Aurelia's caption.**
 
-The newsroom analogy is documented as an explanatory aid in §5.5 and Appendix E. The actual enforcement remains contractual: direct evidence publication, a narrow `GrowthIntent`, deterministic request resolution, immutable provenance, and tests that reject diagnostic or structural hints in Aurelia's channel.
+The enforcement is contractual: direct evidence publication, a narrow `GrowthIntent`, deterministic request resolution, immutable provenance, and tests that reject diagnostic or structural hints in Aurelia's channel. (Readers who want the authority model without the codenames will find it retold as a newsroom in Appendix E.)
 
 A uniform **Scaffold Withdrawal Pattern** governs how the architecture learns under initially noisy, variable, or sparse conditions. Tolaria first establishes causal ground truth under an Academy profile with bitwise-exact replay, Aurelia first learns on repeated host trajectories, and Momir first learns near a viable Urborg reference population. Each scaffold then passes through controlled relaxation and an independent withdrawal gate. Withdrawal removes the scaffold as an ordinary production dependency while retaining it as a reference, calibration, regression, or escalation capability. Exact replay is therefore Tolaria's metrology laboratory—not a requirement that every future field execution remain bitwise identical.