01 — FEATURE ISSUE
A feature is requested. An issue opens.
Staff request features from inside the app; the request lands as a labeled GitHub issue.
SWIPE THE DRAWING →
02 — PARALLEL SESSION
One issue. One branch. One worktree. One session.
Sessions run in parallel, isolated. Hooks physically block edits in the main clone.
SWIPE THE DRAWING →
03 — FAST GATE
The fast gate answers in minutes.
Lint, strict typecheck and unit tests on self-hosted runners. This lane blocks the merge.
SWIPE THE DRAWING →
04 — STAGE GROUPS
Stage groups run the heavy suite.
Ordered e2e groups, each worker on its own isolated database.
SWIPE THE DRAWING →
05 — AUTO STAGING
Merge. Staging deploys itself.
Every squash-merge builds and ships to a box reachable only over a private Tailscale mesh.
SWIPE THE DRAWING →
06 — PRODUCTION
Rehearse first. Deploy second.
Two backups, the migration rehearsed on a copy, a health check — and rollback if anything moves.
SWIPE THE DRAWING →
07 — THE LOOP
The loop closes itself.
A log watcher turns production errors into issues; an agent drafts the fix. Humans merge.
SWIPE THE DRAWING →
SWIPE THE SCREEN →
THE RESULT