PETROVA
A control plane with a thin centre. Methodology in the middle, project truth in each repo.
Where to start
Section titled “Where to start”| If you want to… | Go to |
|---|---|
| Understand the system in one screen | What is PETROVA? |
| Install + run the CLI | Quickstart |
| Build the mental model | Concepts |
| Use the action surface | Verb reference |
| Read the cross-cutting invariants | Meta-rules (MR-1..MR-12) |
| Operate it (onboard, auth, recover) | Operator runbooks |
| Plug an agent fleet in | Integration contracts |
| See why it’s shaped this way | Architecture |
| Load drop-in agent skills | llms.txt (skill catalogue at the top) |
The shape, in one diagram
Section titled “The shape, in one diagram”agent fleet ──verb call──▶ PETROVA ──PR──▶ consumer repoReads flow freely; writes go through the typed verb layer. Boundary diagram is the load-bearing mental model.
The three load-bearing invariants
Section titled “The three load-bearing invariants”- MR-7 — decisions are append-only, dated, in-repo.
- MR-10 — verification rounds are mandatory at phase close.
- MR-12 —
CLAUDE.mdis a projection, not a source.
The other nine MRs scope-shape and clarify; these three are substrate. Without them, the audit trail isn’t real.