governance: steward places REVIEWED-130; record the snapshot instruction for tomorrow
REVIEWED.md carries the steward's own placement of REVIEWED-130 (81 insertions, additive; the single deletion is a trailing-newline adjustment on REVIEWED-129). Committed, not authored — the executor does not write that file (Constitutional Constraint #1). Verified content-faithful against the staged draft before placement: 5,889 chars both, whitespace-normalised identical. Also records the steward's in-session instruction about the pre-LFS snapshot, verbatim, so it survives the session boundary: it is no longer needed in place and moves tomorrow to the drive holding the decommissioned MemPalace material. Written with the three conditions that are easy to lose and expensive to discover later: move rather than migrate export (rewriting commits destroys the exact-copy property that is the snapshot's only purpose); the move must carry .git/lfs/objects, 552 objects and 975 MB, or 399 files arrive as unreadable pointers; and verify by reading back at the destination rather than by the copy succeeding — the rule learned on MemPalace, whose decommissioned material is the destination. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NvZAKSf9aqratbqHbU9LK5
This commit is contained in:
co-authored by
Claude Opus 5
parent
b28cc03737
commit
374285bb4e
+21
@@ -6110,3 +6110,24 @@ Neither number is a census result — both are haystacks. The specification has
|
||||
⚠ **The read-only guarantee was extended, and doing so found a pre-existing hole.** `governance-mcp.py` proves read-only-ness by AST **over itself**; adding a delegate put code outside that proof. Extending it to delegates surfaced (a) a **false-positive class** — bare `.replace` flagged `str.replace()`, which is why the guarantee had never been extended past one file — and (b) that `wake-digest.py`, a delegate **since before today**, was never covered. Its only real mutation is `emit_brief()`, its SessionStart-hook role, unreachable from any tool. Now handled by **declared exemption per delegate**, so a new mutating function fails until someone names it and says why — the same shape as PENDING-165's allowlist, and for the same reason.
|
||||
|
||||
**Awaiting:** nothing on (c)/(d). The 270-candidate classification pass is unscheduled and unclaimed.
|
||||
|
||||
### PENDING-165 — STEWARD INSTRUCTION, 2026-08-26, deferred to 2026-08-27
|
||||
**Recorded verbatim so it is not lost to the session boundary:**
|
||||
|
||||
> *"as for the snapshot, let's deal with that tomorrow and move it to the same drive i have the decommissioned mempalace stuff on"*
|
||||
|
||||
and, earlier in the same exchange:
|
||||
|
||||
> *"I no longer need the snapshot, the repo has been behaving normally and we've been working with it with no problems."*
|
||||
|
||||
**What this settles:** option **(c)** — removing `git-lfs` and with it the vector entirely — is no longer gated on preserving `~/_Dev/chamber-library.pre-lfs-export-20260605` in place. The snapshot moves to the external drive holding the decommissioned MemPalace material.
|
||||
|
||||
**What it does NOT settle, and what must be checked before the move:**
|
||||
- ⚠ **Move, do not `migrate export`.** Rewriting commits destroys the exact-preservation property that is the snapshot's only reason to exist (jurist, 2026-08-26).
|
||||
- ⚠ **The move must carry `.git/lfs/objects` — 552 objects, 975 MB.** A copy that takes the working tree and not the LFS store leaves 399 unreadable pointer files. **Verified 2026-08-26: all 399 tracked files resolve from local objects, 0 remote-only**, so a whole-directory copy is complete — and only a whole-directory copy is.
|
||||
- ⚠ **Verify by reading back at the destination**, not by the copy returning success. The same rule that governs the transcript archive and that was learned on MemPalace — whose decommissioned material is, fittingly, the destination.
|
||||
- ⚠ **`git-lfs` must still be installed at the moment of any future restore.** Removing it under (c) is safe only because reinstalling is a `brew install`; that fact belongs with the archive, not only here.
|
||||
|
||||
**Sequence, for tomorrow:** move + read-back verify → then (c) is free → then `Brewfile:40` and the PENDING-165 (b)/(d) guards become belt-and-braces rather than the only defence.
|
||||
|
||||
**Awaiting:** the steward, 2026-08-27. Nothing for the executor tonight.
|
||||
|
||||
Reference in New Issue
Block a user