proof.bluecrestva.com · a live measurement
This page is its
own proof.
At 03:47:11Z on August 30, 2026, one prompt asked for “an app explaining this, deployed publicly to prove it.” The page you are reading is the deliverable, live on a custom domain with TLS, untouched by human hands.
Frozen once at build, seconds before deploy. This number includes one honest iteration: the first deploy computed the elapsed time per-request instead of at build, so the agent caught it, fixed it, and shipped again — that debugging minute is in the total, not edited out.
The run · August 30, 2026 (UTC)
Prior runs, same harness
Timestamps mined from the original session transcripts — the kickoff prompt, the scaffold command, the first successful deploy. Five of these shipped in a single evening.
| app | prompt → live | harness overhead |
|---|---|---|
| letter-mouse | 3m 04s | 2m 23s |
| star-pop | 4m 12s | 1m 56s |
| piano-party | 4m 24s | 2m 23s |
| brick-bloom | 6m 16s | 4m 02s |
| farm-watch | 7m 55s | 5m 32s |
| firefly-catch | 11m 49s | 2m 02s |
| open-city | 13m 34s | 6m 46s |
“Harness overhead” = scaffold → deployed. The difference is the agent writing the actual app.
Two loops, one pipeline
save → live on a home server. Scaffold 1.1s, build 4.0s, restart 1.1s — measured with the network unplugged. One shared package store (0.47 GB) serves every app.
prompt → public custom domain. OpenNext on Workers; D1, R2, KV, Durable Objects and cron wired by one command each. Deploying is a promotion event, not the loop.
The build fails on any external fetch, and proves it inside an empty network namespace.
No create-next-app, no npm install. A new app can be created with the WAN unplugged.
Route handlers move between Cloudflare and the local box by changing one import.
No reverse proxy and no root: install, deploy and restart never ask for a password.
What the numbers do and don’t claim
- Included: agent thinking and writing time, scaffold, build, resource provisioning, DNS and certificate issuance. The clock starts at the prompt.
- Not claimed: that a full SaaS with auth and billing ships in minutes. These runs are small apps. The harness floor is seconds; app complexity is the variable.
- Verifiable: the zone is real, the certificate is real, and the build timestamp above was computed by the build itself.
- Amended: the contact section below was added after the measured run, backed by a KV namespace the same harness wired in one command. The measurement above is pinned to the original deploy and did not restart the clock.
Want one of these?
I ship apps like this one — live on your domain, in days not weeks. Tell me what you need.
Or: an agent that does this for your own ideas, deployed to infrastructure you own, is in the works. Leave an email and you’ll know when it opens.