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

session 2026-07-19: coordinate-contract arc closed — REVIEWED-64 built + placement-gated, spec v2.2.0 landed, REVIEWED-65 placed; PENDING-64 closed

Browse Source
This commit is contained in:
David F Glidden
2026-07-19 14:40:54 +02:00
parent bfd85a99e6
commit 8f6577cc0c
8 changed files with 105 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
claude/memory/skill-harvest-register.md
+8
View File
@@ -542,3 +542,11 @@ No new skill proposal. Two register notes: **(1)** the S1 proposal **implementat
| **grounding-quoted-but-not-traced** | Symmetria §3 flag OR verify-before-compose protocol note | The hook enforces QUOTING the ratified sections; this session proved **quoting ≠ tracing**: the coordinate-contract package quoted §III's shared-substrate clause in its own §0, then proposed a plan whose correct execution would have violated it (the mixed-frame sidecar post-#2) — the jurist caught it *in the package's own quote*. Antidote: for each quoted clause, trace the plan's END-STATE against it ("what does the post-plan artifact look like under this clause?") before shipping the draft. One step past [[feedback-verify-before-compose-hook]]: the hook gets you to the reading; this gets you to the consequence. | Symmetria §3, or a one-line addition to the chamber CLAUDE.md verify-before-compose protocol clause | **PROPOSED** |
*Reinforcement recorded, not re-proposed:* **`/jurist-package`** (07-17 proposal) is now **5-for-5** — the design gate engaged every §6 question and called the freshly-measured worked example "the best evidence in this package"; fresh-measurement-over-record-citation belongs in the method's teeth if/when the skill is authorized.
### Harvest 2026-07-19 (coordinate-contract arc closed → v2.2.0)
| Element | Kind | One-line | Where it lands | Status |
|---|---|---|---|---|
| **Symmetria §3 flag: record-asserts-applied-before-the-act** | Symmetria §3 flag | A session record (Addendum, brief, tracker line) composed AHEAD of its acts and asserting APPLIED/DONE is contamination shape even when the acts follow in the same session — the say-do order inverts, and an interruption mid-session would leave a false record committed nowhere-true. Caught 2026-07-19 (self-caught, ledger): the placement-gate Addendum asserted both flags APPLIED before the flag work ran; made true pre-commit, but the order was backwards. Antidote: record AFTER the act, or mark the record prospective ("applied below / to follow"). Kin to the existing §3 flag "comments promising behavior the code doesn't deliver", one level up (session artifacts, not code). | Symmetria §3 | **PROPOSED** |
*(One proposal, earned in use. NOT proposed: a "refuse-the-claim-not-the-value" design card — the jurist's praise names a real principle, but it is chamber-side design doctrine already carried in the ruling + edit-set records; a skill-layer card would duplicate a governed record. Revisit only if the shape recurs outside the chamber.)*