Back to corpus
technical notebacklog referencescore 22

Codex plan — what to do next, ranked

> **Topology correction, 2026-04-26:** Mac4 is the current Unity Editor / GUI smoke-test host and real-Femto capture host. Mac5 is still the synthpub LaunchAgent / synthetic fallback host. Do not blindly replace all Mac5 references; see `software/demo/TOPOLOGY-CORRECTION-2026-04-26.md`.

Open full HTMLDownload HTMLCorpus JSONPaper schema

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

> **Topology correction, 2026-04-26:** Mac4 is the current Unity Editor / GUI smoke-test host and real-Femto capture host. Mac5 is still the synthpub LaunchAgent / synthetic fallback host. Do not blindly replace all Mac5 references; see `software/demo/TOPOLOGY-CORRECTION-2026-04-26.md`. _Read `CODEX-CONTEXT.md` + `ARCHITECTURE.md` first. This file is the priority-ordered action list. Each item has: scope, success criteria, files to touch, things to avoid, and when to escalate to Mohamed._ 1. `CODEX-CONTEXT.md` — origin, evolution, decision log. 2. `unity/lume_pcloud/ARCHITECTURE.md` — current state mental model. 3. **This file (`CODEX-PLAN.md`)** — next actions. 4. `MAC5-CODEX-HANDOFF-2026-04-26.md` — bootstrap prompt with commit ledger + smoke-test commands. 5. `DUNCAN-GAP-ANALYSIS.md` — what's left to match Duncan's stack. 6. `Reference/Duncan/INDEX.md` — 83 reels + 69 analyses. - **22 commits** on `main`, no push, Mac1 source-of-truth. - **Mac5 sync deferred** — Tailscale 100% loss across multiple checks. - **10 Unity components** (5 base + 5 Wave 4-5 additions). - **37 pytest tests** passing (33 fast + 4 slow). - **Wave 5 score: 4 of 5 priorities shipped** (impulse, calibration, motion-gate, ARCHITECTURE.md). Remaining: fluid sim, marching cubes. If both fail: - Mac5 is physically off (cable / power) - Tailscale on Mac5 is dead — needs manual restart - Tailscale on Mac1 is dead — `tailscale status` will reveal

Promotion decision

What has to happen next

Keep in the searchable backlog until it intersects a live paper or system.

Why this is not always a full paper yet

Corpus pages are public-safe readers for discovered workspace artifacts. They are not automatically final papers. A corpus item becomes a polished paper only after the editable source, evidence checkpoints, references, figures, render path, and release status are attached through the paper schema.