PETROVA
A control plane with a thin centre. Methodology in the middle, project truth in each repo.
npx @petrova/cli status
flowchart LR
AF["Agent Fleet"] -->|"verb call"| P["PETROVA<br/>(control plane)"]
P -->|"PR"| CR["Consumer Repo"]
Reads flow freely through the verb layer. Writes are gated by typed verbs and land as pull requests in the governed consumer repo. The boundary diagram is the load-bearing mental model.
Where to start
- CONCEPT What is PETROVA? Understand the system in one screen.
- QUICKSTART Quickstart Install and run the CLI.
- CONCEPTS Concepts Build the mental model.
- REFERENCE Verb reference The full action surface.
- INVARIANT Meta-rules The cross-cutting MR-1..MR-12 set.
- RUNBOOK Operator runbooks Onboard, auth, recover.
- INTEGRATION Integration contracts Plug an agent fleet in.
- ARCHITECTURE Architecture Why it's shaped this way.
- SKILLS llms.txt Drop-in agent skill catalogue, at the top.
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.