session 2026-07-27 evening: PENDING-76/77/78 placed; governance drift-check built + wired into /wake-up

PENDING-76 remanded by jurist — required count returned 0 of 11 (the package's own
IV.2 refinement proved its target category empty); executor recommends withdrawal.
PENDING-77 (5 structural defects) and PENDING-78 (.app preferences) released by the
ruling from needing it. Drift check reports contradicted state claims at every wake
and corrects nothing — detection needs no authorization, correction does.

MEMORY.md compacted 20.5KB -> 17.1KB (budget hook); prior Active Session demoted to
MEMORY-reference.md. CLAUDE.md and REVIEWED.md untouched.

Co-Authored-By: Claude <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Xefg5EXwcpd9RMAr63dWrD
This commit is contained in:
David F Glidden
2026-07-27 22:14:25 +02:00
co-authored by Claude
parent 84a23d8550
commit e8b6ce06a3
8 changed files with 338 additions and 9 deletions
+2
View File
@@ -81,6 +81,8 @@ The durable memory *is* the Markdown + JSONL files (git-tracked, dual-remote). T
- Read `~/PENDING.md` — extract items with status PENDING
- Read `~/REVIEWED.md` — extract recent AUTHORIZED/DEFERRED/REJECTED decisions
- Run `git -C ~/dotfiles status -sb` — if dirty or ahead of its remote, the previous wrap's push (wrap-up §6.5) failed or something wrote outside a session. Surface it in the briefing. **Do not commit or push at wake** — the wake reads, it doesn't mutate; the push belongs to the wrap.
- **Governance drift check** — run `python3 ~/dotfiles/scripts/governance-drift-check.py` (~0.2 s). It reports state claims in `~/CLAUDE.md` that the substrate contradicts: unresolvable paths, named tools with no configured server, hooks claimed to fire that are unconfigured, expired date horizons, and structural damage. **Report the count in the briefing; list the findings only if the count changed since the last wake.** Do not correct — correction of doctrine or steward-held state requires `[ESCALATE]` (Constitutional Constraint #1); this step is detection only, which needs no authorization. If the script prints `INSTRUMENT NOT VERIFIED`, its positive controls failed — treat the result as unestablished rather than clean. <!-- 2026-07-27: built on steward authorization. The governance document had carried 9 substrate-contradicted claims for up to 4 months because detection and correction were priced identically; separating them makes staleness *visible* rather than *misleading* — Constitutional Constraint #4 applied to the governance document itself. Every check carries a same-run positive control per the epistemic standard ratified in the jurist's Q2 ruling: an absence is not evidence until the instrument is shown capable of detecting presence. -->
**d. Git state**
Run `git log --oneline -5` in each active repo (skip silently if not a git repo):