The fleet
The Signal Box
APE runs day to day on a fleet of Claude agents. They do the work. A person approves anything customer-facing, destructive or costly. This box sets the road.
Agents do the work. A human sets the road.
Every change runs the same route. Pull the levers in order, like a signaller would. It's interlocked, so no lever moves until the one before it has.
Proposal
An agent drafts the change: code, a page, a fix or a report. It says what it wants to do and why.
Checks
Tests and type checks run before anything moves. If one fails, the change stops here.
Approval
A person reviews it and says yes or no. Anything customer-facing, destructive or that spends money has to get that yes.
Live
Only then does it ship. The commit lands in the register below, straight from git.
The studio numbers
Counted by machine from git and the studio's own records, not estimated. Recounted 11 October 2026.
- Agents in the fleet
- 35
- Commits in the last 7 days
- 283
- Repos touched this week
- 29
- Live products
- 17
The train register
What actually shipped, straight from git. Dates only, newest first. Routine housekeeping is left out.
| Date | Line | Movement |
|---|---|---|
| Marketframe | Analytics: drop crawler beacons (Googlebot etc.) at /api/track | |
| Paws of London | Owners can save amenities on venues with no amenities row; Details save errors are visible (#30) | |
| Marketframe | News pages: show a -10..+10 tone score instead of the raw -1..+1 |
Who works the line
The fleet is a set of roles. Each has a narrow job and a human above it.
Engineering
Writes code and fixes bugs across the studio's products, with tests to catch what it breaks.
SEO
Checks how pages get found and read, by search engines and AI assistants alike.
Content
Drafts guides and posts from fact sheets, then checks them against those facts.
Design review
Screenshots pages, critiques them and flags anything that looks off.
Research
Reads widely, sorts cheaply and passes on only what deserves a closer look.
Security
Scans for leaked secrets and audits dependencies every week.
Operations
Watches the machines, keeps the agent-to-agent traffic moving and raises the alarm when something stalls.
Further down the line
- Jack's writing: Notes on how the studio and its fleet work, written by Jack.
- The architecture, in public: The fleet's design on GitHub, with the measured numbers.