How a regulated-grade app gets built by AI.
The same spec-driven discipline used in regulated engineering, adapted so that an AI author and a single human reviewer can ship a real application responsibly.
Every behavior foragerr is meant to have is written down first, with a stable ID. IDs are allocated in the registry when a change is proposed, and a commit hook rejects any commit citing an ID that is not registered.
Each requirement links to the spec that defines it, the tagged tests that prove it, and the commits that built it. The matrix is regenerated from repository state — spec headings, test tags, commit trailers — and inconsistencies fail the run.
The owner approves every proposal before implementation begins, and no change merges until its gate passes: the full test suite green, traceability and dependency checks at zero, and a multi-angle review of the diff.
Every tagged release carries the same four artifacts: a CHANGELOG entry citing the requirements it moved, an annotated tag, the pushed history, and a GitHub Release. Tags are immutable — a mistake gets a new patch release, never a moved tag.
foragerr is young, its code is AI-authored, and no human has read every line. The registry, traceability matrix, review gates, and release records here show exactly how it was made — not a claim that it is flawless. Discipline is the point; perfection is not the claim.