Repository ledger · canonical docs surface
Babysitter, documented like the system actually runs.
Built straight from ./docs. User guide, setup guides, process design, plugins, and research all live in one auditable source of truth instead of a second marketing-shaped copy of the repo.
/babysitter:call add tests and gates
Iteration 1 -> code + tests
Iteration 2 -> verify failures
Iteration 3 -> converge to target
Result: documented, replayable, reviewableNavigate by intent
Pick the shortest path to the answer you need.
Start Fast
Install Babysitter, configure your harness, and run the first orchestration loop without digging through the whole repo first.
Run The System
Jump straight into the command surface: runs, tasks, sessions, plugins, harnesses, and process-library controls.
Know The Surfaces
See which packages and plugins are public, advanced/operator-facing, or internal-only, then jump to the canonical docs home for each one.
Design Better Processes
Learn how Babysitter turns prompts into bounded, replayable workflows with explicit gates and deterministic evidence.
Ship With GitHub Actions
Use the docs and CI setup guides to connect Babysitter orchestration to your repository workflows and review loops.
Why this site shape
One docs tree, one build, one deployment path.
Source-first
The site is built from the repository docs tree, so process guidance, setup material, and reference pages do not drift from the codebase.
Replay-aware
The docs match how Babysitter works: iterations, evidence, approvals, and deterministic convergence instead of vibes-only automation.
Operator-friendly
Quickstart paths, CLI reference, plugins, and deployment guides are grouped around the real questions users hit while running the system.