Bodies of Knowledge and Canonical Authority¶

01.040.039 v20260810.001

Define the governing architecture and controlled relationships among the Value Realization Body of Knowledge (VRBoK), Alescent Body of Knowledge (ABoK), their principal Frameworks, Canon, Libraries, source material, Perspectives, derivative assets, and the Alescent Legal Framework.

This architecture prevents two opposite failures:

treating every repository artifact as equally authoritative; and
restricting the knowledge system so narrowly that research, developing Practices, Perspectives, examples, evidence, and derivative outputs have no governed place.

Governing Model¶

flowchart TD
    VRBOK[Value Realization Body of Knowledge<br/>VRBoK]
    VRF[Value Realization Framework]
    VRC[Value Realization Canon]
    VRL[Knowledge and Reference Libraries]
    VRS[Source Material and Perspectives]

    ABOK[Alescent Body of Knowledge<br/>ABoK]
    ASF[Alescent Strategic Framework]
    AC[Alescent Canon]
    AVL[Applied Value Library]
    AD[Brand, Website, and Derivative Assets]

    LF[Alescent Legal Framework]

    VRBOK --> VRF
    VRF --> VRC
    VRBOK --> VRL
    VRBOK --> VRS

    VRBOK --> ABOK
    ABOK --> ASF
    ASF --> AC
    ABOK --> AVL
    ABOK --> AD
    ABOK --> LF
    LF -. references and operationalizes .-> AC
    LF -. may incorporate controlled VRBoK terms .-> VRC

Controlled Definitions¶

Body of Knowledge¶

A Body of Knowledge is the complete governed corpus for a defined discipline, institution, or domain. It may include authoritative, provisional, reference, applied, source, historical, and derivative knowledge objects, provided their status and relationships are explicit.

Framework¶

A Framework is an organized system of concepts, relationships, models, principles, rules, methods, and guidance used to understand or govern a subject. A Framework resides within a Body of Knowledge and may contain multiple artifact classes.

Canon¶

Canon is the body of content formally accepted as authoritative within a stated scope. Canon is an authority designation, not an indiscriminate synonym for the complete repository or Body of Knowledge.

Canonical¶

Canonical means formally accepted as controlling within a stated scope. The term may qualify a definition, source, artifact, decision, status, model, or rule.

Canonical Source¶

A Canonical Source is the authoritative source artifact from which derivative expressions must be produced or against which they must be reconciled.

Knowledge Object¶

A Knowledge Object is a governed unit of knowledge, such as a concept, definition, model, principle, Pattern, Practice, Playbook, measure, source record, Perspective, decision, or derivative asset.

Library¶

A Library is a curated collection of reusable knowledge objects. Inclusion in a Library does not by itself confer canonical status.

Source Material¶

Source Material preserves what was submitted, observed, researched, discussed, or received. It supports analysis and traceability but does not become authoritative merely through inclusion.

Perspective¶

A Perspective is a non-canonical exploratory artifact used to develop, question, extend, compare, or challenge existing knowledge. A Perspective may become source evidence for a canonical decision, but it cannot override Canon by itself.

Derivative Asset¶

A Derivative Asset adapts governed source content for a specific audience, channel, context, or use. It inherits meaning from its source and must not silently redefine canonical content.

Knowledge Systems¶

Value Realization Body of Knowledge¶

The VRBoK is the portable and generalized knowledge corpus for Value Realization. Its principal organizing framework is the Value Realization Framework.

Portable doctrine, semantic definitions, general Principles, general Pillars, and other discipline-level constructs belong in the VRBoK. Alescent-specific legal, commercial, operating, institutional, and brand structures do not become portable merely because they apply Value Realization concepts.

Alescent Body of Knowledge¶

The ABoK is the Alescent-specific institutional and applied knowledge corpus. Its principal organizing framework is the Alescent Strategic Framework.

The ABoK may apply, extend, operationalize, commercialize, package, or communicate VRBoK concepts. Where it proposes to change portable doctrine, the change must enter VRBoK canonical governance before it is treated as generally authoritative.

Alescent Legal Framework¶

The Alescent Legal Framework remains a distinct operative framework informed by the ABoK. It may create enforceable rights, obligations, authorities, limitations, assignments, remedies, and relationships.

The Legal Framework is not renamed as a Body of Knowledge. It should reference controlled ABoK and VRBoK terminology where useful, while preserving the priority and interpretation rules of the applicable legal instruments.

Authority Model¶

Authority is explicit¶

Artifact authority must be determined from explicit status, governance, source designation, and scope. It must not be inferred solely from:

repository inclusion;
directory placement;
publication;
formatting quality;
frequency of use;
appearance in a proposal, deck, website, or meeting summary;
existence in downstream knowledge workspace or another downstream system.

Preferred authority statuses¶

Status	Meaning
`canonical`	Formally accepted and authoritative within the stated scope.
`draft`	Under active development and not yet authoritative.
`proposed`	Submitted for review or decision.
`perspective`	Exploratory reasoning or interpretation.
`reference`	Informative and reusable but non-controlling.
`illustrative`	Example or explanatory application.
`derivative`	Produced from governed sources for a defined use.
`deprecated`	Previously used or accepted but no longer preferred.
`superseded`	Replaced by an identified successor.

A workflow status such as implementing or closed does not replace the authority status of the resulting artifact.

Metadata Standard¶

Material knowledge objects should use metadata sufficient to establish system, authority, class, source, and dependency. The preferred pattern is:

knowledge_system: "VRBoK"
authority_status: "canonical"
artifact_type: "Principle"
governing_framework: "Value Realization Framework"
canonical_source: true

For Alescent-specific material:

knowledge_system: "ABoK"
authority_status: "canonical"
artifact_type: "Operating Model"
governing_framework: "Alescent Strategic Framework"
depends_on:
  - "VRBoK"

For non-canonical exploration:

knowledge_system: "ABoK"
authority_status: "perspective"
artifact_type: "Perspective"
canonical_source: false
candidate_destination:
  - "Alescent Strategic Framework"

Metadata adoption may be progressive. Existing documents are not invalid merely because they predate these fields, but material new or substantially revised artifacts should adopt them where practical.

Canonical Review Backlog¶

The Canonical Review Backlog (CRB) is the governance queue for proposed changes, unresolved questions, structural issues, and implementation matters that may affect authoritative VRBoK or ABoK content.

The CRB:

is not itself Canon;
preserves reasoning, source context, decisions, and implementation evidence;
may govern matters spanning the VRBoK, ABoK, Legal Framework, Applied Value Library, or publishing system;
must link to the authoritative artifacts changed after a decision;
retains the acronym CRB and existing repository paths during the transition.

Canonical Development Lifecycle¶

Source, observation, or discussion
        ↓
Perspective or proposed change
        ↓
Canonical Review Backlog
        ↓
Analysis, consultation, and decision
        ↓
Canonical artifact update
        ↓
Validation and Change Register entry
        ↓
Derivative impact review
        ↓
Publication and propagation

Cross-System Rules¶

VRBoK authority. Portable Value Realization definitions and doctrine are governed in the VRBoK.
ABoK authority. Alescent-specific institutional, applied, operating, commercial, and brand knowledge is governed in the ABoK.
No silent redefinition. ABoK artifacts must not silently redefine VRBoK Canon.
Legal operability. The Legal Framework may incorporate knowledge from the ABoK and VRBoK, but executed instruments govern within their legal scope.
Library discipline. Library inclusion does not imply canonical authority.
Perspective discipline. Perspectives remain non-canonical until adopted through governance.
Derivative discipline. Derivative assets must retain source traceability and cannot become authoritative through repetition or publication.
Repository authority. GitHub main remains the authoritative source for repository-governed knowledge. downstream knowledge workspace and other systems are collaborative or downstream mirrors unless explicitly designated otherwise.

Transitional Naming Rules¶

The following path names are retained initially to avoid unnecessary link, build, automation, and integration breakage:

Value Realization Framework/;
Value Realization Framework/Knowledge Library/;
02. Alescent Strategic Framework/Alescent Canon/;
Value Realization Framework/Governance/Canon Review Backlog.md.

Reader-facing titles and descriptions should adopt VRBoK, ABoK, and Canonical Review Backlog immediately. Physical path changes require a separate controlled migration with link, build, automation, and redirect validation.

Review Requirements¶

A material change to this architecture must assess impacts on:

the VRBoK and Value Realization Framework;
the ABoK and Alescent Strategic Framework;
the Alescent Legal Framework;
semantic models and controlled vocabulary;
the CRB, Change Registers, and decision records;
Applied Value Library metadata and governance;
public site names, navigation, and publishing profiles;
downstream knowledge workspace mirrors and queries;
scheduled knowledge-operations prompts;
derivative assets, proposals, and website language.