Latest runs
How a run works
A project enters as a scattered Dump, gets sieved into a brief, then moves through Code, Funnel, Button Function Test and Redeploy — evidence attached at every stage. The Gate decides ship or no-ship. Pass it and the build is stamped Sieved, with a public verify page. Fail it and the run closes with an honest failure report. Both outcomes are wins for the truth.
Runs
Run
The Gate
Whole-stack report
Registry — every function, its phase, its status
Live means working today. Grey means upgrade needed — wired in as far as this phase allows, named honestly, never faked. When its phase arrives, only the inside gets built; the button is already here.
Evidence
Every file attached to a run is fingerprinted (SHA-256) the moment it is attached. The fingerprint rides with the run forever, so the evidence on a stamped run can be checked against the file it claims to be.
Billing
Workspace
Seats & roles
Audit trail
Append-only. Every entry is chained to the one before it, so a quietly edited history breaks the chain and shows. Adapted from the Hopscotch audit engine (sieved 2026-11-15).
Your data — plain files, no landlord
The export is the whole workspace: runs, registry, stamps, audit trail. Keep it anywhere; import it on any device to move the studio.
Button Log
About this build
Stamp verify
The public check, inside the shell. Anyone with a stamp ID can see what was checked and what the build can't do.