Measured 18 August 2026Pre-revenueSeven properties live
The operating method behind seven live properties, built by one person in six months.
A 28-document engineering standard, eight module extraction plans drawn from a 187,344-line production codebase, and 2,183 committed prompt-and-release files.41316 The framework's code extraction has not started. Everything else on this page is running right now.
CookOS is in public beta serving 11,526 validated recipe pages and 1,067 creator pages.
DropOS runs 100 levels on Three.js and Rapier physics. Build 153 went to TestFlight on August 31.
dropos-web.vercel.app · App Store Connect API89
01 / The problem
Every new product restarts the same work, and the reasoning behind it is never written down.
Solo builders do not fail on ideas. They fail on the second product, when nothing from the first one carries over except the parts that happened to live in one person's memory.
What most solo builds do
- Start each product from a blank template
- Keep the standards in one person's head
- Rebuild admin, QA, and analytics per app
- Lose the reasoning the moment context is gone
What it costs
- Months of rebuild before any new idea is testable
- Drift between products that should be identical
- No institutional memory across sessions or tools
- Quality that depends on who is paying attention
What LaunchKitOS changes
- Every unit of work ships with the prompt that produced it
- Standards are versioned files, not habits
- QA gates ship in the same commit as the feature
- The next product inherits by copy, pinned to a version
02 / The method
Five stages, and each one leaves a file behind.
The method is auditable because every stage commits an artifact. That is what makes it transferable to a second product, and to a second operator.
- 01 SpecifyThe unit of work starts as a committed prompt file, not a chat message.
- 02 BuildThe agent executes against written standards it can read, not conventions it has to infer.
- 03 GateQA runs in the same commit as the feature. DropOS registers 48 gates this way.
- 04 ShipA release note is committed with the change, so the record is the repository.
- 05 InheritThe next product copies the core, pinned to a version it can be diffed against.
# the standards an agent reads before it writes anything
accessibility.md accessibility is a P0 design standard
design-quality-standard.md the pixel bar + how to take founder notes
no-duplicate-systems.md one system per job, enforced at review
post-deploy.md verification after every push
qa-agent.md the automated reviewer contract
unit-test-coverage.md coverage floors that gate the deploy
version-rotation.md how a release is cut and recorded
…22 more
# from design-quality-standard.md, verbatim:
"Every surface that ships is pixel-perfect,
best-in-class, production-grade."The library is process governance, not runtime code. 14 of the 29 files still name CookOS specifically; a genericization pass is pending and the repo says so.13
03 / The evidence
Seven properties are publicly reachable. One is a specification.
Ordered by what a stranger can confirm in one click. Status is stated as it actually is, including where it is not good.
04 / Who is building it
One operator, fifteen years of shipping at scale.
- CBSLed digital product and AI work for major media properties.
- YahooLed digital and AI programs across a global brand portfolio.
- SazeracDigital and AI leadership on consumer brands.
- 2026Seven publicly reachable properties, roughly 3,900 commits, and a dated portfolio audit that ranked ten cross-project risks and closed twelve decisions with evidence.1618
Employers are listed as pedigree. They are not clients of this work and no claim is made on their behalf.
A note from the founder
I did not set out to build a framework. I set out to ship one product properly, and the second one made it obvious that the valuable part was never the code. It was the written method: the standard an agent reads before it writes, the gate that runs in the same commit as the feature, and the release note that makes the repository the record.
That method is real and it is on disk. The framework that would package it is not built yet, and I would rather you read that here than discover it in the repository. What I am asking you to evaluate is the compression: seven publicly reachable properties in six months, by one person, with every unit of work traceable to the prompt that produced it.
If that is interesting, the next step is twenty minutes and a walk through any repository you want to pick.
Pick a repository. I will walk you through it.
No deck required for the first conversation. The evidence is the codebase, and it is easier to read than a slide.
Where these numbers come from 20 sources, measured 18 August 2026
| Ref | Figure | Source and method |
|---|---|---|
| 1 | 11,526 recipe pages, 1,067 creator pages | cookos.ai/sitemap.xml and cookos.ai/llms-full.txt, two independent live endpoints agreeing exactly. Validated and indexed rows only. |
| 2 | Deployed version 0.84.70 | cookos.ai/api/version, live response. |
| 3 | 2,213 commits since 3 Feb 2026 | git rev-list --count HEAD in cookos-app, cross-checked against git log. |
| 4 | 187,344 lines across 803 files | git ls-files over app, components, lib, contexts, hooks. Tracked files only. 174,344 lines are CookOS-attributable after removing co-hosted routes. |
| 5 | 255 API routes, 147 migrations, 121 test files | git ls-files counts in cookos-app. |
| 6 | Nine production crons, MCP server behind OAuth 2.1 | crons array in vercel.json; live 401 from the public MCP endpoint. |
| 7 | 81.6% line coverage | coverage-summary.json. Measures an explicit 4,822-line allowlist of auth, MCP, OAuth and search modules, not the whole codebase. |
| 8 | TestFlight build 92, 85 builds delivered | Live read of the App Store Connect API for app 6788594506. Not submitted to the App Store; the 1.0 record is in PREPARE_FOR_SUBMISSION. |
| 9 | 100 levels | Counted by importing the shipping levels module at runtime, not read from a document. |
| 10 | 48 QA gates registered | Gate runner listed live. Gates on change from a recorded baseline that currently accepts 8 failing gates. |
| 11 | 1,132 commits, 71,445 lines | dropos-web since 6 Jul 2026, absolute-path find and wc, excluding vendored dependencies. |
| 12 | 4,813 lines of specification, zero code files | find across core, modules, templates, rules, docs, scripts and sql. Markdown only. VERSION reads 0.1.0. |
| 13 | 28 standards files plus a README, 1,823 lines | Counted and read in launchkitos/rules. Process governance, not runtime code; 14 files still name CookOS. |
| 14 | Eight module extraction plans | Each MODULE.md names the specific source files to extract and its migration range. The search module names 18 files and range 500 to 599. |
| 15 | 98.5% of commits are the hosted game | git log --no-merges over apps returns 1,464 of 1,486. Framework directories last modified 25 Apr 2026. |
| 16 | Roughly 3,900 commits, 2,183 prompt and release files | Per-repo git log and git shortlog across five repos; find over each prompts directory. One human contributor throughout. |
| 17 | Seven publicly reachable properties | Individual live checks returning real titles and body content. See the verification note below. |
| 18 | Portfolio audit, ten risks, twelve decisions | PORTFOLIO.md dated 9 Jun 2026, built from nine inventories and four boundary censuses. |
| 19 | Three-day sprint, 43 live-run sessions | FalseOS repository inventory and its v001 session handoff, 25 to 27 Apr 2026. |
| 20 | Coming-soon live since 13 Jun 2026 | pledgepride.org plus the repository's own status documents. Four legal gates are named there. |