Control Tower · How it builds apps
From control room to app factory
Control Tower started as the console that runs my apps. It has become the thing that builds them.
Describe what you want as requirements; it plans them into sprints on a Work Board, has AI build and a separate AI review
each piece, hands you a checklist to test, and records your signature. New apps come out of it already running in
Dev and SIT, and Prod is always one human click. Every step leaves a file behind, so
any app can show how each requirement was built, reviewed, tested and signed.
01 The shift
Then: a control room
- See every app's live status, one screen
- Start, stop, deploy, promote
- A fail-closed gate and an audit log of releases
- AIOps on a failed release
Now: an app factory
- Requirements become planned, built, reviewed and signed work
- Sprints, planned from the requirements
- Walk away: a whole sprint built while you're gone
- New apps born in Dev and SIT; Prod by the owner's click
- Still the control room: everything above is still there
02 The Work Board
A Jira-style board for every app, Control Tower included. Each piece of work is a card, and every card moves through the same stages.
Requirement→Spec→Build→Review→Test→Sign-off→Done
- Requirements are one sentence each, grouped into areas taken from the app's vision. An area with no requirements shows as work still to do, so nothing is forgotten.
- Status keeps itself honest: a requirement turns Planned, Building and Signed as its items move. Nobody edits status by hand, and the board flags requirements with no item and items with no requirement.
- Every card says who it's waiting on, and a "Needs you" list shows only what's waiting on the owner.
- The same board runs any app, following that app's own process files and names.
03 Sprints, planned from the requirements
AI proposes the sprints; the owner decides.
- A sprint is a theme you can plan and sign as one piece of work, usually three to six items that share a feature or files, ordered so nothing depends on a later sprint.
- One approval for a sprint's specs, and one sign-off at the end, with a checklist that also shows anything that changed along the way.
- A change mid-sprint goes to this sprint or the next, never silently into work that's already signed.
04 Walk away
Approve a sprint, click Walk away, and go live your life.
- It runs the whole sprint: builds each item, has a different AI session review it, and prepares the test checklist, item after item.
- It waits for free memory before starting heavy work, and a failed step names the exact item to blame.
- Questions come to your phone. If it needs a decision, it asks, and you can answer from wherever you are.
- It never signs and never promotes. When you come back, the sprint is waiting for you to test.
05 Auditable, from requirement to signature
Every step leaves a file behind, in the app's own repo.
- Spec: what the item is and how you'll know it works, approved before any build starts.
- Build report: what was done, and just as important, what was not checked.
- Review verdict: from a different session than the builder. Nobody reviews their own work.
- Sign-off: the owner runs the checklist on the real running app, marks each line pass or fail, and signs. A requirement is Signed only when every item that delivers it is.
- An evidence report for every app pulls the trail together.
06 Dev, SIT, and Prod when you're ready
New apps are born in Dev and SIT. Prod is a decision, not a default.
- The New app wizard takes a new app from nothing to running in Dev and SIT, with five CI gates and secret scanning from day one. See the wizard →
- SIT redeploys itself on every green push, so the test environment is always the latest good build.
- Prod only ever moves by the owner's click, through a fail-closed gate, and that click can be undone.
- Each environment is optional. An app without SIT or Prod yet simply shows it greyed out, ready for when it's needed.
07 The human stays in the loop
- The owner approves the vision and architecture of an app before anything is built, inside the app.
- The owner approves every spec before a build starts.
- Builder and reviewer are never the same session.
- Only the owner tests and signs. AI writes the checklist; it never ticks it.
- Only the owner promotes to Prod. AI never releases, never signs, never approves.
- No secret reaches GitHub: every commit is scanned first.
08 The proof: it builds itself
Control Tower is managed on its own Work Board, by the same rules.
103requirements on its board
83signed by the owner after testing
90signed test checklists in its repo
And it's still the control room: everything on the main Control Tower page is still there. For the story of how it got onto a second PC, with two AIs doing the work and a human keeping the yes, read The OG & the Young Buck.