[FIX] Land the skill-harvest FIX lane and apply its first batch (REVIEWED-85)

REVIEWED-85 was placed by the steward at 10:41 today; the wake flagged at 10:44 that /wrap-up SKILL.md was still untouched since 2026-07-07. Landing it. Precondition discharged first. The ruling states its own verification limit: the jurist could not read the skill files, so the /wrap-up §1.6 and /wake-up §2.a quotes underpinning Part III's "contradicts itself" claim were affirmed on timeline evidence rather than checked. Required before landing was mechanical containment-with-positive-control verification of exactly those quotes. Run: 7/7 contained verbatim against the live skills, 5/5 controls absent, instrument verified. §1.6 now carries the two-clause disjunctive test (the executor's own narrower single-clause alternative declined at the gate as less safe), the hard floor with its catch-all sharpened per Q4 and tied to the measured failure rather than left as open judgment, and all three instruments as mandatory. The lane is provisional pending the steward-jurist check-in. The §Important-constraints line still stated the blanket rule the ruling narrowed. Left alone it would have been a second live version of a governance rule inside the file that forbids exactly that. Reconciled, with a note saying why. First batch applied -- the four class-(i) proposals the steward raised 2026-07-29 and which REVIEWED-85 itself dispositions as batch 1, so their classification was ruled rather than self-assessed: a `## What held` ledger section (the ledger could previously only record debits), a `prevention` KG predicate capturing transfer between failure classes, one wake line surfacing it, and the retirement of the standing question's self-report framing in favour of the checkable form -- the last on the grounds contamination-problem.md gives, that direct self-report is the most contaminated form of inquiry. The FIX-lane index is created and carries all four. It records explicitly what is NOT in it: the §1.6 edit itself, which changed what the executor may do without asking and was therefore PROPOSAL by its own test. A lane cannot authorize its own construction. Register rows 174-177 marked applied. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WuMjg3ipEVa3n8CoSzoyvc
2026-08-02 11:55:15 +02:00
parent 25cf5a38eb
commit 62b92bd425
6 changed files with 99 additions and 6 deletions
@@ -0,0 +1,22 @@
+{
+ "sources": {
+   "wrap": "/Users/davidglidden/.claude/skills/wrap-up/SKILL.md",
+   "wake": "/Users/davidglidden/.claude/skills/wake-up/SKILL.md"
+ },
+ "claims": [
+  ["wrap", "This is **event-based, not change-count**"],
+  ["wrap", "apply at wrap like a tracker"],
+  ["wrap", "is surfaced for steward review, not auto-applied"],
+  ["wrap", "the same FIX-vs-PROPOSAL split, one level up"],
+  ["wrap", "Surface each as a proposal in §8 — never create, patch, or retire a skill autonomously at wrap."],
+  ["wrap", "The steward converts proposal to action; only then is a skill changed"],
+  ["wake", "Read `skill-harvest-register.md` directly — the canonical surface for open skill proposals (wrap §1.6 appends there); surface any awaiting steward authorization"]
+ ],
+ "controls": [
+  ["wrap", "never create, patch, or retire a skill autonomously at wake"],
+  ["wrap", "apply at wrap like a ledger"],
+  ["wrap", "the same HARDENING-vs-PROPOSAL split, one level up"],
+  ["wake", "surface any awaiting jurist authorization"],
+  ["wake", "the canonical surface for closed skill proposals"]
+ ]
+}