How we work
Our code is written by Claude Code, several sessions at once, in one repository. This page shows how a change is checked before it is merged, and how often one has needed fixing since.
How a change is checked
- Larger work starts as a written specification, cut into slices that each land as one pull request.
- A Claude Code session writes each slice and its tests in its own copy of the repository; a reviewer agent that can read but not edit then checks it against the specification.
- On the pull request the build runs type checks, lint, tests and the repository's own rule checks. A review bot must report on every change before the session may merge it; a second reads changes to payments, the shared sign-in and permissions code and database schemas, when its usage limit allows.
- Every finding is fixed, rejected with a reason, or recorded for a fix of its own when the defect lies outside the change.
- The session merges its own pull request once every check is green and every finding is answered. A change to the sessions' own instructions or to the merge gate needs the founder's sign-off.
Figures
Pull requests merged 14-21 September 2026, fixes counted to 5 October 2026.
Merged pull requests
126
Counted on GitHub.
Changes to the repository's own rules and tools count too.
Review size
445 lines at the median, 1,006 at the 90th percentile
Lines each pull request adds, tests included, working notes left out.
Deleted lines are not counted, though a reviewer reads them too.
Needed fixing after merge
7 of 126 (5.6%)
A pull request counts when a fix merged within 14 days rewrote lines it added and a Claude agent judged it wrong when it merged.
A separate check of 30 of these pull requests, against every fix to their files within 14 days, agreed on 29; at 95% confidence the two checks disagree on at most 17 in 100.