How it gets built
One person, a crew of AI agents, and a rulebook.
I do not write most of the code. I run the operation. AI agents do the engineering inside a system I shaped with them, and three rules hold it together: every change is proven on a simulated iPhone before it ships, a release gate decides what goes out, and anything that matters gets written down as a law a script can enforce.
- STEP 1
Ask
I describe the change in plain English. The agent reads the code and plans it.
- STEP 2
Prove
It writes the change and a test for it, then shows me the result on a simulated iPhone before anything is pushed. Compiling is not proof.
- STEP 3
Gate
The release gate runs every suite on a large and a small iPhone, in light and dark, plus the laws. Red means no deploy.
- STEP 4
Ship
Agents submit the build through Apple's API. I find out when TestFlight pings my phone.
The release gate
Nothing ships because an agent says it works.
This is the gate's own output for the version on the App Store today: 65 test suites, 999 individual checks and 31 laws, all passing before the build was allowed out.
Each suite drives the real app on a simulator the way a person would, then reads the result back, down to iOS's own queue of pending notifications.
── artifact truth (generated-code greps) GATE PASS artifact: cold-start tap → Messages hook registered LAWS PASS: reverence, warm-name, vocabulary, chain-honesty, … GATE PASS suite: engine_1962_test@pm (3 checks) GATE PASS suite: notif_storm_probe_test@pm (8 checks) GATE PASS suite: relaunch_persistence_probe_test@pm (9 checks) GATE PASS suite: reverence_probe_test@pm (6 checks) GATE PASS suite: somber_calendar_probe_test@pm (6 checks) GATE PASS suite: edge_cases_test@pm (21 checks) GATE PASS suite: small_phone_rescue_test@se (9 checks) … GATE GREEN: 65 suites, host edge matrix (74 tests), 31 laws, four tour legs.
Excerpt of the gate report for build 156. The highlighted suite is the one from the story below.
Law 1 · Reverence
The app must never celebrate a loss.
Some people use Thoughtful to remember someone who has died. A review caught the calendar painting "Anniversary of passing" in celebration rose, because the word anniversary was in it.
The fix shipped the way everything ships: a failing test first, proof on the simulator in light and dark, then a permanent suite in the gate so it can never come back. Two days later it was on my phone.
- 29Dad, anniversary of passing: now a quiet gray dot, no color wash
- 30A wedding anniversary: still rose
- 31A birthday: still amber
# LAW 1 — REVERENCE: any custom-code file that speaks in celebration # (🎉 🎂 'big day' 'Happy ') must carry a somber gate. for f in $(grep -rlE "🎉|🎂|big day|Happy " $GC/custom_code | grep -vE "$L1_ALLOW"); do if ! grep -qE "_somberOcc|somberOf" "$f"; then echo "LAW FAIL reverence: $f celebrates with no somber gate" FAILS=$((FAILS+1)) fi done
- LAW 10 · THE FLOORA tap on a remembrance reminder never opens Messages on its own.
- LAW 23 · UNDO LEAVESAn undo bar has to time out and get out of the way.
- LAW 25 · NO DASHNo em dashes in anything the app says. They read as AI.
- LAW 27 · A REMEMBRANCE ARRIVES QUIETLYNo chime and no badge for someone being remembered.
The board
Before a big release, a board of reviewers audits the app.
Every seat is an AI agent with one job and a named blind spot. In one audit, 17 seats raised 106 findings. A skeptic then re-checked each one against the code, and 88 held up. Those became the next releases.
- The Night Watchmanchecks that reminders really fire.
- The Archivistmakes sure nobody loses their people.
- Grandmais 74, reads with large text, and wants it simple.
- The Chaplainholds an absolute veto on anything touching remembrance.
What I took from it
Agents are fast. Gates make them trustworthy.
The speed was never the hard part. Knowing what is safe to ship was, so that is where the work went.
Judgment can be written down.
Tone, reverence, even punctuation. If it matters, it becomes a law, and a script enforces it on every release.
Show it before you ship it.
That rule came from getting burned by changes that compiled fine and did not work. Now nothing goes out unseen.