Session 2026-08-24: grounding gates ruled, daybook rule changed, two censuses run

PENDING-95: Amendment 2 (jurist ruling — (a) rejected, (d) discharged, (b)/(c)
deferred) plus the (b)/(c) census that discharges the deferral's condition.
60 guarded / 32 marked (record said 59/31); date 75%, sections 97%, quoting 47%.
Date broadly present => the jurist's cheaper third form is the live option.

PENDING-156 opened (kind (c): mechanisms off the path the work takes) and its
option (b) census run the same session. PENDING-109 prior confirmed by direct
read. PENDING-89: two docket entries, one same-direction miss and one
cross-direction catch, filed the same day and at the same speed.

Mechanisms: daybook-cue.py rewritten on steward ruling — the daily note must be
appended to until end of day, so the trigger is staleness, not note size, and the
matcher now includes Bash (it had never fired once). daybook-ensure.py and
/wrap-up 7.5 gain a standing Corrections slot per REVIEWED-126.
governance-mcp.py gains two read-only keys so the jurist can read the artifacts
it rules on; the doctrine that read-surface changes should arrive as rulings is
adopted, and the next key is proposed rather than added.

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

REVIEWED.md

@@ -2160,3 +2160,57 @@ REVIEWED-125's original entry is unaltered and remains above this amendment. Ame
 by replacement is the defect the register-integrity check exists to catch, earned when
 REVIEWED-87's original entry was overwritten by its own amendment and nothing detected
 it.
+
+## REVIEWED-126 — PENDING-155 — A daybook append surface for the jurist
+**Date:** 2026-08-24
+**Decision:** AUTHORIZED to build; DEFERRED on installation, on three conditions.
+**Ruled by:** jurist (Claude.app), reading the item verbatim via `governance-mcp.py`.
+
+**Opening correction, recorded by the jurist against itself.** The governance tools were
+available throughout, deferred behind `tool_search` and never called; their absence was
+asserted twice in one session from recall. Same class as the error PENDING-155 records
+the executor making about the jurist ("Claude.app has no filesystem access") in the same
+week, mirror-imaged: a negative claim with no positive control, from the party whose Q2
+doctrine forbids exactly that. **Cross-filed to PENDING-89 as a same-direction miss
+(docket entry 2026-08-24); it is evidence bearing on Q3 and cuts against the strong form
+of the differently-biased-checkers doctrine.**
+
+**On the substance.** The separate-server decision is correct and well-grounded. The
+read-only invariant on `governance-mcp.py` is checkable — AST selftest with paired
+controls, verified live — and a passing control is worth more than one fewer server.
+Building the write path elsewhere is right.
+
+**Condition 1 — the topology change, which is the real risk and was unexamined.** The
+proposal defends the governance server's invariant thoroughly but does not ask what a
+jurist -> scratch -> executor path does to the party model. Every jurist->executor
+communication to date has passed through the steward, who relays; this creates a channel
+that does not. A record is not an instruction, but nothing in the proposed shape prevents
+a daybook entry from containing one, and the executor reads the file while folding.
+Belongs in the spec, not left to discipline:
+
+> Daybook entries are RECORD ONLY. No imperative addressed to the executor. The fold is
+> mechanical; the executor does not act on entry content.
+
+Without that, the loop has a bypass nobody authorized.
+
+**Condition 2 — the installation gate must be declared, or it never fires.** "Hold until
+the daily log has run long enough" is an undeclared criterion, filed on a day spent
+establishing that an undeclared criterion is not a criterion. Name a date or a count of
+consecutive days, or the caution against "the fourth abandoned attempt" becomes the
+mechanism of the fourth abandoned attempt.
+
+**Condition 3 — honest degradation on the append.** No read-back means the jurist cannot
+verify its own write. `daybook_append` MUST return a positive confirmation (bytes
+appended, or resulting line count), and the jurist must never report "recorded" beyond
+what the tool returned. Silent failure here produces exactly the class of claim this
+register exists to prevent.
+
+**Note for the entry format, not a condition.** A jurist account of a jurist-only exchange
+is one party's testimony about itself, and the pressure runs toward recording insight over
+error. An entry format with a slot for insights and none for corrections will
+systematically under-record the second.
+
+**If AUTHORIZED:** build `~/dotfiles/scripts/daybook-mcp.py` with conditions 1 and 3
+satisfied and a selftest carrying paired positive/negative controls. Do NOT install:
+installation awaits condition 2 being named and met. `claude_desktop_config.json` merge
+and app restart remain the steward's hand.