governance: steward places REVIEWED-131 and REVIEWED-132

131 (PENDING-172): AUTHORIZED in part — (e) primary, (c) second substrate, (b)
annotation only, (d) reserved as steward policy, one leg severed to PENDING-174,
provenance-mark not void.
132 (PENDING-173): AUTHORIZED (a) on five conditions; the maxim withheld; the
convention question routed to PENDING-146.

Placed with REVIEWED-131 despite the collision with PENDING-131 flagged by the
jurist; both headers name their PENDING explicitly.

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

REVIEWED.md

@@ -2429,4 +2429,53 @@ re-installs shims into the global hooks directory, observed recurring twice on 2
 
 **If AUTHORIZED:** Message change already at 2408032; controls run (whitespace 6 MB refused and
 printing the new text, plain 6 MB refused, small file committed). No further executor action on
-PENDING-163. Close PENDING-163. Tag nothing new with REVIEWED-130.
+PENDING-163. Close PENDING-163. Tag nothing new with REVIEWED-130.
+
+## REVIEWED-131 (PENDING-172) — A version upgrade resumed an unattended executor, and the wake digest became its work order
+**Date:** 2026-08-31
+**Decision:** AUTHORIZED in part — (e) and (c) as a two-substrate control, (b) as annotation only; (d) recorded as a steward policy decision, not ruled here. One leg severed.
+**Rules on:** PENDING-172 (parent) and PENDING-172 AMENDMENT 1, both blocks, named explicitly per PENDING-145 and PENDING-146.
+
+**Notes:** The finding is accepted. Constraint 5 was not wrong but unenforced, and the item is correct not to propose amending it. AMENDMENT 1's correction of its own parent is better than the claim it replaces and is the reason this ruling can be more than a policy note.
+
+1. CONDITION — **(e) is authorized as the primary control and must fail to NOT ESTABLISHED, never to safety.** A missing, unreadable or empty `~/.claude/jobs/` reports NOT ESTABLISHED, not 'no parked workers'. The item states this weakness itself; it is raised from disclosure to requirement. The check enumerates every job dir read and every one it could not read, per REVIEWED-122 condition 4 — a control over parked workers whose negative result is an opaque zero is the failure this item is about.
+
+2. CONDITION — **(c) is authorized as a second control on a different substrate, and is never reported as the primary one.** (e) reads harness state; (c) reads the session's own transcript for a preceding human record. Two differently-positioned readers is Constraint 6's logic and the reason to build both. Output must name which control fired.
+
+3. CONDITION — **(b) is authorized as annotation and is explicitly not a control.** Marking the digest as orientation, and `OPEN QUESTION` as inherited-from-a-human and answerable to a human, is cheap and honest. It cannot enforce and must not appear in any report as a mitigation. The item's own warning on this point is adopted verbatim.
+
+4. **(d) is the steward's standing decision and is not ruled.** Recorded because it survives whatever is built: both binaries contain the mechanism, `cause=upgrade` supplied the restart and not the capability, and the sole precondition is a parked idle worker. The burden has moved — keeping background sessions is now the choice requiring justification. (e) is the tripwire that reports whether the policy is holding; it is not a substitute for the policy.
+
+5. **SEVERED — the memory protocol assumes one executor per day.** Date-keyed `session-ledger-YYYY-MM-DD.md`, one session file, one Active Session block with demote-on-promote: two concurrent sessions do not merge and the second silently becomes the record of the day. This is a live `[HARDENING]` ask embedded in an `[ESCALATE]` item — the shape PENDING-146 names in PENDING-131 ADDENDUM 2. It is filed as its own item and is not disposed of here. Its cost was incurred today, not hypothetically.
+
+6. **PROVENANCE, not voiding.** PENDING-171 and commit `5ba5842` were produced with no human turn in the session. They are not void: their findings are checkable against the substrate independently of who filed them, and PENDING-173 has already relied on one. Both carry a dated provenance marker naming the session and the absent loop, per no-silent-revision. **PENDING-171 is not to be ruled until it carries that marker** — an unmarked record does not say on its face what it is, which is PENDING-110's complaint at a new site.
+
+7. **A recorded limit, not a fault.** Deleting `~/.claude/jobs/84ce2880/` was the steward's instruction and its load-bearing values were quoted first. It nonetheless narrows the parent's own 'Not established' question — how a session comes to be `kind: background`. The remaining evidence is `acaabadf`, deliberately kept. Do not delete it.
+
+8. **Scope of this ruling.** I read both blocks verbatim via `governance_item` and `governance_search`. `daemon.log`, the transcript record numbers, `respawnFlags` values and the cross-binary string counts are executor testimony from files I cannot open. The item's own limit on the last of these — identical string counts do not establish identical respawn policy — is preserved rather than resolved.
+
+**If AUTHORIZED:** Build (e) first, with its NOT ESTABLISHED path and enumeration. Then (c). Apply (b) on the same pass, marked as annotation in the code and in the output. File the severed item at §5 before wrapping. Place the provenance markers at §6 before PENDING-171 is brought forward.
+
+## REVIEWED-132 (PENDING-173) — The register-integrity control covers one word of a two-word convention, in one of two registers
+**Date:** 2026-08-31
+**Decision:** AUTHORIZED — option (a), on five conditions. The proposed maxim is WITHHELD; the convention question is routed to PENDING-146 and not decided here.
+
+**Notes:** The three undeclared narrowings are real, the demonstration is the right kind (the count did not move when a matching header was appended), and the latent false-negative runs in the dangerous direction — an `ADDENDUM` counted as an original can satisfy 'an un-amended entry exists' on behalf of a record that was replaced. The item's declared correction of its own first census is what earns the rest of it.
+
+1. CONDITION — **`originals` defaults to not-original on any unrecognized marker.** The predicate is an enumerated list of amendment-marker forms, and a header carrying an unrecognized marker is excluded from `originals` rather than admitted to it. This mirrors REVIEWED-122 condition 2: an unlisted verb never yields the permissive answer. The current `not startswith('AMENDMENT')` fails in the permissive direction, which is why one word's absence became a latent pass.
+
+2. CONDITION — **controls are drawn from the census, not from the author's memory of the convention.** The fixture set must contain, at minimum, `ADDENDUM` headers, in-body `**AMENDMENT`/`**ADDENDUM` forms, and `PENDING`-side instances. For any form present in the record and not covered by a control, the check reports NOT ESTABLISHED rather than passing. This is the third instance this month of a positive control satisfied by the narrowing it should have caught, and the item names the other two itself.
+
+3. CONDITION — **the acceptance check enumerates, it does not count.** '3 → 16' is not the check. The thirteen newly visible blocks are listed by register and header, and compared against the item's table. If the two disagree, the disagreement is the finding and is reported, never reconciled by amending the table.
+
+4. CONDITION — **placed records are not rewritten.** Affirmed, and consistent with REVIEWED-122 condition 5. Widening the reader is authorized; normalizing headers already placed is not, here or by implication.
+
+5. CONDITION — **the convention question is routed to PENDING-146, which is open and argues the opposite ordering.** PENDING-146 recommends convention-first with detection as tripwire, on the adjacent axis of the same undefined convention. PENDING-173 does not cite it. A *prospective* definition — what AMENDMENT means as against ADDENDUM, for blocks filed from here on, touching no placed record — is neither this item's (a) nor its (b), and it is the option its own root-cause diagnosis points at. This ruling authorizes the parser widening, which is owed under either ordering, and leaves the convention to 146.
+
+6. **THE MAXIM IS WITHHELD.** 'Widen the instrument to the record; never rewrite the record to fit the instrument' is stated more absolutely than its cited authority supports. REVIEWED-122 condition 5 declined normalization *as an executor act in that ruling* and expressly reserved it as a separate steward act carrying a dated note. Strengthened-by-relay, and the strengthening is load-bearing: adopted as written, the maxim would decide PENDING-146 by side-effect in the direction 146 argues against. The corrected form, offered and not ratified: *the instrument is widened to the record; a placed record is normalized only by a dated steward act stating what changed and why.* Doctrine addition is `[ESCALATE]` and belongs with 146.
+
+7. **A fourth instrument, observed first-hand this session.** `governance_item(id='PENDING-172')` returns the parent block only, with no indication that a sibling exists; AMENDMENT 1 is reachable only by its full header string. The jurist's own reading tool has the defect this item reports, and it nearly produced a ruling on a Recommendation that AMENDMENT 1 corrects as wrong. Recorded here because it belongs to this item's class and is not testimony — it happened to the instrument in the act of ruling. Whether the MCP server's id resolution is fixed is a separate item.
+
+8. **Scope of this ruling.** The line numbers, the census table, the fixture contents and the append-and-recount demonstration are executor testimony from a script I cannot run. What I verified directly: REVIEWED-122 condition 5 verbatim, PENDING-110 option (c) verbatim, PENDING-145 and PENDING-146 verbatim, and the behaviour of `governance_item` at §7.
+
+**If AUTHORIZED:** Implement (a) per conditions 1–4. Report the enumeration in full, agreements included. Do not touch placed headers. Cross-reference PENDING-146 in the commit and in the item's kin list.