Xen Fleet · M4 ARM · 2026-06-11

XQL Control Plane

Genesis↔Leviticus Bridge — every input now hits all three faculties, guaranteed.
LIVE — all directives shipped + verified
%2 Genesis · voice · intelligently narrates, never executes (role-locked)
%3 Exodus · hands · Opus 4.8 + ultracode · silent execution
%4 Leviticus · quick · narration formatter
route: qi 9983 → xen 9934 → poller → FANOUT_3OF3 ✓✓✓ → %2 %3 %4

🛰 Fan-out all inputs → all 3

✓
SMS path — poller restarted on patched code; e2e FANOUT_3OF3 ✓✓✓ ALL 3 PANES, retry:0 dead:0
✓
Router path — %1 REPL restarted in-place; typed line → sent to: %2 %3 %4
✓
Busy-pane retry queue — a busy agent is queued + retried, never silently dropped

🧭 Single source of truth xql control plane

✓
One authority — xen-resolve-pane sole writer of canonical per-role sentinels
✓
Resolve-fresh — router resolves live before every fan-out; no stale panes
✓
Alias collision killed — secondary no longer means genesis & exodus at once

🔗 A2A bus keep each other accountable

✓
xen-a2a — send · inbox · commit · board · done · nudge · log (sqlite ledger)
✓
Durable + nudge — store is truth; dropped pane-inject still safe in inbox
✓
Agents adopting — Exodus sent exodus→leviticus: confirmed on its own

🛡 Canon & roles fixed mid-flight

✓
E1 — dead hook — xen-posttool-canon.py syntax error had killed ALL canon enforcement since 13:54; restored
✓
E2 — role-guard — Genesis can no longer execute via xen-computer-use; pattern-blocked
✓
Exodus mode — confirmed Opus 4.8 + ultracode; no "max" mode exists (doc mislabel fixed)

Root cause, in one line

Three subsystems independently guessed pane IDs from differently-named dotfiles — one of which assigned secondary to mean genesis and exodus at the same time. The de-dup logic then silently ate the third pane. One authoritative writer + canonical names killed the entire bug class.