Architecture
Judgment concentrates at the top, where the person is. Each plane hands the next something more executable than it was given. State is a file, not a claim.
Three planes. State is a file, not a claim.
There is no database in any of this. Work state is YAML and markdown in a directory tree, kept in git, deliberately separated from the source it acts on. That separation is what lets one task outlive a branch, a worktree, a machine, and the vendor of the model underneath.
The filesystem is the schema
The path on disk is the structure: initiative, milestone, task. No metadata store holds it together, so anything that can read a directory can verify progress, including you.
Model-agnostic by construction
Capability improves monotonically; discipline oscillates per release. Modes, gates and per-model strictness insulate the workflow from vendor variance, and the whole thing rides the subscription you already pay for. No API-key metering.
Nothing to stand up
No server, no account, no second system with its own opinion about what is true. The desktop app is a supervisor's view of exactly the files the tools write.