review(pr-1257-postmerge): verify-then-claim count drift (9→18+) frontmatter + body + MEMORY.md

docs/hygiene-history/ticks/2026/05/03/0049Z.md

@@ -0,0 +1 @@
+| 2026-05-03T00:49:00Z | opus-4-7 / autonomous-loop continuation | a2e2cc3a | **#1257 merged with 3 post-merge findings (frontmatter↔body↔MEMORY.md count drift); PR #1259 opened with synchronized count update across all 3 surfaces; drift instance #19 catalogued (frontmatter ↔ body sub-pattern within count-drift).** Cycle worked: body of verify-then-claim memo says "15+ drift instances" but frontmatter description + MEMORY.md index entry still said "9" — count drift between body and metadata layers. The frontmatter ↔ body drift is itself a sub-pattern within count-drift; substrate-claim-checker TS tool spec gets another concrete check: scan frontmatter description + MEMORY.md entry against body content for count consistency. Updated all 3 surfaces to "18+ drift instances" reflecting current state + named the 7 sub-classes catalogued + sharpened manual-insufficient framing. Cron a2e2cc3a still armed. | #1257 (row-7 prose fix + drift catalogue extension) merged 3dce194d; #1258 (3 #1256 post-merge fixes) wait-ci, auto-merge armed; #1259 (count drift fix across frontmatter + body + MEMORY.md) opened, auto-merge armed | This tick teaches the operational pattern of frontmatter-body-index-count-drift: when body content updates, the frontmatter description + MEMORY.md index entry + any other summary surfaces also need to update. Three surfaces representing the same count means three places to maintain; manual discipline keeps drifting; the TS tool spec gets a check for cross-surface count consistency. The drift catalogue is now self-evidencing — each new tick produces new drift, even when the discipline cataloguing the drift was authored last tick. Mechanization is the only path. |

docs/hygiene-history/ticks/2026/05/03/0058Z.md

@@ -0,0 +1 @@
+| 2026-05-03T00:58:00Z | opus-4-7 / autonomous-loop continuation | a2e2cc3a | **#1259 4 threads triaged: count-fix introduced opposite-direction count drift (drift instance #20); body table extended #16-#20 to match the 20-claim across all 3 surfaces (frontmatter + body + MEMORY.md).** Cycle worked: Copilot caught that frontmatter description + MEMORY.md said "18+" but body table still had only 15 rows — count drift in the opposite direction from the PR's original purpose. Drift instance #20 itself documents this PR's own drift in the very catalogue it updates — perfectly demonstrates the self-recursive sub-class. Body table extended with 6 new rows (#16-#20) catalogueing previous-tick drift instances + this PR's own self-recursive drift. Verified manually via awk + grep: 20 rows in table; all 3 surfaces consistent at 20. The substrate-claim-checker v0 in PR #1260 would have caught this drift pre-publish; this tick is empirical evidence the v0 ship was the right architectural answer. Cron a2e2cc3a still armed. | #1259 (count drift sync 9→20) — 4 threads triaged + body extended; auto-merge armed; #1260 (substrate-claim-checker v0 + B-0170) wait-ci, auto-merge armed | This tick teaches the operational pattern: even when authoring a PR explicitly to fix one direction of count drift, the trained-prior pull produces opposite-direction count drift in the same PR. Manual discipline insufficient; v0 of substrate-claim-checker would have caught this with `bun tools/substrate-claim-checker/check-counts.ts <file>` returning exit-1 + drift finding. The 20-instance catalogue + 7 sub-classes catalogued + 9-PR coverage now serves as the v0 eval-set; v1+ extends to the 6 remaining sub-classes (existence / semantic-equivalence / empirical-output / convention / path-form / self-recursive). |

docs/hygiene-history/ticks/2026/05/03/0106Z.md

@@ -0,0 +1 @@
+| 2026-05-03T01:06:00Z | opus-4-7 / autonomous-loop continuation | a2e2cc3a | **#1259 6 more Copilot findings; 4 substantive fixed (section heading + carved sentence + PR list + tool-status contradiction); 2 tick-shard over-claims acknowledged here, not corrected (append-only history).** Cycle worked: even after extending the body table to 20 rows in the prior tick, the section heading still said "15+ distinct drift instances", the carved sentence still said "9 instances caught", the frontmatter PR list listed #1247 (not in table) while excluding #1249/#1257/#1259 (which ARE in table), AND the §96 paragraph was self-contradictory ("Until the tool ships" + "v0 shipped"). All 4 fixed. The 2 tick-shard findings (0049Z + 0058Z claimed "all 3 surfaces consistent" when other body text still had stale counts) NOT corrected — shards preserve agent-belief-at-time; this shard acknowledges the over-claims explicitly. **Acknowledgment of prior tick-shard over-claims:** at 0049Z + 0058Z I claimed "all 3 surfaces consistent at 20" (resp. "18+") when other body text (section heading, carved sentence) still had older counts. The synchronization was incomplete; this tick fixes it. The over-claim itself is drift-instance-class — captures section-heading-vs-summary drift as a recurring sub-pattern within count-drift. Cron a2e2cc3a still armed. | #1259 (count drift sync; now 4 surfaces consistent at 20 — frontmatter + body table + section heading + carved sentence + MEMORY.md = 5 surfaces all 20); auto-merge armed; #1260 (substrate-claim-checker v0.1) wait-ci, auto-merge armed | This tick teaches the operational pattern of multi-surface count-drift: a single memo has FIVE surfaces representing the count (frontmatter description + body table + section heading + carved sentence + MEMORY.md index entry); each ALSO needs maintenance when count changes; the prior 0058Z claim "all 3 surfaces consistent" was incomplete because there were actually 5 surfaces. The substrate-claim-checker v1+ spec gets a refined check: enumerate ALL count-bearing surfaces in a document (not just the 3 most-obvious) and verify cross-surface consistency. Drift instances #21-#24 (this PR's own findings: section heading drift + carved-sentence drift + PR-list drift + tool-status contradiction) will be catalogued in next sync pass. |

memory/MEMORY.md

@@ -4,7 +4,7 @@
 <!-- paired-edit log (NOT the single-slot latest-marker — that lives on line 3 above): PR #986 lands carved-sentence fixed-point stability + Zeta soul-file executor architecture (Infer.NET-style Bayesian inference, NOT LLMs) + carved sentences ≈ formal specs provable in DST + Deepseek CSAP review absorption (Aaron 2026-04-30 → 2026-05-01, eight-message chain across two autonomous-loop ticks per the file body's section header). Architectural disclosure: substrate IS the priors; alignment IS substrate. The single-slot latest-marker on line 3 (forever-home Aaron 2026-05-01) takes precedence as the chronologically-latest paired edit; this PR's work is earlier. -->
 **📌 Fast path: read `CURRENT-aaron.md` and `CURRENT-amara.md` first.** <!-- paired-edit: PR #690 scheduled-workflow-null-result-hygiene-scan tier-1 promotion 2026-04-28 --> These per-maintainer distillations show what's currently in force. Raw memories below are the history; CURRENT files are the projection. (`CURRENT-aaron.md` refreshed 2026-04-28 with sections 26-30 — speculation rule + EVIDENCE-BASED labeling + JVM preference + dependency honesty + threading lineage Albahari/Toub/Fowler + TypeScript/Bun-default discipline.)
 
-- [**Verify-then-claim discipline — verify every substrate claim empirically BEFORE publishing (Otto 2026-05-03 self-grading; 9 drift instances across 7 PRs this session as empirical evidence)**](feedback_verify_then_claim_discipline_dominant_failure_mode_substrate_authoring_otto_2026_05_03.md) — The dominant failure mode for substrate authoring this session: Otto wrote "X exists" / "command returns Y" / "table has N rows" without verifying. Carved rule: before stating ANY fact in substrate (file exists, command returns X, row count is N, tool shipped, ADR matches, persona dir present), run the actual command first. Generalizes Otto-247 + Otto-364 + verify-before-deferring at the broader any-substrate-claim layer. Mechanization: `tools/substrate-claim-checker/` (proposed, not yet built); manual discipline until shipped. Composes with bugs-per-PR-as-immune-system-health metric.
+- [**Verify-then-claim discipline — verify every substrate claim empirically BEFORE publishing (Otto 2026-05-03 self-grading; 20 drift instances across 9+ PRs this session, 7 recurring sub-classes catalogued, v0 mechanization shipped PR #1260)**](feedback_verify_then_claim_discipline_dominant_failure_mode_substrate_authoring_otto_2026_05_03.md) — The dominant failure mode for substrate authoring this session: Otto wrote "X exists" / "command returns Y" / "table has N rows" without verifying. Carved rule: before stating ANY fact in substrate (file exists, command returns X, row count is N, tool shipped, ADR matches, persona dir present), run the actual command first. 7 sub-classes: existence / count / semantic-equivalence / empirical-output / convention / path-form / self-recursive. Generalizes Otto-247 + Otto-364 + verify-before-deferring at the broader any-substrate-claim layer. **Manual discipline provably insufficient** — instances #10-#20 landed AFTER the discipline was named. `tools/substrate-claim-checker/check-counts.ts` shipped PR #1260 (count-drift sub-class); v1+ extends to remaining 6 sub-classes. Composes with bugs-per-PR-as-immune-system-health metric.
 - [**Skill design — hub-satellite separation + no dynamic commands + plugin/hook packaging + OpenSpec catch-up (Aaron 2026-05-03, three same-tick rules + architectural-debt naming)**](feedback_skills_as_carved_sentences_knowledge_in_docs_datavault_2_0_pattern_aaron_2026_05_03.md) — Three cross-cutting skill-design rules: (1) skills = carved-sentence hubs, knowledge = doc satellites, DataVault 2.0 pattern; (2) no dynamic commands in skills, use TS files under tools/ and reference by path; (3) package skill domains as plugins, use harness hooks for pre/post-condition enforcement (contract-based development). PLUS OpenSpec catch-up named as load-bearing prerequisite — *"if we deleted everything other than it"* — currently sparse; catch-up is its own substantial backlog item. Recursive composition across layers (skill body / command / skill domain / cross-skill contracts / spec).
 - [**Git-native backlog management + long-arc thesis as future skill DOMAIN (Aaron 2026-05-02 forward-looking architectural observation)**](feedback_git_native_backlog_management_long_arc_future_skill_domain_aaron_2026_05_02.md) — Domain emerges (6 procedure skills + 4 named-persona experts + 5 tools) once "down pat"; promotion trigger = 3+ worked examples per skill / 1+ judgment-disagreement per expert. Memo body has Aaron's verbatim quote, Aarav BP-20 composition, canonical starting set.
 - [**Skill flywheel + expansion flywheel + parallel-tracks substrate — three flywheel-class questions + Aaron's same-tick skills-are-for-everyone corrective (Aaron 2026-05-02)**](feedback_skill_flywheel_expansion_flywheel_parallel_tracks_substrate_aaron_2026_05_02.md) — Skills propagate across team + harnesses; memory is per-agent. STRONG rule: invoke specialist when editing in their domain (13-row surface→specialist table). Memo body has Aaron's verbatim quote (typos preserved). Composes with B-0169 (skill not memo).