Scenario gallery

Five original persona flows showing how a trusted repository handoff can support different work. Domain checks remain examples owned by each project.

supported uses shipped CLI behavior reference project-owned pattern illustrative example only

supported

A — Software engineering

Pain: A new agent session starts in the wrong checkout or follows a handoff written for an older revision.

How the kit helps

Baseline: Repository-bound status plus one validated NEXT handoff.
Project checks: CI and domain tests remain owned and run by the repository.
Operator review: The team reviews the task, work, and merge; Overseer does not approve them.
Optional Muse: Select Muse authority and a controlled GitHub mirror when that model fits.

Ship path — validate context, do the work, then use the project’s normal review

Reviewed NEXT
Status matches
Agent works
Tests + review
Merge

Context mismatch → stop; failed project checks → no merge

Start with the shipped local workflow: Git-only quickstart

reference

B — Video studio

Pain: A session resumes from stale production notes, and project-specific QC steps are easy to miss.

How the kit helps

Baseline: One repository-bound NEXT identifies the reviewed production task.
Project checks: The studio may keep its own narration, export, and QC scripts.
Human review: A listener can approve the export through the studio’s own process.
Optional Muse: Muse authority can retain repository history; the kit does not ship a video workflow.

Example production lane — project scripts and human review remain external to the kit

Narration
Export
QC scripts

Independent listen
Publish through studio process

Any project check fails → revise before publish

reference

C — Research paper pipeline

Pain: A research session loses its source context or continues from stale task instructions.

How the kit helps

Project checks: A research repository may record source URLs, hashes, quote spans, and regenerated tables.
Human review: A researcher can re-fetch sources and compare the draft with project evidence.
Optional Muse: Muse authority may preserve repository history when the team chooses it.

Evidence loop — re-fetch until quotes and tables match sources

Retrieve + hash
Quote / table checks
Verifier re-fetch

Bind output SHA → draft

Optional: pin evidence pack for peer review

Illustrative project workflow — research checks are not shipped in kit core.

illustrative

D — Accounting close

Pain: A close process resumes without a clear repository handoff or current reconciliation task.

How the kit helps

Project checks: An accounting repository may define CSV schemas, checksums, and reconciliation thresholds.
Human control: Separate preparation and review roles authorize any financial export.
Boundary: Overseer does not execute transfers, enforce roles, or provide an accounting domain pack.

Dual control — prep and review stay separate until authorize

Prep
CSV + checksum
Reconcile diffs

Review
Re-run checks
Human authorize

Export / payout file

Illustrative only: financial authorization stays outside Overseer

Illustrative only — no kit claim of a production accounting workflow.

reference

E — Classroom

Pain: Students resume from copied or stale instructions and may skip the teacher’s project checks.

How the kit helps

Baseline: A repository-bound NEXT carries the teacher’s reviewed assignment task.
Project checks: The course may require tests and secret scanning before submission.
Human review: A teacher or TA reviews the work; Overseer does not grade it.
Optional Muse: A course may choose Muse authority; Git-only remains fully supported.

Teacher sets the rails; student work cannot self-grade

Teacher
Install kit
Freeze assignment

Student
Build
Tests green
TA verify
Grade publish

Optional later lesson: choose Muse authority explicitly

Boundary: This is an example teaching pattern. The kit ships repository context and handoff commands, not a classroom platform.