Scenario gallery
Five personas showing how L0→L3 layers compose. Badges indicate maturity — not every scenario is production-validated in the kit repo.
Badge key:
dogfood in active use ·
reference documented pattern ·
aspirational illustrative only
dogfood
A — Video studio
Pain: Remakes, fake approvals, and “done” narration before export gates pass.
Layer usage
- L0: Production status board + overseer handover per video lane.
- L1: Verify scripts for narration, export, QC —
verify-step orchestrator.
- L2: Independent verifier re-runs gates; human listen-approve on ledger.
- L3: Optional signed approvals + custody pin on Muse.
Human → Producer → L1 verify scripts → Verifier → Status board
↓ fail = no advance
optional Muse custody pin
Reference consumer: VideoFactory setup
reference
B — Research paper pipeline
Pain: Fabricated citations and tables that do not match source data.
Layer usage
- L1: Source URL + retrieved hash; quote span checks; table regeneration from CSV.
- L2: Verifier re-fetches sample sources; verdict binds output SHA.
- L3: Evidence pack as content-addressed tree for peer review snapshot.
Domain pack stub — not shipped in kit core.
aspirational
C — Accounting close
Pain: Disputed payouts and reconciliations without dual control.
Layer usage
- L1: CSV schema + checksum; reconcile diff thresholds.
- L2: Separate prep vs review producer roles; verifier + human Tier-3 on export.
- L3: Muse capabilities map to propose vs execute transfers.
Illustrative — aspirational domain pack; no kit claim of production close workflow.
reference
D — Classroom / Scooling
Pain: Students skip tests and self-mark assignments complete.
Layer usage
- L0: Freeze → Auto → build-verification discipline on every assignment.
- L1: Optional assignment checkpoints (tests green, no secrets in repo).
- L2: Optional TA verifier session before grade publish.
- L3: Optional student Muse identity for portfolio provenance.
Traffic story: Teacher installs on GitHub; later lesson offers MuseHub upgrade for signed portfolio history.
dogfood
E — Multi-org open source
Pain: Maintainer merges without freeze review; contributors lack honest phase boundaries.
Layer usage
- L0: Public ROADMAP + HANDOVER; Thinking → Auto gates.
- L1: CI runs domain tests as checkpoint equivalents.
- L2: Freeze review API provider in GitHub Actions (
provider: api).
- L3: Optional mirror to Muse for provenance badge (mirror branch SHA).
This repo dogfoods the pattern: freeze-review workflow · K9–K12 roadmap