Glossary
The vocabulary this section uses, defined once.
Backend — a specific agent tool a seat drives: Claude Code, Codex, or a local model
behind an OpenAI-compatible lane.
Board — the persisted, exportable account of the fleet's work: events and gate history.
Bridge — a project's command deck: orders, decisions, board, conventions — the durable
documents the fleet works from.
Cap — the hard per-run spending limit, derived as 2× the quote; the run stops there.
Channel files — the gitignored per-worktree wire between roles: _MASTER_ORDER.md
(master → executor, with a mandatory REASON), _EXEC_STATUS.md (executor → master:
started-ack, blocked-on, and the stop-2-ready close gate), _REVIEW_STATUS.md (the review
role's one file).
CLOSE-OK — the executor's close signal: one line carrying the return's identity
(stream, commit, branch, worktree), valid only with the persisted status file behind it.
Executor — the agent implementing one stream's scope inside its own worktree.
Gate — one recorded human decision on one stream; the only way a stream advances past a
decision point.
Headroom — the pre-dispatch capacity probe: where the fleet has room for one more run
of a given model. A report, never a dispatch.
Lane — a named model endpoint in configuration: URL plus the name of its credential
variable.
Mailbox — the insert-only channel for owner directives to running work; the daemon
delivers, the mailbox never dispatches.
Master — the planning and coordination role: writes dispatch material, owns worktree
lifecycle, adjudicates returns; never implements, never merges.
Order — the written specification a stream runs against: scope, confinement,
collisions, test plan, DoD, budget, assumptions.
Projection — any view computed from the record (CLI, dashboard, VS Code tree, export,
MCP). Never a source of state.
Quote — the expected per-run cost, recorded at dispatch so drift is measurable.
Record — the durable account of everything that happened: gates, runs, costs, refusals,
observed git facts. The single source every projection reads.
Review — the independent evaluation of an executor's return; a recommendation, recorded
as judgment, never the decision itself.
Seat — a named executor identity on one machine slot, with its own isolated agent
profile.
STOP-1 / STOP-2 — the two structured stops in a stream's life: the plan (before
implementation) and the proof (after it), each gated by a human.
Stream — the unit of work: one scoped task, one branch, one worktree, one lifecycle.
Teardown — the recorded act of closing a merged stream's workspace, with every return
artifact's fate dispositioned.
Wave — a set of related streams viewed together: branch → base → gate → merge.