Beta Coverage & QA Ledger

Why this exists:

• Keep the Beta playground honest — every scratch pad should cite a canonical briefing before anyone touches schema or Supabase.
• Track which experiments are simply references vs. ready to wire so we don’t mis-prioritize engineering time.
• Provide a single QA checklist when we “trust but verify” Phase 0 drops.

Rendered in product at /beta/coverage with the underlying data shared in apps/stps/src/lib/stps/beta/experiments.ts.

Snapshot (Nov 2025)

• Streams: Presets (5), Schema (5), Sessions (4), Architecture (7), AI & Data (4).
• “Ready for wiring” = docs + Beta page ready; waiting on adapters/storage.
• “Reference only” = intentionally narrative/spec level (no backend commitments yet).

Coverage notes

1. Shared data file — All experiment metadata (docs, phase focus, next action) lives in beta/experiments.ts. Pages, coverage, and ops board pull from it.
2. Docs cross-linking — /beta/coverage shows which experiments cite methodology-summary, phase0-checklist, claude-overview, etc. All 25 experiments now have references.
3. Phase tracking — Each entry has a phaseFocus string so we can see the rollout ladder at a glance. Use it to flag scope creep before we touch Phase 3 items.
4. Next moves — Table rows list the concrete follow-up (e.g., “wire preset simulator into generator”, “add ceiling enforcement to Supabase policies”).
5. Ops board — /beta/ops-telemetry replaces the “missing board” TODO; update it alongside the coverage ledger whenever migrations or flags change.
6. Schema lint in CI — npm --workspace apps/stps run test now runs lint:schema before the existing test suite, so Blueprint ↔ schema drift blocks builds automatically.

QA checklist

1. Docs first — Update the relevant briefing (methodology-summary, process-summary, etc.) before adjusting a Beta page.
2. Beta sanity — After editing, load both /beta and /beta/coverage to ensure:
   • The page appears in the correct tab/category.
   • The coverage table shows the right status, doc links, and next move.
3. Snapshot integrity — When a flow is “Ready for wiring”, translate it into:
   • Supabase schema or seed updates (generate:phase0-seed).
   • Convex store/provider changes (so Phase0Provider parity stays intact).
4. Deployment rehearsal — Re-run the Phase 0 checklist steps (feature gate, auth prompt, env vars) before sharing builds with stakeholders.

Gaps / new ideas

• Automated lint — npm --workspace apps/stps run lint:schema now checks node kinds vs. blueprint (allows future collection node). Wire it into preflight checklists.
• Preset health — /beta/coverage now exposes sample snapshots (pass/warn). Next: wire into live Preset Lab runs + seed generator tests.

Use this file + /beta/coverage whenever the context window feels overloaded. It’s the quick “are we done thinking before building?” litmus test.