How it's built
Built with AI coding tools, in the open, under rules strict enough for production money.
The Method apps are written by a working producer with AI coding agents, under tests and review. That's said openly here so you can judge the work on its checks, not on a guess about how it was made. The apps themselves contain no generative AI: nothing writes your script or invents your numbers.
Clean room
Every app is independent work. Nobody on the project decompiles, disassembles or
debugs another vendor's software, or copies its code, help text, icons, templates or
bundled data. Learning how productions work, using other tools normally and reading
the open files they export are fine. Each repository's CLEAN-ROOM.md has
the full rules, and every contribution follows them.
Tests
Every change runs the full test suite before it lands. Test functions in each app, counted on 16 October 2026:
| App | Tests | Also |
|---|---|---|
| Method Storyteller | 43 | Strict lint rules; early days. |
| Method Reader | 3,573 | Every conversion checked against a frozen set of expected answers. |
| Method Schedule | 622 | Timing budgets: an edit and redraw must stay under 5 ms on a big board. |
| Method Budget | 1,255 | Seeded property tests, and nightly fuzzing of every file format it reads. |
Money and files
- Money is whole cents, never floating point. Rates and percentages use an exact decimal type with a written rounding rule.
- Saves are atomic, with autosave and recovery: a crash never costs you the file.
- Every file format is plain, documented text, specified in its repository, so your work opens in twenty years with or without these apps.
Supply chain
- Every dependency must be at least 14 days old before it's used, and every licence and security advisory is checked on every change.
- Build steps are pinned to exact versions. Released Mac apps are signed and notarized by Apple.
- MIT OR Apache-2.0, every line on GitHub.