From Bootstrap to 31 Repos

What this means for you

Petrova did not arrive as a launch event. It earned its shape one phase at a time: bootstrap the playbook, prove it on one repo, then onboard others one by one until the same prompts and templates were keeping a fleet of repos in sync.

The pitch

Each phase ships with a written acceptance gate and a friction check before it closes. Nothing waves through. The proof petrova works is that the same loop has now closed on 31 repos in the same workspace.

Who it’s for

The developer evaluating petrova who wants to see receipts, not slides — what was promised at the start of each phase and what actually shipped at the end.

Proof points

• Phase 0 closed end of April: the playbook, its prompts, and the first generated CLAUDE.md / MILESTONES.md / AGENTS.xml triple
• Phase 1 active now: rolling out the same three files to identity, contract, and infra repos in a fixed order
• 31 repos already share one registry and one set of methodology rules
• Every phase close leaves a dated decision doc — the next session can read the trail without asking anyone

timeline
  title Petrova phase cadence
  Phase 0 close : Playbook bootstrapped : First three files generated : Workspace registry seeded
  Phase 1 open  : Onboarding identity, contract, and infra repos : Per-repo bootstrap on a fixed order
  Phase 1 mid   : 31 repos coordinated under one playbook : Weekly health check scheduled
  Phase 2 next  : Tighten how shared-code pointer bumps land : Each bump carries its own paper trail