How it is built
One developer, a crew, and a paper trail.
SproutCrew is made by one person working with AI agents, under the rule the app itself applies: one writes, another checks, and a person approves. This page is the process, from an idea to a signed download.
- 1,161automated tests on the core, run before every commit
- 79interface tests
- 7signed builds reviewed, 2 offered publicly
- 100+numbered entries in the issue log since October 31, 2026
Figures are for the 2.1.0 release, November 17, 2026.
1. Plan
One list, one row for each idea.
- Every idea, fix and launch task is a row in one roadmap, tagged by phase, priority and status. A row moves to Shipped only after the running app has been checked, never when the code is merely written.
- The public roadmap is a short, curated view of that list.
- Decisions are written down with their date and their reason, so a later change can be traced to who asked for it and why.
2. Build
Tests first where money, limits or privacy are involved.
- Parsers, the cost ledger, spending holds, stop rules and redaction get their tests before their code.
- Three checks run before every commit: formatting, the linter with warnings treated as errors, and the full test suite.
- A feature that a person can see updates the help page in the same commit, so the help never trails the app.
- The core holds every rule about what a crew may do. Text written by a model is treated as data and never becomes a command or a permission.
3. Review
A second reader, on purpose.
- SproutCrew is built the way it works. AI coding agents write most of the code, a different model reviews it, and a person approves what goes in.
- Before a release, a reviewer with no network access and no credentials reads every change since the last one. Each finding is checked against the code before it is accepted, then fixed with a test where one fits.
- For 2.1.0 that review found no high-severity issue, one medium and seven low. Seven were fixed before release. The eighth affects only the developer's own Mac.
4. Release
Signed, notarized, and checkable by anyone.
- Each build is signed with an Apple Developer ID, uses the hardened runtime and is notarized by Apple. The release script refuses a build in which any bundled program is unsigned or built for the wrong chip.
- The download page shows the SHA-256 of the exact file. The download button stays hidden unless the release record names a file at the expected address with a valid checksum.
- The sources of the open-source parts that require it, and all notices, are published beside each installer.
- The previous version of the site is kept, so a release can be rolled back.
5. Record
What was checked, and what was not.
- Every problem found, by the developer or in testing, gets a numbered entry in an issue log: the cause, the fix, what was tested and what was not.
- Each release has a record that ends with the checks nobody has done yet. A build that started correctly is described as a build that started correctly, and nothing more.
- The changelog is written from those records.
6. Listen
Without watching.
- The app has no analytics, so there is no count of users and no record of what anyone does in it. That is a decision, and it is on the roadmap under Not planned.
- What is known comes from people: testers who follow a task sheet on their own Macs and report what broke, and anyone who writes to [email protected].
- When something fails, Settings can export a small log to send. It holds the app version, connection checks and failed steps by kind. It never holds your text, file names or keys.
Read the code
The source of each public release is on GitHub, so anyone can check what the app does with their keys and files, or build it themselves. It is source-available under the PolyForm Shield licence: you may read, run, fork and change it, and you may not use it to offer a competing product.
The architecture, with diagrams, is in Inside the build.