🆗 Overseer Kit

Phased AI work without amnesia, fake DONE, or silent drift — on plain GitHub.

Optional MuseHub depth when you need provenance, signed identity, and non-invertible history.

The problem

AI-assisted development breaks down at the boundaries between sessions:

• Amnesia — each new chat re-derives context from scratch.
• Self-approval — agents mark phases DONE without independent verification.
• Silent drift — roadmaps and handovers fall out of sync with reality.
• Skipped tests — expensive remakes when mechanical gates are bypassed.

🆗 Overseer Kit makes skipping honesty expensive — not by running your product, but by governing how phased work proceeds.

L0 in 60 seconds — roadmap + handover

Every repo gets a living ROADMAP (phase control board) and HANDOVER (session relay with one next step). Fresh AI sessions paste the handover prompt instead of guessing.

./cli/overseer init --regime git-only
./cli/overseer governance-sync --dry-run
./cli/overseer status

L0 alone is useful on any GitHub repo. No Muse install required.

Add L1 — mechanical checkpoints

When artifacts are measurable (media exports, test suites, data transforms), L1 runs verify scripts before the pipeline advances.

Domain logic stays in your verify scripts — the kit ships the orchestrator socket, not video QC or accounting rules.

Add L2 — boss / worker / checker

When handoffs involve money, publish, or audit stakes, L2 adds role-gated verdicts on an append-only ledger.

Producers cannot self-certify. Verifiers run in independent sessions. Tampering breaks the chain.

Optional L3 — MuseHub substrate

Same CLI commands. When you flip to muse+git-mirror, you gain content-addressed history, safe GitHub mirror export, and drift realign — without gating L0–L2.

Guardrail: no core governance feature is MuseHub-only. Git-only is a first-class baseline.

Modularity — lanes, modules, domain packs

Who it is for

See the full scenario gallery →

Quickstart — git-only in 5 minutes

1. Clone overseer-kit.
2. From your consumer repo: ./cli/overseer -C . init --regime git-only --non-interactive
3. Open docs/OVERSEER-HANDOVER.md → copy the paste-ready prompt.
4. Run ./cli/overseer governance-sync --dry-run before ending each session.

Full guide: Git-only quickstart · Consumer pattern: CONSUMER-ADAPTER-PATTERN.md

MuseHub upgrade path

When provenance matters, flip regime — same commands, deeper history:

1. Install Muse and run muse init in your repo.
2. Set regime: muse+git-mirror in .overseer/config.yaml.
3. ./cli/overseer sync — seeds bridge workflow + safe deploy script.
4. Day-to-day: muse commit on feature branches. Publish via scripts/muse-bridge-deploy.sh only.

Operator runbook: K7 dogfood runbook

Public roadmap

Full ROADMAP.md

GitHub → Kit → MuseHub

Start where you are. Add layers when stakes rise. Upgrade substrate only when provenance pays for itself.

Not another agent framework. Governance + honesty for people who already use Cursor and GitHub.