b.akery — the evidence room
I don’t write the code.
I write the intent.
Precisely enough that the code is inevitable. That is the whole method: the operator authors intent and constraints, the machine authors the artifacts, and every dollar-figure and every claim still gets checked by hand. When intelligence is cheap, the scarce things are knowing exactly what to build and actually shipping it. b.akery is that method — an open-source CTO for non-technical founders.
Everything on this page is the method demonstrating itself: the speed, the reasoning, the polish. This page included.
- 01 Commit stamps
- how fast it shipped — timestamped, not claimed
- 02 A shipped storefront
- operate the real content-and-commerce flow
- 03 A call console
- ask for a call from a voice agent I built
- 04 How it works
- four failure modes, four gates — try one live
Four exhibits today. The room fills up: the argued decisions, the front-office system, a live line to Clara.
This site, timestamped.
The honest way to prove speed is the record. The git history and the Cloudflare deploy log are both public and both hard to fake. So here is this exact page, from nothing to live.
- 2026-07-15first commitAn empty repository. No design, no copy, no pipeline.
- ~1 dayto live on the apexFirst commit to jamesdnichols.com serving real traffic, 2026-07-16. A Cloudflare deploy stamp, not a claim.
- ~6.5 daysto built out237 commits and counting — the lander, the guides, the calculators, the measurement layer, this room.
Every figure here is read from the git log at build time, so it can only ever be current. git + Cloudflare stamps.
A storefront, rebuilt so you can click it.
Content plus commerce: a park page, a guide, a checkout. Operate the flow — this is the outcome the method ships, not a screenshot of it.
idea → monetized content, ~6 weeks
Astro · Cloudflare Workers + D1 · Shopify
Atlas · national parks
Arches National Park
Red rock, high desert, and the most concentrated set of natural arches on earth. Plan the trails, the light, and the crowds before you go.
The Arches Field Guide
Trail-by-trail, where to park, and the best hour for photographs.
$12
Facsimile. Rebuilt from scratch in Astro for this page — not the live store, no real checkout, and the park and guide are illustrative. The real Atlas sold national-park guides on Shopify.
Ask a question. A system I built calls you back.
Clara answers the phones for home-service contractors. The strongest kind of proof is the one you can talk to — so leave a number and she rings you.
idea → Clara on a live line, ~2 weeks (git: 2026-04-05 → 04-18)
Retell AI · SIP telephony · Cloudflare Workers + D1
Clara answers the phones for home-service contractors — books jobs, quotes windows, never sleeps. Ask her anything an HVAC customer would, and she calls you back.
Runs on TradeFront’s registered calling stack — A2P 10DLC brand and TCPA consent, the part almost every agent demo skips.
Live. Leave a number and Clara dials it once, on a recorded line, under TradeFront's registered A2P 10DLC and TCPA consent trail. Outbound-only and opt-in by design — no open number to abuse, one call per number per day, hard daily cap.
How b.akery works.
You've used ChatGPT or Claude. It wrote confident garbage, invented a statistic, forgot everything by Tuesday, and said "done" about things that were visibly broken. Same models here — different results. The difference is a system built around four specific failure modes.
1 It forgets everything.
Every session starts by rereading a standing contract: what is true, what is in flight, how to behave. Next to the facts sits a stranger thing — a written list of what the model will plausibly get wrong, with dated corrections it is told not to undo. The amnesia is assumed, then engineered around.
"The launch-kit 470k/400k figures are SUPERSEDED — do not 'correct' surfaces back to them."
A real entry, written to stop a future AI session from "helpfully" reverting a corrected fact. It worked.
2 It invents numbers.
No figure ships from the model's mouth. Every public number traces to an analysis document carrying the query that reproduces it and the base it was measured on — and where the model does arithmetic, one math file holds every formula, derived in comments, with tests that assert hand-computed values only.
This site's flashiest stat was a 19.5x ROAS. Held to the light: it counted only $122,830 of the $414,273 actually spent — a selection artifact. It got demoted to the fine print, and the page now leads with 9.2x on every dollar. The method downgraded its own best number. Nobody fakes that.
// engine.mjs: "No constant in this file comes from a language model."
3 It says "done" when it isn't.
Rules the model "should follow" are worthless — so here they're checks that fail the build. Typecheck, arithmetic tests, contrast math, and a copy gate that bans the builder's own jargon from ever reaching a buyer. And every checker must first catch fifteen planted errors before it is allowed to certify anything: a gate that can't see known-bad pages doesn't get an opinion.
$ try the gates — the same regexes that gate this page's deploys, imported from the same file
Verdicts print here, exactly as the build prints them.
For the developers — the eaten-space check, as shipped:[A-Za-z0-9—.?!,:;]<(strong|em|b|i|a|span)\b[^>]*>[A-Za-z0-9] · it reads the raw HTML because every other scanner strips tags to spaces first and literally cannot see this bug.
4 A green checkmark isn't the truth.
Automated checks render every changed page at phone and desktop width, light and dark, and assert computed styles. Then the part no tool can do: a commit that touches design is blocked unless a dated "I actually looked" entry ships with it. The hook is honest about its limit — it checks the log moved; the looking is the point.
"The dev server was serving an error page. vision-verify printed 'ok'. Only looking caught it."
Three separate entries where every mechanical gate was green and a human eye still caught the real bug. That log is why the gates are trusted: they're allowed to be wrong, on record.
Not a one-off.
The same discipline runs in five systems, and every rule below was born from a real incident in that repo — one per month, months before this page existed.
- MAR 2026 · margin pipelineA one-character deploy flag wiped production credentials. The rule went into the log the same week, and a machine tripwire has re-checked it on every scheduled sweep since.
- APR 2026 · voice agentA test harness phones the AI receptionist and scores the transcript. The failing report stayed checked into the repo until the fix shipped, next day.
- MAY 2026 · treasuryWhere money is counted, the model never does arithmetic: it writes the queries, the database computes, and ingestion ships with run-twice idempotency tests.
- JUN 2026 · storefrontA filled button rendered green-on-green (invisible) and passed every lint. Verification moved to the computed render — the rule this page’s own gate descends from.
- JUL 2026 · dialectic engineOn its first live run, agents “succeeded” while returning auth errors. Hardened the same afternoon: agent-reported errors hard-fail, never salvaged into output.
The model isn't smarter. Its failure modes are made non-recurring.
Every escaped bug becomes a permanent gate, the same day. That's the whole method — and it's what you're reading right now.
Want the method, not just the demo?
b.akery is the open method behind all of this: the templates, the guardrails, and the discipline that turns a non-engineer’s intent into shipped systems. Leave an email and I’ll send it as it opens up. No spam, no hard sell.
Rather have it built for you than build it yourself? See how I work with brands — or start with the person.