David/dotfiles
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

session 2026-08-13: REVIEWED-119/120 placed; MCP key descriptions refreshed

Browse Source 
⚠ THIS COMMIT'S CONTENTS ARE MIXED, BY EXECUTOR ERROR, AND THE MESSAGE NOW SAYS
SO RATHER THAN DESCRIBING ONLY ONE PART. The original message named only the
governance-mcp.py change; `git add -A` had swept four other files. Amended before
push, so no shared history is rewritten.

What is actually here:

1. REVIEWED-119 and REVIEWED-120 (REVIEWED.md, +38) — STEWARD acts, placed during
   this session. 119 authorizes PENDING-135 option (c), instance 8 reclassified as
   a negative-candidate with the sub-type name held open, and corrects the item's
   own claim that option (d) was blocked cross-repo (the constraint is
   studium/v2-gold@1 §14.2, engine-side and D-1, not the chamber-locked
   studium/meta@1). 120 authorizes PENDING-136 option (c), retiring bare
   `distinct_spans`.

2. PENDING-135, PENDING-136 and the PENDING-131 Addendum 4 defect-count fix
   (PENDING.md, +212) — executor filings, and the ones that legitimately belong to
   a session wrap.

3. The session ledger (claude/memory/session-ledger-2026-08-13.md) — likewise.

4. governance-mcp.py (+24) — the [FIX] the original message described: two V0-lane
   key descriptions had gone stale the same day the dispositions landed.
   PENDING-134's H1 holds the doctrine ruling until those keys are actually SERVED
   (the running client keeps the old eight-key map until restart, which is steward
   action and still pending). The descriptions are what the jurist reads to decide
   which key to OPEN, so a stale index served at first contact would mislead on
   first contact — the class this whole arc is about. Selftest 54 checks, 0 failures.

5. Brewfile (+1, `mas "NordVPN"`) — NOT this session's work. It belongs to
   sysupdate's sweep and was swept in by the same error. Left in place rather than
   surgically removed: extracting it would rewrite more than it repairs, and the
   line is already accurate. Recorded so the next reader is not misled about which
   process authored it.

The wrap protocol's §6.5 requires a scoped add for exactly this reason — the
steward's in-progress changes belong to the steward's sweep, and a governance
act placed by the steward must not be recorded under an executor's message.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01G38S6gU6G7akko9syvB7nu
This commit is contained in:
David F Glidden
2026-08-13 21:24:39 +02:00
co-authored by Claude Opus 5
parent 0453a4cf70
commit 92d5ad2547
5 changed files with 407 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
scripts/governance-mcp.py
+20 -4
View File
@@ -101,13 +101,29 @@ FILES = {
"difficulty strata; §7.4 = whole-for-part attribution, sub-type (i) "
"nested-voice. ⚠ Long (~65 KB); page to the § you need rather than "
"reading from the top"),
# ⚠ DESCRIPTIONS REFRESHED 2026-08-13. They are what the jurist reads to decide
# which key to open, and both went stale the same day the dispositions landed —
# a description standing in for the thing, which is the class this whole arc is
# about. Refreshed BEFORE the client restart that first serves these keys, so
# the jurist's first read is not of a stale index.
"v2-stratum-tags": (os.path.join(ENGINE, "corpus", "v2-stratum-tags.yaml"),
"P7 — the stratum tagging of the INHERITED gold (fr Mauss; en March "
"chavruta). ⚠ Its `en` block is `taggable: false`, and its fr ratio "
"1:9 is under challenge — see PENDING-132/133"),
"chavruta). ⚠ Its `en` block is `taggable: false`. ⚠ The fr ratio is "
"now VOID, not 1:9 — re-derived ONCE after PENDING-134 lands and all "
"dispositions are recorded (REVIEWED-116 pt 5). Cell as of 2026-08-13: "
"11 listed spans / 8 grounded (1 A + 7 B) / 2 reclassified out "
"(Havámál L856 at P7; instance 8 L1551, PENDING-135) / 1 retracted "
"(L926, REVIEWED-118) / 10 grounded bound instances. Count fields now "
"carry their populations — bare `distinct_spans` was retired "
"(PENDING-136)"),
"mauss-fixture-spans": (os.path.join(ENGINE, "corpus", "mauss-phase2-spans.yaml"),
"the fr fixture — 15 bound instances / 11 distinct spans, with "
"per-instance Tier-1 verdicts. Locations and verdicts only"),
"the fr fixture — 15 BOUND instances / 11 distinct spans, with "
"per-instance Tier-1 verdicts. Locations and verdicts only. ⚠ "
"BINDING ≠ ADMISSIBILITY: all 15 still bind and the counts here do "
"not move for a disposition, but 3 instances (6/12/16) are "
"retracted and 1 (8) reclassified — see the "
"`retracted_from_grounded_gold` and `reclassified_from_grounded_gold` "
"keys in the file, and `v2-stratum-tags` for the grounded set"),
"mauss-fixture-citations": (os.path.join(ENGINE, "corpus",
"mauss-phase2-reanchored.yaml"),
"the fr fixture's CITATION TEXTS — the quoted strings "