// GUIDE · MAP

A reading map by audience.

What you read first depends on what you're trying to do with Vivarium. Pick one card below and you're 5–30 minutes from running something yourself.

// 01 · MAIN ROUTES

Four persona routes.

The four most common entry points: try it now, integrate it with your repo, drive it from an AI agent, or contribute one reproduction.

Open one recipe in your browser, click once, read the verdict. No install, no account — try it now.

One `.vivarium/manifest.toml` plus a reusable workflow registers a reproduction from your own repository.

Drive the MCP tools from Claude Code / Aider / Cline via `@aletheia-works/vivarium-mcp`.

Copy the closest Layer 1 recipe, swap the bug script, and let the shared helpers keep verdict wiring consistent.

// 02 · ADVANCED

Guides for specific intents that build on the four main routes.

End-to-end flow for verifying an AI agent's candidate fix against a Vivarium recipe. The `verify_branch_fix` MCP tool integrates with this.

For managing private bug recipes inside your org, or trying your own tuning. Includes the GitHub Pages deploy.

Lost on a term? Layer 1/2/3, verdict, manifest, contract, recipe, slug — all collected in the glossary.Glossary