Structured build reports
Not marketing fiction. Each case study shows the prompt, the manifest, the generation stats, the repair cycles, and what we learned — including what didn’t work first time.
Building Check Writer Pro — illustrative build report
PLACEHOLDER. This page describes what a successful build report would look like for a Windows desktop MICR check writer. The numbers below are illustrative — the desktop pipeline has not produced a verified artifact yet (Windows bridge provisioned-but-stopped, no end-to-end desktop run on prod). The web pipeline ships verified runs daily; see /factory/case-studies/recipe-manager-web for the first one and /factory/proof for the live list.
Recipe Manager Web — first verified factory pass on prod
Real prod run, 2026-05-18, job 5b405f2f. Prompt → 22 generated files → Build PASS → Launch PASS → 485 KB tar.gz with sha256. The complete factory pipeline produces a verifiable deliverable on production from a single prompt.
Want your build report public?
Design partners get a structured build report after their first production app. Helps your stakeholders see exactly what was generated, what was repaired, and what to expect on revision 2.
Become a design partner →