Every phase has a verification gate. You do not advance until the gate passes. This is not bureaucracy — it is discipline. The difference between a ship that launches and a ship that explodes is whether someone checked the seals.

Picard

v23.0: Every agent in the protocol has a persistent subagent definition with model tiering (Opus/Sonnet/Haiku) and tool restrictions. Dynamic dispatch (ADR-044) matches specialists to your code changes automatically.

THE GATE

The protocol is now governed by a stack of mechanically-enforced ADRs. Skipping the pre-scan is no longer an act of will — it is physically blocked at the runtime boundary.

ADR-048 — Silver Surfer pre-scan: Haiku selects the optimal roster before every gated command, based on the actual code changed in this session.
ADR-050 — Native Claude Code coexistence: /review alias for /engage, /security alias for /sentinel.
ADR-051 — Silver Surfer Gate hook: a PreToolUse hook on the Agent tool blocks any non-Surfer sub-agent launch until a roster has been recorded. Enforcement is mechanical, not prose-only.
ADR-060 — Gate state relocation: per-user state at $XDG_RUNTIME_DIR/voidforge-gate/ (Linux) or $HOME/.voidforge/gate/ (macOS), 0700. No more world-writable /tmp.
ADR-061 — npm rename to voidforge-build (the @voidforge org was unavailable). Bin name unchanged; post-install UX identical.

The gate fails closed on unknown bypass flags — passing anything other than --light or --solo exits 2 with an error. No silent bypass. (SEC-003 hardening.)

THE LONG MEMORY

Before Phase 0 begins, Wong loads two files: docs/LESSONS.md (cross-project patterns) and docs/LEARNINGS.md (project-scoped operational knowledge). LEARNINGS.md contains API quirks, decision rationale, and root causes discovered in prior sessions. Every agent starts informed — your next build begins where the last one left off.

LEARN MORE →

0