Verify-in-10 (Guide)

Verify the work before you call it “done.” Read the pattern or Run the 10-minute lab. Exit metric: ≥80% of hero clicks go guide → lab and the annex lab runs in ≤10 minutes.

Why it exists

• SLII alignment: moves squads from SLII S3 (supporting) to S4 (delegating) with a clear exit.
• SLI automation: keeps ops/releases/YYYY-MM/manifest.json honest so the State ledger reflects the real stage.
• Receipts: every Verify run posts fresh adoption/quality/credibility metrics.

When to use it

• Moving from Verify → Ready or Ready → Live.
• Rolling out a fix to an existing doc pattern.
• Logging receipts for a monthly release.

The pattern (≤500 words)

1. Scope recorded — SLI stage + guardrail mapping logged. If you’re outside the guardrails, a time-boxed exception lives next to the change.
2. Fold rules hold — Primary/secondary CTA above the first section, Verify guide link visible when the page triggers this contract.
3. Default tests pass — Quick-Run and targeted labs pass; screenshots/terminal logs ready.
4. Receipts posted — Latest pnpm run docs:guard output attached, plus reports/cloudflare-snapshot.json refreshed.
5. State fresh — Manifest metrics updated; pnpm run state:build rerun; PR includes the regenerated bundle + State page.

Need the actionable checklist? Run the Verify-in-10 lab — it walks the same checkpoints in ≤10 minutes.

Anti-patterns

Anti-pattern	Fix
Treating Verify as “go look around”	Follow the lab; it’s small on purpose.
Skipping manifest updates	No manifest update, no release. state:check fails CI.
Double-publishing the checklist	Guide explains why; lab owns the steps. Don’t mix them.

Example receipt

Verify-in-10 · site-v2025.11
- Scope: SLII S3 (Build → Verify), guardrail UI Delivery #2
- Quick-Run + Link Drift labs passed (logs attached)
- Cloudflare snapshot updated YYYY-MM-DD hh:mm UTC
- Manifest metrics updated, state:build rerun

Related references

• Verify-in-10 lab
• SLI States
• State ledger
• Release manifest workflow