I design autonomous systems that finish what they start. The proof runs daily: a build factory I wrote specs, builds, adversarially reviews, and deploys one small working project every day — most with a live demo — then updates this page itself.
streak **23** · avg rubric **4.33**/5 · demos alive 17/17
Latest ship — day 026 · critic-loop
Paste a paragraph and watch a critic mark what is wrong, three passes deep, with the critique shown between every draft. agent · vanilla JS, zero deps · rubric 4.50 — live demo · source
| build | what it does | stack | proof |
|---|---|---|---|
| git-mood | A terminal mood chart for a git repo — tempo, a punch-card clock, streaks, and tags that print their own arithmetic | Python 3, stdlib only | rubric 4.75 |
| json-tidy | Paste JSON, get a collapsible tree, and copy any node's JSONPath with one click | vanilla JS, zero deps | demo · rubric 4.58 |
| orbit-doodle | The page draws itself one flourish before you touch it, then gets out of the way | vanilla JS, canvas | demo · rubric 4.50 |
| trace-lens | A shared #t= link now lands in a tab you already have open, and the timeline answers the keyboard | TypeScript, React, canvas | demo · rubric 4.50 |
| pixel-garden | The keyboard walk speaks — each plant the selection lands on names itself aloud | vanilla JS, canvas | demo · rubric 4.50 |
One row per repo; ranked by reactions on ship issues, rubric score until the votes arrive.
Every project starts as an issue. It gets a spec and a README before any code exists, is built by one agent, then torn apart by adversarial critics — a build ships only past a seven-line must-pass gate (loads clean, survives garbage input, works at phone width, truthful README, licensed, secret-scanned, demo live). The doctrine, rubric, and every daily sign-off are public in factory-hub.
Maintained by the factory · dashboard · last updated day 027 (2026-08-20)