intake never sleeps · agents plan, build, attack and document · gate one is an agent · gate two is a person · live is one command from reverted
The crossing // seven steps, two of them gates
What happens to one issue
The asymmetry // why this works at all
A second lane costs almost nothing.
A second review costs the same as the first.
That one sentence decides the shape of everything else. Lanes are cheap to run side by side; the reading at the end of them is not, and never will be. So the scarce thing is protected and everything upstream of it is arranged to make that read fast.
Small branches. Intent written down before code, so a diff is read against a stated goal instead of an inferred one. Tests already green. The adversary's report attached. The review that would have taken an afternoon takes twenty minutes — and that is the number that decides how many lanes can be open.
How long a finished branch waits before it gets read. When this climbs, we close a lane rather than let the queue grow — a backed-up gate is how quality quietly becomes optional.
The invariants // what never gets traded away
Why parallel doesn't cost quality
An agent can't work from a hallway chat, so every piece of work starts as a written spec with a testable done. It felt like busywork for about a week. Now it's why two people can hold five lanes of context without losing the thread.
A dedicated agent attacks each branch on sight — edge cases, malformed input, the ugly path. It can block a release on its own and cannot unblock one. Every bug it finds is one that never reaches the review queue.
Lanes are cheap to run in parallel; the reading at the end of them is not. So the whole floor is arranged to make that read fast — small branches, written intent, tests already green, the adversary's report attached. That seat isn't going anywhere — it's the one part of this we don't want to automate.
Reproducible builds, signed artifacts, one-command rollback. When undo is cheap and instant, shipping stops being a ceremony you schedule and becomes something that happens the afternoon the work is done.
Always listening // the floor has no front door
Work arrives on its own
Most of what gets built was never anyone's idea — it was something a person said in a thread. Agents sit on every channel, triage what arrives, and either file it as an issue or draft the reply. What they never do is send.
Listens to what users actually say, reproduces it, and files the ones that are real as issues — which then get refined and built like anything else.
GATE // Issues are filed freely. Replies in public threads are signed as an agent.Reads the correspondence, drafts the reply, attaches what it needed to look up to write it.
GATE // A person reads every reply before it sends. No exceptions.Plans the calendar, writes the posts, prepares the assets, and schedules nothing on its own.
GATE // Nothing goes out under our name without sign-off.Researches who might actually want this, drafts the outreach, and keeps the list small on purpose.
GATE // Signed off before a single message leaves.Turnaround // before and now
Where the weeks went
Rough figures from our own work, not a benchmark. The point is not the ratio — it is which step moved. Building was never the slow part.
What this buys you // the promises, plainly
And the gate itself // the part that is supposed to shrink
Both gates exist for the same three reasons — security, compliance, and not saying things that aren't true. None of those is a reason to keep someone clicking forever. So the rule is simple: when a gate has become nothing but a yes, it stops being a gate — the check moves into the floor as something an agent enforces, and the attention moves on to the next thing that actually needs judgement.