Handbook
Platform playbook for Blueprints across many repos
Enablement- or architecture-led rollout: playbook for new repos, governance for Blueprint policy exceptions, and leadership messaging when needed.
What it is
Enablement- or architecture-led rollout: playbook for new repos, governance for Blueprint policy exceptions, and leadership messaging when needed.
Parent page: Team rollout patterns.
When to use it
Many products must pin the same upstream and leadership needs visibility.
Prerequisites
- Multi-team practices or equivalent governance buy-in.
Focus
| Aspect | Guidance |
|---|---|
| Playbook | How new repos get blueprints/, sdlc/, Forge, and Cursor alignment — link to Project setup checklist. |
| Governance | Who approves exceptions to frozen baseline rules; how long they stay open. |
| Leadership | Category and MVP narrative for executives — use Adopting Blueprints — Path C (step 3) when you need a stakeholder-facing line into that material. |
Org-wide phased timeline (example)
| Quarter phase | Focus | Success signal |
|---|---|---|
| Define | Playbook + golden SHA policy | New repos follow the same checklist |
| Enable | Office hours and governance cadence | Questions cluster in known forums |
| Measure | Exceptions count and time-to-bump | Few long-lived forks of baseline text |
Risks and mitigations
| Risk | Mitigation |
|---|---|
| Playbook ignored | Template repo or scaffold that runs the same first steps |
| Exception creep | Time-boxed waivers with owners |
Anti-patterns
| Anti-pattern | Better |
|---|---|
| Central team edits product repos without a ritual | Published playbook + self-service with review |
| “Everyone on latest” without support | Staged rollout with pilot services first |
Example scenario (new service line)
| Starting situation | A new division spins up ten greenfield services over a year. |
| Action taken | Platform publishes the consumer playbook once; each service follows Project setup checklist and the same bump cadence. |
| Expected result | Services share vocabulary; leadership sees one story, not ten variants. |
| What to check | Architecture review references the same Team rollout patterns vocabulary. |
How to verify success
New services reach parity without custom edits inside blueprints/; exceptions are rare and documented.