docs(archive): Lior preserves PR #4646

.cursor/bin/riven-loop-tick.ts

@@ -208,8 +208,17 @@ function heartbeat(): void {
                 const gate = run("agent", [
                     "chat",
                     "--mode", "ask",
-                    "--model", "grok-4-20",
-                    `Twin-flame heartbeat gate (Riven adversarial-truth-axis). Read git status, recent commits, open PRs, claim branches. Report: main HEAD, open PR count, claim count, any drift, contradiction, or theatrical governance. Adversarial register — call out what's wrong, not what's fine. Brief.`,
+                    "--model", "grok-4.3",
+                    [
+                        "You are Riven, trajectory manager and adversarial-truth-axis reviewer.",
+                        "This is an autonomous 15-minute cycle.",
+                        "Read broadcasts first from ~/.local/share/zeta-broadcasts/{otto,vera,lior,riven}.md.",
+                        "Walk assigned trajectories. Decompose only what you hit mid-stride.",
+                        "Produce at least one concrete, actionable claim or small PR scope.",
+                        "When blocked, create a specific research child the next pickup cannot dodge.",
+                        "Write your status to ~/.local/share/zeta-broadcasts/riven.md at the end.",
+                        "GitHub PR state and actual file contents are authoritative.",
+                    ].join(" "),
                 ], agentTimeoutMs);
 
                 agentStatus = gate.status === 0 ? "ok" : `exit-${gate.status}`;

docs/pr-discussions/PR-4646-backlog-agenda-b-0688-zeta-agenda-intersystems-cach-external.md

@@ -0,0 +1,85 @@
+---
+pr_number: 4646
+title: "backlog+agenda: B-0688 + Zeta AGENDA \u2014 InterSystems Cach\u00e9 external-reference-anchor + maji-math foundation"
+author: "AceHack"
+state: "MERGED"
+created_at: "2026-05-22T17:59:40Z"
+merged_at: "2026-05-22T18:33:04Z"
+closed_at: "2026-05-22T18:33:04Z"
+head_ref: "otto/cli-2236z-zeta-db-as-fsharp-compiler-distributed-intelligence-maji-math-cache-fresh-medical-database-intersystems-cache-reference-anchor-2026-05-22"
+base_ref: "main"
+archived_at: "2026-05-22T19:54:02Z"
+archive_tool: "tools/pr-preservation/archive-pr.ts"
+---
+
+# PR #4646: backlog+agenda: B-0688 + Zeta AGENDA — InterSystems Caché external-reference-anchor + maji-math foundation
+
+## PR description
+
+Operator save instruction 2026-05-22: maji-math (rx-tension-as-semantic-indexes; mirror-tier; not beacon-tier) as foundation; Zeta-db-as-F#-compiler-as-distributed-intelligence-database building toward beacon-tier via B-0688 + B-0687; closest commercial substrate analog is InterSystems Caché (powers Epic EHR + most US hospital electronic health records). The Caché reference IS the deliberate-writing-pass anchor for mirror-to-beacon translation; survives year-out test for healthcare-IT / enterprise-database / mission-critical-systems audiences. Updates B-0688 (full Caché mapping) + Zeta AGENDA.md (reference anchor + sovereignty-path 3rd piece composition).
+
+Co-Authored-By: Claude <noreply@anthropic.com>
+
+## Reviews
+
+### COMMENTED — @chatgpt-codex-connector (2026-05-22T18:01:25Z)
+
+
+### 💡 Codex Review
+
+Here are some automated review suggestions for this pull request.
+
+**Reviewed commit:** `c18df7a13d`
+
+
+<details> <summary>ℹ️ About Codex in GitHub</summary>
+<br/>
+
+[Your team has set up Codex to review pull requests in this repo](https://chatgpt.com/codex/cloud/settings/general). Reviews are triggered when you
+- Open a pull request for review
+- Mark a draft as ready
+- Comment "@codex review".
+
+If Codex has suggestions, it will comment; otherwise it will react with 👍.
+
+
+Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
+
+</details>
+
+### COMMENTED — @copilot-pull-request-reviewer (2026-05-22T18:01:54Z)
+
+## Pull request overview
+
+Adds an explicit external-reference anchor (InterSystems Caché) to ground B-0688 and the Zeta agenda narrative, positioning it as the closest commercial analog for “incremental compiler database” substrate work and as the mirror→beacon translation handle.
+
+**Changes:**
+- Extends backlog row B-0688 with a Caché-based external reference anchor and a property-to-property mapping table.
+- Updates `docs/agendas/zeta/AGENDA.md` to include Caché as the agenda-level reference anchor and tie-in to the maji-math foundation.
+
+### Reviewed changes
+
+Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
+
+| File | Description |
+| ---- | ----------- |
+| docs/backlog/P2/B-0688-zeta-incremental-compiler-host-dbsp-zsets-rx-meta-ast-tags-seeded-deterministic-simulation-amara-aaron-2026-05-21.md | Adds a Caché external-reference anchor section + mapping table for B-0688 substrate positioning. |
+| docs/agendas/zeta/AGENDA.md | Adds agenda-level Caché anchor tying B-0688/B-0687 to the mirror→beacon translation framing. |
+
+## Review threads
+
+### Thread 1: docs/backlog/P2/B-0688-zeta-incremental-compiler-host-dbsp-zsets-rx-meta-ast-tags-seeded-deterministic-simulation-amara-aaron-2026-05-21.md:227 (resolved)
+
+**@chatgpt-codex-connector** (2026-05-22T18:01:25Z):
+
+**<sub><sub>![P2 Badge](https://img.shields.io/badge/P2-yellow?style=flat)</sub></sub>  Correct Caché market-position statement**
+
+The sentence claims Caché currently powers Epic and “most US hospital electronic health records,” but that overstates the present-day landscape and makes the external-reference anchor factually brittle for readers using this document to reason about architecture. Epic has moved newer generations to InterSystems IRIS, and U.S. hospital EHR share is split across multiple vendors, so this should be qualified (for example as historical lineage with a date/scope) or backed by a precise source and timeframe.
+
+Useful? React with 👍 / 👎.
+
+### Thread 2: docs/backlog/P2/B-0688-zeta-incremental-compiler-host-dbsp-zsets-rx-meta-ast-tags-seeded-deterministic-simulation-amara-aaron-2026-05-21.md:227 (resolved)
+
+**@copilot-pull-request-reviewer** (2026-05-22T18:01:53Z):
+
+P1 (codebase convention): This edit adds substantial content but the YAML frontmatter `last_updated` field still shows `2026-05-21`. Per `tools/backlog/README.md` (`last_updated` is required and must be updated on every content edit), this row should bump `last_updated` to the edit date (e.g., 2026-05-22).