implementlisted

# implement A deterministic gate decides done — a test, a linter or a compiler exit code, never a self-assessment and never a judge model. Cheap `worker`-class subagents do the volume; this thread takes over when they stall. The full invariant is `references/gate-pattern.md`; the worker substrate (bridge, ids, launch) is `WORKERS.md`. ## Pick the mode by what you were handed One axis — the input — because it decides everything else. One story has one gate; a goal must be split before anything can be gated; a plan already carries the split. "Keep going until it is green" is not a mode, it is what the machine does as soon as there is more than one story. | you have | invoke | what runs | |---|---|---| | one acceptance criterion + a gate command | `--from task` *(default)* | **Part A**, once | | a goal too big for one gate | `--from goal` | **Part B**: decompose, then Part A per story | | a plan produced by `plan` | `--from plan` | Part B, with the split taken from the plan | | either multi-story form | `+ --parallel` | disjoint stories concurrently | `--parallel` is a modifier, not a value on the axis: it means nothing until there is more than one story, and it never changes what a gate is or when the frontier steps in. > **Who may run which.** `--from task` is the only cell a worker may drive — Part A needs > nothing beyond one subagent spawn and a shell. Every multi-story form fans out through > `Workflow` or several concurrent spawns, and a worker is denied both uncond