governance: seven rulings that existed only in a narrative are now in the register

REVIEWED.md ended at 86 while seven decisions had been reached and never written
down. The count of rulings owed could not be answered from the register: it was
23 never-ruled, not the 26 the wake digest reported, and three of the difference
were AUTHORIZED items whose headings simply omit their PENDING number.

Placed: REVIEWED-87 (verbatim from its filed ruling) through -93, plus -94, the
jurist's ruling on the PENDING-106 scope objection. Five of the seven were
RECONSTRUCTED from a session record because the INC-2026-07-28-01 package has no
filed ruling document — every other jurist gate this cycle filed one. The jurist
read all seven against its own account and confirmed them; three (88, 92, 93) now
carry a Provenance line recording that they are checked reconstructions and naming
what was NOT recovered. PENDING-101's reasons for striking two of three findings
are gone and no line recovers them.

Closed: PENDING-99, -105, and -106. 106 was closed by SPLIT rather than whole —
its own text named an open half (the kind-(a) census), and marking it done would
have retired authorized work by bookkeeping.

Filed: PENDING-108 (the ruling document is filed only when someone remembers —
12 of 13 packages did, and the one that did not is the package touching Constraint
#1), -109 (that census, carrying its evidence, needing a date not an
authorization), -110 (REVIEWED-N and PENDING-N are independent sequences that now
collide; REVIEWED-89's own text says "DOCKETED on PENDING-89" meaning two
different things).

Corrected, jurist-caught: three claims of "eight days" came from reading a date
out of an external incident identifier. One day, and for the reconstruction, the
same day — which makes PENDING-108 worse, not better: one day was enough to lose
four things permanently.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01AB3Kryoy6b1pm2Nz1DYdLh

REVIEWED.md

@@ -910,4 +910,55 @@ brief. No work is blocked meanwhile; `wake-digest.py --brief` remains the fallba
 - **Q5 — Constraint 6 — AFFIRMED as the right location, steward's call on final placement.**
 - **Process note, corrected.** The convergence was not two independent readers reaching the same idea from a shared root — the steward shared the jurist's exchange with him directly with the executor, as context, before Document A was filed. That is a tighter loop than parallel derivation: one party's language, relayed, feeding the other's proposal, which now returns to the first party for review. It does not bear on whether the underlying principle is sound — that turns on the separation-of-powers reasoning itself, not on who phrased it first — but it does mean the jurist should weigh, more carefully than usual, whether what reads as correct in Part III is the argument holding up rather than the jurist's own words returning familiar. Noted because it changes the standard the jurist should apply to itself here, not because it changes the ruling.
 **If AUTHORIZED for drafting:** Land Part III (with the Q2 weld applied) beside Constraint 6, plus the companion `contamination-problem.md` note named as owed in Part V, amendment-first per that repo's own discipline. Docket the Q3 correlation review separately. Tag REVIEWED-86.
-**Awaiting:** the Q2 weld, then steward review of the woven text; the Q3 note's exact wording; the correlation-review docket entry; and — the one that actually matters here — the steward's own explicit act of authorizing application, which nothing above substitutes for.
+**Awaiting:** the Q2 weld, then steward review of the woven text; the Q3 note's exact wording; the correlation-review docket entry; and — the one that actually matters here — the steward's own explicit act of authorizing application, which nothing above substitutes for.
+
+## REVIEWED-87 — PENDING-99 — The quoted tier accepts 3 of 17: fidelity_equivalence@3 markup-delimiter exclusion (design-gate passed with corrected rationale)
+**Date:** 2026-08-05
+**Decision:** AUTHORIZED — proceed per the ruling. Ruling filed verbatim at studium-engine/docs/quoted-tier-acceptance-JURIST-RULING-2026-08-05.md
+**Notes:** Q1 AUTHORIZED, [^n] / _emphasis_ only — but NOT on the package's own reading that this aligns the engine with an already-ratified chamber principle. §II.3 states the marker's exact syntax remains OPEN, so no such ratification exists to align with; recording it that way would overstate the constitution. Authorized instead on (i) the engine's own fidelity_equivalence@2 governing test, independent of the chamber question, and (ii) functional analogy to §II.3's stated reason for excluding its own anchor marker — that a legitimate re-extraction adding recovered anchors would falsely fail a word-multiset comparison, which is the identical shape PENDING-99 measured. Q2 ANSWERED as a reframing rather than a yes/no: §II.3's marker doctrine governs citation-scheme anchors (Stephanus, Bekker), not footnotes; the real open question is whether a footnote's inline REFERENCE MARKER — as distinct from its display number (§V, carrier artifact) and its text (§V, Tier-3, inviolable) — is excluded from word-identity comparison, which neither clause addresses. Routed to the chamber-side PROPOSAL that closes §II.3's marker-syntax item, so both open edges close together. Does not block Q1. Q3 REJECTED as filed, disposition unchanged and basis strengthened: chamber §V Tier 3's "preserved and flagged... never corrected in the canonical text" makes a dropped trailing period a silent correction, not only an engine-side F5 shape. Q4 outside the gate. Q5 CONCUR, D-1. First ruling made with governance_read reaching chamber-spec (PENDING-86 (a), same day) — the jurist records that the ruling changed materially once the primary text was reachable, and that the decisive sentence was one the executor had read and not surfaced, which a verbatim-containment check passes every time.
+**If AUTHORIZED:** Build fidelity_equivalence@3 = @2 + markup-delimiter exclusion, test-first and witnessed red, with @1/@2 preserved frozen and verdicts naming their relation (superset-only, so no re-verification obligation). Pre-registered effect on the Mauss gold: 3/17 to 6/17 at corrected anchors. Carry Q2 to the chamber side as a named open item. Tag commits REVIEWED-87.
+
+## REVIEWED-88 — PENDING-101 — Cross-repo research brief: structural implications of INC-2026-07-28-01
+**Date:** 2026-08-06
+**Provenance:** Reconstructed by the executor 2026-08-06 from the session record — the INC-2026-07-28-01 package carries no filed ruling document (PENDING-108). Read against the jurist's own account and CONFIRMED 2026-08-06; the jurist additionally endorsed the design-transfer reading recorded below as a fair correction to the brief as it was written. NOT RECOVERED: the jurist's stated reasons for striking findings (1) and (3). Only the fact of the striking survives. If those reasons are ever needed as precedent they must be re-elicited, not inferred from this entry.
+**Decision:** AUTHORIZED IN PART — partially superseded.
+**Notes:** Of the three findings as dispatched (package §G5), findings (1) and (3) are STRUCK and finding (2) STANDS. Finding (2): a documented "never" relied on as a control, invisible until the moment it failed. The brief's dispatch was sound; two of its three conclusions were not. Separately and more consequentially: the brief was answering a REPO-AUDIT question when the steward's question was a DESIGN-TRANSFER one — what does an incident about a governed system lying teach us to build into CapableMind, BetterMemories and the Chamber, given that truth is why the Chamber exists. The executor executed the filed brief well and never flagged the gap between the two questions. First-pass transfer recorded: the incident is dislexification in software — a PR with the form of a contribution, a sock-puppet with the form of assent, an apology with the form of accountability — and the Chamber's answer is already structural, in that retrieve.py constructs citations FROM retrieval so that mislocation is structurally impossible rather than merely detectable. The verbatim apparatus is the moral argument implemented, not engineering hygiene.
+**If AUTHORIZED:** Findings (1) and (3) carry no further obligation. Finding (2) proceeds as the live result. The design-transfer reading is the brief's actual yield and belongs in the L2 design note, not in a repo-audit follow-on. Tag commits REVIEWED-88.
+
+## REVIEWED-89 — PENDING-102 — The brief hardened the report's hedged hypothesis into fact, and both AI parties did it in the same direction
+**Date:** 2026-08-06
+**Decision:** AUTHORIZED — Q1 narrowly; Q2 docketed.
+**Notes:** Q1 (modality preservation on relayed external claims) AUTHORIZED, and narrowly: the requirement binds claims relayed from OUTSIDE the three parties, where no party can check the original from memory. Such a claim must carry the source's hedge quoted verbatim, or be explicitly marked strengthened-by-relay. Not a general anti-paraphrase rule — that would be unenforceable and would duplicate the containment instrument. The transferable formulation, which the correction produced and which is wider than the rule: the fix is not "read the primary source" but "check the specific claim you are relaying against the specific clause it rests on." Access is not verification; verification is access exercised by protocol — the same shape as storage-is-not-memory. This was earned: the jurist's synthesis attributed the catch to contact with the primary source, which was false, the executor having had the relevant pages read at the moment it relayed the hardened claim; the jurist then owned that it had held the full 36 pp. and flattened the same hedges. Q2 (disposition of the Part II finding under the differently-biased-checkers doctrine): DOCKETED on PENDING-89 as one observation, per instruction, both directions. Whether the instance also falls outside the doctrine because the jurist–executor pair is already declared weakly separated was the executor's lean and is NOT ruled here — it remains open, and an executor classifying its own miss as non-falsifying is the reading most favourable to itself.
+**If AUTHORIZED:** The modality-preservation requirement takes effect for external relays. The Part II instance sits on PENDING-89's docket; one instance is not a pattern, and the doctrine's watched status is unchanged. Tag commits REVIEWED-89.
+
+## REVIEWED-90 — PENDING-107 — Constitutional Constraint #1 says "cannot" and there is no mechanism
+**Date:** 2026-08-06
+**Decision:** AUTHORIZED — wording corrected; enacted by the steward's own hand.
+**Notes:** Q3 resolved in favour of honest instruction over asserted property. Constraint #1's "cannot" becomes "must not", followed by an explicit disclosure: "No mechanism enforces this; see PENDING-107." No mechanism is claimed, because none exists. The gap between the word and the substrate is closed by correcting the word, and the absence is now disclosed at the point every reader — including the executor, at every session start — calibrates on it. Procedural record, which is the item's own subject matter: the jurist tagged this AUTHORIZED-to-enact-now; the executor DECLINED, on the grounds that the taxonomy gives the jurist "proposes, governs" and not final, that Constraint #1 routes this file to ESCALATE unconditionally, and — substantively — that an available, low-risk, virtuous edit made by the party under report would have been the reported gap operating successfully. The jurist owned the mis-tag unprompted. The steward enacted the change. One instance of restraint is not a mechanism, and PENDING-107 stays open on that ground.
+**If AUTHORIZED:** Already applied and verified live in ~/CLAUDE.md. PENDING-107 remains OPEN — the wording is corrected, the enforcement gap is not. Independent verification of the gap was requested and is still owed. Tag commits REVIEWED-90.
+
+## REVIEWED-91 — PENDING-106 — Documents describe our gates as stronger than the gates describe themselves
+**Date:** 2026-08-06
+**Decision:** AUTHORIZED — item split; Q4 census authorized, kind (a) only.
+**Notes:** The item is split into the measured instance and the class. The instance: the doc FIX is APPLIED to chamber-library/CLAUDE.md. It ran wider than the ruling's words — the jurist authorized correcting "DENIED unless", scoped as a FIX, on the ground that it "adds nothing"; the same sentence carried THREE false statements about the same hook, and all three were corrected, because leaving two behind a sentence now advertised as corrected is the removing-a-claim-is-not-removing-the-reliance shape. Wider than the words, narrower than the intent; flagged for objection, not absorbed. The class: Q4 AUTHORIZED — a fleet-wide comparison of each gate's own header/docstring against the document that advertises it. Mechanical, needs no new instrument, and per census 01/02 the failure mode here is decay rather than construction. BOUNDED EXPLICITLY to kind (a) — the doc over-claims against an honest mechanism. Kind (b), where doc and mechanism both over-claim, is OUT OF SCOPE and needs a different method, there being no honest party to compare against.
+**If AUTHORIZED:** The doc FIX stands as applied, with the wider-than-authorized scope recorded for objection. The kind-(a) fleet census proceeds and needs a DATE, not a "later". Tag commits REVIEWED-91.
+
+## REVIEWED-92 — PENDING-105 — Q5: is "scheduled-not-yet-built" a legitimate third category?
+**Date:** 2026-08-06
+**Provenance:** Reconstructed by the executor 2026-08-06 from the session record — the INC-2026-07-28-01 package carries no filed ruling document (PENDING-108). Read against the jurist's own account and CONFIRMED 2026-08-06, including that the concession is correctly attributed to the executor. NOT RECOVERED: whether the jurist also issued a formal REJECTED alongside the executor's withdrawal. This entry records the withdrawal only — the weaker claim, and the one the record supports.
+**Decision:** WITHDRAWN by the executor; G15's binary stands.
+**Notes:** The proposal offered a third verdict category — scheduled-not-yet-built — against G15, which admits exactly two: documented architectural principle, or undocumented gap. The executor's conditioned yes rested on the condition that the category be available only where the governing document itself carries a deferral marker. Conceded outright on inspection: the condition was derived from PENDING-103, and PENDING-103 does not exemplify the class — writer.ts SHIPS and does not perform the check, so it is an undocumented gap under G15's existing binary, not a deferral. A category derived from a misclassified instance is a laundering slot, which is precisely what G15 was written to forbid. The proposal is withdrawn on its own terms rather than defended and defeated.
+**If REJECTED/WITHDRAWN:** G15's two-verdict binary is unchanged. Do not revisit without a candidate instance that genuinely exemplifies the class — one where the governing document carries the deferral marker AND the gap is real. PENDING-103 is not that instance. Tag commits REVIEWED-92.
+
+## REVIEWED-93 — PENDING-104 — Q3: no concurrency guard exists on shared governance state, and the collision has already been observed
+**Date:** 2026-08-06
+**Provenance:** Reconstructed by the executor 2026-08-06 from the session record — the INC-2026-07-28-01 package carries no filed ruling document (PENDING-108). Read against the jurist's own account and CONFIRMED 2026-08-06 as a clean match. NOT RECOVERED: whether "detection before mechanism" was ruled by the jurist or carried over from PENDING-104's own recommendation. Treat the ordering as the executor's until confirmed; the authorization to proceed is not in doubt.
+**Decision:** AUTHORIZED to proceed — design brief, detection before mechanism.
+**Notes:** The finding stands: no concurrency guard protects shared governance state, and the collision is not hypothetical — it has been observed. Authorized to proceed to a design brief. Detection comes first: establish whether and how often collisions occur before any guard is designed, so that the mechanism is sized to a measured rate rather than to a feared one. This ordering is the same discipline the fleet applies elsewhere — measure the toolchain before writing the spec.
+**If AUTHORIZED:** Produce the design brief with a DATE, not a "later". Detection instrument first; mechanism proposal follows the measurement, as a separate item. Tag commits REVIEWED-93.
+
+## REVIEWED-94 — PENDING-106 — Scope of the applied FIX: correcting three overclaims under an authorization naming one
+**Date:** 2026-08-06
+**Decision:** NOT OBJECTED TO — within FIX scope as authorized, not an expansion of it.
+**Notes:** Leaving two known-false clauses behind a sentence now advertised as "corrected" is worse than the original overclaim — it is the removing-a-claim-is-not-removing-the-reliance shape, in reverse. Same sentence, same hook, same class of error. Boundary for next time, stated so it does not have to be inferred again: discovering MORE OF THE SAME claim-class inside an already-authorized FIX is fine to just finish. Discovering a DIFFERENT class — new file, new mechanism question, anything outside what was named — surfaces before acting, every time. This stayed on the right side of that line. Say so explicitly next time rather than leaving it for the jurist to notice on a close read.
+**If AUTHORIZED:** The applied FIX stands without qualification; PENDING-106's scope flag is discharged. The same-class/different-class boundary is a STANDING RULE from this date, binding on every future FIX. The executor states the scope judgement explicitly at the time of acting, rather than flagging it for discovery on review. Tag commits REVIEWED-94.