Documentation

Use the CLI that ships.

Initialize → check status → read NEXT → publish a reviewed replacement.

v1.0.0-rc.1 prerelease Git-only needs no Muse installation or account.

Current documents

The daily flow

After following the installation guide, set PROJECT_ROOT to an existing Git checkout you are authorized to initialize.

./cli/ok -C "$PROJECT_ROOT" init --vcs git \
  --repo-name PROJECT-NAME --lane product --model 'GPT-6 Astra'
"$PROJECT_ROOT/.overseer/bin/ok" status --json
"$PROJECT_ROOT/.overseer/bin/ok" next

Use the UUID, branch, revision, and next_sha256 reported by status when you publish reviewed task text:

./cli/ok -C "$PROJECT_ROOT" next-write \
  --repo-id UUID-FROM-STATUS --branch BRANCH-FROM-STATUS \
  --lane product --model 'GPT-6 Astra' \
  --action-id REVIEWED-ACTION --action-kind plan \
  --base-head REVISION-FROM-STATUS --expect-next NEXT-SHA256-FROM-STATUS \
  --prompt-file .overseer/local/task.txt

NEXT validates and prints the task. It does not execute it. Use action kind stop when no executable task remains.

The seven public commands

Bounded-v1 command surface
CommandPurpose
statusRead repository identity, runtime, revision, and NEXT status.
initInitialize one checkout with its identity and local handoff files.
syncRefresh the bound launcher and runtime pin after an explicit update.
adoptExplicitly change repository authority or restore preserved configuration.
mirrorPrepare and verify a Muse projection; explicitly deliver its GitHub mirror and pull request.
nextValidate and print the trusted handoff without running it.
next-writePublish a reviewed handoff with exact context and the previous NEXT digest.

Product boundary

A focused local tool

Overseer has no hosted service, desktop runtime, automatic task execution, automatic merge, telemetry, or updater. Hooks are optional and off by default. Older specifications and desktop material remain historical records; current guides describe the bounded v1.