ELP-2 — Survivor Architecture

# ELP-2 — Survivor Architecture > Crucible Stage 3 FORGE | cycle: chain:full-omega #2 | date: 2026-05-13 > Input layers: L1 meta-review (27 findings, NO-SHIP), L2 AMR (AMEND), L4 Evo3 (Hybrid wins) > Layer 3 (Codex adversarial): pending — see footnote at §15. Three of four scrutiny layers returned a convergent verdict: ELP-1 as written cannot ship. The CRITICAL findings are structural — a /inject format mismatch that breaks the primary dispatch path, a concurrent SKILL.md write race enabled by a 5-minute claim TTL, and a Syncthing-backed filesystem fallback that is architecturally described but physically unprovisioned. These are not tuning problems; they are root-cause failures. The verdict is not "abandon the loop." The four caveats ELP-1 was designed to kill are real. Claude Code session closure kills the current ScheduleWakeup loop. Stall detection is absent. A single driver is a single point of failure. These problems are worth solving. The verdict is: replace ELP-1's bespoke distributed worker system with a thin Pulse-backed hybrid that kills the same four caveats at roughly 40% of ELP-1's build cost, with no CRITICAL correctness bugs, and a clean upgrade path to full ELP-1 semantics when SOOP-3 demands it. 1. Read filesystem state, compute which of the 10 SOOP-2 criteria pass or fail. 2. Decide what batch of work to dispatch next (or whether Mohamed's approval is required first). 3. Dispatch via Pulse (for work that fits Pulse's session model) or inline (for trivial work). 4. Write the heartbeat file, append to the dispatch log, regenerate the dashboard. 5. Sleep and repeat.