Skip to content

Value Realization Semantic Model

01.020.000 v20260803.002

Change Log

The Value Realization Semantic Model is the machine- and agent-oriented semantic layer for the Value Realization Body of Knowledge and its principal organizing Value Realization Framework.

It includes ontology, taxonomy, controlled vocabulary, rules, inference guidance, LLM instructions, generated context, authority and lifecycle semantics, and related governance.

Knowledge Architecture Responsibilities

The Semantic Model must preserve the distinctions among Bodies of Knowledge, Frameworks, Canon, canonical sources, Knowledge Objects, Libraries, Source Material, Perspectives, Derivative Assets, authority and lifecycle status, and the distinct Alescent Legal Framework.

It must also preserve distinctions among:

Taxonomy Migration State

The legacy authoritative taxonomy remains at:

Value Realization Framework/Taxonomy/Value Realization Taxonomy.yaml

That path remains active to avoid breaking generation, publishing, linking, validation, and agent-context scripts.

New semantically complete taxonomy modules may be maintained under this Semantic Model where they identify their synchronization relationship to the legacy taxonomy. The first such module is:

020. Taxonomy/Maturity Progression Effort and Play Taxonomy.yaml

The legacy Value Realization Taxonomy remains the controlling machine-readable taxonomy. The scoped module supports coherent development and generation of the maturity, Progression, Effort, Play, and Playbook terms and is synchronized into that authoritative taxonomy. It must not be treated as a competing canonical source.

Implemented Ontology and Vocabulary Artifacts

Ontology

  • 010/010.md
  • 010/020.md
  • 010/030.md
  • 010/020/010.md
  • 010/020/020.md
  • 010/020/100.md

Taxonomy

  • legacy authoritative taxonomy at ../Taxonomy/Value Realization Taxonomy.yaml
  • 020. Taxonomy/Maturity Progression Effort and Play Taxonomy.yaml, a scoped source module synchronized into the authoritative taxonomy
  • 020. Taxonomy/Effect Reference Taxonomy.yaml, a scoped source module synchronized into the authoritative taxonomy

Controlled Vocabulary

  • 030/010.md
  • 030/020.md
  • 030/030.md

Synchronization Rule

A term or relationship must not remain governed by competing definitions.

Where a new semantic module is introduced:

  1. the module must identify its governing scope and source status;
  2. the ontology, taxonomy, controlled vocabulary, and human-readable doctrine must use consistent definitions;
  3. legacy taxonomy and generated views must be synchronized or explicitly marked as pending migration;
  4. ABoK semantic extensions may specialize but must not silently redefine portable VRBoK terms;
  5. build, publishing, validation, and agent-context routines must be updated where the new path is exposed.

Metadata Guidance

Material knowledge objects should identify their knowledge system, authority status, artifact type, governing framework, canonical-source status, and dependencies where practical.

Example:

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

Alescent-specific example:

knowledge_system: "ABoK"
authority_status: "reference"
artifact_type: "Progression Pattern"
governing_framework: "Alescent Strategic Framework"
depends_on:
  - "01.030.031.020"

Intended Structure

  • 010. Ontology/
  • 020. Taxonomy/
  • 030. Controlled Vocabulary/
  • 040. Rules and Inference/
  • 050. LLM Instructions/
  • 060. Generated Context/
  • 900. Governance/

Governance

Semantic changes require synchronized review of doctrine, ontology, taxonomy, controlled vocabulary, registries, public navigation, derivative assets, and generated agent context.

Generated files must be regenerated through the repository routines rather than edited directly.