session 2026-07-19 late-night: S2b whole — omnibus unit + witness vocab + Eichmann pilot ran+RULED (PENDING-67 filed, interim EPUB stop, order-gap docketed) + REVIEWED-55 resolved stale + four-stroke harvest review ruled&built

claude/skills/symmetria/SKILL.md

@@ -72,8 +72,11 @@ Notice these in your own writing or in code you read:
 - "As discussed" / "as planned" without re-checking what was agreed.
 - Synthesis before exploration is complete.
 - Bypassing safety mechanisms without explicit steward authorization.
-- Frame-inheritance from a prior verification into an untested domain — the prior pass tested what it tested; an extension claims what it did not test. Re-run verification at the scope of the extension. <!-- 2026-06-05: trust-prior-pass-frame flag (steward-authorized; feedback memory 2026-05-28) -->
+- Frame-inheritance from a prior verification into an untested domain — the prior pass tested what it tested; an extension claims what it did not test. Re-run verification at the scope of the extension. This includes reusing an *instrument* across a tier/case it wasn't demonstrated on (a check proven for one tier is not proven for another — demonstrate per case), and restating a finding scoped to one condition as an unconditional verdict (verify a claim's scope before generalizing it). <!-- 2026-06-05: trust-prior-pass-frame flag (steward-authorized; feedback memory 2026-05-28); 2026-07-19 harvest review: widened with per-tier-demonstration (07-12, V-TEXT k-gram false-flagging V-DSL) + claim-scope (06-28, "olmOCR RETIRED" overclaim) -->
 - A census read through truncation (`| head -N`, a clipped listing, a sampled grep) treated as the full census. Count first (`wc -l`), then look — coverage claims require censused routes, not seen routes. <!-- 2026-06-05: 3 instances caught same day -->
+- A claim asserted from a **derived or recalled form when the substrate is checkable** — a regex over derived text, a fuzzy-matcher hit read as membership, a soft classification where a checkable number/fact/test was producible, an answer from training where the banked record (docs, registers, prior briefs) already holds the considered answer, instructions re-derived instead of citing the governed doc, acting in a repo before reading its CLAUDE.md. Verify against the substrate first; produce the checkable claim; if it can't be produced cleanly, that inability is the finding. <!-- 2026-07-19 harvest review (steward-authorized): consolidates claim-from-derived-artifact (07-03, jurist-elevated standing practice, 3×) · fuzzy-matcher membership (06-15, 4× one session) · soft-classification-over-checkable-claim (07-13, steward-named 5×/day) · answer-from-training-before-banked-record (07-14, recurred in 48h) · re-derived-instructions (07-01) · enter-repo-read-docs-first (07-09) -->
+- **Completion is a tripwire** — the *feeling* of "done" (a fluent pass, a wall of green, a "finally", a closable-now bucket) is the cue to verify the tail, not the signal to ship. Ask which failure class each green check can actually *see*; reconcile any closed/complete claim against the authoritative source, not the derived close-list; treat the closable-vs-blocked partition as itself a claim to check. <!-- 2026-07-19 harvest review (steward-authorized): recurrence-promoted per the governed watch-item pattern (memory 2026-07-06; recurrence 07-07 gate-suite-blind-to-failure-class; + closable-now-is-a-claim 07-16 jurist-named; + reconcile-before-"finally" 07-17) -->
+- **The say–do seam** — a record composed ahead of its acts (an Addendum/tracker/brief asserting APPLIED or DONE before the act ran); a grounding *quoted* but not *traced* (for each quoted clause, trace the plan's END-state against it — and one level deeper: which way does the inference run in the new state; is any class you named actually two kinds with opposite dispositions). Record after the act, or mark the record prospective. <!-- 2026-07-19 harvest review (steward-authorized): the 07-19 family — record-asserts-applied-before-the-act (self-caught at the ledger) · grounding-quoted-but-not-traced (jurist-caught in the package's own quote) · consequence-trace-one-level-shallow (both PENDING-65 struck framings); kin to comments-promising-behavior, at the session-artifact level -->
 
 
 When you notice one, name it. In chat, in the ledger, or both. Don't accumulate observations for "a good moment" — there is no good moment, only now.