The builds still between us and moving sites for real — what blocks, what rides along on the boxes, and the calls only Robert can make. Updated at every landing, same link.
Rebuilt after the forms reviews · six launch blockers, all named · annotate anywhere, I read it
The bar. A teammate files a site and, with no one from engineering in the loop:
a clean copy lands in about thirteen minutes with forms already working safely · QA walks it
· the site flips to its real address with real recipients · and every step leaves a
receipt someone else could check. Ready means that whole walk works for a stranger — not that
each piece worked once for us.
↘ go deeper — what changed since the last version of this page
The forms night and the day after happened. Independent review broke the recipient-routing safety guard twice with real measured attacks; both holes were cured the same day and the guard that stands is the strictest form — a deploy must carry byte-for-byte the routing our composer generated or it refuses by practice name. The test-email leak (a probe once emailed a real inbox) is closed and review-passed. Adamson went LIVE on its real domain. Visibility now follows the address by construction: staging invisible to Google, real domains indexable from birth. The copy door was deliberately stopped overnight during the scare and its safe-restart is ruled and sequenced. Yesterday landed ten merges on the main line; today deliberately landed zero — the two flagship builds are held in review on purpose.
Where we are — the cohort and the machinery
The launch cohort is ten sites. Adamson is live on its real domain.
Eight more serve cleanly with their forms verified page-by-page (mostly the practices’ own embedded forms, passing through untouched).
Avonlake is the one blocked site — its form renders but dies before submission; its repair has passed review and waits only on your nod.
Behind the cohort, Alie’s next batch of 46 no-forms sites is filed and waiting on the door restart.
The six blockers — every build between us and moving sites
In landing order. Four are builds already made and in their final gates; two are your keystrokes. Builds marked blocker hold the line; everything else rides along on the boxes.
1 · The routing guard — built, in its third independent review.
Guarantees a practice marked live actually receives its own leads: the deploy refuses anything that is not byte-for-byte the composer’s routing, and names the practice it is refusing for. Reviews one and two each caught a real hole; each was cured same-day. Lands when review three passes.
↘ go deeper
Canon PR #2135, head fd3137578e. Round-1 BLOCK: guard tested string emptiness — a live practice deployed green with an empty routing list. Round-2 BLOCK: coverage-by-form was a proxy four hand-set values could satisfy while delivering nothing. The standing cure binds the composed payload’s fingerprint into a committed receipt; all four attack values are permanent regression tests. Review three also probes one level deeper (a page-address routing row shadowing a form row); if that measures true it comes to Robert as a ruling, not another patch — both desks pre-committed.
2 · The no-test-emails guard — built, review PASSED.
A delivery test can never email a real practice again: before the fix one probe sent a real email; after, zero, across every way a form can post — verified by an independent reviewer who rebuilt the proof from raw counts. Merges right behind the routing guard (they share a branch).
3 · Your one tap. When 1 and 2 are green: merge both · one deploy · one secret to set. Batched into a single moment; I bring it to you ready.
4 · Avonlake’s repair — built, review-passed, waiting on your nod.
Fixes the class where our rewrite corrupted a form’s script (the render-but-dead defect), with a standing per-form parse gate so the class cannot ship again. Your approval of the frame retirement merges it and takes the cohort to ten of ten.
5 · The first delivery receipt. After 3 and 4 plus one plane redeploy: run the first end-to-end “a submission actually arrived” receipt on the healed avonlake — the proof template every launched form gets from then on.
6 · The door restart — ruled, sequenced, your five keystrokes.
Update the copy door’s code (brings the guard against old queued requests auto-running), switch its forms pass off (the population has no forms; the switch makes that provable), start, watch, abort-rule armed. Unblocks Alie’s 46 sites tonight.
On the boxes — hardening routed today, none of it launch-blocking
Trunk box · ten builds queued. Vacuous-check hardening (a required check could pass having run zero tests) · the database-migration gap on the lead store · missing security headers in warehouse rebuilds · a fleet sweep for filename collisions · a retry port · daemon inherited-state census · four older instrument residuals. Routed to the box today after two boxes reported their queues dry — the routing lag was mine, now on the every-sweep rhythm.
Elsewhere. Birth box: one detector build (forms hiding in script-tag mounts). Plane: one auditability residual. Forms canon: five wire-or-retire rows from the census (instruments that exist but gate nothing yet). Desk: one doctrine question on what the form census reads. The exam — the sealed twelve-ask final — is staged on your chosen substrate and resumes after the forms tap.
Your calls — what only you can move
Now · the avonlake nod Approve the frame retirement in the fast-lane session → cohort goes ten of ten.
Now · the door keystrokes Five commands, sequenced and ruled → Alie’s 46 sites start moving.
Now · two lane rulings Keep-or-rethink on the two builds that failed review twice.
Soon · the one tap Comes to you only when the routing review runs out of ways to break the fix.