Overseer Kit v1 documentation
Start with the repository README.md. It describes installation, initialization,
daily use, handoff publication, update notifications, and current limitations.
Current documents
| Document | Purpose |
|---|---|
| Scope reset | Authoritative bounded-v1 product scope |
| Validation | Reviews, test results, installation/rollback, and consumer pilot evidence |
| Muse restoration audit | Corrected Muse-first scope, reproduced gaps, architecture, and restoration plan |
| Canonical NEXT format | How v1 reads and publishes the sole handoff |
| Explicit adoption and rollback | Git/Muse selection, local exclusions, config migration and rollback |
| Roadmap | Current milestone summary; never a prompt source |
| Handover | Current evidence summary; never a prompt source |
| Test scope | Supported and historical test boundaries |
Historical material
The October 2026 scope reset superseded the former hosted/desktop product, multi-repository orchestration, freeze/ledger gates, governance-sync, publishing commands, OCI/registry design, and automatic recovery machinery.
Older specifications, runbooks, landing pages, templates, skills, policies, tools,
and phase records remain in this repository as historical source and evidence.
Unless a current document above explicitly incorporates them, they do not describe
the v1 command surface and should not be followed as installation or operating
instructions. cli/legacy_main.py preserves the former CLI source; cli/main.py
exposes only bounded v1.
The owner corrected the mistaken exclusion of MuseHub authority and GitHub mirroring. R1 implements optional local Muse handoffs and adoption; mirror repair and combined validation are pending. The historical bridge has known audit findings; its runbook is evidence, not a currently approved publication procedure.