Docs
Start with the honesty loop: freeze and challenge the plan, build accepted phases, review the implementation, then hand over what is actually true.
On this site
- How it works — plan review, phased build, completion review, and truthful handover
- Structure — ROADMAP/HANDOVER lanes, safety layers, and optional repository authority
- Get started — read the source guide, freeze the plan, build, verify, and hand over
- Scenario gallery — the same governance loop applied to different kinds of work
Start the workflow
- Read the manual source delivery guide. Acceptance applies to its pinned snapshot; the integration candidate is later work.
- In an already initialized project:
.overseer/bin/ok -C "$PROJECT_ROOT" next --lane product. Check the returned project, revision, lane and model. Existing-project installation remains on hold. - Write bounded phases in ROADMAP, freeze the outputs and acceptance evidence, then resolve findings from a separate agent chat or human reviewer before build.
- Build the accepted phases, run project-owned checks, and have a separate reviewer compare the result with the freeze before DONE. Update ROADMAP and HANDOVER to match reality, then use
next-writeto carry the reviewed next task forward.
The reviews are independent actions performed by your chosen agent session or human reviewer. The maintained CLI supplies review, verification, evidence and handover tools; it does not appoint the independent reviewer or enforce an agent vendor’s tool permissions. The rc.1 prerelease is an earlier bounded CLI, not this full-product delivery.
GitHub docs
Current guides, living-document templates, and the full documentation tree live in the repository. Repository, revision, and NEXT checks support the governance loop; they are not its purpose. This public website does not run Overseer, execute prompts, perform reviews, or access a repository.