Canon Consumption Guidelines¶
Purpose¶
Define how product repositories consume and remain aligned to the Value Realization canon, including taxonomy, semantic model, philosophy, and governance constructs.
Canon is authoritative¶
Product repositories must treat the Value Realization Framework taxonomy and semantic model as authoritative controlled vocabulary.
Products should not redefine canon terms. Where product-specific meaning is required, create a product-local term and crosswalk it explicitly.
Pinning strategy¶
Products must pin the canon to a specific revision of this repository.
Accepted patterns include:
- a pinned repository reference;
- a vendored canon folder with a stated sync procedure;
- a release artifact published from tagged releases.
Minimum canon subset¶
At minimum, products should reference:
01. Value Realization Framework/Taxonomy/Value Realization Taxonomy.yaml01. Value Realization Framework/Governance/Naming Policy.md
Where Alescent-specific content is relevant, products should also reference:
Alescent Strategic Framework/Alescent Canon/Semantic Model/Alescent Semantic Model.yamlAlescent Strategic Framework/Applied Value Library/Data Model/Library Item Metadata Model.yaml
Crosswalk discipline¶
If a product introduces internal term variants, it must maintain a crosswalk file.
Crosswalk entries must map product-local terms to canonical terms and state whether the mapping is exact, partial, or deprecated.
Release and compatibility¶
Major canon releases should be tagged as vYYYYMMDD.
Product repositories should reference the tag or commit used at build time.
When the canon changes a definition materially, impacted products must adopt the change or document the incompatibility and maintain a crosswalk exception.