Guide
Adopting the Library Across a Group or Multi-Entity Structure
The docs/adopter-guide.md and its worked example docs/worked-example-adoption.md show a single organization adopting the library. A group, holding company, or multi-entity structure has a further decision the single-entity guidance does not address: how to adopt the library across several legal entities that share governance but differ in jurisdiction, sector, and regulatory exposure. This guide adds that topology layer. It composes the corpus's existing group-scope precedents, the jurisdiction-annex layering model, and the versioning policy by cross-reference; it does not restate the single-entity adoption mechanics, for which the adopter guide governs.
- Type
- Guide
- Version
- 0.0.1
- Date
- 2026-07-09
- 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 versioning policy
- Licence
- CC BY-SA 4.0
Read the full text on GitHub (opens in a new tab)
Outline
- Purpose
- The three adoption topologies
- Versioning and the CalVer surface per topology
- Role mapping when governance authorities differ per entity
- Jurisdictional layering
- Trade-offs per topology
- Limitations and cross-references
Related documents
- Adopter Guidedocs
- Adopter Decision Treedocs
- Worked Example: Adopting the Library into a Running Programmedocs
- Adopter Implementation Roadmap Templatedocs
- Role Authority Registergovernance
- Privacy Jurisdiction Indexprivacy
Next
All Documents