Schematics
Every diagram in the docs on one page, in the order the pieces depend on each other.
In simple words
The drawing set. Every diagram that appears on a concept page is collected here in dependency order, so the whole system can be read in one pass rather than found a page at a time.
Each diagram links back to the page that explains it. If a picture raises a question, that page answers it.
Nothing here is new: these are the same figures, on one sheet.
The types, and what each one holds
Nine types, in the order they depend on each other.
| Type | What it holds | What it points at |
|---|---|---|
| Task | The intent, its checklist, its history | the runs it started |
| Run | One attempt: status, branch, worktree, verdict | a Crew, a Task, a snapshot of a Flow |
| Flow | The ordered recipe, its seats and its loop | its own Steps and Seats, nothing else |
| Step | One phase: kind, stage, inputs, outputs | a Seat, when its kind takes one |
| Seat | A label and a description. That is all | nothing. It is a slot |
| Crew | Your roster, plus two overrides | its Roles |
| Role | Prompt, permissions, skills, the seats it fills | a Profile |
| Profile | Model, effort, token cap, timeout | a Provider |
| Provider | Command, args, env, settings | the binary or endpoint on your machine |
The seam falls between Seat and Role. Everything above it is what a flow ships and can travel; everything below it is yours.
What a flow is made of
A flow is closed: its two references point at its own types. Explained on Flow.
What a profile is made of
The profile is the join, and the only place a model, an effort level, a token cap and a timeout are named together. Explained on Profile.
What a run is made of
Enough state to be resumed, and enough evidence to be audited. Explained on Run.
The default flow
Four steps and one bounded cycle. Explained on Steps.
How a run is driven
Three front doors, one core, one boundary. Explained on Architecture overview.
What one turn does
The box on the right is the part Vibestrate cannot see into, which is why the permission model gates changes rather than commands. Explained on Architecture overview.
How a failed turn is resolved
The class decides which rung the turn enters at, and only hard skips the ladder
entirely. Explained on Safety.
Related
- Architecture overview - how the pieces fit together.
- Repository map - where each module lives.
project.ymlreference - the generated, field-by-field schema.
