SCENARIOS
Examples of how the bounded CLI can fit into your work.
These are illustrative scenarios, not claims of shipped project integrations or additional automated features. You choose the task and decide when to publish it.
Two similar projects
You switch between similar repository folders. Run the repository-bound launcher in the intended checkout before copying NEXT. Identity and physical-root checks refuse a foreign binding or copied handoff.
status → next
Returning to a branch
A task written before a branch switch or later commit may be stale. Check status and NEXT. Review what changed, then explicitly publish a replacement against the current revision and prior NEXT digest.
status → next → next-write
A Git-only developer
Initialize a Git checkout and read its handoff locally. Git-only operation is permanent and needs no Muse package, account or later migration.
init → status → next
A team choosing Muse
Review adoption and rollback guidance, prepare the separate pinned Muse environment, and preview the change. Explicit adoption changes the selected authority; the appearance of Muse metadata alone never changes a Git binding.
adopt
A maintainer publishing source
With Muse selected, prepare a reviewed projection, verify the source and destination identities, and explicitly deliver the mirror. Delivery can create a pull request; the operator remains responsible for review and merge.
mirror
Git-only quickstart · Explicit adoption and rollback · Controlled mirroring
v1.0.0-rc.1 is a prerelease. No hosted service, desktop runtime or automatic task execution is involved.