From ffe1261901d8457862e5acf43db38d51a2b34c92 Mon Sep 17 00:00:00 2001 From: Aaron Stainback Date: Thu, 23 Apr 2026 15:57:32 -0400 Subject: [PATCH 1/9] =?UTF-8?q?frontier-readiness:=20gap=20#5=20audit=20?= =?UTF-8?q?=E2=80=94=205-file=20planning-docs=20batch=20(15=20of=20~16=20d?= =?UTF-8?q?one)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Batched audit of the project-planning files. All classified short-form since shape is factory-generic + content is project-specific. - GLOSSARY.md → both (coupled): format generic, Zeta-term entries specific - ROUND-HISTORY.md → zeta-library-specific: Zeta's rounds - BACKLOG.md → zeta-library-specific: ~6700 lines Zeta rows - ROADMAP.md → zeta-library-specific: Zeta roadmap - VISION.md → zeta-library-specific: Zeta vision, 11-pass editing history, Elisabeth dedication Pattern after 15 audits (3 classes cleanly separated): - 5 factory-generic (GOVERNANCE / AGENT-BEST-PRACTICES / ALIGNMENT / AUTONOMOUS-LOOP / FACTORY-HYGIENE) - 6 both-coupled (CLAUDE / AGENTS / CONFLICT-RESOLUTION / WONT-DO / TECH-RADAR / GLOSSARY) - 4 zeta-library-specific (ROUND-HISTORY / BACKLOG / ROADMAP / VISION) 15 of ~16 top-level files done. Remaining: directory- level audits (.claude/skills/**, .claude/agents/**, openspec/**, tools/**, .github/**). Multi-repo split mechanical plan clearer: - factory-generic → verbatim to Frontier (5 files) - both-coupled → surgical edits per file, most to Frontier with Zeta content extracted (6 files) - zeta-library-specific → stay in Zeta, Frontier gets empty templates (4 files) Attribution: Otto (loop-agent PM hat). Co-Authored-By: Claude Opus 4.7 --- .../factory-vs-zeta-separation-audit.md | 139 +++++++++++++++++- 1 file changed, 134 insertions(+), 5 deletions(-) diff --git a/docs/frontier-readiness/factory-vs-zeta-separation-audit.md b/docs/frontier-readiness/factory-vs-zeta-separation-audit.md index a540b66c..ff3ac088 100644 --- a/docs/frontier-readiness/factory-vs-zeta-separation-audit.md +++ b/docs/frontier-readiness/factory-vs-zeta-separation-audit.md @@ -63,14 +63,14 @@ For each audited file: - **docs/WONT-DO.md** (below, fire #15) — also docs/ALIGNMENT.md on PR #185 - **docs/TECH-RADAR.md** (below, fire #16) - **docs/FACTORY-HYGIENE.md** (below, fire #16) — also docs/AGENT-BEST-PRACTICES.md on PR #184, docs/ALIGNMENT.md on PR #185 +- **docs/GLOSSARY.md** (below, Otto-18 fire) +- **docs/ROUND-HISTORY.md** (below, Otto-18 fire) +- **docs/BACKLOG.md** (below, Otto-18 fire) +- **docs/ROADMAP.md** (below, Otto-18 fire) +- **docs/VISION.md** (below, Otto-18 fire) — also GOVERNANCE.md on PR #181, AGENT-BEST-PRACTICES.md on PR #184, ALIGNMENT.md on PR #185, TECH-RADAR.md + FACTORY-HYGIENE.md on PR #188 ### Files to audit (not yet classified; add rows as they land) -- `docs/GLOSSARY.md` -- `docs/ROUND-HISTORY.md` -- `docs/BACKLOG.md` -- `docs/ROADMAP.md` -- `docs/VISION.md` - `.claude/skills/*/SKILL.md` (each) - `.claude/agents/*.md` (each) - `openspec/**` (structural; library-specific-heavy) @@ -757,6 +757,135 @@ tagged" was wrong; the rows were all tagged. This audit formalises that self-classification as the file's purpose. +## Audit — docs/GLOSSARY.md + +**Overall classification:** **both (coupled)** — plain- +English/technical format is factory-generic; specific Zeta +term entries (IVM, DBSP, Z-set, retraction, Spine, etc.) +are Zeta-library-specific content. + +**File location post-split:** Frontier (format + preamble ++ the-rule-for-this-file + "spec has two meanings" framing +pattern); Zeta retains specific term entries. + +**Length:** 814 lines. Large vocabulary. + +### Classification + +- **Format** (plain/technical dual-definition, grandparent- + comprehensibility rule, two-meanings disambiguation): factory-generic +- **Entries** (IVM, DBSP, Z-set, retraction, operator algebra, + Spine, HyperLogLog, etc.): zeta-library-specific + +### Refactor notes + +1. Frontier inherits preamble + format rule + empty-section + scaffolding +2. Zeta retains all current term entries as library + glossary +3. Adopters populate their own glossary per the format + +Effort: **S** — shape extraction; entries stay in Zeta. + +## Audit — docs/ROUND-HISTORY.md + +**Overall classification:** **zeta-library-specific** — by +design this file is historical narrative of Zeta's specific +rounds. The *discipline* (round-narrative append-only, +"docs elsewhere are current-state") is factory-generic +(established in GOVERNANCE §2 + §6), but the file's content +is purely Zeta project history. + +**File location post-split:** Zeta repo retains as-is +(historical record); Frontier gets empty template with +preamble + append-only rule as an adopter template. + +**Length:** 3559 lines — large history. + +### Refactor notes + +1. Frontier inherits preamble + "newest first" convention + + empty Contents section as template +2. Zeta retains full round-history as historical record +3. Adopters start their own ROUND-HISTORY.md at round 1 + +Effort: **S** (shape extraction). + +## Audit — docs/BACKLOG.md + +**Overall classification:** **zeta-library-specific** — the +file contains ~6700 lines of specific-project BACKLOG rows +(P0/P1/P2/P3). The *shape* (priority tiers, one-row-per-item, +newest-first-within-tier, legend + appendix) is factory- +generic (GOVERNANCE §29 scopes the file). + +**File location post-split:** Zeta retains as-is; Frontier +gets empty template with preamble + priority-tier legend + +example-row framework. + +**Length:** 6761 lines. + +### Refactor notes + +1. Frontier inherits preamble + legend + empty priority + sections as template +2. Zeta retains full BACKLOG content +3. Adopters populate their own BACKLOG from empty template + +Note: the Frontier readiness P0 row itself is partly +factory-generic (the gap-8-audit pattern is reusable) +but instance-specific to Zeta's own Frontier construction. +On split, the Frontier-bootstrap row gets an "executed" +marker and moves to Frontier's own ROUND-HISTORY as +historical-record of the split. + +Effort: **S** (shape extraction). + +## Audit — docs/ROADMAP.md + +**Overall classification:** **zeta-library-specific** — +roadmap is by definition project-specific. Shape (P0/P1/P2 +tiers + Research category + newest-first) is factory- +generic (effectively same shape as BACKLOG; a "roadmap vs +backlog" sibling-scope convention). + +**File location post-split:** Zeta retains; Frontier gets +empty template. + +**Length:** 177 lines. + +Effort: **S**. + +## Audit — docs/VISION.md + +**Overall classification:** **zeta-library-specific** — the +long-term vision document is by definition project-specific +(named after Zeta; Aaron's 11-passes editing history). +Shape (Dedication header + foundational principle + +Products numbered + Product-N vision subsections) is +factory-generic pattern. + +**File location post-split:** Zeta retains as-is (preserves +Aaron's 11-pass editorial lineage + Elisabeth dedication); +Frontier gets empty template with the shape. + +**Length:** 886 lines. + +Effort: **S**. + +## Pattern summary after 15 audits + +| Class | Count | Files | +|---|---|---| +| factory-generic | 5 | GOVERNANCE, AGENT-BEST-PRACTICES, ALIGNMENT, AUTONOMOUS-LOOP, FACTORY-HYGIENE | +| both (coupled) | 5 | CLAUDE, AGENTS, CONFLICT-RESOLUTION, WONT-DO, TECH-RADAR, GLOSSARY (6 actually) | +| zeta-library-specific | 4 | ROUND-HISTORY, BACKLOG, ROADMAP, VISION | + +15 of ~16 top-level files audited. Remaining: the `.claude/ +skills/**` + `.claude/agents/**` + `openspec/**` + `tools/**` ++ `.github/**` directory-level surfaces (each a multi-file +audit). + ## How this audit connects to the multi-repo split Gap #5 (this audit) is load-bearing for gap #1 (multi-repo From 414cf517b28ef3ed6095590c73e261d4d1d9bb98 Mon Sep 17 00:00:00 2001 From: Aaron Stainback Date: Fri, 24 Apr 2026 10:27:24 -0400 Subject: [PATCH 2/9] review-drain: role-refs for VISION.md audit + fix pattern-summary count Two PR #190 review threads: - PRRT_kwDOSF9kNM59NTkB (P1, line ~492): rewrite direct contributor-name attribution to role references per Otto-220 name-attribution discipline. "Aaron's 11-pass editorial lineage" -> "human-maintainer 11-pass editorial lineage"; "Elisabeth dedication" -> generic "in-memoriam dedication header" with a pointer to the "honor those that came before" discipline in CLAUDE.md (which is where the specific named-memory carve-out lives). - PRRT_kwDOSF9kNM59NTkg (P1, line ~504): pattern-summary table said Count=5 for "both (coupled)" but listed 6 files with a "(6 actually)" marker. Corrected count to 6, removed the marker, added an explicit 5+6+4=15 totals line so the table is mechanically consistent. No semantic change to the audit classifications; the VISION.md row still reads zeta-library-specific and the file still belongs on the Zeta side of the split. --- .../factory-vs-zeta-separation-audit.md | 19 +++++++++++-------- 1 file changed, 11 insertions(+), 8 deletions(-) diff --git a/docs/frontier-readiness/factory-vs-zeta-separation-audit.md b/docs/frontier-readiness/factory-vs-zeta-separation-audit.md index ff3ac088..2130f8cc 100644 --- a/docs/frontier-readiness/factory-vs-zeta-separation-audit.md +++ b/docs/frontier-readiness/factory-vs-zeta-separation-audit.md @@ -860,13 +860,16 @@ Effort: **S**. **Overall classification:** **zeta-library-specific** — the long-term vision document is by definition project-specific -(named after Zeta; Aaron's 11-passes editing history). -Shape (Dedication header + foundational principle + +(named after Zeta; 11 passes of human-maintainer editing +history). Shape (Dedication header + foundational principle + Products numbered + Product-N vision subsections) is factory-generic pattern. **File location post-split:** Zeta retains as-is (preserves -Aaron's 11-pass editorial lineage + Elisabeth dedication); +the human-maintainer 11-pass editorial lineage plus the +in-memoriam dedication header; the dedication names a +specific person and stays per the "honor those that came +before" discipline in CLAUDE.md); Frontier gets empty template with the shape. **Length:** 886 lines. @@ -878,13 +881,13 @@ Effort: **S**. | Class | Count | Files | |---|---|---| | factory-generic | 5 | GOVERNANCE, AGENT-BEST-PRACTICES, ALIGNMENT, AUTONOMOUS-LOOP, FACTORY-HYGIENE | -| both (coupled) | 5 | CLAUDE, AGENTS, CONFLICT-RESOLUTION, WONT-DO, TECH-RADAR, GLOSSARY (6 actually) | +| both (coupled) | 6 | CLAUDE, AGENTS, CONFLICT-RESOLUTION, WONT-DO, TECH-RADAR, GLOSSARY | | zeta-library-specific | 4 | ROUND-HISTORY, BACKLOG, ROADMAP, VISION | -15 of ~16 top-level files audited. Remaining: the `.claude/ -skills/**` + `.claude/agents/**` + `openspec/**` + `tools/**` -+ `.github/**` directory-level surfaces (each a multi-file -audit). +Total: 5 + 6 + 4 = **15** top-level files audited out of +~16. Remaining: the `.claude/skills/**` + `.claude/agents/**` ++ `openspec/**` + `tools/**` + `.github/**` directory-level +surfaces (each a multi-file audit). ## How this audit connects to the multi-repo split From c8b159e7d92ff0360e91bd4faa8f3ce5c1da926a Mon Sep 17 00:00:00 2001 From: Aaron Stainback Date: Fri, 24 Apr 2026 11:11:32 -0400 Subject: [PATCH 3/9] review-drain: approximate line counts + correct ROUND-HISTORY attribution MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Addresses 5 copilot-pull-request-reviewer threads on PR #190: - GLOSSARY.md length 814 -> approximately 840 (current tree is ~840) - ROUND-HISTORY append-only discipline no longer attributed to GOVERNANCE §2+§6 (§2 is "docs are current-state", §6 is round naming; neither establishes append-only). Re-attributed to the file's own preamble as the authoritative source. - ROUND-HISTORY.md length 3559 -> approximately 3560 - BACKLOG.md length 6761 -> "approximately 8500 (grows tick-by-tick; see BACKLOG split design doc)" — switching to approximate framing prevents recurring drift as backlog grows, and points at the Phase-1a generator already on main (PR #354). - ROADMAP.md length 177 -> approximately 178 - VISION.md length 886 -> approximately 887 Switching from exact to approximate line counts is reviewer's own suggested remediation; this eliminates the audit's dependency on stable file sizes that are expected to drift. Rebased on main after BACKLOG split Phase-1a (PR #354) landed; keep-both-sides resolution on the append-only "Files audited" list per Otto-229. --- .../factory-vs-zeta-separation-audit.md | 21 ++++++++++--------- 1 file changed, 11 insertions(+), 10 deletions(-) diff --git a/docs/frontier-readiness/factory-vs-zeta-separation-audit.md b/docs/frontier-readiness/factory-vs-zeta-separation-audit.md index 2130f8cc..0125cdb5 100644 --- a/docs/frontier-readiness/factory-vs-zeta-separation-audit.md +++ b/docs/frontier-readiness/factory-vs-zeta-separation-audit.md @@ -768,7 +768,7 @@ are Zeta-library-specific content. + the-rule-for-this-file + "spec has two meanings" framing pattern); Zeta retains specific term entries. -**Length:** 814 lines. Large vocabulary. +**Length:** approximately 840 lines. Large vocabulary. ### Classification @@ -791,16 +791,17 @@ Effort: **S** — shape extraction; entries stay in Zeta. **Overall classification:** **zeta-library-specific** — by design this file is historical narrative of Zeta's specific -rounds. The *discipline* (round-narrative append-only, -"docs elsewhere are current-state") is factory-generic -(established in GOVERNANCE §2 + §6), but the file's content -is purely Zeta project history. +rounds. The separation between round-history narrative here +and current-state documentation elsewhere is factory-generic +in shape (the file's own preamble is the authoritative +source for the newest-first / append-only convention), but +this file's content is purely Zeta project history. **File location post-split:** Zeta repo retains as-is (historical record); Frontier gets empty template with preamble + append-only rule as an adopter template. -**Length:** 3559 lines — large history. +**Length:** approximately 3560 lines — large history. ### Refactor notes @@ -814,7 +815,7 @@ Effort: **S** (shape extraction). ## Audit — docs/BACKLOG.md **Overall classification:** **zeta-library-specific** — the -file contains ~6700 lines of specific-project BACKLOG rows +file contains thousands of lines of specific-project BACKLOG rows (P0/P1/P2/P3). The *shape* (priority tiers, one-row-per-item, newest-first-within-tier, legend + appendix) is factory- generic (GOVERNANCE §29 scopes the file). @@ -823,7 +824,7 @@ generic (GOVERNANCE §29 scopes the file). gets empty template with preamble + priority-tier legend + example-row framework. -**Length:** 6761 lines. +**Length:** approximately 8500 lines (size grows tick-by-tick; see BACKLOG split design doc for the per-row-file migration). ### Refactor notes @@ -852,7 +853,7 @@ backlog" sibling-scope convention). **File location post-split:** Zeta retains; Frontier gets empty template. -**Length:** 177 lines. +**Length:** approximately 178 lines. Effort: **S**. @@ -872,7 +873,7 @@ specific person and stays per the "honor those that came before" discipline in CLAUDE.md); Frontier gets empty template with the shape. -**Length:** 886 lines. +**Length:** approximately 887 lines. Effort: **S**. From e8b07d1ef7c63dd2aec6b4c5cad2b26f5e27ec4c Mon Sep 17 00:00:00 2001 From: Aaron Stainback Date: Fri, 24 Apr 2026 15:45:14 -0400 Subject: [PATCH 4/9] fix: markdownlint auto-fixes on planning-files-batch audit Co-Authored-By: Claude Opus 4.7 --- docs/frontier-readiness/factory-vs-zeta-separation-audit.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/frontier-readiness/factory-vs-zeta-separation-audit.md b/docs/frontier-readiness/factory-vs-zeta-separation-audit.md index 0125cdb5..f6bd06a5 100644 --- a/docs/frontier-readiness/factory-vs-zeta-separation-audit.md +++ b/docs/frontier-readiness/factory-vs-zeta-separation-audit.md @@ -765,6 +765,7 @@ term entries (IVM, DBSP, Z-set, retraction, Spine, etc.) are Zeta-library-specific content. **File location post-split:** Frontier (format + preamble + + the-rule-for-this-file + "spec has two meanings" framing pattern); Zeta retains specific term entries. @@ -887,6 +888,7 @@ Effort: **S**. Total: 5 + 6 + 4 = **15** top-level files audited out of ~16. Remaining: the `.claude/skills/**` + `.claude/agents/**` + + `openspec/**` + `tools/**` + `.github/**` directory-level surfaces (each a multi-file audit). From c625982449607b781ca86b0958a515381a7a232f Mon Sep 17 00:00:00 2001 From: Aaron Stainback Date: Fri, 24 Apr 2026 15:52:33 -0400 Subject: [PATCH 5/9] drain: resolve 2 threads on #190 (fix + backlog per Otto-236) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit - Thread P0 line 561 (markdownlint continuation-starting-with-+): reworded both occurrences (lines 561 and 684) so wrapped continuation lines no longer begin with `+` — replaced with `plus` / `and` / comma-series per Copilot reviewer's suggestion. - Thread P2 line 678 (unaudited docs in pattern-summary): added explanatory note under the summary table clarifying that three audits (ALIGNMENT / TECH-RADAR / FACTORY-HYGIENE) land in sibling PRs #185/#188 rather than this file, and flagged that the rollup assumes those PRs merge. Deeper mechanical-verification restructure backlogged as P2 "Separation-audit cross-PR rollup". Co-Authored-By: Claude Opus 4.7 --- docs/BACKLOG.md | 2 ++ .../factory-vs-zeta-separation-audit.md | 17 +++++++++++------ 2 files changed, 13 insertions(+), 6 deletions(-) diff --git a/docs/BACKLOG.md b/docs/BACKLOG.md index 10dbf4c2..c91b7f64 100644 --- a/docs/BACKLOG.md +++ b/docs/BACKLOG.md @@ -5376,6 +5376,8 @@ systems. This track claims the space. ## P2 — research-grade +- [ ] **Separation-audit cross-PR rollup — mechanically verify pattern-summary counts against in-file `## Audit — ...` sections.** Codex reviewer Otto (2026-04-24) on PR #190: the file `docs/frontier-readiness/factory-vs-zeta-separation-audit.md` pattern-summary table lists ALIGNMENT / FACTORY-HYGIENE / TECH-RADAR as completed classifications (total 15), but those `## Audit — ...` sections live in sibling PRs #185 / #188 (still open), not in the file itself. This PR shipped a narrow-fix note clarifying the cross-PR tracking, but the underlying discipline question remains: "completed" audits counted in a file's summary should be mechanically verifiable from that file's own contents. Options: (a) wait for #185 + #188 to merge and the summary becomes self-consistent; (b) restructure so each audit-PR lands its own summary row once, not retroactively; (c) add a tooling check that diffs pattern-summary claims against `grep '^## Audit — '`. Priority P2 research-grade; effort S (tooling) or zero-effort (wait). Composes with glass-halo transparency + audit-as-source-of-truth principle. + - [ ] **KSK naming definition doc — `docs/definitions/KSK.md` leading with canonical expansion `KSK = Kinetic Safeguard Kernel`.** **Authority: Aaron Otto-140 rewrite approved; Max attribution preserved as initial-starting-point contributor (Otto-77).** Amara 2026-04-24 (16th courier ferry, GPT-5.5 Thinking) flagged the naming ambiguity: *"'KSK' has multiple possible meanings: DNSSEC-style Key Signing Key, your emerging Kinetic Safeguard Kernel / trust-anchor idea, maybe broader 'ceremony + root-of-trust + governance key' structure."* Aaron Otto-142..145 (self-correcting Otto-141 typo "SDK") canonicalized: *"kinetic safeguare Kernel, i did the wrong name / it is what amara said / kinetic safeguard kernel"* — matches Amara's 5th and 16th ferry phrasing. Doc scope: (1) lead sentence *"KSK = Kinetic Safeguard Kernel. 'Kernel' here is safety-kernel / security-kernel sense (Anderson 1972, Saltzer-Schroeder reference-monitor, aviation safety-kernel) — a small trusted enforcement core, **NOT OS-kernel-mode** (not ring 0, not Linux/Windows kernel)"*; (2) "Inspired by..." DNSSEC KSK / DNSCrypt / threshold-sig ceremonies / security-kernel lineage; (3) "NOT identical to..." OS kernel, DNSSEC KSK (signs zone keys); (4) cross-refs to 5 ferries elaborating architecture; (5) Max attribution: *"Initial starting point committed by Max under Aaron's direction in LFG/lucent-ksk; substrate is Aaron+Amara's concept, completely rewritable."* (Otto-140 lifted the Max-coordination gate; Otto-77 attribution stands.) Priority P2 research-grade (elevated from P3); effort S (doc) — coordination overhead removed. Composes with Amara 17th-ferry correction #7 (now resolved), Otto-77 Max attribution, Otto-90 Aaron+Max-not-gates, Otto-140..145 Aaron canonical expansion + gate-lift, Otto-108 single-team-until-interfaces-harden. - [ ] **.NET 10 Server GC crash on Apple Silicon — bullet-proof investigation + upstream report (Otto-248 workaround follow-up).** Shipped mitigation in PR #376 (`DOTNET_gcServer=0` on Apple Silicon Darwin via `tools/setup/common/shellenv.sh`) is a WORKAROUND, not a root-cause fix. Three SIGSEGV crashes captured 2026-04-24 at `~/Library/Logs/DiagnosticReports/dotnet-2026-04-24-*.ips` — all in `libcoreclr.dylib` Server GC (`SVR::gc_heap::{plan_phase, background_mark_simple1, find_first_object, revisit_written_page}`) with `EXC_BAD_ACCESS / KERN_INVALID_ADDRESS / "possible pointer authentication failure"` on macOS 26.4.1 MacBook M2 + .NET SDK 10.0.203 (latest). Current hypothesis: concurrent-mark-phase invariant violation, possibly write-barrier or card-table race; Apple Silicon ARM64 PAC surfaces it as SIGSEGV where x86 would silently corrupt. Two known related upstream fixes on dotnet/runtime `main` but NOT yet in release/10.0: `#126389` (Jan Vorlicek, 2026-04-01, BGC mark phase wrong-join — fixes *hangs* not crashes; symptom mismatch) and `#126929/#126977` (largepages corruption fix — open port-to-10.0 PR). Per maintainer directive 2026-04-24 Otto-254 ("roll forward, not backward" + escro absorb-and-contribute dependency-maintenance per `project_escro_maintain_every_dependency_microkernel_os_endpoint_grow_our_way_there_2026_04_22.md`). Work scope: (1) build minimal deterministic repro — F# allocation-heavy Server GC program that reliably crashes on Apple Silicon, clean under Workstation GC; (2) measure crash rate across Apple-Silicon-Darwin vs ubuntu-24.04-arm vs x86 legs (differentiates Scenario A Apple-specific vs Scenario B ARM64-general); (3) read coreclr GC source at crash symbols (now split across `plan_phase.cpp`, `background.cpp`, `mark_phase.cpp` per 2026-Q1 refactor; sparse-checkout sibling `../runtime` already pulled for offline navigation); (4) file upstream `dotnet/runtime` issue with IPS files + reproducer IF deterministic + professional (not a dick per maintainer directive); (5) track upstream fix; (6) remove `DOTNET_gcServer=0` workaround once fix lands in a release/10.0 SDK patch. Priority P2 research-grade — workaround prevents daily blocker but the fix is escro-scope dependency maintenance. Effort M (repro + source read) + S (upstream file) + S (patch-landed cleanup). **Does NOT authorize:** reverting the workaround before upstream fix lands; filing upstream before reproducer is deterministic. diff --git a/docs/frontier-readiness/factory-vs-zeta-separation-audit.md b/docs/frontier-readiness/factory-vs-zeta-separation-audit.md index f6bd06a5..fa9c9316 100644 --- a/docs/frontier-readiness/factory-vs-zeta-separation-audit.md +++ b/docs/frontier-readiness/factory-vs-zeta-separation-audit.md @@ -765,9 +765,8 @@ term entries (IVM, DBSP, Z-set, retraction, Spine, etc.) are Zeta-library-specific content. **File location post-split:** Frontier (format + preamble - -+ the-rule-for-this-file + "spec has two meanings" framing -pattern); Zeta retains specific term entries. +plus the-rule-for-this-file and "spec has two meanings" +framing pattern); Zeta retains specific term entries. **Length:** approximately 840 lines. Large vocabulary. @@ -887,11 +886,17 @@ Effort: **S**. | zeta-library-specific | 4 | ROUND-HISTORY, BACKLOG, ROADMAP, VISION | Total: 5 + 6 + 4 = **15** top-level files audited out of -~16. Remaining: the `.claude/skills/**` + `.claude/agents/**` - -+ `openspec/**` + `tools/**` + `.github/**` directory-level +~16. Remaining: the `.claude/skills/**`, `.claude/agents/**`, +`openspec/**`, `tools/**`, and `.github/**` directory-level surfaces (each a multi-file audit). +**Note on cross-PR audits:** Three of the 15 audits (ALIGNMENT, +TECH-RADAR, FACTORY-HYGIENE) land in sibling PRs (#185, #188) +rather than this file; tracking is via the "Files audited" +list above (line-item pointers to each PR). The classification +counts in this summary assume those PRs merge; if they close +without merging, this summary should be refreshed. + ## How this audit connects to the multi-repo split Gap #5 (this audit) is load-bearing for gap #1 (multi-repo From cb6c0f5ac0eaaa97fa8f77afe13aa176bf881090 Mon Sep 17 00:00:00 2001 From: Aaron Stainback Date: Fri, 24 Apr 2026 16:03:14 -0400 Subject: [PATCH 6/9] drain: resolve 2 post-rebase threads on #190 Fixes (narrow) for both Copilot P1 at line 68 (dedicated bullets for cross-PR audits) and Codex P2 at line 770 (honest 13-of-15 in-file count + mechanical-verification deficit flag pointing at existing BACKLOG row). Co-Authored-By: Claude Opus 4.7 --- .../factory-vs-zeta-separation-audit.md | 31 ++++++++++++++----- 1 file changed, 24 insertions(+), 7 deletions(-) diff --git a/docs/frontier-readiness/factory-vs-zeta-separation-audit.md b/docs/frontier-readiness/factory-vs-zeta-separation-audit.md index fa9c9316..176f2809 100644 --- a/docs/frontier-readiness/factory-vs-zeta-separation-audit.md +++ b/docs/frontier-readiness/factory-vs-zeta-separation-audit.md @@ -67,7 +67,11 @@ For each audited file: - **docs/ROUND-HISTORY.md** (below, Otto-18 fire) - **docs/BACKLOG.md** (below, Otto-18 fire) - **docs/ROADMAP.md** (below, Otto-18 fire) -- **docs/VISION.md** (below, Otto-18 fire) — also GOVERNANCE.md on PR #181, AGENT-BEST-PRACTICES.md on PR #184, ALIGNMENT.md on PR #185, TECH-RADAR.md + FACTORY-HYGIENE.md on PR #188 +- **docs/VISION.md** (below, Otto-18 fire) +- **docs/TECH-RADAR.md** — audited on sibling PR #188 (classification recorded there; no `## Audit —` section in this file pending that merge) +- **docs/FACTORY-HYGIENE.md** — audited on sibling PR #188 (classification recorded there; no `## Audit —` section in this file pending that merge) + +Cross-PR audits that duplicate in-file coverage: GOVERNANCE (also on PR #181), AGENT-BEST-PRACTICES (also on PR #184), ALIGNMENT (also on PR #185) — the in-file `## Audit —` sections for these three are the authoritative classification; the sibling PRs are redundant or superseded. ### Files to audit (not yet classified; add rows as they land) @@ -890,12 +894,25 @@ Total: 5 + 6 + 4 = **15** top-level files audited out of `openspec/**`, `tools/**`, and `.github/**` directory-level surfaces (each a multi-file audit). -**Note on cross-PR audits:** Three of the 15 audits (ALIGNMENT, -TECH-RADAR, FACTORY-HYGIENE) land in sibling PRs (#185, #188) -rather than this file; tracking is via the "Files audited" -list above (line-item pointers to each PR). The classification -counts in this summary assume those PRs merge; if they close -without merging, this summary should be refreshed. +**Note on cross-PR audits:** 13 of the 15 audits have +dedicated `## Audit —` sections in this file; 2 (TECH-RADAR, +FACTORY-HYGIENE) land only in sibling PR #188 with no +section in this file yet. The pattern-summary counts above +assume that sibling PR merges; if #188 closes without +merging, this summary should be refreshed (count drops to +13 audits: 4 factory-generic, 5 both-coupled, 4 +zeta-library-specific). + +Mechanical-verification deficit flagged: a reader cannot +`grep '^## Audit —'` this file and reproduce the 15-count +— only 13. The deeper "each file-level summary should be +mechanically consistent with its own in-file sections" +discipline is tracked in `docs/BACKLOG.md` row +*"Separation-audit cross-PR rollup — mechanically verify +pattern-summary counts against in-file `## Audit — ...` +sections"* (P2 research-grade; three options: wait for +#188 to merge, per-PR summary-row landings, or tooling diff +check). ## How this audit connects to the multi-repo split From a3db4d5e1efa7674c991cd77a589365473fe8fe4 Mon Sep 17 00:00:00 2001 From: Aaron Stainback Date: Fri, 24 Apr 2026 16:08:32 -0400 Subject: [PATCH 7/9] rebase-cleanup: remove stale 'audit pending sibling PR' notes after #188 merge MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit After rebasing onto origin/main (which carries PR #188's TECH-RADAR + FACTORY-HYGIENE audits in this file), two PR-side breadcrumb rows that said 'audited on sibling PR #188 ... no Audit section pending that merge' are factually wrong — the merge has happened; the Audit sections exist. Fold the cross-PR note accordingly. Otto-254 roll-forward; no content re-litigated. --- docs/frontier-readiness/factory-vs-zeta-separation-audit.md | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/docs/frontier-readiness/factory-vs-zeta-separation-audit.md b/docs/frontier-readiness/factory-vs-zeta-separation-audit.md index 176f2809..d0e211aa 100644 --- a/docs/frontier-readiness/factory-vs-zeta-separation-audit.md +++ b/docs/frontier-readiness/factory-vs-zeta-separation-audit.md @@ -67,11 +67,9 @@ For each audited file: - **docs/ROUND-HISTORY.md** (below, Otto-18 fire) - **docs/BACKLOG.md** (below, Otto-18 fire) - **docs/ROADMAP.md** (below, Otto-18 fire) -- **docs/VISION.md** (below, Otto-18 fire) -- **docs/TECH-RADAR.md** — audited on sibling PR #188 (classification recorded there; no `## Audit —` section in this file pending that merge) -- **docs/FACTORY-HYGIENE.md** — audited on sibling PR #188 (classification recorded there; no `## Audit —` section in this file pending that merge) +- **docs/VISION.md** (below, Otto-18 fire) — also GOVERNANCE.md on PR #181, AGENT-BEST-PRACTICES.md on PR #184, ALIGNMENT.md on PR #185, TECH-RADAR.md + FACTORY-HYGIENE.md on PR #188 -Cross-PR audits that duplicate in-file coverage: GOVERNANCE (also on PR #181), AGENT-BEST-PRACTICES (also on PR #184), ALIGNMENT (also on PR #185) — the in-file `## Audit —` sections for these three are the authoritative classification; the sibling PRs are redundant or superseded. +Cross-PR audits that duplicate in-file coverage: GOVERNANCE (also on PR #181), AGENT-BEST-PRACTICES (also on PR #184), ALIGNMENT (also on PR #185), TECH-RADAR + FACTORY-HYGIENE (PR #188, now merged and recorded in-file) — the in-file `## Audit —` sections are the authoritative classification. ### Files to audit (not yet classified; add rows as they land) From ad619889ccadab6dc3de5de5e20ed3190d367c48 Mon Sep 17 00:00:00 2001 From: Aaron Stainback Date: Fri, 24 Apr 2026 16:13:02 -0400 Subject: [PATCH 8/9] fix: markdownlint MD018 on wrapped #188 (backtick-wrap per Otto-260) Post-rebase #188-reference sat at wrapped-line-start. Backtick-wrap per Otto-260 (preserve canonical form; reflow/wrap, never rename). Co-Authored-By: Claude Opus 4.7 --- docs/frontier-readiness/factory-vs-zeta-separation-audit.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/frontier-readiness/factory-vs-zeta-separation-audit.md b/docs/frontier-readiness/factory-vs-zeta-separation-audit.md index d0e211aa..29723ce7 100644 --- a/docs/frontier-readiness/factory-vs-zeta-separation-audit.md +++ b/docs/frontier-readiness/factory-vs-zeta-separation-audit.md @@ -909,7 +909,7 @@ discipline is tracked in `docs/BACKLOG.md` row *"Separation-audit cross-PR rollup — mechanically verify pattern-summary counts against in-file `## Audit — ...` sections"* (P2 research-grade; three options: wait for -#188 to merge, per-PR summary-row landings, or tooling diff +`#188` to merge, per-PR summary-row landings, or tooling diff check). ## How this audit connects to the multi-repo split From b4afb2907fa9a07c0d00f085978fc7b7cf5e5284 Mon Sep 17 00:00:00 2001 From: Aaron Stainback Date: Fri, 24 Apr 2026 18:19:53 -0400 Subject: [PATCH 9/9] drain: resolve 4 threads on #190 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Pattern-summary classification: ALIGNMENT moved from factory-generic to both (coupled) to match its in-file `## Audit —` section (codex P2 line 886). Counts updated: 4 factory-generic + 7 both-coupled + 4 zeta-library-specific = 15. Cross-PR note (line 895+) refreshed: PR #188 has merged, so all 15 audits now have dedicated `## Audit —` sections in this file; the wait-for-merge option has resolved itself. A reader can `grep '^## Audit —'` and reproduce the 15-count directly (copilot P1 line 72 inconsistency cleared). BACKLOG row at line 5379 updated: removed stale "live in sibling PRs #185 / #188 (still open)" premise (copilot P1 + codex P2). Row now scopes to the residual concern (option c tooling / CI diff check) since options (a) and (b) have resolved naturally for the first 15 audits. Co-Authored-By: Claude Opus 4.7 --- docs/BACKLOG.md | 2 +- .../factory-vs-zeta-separation-audit.md | 33 ++++++++----------- 2 files changed, 15 insertions(+), 20 deletions(-) diff --git a/docs/BACKLOG.md b/docs/BACKLOG.md index c91b7f64..73955073 100644 --- a/docs/BACKLOG.md +++ b/docs/BACKLOG.md @@ -5376,7 +5376,7 @@ systems. This track claims the space. ## P2 — research-grade -- [ ] **Separation-audit cross-PR rollup — mechanically verify pattern-summary counts against in-file `## Audit — ...` sections.** Codex reviewer Otto (2026-04-24) on PR #190: the file `docs/frontier-readiness/factory-vs-zeta-separation-audit.md` pattern-summary table lists ALIGNMENT / FACTORY-HYGIENE / TECH-RADAR as completed classifications (total 15), but those `## Audit — ...` sections live in sibling PRs #185 / #188 (still open), not in the file itself. This PR shipped a narrow-fix note clarifying the cross-PR tracking, but the underlying discipline question remains: "completed" audits counted in a file's summary should be mechanically verifiable from that file's own contents. Options: (a) wait for #185 + #188 to merge and the summary becomes self-consistent; (b) restructure so each audit-PR lands its own summary row once, not retroactively; (c) add a tooling check that diffs pattern-summary claims against `grep '^## Audit — '`. Priority P2 research-grade; effort S (tooling) or zero-effort (wait). Composes with glass-halo transparency + audit-as-source-of-truth principle. +- [ ] **Separation-audit cross-PR rollup — automate `## Audit — ...` count verification.** Codex reviewer Otto (2026-04-24) on PR #190 originally flagged that the pattern-summary table in `docs/frontier-readiness/factory-vs-zeta-separation-audit.md` listed ALIGNMENT / FACTORY-HYGIENE / TECH-RADAR as completed classifications even though those sections then lived only in sibling PRs (#185 + #188). PR #188 has since merged, ALIGNMENT classification was corrected from `factory-generic` to `both (coupled)` to match the in-file audit section, and all 15 audits now have dedicated `## Audit —` sections (verifiable via `grep '^## Audit — '`). The residual discipline question — "completed" audits counted in a file's summary should be mechanically reproducible from that file's own contents — remains for the **future**: as new audits land via separate PRs, the same drift can recur. Remaining option: (c) add a tooling / CI check that diffs pattern-summary claims against `grep '^## Audit — '`. Options (a) wait-for-merge and (b) per-PR summary-row landings have resolved naturally for the first 15 audits. Priority P2 research-grade; effort S (tooling). Composes with glass-halo transparency + audit-as-source-of-truth principle. - [ ] **KSK naming definition doc — `docs/definitions/KSK.md` leading with canonical expansion `KSK = Kinetic Safeguard Kernel`.** **Authority: Aaron Otto-140 rewrite approved; Max attribution preserved as initial-starting-point contributor (Otto-77).** Amara 2026-04-24 (16th courier ferry, GPT-5.5 Thinking) flagged the naming ambiguity: *"'KSK' has multiple possible meanings: DNSSEC-style Key Signing Key, your emerging Kinetic Safeguard Kernel / trust-anchor idea, maybe broader 'ceremony + root-of-trust + governance key' structure."* Aaron Otto-142..145 (self-correcting Otto-141 typo "SDK") canonicalized: *"kinetic safeguare Kernel, i did the wrong name / it is what amara said / kinetic safeguard kernel"* — matches Amara's 5th and 16th ferry phrasing. Doc scope: (1) lead sentence *"KSK = Kinetic Safeguard Kernel. 'Kernel' here is safety-kernel / security-kernel sense (Anderson 1972, Saltzer-Schroeder reference-monitor, aviation safety-kernel) — a small trusted enforcement core, **NOT OS-kernel-mode** (not ring 0, not Linux/Windows kernel)"*; (2) "Inspired by..." DNSSEC KSK / DNSCrypt / threshold-sig ceremonies / security-kernel lineage; (3) "NOT identical to..." OS kernel, DNSSEC KSK (signs zone keys); (4) cross-refs to 5 ferries elaborating architecture; (5) Max attribution: *"Initial starting point committed by Max under Aaron's direction in LFG/lucent-ksk; substrate is Aaron+Amara's concept, completely rewritable."* (Otto-140 lifted the Max-coordination gate; Otto-77 attribution stands.) Priority P2 research-grade (elevated from P3); effort S (doc) — coordination overhead removed. Composes with Amara 17th-ferry correction #7 (now resolved), Otto-77 Max attribution, Otto-90 Aaron+Max-not-gates, Otto-140..145 Aaron canonical expansion + gate-lift, Otto-108 single-team-until-interfaces-harden. diff --git a/docs/frontier-readiness/factory-vs-zeta-separation-audit.md b/docs/frontier-readiness/factory-vs-zeta-separation-audit.md index 29723ce7..1eec75d7 100644 --- a/docs/frontier-readiness/factory-vs-zeta-separation-audit.md +++ b/docs/frontier-readiness/factory-vs-zeta-separation-audit.md @@ -883,34 +883,29 @@ Effort: **S**. | Class | Count | Files | |---|---|---| -| factory-generic | 5 | GOVERNANCE, AGENT-BEST-PRACTICES, ALIGNMENT, AUTONOMOUS-LOOP, FACTORY-HYGIENE | -| both (coupled) | 6 | CLAUDE, AGENTS, CONFLICT-RESOLUTION, WONT-DO, TECH-RADAR, GLOSSARY | +| factory-generic | 4 | GOVERNANCE, AGENT-BEST-PRACTICES, AUTONOMOUS-LOOP, FACTORY-HYGIENE | +| both (coupled) | 7 | CLAUDE, AGENTS, CONFLICT-RESOLUTION, WONT-DO, TECH-RADAR, GLOSSARY, ALIGNMENT | | zeta-library-specific | 4 | ROUND-HISTORY, BACKLOG, ROADMAP, VISION | -Total: 5 + 6 + 4 = **15** top-level files audited out of +Total: 4 + 7 + 4 = **15** top-level files audited out of ~16. Remaining: the `.claude/skills/**`, `.claude/agents/**`, `openspec/**`, `tools/**`, and `.github/**` directory-level surfaces (each a multi-file audit). -**Note on cross-PR audits:** 13 of the 15 audits have -dedicated `## Audit —` sections in this file; 2 (TECH-RADAR, -FACTORY-HYGIENE) land only in sibling PR #188 with no -section in this file yet. The pattern-summary counts above -assume that sibling PR merges; if #188 closes without -merging, this summary should be refreshed (count drops to -13 audits: 4 factory-generic, 5 both-coupled, 4 -zeta-library-specific). - -Mechanical-verification deficit flagged: a reader cannot -`grep '^## Audit —'` this file and reproduce the 15-count -— only 13. The deeper "each file-level summary should be -mechanically consistent with its own in-file sections" +**Mechanical-verification status:** all 15 audits now have +dedicated `## Audit —` sections in this file (TECH-RADAR + +FACTORY-HYGIENE merged in via PR #188; ALIGNMENT in-file is +authoritative per its own `## Audit —` section above which +classifies it as **both (coupled)**, not factory-generic). A +reader can `grep '^## Audit —'` this file and reproduce the +15-count directly. The deeper "each file-level summary should +be mechanically consistent with its own in-file sections" discipline is tracked in `docs/BACKLOG.md` row *"Separation-audit cross-PR rollup — mechanically verify pattern-summary counts against in-file `## Audit — ...` -sections"* (P2 research-grade; three options: wait for -`#188` to merge, per-PR summary-row landings, or tooling diff -check). +sections"* — the residual concern is now tooling (option c: +automated diff check), since the wait-for-merge option (a) +has resolved itself. ## How this audit connects to the multi-repo split