Guide
Worked Example: Adopting the Library into a Running Programme
This walkthrough follows one fictional organization from cloning the library through its first year of operating a governance programme, showing the file-by-file decisions an adopter makes at each stage. It is the companion to docs/worked-example.md, which walks the opposite direction (converting a draft into a library artefact): that example is for contributors, this one is for adopters. It does not restate the adopter tooling. It references docs/template-quickstart.md, docs/template-startup-roadmap.md, docs/template-implementation-roadmap.md, docs/decision-tree.md, and docs/adopter-guide.md at each step, and shows how they fit together for a single concrete adopter.
- Type
- Guide
- Version
- 1.0.2
- Date
- 2026-10-24
- Owner
- Governance Library Maintainer
- Approving authority
- Governance Library Maintainer
- Classification
- Public
- Confidentiality
- Public
- Category
- Documentation
- Review frequency
- Annual and upon material change to the adopter guide or the adoption tooling
- Licence
- CC BY-SA 4.0
Read the full text on GitHub (opens in a new tab)
Outline
- The adopter
- Step 1: Clone or fork
- Step 2: Copy the Day-1 six-artefact floor
- Step 3: Substitute roles and identifiers
- Step 4: Phase 1 (days 1 to 90), reach the floor
- Step 5: Phase 2 (days 91 to 180), operationalize and add AI
- Step 6: Year-1 close and tracking upstream
- Common pitfalls
- Summary
Related documents
- Worked Example: Converting a Draft into a CC BY-SA 4.0 Artefactdocs
- Adopter Guidedocs
- Adopter Quickstart Templatedocs
- Adopter Startup Roadmap Templatedocs
- Adopter Implementation Roadmap Templatedocs
- Adopter Decision Treedocs
Next
All Documents