How it's tested
The engineering discipline, measured — not claimed.
What the suite guards
Honesty gates
Public copy passes a fail-closed screen — forecast words and invented numbers can't ship; pages that can't be verified are withheld.
Money paths fail closed
Checkout, plan gates, and auth refuse on any doubt. A founding client's locked rate is stamped at activation and pinned unchangeable.
Never-send
The machine drafts; a human sends. The only posting trigger is an explicit approve — pinned so it can't regress.
Tenant isolation
Every client sees only their own data; the owner's account is pinned byte-identical across refactors.
Page weight budgets
The funnel pages are asserted under fixed byte budgets with no external scripts — one request to first render.
The plumbing
Writer output shape, webhook retries, rolling-metric math, cron wiring, backup restore drills — each has regression pins.
Every deploy runs the full suite first, smoke-tests the live box, and auto-rolls-back on failure — each ship is a line on the open ledger. The methods behind the public numbers: how we score.