Scenarios
Fewer context mistakes.
More deliberate handoffs.
These are examples of how the bounded CLI can fit into real work. They are not claims of shipped integrations or automatic features.
v1.0.0-rc.1 prerelease
Two similar projects
Prevent a prompt from the wrong project
You switch between similar repository folders. The repository-bound launcher checks the persistent UUID and exact physical root before printing NEXT. A copied configuration or foreign handoff stops.
status → next
Returning to a branch
Resume against the right revision
A task written before a branch switch or later commit may be stale. Check status and NEXT, review what changed, then publish a replacement against the current revision and previous NEXT digest.
status → next → next-write
A Git-only developer
Keep the tools you already use
Initialize a Git checkout and read its handoff locally. Git-only operation is permanent and requires no Muse package, account, or later migration.
init → status → next
A team choosing Muse
Choose repository authority explicitly
Review adoption and rollback guidance, prepare the separate pinned Muse environment, and preview the change. Muse metadata by itself never changes a Git binding.
adopt
A maintainer publishing source
Inspect a controlled GitHub mirror
With Muse selected, prepare a reviewed projection, verify both source and destination identities, and explicitly deliver the mirror. Delivery may create a pull request; the operator reviews and merges it.
mirror
Start with your own repository.
Git-only quickstart · Muse adoption and rollback · Controlled mirroring
Overseer does not choose the task or run it. This website is informational and does not run Overseer.