The public wedge is not a vibe claim. These are the current operator-backed proof points for Sara, launch traction, vertical templates, selective iteration, and deployment reliability on staging.
Sara learning loop
5
multilingual regression briefs passed
Staging has one deployed brief-normalizer prompt that was seeded as an editor-origin candidate, promoted through Sara's regression-backed promoter, and deployed after archived evidence beat the baseline across five Persian, Arabic, Hindi, and Gujarati briefs.npm run sara:proof:staging:editor:deep:required
Persian/Arabic launch traction
0/100
launch-sourced brief submissions
The Persian and Arabic launch pages now preserve acquisition source into signup audit events, direct job payload attribution, and pre-auth launch brief lead attribution. Current proof: 0/100 launch-sourced brief submissions; 0/30 completed launch-sourced sites. Campaign proof: x1-persian-launch 0, x1-arabic-launch 0, Not recorded 0.Next action: Convert 100 more launch-sourced briefs and 30 more completed launch sites.
The latest staging proof window reports 10/10 selective jobs under the spend bar, with copy-only revisions reusing parent artifacts instead of replaying the full model pipeline.npm run iteration:proof:staging
Editor-agent loop
1/3
active editors with merged agent proposals
The multi-editor mechanics are shipped: proposal authorship, bounded concurrent processing, PR attribution, and the leaderboard. Current proof: 1/3 active editors have at least 1 merged editor-agent proposal.Next action: Onboard 2 more active editors with merged editor-agent PRs.
The public /founding-editor form now feeds the N2 proof path. Selected, sent, and first merged editor-agent PR evidence count toward the active roadmap proof without exposing applicant identity. Current application proof: 0/3 selected, 0/3 sent, first PR not merged. Missing criteria: Persian-speaking or RTL reviewer, design background, shipped websites for paying clients. Application sources: X4 founding-editor outreach 0, Public founding-editor page 0.npm run roadmap:proof:active:staging:required
Sara-origin proposals
100%
merged proposals from quality signals
The quality-signal bridge can queue Sara's draft as a normal editor proposal, run one editor-agent cycle, and open the resulting GitHub PR with npm run quality:proposal-cycle:open-pr:staging -- --first-operator. Measure closure with npm run l2:agent-origin-proof:staging. Current proof: 1/1 merged proposals originated from Sara quality signals (100%).Next action: Keep Sara-origin proposals at or above 50% of merged editor proposals.
npm run quality:proposal-cycle:open-pr:staging -- --first-operator
Vertical template depth
10
production template previews guarded
Ten production-capable vertical template previews are live: photographer portfolio, quant strategy, restaurant menu, single-product DTC, freelancer case study, real estate listings, personal brand writer, wedding/event, clinic/dentist, and bilingual local services. Staging smoke now exercises every preview route.
The L4 bar is ten registered specialist templates before Site Machine can claim durable depth beyond the first wedge set. Current proof: 10/10 production vertical templates are registered.npm run l4:template-depth-proof
L4 build depth
10/10
registered templates build-backed
The ten-template registry is visible, but the next engineering depth bar is build/customizer coverage for every registered specialist template. Current proof: 10/10 registered production vertical templates are build-backed.npm run l4:template-build-depth-proof
L4 specialist builds
5/5
specialist templates completed on staging
The five newly registered specialist slugs now have completed staging build artifacts with generated workspaces and no failed validation. This proof is intentionally not counted as X2 prompt-provenance because those held runs used deterministic specialist fallback rather than deployed prompt-version provenance.npm run l4:specialist-build-run-proof:staging
L4 specialist prompts
5/5
specialist templates prompt-backed on staging
The same five specialist slugs now also have completed staging jobs with deployed brief-normalizer prompt provenance recorded in job payloads. This proves the newly registered verticals are no longer only deterministic artifact runs.npm run l4:specialist-prompt-proof:staging
Release reliability
10/7
green staging runs
The active roadmap proof includes the GitHub Actions staging streak, Vercel deploy, URL smoke, and authenticated build-pipeline smoke while N2 and N4 are explicitly parked.npm run roadmap:proof:active:staging:required
Active roadmap state
N1, N3, N5, X2, X3, and X5 are closed with N2/N4 parked.
The current proof board passes with the parked gates excluded. That means the learning mechanism, doc drift fix, creator quality surface, vertical-template prompt proof, selective iteration fast path, and staging reliability proof are closed. Future proof bars are measured publicly. Open future bars: X1 and X4. Closed future bars: L2 and L4. The remaining parked work is business/operator configuration and external proof rather than hidden engineering uncertainty; N2 selected/sent application counts are now visible above.
future roadmap proof
X1 and X4 stay measurable as open future bars.
The future proof report aggregates launch traction, multi-editor loop volume, Sara-origin proposal share, and ten-template depth without weakening the active deployment gate. Closed future bars: L2 and L4. Run npm run roadmap:proof:future:staging to see the staging DB-backed snapshot, run npm run roadmap:proof:future:production to verify the live production board on sitemachine.ai, or inspect the public JSON at /api/proof/future. The public API contract is available at /api/openapi.
N2
Founding-editor external proof
The mechanism exists, and the public pilot page is now shareable at /founding-editor, but the public proof still needs one real external editor to merge one product-improving PR through the agent loop.
N4
Annual Stripe checkout proof
Annual checkout code is wired. The remaining proof is production Stripe yearly price configuration and one real annual checkout. Verify production readiness with npm run stripe:annual-proof:production.
The wedge is visible. Now it needs volume.
The next proof step is real editor and creator repetition: more regression briefs, more real examples per vertical, and one external editor shipping through the loop.