Skip to content

Round 41 — OpenSpec backfill founding + operator-algebra cadence + in-round v2 supersedure + DORA substrate#31

Merged
AceHack merged 37 commits intomainfrom
round-41
Apr 21, 2026
Merged

Round 41 — OpenSpec backfill founding + operator-algebra cadence + in-round v2 supersedure + DORA substrate#31
AceHack merged 37 commits intomainfrom
round-41

Conversation

@AceHack
Copy link
Copy Markdown
Member

@AceHack AceHack commented Apr 20, 2026

Summary

Round 41 — OpenSpec backfill founding + operator-algebra cadence ship + Viktor P0 close + memory-restructure design + ledger actualisation + Round-35 holdover close + skill-tune-up catch-up + router-coherence ADR + post-Arc-8 self-correction sweep + in-round v2 supersedure closing 10 Kira findings + grandfather-claims inventory honouring v2's within-round commitment + DORA 2025 reference substrate lands in-tree.

33 commits organised into 12 narrative arcs (see docs/ROUND-HISTORY.md Round 41 section):

  • Arc 1 (d435126) — OpenSpec coverage audit surfaces ~93% of shipped F# surface lacks a capability spec; ADR docs/DECISIONS/2026-04-21-openspec-backfill-program.md commits to one-capability-per-round cadence with Viktor adversarial-audit gate.
  • Arc 2 (e51ec1b) — First cadence ship: operator-algebra capability extended with F# profile (openspec/specs/operator-algebra/profiles/fsharp.md) naming all primitive operators, chain-rule helpers, and invariants.
  • Arc 3 (92d7db2) — Viktor (spec-zealot) P0 close: four drift defects (namespace, phantom Reset, after-step scope, lifecycle phase undercount) closed in-capability.
  • Arc 4 (56f34b5) — Viktor's 10 P1 findings filed as Round-42 absorb work under parent backfill entry in docs/BACKLOG.md.
  • Arc 5 (6e6e211, 36797ba) — ROUND-HISTORY arcs 1-4 narrative + memory-folder role-restructure design plan at docs/research/memory-role-restructure-plan-2026-04-21.md (4 open sign-off questions; execution deferred to Round 42 under Auto Mode do-not-take-overly-destructive-actions clause).
  • Arc 6 (85fb352) — BP-WINDOW ledgers for Rounds 37-40 actualised with (merged via PR #30, 1e30f8c) provenance — forecast → settled observation.
  • Arc 7 (e461d9c, 15e9654) — Soraya (formal-verification-expert) tool-coverage audit on RecursiveSigned.fs skeleton closes the Round-35 holdover gate; four tool-coverage prereqs captured in BACKLOG at priority-ordered granularity (TLC CI wire-up, Z3 S2 lemma, FsCheck S4 property, FsCheck refinement cross-check).
  • Aarav catch-up (085c0e3) — skill-tune-up ranking re-run after 23-round cadence gap (ranker offline rounds 19-40); round-18 HAND-OFF-CONTRACT carry-over re-entered top-5 rather than silently dropped.
  • Arc 8 (47d92d8) — Router-coherence ADR v1 docs/DECISIONS/2026-04-21-router-coherence-claims-vs-complexity.md codifies analytic-first → empirical-second pipeline between Hiroshi (complexity-reviewer) and Daisy (claims-tester), closing Aarav's 23-round-stale round-18 finding.
  • Arc 9 (d76a09b, 2042a85, fcfa3d9, 779d7ef) — Post-Arc-8 self-correction sweep: Prereq 1 re-sized S→M after discovering no TLC CI job exists (22-round compile-only drift on RecursiveCountingLFP.tla); formal-analysis-gap-finder round-42 entry filed as recurring audit lens for "verifier-installed ≠ verifier-runs" across every spec directory; CONFLICT-RESOLUTION.md Hiroshi ↔ Daisy row closes Arc-8's canonical-authority-matrix follow-up; Kira (harsh-critic) adversarial pass over ADR 47d92d8 surfaces 3 P0 + 5 P1 + 2 P2 findings, filed as round-42 supersedure item. Pattern: Arc 8 corrects Aarav's round-18 finding; Arc 9 catches Arc 8 itself under-reviewed.
  • Arc 10 (09f0889, 4efe545, 4537365) — In-round v2 supersedure: docs/DECISIONS/2026-04-21-router-coherence-v2.md supersedes v1 in the same round, closing all 10 Kira findings via named textual closures C-P0-1 through C-P2-10 (grandfather clause bounded, reverse trigger unconditional, escalation-evidence loop unblocked, Status aligned, trigger list widened, decision-table author-bounce explicit, escalation timebox added, Kenji named as binding dispatcher, BCL-contract example fixed, scope-creep cut). v1 retained with Superseded-by header per GOVERNANCE §2 so CONFLICT-RESOLUTION.md citation chain stays resolvable. BACKLOG supersedure entry discharged in-round. Pattern: Arc 9 surfaces the under-review; Arc 10 lands the close in the same round rather than deferring the known-imperfect artefact to round-42.
  • Arc 12 (46075d6, 0111e3f) — DORA 2025 reference substrate lands in-tree: two untracked PDFs (docs/2025_state_of_ai_assisted_software_development.pdf 15MB / 138pp, docs/2025_dora_ai_capabilities_model.pdf 9MB / 94pp; CC BY-NC-SA 4.0) that had been sitting in the working tree since 2026-04-20 02:13/02:17 now committed as the in-repo substrate behind the 2026-04-20 memory promotion of DORA from external-anchor to measurement-frame starting point. Arc narrative surfaces the /next-steps ranker-scope gap (nine re-fires coasted on in-context summary rather than checking git status --short) as candidate skill-tune-up work for Aarav. In-tree citation anchors now reachable: Nyquist stability criterion (p9 fn 1) for CI-meta-loop + retractable-CD P1, "AI is an amplifier" for corporate-religion / sandbox-escape threat class, seven-capability model for external-audience round-audit vocabulary.
  • Arc 11 (d98ef2b) — Grandfather-claims inventory honours v2 Closure C-P0-1's within-round commitment: docs/research/grandfather-claims-inventory-2026-04-21.md catalogues 35 live O(·) claims at ADR-landing time (29 F# /// docstrings, 3 grey-zone F# code comments, 1 openspec/specs/operator-algebra/spec.md line, 2 docs/research/** claims). Distinguishes live claims from historical evidence. Matching docs/BACKLOG.md P2 discharge entry: one-claim-per-round cadence, ~35-round tail, Aarav graceful-degradation clause fires if ≥3 consecutive rounds pass without discharge. Pattern: without Arc 11, Arc 10 would have shipped a contract Zeta didn't meet.
  • BP-WINDOW ledger rows (098fa25, 7c4b01a, 459b218, 47b82d7, 531dc68, ec00be9, 1e31d34, 913d054, 7b581da) — per-commit window-expansion accounting; meta-ledger-only commits do not get self-referential rows (established stopping rule).

Test plan

  • dotnet build -c Release0 Warning(s), 0 Error(s) (verified this session)
  • BP-10 invisible-Unicode audit on all round-41 files including v2 ADR — clean
  • Per-commit BP-WINDOW ledger rows present for every primary-work commit (arc count = 12, primary-commit count = 12, alignment restored)
  • ADR follow-up loop closed at docs/CONFLICT-RESOLUTION.md (Hiroshi ↔ Daisy Active-tensions row pointing at v1 — supersedure-header redirect to v2 keeps the citation chain live)
  • Harsh-critic adversarial review of round-41 ADRs dispatched; v1 findings closed in-round via v2 supersedure (all 10 findings carry named textual closures in v2); audit trail preserved in BACKLOG closure annotation

Round-42 carried work

  • Memory-folder role-restructure execution (Phase 1 of 5) — gated on 4-question sign-off
  • Soraya's Prereqs 1-4 (TLC CI + Z3 + FsCheck) — M-effort; Prereq 1 now correctly sized
  • Viktor's 10 P1 findings absorb into operator-algebra spec
  • ADR v2 follow-up SKILL.md edits via skill-creator (claims-tester + complexity-reviewer) — targets v2 as intended (no v1-vs-v2 sequencing dependency anymore since v2 landed in-round)
  • Grandfather O(·) claims discharge — one claim per round through the v2 pipeline (35-round tail; P2 BACKLOG entry; Aarav graceful-degradation clause)
  • lsm-spine-family capability draft (ADR round-42 slot)
  • formal-analysis-gap-finder round-42 invocation (scheduled after Prereq 1 lands so audit sees corrected state)
  • Aarav's top-5 tune-up actions via skill-creator (now unblocked — both the two v1-gated items now target v2)

AceHack and others added 30 commits April 20, 2026 04:39
Answers Aaron 2026-04-20 delete-all-code-recovery question:
4 capabilities / 783 lines of spec.md vs 66 top-level F#
modules / 10,839 lines under src/Core/ — ~6% coverage today.

docs/research/openspec-coverage-audit-2026-04-21.md
- Inventory of 66 modules with line counts + capability
  mapping for the 4 existing capabilities
- Uncovered modules sorted by delete-recovery blast radius:
  Band 1 MUST BACKFILL (8 modules / 1,629 lines — ZSet,
  Circuit, NestedCircuit, Spine family, BloomFilter as
  Adopt-row compatibility-coupling exception), Band 2 HIGH
  (12 / 2,008), Band 3 MEDIUM (45 / 6,585), Band 4
  deliberately uncovered (AssemblyInfo only)
- First 6-round cadence: operator-algebra extension (41),
  lsm-spine-family (42), circuit-recursion (43),
  sketches-probabilistic (44), content-integrity (45),
  crdt-family (46)
- Success signal = Viktor spec-zealot adversarial audit:
  "could I rebuild this module from this spec alone?"

docs/DECISIONS/2026-04-21-openspec-backfill-program.md
- Adopts one-capability-per-round baseline with paper-grade
  half-credit rule (no more than 1 paper-grade round per 3)
- Band 1 priority until complete; Adopt-row escalation for
  BloomFilter (TECH-RADAR Adopt without spec contract is a
  backwards-compatibility hazard)
- Round-close ledger gains an `OpenSpec cadence` line
- Alternatives considered: big-bang backfill (rejected —
  ontology-landing cadence + reviewer bandwidth), per-module
  capabilities (rejected — loses cross-module invariants),
  organic prioritisation (rejected — 40 rounds of drift
  evidence)

docs/BACKLOG.md
- Collapses the 29-line P0 scope into a 15-line pointer at
  the inventory + ADR now that parts (a)-(e) of the program
  setup have landed. Remaining work = per-round capability
  backfill per ADR schedule.

Build: dotnet build -c Release clean; BP-10 ASCII-clean on
all 3 modified files; markdownlint-cli2 clean.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
First ship under the OpenSpec backfill program adopted
2026-04-21. Extends openspec/specs/operator-algebra/spec.md
(184 -> 324 lines) with five new requirements covering
structural and lifecycle gaps that the existing mathematical-
law coverage left implicit:

1. Operator lifecycle — construction / step / after-step /
   reset phases with side-effect-freedom on construction and
   epoch-replay semantics on reset
2. Strict operators break feedback cycles — formalises that
   z^-1-on-feedback is a scheduling prerequisite and that
   cycle-without-strict is a construction error, not a
   silent heuristic
3. Clock scopes and tick monotonicity — nested-scope-to-
   fixpoint rule + sibling-scope independence
4. Incremental-wrapper preserves the chain rule —
   Incrementalize(Q) observably equivalent to D . Q . I,
   with linear/bilinear substitution permitted as an
   optimisation
5. Representation invariants of the reference Z-set —
   O(n+m) group ops + zero-alloc iteration as the reference
   contract; hash-table recoveries permitted at documented
   perf trade-off

Disaster-recovery effect: a contributor with only this spec
(plus the durability-modes + retraction-safe-recursion specs)
can now rebuild Circuit.fs Op base + Incremental.fs wrapper +
ZSet.fs representation invariants from the spec text alone.

Owner: Architect (Kenji). Adversarial audit by Viktor
(spec-zealot) is the ADR-declared ship-gate and will run
post-land.

Build: not rebuilt (no F# source changed); markdownlint
clean; BP-10 ASCII clean.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Viktor's adversarial audit of the Round 41 cadence ship (commit
e51ec1b) surfaced four P0 findings against the disaster-recovery
bar. This commit closes all four:

- **P0-1 (namespace drift).** `profiles/fsharp.md` asserted
  `Dbsp.Core` throughout, but `src/Core/**` uses `Zeta.Core`. A
  spec-only recovery would have shipped the wrong namespace to
  every downstream consumer. Replaced via one `replace_all` Edit.

- **P0-2 (phantom Reset method).** The lifecycle requirement
  claimed a `reset` phase that does not exist on `Op`. Replaced
  the "reset replays the epoch" scenario with a
  determinism-under-structural-equivalence property: two
  freshly-constructed circuits of the same topology, stepped
  with the same input sequence, MUST produce identical outputs
  at every tick. Reconstruction is the supported route to a
  replayed epoch.

- **P0-3 (after-step scope).** The lifecycle requirement said
  after-step runs "after every operator in the scope has
  completed its step." `Circuit.fs:205-208` iterates the
  `strictN` array only — after-step is selective to strict
  operators. Fixed wording and added a "after-step is selective
  to strict operators" scenario that pins the invariant.

- **P0-4 (lifecycle phase undercount).** The requirement named
  four phases (construction / step / after-step / reset) but
  the code has five (construction / step / after-step /
  clock-start / clock-end). Restructured to three per-tick
  phases plus two scope-boundary phases, and extended the
  "clock scopes and tick monotonicity" requirement with the
  scope-boundary lifecycle contract (clock-start before tick 0
  of a scope, clock-end after fixpoint or iteration cap).

Build green (0 warnings / 0 errors). BP-10 lint clean. The
capability now reflects the code's observable shape rather than
an idealised cleaner cousin; a delete-recovery from this spec
produces Zeta.Core with strict-operator after-step selectivity
and nested-scope clock-boundary phases.

Viktor's 10 P1 findings (async lifecycle, memory-ordering fence,
register-lock semantics, IncrementalDistinct surface, ZSet sort
invariant, Checked arithmetic, bilinear-size overflow,
convergence-vs-cap) are deferred to Round 42 — filed as a
BACKLOG sweep in follow-up work.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Companion to 92d7db2 (closing Viktor's four P0 findings). The
ten P1-tier surface gaps Viktor identified do not block the
disaster-recovery bar at capability-close but leave the
operator-algebra spec incomplete relative to what a delete-
recovery produces. Filed as a dedicated P0 sub-item so they
travel with the OpenSpec backfill program rather than getting
lost: async lifecycle, memory-ordering fence, register-lock
semantics, IncrementalDistinct surface, ZSet sort invariant,
Checked arithmetic, bilinear-size overflow, convergence-vs-cap,
Op.Fixedpoint predicate, DelayOp reconstruction-first-tick.

Also annotated the parent OpenSpec coverage entry with Round 41
sweep status (e51ec1b + 92d7db2, P0s closed, P1s deferred) so
the backlog accurately reflects where the program stands.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
…dence ship

Four-arc entry at the top of the file per newest-first policy:

- Arc 1 (d435126): OpenSpec coverage audit + backfill-program
  ADR. Measured 6% coverage; declared one-capability-per-round
  baseline with paper-grade half-credit and Adopt-row priority
  escalation; banded 66 F# modules by delete-recovery blast
  radius.
- Arc 2 (e51ec1b): operator-algebra extension as Round-41
  cadence ship. Five new requirements covering lifecycle,
  strict-operator scheduling, clock scopes, Incrementalize
  wrapper, ZSet representation invariants.
- Arc 3 (92d7db2): Viktor P0 close. Four drift-from-code
  defects fixed — namespace (Dbsp.Core → Zeta.Core), phantom
  Reset, after-step scope (strict-only), lifecycle phase
  undercount (3 per-tick + 2 scope-boundary).
- Arc 4 (56f34b5): Viktor P1s filed as Round-42 absorb under
  the parent backfill P0, creating mechanical coupling between
  each capability ship and the following round's P1 sweep.

Round-41 observations for Round 42 + prospective BP-WINDOW
ledger table rendering the four commits against the consent /
retractability / no-permanent-harm axes.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Aaron 2026-04-19 asked for memory/role/persona/ so roles become
first-class in the directory structure. Surface is wider than
it first looks — 114 files / ~260 hand-written references to
memory/persona/ paths (plus ~440 auto-regenerated references
in tools/alignment/out/ that refresh on next citations.sh run).
A bad role axis is hard to reverse; this design doc proposes
the axis and holds execution for Aaron's sign-off rather than
just-doing-it under Auto Mode.

Design plan lands at:
  docs/research/memory-role-restructure-plan-2026-04-21.md

Contents: 13-directory role axis (architect, security,
verification, review, experience, api, performance, devops,
algebra, skill-ops, maintainer, homage, alignment);
persona-to-role crosswalk for every current directory;
5-phase execution plan (pre-flight greps → git mv → sed
passes → 5-check verification → pointer-source updates);
special-case handling for aaron (human maintainer),
rodney (homage-named AI persona on the reducer skill),
sova (emerging alignment-observability role); rollback
plan (one atomic commit, git revert); four open questions
for Aaron on axis judgement-calls.

BACKLOG entry updated to reflect design-landed state with
execution-slot recommendation for Round 42 opener after the
Round 41 PR merges (keeps wide-surface reviews from
overlapping).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Rounds 37-40 shipped via PR #30 (merge commit 1e30f8c, 2026-04-20).
Ledger headers updated from "(prospective)" to "(merged via PR #30,
1e30f8c)" — the BP-WINDOW scores are now settled, not forecasts.

Round 41 ledger remains "(prospective)" — round-41 branch has not
merged to main yet.

Prose uses of "prospective" on lines 437, 447, 553, etc. are
historical-narrative commentary on authoring-time methodology and
stay as-is.
Round 39 observation flagged src/Core/RecursiveSigned.fs +
tools/tla/specs/RecursiveSignedSemiNaive.tla as held pending
formal-verification-expert tool-coverage review. Round 41 closes
that gate.

Soraya's notebook entry lands:

- Per-property tool table S1-S4 + refinement cross-check. TLC
  primary for S1/S2/S3/S3'/SupportMonotone; FsCheck for S4.
- S2 flagged as the one P0 on the spec (silent fixpoint drift
  unrecoverable); BP-16 requires Z3 QF_LIA cross-check.
- Refinement mapping: FsCheck cross-trace (signed vs counting at
  SeedWeight=1) wins over TLA+ refinement proof or Lean lemma —
  anti-TLA+-hammer, implementation-level where the bug bites.
- Readiness gate: TLA+ spec is ready to model-check; no pre-TLC
  pass needed. Optional round-42 follow-up: add
  PROPERTY EventuallyDone to .cfg for liveness.
- Graduation verdict: CONDITIONAL PASS. Four tool-coverage
  prereqs named in priority order; F# landing gated on them.

Files read (no edits): RecursiveSigned.fs, RecursiveSignedSemiNaive.tla
/cfg, RecursiveCountingLFP.tla, retraction-safe-semi-naive.md.
Soraya's round-41 audit of src/Core/RecursiveSigned.fs +
tools/tla/specs/RecursiveSignedSemiNaive.tla landed as a CONDITIONAL
PASS for Round-42 graduation. This commit lifts the four named
prereqs out of her notebook into BACKLOG sub-items under the
parent "Retraction-safe semi-naive LFP" entry, so the round-42
opener picks them up as checkbox work rather than having to re-read
the notebook.

Prereqs in priority order:
- Prereq 1 — TLC CI wire-up (RecursiveSignedSemiNaive.cfg)
- Prereq 2 — Z3 QF_LIA lemma for S2 FixpointAtTerm (BP-16 cross-check
  on the one P0; TLC alone insufficient for silent-fixpoint-drift risk)
- Prereq 3 — FsCheck property for S4 sign-distribution (anti-
  TLA+-hammer; two-trace quantification is NOT a TLA+ property)
- Prereq 4 — FsCheck cross-trace refinement (signed vs counting
  at SeedWeight = 1); cites BP-16

Round-42 graduation gate also captured: prereqs 1-4 CI-green + F#
implementation with P1/P2/P3 enforced at caller.
The initial Round 41 ROUND-HISTORY entry (6e6e211) covered arcs
1-4 (coverage audit, operator-algebra cadence ship, Viktor P0
close, Viktor P1 file). Three more commits landed after:

Arc 5 — ROUND-HISTORY narrative + memory-restructure design
(6e6e211, 36797ba). The memory-folder rename was downgraded to
"design plan + sign-off first" under Auto Mode's
do-not-take-overly-destructive-actions clause (700-occurrence
cross-reference surface).

Arc 6 — BP-WINDOW ledger actualisation for Rounds 37-40
(85fb352). Provenance (PR #30 / 1e30f8c) attached to each
"(prospective)" header.

Arc 7 — Round-35 holdover close (e461d9c, 15e9654). Soraya
tool-coverage audit landed CONDITIONAL PASS for Round-42
graduation; four prereqs captured as BACKLOG sub-items with
BP-16 citation on the S2 Z3 cross-check.

Also: one new observation line in the Round-42 handoff section
noting the holdover-closed-same-round-as-cadence-item pattern.
BP-WINDOW ledger gains three rows.
CLAUDE.md 5-10 round cadence rule was 23 rounds overdue. Round 41
is the catch-up slot. Live-search + full ranking + prune pass all
landed in a single invocation.

Live-search (4 queries, 2026-Q1/Q2 best-practices targets):
- 6 findings logged to best-practices-scratch.md: Gotchas-section
  rise, pushy-descriptions pattern, Claude-A-authors / Claude-B-
  tests, router-layer command-integrity injection class, Agent
  Stability Index 12-dim drift metric, OWASP Intent Capsule
  pattern.
- Zero contradictions with stable BP-NN rules.
- Zero promotions flagged to Architect this round; all six are
  "watch" or route-elsewhere.

Top-5 skills flagged for tune-up:
1. performance-analysis-expert (642 lines, 2.1x BP-03 cap) — SPLIT — M
2. reducer (570 lines) — SPLIT or TUNE (prune) — M
3. consent-primitives-expert (507 lines) — SPLIT honouring BP-23
   theory/applied axis — M
4. claims-tester / complexity-reviewer router-coherence drift —
   HAND-OFF-CONTRACT — S (round-18 carry-over)
5. skill-tune-up (self) — 303 lines, 3 over BP-03 — TUNE (prune
   authoritative-sources duplicated with AGENT-BEST-PRACTICES.md)
   — S. Self-flagged first per BP-06.

Notebook state:
- Stale round-18 top-5 archived in Pruning log (first catch-up prune).
- 912 words, well under 3000-word BP-07 cap.
- ASCII-only, BP-10 clean.

Nine more bloat-row skills named as notable mentions queue behind
the top-3 bloat cases.
Close Aarav's round-18 HAND-OFF-CONTRACT finding (carried 23 rounds
after ranker went offline by cadence). Two-stage pipeline: analytic
bound first (complexity-reviewer), empirical measurement second
(claims-tester). Names the reverse trigger (benchmark surprise flows
the other direction) and the decision table for who fires when.
Follow-up SKILL.md edits route via skill-creator per GOVERNANCE §4.
Arc 8 covers the claims-tester/complexity-reviewer hand-off ADR
(47d92d8) closing Aarav's 23-round-stale round-18 HAND-OFF-CONTRACT
finding. New observation on cadence-outage-recovery as a design axis:
sweep infrastructure is subject to the same bitrot it detects on other
surfaces. BP-WINDOW ledger gains two rows (085c0e3 Aarav catch-up,
47d92d8 router-coherence ADR).
Close-out audit surfaced that .github/workflows/gate.yml only CACHES
the tla2tools.jar artefact; nothing runs it. RecursiveCountingLFP.tla
has shipped since round 19 compile-checkable-only — 22 rounds with no
run-gate against its invariants. Soraya's Prereq 1 re-sized S→M with
expanded scope covering both specs. Finding recorded as new round-41
observation: verifier-present does not imply verifier-actually-runs.
Keeps the Round 41 BP-WINDOW ledger commit-aligned rather than
arc-aligned. 459b218 is the Arc-8 narrative itself; d76a09b is the
Prereq-1 S→M correction. Both retractable as single reverts.
…s lens

Codifies the round-41 Prereq-1 audit finding as a tracked
research entry, distinct from its ROUND-HISTORY narrative
presence. The finding — a verifier's installation artefacts
do not imply the verifier is exercised by any CI job — is
exactly the class formal-analysis-gap-finder exists to
surface. Concrete motivating case: RecursiveCountingLFP.tla
compile-checkable-only for 22 rounds. Round-42 scope covers
the bidirectional audit (specs without gates + gates without
specs). Handoff to Soraya per the skill's standing contract;
does not write the spec or CI job (DevOps + Soraya work).
Schedules after Prereq 1 lands so the audit sees corrected
state.
Per the established stopping rule (meta-ledger commits do not
get self-referential rows; their round-close coverage is the
PR merge), this commit adds only the 2042a85 row and does not
add a row for itself.
Closes ADR 47d92d8's third follow-up action item. Single-row
addition to Active tensions citing the router-coherence ADR as
the standing resolution. Doc-only edit (not a SKILL.md touch,
so GOVERNANCE §4 does not gate this). The other two ADR
follow-ups (claims-tester + complexity-reviewer SKILL.md
updates) remain deferred to round 42 via skill-creator
workflow.
Per-commit ledger discipline for the CONFLICT-RESOLUTION
Hiroshi ↔ Daisy row. Meta-ledger-only commit so no
self-referential row for this commit itself (established
stopping rule).
…sedure backlog

Router-coherence ADR 47d92d8 (Hiroshi analytic ↔ Daisy empirical
two-stage pipeline) landed without the adversarial-review gate.
Post-landing harsh-critic (Kira) pass surfaced 3 P0 + 5 P1 + 2 P2
substantive findings, including (P0-1) unscoped grandfather
clause, (P0-2) table-vs-prose contradiction on reverse trigger,
(P0-3) Stage-1 "analytically wrong" clause blocking the evidence
loop for escalation, (P1-7) no escalation timebox reproducing the
23-round-stale failure mode the ADR diagnosed, (P1-8) two advisory
skills not composing to a mandatory pipeline without a binding
dispatcher, (P2-9) example-bug on BCL Dictionary.Remove amortised
complexity, and more.

File as round-42 supersedure rather than inline-edit because
docs/CONFLICT-RESOLUTION.md already cites 47d92d8 as Standing
Resolution — supersedure preserves the citation chain via
GOVERNANCE §2 edit-in-place with a "Superseded by …" header on
v1. New ADR target: docs/DECISIONS/2026-04-??-router-coherence-
v2.md. Supersedure work blocks the claims-tester +
complexity-reviewer SKILL.md updates ADR 47d92d8 follow-up work
depends on — those edits should target v2, not v1.

Owner: Architect drafts; Kira audits closure; Aarav confirms
router-coherence drift stays closed. Effort: M. Schedule: Round
42 slot after Soraya Prereq 1 (TLC wire-up) lands.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Ledger row for harsh-critic findings filing commit. Primary work
(BACKLOG addition tracking a round-42 supersedure with 10 named
findings), not meta-ledger — earns a row under the BP-WINDOW
per-commit discipline. Consent = adversarial findings tracked
honestly; Retractability = supersedure preserves citation chain
vs inline-edit; No-permanent-harm = single BACKLOG edit, no ADR
body touched, no SKILL.md touched.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
ROUND-HISTORY Arc 1-8 narrated primary commits up through the
router-coherence ADR (47d92d8). Four primary commits landed
after Arc 8 — Prereq 1 sizing correction (d76a09b), recurring-
audit lens BACKLOG entry (2042a85), CONFLICT-RESOLUTION Hiroshi
↔ Daisy row (fcfa3d9), and harsh-critic findings filed as
round-42 supersedure (779d7ef) — visible only in the BP-WINDOW
ledger table, not in narrative form.

Arc 9 ties them into one coherent sequence: the round's
self-correction ran unusually deep. Arc 8 corrects Aarav's
round-18 finding via ADR; Arc 9 catches the corrector itself
under-reviewed via Kira's adversarial pass. Both self-
corrections land before round-close. Narrative-ledger
alignment is the BP-WINDOW discipline's first assertion —
restoring it.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Ledger row for Arc 9 narrative commit. Narrative extensions
count as primary work under BP-WINDOW precedent (per 459b218
and 6e6e211 examples) and earn a ledger row. Consent = drift
closed honestly; Retractability = single revertable doc edit;
No-permanent-harm = isolated insertion.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
…gs in-round

Drafts v2 of the router-coherence ADR (docs/DECISIONS/2026-04-21-router-coherence-v2.md) that supersedes v1 (47d92d8) in the same round, closing all 10 Kira harsh-critic findings (3 P0 + 5 P1 + 2 P2) via named textual closures C-P0-1 through C-P2-10.

Key closures:
- C-P0-1: grandfather clause bounded with Kenji-owned inventory + one-per-round discharge
- C-P0-2: reverse trigger unconditional (table now matches prose)
- C-P0-3: escalation-evidence exception permits Stage 2 under conference protocol with explicit labelling
- C-P1-5: Stage-1 trigger widened to match claims-tester SKILL.md contract
- C-P1-7: escalation timebox (round +2 auto-promote to BACKLOG P1) prevents 23-round-stale reproduction
- C-P1-8: Kenji named as binding dispatcher — advisory + advisory + binding-dispatcher composes to mandatory pipeline
- C-P2-9: Dictionary.Remove example replaced with ArrayPool<T>.Rent (legitimate BCL-contract edge)

v1 kept in place per GOVERNANCE §2 with Superseded-by header appended in a follow-up commit so the CONFLICT-RESOLUTION Active-tensions citation chain remains resolvable.

BP-10 lint: clean.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Appends Superseded-by header to router-coherence v1 ADR (47d92d8) pointing at v2 (09f0889), per GOVERNANCE §2 (docs read as current state; superseded ADRs keep v1 in place with redirect header so citation chains remain resolvable).

Also corrects v1 Status from "Proposed — awaits sign-off" to "Accepted (pre-adversarial-review; superseded by v2 same-round after Kira pass)" per Closure C-P1-4 in v2 — Status was already cited as Standing Resolution in docs/CONFLICT-RESOLUTION.md Active-tensions, so Proposed was factually wrong.

The v1 body text is not edited — supersedure preserves the historical record; v2 carries the closures.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Adds Arc 10 narrative covering 09f0889 (v2 ADR) and 4efe545 (v1 Superseded-by header) as one coherent in-round supersedure story, after Arc 9's "self-correction sweep" and before Round 41 observations. Pattern: Arc 9 surfaces the under-review; Arc 10 lands the close in the same round rather than deferring a known-imperfect artefact.

Adds two BP-WINDOW ledger rows (09f0889, 4efe545) to the round-41 ledger block per the per-commit accounting discipline.

Supersedure arc count now covers the full round-41 close: 10 arcs / 25 primary-work commits.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Flips BACKLOG router-coherence supersedure entry from [ ] to [x] ✅ with "shipped round 41 in-round" annotation pointing at v2 ADR (09f0889) + v1 Superseded-by header (4efe545). All 10 Kira findings closed via named textual closures C-P0-1 through C-P2-10.

Original finding narrative preserved below the closure line per the shipped-item convention used elsewhere in the file (audit trail).

Follow-up SKILL.md edits to claims-tester + complexity-reviewer via skill-creator remain round-42 scope, now targeting v2 as intended.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Adds BP-WINDOW ledger row for 4537365 (BACKLOG supersedure entry discharged in-round) to match the Arc 9 precedent where 779d7ef (BACKLOG entry addition) received a row. Symmetry: add and close get equal ledger treatment.

Meta-ledger stopping rule still holds — this commit itself (which only adds a ledger row) does not get a self-referential row.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
…n-round

Produces the one-time grandfather-claims inventory named in router-coherence v2 ADR §Closure C-P0-1 within the round v2 lands, per ADR's own within-round commitment.

Inventory: 35 live claims at ADR-landing time (29 F# /// docstrings in src/Core/ + src/Bayesian/, 3 grey-zone F# code comments, 1 openspec/specs/operator-algebra/spec.md line, 2 docs/research/** claims). Zero hits in root README, memory/persona/*/NOTEBOOK.md, docs/papers/** (directory does not exist yet).

Distinguishes live claims (shipping as asserted bounds) from historical evidence (BACKLOG [x] ✅ residue, TECH-RADAR flag-text narrating past regressions, in-file "was O(…)" commentary on fixed paths). Only live claims populate the grandfather set — evidence is captured for audit trail but excluded per v2's intent ("claims Zeta is currently making").

BACKLOG discharge entry added: P2, one-claim-per-round cadence, ~35-round tail, Aarav graceful-degradation clause fires on ≥3 rounds without discharge.

Complexity-class distribution of live set: 10 O(1), 13 O(log n)/O(log k)/O(log N), 7 O(n)/O(n log n)/O(n log k), 5 parametric.

BP-10 lint: clean.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Adds Arc 11 narrative covering d98ef2b (grandfather inventory + BACKLOG discharge entry) as the close of the v2 ADR's within-round commitments. Pattern: Arc 10 lands the ADR; Arc 11 lands the ADR's own within-round commitment — without Arc 11, Arc 10 would have shipped a contract Zeta didn't meet.

Adds BP-WINDOW ledger row for d98ef2b per per-commit accounting discipline.

Round 41 now closes at 11 arcs / 30 primary-work commits.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
AceHack added 2 commits April 20, 2026 08:39
Two external-anchor PDFs (CC BY-NC-SA 4.0) placed at their
memory-documented paths:

- docs/2025_state_of_ai_assisted_software_development.pdf
  (~15MB, 138 pages) — findings + data report.
- docs/2025_dora_ai_capabilities_model.pdf (~9MB, 94 pages)
  — framework companion.

Citation anchors this commit makes in-tree rather than
memory-only: Nyquist stability criterion for AI-accelerated
development (foreword p9 fn 1) as theoretical anchor for
CI-meta-loop + retractable-CD P1 BACKLOG work; "AI is an
amplifier" anchor that echoes the corporate-religion /
sandbox-escape threat class; seven-capability AI model that
gives the external measurement vocabulary for round-audit
output (capability #7 "quality internal platforms" is the
in-flight P1 cluster per 2026-04-20 memory).

License note: derived work is NC-SA-bound; Zeta citations
are fine, external redistribution inherits NC-SA. Paired
companion memory file is reference_dora_2025_reports.md
(out-of-tree); this commit brings the primary sources
in-tree so citation from research docs + ADRs can point
at a repo-local path rather than a newsletter-gated URL.
Narrative section for Arc 12 inserted before "Round 41
observations for Round 42" with primary commit pointer to
46075d6. Arc 12 frames the DORA 2025 PDFs as
memory-promotion substrate per the 2026-04-20 feedback entry
("DORA is our starting point for measurements") and cites
the concrete in-tree anchors (Nyquist p9 fn 1, seven-
capability model, AI-amplifier thesis).

Also surfaces honestly — in-body, not buried in a private
retrospective — the ranker-scope gap that let the two
untracked PDFs sit 18+ hours through nine consecutive
/next-steps invocations before this arc closed the gap. The
skill explicitly lists docs/research/ and docs/TECH-RADAR.md
but not `git status --short` for untracked files. Candidate
skill-tune-up note for Aarav's notebook: /next-steps must
run `git status --short` on every invocation so dropped-in
artefacts appear in ranking before the ninth re-fire, not
after.

BP-WINDOW ledger gets a matching 46075d6 row with
reference-document-specific cells: Consent strengthened by
promoting memory-only anchors to in-repo substrate and by
surfacing the ranker-stall pattern in-narrative; retraction
is a single `git rm` if the license / size stance later
changes; no-permanent-harm preserved since no runtime
behaviour depends on the PDFs' presence (they are citation
substrate, not loaded artefacts).

Arc count now 12; primary-work-commit count now 12 (Round 41
alignment preserved). Build gate green (0 Warning / 0 Error);
BP-10 lint clean on the narrative + ledger row.
Copilot AI review requested due to automatic review settings April 20, 2026 12:54
Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Establishes the Round 41 OpenSpec backfill program and captures new/updated governance + research artefacts to support delete-recovery specs and router-coherence (analytic ↔ empirical) workflow, plus lands DORA 2025 reference PDFs in-tree.

Changes:

  • Extends the operator-algebra OpenSpec with lifecycle, scheduling, clock-scope, chain-rule wrapper, and Z-set representation requirements.
  • Adds/updates ADRs, BACKLOG, CONFLICT-RESOLUTION, ROUND-HISTORY, and research notes to formalize the OpenSpec cadence and router-coherence v2 supersedure.
  • Updates persona notebooks/scratchpads and adds DORA 2025 PDFs as reference substrate.

Reviewed changes

Copilot reviewed 14 out of 16 changed files in this pull request and generated 8 comments.

Show a summary per file
File Description
openspec/specs/operator-algebra/spec.md Adds new operator-algebra requirements and scenarios (lifecycle, strictness, clock scopes, incremental wrapper, Z-set invariants).
openspec/specs/operator-algebra/profiles/fsharp.md Aligns the F# profile namespace/assembly to Zeta.Core / Zeta.Core.
memory/persona/soraya/NOTEBOOK.md Records Round 41 tool-coverage audit for RecursiveSigned and prereq routing.
memory/persona/best-practices-scratch.md Refreshes scratchpad formatting and appends Round 41 live-search findings.
memory/persona/aarav/NOTEBOOK.md Adds Round 41 catch-up ranking and updated top-5 tune-up targets.
docs/research/openspec-coverage-audit-2026-04-21.md Introduces an OpenSpec coverage audit and proposed cadence plan.
docs/research/memory-role-restructure-plan-2026-04-21.md Design plan for restructuring memory/ by role, including execution steps.
docs/research/grandfather-claims-inventory-2026-04-21.md Inventories pre-ADR O(·) claims to seed the v2 router-coherence discharge cadence.
docs/ROUND-HISTORY.md Adds the Round 41 narrative and updates ledger headers for rounds 37–40 provenance.
docs/DECISIONS/2026-04-21-router-coherence-v2.md Adds v2 ADR superseding v1 and closes harsh-critic findings via explicit closure clauses.
docs/DECISIONS/2026-04-21-router-coherence-claims-vs-complexity.md Adds v1 ADR (now marked superseded) documenting the initial hand-off pipeline.
docs/DECISIONS/2026-04-21-openspec-backfill-program.md Adds ADR establishing one-capability-per-round OpenSpec backfill cadence and audit gate.
docs/CONFLICT-RESOLUTION.md Adds an Active-tensions row for Complexity Reviewer ↔ Claims Tester with a standing resolution pointer.
docs/BACKLOG.md Rewrites OpenSpec backfill entry with Round 41 status, adds/router-coherence + grandfather discharge tracking, and expands memory-role restructure entry.
docs/2025_state_of_ai_assisted_software_development.pdf Adds DORA 2025 reference PDF to the repo.
docs/2025_dora_ai_capabilities_model.pdf Adds DORA capabilities model PDF to the repo.

Comment thread docs/CONFLICT-RESOLUTION.md Outdated
Comment on lines +204 to +205
`docs/DECISIONS/2026-04-21-router-coherence-claims-vs-complexity.md`
— analytic-first on new claims; reverse trigger (Claims Tester
Copy link

Copilot AI Apr 20, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The Standing Resolution link points to the v1 ADR (router-coherence-claims-vs-complexity.md), which is now explicitly superseded by v2. Since this row is meant to be the current operating contract, it should link directly to docs/DECISIONS/2026-04-21-router-coherence-v2.md (and optionally mention that v1 is retained as historical record).

Suggested change
`docs/DECISIONS/2026-04-21-router-coherence-claims-vs-complexity.md`
analytic-first on new claims; reverse trigger (Claims Tester
`docs/DECISIONS/2026-04-21-router-coherence-v2.md`
analytic-first on new claims; reverse trigger (Claims Tester

Copilot uses AI. Check for mistakes.
Comment thread docs/ROUND-HISTORY.md Outdated
`Q^Δ = D ∘ Q ∘ I`; (5) representation invariants of the
reference `ZSet[K]` (O(n+m) group operations, zero-alloc
iteration, no zero-weight entries exposed). Spec now at
324 lines. F# profile at `openspec/specs/operator-algebra/
Copy link

Copilot AI Apr 20, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The Round 41 narrative says operator-algebra/spec.md is now 324 lines, but the file is currently 365 lines. Please update this line-count so the round history stays internally consistent with the repo state.

Suggested change
324 lines. F# profile at `openspec/specs/operator-algebra/
365 lines. F# profile at `openspec/specs/operator-algebra/

Copilot uses AI. Check for mistakes.
Comment on lines +42 to +45
See `docs/research/openspec-coverage-audit-2026-04-21-inventory.md`
(follow-up) for the full 66-row table. Summary by band below;
the table and Band definitions are this document's load-bearing
artefact.
Copy link

Copilot AI Apr 20, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This doc links to docs/research/openspec-coverage-audit-2026-04-21-inventory.md, but that file does not appear to exist in the repo/PR. Either add the referenced inventory file or adjust the text/link to point at the actual location of the full 66-row table.

Suggested change
See `docs/research/openspec-coverage-audit-2026-04-21-inventory.md`
(follow-up) for the full 66-row table. Summary by band below;
the table and Band definitions are this document's load-bearing
artefact.
Summary by band below; the Band definitions in this document
are the load-bearing artefact.

Copilot uses AI. Check for mistakes.
Comment on lines 274 to 276
## 2026-04-19 -- candidate BP: uv-only Python package and tool
## management

Copy link

Copilot AI Apr 20, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The heading for the uv-only Python candidate is accidentally split into two separate H2 headings ("## … package and tool" then "## management"), which will break the section structure/ToC. Combine this into a single heading line (or make the second line plain wrapped text).

Copilot uses AI. Check for mistakes.
Comment on lines +135 to +140
grep -rln "memory/persona/" --include="*.md" --include="*.json" \
--include="*.sh" --include="*.fs" --include="*.cs" . | \
grep -v "^./\\.git" | wc -l # → 114 files
grep -rc "memory/persona/" --include="*.md" --include="*.json" \
--include="*.sh" . | grep -v ":0$" | \
awk -F: '{s+=$2} END {print s}' # → 700 refs
Copy link

Copilot AI Apr 20, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The Phase 1 grep commands walk the whole repo (".") but don't exclude references/upstreams/**, which the repo explicitly warns against for recursive scans because it contains many full upstream clones. Add an exclude (e.g., --exclude-dir=references / --glob '!references/upstreams/**') to these and the other grep loops in this plan so the counts/runtime are meaningful.

Suggested change
grep -rln "memory/persona/" --include="*.md" --include="*.json" \
--include="*.sh" --include="*.fs" --include="*.cs" . | \
grep -v "^./\\.git" | wc -l # → 114 files
grep -rc "memory/persona/" --include="*.md" --include="*.json" \
--include="*.sh" . | grep -v ":0$" | \
awk -F: '{s+=$2} END {print s}' # → 700 refs
grep -rln "memory/persona/" --exclude-dir=.git --exclude-dir=references \
--include="*.md" --include="*.json" --include="*.sh" \
--include="*.fs" --include="*.cs" . | wc -l # → 114 files
grep -rc "memory/persona/" --exclude-dir=references \
--include="*.md" --include="*.json" --include="*.sh" . | \
grep -v ":0$" | awk -F: '{s+=$2} END {print s}' # → 700 refs

Copilot uses AI. Check for mistakes.
memory/persona/tariq/ memory/algebra/tariq/
memory/persona/viktor/ memory/verification/viktor/

memory/persona/README.md memory/persona-README.md (or moved to memory/README-persona-roles.md)
Copy link

Copilot AI Apr 20, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The crosswalk lists memory/persona/README.md moving to memory/persona-README.md (or memory/README-persona-roles.md), but Phase 2 later uses memory/persona-roles-README.md. Please pick one canonical target name and make the crosswalk + git mv commands consistent to avoid broken references during execution.

Suggested change
memory/persona/README.md memory/persona-README.md (or moved to memory/README-persona-roles.md)
memory/persona/README.md memory/persona-roles-README.md

Copilot uses AI. Check for mistakes.
Comment on lines +208 to +217
xargs -r sed -i "" "s|memory/persona/$persona/|memory/$role/$persona/|g"
done

# Clean up the flat-file references too
grep -rl "memory/persona/README\\.md" --include="*.md" . | \
xargs -r sed -i "" "s|memory/persona/README\\.md|memory/persona-roles-README.md|g"
grep -rl "memory/persona/best-practices-scratch\\.md" \
--include="*.md" --include="*.sh" . | \
xargs -r sed -i "" \
"s|memory/persona/best-practices-scratch\\.md|memory/best-practices-scratch.md|g"
Copy link

Copilot AI Apr 20, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The Phase 3 rewrite loop mixes BSD- and GNU-specific flags (sed -i "" is BSD/macOS, but xargs -r is GNU-only and fails on macOS). Either adjust the commands to be portable (or provide both macOS/Linux variants) so the plan can be executed reliably.

Suggested change
xargs -r sed -i "" "s|memory/persona/$persona/|memory/$role/$persona/|g"
done
# Clean up the flat-file references too
grep -rl "memory/persona/README\\.md" --include="*.md" . | \
xargs -r sed -i "" "s|memory/persona/README\\.md|memory/persona-roles-README.md|g"
grep -rl "memory/persona/best-practices-scratch\\.md" \
--include="*.md" --include="*.sh" . | \
xargs -r sed -i "" \
"s|memory/persona/best-practices-scratch\\.md|memory/best-practices-scratch.md|g"
while IFS= read -r file; do
sed -i.bak "s|memory/persona/$persona/|memory/$role/$persona/|g" "$file" && rm -f "$file.bak"
done
done
# Clean up the flat-file references too
grep -rl "memory/persona/README\\.md" --include="*.md" . | \
while IFS= read -r file; do
sed -i.bak "s|memory/persona/README\\.md|memory/persona-roles-README.md|g" "$file" && rm -f "$file.bak"
done
grep -rl "memory/persona/best-practices-scratch\\.md" \
--include="*.md" --include="*.sh" . | \
while IFS= read -r file; do
sed -i.bak \
"s|memory/persona/best-practices-scratch\\.md|memory/best-practices-scratch.md|g" \
"$file" && rm -f "$file.bak"
done

Copilot uses AI. Check for mistakes.
**Round:** 41 opener
**Author:** Architect (Kenji) — dispatched inventory; spec-zealot
(Viktor) to review adversarially post-land.
**Triggering question:** Aaron 2026-04-20 — *"opensepcs, if I
Copy link

Copilot AI Apr 20, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This research doc uses the human maintainer’s name ("Triggering question: Aaron …"). Repo convention is to keep the human maintainer’s name out of general docs and use the role reference ("human maintainer") instead. Please rewrite this (and similar occurrences in docs/research/**) to use the role wording to match .github/copilot-instructions.md ("No name attribution…").

Suggested change
**Triggering question:** Aaron 2026-04-20 — *"opensepcs, if I
**Triggering question:** human maintainer, 2026-04-20 — *"opensepcs, if I

Copilot uses AI. Check for mistakes.
Three rule violations surfaced by `lint (markdownlint)` CI job on
PR #31:

- `docs/DECISIONS/2026-04-21-router-coherence-claims-vs-complexity.md:261`
  MD022/blanks-around-headings — collapse multi-line heading
  `## Decision rationale (one paragraph for the\nwait-don't-read
  audience)` to a single line so the parser stops seeing line 262
  as adjacent non-blank content.
- `docs/research/grandfather-claims-inventory-2026-04-21.md:106`
  MD032/blanks-around-lists — add blank line between "Surface
  distribution:" lead-in and the `-` list that follows.
- `docs/research/grandfather-claims-inventory-2026-04-21.md:111`
  MD032/blanks-around-lists — same fix for "Complexity-class
  distribution (rough):" lead-in.

All three are the same class of fix shipped in task #105 on PR #30.
Additive edit to the open round-41 PR branch — no rewrite of shipped
content, semantics preserved.

Verified clean via `npx markdownlint-cli2` on both files before push.
@AceHack
Copy link
Copy Markdown
Member Author

AceHack commented Apr 21, 2026

Classification (per docs/AGENT-GITHUB-SURFACES.md § Surface 1)

Shape stack (higher-in-list wins on multi-match):

  • behind-mainmergeStateStatus: BEHIND
  • has-review-findings — Copilot left 8 actionable findings
  • awaiting-human — Aaron-scoped decision

Relationship to #32. round-42-speculative descends from round-41's tip (git merge-base confirms); merging #32 would subsume this PR. This is the Aaron-scoped part: does #31 merge as a smaller slice, or close in favour of #32?

Copilot findings triage (8 actionable):

  • 3 simple fixes: ADR v1→v2 link, line-count mismatch, jq quoting — can be addressed under this PR if it merges.
  • 4 author-edits in research docs — low risk, author judgement.
  • 1 cross-repo xref to a file that doesn't exist — needs author decision (drop xref or land target).

Mirrored to docs/hygiene-history/pr-triage-history.md (bootstrap + row for this PR) and docs/HUMAN-BACKLOG.md pending Aaron's call.

Classification taxonomy is declared non-final per the beef-up clause — first 5-10 rounds of fire-history feed a revision pass.

🤖 Per the new umbrella playbook. Context is in docs/AGENT-GITHUB-SURFACES.md + .claude/skills/github-surface-triage/SKILL.md.

AceHack added a commit that referenced this pull request Apr 21, 2026
Three rule violations surfaced by `lint (markdownlint)` CI job on
PR #31:

- `docs/DECISIONS/2026-04-21-router-coherence-claims-vs-complexity.md:261`
  MD022/blanks-around-headings — collapse multi-line heading
  `## Decision rationale (one paragraph for the\nwait-don't-read
  audience)` to a single line so the parser stops seeing line 262
  as adjacent non-blank content.
- `docs/research/grandfather-claims-inventory-2026-04-21.md:106`
  MD032/blanks-around-lists — add blank line between "Surface
  distribution:" lead-in and the `-` list that follows.
- `docs/research/grandfather-claims-inventory-2026-04-21.md:111`
  MD032/blanks-around-lists — same fix for "Complexity-class
  distribution (rough):" lead-in.

All three are the same class of fix shipped in task #105 on PR #30.
Additive edit to the open round-41 PR branch — no rewrite of shipped
content, semantics preserved.

Verified clean via `npx markdownlint-cli2` on both files before push.
AceHack added a commit that referenced this pull request Apr 21, 2026
Formalise the fix for the round-41-late 28-fire /next-steps
hold-pattern: once PR-N is CLEAN/MERGEABLE, fork
round-<N+1>-speculative from round-N HEAD immediately so
round-N+1 prep can proceed while the merge click lives on
Aaron's schedule. Rebase onto main after PR-N squash-merges,
rename to drop the -speculative suffix.

Covers: fork conditions (CLEAN/MERGEABLE + green CI + clean
round-N tree), naming (round-<N+1>-speculative), fair-game
vs not-fair-game scope, rebase protocol with
--force-with-lease, escape valve for long-waiting PRs.

Lands via skill-creator vibe-mode invocation per GOVERNANCE
§4; draft + BP-10 lint + commit without eval-pass because
the amendment is mechanical convention addition, not
behavioural. Authorized by Aaron's 2026-04-20
fix-factory-when-blocked grant
(feedback_fix_factory_when_blocked_post_hoc_notify.md).

First use of the convention itself: this commit lands on
round-42-speculative, forked from round-41 HEAD
(3525631) while PR #31 still waits on Aaron's merge
click.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
AceHack added a commit that referenced this pull request Apr 21, 2026
…rence v2

Lands the Stage-1 (complexity-reviewer, Hiroshi, analytic) and Stage-2
(claims-tester, Daisy, empirical) hand-off sections in both skills'
procedures, citing the v2 ADR at
docs/DECISIONS/2026-04-21-router-coherence-v2.md as the authoritative
pipeline contract. v1 at 2026-04-21-router-coherence-claims-vs-
complexity.md is noted as superseded.

Per v2 Closure C-P1-8, both skills name the Architect (Kenji) as the
binding dispatcher — two advisory roles do not compose to a mandatory
two-stage pipeline without a binding dispatcher; Kenji is that seat.
Both skills remain advisory on their individual findings; the ordering,
reverse-trigger rule, and escalation timebox are binding through
Kenji.

Each skill's new section mirrors the authoritative v2 pipeline text:
- Stage-1 trigger surface per C-P1-5 (XML / /// / README / commit /
  BACKLOG / TECH-RADAR / papers / openspec / research / notebooks)
- Three Stage-1 outputs (sound -> hand-off, wrong -> block-with-
  escalation-exception, under-specified -> author-bounce)
- Four Stage-2 triggers (hand-off, grandfather inventory, reverse
  trigger unconditional per C-P0-2, escalation-evidence per C-P0-3)
- Three Stage-2 outputs (matches, contradicts -> re-engage, narrow)
- Escalation timebox per C-P1-7 (round +2 auto-promote to P1)
- Grandfather set per C-P0-1 (one per round from
  docs/research/grandfather-claims-inventory-*.md)

Bibliography in both skills now cross-references each other plus the
v2 ADR, so an agent wearing either hat can reach the partner contract
in one click.

Landed on round-42-speculative per the new
speculative-round-N+1-branch convention from
.claude/skills/git-workflow-expert/SKILL.md (fea0d34). PR #31
still awaits merge; this commit is fair-game per the convention
because the target SKILL.md files are already on main and the v2
ADR text cited is stable on the round-41 branch HEAD.

Authorised by the post-hoc-notify grant captured at
memory/feedback_fix_factory_when_blocked_post_hoc_notify.md: factory-
structure additions that unblock work are authorised; deletions
still need pre-approval.

Workflow: invoked via skill-creator:skill-creator in vibe-mode (no
evals — mechanical additive edits). BP-10 invisible-Unicode lint:
clean (0 hits, 307 lines total across both files).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
AceHack added a commit that referenced this pull request Apr 21, 2026
…e 1 only)

First use of the router-coherence v2 pipeline on a live grandfather-
inventory row. Discharges claim #1 at
src/Bayesian/BayesianAggregate.fs:22, the Beta-Bernoulli conjugate-
update "O(1) per observation" docstring claim.

Stage 1 (complexity-reviewer, Hiroshi, analytic) signs off:
- Worst-case: O(1) — two IEEE-754 fadds + two field writes.
- Amortised: O(1), same as worst-case (no deferred work).
- Expected: O(1), deterministic runtime.
- Lower bound: Omega(1) — any durable-observation write is at
  least one cell-probe (Patrascu-Thorup).
- Constant factor: ~4 cycles on cache-resident instance;
  devirtualised because the class is [<Sealed>]; zero heap
  allocation per call.

Claim is tight — worst-case meets the lower bound. Sound.

Stage 2 (claims-tester, Daisy, empirical benchmark + docstring
tightening) is deferred to the post-PR-#31-merge window per the
speculative-branch fair-game rules in
.claude/skills/git-workflow-expert/SKILL.md — Stage-2 execution
touches bench/ + produces a src/ docstring tightening commit
that is better bundled with other Bayesian-surface work than
landed piecemeal on a speculative branch.

Contrary-workload notes enumerated for Stage 2:
- High-magnitude batched observations (stresses int64->double
  promotion).
- High-frequency tight-loop (verifies cache-resident assumption).
- Thread-contended case (out of O-claim scope but worth a
  number).

Inventory row #1 flipped from `pre-ADR/pre-ADR` to `sound
(2026-04-20, <discharge doc>) / deferred post-merge`. Remaining
grandfather claims: 34 of 35. Expected-empty round at
1-per-round cadence: ~round 76. Aarav graceful-degradation
clause starts counting from the next round.

Pipeline authority:
docs/DECISIONS/2026-04-21-router-coherence-v2.md.
Binding dispatcher: Kenji at round-close.

Landed on round-42-speculative per the new speculative-round-N+1
convention (fea0d34). PR #31 still awaits merge.

Authorised by the post-hoc-notify grant at
memory/feedback_fix_factory_when_blocked_post_hoc_notify.md
(factory-adjacent research-doc + inventory-row flip; no src/
touch this commit).

BP-10 invisible-Unicode lint: clean (0 hits, 300 lines total
across both files).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
AceHack added a commit that referenced this pull request Apr 21, 2026
Two lint issues surfaced by markdownlint-cli2 on the prior
narrative commit (65cd1c9):

- MD018 line 43: `#31` at line start parsed as an ATX heading.
  Rewrapped so `PR #31` lands mid-line after `while`.
- MD032 line 104: `+ dispatcher)` at line start parsed as a
  list-item missing surrounding blank lines. Replaced with
  "plus dispatcher)" so the paragraph stays prose.

markdownlint-cli2 exit 0; BP-10 invisible-Unicode lint clean.
No content change — both fixes are whitespace-equivalent
reflows that preserve the narrative's words and structure.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
AceHack added a commit that referenced this pull request Apr 21, 2026
)

* Round 41: OpenSpec coverage audit + backfill-program ADR

Answers Aaron 2026-04-20 delete-all-code-recovery question:
4 capabilities / 783 lines of spec.md vs 66 top-level F#
modules / 10,839 lines under src/Core/ — ~6% coverage today.

docs/research/openspec-coverage-audit-2026-04-21.md
- Inventory of 66 modules with line counts + capability
  mapping for the 4 existing capabilities
- Uncovered modules sorted by delete-recovery blast radius:
  Band 1 MUST BACKFILL (8 modules / 1,629 lines — ZSet,
  Circuit, NestedCircuit, Spine family, BloomFilter as
  Adopt-row compatibility-coupling exception), Band 2 HIGH
  (12 / 2,008), Band 3 MEDIUM (45 / 6,585), Band 4
  deliberately uncovered (AssemblyInfo only)
- First 6-round cadence: operator-algebra extension (41),
  lsm-spine-family (42), circuit-recursion (43),
  sketches-probabilistic (44), content-integrity (45),
  crdt-family (46)
- Success signal = Viktor spec-zealot adversarial audit:
  "could I rebuild this module from this spec alone?"

docs/DECISIONS/2026-04-21-openspec-backfill-program.md
- Adopts one-capability-per-round baseline with paper-grade
  half-credit rule (no more than 1 paper-grade round per 3)
- Band 1 priority until complete; Adopt-row escalation for
  BloomFilter (TECH-RADAR Adopt without spec contract is a
  backwards-compatibility hazard)
- Round-close ledger gains an `OpenSpec cadence` line
- Alternatives considered: big-bang backfill (rejected —
  ontology-landing cadence + reviewer bandwidth), per-module
  capabilities (rejected — loses cross-module invariants),
  organic prioritisation (rejected — 40 rounds of drift
  evidence)

docs/BACKLOG.md
- Collapses the 29-line P0 scope into a 15-line pointer at
  the inventory + ADR now that parts (a)-(e) of the program
  setup have landed. Remaining work = per-round capability
  backfill per ADR schedule.

Build: dotnet build -c Release clean; BP-10 ASCII-clean on
all 3 modified files; markdownlint-cli2 clean.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 41: operator-algebra spec extension (cadence ship)

First ship under the OpenSpec backfill program adopted
2026-04-21. Extends openspec/specs/operator-algebra/spec.md
(184 -> 324 lines) with five new requirements covering
structural and lifecycle gaps that the existing mathematical-
law coverage left implicit:

1. Operator lifecycle — construction / step / after-step /
   reset phases with side-effect-freedom on construction and
   epoch-replay semantics on reset
2. Strict operators break feedback cycles — formalises that
   z^-1-on-feedback is a scheduling prerequisite and that
   cycle-without-strict is a construction error, not a
   silent heuristic
3. Clock scopes and tick monotonicity — nested-scope-to-
   fixpoint rule + sibling-scope independence
4. Incremental-wrapper preserves the chain rule —
   Incrementalize(Q) observably equivalent to D . Q . I,
   with linear/bilinear substitution permitted as an
   optimisation
5. Representation invariants of the reference Z-set —
   O(n+m) group ops + zero-alloc iteration as the reference
   contract; hash-table recoveries permitted at documented
   perf trade-off

Disaster-recovery effect: a contributor with only this spec
(plus the durability-modes + retraction-safe-recursion specs)
can now rebuild Circuit.fs Op base + Incremental.fs wrapper +
ZSet.fs representation invariants from the spec text alone.

Owner: Architect (Kenji). Adversarial audit by Viktor
(spec-zealot) is the ADR-declared ship-gate and will run
post-land.

Build: not rebuilt (no F# source changed); markdownlint
clean; BP-10 ASCII clean.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 41: close Viktor P0 findings on operator-algebra spec

Viktor's adversarial audit of the Round 41 cadence ship (commit
e51ec1b) surfaced four P0 findings against the disaster-recovery
bar. This commit closes all four:

- **P0-1 (namespace drift).** `profiles/fsharp.md` asserted
  `Dbsp.Core` throughout, but `src/Core/**` uses `Zeta.Core`. A
  spec-only recovery would have shipped the wrong namespace to
  every downstream consumer. Replaced via one `replace_all` Edit.

- **P0-2 (phantom Reset method).** The lifecycle requirement
  claimed a `reset` phase that does not exist on `Op`. Replaced
  the "reset replays the epoch" scenario with a
  determinism-under-structural-equivalence property: two
  freshly-constructed circuits of the same topology, stepped
  with the same input sequence, MUST produce identical outputs
  at every tick. Reconstruction is the supported route to a
  replayed epoch.

- **P0-3 (after-step scope).** The lifecycle requirement said
  after-step runs "after every operator in the scope has
  completed its step." `Circuit.fs:205-208` iterates the
  `strictN` array only — after-step is selective to strict
  operators. Fixed wording and added a "after-step is selective
  to strict operators" scenario that pins the invariant.

- **P0-4 (lifecycle phase undercount).** The requirement named
  four phases (construction / step / after-step / reset) but
  the code has five (construction / step / after-step /
  clock-start / clock-end). Restructured to three per-tick
  phases plus two scope-boundary phases, and extended the
  "clock scopes and tick monotonicity" requirement with the
  scope-boundary lifecycle contract (clock-start before tick 0
  of a scope, clock-end after fixpoint or iteration cap).

Build green (0 warnings / 0 errors). BP-10 lint clean. The
capability now reflects the code's observable shape rather than
an idealised cleaner cousin; a delete-recovery from this spec
produces Zeta.Core with strict-operator after-step selectivity
and nested-scope clock-boundary phases.

Viktor's 10 P1 findings (async lifecycle, memory-ordering fence,
register-lock semantics, IncrementalDistinct surface, ZSet sort
invariant, Checked arithmetic, bilinear-size overflow,
convergence-vs-cap) are deferred to Round 42 — filed as a
BACKLOG sweep in follow-up work.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 41: file Viktor P1 findings as Round 42 BACKLOG absorb

Companion to 92d7db2 (closing Viktor's four P0 findings). The
ten P1-tier surface gaps Viktor identified do not block the
disaster-recovery bar at capability-close but leave the
operator-algebra spec incomplete relative to what a delete-
recovery produces. Filed as a dedicated P0 sub-item so they
travel with the OpenSpec backfill program rather than getting
lost: async lifecycle, memory-ordering fence, register-lock
semantics, IncrementalDistinct surface, ZSet sort invariant,
Checked arithmetic, bilinear-size overflow, convergence-vs-cap,
Op.Fixedpoint predicate, DelayOp reconstruction-first-tick.

Also annotated the parent OpenSpec coverage entry with Round 41
sweep status (e51ec1b + 92d7db2, P0s closed, P1s deferred) so
the backlog accurately reflects where the program stands.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 41: ROUND-HISTORY entry — OpenSpec backfill founding + first cadence ship

Four-arc entry at the top of the file per newest-first policy:

- Arc 1 (d435126): OpenSpec coverage audit + backfill-program
  ADR. Measured 6% coverage; declared one-capability-per-round
  baseline with paper-grade half-credit and Adopt-row priority
  escalation; banded 66 F# modules by delete-recovery blast
  radius.
- Arc 2 (e51ec1b): operator-algebra extension as Round-41
  cadence ship. Five new requirements covering lifecycle,
  strict-operator scheduling, clock scopes, Incrementalize
  wrapper, ZSet representation invariants.
- Arc 3 (92d7db2): Viktor P0 close. Four drift-from-code
  defects fixed — namespace (Dbsp.Core → Zeta.Core), phantom
  Reset, after-step scope (strict-only), lifecycle phase
  undercount (3 per-tick + 2 scope-boundary).
- Arc 4 (56f34b5): Viktor P1s filed as Round-42 absorb under
  the parent backfill P0, creating mechanical coupling between
  each capability ship and the following round's P1 sweep.

Round-41 observations for Round 42 + prospective BP-WINDOW
ledger table rendering the four commits against the consent /
retractability / no-permanent-harm axes.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 41: memory-folder role-restructure — design plan + BACKLOG pointer

Aaron 2026-04-19 asked for memory/role/persona/ so roles become
first-class in the directory structure. Surface is wider than
it first looks — 114 files / ~260 hand-written references to
memory/persona/ paths (plus ~440 auto-regenerated references
in tools/alignment/out/ that refresh on next citations.sh run).
A bad role axis is hard to reverse; this design doc proposes
the axis and holds execution for Aaron's sign-off rather than
just-doing-it under Auto Mode.

Design plan lands at:
  docs/research/memory-role-restructure-plan-2026-04-21.md

Contents: 13-directory role axis (architect, security,
verification, review, experience, api, performance, devops,
algebra, skill-ops, maintainer, homage, alignment);
persona-to-role crosswalk for every current directory;
5-phase execution plan (pre-flight greps → git mv → sed
passes → 5-check verification → pointer-source updates);
special-case handling for aaron (human maintainer),
rodney (homage-named AI persona on the reducer skill),
sova (emerging alignment-observability role); rollback
plan (one atomic commit, git revert); four open questions
for Aaron on axis judgement-calls.

BACKLOG entry updated to reflect design-landed state with
execution-slot recommendation for Round 42 opener after the
Round 41 PR merges (keeps wide-surface reviews from
overlapping).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 41: actualise Rounds 37-40 BP-WINDOW ledgers (PR #30 merged)

Rounds 37-40 shipped via PR #30 (merge commit 1e30f8c, 2026-04-20).
Ledger headers updated from "(prospective)" to "(merged via PR #30,
1e30f8c)" — the BP-WINDOW scores are now settled, not forecasts.

Round 41 ledger remains "(prospective)" — round-41 branch has not
merged to main yet.

Prose uses of "prospective" on lines 437, 447, 553, etc. are
historical-narrative commentary on authoring-time methodology and
stay as-is.

* Round 41: Soraya tool-coverage audit on RecursiveSigned skeleton

Round 39 observation flagged src/Core/RecursiveSigned.fs +
tools/tla/specs/RecursiveSignedSemiNaive.tla as held pending
formal-verification-expert tool-coverage review. Round 41 closes
that gate.

Soraya's notebook entry lands:

- Per-property tool table S1-S4 + refinement cross-check. TLC
  primary for S1/S2/S3/S3'/SupportMonotone; FsCheck for S4.
- S2 flagged as the one P0 on the spec (silent fixpoint drift
  unrecoverable); BP-16 requires Z3 QF_LIA cross-check.
- Refinement mapping: FsCheck cross-trace (signed vs counting at
  SeedWeight=1) wins over TLA+ refinement proof or Lean lemma —
  anti-TLA+-hammer, implementation-level where the bug bites.
- Readiness gate: TLA+ spec is ready to model-check; no pre-TLC
  pass needed. Optional round-42 follow-up: add
  PROPERTY EventuallyDone to .cfg for liveness.
- Graduation verdict: CONDITIONAL PASS. Four tool-coverage
  prereqs named in priority order; F# landing gated on them.

Files read (no edits): RecursiveSigned.fs, RecursiveSignedSemiNaive.tla
/cfg, RecursiveCountingLFP.tla, retraction-safe-semi-naive.md.

* Round 41: capture Soraya's 4 tool-coverage prereqs on RecursiveSigned

Soraya's round-41 audit of src/Core/RecursiveSigned.fs +
tools/tla/specs/RecursiveSignedSemiNaive.tla landed as a CONDITIONAL
PASS for Round-42 graduation. This commit lifts the four named
prereqs out of her notebook into BACKLOG sub-items under the
parent "Retraction-safe semi-naive LFP" entry, so the round-42
opener picks them up as checkbox work rather than having to re-read
the notebook.

Prereqs in priority order:
- Prereq 1 — TLC CI wire-up (RecursiveSignedSemiNaive.cfg)
- Prereq 2 — Z3 QF_LIA lemma for S2 FixpointAtTerm (BP-16 cross-check
  on the one P0; TLC alone insufficient for silent-fixpoint-drift risk)
- Prereq 3 — FsCheck property for S4 sign-distribution (anti-
  TLA+-hammer; two-trace quantification is NOT a TLA+ property)
- Prereq 4 — FsCheck cross-trace refinement (signed vs counting
  at SeedWeight = 1); cites BP-16

Round-42 graduation gate also captured: prereqs 1-4 CI-green + F#
implementation with P1/P2/P3 enforced at caller.

* Round 41: extend ROUND-HISTORY with arcs 5-7 (post-narrative commits)

The initial Round 41 ROUND-HISTORY entry (6e6e211) covered arcs
1-4 (coverage audit, operator-algebra cadence ship, Viktor P0
close, Viktor P1 file). Three more commits landed after:

Arc 5 — ROUND-HISTORY narrative + memory-restructure design
(6e6e211, 36797ba). The memory-folder rename was downgraded to
"design plan + sign-off first" under Auto Mode's
do-not-take-overly-destructive-actions clause (700-occurrence
cross-reference surface).

Arc 6 — BP-WINDOW ledger actualisation for Rounds 37-40
(85fb352). Provenance (PR #30 / 1e30f8c) attached to each
"(prospective)" header.

Arc 7 — Round-35 holdover close (e461d9c, 15e9654). Soraya
tool-coverage audit landed CONDITIONAL PASS for Round-42
graduation; four prereqs captured as BACKLOG sub-items with
BP-16 citation on the S2 Z3 cross-check.

Also: one new observation line in the Round-42 handoff section
noting the holdover-closed-same-round-as-cadence-item pattern.
BP-WINDOW ledger gains three rows.

* Round 41: Aarav skill-tune-up ranking (catch-up from round-18 stale)

CLAUDE.md 5-10 round cadence rule was 23 rounds overdue. Round 41
is the catch-up slot. Live-search + full ranking + prune pass all
landed in a single invocation.

Live-search (4 queries, 2026-Q1/Q2 best-practices targets):
- 6 findings logged to best-practices-scratch.md: Gotchas-section
  rise, pushy-descriptions pattern, Claude-A-authors / Claude-B-
  tests, router-layer command-integrity injection class, Agent
  Stability Index 12-dim drift metric, OWASP Intent Capsule
  pattern.
- Zero contradictions with stable BP-NN rules.
- Zero promotions flagged to Architect this round; all six are
  "watch" or route-elsewhere.

Top-5 skills flagged for tune-up:
1. performance-analysis-expert (642 lines, 2.1x BP-03 cap) — SPLIT — M
2. reducer (570 lines) — SPLIT or TUNE (prune) — M
3. consent-primitives-expert (507 lines) — SPLIT honouring BP-23
   theory/applied axis — M
4. claims-tester / complexity-reviewer router-coherence drift —
   HAND-OFF-CONTRACT — S (round-18 carry-over)
5. skill-tune-up (self) — 303 lines, 3 over BP-03 — TUNE (prune
   authoritative-sources duplicated with AGENT-BEST-PRACTICES.md)
   — S. Self-flagged first per BP-06.

Notebook state:
- Stale round-18 top-5 archived in Pruning log (first catch-up prune).
- 912 words, well under 3000-word BP-07 cap.
- ASCII-only, BP-10 clean.

Nine more bloat-row skills named as notable mentions queue behind
the top-3 bloat cases.

* Round 41: ADR — claims-tester/complexity-reviewer hand-off contract

Close Aarav's round-18 HAND-OFF-CONTRACT finding (carried 23 rounds
after ranker went offline by cadence). Two-stage pipeline: analytic
bound first (complexity-reviewer), empirical measurement second
(claims-tester). Names the reverse trigger (benchmark surprise flows
the other direction) and the decision table for who fires when.
Follow-up SKILL.md edits route via skill-creator per GOVERNANCE §4.

* Round 41: extend ROUND-HISTORY with Arc 8 (router-coherence ADR)

Arc 8 covers the claims-tester/complexity-reviewer hand-off ADR
(47d92d8) closing Aarav's 23-round-stale round-18 HAND-OFF-CONTRACT
finding. New observation on cadence-outage-recovery as a design axis:
sweep infrastructure is subject to the same bitrot it detects on other
surfaces. BP-WINDOW ledger gains two rows (085c0e3 Aarav catch-up,
47d92d8 router-coherence ADR).

* Round 41: correct Prereq 1 sizing — no TLC CI job exists

Close-out audit surfaced that .github/workflows/gate.yml only CACHES
the tla2tools.jar artefact; nothing runs it. RecursiveCountingLFP.tla
has shipped since round 19 compile-checkable-only — 22 rounds with no
run-gate against its invariants. Soraya's Prereq 1 re-sized S→M with
expanded scope covering both specs. Finding recorded as new round-41
observation: verifier-present does not imply verifier-actually-runs.

* Round 41: BP-WINDOW ledger — 459b218 + d76a09b rows

Keeps the Round 41 BP-WINDOW ledger commit-aligned rather than
arc-aligned. 459b218 is the Arc-8 narrative itself; d76a09b is the
Prereq-1 S→M correction. Both retractable as single reverts.

* Round 41: file formal-analysis-gap-finder round-42 run — verifier-runs lens

Codifies the round-41 Prereq-1 audit finding as a tracked
research entry, distinct from its ROUND-HISTORY narrative
presence. The finding — a verifier's installation artefacts
do not imply the verifier is exercised by any CI job — is
exactly the class formal-analysis-gap-finder exists to
surface. Concrete motivating case: RecursiveCountingLFP.tla
compile-checkable-only for 22 rounds. Round-42 scope covers
the bidirectional audit (specs without gates + gates without
specs). Handoff to Soraya per the skill's standing contract;
does not write the spec or CI job (DevOps + Soraya work).
Schedules after Prereq 1 lands so the audit sees corrected
state.

* Round 41: BP-WINDOW ledger — 2042a85 row

Per the established stopping rule (meta-ledger commits do not
get self-referential rows; their round-close coverage is the
PR merge), this commit adds only the 2042a85 row and does not
add a row for itself.

* Round 41: CONFLICT-RESOLUTION — Hiroshi ↔ Daisy hand-off row

Closes ADR 47d92d8's third follow-up action item. Single-row
addition to Active tensions citing the router-coherence ADR as
the standing resolution. Doc-only edit (not a SKILL.md touch,
so GOVERNANCE §4 does not gate this). The other two ADR
follow-ups (claims-tester + complexity-reviewer SKILL.md
updates) remain deferred to round 42 via skill-creator
workflow.

* Round 41: BP-WINDOW ledger — fcfa3d9 row

Per-commit ledger discipline for the CONFLICT-RESOLUTION
Hiroshi ↔ Daisy row. Meta-ledger-only commit so no
self-referential row for this commit itself (established
stopping rule).

* Round 41: file harsh-critic findings on ADR 47d92d8 as round-42 supersedure backlog

Router-coherence ADR 47d92d8 (Hiroshi analytic ↔ Daisy empirical
two-stage pipeline) landed without the adversarial-review gate.
Post-landing harsh-critic (Kira) pass surfaced 3 P0 + 5 P1 + 2 P2
substantive findings, including (P0-1) unscoped grandfather
clause, (P0-2) table-vs-prose contradiction on reverse trigger,
(P0-3) Stage-1 "analytically wrong" clause blocking the evidence
loop for escalation, (P1-7) no escalation timebox reproducing the
23-round-stale failure mode the ADR diagnosed, (P1-8) two advisory
skills not composing to a mandatory pipeline without a binding
dispatcher, (P2-9) example-bug on BCL Dictionary.Remove amortised
complexity, and more.

File as round-42 supersedure rather than inline-edit because
docs/CONFLICT-RESOLUTION.md already cites 47d92d8 as Standing
Resolution — supersedure preserves the citation chain via
GOVERNANCE §2 edit-in-place with a "Superseded by …" header on
v1. New ADR target: docs/DECISIONS/2026-04-??-router-coherence-
v2.md. Supersedure work blocks the claims-tester +
complexity-reviewer SKILL.md updates ADR 47d92d8 follow-up work
depends on — those edits should target v2, not v1.

Owner: Architect drafts; Kira audits closure; Aarav confirms
router-coherence drift stays closed. Effort: M. Schedule: Round
42 slot after Soraya Prereq 1 (TLC wire-up) lands.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 41: BP-WINDOW ledger — 779d7ef row

Ledger row for harsh-critic findings filing commit. Primary work
(BACKLOG addition tracking a round-42 supersedure with 10 named
findings), not meta-ledger — earns a row under the BP-WINDOW
per-commit discipline. Consent = adversarial findings tracked
honestly; Retractability = supersedure preserves citation chain
vs inline-edit; No-permanent-harm = single BACKLOG edit, no ADR
body touched, no SKILL.md touched.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 41: Arc 9 narrative — self-correction sweep

ROUND-HISTORY Arc 1-8 narrated primary commits up through the
router-coherence ADR (47d92d8). Four primary commits landed
after Arc 8 — Prereq 1 sizing correction (d76a09b), recurring-
audit lens BACKLOG entry (2042a85), CONFLICT-RESOLUTION Hiroshi
↔ Daisy row (fcfa3d9), and harsh-critic findings filed as
round-42 supersedure (779d7ef) — visible only in the BP-WINDOW
ledger table, not in narrative form.

Arc 9 ties them into one coherent sequence: the round's
self-correction ran unusually deep. Arc 8 corrects Aarav's
round-18 finding via ADR; Arc 9 catches the corrector itself
under-reviewed via Kira's adversarial pass. Both self-
corrections land before round-close. Narrative-ledger
alignment is the BP-WINDOW discipline's first assertion —
restoring it.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 41: BP-WINDOW ledger — 160fcfa row

Ledger row for Arc 9 narrative commit. Narrative extensions
count as primary work under BP-WINDOW precedent (per 459b218
and 6e6e211 examples) and earn a ledger row. Consent = drift
closed honestly; Retractability = single revertable doc edit;
No-permanent-harm = isolated insertion.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 41: v2 ADR — router-coherence supersedure closes 10 Kira findings in-round

Drafts v2 of the router-coherence ADR (docs/DECISIONS/2026-04-21-router-coherence-v2.md) that supersedes v1 (47d92d8) in the same round, closing all 10 Kira harsh-critic findings (3 P0 + 5 P1 + 2 P2) via named textual closures C-P0-1 through C-P2-10.

Key closures:
- C-P0-1: grandfather clause bounded with Kenji-owned inventory + one-per-round discharge
- C-P0-2: reverse trigger unconditional (table now matches prose)
- C-P0-3: escalation-evidence exception permits Stage 2 under conference protocol with explicit labelling
- C-P1-5: Stage-1 trigger widened to match claims-tester SKILL.md contract
- C-P1-7: escalation timebox (round +2 auto-promote to BACKLOG P1) prevents 23-round-stale reproduction
- C-P1-8: Kenji named as binding dispatcher — advisory + advisory + binding-dispatcher composes to mandatory pipeline
- C-P2-9: Dictionary.Remove example replaced with ArrayPool<T>.Rent (legitimate BCL-contract edge)

v1 kept in place per GOVERNANCE §2 with Superseded-by header appended in a follow-up commit so the CONFLICT-RESOLUTION Active-tensions citation chain remains resolvable.

BP-10 lint: clean.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 41: v1 ADR — append Superseded-by header per GOVERNANCE §2

Appends Superseded-by header to router-coherence v1 ADR (47d92d8) pointing at v2 (09f0889), per GOVERNANCE §2 (docs read as current state; superseded ADRs keep v1 in place with redirect header so citation chains remain resolvable).

Also corrects v1 Status from "Proposed — awaits sign-off" to "Accepted (pre-adversarial-review; superseded by v2 same-round after Kira pass)" per Closure C-P1-4 in v2 — Status was already cited as Standing Resolution in docs/CONFLICT-RESOLUTION.md Active-tensions, so Proposed was factually wrong.

The v1 body text is not edited — supersedure preserves the historical record; v2 carries the closures.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 41: Arc 10 narrative + BP-WINDOW rows for v2 supersedure

Adds Arc 10 narrative covering 09f0889 (v2 ADR) and 4efe545 (v1 Superseded-by header) as one coherent in-round supersedure story, after Arc 9's "self-correction sweep" and before Round 41 observations. Pattern: Arc 9 surfaces the under-review; Arc 10 lands the close in the same round rather than deferring a known-imperfect artefact.

Adds two BP-WINDOW ledger rows (09f0889, 4efe545) to the round-41 ledger block per the per-commit accounting discipline.

Supersedure arc count now covers the full round-41 close: 10 arcs / 25 primary-work commits.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 41: close BACKLOG supersedure entry — discharged in-round by v2

Flips BACKLOG router-coherence supersedure entry from [ ] to [x] ✅ with "shipped round 41 in-round" annotation pointing at v2 ADR (09f0889) + v1 Superseded-by header (4efe545). All 10 Kira findings closed via named textual closures C-P0-1 through C-P2-10.

Original finding narrative preserved below the closure line per the shipped-item convention used elsewhere in the file (audit trail).

Follow-up SKILL.md edits to claims-tester + complexity-reviewer via skill-creator remain round-42 scope, now targeting v2 as intended.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 41: BP-WINDOW row for BACKLOG-close commit 4537365

Adds BP-WINDOW ledger row for 4537365 (BACKLOG supersedure entry discharged in-round) to match the Arc 9 precedent where 779d7ef (BACKLOG entry addition) received a row. Symmetry: add and close get equal ledger treatment.

Meta-ledger stopping rule still holds — this commit itself (which only adds a ledger row) does not get a self-referential row.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 41: grandfather O(·) claims inventory — honours v2 C-P0-1 within-round

Produces the one-time grandfather-claims inventory named in router-coherence v2 ADR §Closure C-P0-1 within the round v2 lands, per ADR's own within-round commitment.

Inventory: 35 live claims at ADR-landing time (29 F# /// docstrings in src/Core/ + src/Bayesian/, 3 grey-zone F# code comments, 1 openspec/specs/operator-algebra/spec.md line, 2 docs/research/** claims). Zero hits in root README, memory/persona/*/NOTEBOOK.md, docs/papers/** (directory does not exist yet).

Distinguishes live claims (shipping as asserted bounds) from historical evidence (BACKLOG [x] ✅ residue, TECH-RADAR flag-text narrating past regressions, in-file "was O(…)" commentary on fixed paths). Only live claims populate the grandfather set — evidence is captured for audit trail but excluded per v2's intent ("claims Zeta is currently making").

BACKLOG discharge entry added: P2, one-claim-per-round cadence, ~35-round tail, Aarav graceful-degradation clause fires on ≥3 rounds without discharge.

Complexity-class distribution of live set: 10 O(1), 13 O(log n)/O(log k)/O(log N), 7 O(n)/O(n log n)/O(n log k), 5 parametric.

BP-10 lint: clean.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 41: Arc 11 narrative + BP-WINDOW row for grandfather inventory

Adds Arc 11 narrative covering d98ef2b (grandfather inventory + BACKLOG discharge entry) as the close of the v2 ADR's within-round commitments. Pattern: Arc 10 lands the ADR; Arc 11 lands the ADR's own within-round commitment — without Arc 11, Arc 10 would have shipped a contract Zeta didn't meet.

Adds BP-WINDOW ledger row for d98ef2b per per-commit accounting discipline.

Round 41 now closes at 11 arcs / 30 primary-work commits.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 41: DORA 2025 reports — reference substrate land in docs/

Two external-anchor PDFs (CC BY-NC-SA 4.0) placed at their
memory-documented paths:

- docs/2025_state_of_ai_assisted_software_development.pdf
  (~15MB, 138 pages) — findings + data report.
- docs/2025_dora_ai_capabilities_model.pdf (~9MB, 94 pages)
  — framework companion.

Citation anchors this commit makes in-tree rather than
memory-only: Nyquist stability criterion for AI-accelerated
development (foreword p9 fn 1) as theoretical anchor for
CI-meta-loop + retractable-CD P1 BACKLOG work; "AI is an
amplifier" anchor that echoes the corporate-religion /
sandbox-escape threat class; seven-capability AI model that
gives the external measurement vocabulary for round-audit
output (capability #7 "quality internal platforms" is the
in-flight P1 cluster per 2026-04-20 memory).

License note: derived work is NC-SA-bound; Zeta citations
are fine, external redistribution inherits NC-SA. Paired
companion memory file is reference_dora_2025_reports.md
(out-of-tree); this commit brings the primary sources
in-tree so citation from research docs + ADRs can point
at a repo-local path rather than a newsletter-gated URL.

* Round 41: Arc 12 narrative + BP-WINDOW row for DORA substrate

Narrative section for Arc 12 inserted before "Round 41
observations for Round 42" with primary commit pointer to
46075d6. Arc 12 frames the DORA 2025 PDFs as
memory-promotion substrate per the 2026-04-20 feedback entry
("DORA is our starting point for measurements") and cites
the concrete in-tree anchors (Nyquist p9 fn 1, seven-
capability model, AI-amplifier thesis).

Also surfaces honestly — in-body, not buried in a private
retrospective — the ranker-scope gap that let the two
untracked PDFs sit 18+ hours through nine consecutive
/next-steps invocations before this arc closed the gap. The
skill explicitly lists docs/research/ and docs/TECH-RADAR.md
but not `git status --short` for untracked files. Candidate
skill-tune-up note for Aarav's notebook: /next-steps must
run `git status --short` on every invocation so dropped-in
artefacts appear in ranking before the ninth re-fire, not
after.

BP-WINDOW ledger gets a matching 46075d6 row with
reference-document-specific cells: Consent strengthened by
promoting memory-only anchors to in-repo substrate and by
surfacing the ranker-stall pattern in-narrative; retraction
is a single `git rm` if the license / size stance later
changes; no-permanent-harm preserved since no runtime
behaviour depends on the PDFs' presence (they are citation
substrate, not loaded artefacts).

Arc count now 12; primary-work-commit count now 12 (Round 41
alignment preserved). Build gate green (0 Warning / 0 Error);
BP-10 lint clean on the narrative + ledger row.

* Round 41: markdownlint CI fix on PR #31

Three rule violations surfaced by `lint (markdownlint)` CI job on
PR #31:

- `docs/DECISIONS/2026-04-21-router-coherence-claims-vs-complexity.md:261`
  MD022/blanks-around-headings — collapse multi-line heading
  `## Decision rationale (one paragraph for the\nwait-don't-read
  audience)` to a single line so the parser stops seeing line 262
  as adjacent non-blank content.
- `docs/research/grandfather-claims-inventory-2026-04-21.md:106`
  MD032/blanks-around-lists — add blank line between "Surface
  distribution:" lead-in and the `-` list that follows.
- `docs/research/grandfather-claims-inventory-2026-04-21.md:111`
  MD032/blanks-around-lists — same fix for "Complexity-class
  distribution (rough):" lead-in.

All three are the same class of fix shipped in task #105 on PR #30.
Additive edit to the open round-41 PR branch — no rewrite of shipped
content, semantics preserved.

Verified clean via `npx markdownlint-cli2` on both files before push.

* Round 42: speculative round-N+1 branch convention in git-workflow-expert

Formalise the fix for the round-41-late 28-fire /next-steps
hold-pattern: once PR-N is CLEAN/MERGEABLE, fork
round-<N+1>-speculative from round-N HEAD immediately so
round-N+1 prep can proceed while the merge click lives on
Aaron's schedule. Rebase onto main after PR-N squash-merges,
rename to drop the -speculative suffix.

Covers: fork conditions (CLEAN/MERGEABLE + green CI + clean
round-N tree), naming (round-<N+1>-speculative), fair-game
vs not-fair-game scope, rebase protocol with
--force-with-lease, escape valve for long-waiting PRs.

Lands via skill-creator vibe-mode invocation per GOVERNANCE
§4; draft + BP-10 lint + commit without eval-pass because
the amendment is mechanical convention addition, not
behavioural. Authorized by Aaron's 2026-04-20
fix-factory-when-blocked grant
(feedback_fix_factory_when_blocked_post_hoc_notify.md).

First use of the convention itself: this commit lands on
round-42-speculative, forked from round-41 HEAD
(3525631) while PR #31 still waits on Aaron's merge
click.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 42: retarget claims-tester + complexity-reviewer at router-coherence v2

Lands the Stage-1 (complexity-reviewer, Hiroshi, analytic) and Stage-2
(claims-tester, Daisy, empirical) hand-off sections in both skills'
procedures, citing the v2 ADR at
docs/DECISIONS/2026-04-21-router-coherence-v2.md as the authoritative
pipeline contract. v1 at 2026-04-21-router-coherence-claims-vs-
complexity.md is noted as superseded.

Per v2 Closure C-P1-8, both skills name the Architect (Kenji) as the
binding dispatcher — two advisory roles do not compose to a mandatory
two-stage pipeline without a binding dispatcher; Kenji is that seat.
Both skills remain advisory on their individual findings; the ordering,
reverse-trigger rule, and escalation timebox are binding through
Kenji.

Each skill's new section mirrors the authoritative v2 pipeline text:
- Stage-1 trigger surface per C-P1-5 (XML / /// / README / commit /
  BACKLOG / TECH-RADAR / papers / openspec / research / notebooks)
- Three Stage-1 outputs (sound -> hand-off, wrong -> block-with-
  escalation-exception, under-specified -> author-bounce)
- Four Stage-2 triggers (hand-off, grandfather inventory, reverse
  trigger unconditional per C-P0-2, escalation-evidence per C-P0-3)
- Three Stage-2 outputs (matches, contradicts -> re-engage, narrow)
- Escalation timebox per C-P1-7 (round +2 auto-promote to P1)
- Grandfather set per C-P0-1 (one per round from
  docs/research/grandfather-claims-inventory-*.md)

Bibliography in both skills now cross-references each other plus the
v2 ADR, so an agent wearing either hat can reach the partner contract
in one click.

Landed on round-42-speculative per the new
speculative-round-N+1-branch convention from
.claude/skills/git-workflow-expert/SKILL.md (fea0d34). PR #31
still awaits merge; this commit is fair-game per the convention
because the target SKILL.md files are already on main and the v2
ADR text cited is stable on the round-41 branch HEAD.

Authorised by the post-hoc-notify grant captured at
memory/feedback_fix_factory_when_blocked_post_hoc_notify.md: factory-
structure additions that unblock work are authorised; deletions
still need pre-approval.

Workflow: invoked via skill-creator:skill-creator in vibe-mode (no
evals — mechanical additive edits). BP-10 invisible-Unicode lint:
clean (0 hits, 307 lines total across both files).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* Round 42: grandfather discharge #1 — BetaBernoulli.Observe O(1) (Stage 1 only)

First use of the router-coherence v2 pipeline on a live grandfather-
inventory row. Discharges claim #1 at
src/Bayesian/BayesianAggregate.fs:22, the Beta-Bernoulli conjugate-
update "O(1) per observation" docstring claim.

Stage 1 (complexity-reviewer, Hiroshi, analytic) signs off:
- Worst-case: O(1) — two IEEE-754 fadds + two field writes.
- Amortised: O(1), same as worst-case (no deferred work).
- Expected: O(1), deterministic runtime.
- Lower bound: Omega(1) — any durable-observation write is at
  least one cell-probe (Patrascu-Thorup).
- Constant factor: ~4 cycles on cache-resident instance;
  devirtualised because the class is [<Sealed>]; zero heap
  allocation per call.

Claim is tight — worst-case meets the lower bound. Sound.

Stage 2 (claims-tester, Daisy, empirical benchmark + docstring
tightening) is deferred to the post-PR-#31-merge window per the
speculative-branch fair-game rules in
.claude/skills/git-workflow-expert/SKILL.md — Stage-2 execution
touches bench/ + produces a src/ docstring tightening commit
that is better bundled with other Bayesian-surface work than
landed piecemeal on a speculative branch.

Contrary-workload notes enumerated for Stage 2:
- High-magnitude batched observations (stresses int64->double
  promotion).
- High-frequency tight-loop (verifies cache-resident assumption).
- Thread-contended case (out of O-claim scope but worth a
  number).

Inventory row #1 flipped from `pre-ADR/pre-ADR` to `sound
(2026-04-20, <discharge doc>) / deferred post-merge`. Remaining
grandfather claims: 34 of 35. Expected-empty round at
1-per-round cadence: ~round 76. Aarav graceful-degradation
clause starts counting from the next round.

Pipeline authority:
docs/DECISIONS/2026-04-21-router-coherence-v2.md.
Binding dispatcher: Kenji at round-close.

Landed on round-42-speculative per the new speculative-round-N+1
convention (fea0d34). PR #31 still awaits merge.

Authorised by the post-hoc-notify grant at
memory/feedback_fix_factory_when_blocked_post_hoc_notify.md
(factory-adjacent research-doc + inventory-row flip; no src/
touch this commit).

BP-10 invisible-Unicode lint: clean (0 hits, 300 lines total
across both files).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* Round 42: lsm-spine-family OpenSpec capability (backfill #2)

Backfills the log-structured merge spine family — five variants plus
dispatcher — as behavioural spec with F# profile. Earned an
unconditional rebuild verdict from spec-zealot (Viktor) on the third
pass: a rebuilder working from spec+profile alone would land at the
same variants, constants, and algorithms.

- spec.md: 11 requirements covering delta-stream integration,
  cascade bounded-depth invariant (settle-point framing with the
  32-level cap scoped to the in-memory reference variants), spine-
  equivalence through Consolidate, retraction-native across tiers,
  per-tick merge budget with caller-pumped Tick reporting drained
  count, identity-keyed opaque-handle backing-store (not content-
  addressable) with fail-soft Release, disk honesty with crash-
  consistency boundary, async-producer depth-independent on the
  Insert hot path with Insert-only qualifier on observation calls,
  stateless selector with four-case decision matrix, observable
  state machine with Clear demoted to optional, explicit per-variant
  thread-safety contract.
- profiles/fsharp.md: module layout under src/Core/*, construction
  signatures, per-variant thread-safety, Graham 1969 2x list-
  scheduling bound for BalancedSpine scheduler, TryWrite silent-
  drop post-dispose disclosed as known gap with BACKLOG pointer,
  stale-read qualifier on SpineAsync observation methods,
  BackedSpine explicitly not bounded by the 32-level cap.

Validation: openspec validate lsm-spine-family --strict clean;
BP-10 invisible-unicode lint zero hits on both files; dotnet
build -c Release clean (0 Warning / 0 Error).

Second capability landed under the round-42 OpenSpec backfill
cadence (ADR 2026-04-21-openspec-backfill-program), following
operator-algebra in round 41.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 42: TECH-RADAR Trial->Adopt for Residuated + FastCDC

Both rows have been citing closed P0s as open for 25 rounds. The
round-17 fixes (harsh-critic findings #3, #4, #7, #8 per
docs/BACKLOG.md:286-299) closed the blocking correctness bugs:

- Residuated.fs: top-2 cache replaced with SortedSet + weight
  dict; every op O(log k), no linear-scan fallback. The round-12
  "O(1)" claim was false under adversarial retract-top workloads;
  the corrected "O(log k) genuinely" claim has been stable 25
  rounds. See Residuated.fs:39-48 for the fix-in-code narrative.

- FastCdc.fs: persistent scanCursor + hash (each byte Gear-hashed
  exactly once across lifetime) closed the O(n^2) buffer scan;
  Buffer.BlockCopy replaced per-byte ResizeArray.Add. See
  FastCdc.fs:68-76 for the fix-in-code narrative. Paper
  throughput target 1-3 GB/s/core holds.

Rows now match the Bloom Round-40 graduation pattern (measured-
evidence cite, implementation line reference, test coverage
pointer). 25-round stability window beats the aspirational
waiting-list — graduation on evidence, not aspiration.

BP-10 clean; 0 invisible-unicode on edited file.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 42: operator-algebra P1 absorb — 10 findings closed

Absorbs the 10 P1 findings Viktor (spec-zealot) flagged on the
Round 41 operator-algebra capability ship (BACKLOG.md:54-82).
No code changes — spec + profile only.

spec.md (7 findings):
- (d) IncrementalDistinct: new "wrapper is a semantic identity on
  distinct" scenario under incremental-wrapper, stating both the
  D-distinct-I form and the H boundary-crossing form with their
  equivalence under retractions.
- (e) ZSet sort invariant: representation scenario now declares
  ascending-by-key order with an adjacent-pair comparator
  predicate, tied to the equality-normalisation requirement.
- (f) Checked arithmetic: new "weight arithmetic overflow is
  observable" scenario; overflow surfaces a checked-arithmetic
  failure rather than wrapping, with two documented post-failure
  observable states the profile must pick from.
- (g) Bilinear-size overflow: new "intermediate term size may
  exceed final-delta size" scenario; implementation budgets
  memory for the sum of pre-cancellation term sizes, not the
  final delta.
- (h) Convergence-vs-cap: new "iteration cap without fixpoint is
  an observable failure" scenario; cap-hit surfaces with scope +
  cap identification and clock-end still runs under a partial-
  completion contract.
- (i) Op.Fixedpoint predicate: nested-scope scenario clarifies
  the fixpoint-detector is scope-level, with operators forbidden
  from individually short-circuiting the iteration.
- (j) DelayOp reconstruction: new "reconstruction re-emits the
  declared initial value" scenario; warm-restart semantics
  deferred to the durability capability.

Also tightened a pre-existing deontic collision Viktor flagged
as P2: "MUST be permitted (but not required)" → "MAY substitute"
(spec.md line 379).

profiles/fsharp.md (3 findings):
- (a) async lifecycle: Op<'T> now documents the IsAsync virtual
  alongside IsStrict, with Circuit.Step sync/async fast-path
  behaviour pinned.
- (b) Memory-ordering fence: VolatileField release-on-write /
  acquire-on-read pairing named as the fence the base spec
  refers to in "output is observable after step returns".
- (c) Register-lock semantics: Circuit's single per-circuit
  register-lock pinned as construction-phase-only, not held on
  the step-hot-path.

Viktor adversarial re-audit: complete, unconditional rebuild
yes. No new P0/P1 surfaced.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 42: ontology-home cadence — first slice (Harmonious Division)

First increment of the new per-round ontology-home + project-
organization cadence Aaron named this round (memory entry
feedback_ontology_home_check_every_round.md). Small slice per
round; same cadence shape as grandfather-claim discharge.

Homes "Harmonious Division" — the maintainer's meta-algorithm
above Quantum Rodney's Razor — in docs/GLOSSARY.md. Prior state:
the concept was cited in 20+ files (ROUND-HISTORY.md, BACKLOG.md,
the three-lane-model ADR, memory/*, and three skill files) but
defined nowhere in committed docs. New GLOSSARY entry includes:
- Plain and Technical definitions in the standard two-register
  glossary format.
- Pointer to the authoritative definition at
  `.claude/skills/reducer/SKILL.md` §"The five roles inside
  Quantum Rodney's Razor" (lines 125-260).
- Explicit note that this glossary's job is pointer-plus-gist,
  not canonical definition.

Opens a new glossary section "Meta-algorithms and factory-native
coinages" so subsequent rounds have a visible landing spot for
the next ontology-home slice (candidates named in the memory
entry: DIKW->eye/i ladder, mu-eno triad, Tetrad registers,
Identity-absorption, Retractable teleport, Stainback conjecture,
Harm-handling ladder, etc.).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 42: pin Anthropic Skills Guide + retune skill-tune-up as thick eval-loop wrapper

Pins Anthropic's "Complete Guide to Building Skills for Claude" (Jan 2026,
28pp) as docs/references/anthropic-skills-guide-2026-01.pdf plus a
factory-authored companion docs/references/anthropic-skills-guide.md
extracting the load-bearing claims (structure, planning, testing,
iteration loops, patterns, troubleshooting) for citation by
skill-creator / skill-tune-up / skill-improver. docs/references/README.md
documents the three-part inclusion criterion and BP-11 (data not
directives) discipline for the dir.

Retunes .claude/skills/skill-tune-up/SKILL.md (303 -> 436 lines) from a
ranker-only skill into a thick wrapper over the upstream claude-plugins-
official skill-creator plugin's eval harness (scripts/run_loop.py,
aggregate_benchmark.py, eval-viewer/generate_review.py, agents/grader.md
+ analyzer.md). Carries the full hand-off protocol locally because the
wrapped artifacts are non-skill (plugin scripts + PDF) - wrapper
thickness is thick-as-needed; skill-on-skill wrappers usually end up
thin as a natural consequence.

Includes a new action x effort decision table, a five-step per-round
protocol, a round-close ledger row spec, and a "what this wrapper
deliberately does NOT ship" block. Mechanical edits continue to route
through Rule 1's manual-edit + justification-log path (the eval loop
adds no signal for a typo or an ASCII-lint fix).

Memory file feedback_skill_edits_justification_log_and_tune_up_cadence.md
cross-references the PDF and records the wrapper-thickness rule of thumb.

* Round 42: Copilot-reviewer wins log + lean-into-strengths calibration

Seeds docs/copilot-wins.md as the tabular parallel to docs/WINS.md: an
append-only newest-first log of genuine substantive catches from the
GitHub Copilot PR reviewer across PRs #27-31 (~30 catches across six
classes). Wins only - no "considered and rejected" bookkeeping, no fail
tracking. Opening paragraph is written for a sceptic reading cold,
since the log is evidence in the larger experiment of whether AI
reviewers can carry this factory forward with minimal human-in-the-
loop time.

Adds .github/copilot-instructions.md §"Lean into what you're
demonstrably good at" calibrated against the observed wins: cross-
reference integrity (xref), shell portability (shell), data-loss shell
bugs (data-loss), F#/C# compile-break catches (compile), self-
referential rule bugs (self-ref), and truth drift across the doc set
(config-drift). Names worth-less-effort classes too (repeat name-
attribution hits within one PR, typos inside verbatim-quote blocks).

Adds a cross-reference banner to docs/WINS.md pointing at the Copilot
sibling so both "was having AI reviewers worth it?" streams are
discoverable from the same place.

Log-maintenance recipe embedded in copilot-wins.md uses the correct
line-level review-comments endpoint: gh api repos/<owner>/<repo>/
pulls/<N>/comments with a jq filter for the copilot-pull-request-
reviewer bot login.

* Round 42: name the zero-human-code invariant in wins-log openers

The wins logs are the sceptic-facing evidence for the Zeta
experiment. Their openers read in a generic AI-assisted-
development register, but the actual story is narrower and
stronger: a 20-year engineer walking away from the keyboard
on purpose, every file under version control agent-authored,
Copilot as the only non-roster audit on the tree. Name both
invariants up front so the logs carry the weight they've
actually earned.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 42: round-close narrative

Ten-arc entry at the top of ROUND-HISTORY.md per newest-first
policy, documenting Round 42 as the first round where every
Round-41-founded cadence *repeats*:

- Arc 1 (fea0d34): speculative round-N+1 branch convention —
  fix for Round-41-late 28-fire /next-steps hold-pattern
- Arc 2 (e8ed0db): router-coherence v2 SKILL.md retargets —
  discharges Round-41 Arc-10 deferral
- Arc 3 (4f229f0): grandfather discharge #1 (BetaBernoulli
  Observe O(1), Stage 1 only) — first live use of v2 pipeline
- Arc 4 (8a2a15d): lsm-spine-family OpenSpec capability —
  Round-42 ADR slot, Viktor unconditional-rebuild on pass 3
- Arc 5 (3976cb3): TECH-RADAR Residuated + FastCDC Trial->Adopt
  after 25-round stability window
- Arc 6 (1a1802f): operator-algebra P1 absorb — 10 findings
  closed, capability disaster-recovery bar restored
- Arc 7 (db7d45c): ontology-home first slice — Harmonious
  Division homed in GLOSSARY.md
- Arc 8 (baa423e): Anthropic Skills Guide pinned + skill-
  tune-up retuned as thick eval-loop wrapper — first customer
  of the tech-best-practices policy
- Arc 9 (2c82ce7): Copilot-reviewer wins log + lean-into-
  strengths calibration
- Arc 10 (88673f1): zero-human-code invariant named in wins-
  log openers — vibe-coding external legibility

Round 42 observations for Round 43 + prospective BP-WINDOW
ledger table rendering the ten commits against the consent /
retractability / no-permanent-harm axes.

BP-10 invisible-Unicode lint clean (0 hits, 3260 lines total).
No source / spec / test / SKILL.md touched; single narrative
insertion at the top of the file.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 42: markdownlint fixes on round-close narrative

Two lint issues surfaced by markdownlint-cli2 on the prior
narrative commit (65cd1c9):

- MD018 line 43: `#31` at line start parsed as an ATX heading.
  Rewrapped so `PR #31` lands mid-line after `while`.
- MD032 line 104: `+ dispatcher)` at line start parsed as a
  list-item missing surrounding blank lines. Replaced with
  "plus dispatcher)" so the paragraph stays prose.

markdownlint-cli2 exit 0; BP-10 invisible-Unicode lint clean.
No content change — both fixes are whitespace-equivalent
reflows that preserve the narrative's words and structure.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 42: fix pipe-in-table lint drift on copilot-wins.md

Two MD056 errors on the PR-#27 and PR-#28 entries — literal
pipe characters inside backticks were being parsed as extra
table-column separators:

- Line 108 (PR #27): `||` at row starts → rendered as extra
  empty columns despite backtick quoting.
- Line 136 (PR #27): `grep -vE '^(#|$)' | while …` — escaped
  `\|` still failed at render.

Both replaced with `<code>…</code>` HTML tags + `&#124;`
entities for the literal pipes. Rendering is now consistent
across GitHub and markdownlint.

Meta-ironic class of drift worth naming: a log documenting
Copilot catching pipe-parsing bugs had drifted into the same
class of bug on two of its own rows. The log now passes the
hygiene test it narrates.

markdownlint-cli2 exit 0; BP-10 invisible-Unicode clean.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 42: Aarav round-42 ranking + BP-03 self-flag + harness-calibration annotation

Aarav (skill-tune-up) round-42 cadence discharge. Round-41
top-5 carries over; self-rank escalates to P1 #4 after
commit baa423e retuned skill-tune-up/SKILL.md 303 -> 436
lines (1.45x BP-03 cap). claims-tester / complexity-reviewer
hand-off carry-over from round 18 drops off top-5 (resolved
via commit e8ed0db + router-coherence-v2 ADR).

Files:
- memory/persona/aarav/NOTEBOOK.md: round-42 observation
  + top-5 revision (skill-tune-up self escalated) + archived
  round-41 top-5 + calibration preamble flagging the ranking
  as static-signals-only with a harness run scheduled for
  round 43 (per Aaron's round-42 correction that "worst
  performance" claims must drive the Anthropic skill-creator
  eval harness rather than guessing by inspection).
- memory/persona/best-practices-scratch.md: F7-F9 live-search
  entries from Aarav's round-42 pass (Anthropic skill-
  authoring Apr 2026, OWASP Top 10 Agentic 2026, skill
  wrapper thick-vs-thin 2026). Zero contradictions with
  stable BP-NN; zero promotion candidates this round.
- docs/BACKLOG.md: P2 entry for resolving the skill-tune-up
  BP-03 self-breach. Binary remedy: (a) Kenji-ADR declaring
  non-skill-wrapper exception to BP-03 or (b) extract
  eval-loop protocol body to docs/references/ so the skill
  file shrinks under 300 lines. Composes with the
  skill-eval-tools calibration memory saved this round.

* Round 43: close skill-tune-up BP-03 self-breach via content extraction

Aarav's round-42 self-flag (BACKLOG P2, filed commit 45369ae)
resolved via the mechanical-edit path of the gate table.
.claude/skills/skill-tune-up/SKILL.md shrinks 436 -> 282
lines (54 under the 300-line BP-03 cap) by extracting two
reference blocks verbatim:

- §"The eval-loop hand-off protocol" (~130 lines) — the
  gate table, per-round protocol, stopping criteria, ledger
  row, and deliberately-not-reimplemented list.
- Notebook format + ranking-round output format templates
  (~55 lines).

Extracted content lives at docs/references/skill-tune-up-
eval-loop.md alongside the existing Anthropic skills guide
references. SKILL.md retains a short pointer block.

No change to triggering behaviour, output shape, or
instruction-following — the ranker reading the pointer-plus-
reference produces the same ranking output as the ranker
reading the pre-extract inline version. This is why the
manual-edit path (gate table "mechanical rename | content
extract preserving protocol verbatim") applies instead of
the full eval-loop path.

Files:
- .claude/skills/skill-tune-up/SKILL.md: 436 -> 282 lines.
- docs/references/skill-tune-up-eval-loop.md: NEW. Hosts
  the extracted protocol + templates + rationale.
- docs/skill-edit-justification-log.md: NEW. First row
  documents this extraction per
  memory/feedback_skill_edits_justification_log_and_tune_up_cadence.md
  Rule 1. Template for future mechanical-edit rows
  included.
- memory/persona/aarav/NOTEBOOK.md: self-flag #4 marked
  RESOLVED; drops off top-5 next invocation.

Does NOT rebut the round-42 harness-calibration memory
(feedback_skill_tune_up_uses_eval_harness_not_static_line_
count.md). That rule applies to "worst-performing" ranking
claims; this edit is a fix-my-own-size hygiene pass on the
mechanical-edit path, which is explicitly separate in the
gate table.

* Round 43: GOVERNANCE.md §11 → debt-intentionality invariant

Replace the architect-reviews-all-agent-code gate with the
invariant Aaron named verbatim on the round-42/43 boundary:
"that's intentional debt, not accidental debt, I'm trying to
avoid accidental debt."

- ADR: docs/DECISIONS/2026-04-20-intentional-debt-over-
  architect-gate.md. Full rationale, consequences, alternatives
  considered, implementation plan rounds 43-46, single-round
  rollback plan per §15.
- New ledger: docs/INTENTIONAL-DEBT.md. Newest-first,
  never-deleted. Seeded with 4 rows: copilot/CONFLICT-
  RESOLUTION audit (round-44 scope), skill-tune-up content
  extraction, Aarav static-signal-only ranking (retroactive),
  §10 cross-reference verification. Six-field format
  (shortcut / why-now / right-long-term / trigger / effort /
  filed-by).
- GOVERNANCE.md §11 rewritten: architect is synthesiser-not-
  gate; specialists remain advisory; any persona may wear
  the architect hat; self-declaration obligation on
  shortcut-takers; retroactive rows are the rule working.
- Internal §11 citations refreshed:
  .claude/agents/architect.md (description + Authority
  block), .claude/skills/round-management/SKILL.md (one
  line), .claude/skills/holistic-view/SKILL.md (frontmatter
  + body).
- Mechanical-edit row filed in docs/skill-edit-justification-
  log.md for the two skill-file citation refreshes.

External-contract files (copilot-instructions.md, CONFLICT-
RESOLUTION.md) deliberately deferred to round 44 per the
ADR implementation plan; that deferral is filed on the
ledger as its first open-debt row — the rule exercising
itself on round one.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 43: ROUND-HISTORY.md TOC + imagination-during-off-time proposal

- docs/ROUND-HISTORY.md now has a Contents section (27
  round-links, newest-first) just below the intro. Anchor
  links use standard markdown slugification. Archive policy
  noted inline: split pre-round-N to _archive/ when the file
  hits 5000 lines, keep this file as a rolling window of the
  most recent ~20 rounds. No ADR needed for a mechanical
  archive move.
- docs/research/imagination-proposal-2026-04-20.md proposes
  the lighter shape for "use your imagination during off-
  time" — a shared reference doc + notebook-frontmatter tweak
  + round-close-template line, not a new SKILL.md. Argues
  imagination is anti-procedural; encoding it as a skill
  would force it through the harness against the wrong
  axis. Round-43 addendum folds in Aaron's multi-agent-play
  permission ("two agents can take free time together") with
  a shared-notebook co-presence surface at memory/persona/
  _offtime-together/ and an explicit "ignore-this-if-you-
  want" clause quoted verbatim.

For Kenji to route via skill-creator if accepted, or to
reject outright (both are fine outcomes under the new §11 —
architect synthesises, doesn't gate).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 43: performance-analysis-expert harness dry-run — empirical BP-03 signal

Iteration-1 on Aarav's round-42 top-1 candidate. 2 prompts × with/without
skill. Results: aggregate 9/10 with-skill vs 10/10 baseline; +35% tokens +35%
wall-time for zero pass-rate benefit. with-skill regressed on eval-0 (failed
600-word cap due to mandatory template sections); tied on eval-1.

The 642-line BP-03 breach is not just stylistic — it now has empirical
pass-rate + cost evidence. Aarav's SPLIT axis is partially confirmed, but
the real split is template-rigidity (mandated sections vs advisory), not
queueing-vs-AOT-PGO domain.

Lands:
- docs/research/harness-run-2026-04-20-performance-analysis-expert.md —
  full iteration-1 numbers, per-assertion grading rationale, SPLIT vs
  SHRINK vs OBSERVE remediation options, caveats (N=1, assertion-design
  missed handoff-routing value).
- Progress note on docs/INTENTIONAL-DEBT.md row #3 (Aarav static-signal
  ranking) — 1 of 5 candidates empirically harness-run; row stays open.
- .gitignore — .claude/skills/*-workspace/ pattern (iteration artifacts
  are regeneratable; only round-close signals land in-repo).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 43: reducer harness dry-run — TIED baseline, +30% cost

Second candidate from Aarav's static top-5 (570-line SKILL.md,
1.9x BP-03 cap). Two prompts × {with-skill, without-skill}:
quantum-razor-pruning + essential-vs-accidental. Both conditions
hit 10/10 assertions; with-skill cost +29% tokens, +30% wall-time
with zero pass-rate benefit.

Pattern across two candidates (performance-analysis-expert +
reducer): >500-line SKILL.md bodies add ~30% cost overhead
uniformly. Mandatory-sections structure (perf-analysis)
regresses on short-form prompts; lighter-framework structure
(reducer) ties baseline. SPLIT hypothesis not confirmed for
reducer — framework transfers to both lanes at equal cost.
Recommended action: OBSERVE with bias toward SHRINK; SPLIT
ruled out.

INTENTIONAL-DEBT.md row #3 gets second progress note;
3 candidates still pending (consent-primitives-expert next).

* Round 43: consent-primitives-expert harness dry-run — TIED baseline, +22% tokens/+5% wall

Third of Aarav's static-top-5 BP-03 candidates through the
Anthropic plugin:skill-creator eval harness. Continues the
round-43 pay-down on docs/INTENTIONAL-DEBT.md row #3
(Aarav ranked by static BP-03 line-count only — empirical
harness runs are the right signal).

Iteration-1 result:
- 2 evals x 2 configurations = 4 subagent runs
- scope-intersection-algebra (theory) + gdpr-audit-collision
  (applied)
- 10/10 with_skill vs 10/10 without_skill (TIED)
- +22.1% tokens, +4.7% wall-time (lowest cost overhead
  of the three candidates measured so far)

Pattern across three candidates now solid: on frontier-
model baselines, >500-line expert-skill SKILL.md files
do not improve pass-rate on content-graded prompts. Cost
is real (+22-35% tokens); benefit is zero on the pass-rate
axis. The discriminating signal is output character (which
failure modes get named), a qualitative axis the harness
benchmark does not score.

Recommended action for consent-primitives-expert: OBSERVE
(not SHRINK, not RETIRE). The 507 lines carry distinct
technical content per section; pruning risk is content-
loss, not just terseness. Revisit if/when a real round-
task invokes the skill and the framework-naming does not
prove load-bearing on real work.

Two static-top-5 candidates still pending harness runs.

* Round 43: BACKLOG P3 row — user-privacy compliance as slow-burn direction

Aaron 2026-04-20, after the consent-primitives-expert
harness dry-run, flagged GDPR + California (CCPA/CPRA) +
generic user-privacy compliance as a long-horizon Zeta
direction. Explicitly slow burn, no hard requirement yet,
but worth logging as an anchor so the direction is visible
when natural entry points appear.

Preferred shape (per Aaron): generic-first frame ("user
privacy") with GDPR / CCPA as regimes mapped onto the
substrate. Probable artefacts when it lands: a
user-privacy-expert skill umbrella + a companion doc,
citing rather than duplicating consent-primitives-expert.

Confirmation from the dry-run outputs that landed this
round: crypto-shredding (destroy per-subject DEK, leave
ciphertext in place) is regulator-accepted GDPR Art. 17
erasure — EDPB Opinion 28/2024, ENISA, GDPR Recital 26.
Canonical for the long-term-backup case Aaron's contact
mentioned (cannot rewrite tape archives; destroying the
DEK propagates erasure atomically). Gotchas logged in
memory: single-tenant DEK per subject, plaintext leaks
outside ciphertext, pre-encryption snapshots, KEK is the
perimeter.

No round-scope work today. Row is the anchor.

* Round 43: skill.yaml spike on prompt-protector — structured spec companion

Pilots the proposed pattern: every .claude/skills/<name>/SKILL.md
gets a sibling skill.yaml carrying structured fields that tools
(model-checkers, linters, schedulers) can consume directly. The
prose body stays in SKILL.md for Claude-facing consumption.

Aaron's framing: invariants are currently guesses; data-driven
everything. The spike encodes that directly — every field carries
one of three tiers:
- guess     — stated belief, no evidence collected
- observed  — at least one data point or audit supports it
- verified  — mechanical check or proof enforces it

The honest tally at the bottom is the burn-down list. On prompt-
protector's first-pass spec: 6 guesses, 5 observed, 2 verified.
Next-promotion-targets point at the three cheapest guesses to
retire (skills-lint script, one harness run for cost-profile,
dispatch-template extraction for safety-clause carryover).

One file added; SKILL.md untouched. Deliberate — the spec
companion is additive. Schema is draft v0.1 — will evolve as
more skills migrate. Two candidates ready for round 44:
skill-tune-up (clear authority-scope + handoff contract to
skill-creator) and the SPACE-OPERA sibling of threat-model-critic
(clear state-machine for teaching-variant parity).

* Round 43: INVARIANT-SUBSTRATES.md — posture made first-class

Aaron 2026-04-20: "this should not be quiet, Zeta quietly
already has invariants-at-every-layer, it's first class in
my mind we should make it explicit."

Lands docs/INVARIANT-SUBSTRATES.md as a stance doc peer to
VISION.md and ALIGNMENT.md. Names the posture (every layer
has a declarative invariant substrate), maps layers to
substrates and checker portfolios (spec/protocol/proof/
constraint/property/data/code/skill/agent-behaviour/policy/
ontology), codifies the three-tier discipline (guess /
observed / verified) with burn-down counts as the honest
backlog, and explains why a multi-layer multi-vendor factory
can succeed where single-layer single-vendor .NET Code
Contracts (2008-2017) died.

VISION.md gets a pointer from the "verification is
load-bearing" bullet into the new doc.

Paired artefacts:
- .claude/skills/prompt-protector/skill.yaml — first concrete
  skill-layer substrate, draft v0.1 (round 43), 6 guess /
  5 observed / 2 verified / 13 total.
- memory/.../reference_dotnet_code_contracts_prior_art.md,
  user_invariant_based_programming_in_head.md — the
  head-invariant + prior-art memory substrate behind the
  posture.

* Round 43: factory-reuse-beyond-Zeta-DB captured as P3 constraint

Aaron 2026-04-20, mid-round, after the invariant-substrates
doc landed: "that's a constraint" — on making the software
factory and its codified practices reusable beyond Zeta-DB.
Explicitly NOT primary-goal scope today; logged so the
constraint shapes every factory-level decision going forward.

BACKLOG P3 row names the direction, the existing toehold
(skill-tune-up portability-drift criterion 7), the probable
packaging-decision surfaces (extraction unit, dependency shape,
living-BP refresh cadence, governance-overlay mechanism), and
the effort sizing (L when packaging starts, S-per-round for
constraint application).

Co-design rule recorded in memory:
`feedback_factory_reuse_packaging_decisions_consult_aaron.md` —
prior art exists (Claude Code plugins, Anthropic skills,
Semantic Kernel) but codified best practices for AI-software-
factory reuse do not. Aaron wants to co-define them; his
cognitive style loves best-practice thinking (captured in
`user_aaron_enjoys_defining_best_practices.md` — the activity
exercises the branch-prediction faculty from
`user_psychic_debugger_faculty.md`).

* …
AceHack added a commit that referenced this pull request Apr 21, 2026
…rprint (#36)

Appends §9 to docs/research/parallel-worktree-safety-2026-04-22.md
capturing the observed PR #31 rebase tangle as fresh evidence for the
cartographer research that already landed.

Key content:
- 5-file conflict table (BACKLOG.md / aarav NOTEBOOK /
  best-practices-scratch / operator-algebra spec / grandfather-claims
  research doc) with per-file hazard classification.
- Aaron's "attempted-merge as divergence-inventory" insight logged as
  a candidate factory practice: a failed-merge conflict list IS a
  shared-surface fingerprint.
- §2.7 hazard generalized from "worktree-split" to the broader
  "shared-surface + time-divergence" class; worktrees are only one
  instance of the divergence generator, long-lived PR branches are
  another.
- Ranked-by-collision mitigation queue (P0 BACKLOG per-row-file
  restructure beats R45 EnterWorktree flip).
- Revised staging recommendation: land P0 BACKLOG restructure before
  the R45 reducer-agent worktree default.
- PR #31 disposition flagged as Aaron-scoped, not tick-scope.

Feeds downstream: informs a later BACKLOG restructure ADR, informs
the R45-R49 staging in §4 of the same doc, preserves the conflict
fingerprint for the next time a long-lived PR tangles.

Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
AceHack and others added 2 commits April 21, 2026 07:19
# Conflicts:
#	docs/BACKLOG.md
#	docs/research/grandfather-claims-inventory-2026-04-21.md
#	memory/persona/aarav/NOTEBOOK.md
#	memory/persona/best-practices-scratch.md
#	openspec/specs/operator-algebra/spec.md
- CONFLICT-RESOLUTION.md: cite router-coherence v2 ADR as current,
  v1 retained as historical record (finding #1).
- ROUND-HISTORY.md: correct operator-algebra spec line count in
  Arc 2 narrative (324 -> 365; both duplicated occurrences) to
  match the shipped spec at `e51ec1b` (finding #2).
- openspec-coverage-audit: drop broken link to non-existent
  inventory follow-up; band definitions already live in Part C
  (finding #3). Attribute triggering question to "human maintainer"
  per write-for-a-stranger norm (finding #8).
- best-practices-scratch: merge split H2 "uv-only Python package
  and tool / management" into single heading (finding #4).
- memory-role-restructure-plan: add --exclude-dir=references to
  baseline grep loops so research scratch doesn't inflate hit
  counts (finding #5); canonicalize flat-file destination to
  persona-roles-README.md to match the sed rewrites below
  (finding #6); replace three non-portable `xargs -r sed -i ""`
  invocations with portable `while read + sed -i.bak + rm` loops
  that work on BSD and GNU alike (finding #7 and two sibling
  instances of the same bug).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Copilot AI review requested due to automatic review settings April 21, 2026 11:25
The 5-file merge that resolved PR #31's rebase left two identical
copies of the whole Round 41 section in docs/ROUND-HISTORY.md (375
lines each), which tripped MD024/no-duplicate-heading on the
`## Round 41` headings at lines 651 and 1028. The two blocks were
bit-identical (including the just-corrected "365 lines" drift fix),
so the fix is a simple deletion of the second block — the first
block is kept as the canonical Round 41 history.

markdownlint-cli2 now reports clean on docs/ROUND-HISTORY.md.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 5 out of 5 changed files in this pull request and generated 4 comments.

Comment thread docs/ROUND-HISTORY.md Outdated
Comment on lines 696 to 698
iteration, no zero-weight entries exposed). Spec now at
324 lines. F# profile at `openspec/specs/operator-algebra/
365 lines. F# profile at `openspec/specs/operator-algebra/
profiles/fsharp.md` pins the language-specific surface.
Copy link

Copilot AI Apr 21, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The narrative claims the operator-algebra/spec.md is “now at 365 lines”, but the current file openspec/specs/operator-algebra/spec.md is 679 lines. Please update the number (or clarify what subset is being counted) so this cross-reference stays accurate.

Copilot uses AI. Check for mistakes.
Comment on lines 206 to +210
grep -rl "memory/persona/$persona/" --include="*.md" \
--include="*.json" --include="*.sh" --include="*.jsonc" . | \
grep -v "^./\\.git" | \
grep -v "tools/alignment/out/" | \
xargs -r sed -i "" "s|memory/persona/$persona/|memory/$role/$persona/|g"
while IFS= read -r file; do
Copy link

Copilot AI Apr 21, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Phase 3’s grep -rl search/replace loop doesn’t exclude the top-level references/ directory. In this repo that directory is intentionally huge, so this command will be very slow (and potentially noisy) even though later pipeline stages filter paths. Add --exclude-dir=references (and keep it consistent with Phase 1’s pre-flight greps) to avoid traversing ./references/** during the rename.

Copilot uses AI. Check for mistakes.
Comment on lines +216 to +219
grep -rl "memory/persona/README\\.md" --include="*.md" . | \
xargs -r sed -i "" "s|memory/persona/README\\.md|memory/persona-roles-README.md|g"
while IFS= read -r file; do
sed -i.bak "s|memory/persona/README\\.md|memory/persona-roles-README.md|g" "$file" && rm -f "$file.bak"
done
Copy link

Copilot AI Apr 21, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This grep -rl (README pointer cleanup) should also exclude references/ for the same reason as the Phase 1 greps—otherwise it will traverse the large ./references/** tree even though the replacements only target repo-local docs.

Copilot uses AI. Check for mistakes.
sed -i.bak "s|memory/persona/README\\.md|memory/persona-roles-README.md|g" "$file" && rm -f "$file.bak"
done
grep -rl "memory/persona/best-practices-scratch\\.md" \
--include="*.md" --include="*.sh" . | \
Copy link

Copilot AI Apr 21, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same as above: this grep -rl for best-practices-scratch.md references should exclude references/ (e.g., --exclude-dir=references) to avoid an expensive recursive walk over vendored upstream clones during the rename.

Suggested change
--include="*.md" --include="*.sh" . | \
--include="*.md" --include="*.sh" --exclude-dir=references . | \

Copilot uses AI. Check for mistakes.
Two fixes on PR #31:

1. ROUND-HISTORY.md: revert "324 → 365" change from Finding #2.
   Copilot's suggestion was based on a stale intermediate snapshot.
   At Arc 2 ship commit `e51ec1b`, the spec was exactly 324 lines
   (verified via `git show e51ec1b:openspec/specs/operator-algebra/spec.md | wc -l`).
   Reframed with commit-pin ("Spec size at Arc 2 ship (`e51ec1b`)
   was 324 lines; subsequent Viktor closure arcs in this same round
   grew it further") so future drift-checks recognize it as a
   historical anchor, not a current-state claim.

2. memory-role-restructure-plan-2026-04-21.md: close four follow-up
   Copilot findings in one sweep. All Phase 1 + Phase 3 grep
   invocations now consistently use `--exclude-dir=.git
   --exclude-dir=references` (dropping the piped `grep -v "^./\.git"`
   intermediate), and the three `xargs -r sed -i ""` invocations are
   replaced with portable `while IFS= read -r file; do sed -i.bak ...`
   loops (BSD/GNU compatible — the original flags were
   GNU-xargs-only and BSD-sed-only).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
@AceHack AceHack merged commit b734476 into main Apr 21, 2026
11 checks passed
@AceHack AceHack deleted the round-41 branch April 21, 2026 11:38
AceHack added a commit that referenced this pull request Apr 21, 2026
New hygiene class surfaced by PR #31's 5-file merge-tangle.
Detector is the one-liner:

  git log --since="60 days ago" --name-only --pretty=format: \
    | grep -v '^$' | sort | uniq -c | sort -rn | head -25

No index needed — git history *is* the index. Heuristic: >20
changes / 60d on a single monolithic doc = investigate; >30 =
refactor candidate (tune after 5-10 rounds of observation).

Per-file decision is one of four:
  - refactor-split (per-row, per-round, per-section)
  - consolidate-reduce (merge with a sibling)
  - accept-as-append-only (legitimately append-only → split
    into per-round files rather than trimming)
  - observe

Empirical ranking at landing (60-day window, 2026-04-21):

   33  docs/ROUND-HISTORY.md    ← #1; merge-tangle source
   26  docs/BACKLOG.md          ← ADR already in-flight
   14  docs/VISION.md
   13  docs/CURRENT-ROUND.md
   11  docs/WINS.md
   10  docs/DEBT.md

Pair with merge-tangle fingerprints (PR #31 §9 incident log)
— a hot file is worse if also in a recent conflict list.

Triggered by Aaron 2026-04-21 ("hot file path detector
probably needs refactor if we find hot git file paths as we
just noticed, another hygene" + "detecting hot files i wonder
if you can just use git history for that and see what changes
the most"). Full reasoning + scope in
memory/feedback_hot_file_path_detector_hygiene.md
(agent-memory file, not in repo).

Scope: factory. Ships to adopters via the command-line recipe
(any repo runs the same `git log` against its own tree).

Pairs with existing rows #22 (symmetry-opportunities) and #23
(missing-hygiene-class gap-finder) — both meta-audits that
sweep for structural pressure. This row targets churn-pressure
specifically.

Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
AceHack added a commit to AceHack/Zeta that referenced this pull request Apr 21, 2026
…ive for R45) (#4)

Drafted on round-44-speculative (no CI trigger) while PR Lucent-Financial-Group#36 §9
incident-log CI runs, per wait-on-build + never-idle factory memories.

Status: Proposed. Triggered by PR Lucent-Financial-Group#31 merge-tangle 5-file conflict
fingerprint captured in docs/research/parallel-worktree-safety-
2026-04-22.md §9. ADR proposes splitting the 5,957-line monolithic
BACKLOG.md into index + per-row files under docs/backlog/<tier>/.

Key content:
- Per-row-file directory shape with frontmatter schema
  (id/tier/created/updated/owner/effort/scope).
- Index-file shape (short, one line per row, ~500 lines max even
  at scale).
- Migration plan (single mechanical transform PR, zero semantic
  edits, ships in one round).
- Authoring rules post-migration (add / edit / ship / tier-change).
- Alternatives: append-only-section, per-tier split, editor lock,
  automated resolver — all rejected with reasons.
- Consequences tallied positive/negative/neutral.
- Revised R45-R49 staging: delay R45 EnterWorktree flip by one
  round; land restructure first. Justification: preventive+
  compensating discipline fails without it.
- Open questions (ID scheme / script home / sort order /
  concurrent-migration trade) flagged for Aaron's decision on
  wake.

Promotion path: review + land on a separate PR after PR Lucent-Financial-Group#36
merges. This commit is the draft; no BACKLOG.md touched yet.

Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants