Draft, open for argument

Journey

The road has stages, and each stage has a constraint that tends to show up first.

The level names follow Dan Shapiro’s five levels, from autocomplete to the dark factory. This page adds the question a team actually faces at each one: what is holding the line right now?

Stage What it looks like Constraint that usually appears Typical fix
0. By hand People type, autocomplete helps Typing and coding time Agentic coders, voice dictation
1. Agents on laptops Two or three agents per engineer, every action approved Approvals, laptop capacity Sandbox, auto-approve, remote servers
2. Parallel agents Eight sessions per engineer CI time, shared staging Cached CI, environment per agent
3. Agents verify Agents prove their work end to end Human attention, review queue Orchestrator, AI reviewers
4. Merge on evidence Most changes merge without a human reading them Merge conflicts, release cadence Merge queue, continuous deploy
5. Lights out Specs in, software out Deciding what to build Agent-drafted specs, engineers own outcomes

The order is typical, not fixed. A team with a 90-minute CI run meets that constraint at stage 1. A team with a strict change-approval process meets release cadence long before stage 4. Lights Out lets you enter your own numbers and see where your line starts.