Scenario gallery
Five personas showing how living docs and safety layers compose in practice. Each flow below is different — matching that job’s real path.
dogfood in active use
reference documented pattern
aspirational illustrative only
dogfood
A — Software engineering
Pain: Agents mark features DONE without freeze review; contributors lack honest phase boundaries; merges skip gates.
How the kit helps
- Baseline: Public phase board + handover; design → build gates on every slice.
- Checkpoints: CI and domain tests as gate equivalents before merge.
- Dual control: Independent freeze review (local or API provider in GitHub Actions).
- Optional deepen: Muse mirror for provenance when history stakes rise.
Ship path — freeze before build; CI blocks merge
- Spec freeze
- Independent review
- Auto build
- CI gates
- Merge
Review or CI red → no merge
This repo ships a CI pattern as a template:
freeze-review workflow template
dogfood
B — Video studio
Pain: Remakes, fake approvals, and “done” narration before export gates pass.
How the kit helps
- Baseline: Production status board + handover per video lane.
- Checkpoints: Verify scripts for narration, export, QC.
- Dual control: Independent verifier re-runs gates; human listen-approve on the ledger.
- Optional deepen: Signed approvals + custody pin on Muse when provenance pays for itself.
Production lane — scripts verify; human listens before advance
- Narration
- Export
- QC scripts
↘
- Independent listen
- Status board advance
Any verify fail → remake, no board advance
reference
C — Research paper pipeline
Pain: Fabricated citations and tables that do not match source data.
How the kit helps
- Checkpoints: Source URL + retrieved hash; quote span checks; table regeneration from CSV.
- Dual control: Verifier re-fetches sample sources; verdict binds output SHA.
- Optional deepen: Evidence pack as content-addressed tree for peer review snapshot.
Evidence loop — re-fetch until quotes and tables match sources
- Retrieve + hash
- Quote / table checks
- Verifier re-fetch
↻ mismatch → rewrite from sources
- Bind output SHA → draft
Optional: pin evidence pack for peer review
Domain pack stub — not shipped in kit core.
aspirational
D — Accounting close
Pain: Disputed payouts and reconciliations without dual control.
How the kit helps
- Checkpoints: CSV schema + checksum; reconcile diff thresholds.
- Dual control: Separate prep vs review roles; verifier + human authorization on export.
- Optional deepen: Muse capabilities map to propose vs execute transfers.
Dual control — prep and review stay separate until authorize
- Prep
- CSV + checksum
- Reconcile diffs
- Review
- Re-run checks
- Human authorize
↓ both green
- Export / payout file
Propose ≠ execute on Muse when transfers are live
Illustrative — aspirational domain pack; no kit claim of a production close workflow.
reference
E — Classroom
Pain: Students skip tests and self-mark assignments complete.
How the kit helps
- Baseline: Freeze → build → verification discipline on every assignment.
- Checkpoints: Optional assignment gates (tests green, no secrets in repo).
- Dual control: Optional TA verifier session before grade publish.
- Optional deepen: Student Muse identity for portfolio provenance.
Teacher sets the rails; student work cannot self-grade
- Teacher
- Install kit
- Freeze assignment
→ handoff
- Student
- Build
- Tests green
- TA verify
- Grade publish
Later lesson: optional Muse pin for portfolio history
Traffic story: Teacher installs on GitHub; later lesson offers optional Muse deepen for signed portfolio history.