skills: build both authorized harvest proposals (2026-07-27)

/wake-up PATCH — substrate-check the briefing's backlog section. REVIEWED.md's "If AUTHORIZED: build X" clauses record what was AUTHORIZED, never what was DONE; the same holds for a PENDING item's Awaiting line and any tracker's next steps. Earned: the wake reported REVIEWED-72/73/74 as authorized-but-unbuilt when TWO were already built and landed, and the wave reported as blocked was already unblocked. The patch requires verifying against the substrate (code, spec header, repo CLAUDE.md) and marking each item verified/unverified — because the wake briefing is the highest-leverage place a false claim can land: it shapes the steward's picture of their own project before any work begins, and arrives with the authority of a status report. /field-divergence-sweep CREATE — the standing probe for one value computed in more than one place. Core: derive the rule from what a CONSUMER must do, never by picking the surviving implementation (comparison is selection, not derivation); enumerate and test the shapes where each candidate happens to be right (complementary-correctness defeats sampling); collapse to one imported implementation; migrations RECOMPUTE rather than adjust; land producer-then-consumers in one change-set with a byte-diff proof. Grounded in the proven source_lines run rather than recall, including the failure the skill exists to prevent — it found the field computed two ways, then both ways wrong, then the third wrongness inside a fix committed an hour earlier (lintott off by 308 lines). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Xefg5EXwcpd9RMAr63dWrD
2026-07-27 19:39:35 +02:00
parent ffb9b09b48
commit 84a23d8550
3 changed files with 125 additions and 3 deletions
@@ -52,10 +52,10 @@ The single place proposed skills live so they don't evaporate between sessions.

 | Skill | Kind | One-line | Origin | Status |
 |---|---|---|---|---|
-| `/wake-up` | patch | **Substrate-check the briefing's backlog section.** §3's "What's unresolved" currently lets REVIEWED.md's *"If AUTHORIZED: build …"* clauses be read as *status*. They are **forward instructions, not status** — I told the steward at wake that REVIEWED-72/73/74 were all authorized-but-unbuilt; **2 of 3 were already built and landed** (v2.6.0), and the wave I reported as blocked was already unblocked. Proposed patch: before listing an authorized item as outstanding, verify against the substrate (code / spec header / repo CLAUDE.md), and say "verified against substrate" or "unverified" in the briefing. The wake briefing is a claim surface like any other, and it is the **highest-leverage place** for a false claim to land — it shapes the steward's picture of their own project before any work begins. | 2026-07-27 (steward-visible error, self-caught within the same turn) | **PROPOSED** |
-| `/field-divergence-sweep` | create | **Sweep for one field computed in more than one place, then derive the rule from the consumer.** Method proven this session at steward direction, and the yield was not zero on the first run: grep the fleet for multi-site computations of the same field → for each, ask *what must a consumer be able to DO with this value* and derive the rule from that (never pick the surviving implementation — that is selection, not derivation) → enumerate the shapes where each existing candidate happens to be right and test **all** of them (complementary-correctness defeats sampling) → collapse to ONE imported implementation → any migration RECOMPUTES, never does arithmetic on the stored value. Found `source_lines` wrong **twice** (including in a fix committed an hour earlier; lintott off by **308 lines**), and cleared `sha256` + the tokenizers with an empirical cross-check. Same probe as the no-op orphan sweep, aimed at **values** instead of stages. Steward: *"this instance says the yield won't be zero."* | 2026-07-27 (steward-directed; grounded in [[feedback-derive-the-rule-from-the-consumer-not-from-the-survivor]]) | **PROPOSED** |
+| `/wake-up` | patch | **Substrate-check the briefing's backlog section.** §3's "What's unresolved" currently lets REVIEWED.md's *"If AUTHORIZED: build …"* clauses be read as *status*. They are **forward instructions, not status** — I told the steward at wake that REVIEWED-72/73/74 were all authorized-but-unbuilt; **2 of 3 were already built and landed** (v2.6.0), and the wave I reported as blocked was already unblocked. Proposed patch: before listing an authorized item as outstanding, verify against the substrate (code / spec header / repo CLAUDE.md), and say "verified against substrate" or "unverified" in the briefing. The wake briefing is a claim surface like any other, and it is the **highest-leverage place** for a false claim to land — it shapes the steward's picture of their own project before any work begins. | 2026-07-27 (steward-visible error, self-caught within the same turn) | **BUILT 2026-07-27** (steward-authorized; provenance comment in SKILL.md §3) |
+| `/field-divergence-sweep` | create | **Sweep for one field computed in more than one place, then derive the rule from the consumer.** Method proven this session at steward direction, and the yield was not zero on the first run: grep the fleet for multi-site computations of the same field → for each, ask *what must a consumer be able to DO with this value* and derive the rule from that (never pick the surviving implementation — that is selection, not derivation) → enumerate the shapes where each existing candidate happens to be right and test **all** of them (complementary-correctness defeats sampling) → collapse to ONE imported implementation → any migration RECOMPUTES, never does arithmetic on the stored value. Found `source_lines` wrong **twice** (including in a fix committed an hour earlier; lintott off by **308 lines**), and cleared `sha256` + the tokenizers with an empirical cross-check. Same probe as the no-op orphan sweep, aimed at **values** instead of stages. Steward: *"this instance says the yield won't be zero."* | 2026-07-27 (steward-directed; grounded in [[feedback-derive-the-rule-from-the-consumer-not-from-the-survivor]]) | **BUILT 2026-07-27** — `~/dotfiles/claude/skills/field-divergence-sweep/SKILL.md`, symlinked into `~/.claude/skills/` (authored-skill convention); grounded in the proven `source_lines` run, not recall |

-*(Both are load-bearing rather than tidy-up: the first is a correction to a briefing surface that misled the steward, the second is a method that found a live 308-line coordinate error on its first run. No other harvest — the session's other lessons are banked as feedback memories, not skills.)*
+**BOTH AUTHORIZED + BUILT 2026-07-27 (same sitting).** *(Both are load-bearing rather than tidy-up: the first is a correction to a briefing surface that misled the steward, the second is a method that found a live 308-line coordinate error on its first run. No other harvest — the session's other lessons are banked as feedback memories, not skills.)*

 ## Open proposals