Concepts

Three documents shape how to think about Unibench. They're worth reading in order on first encounter; the rest of the docs assume this vocabulary.

• The four principles — the product decisions that drive what Unibench is and isn't.
• The project model — what a project is on disk, what state the daemon owns, how lifecycle phases work.
• The recipe model — what add-on recipes are, why they're additive-only, and where the boundary sits between recipes and seed scripts.

Once you have a feel for these, the rest of the docs are reference:

• Manifest reference — auto-generated from the typed manifest.
• Service-type reference — per-service defaults, exposed knobs, inspection-drawer contents.
• Recipe library — per-recipe docs.
• Troubleshooting — common failures + workarounds; the agent handles the long tail.