Client Delivery › C3 spec: Knowledge config
C3 spec: Knowledge config
C3 / L3 Knowledge: what this client reads as true, in their own language, under their data rights.
REQ-K-00, version-pinned by default: every engagement reads one pinned ontology release; nothing reads latest. The promotion gate is always on; there is no configuration that bypasses it.
REQ-K-00, version-pinned by default: every engagement reads one pinned ontology release; nothing reads latest. The promotion gate is always on; there is no configuration that bypasses it.
The ground rules and artifact-placement conventions on the C1 specification apply to every band: values enter once in the binding, everything downstream is generated, nothing is hand-edited. Columns: discovery section, binding key, the exact artifact the value materializes into, when it takes effect, and the check that verifies it.
The configuration map
| ID | Client input | Disc. | Binding key | Materializes as | Takes effect | Verified by |
|---|---|---|---|---|---|---|
| K-01 | Ontology version pin | Kickoff | knowledge.ontology_pin | ontology.lock in the engagement repo; the pinned release loads read-only into the graph store at provisioning | Regression-gated release | Referential-integrity check against the pinned release; client data can never write to the ontology store |
| K-02 | Overlay selection (domain- or function-specific) | B | knowledge.overlay | Overlay release reference in ontology.lock, loaded alongside the base | Regression-gated release | Overlay compatibility check against the pinned base version |
| K-03 | Stage and gate name mapping: the client's lifecycle language | B | knowledge.stage_map{} | Mapping file client-<name>/knowledge/stage-map.yaml consumed by the orchestrator and the renderer's labels | Next run | Completeness check: every ontology stage mapped; a client stage with no ontology home becomes a triage record, never a silent addition |
| K-04 | Benchmark scope and data rights | I | knowledge.data_rights | Machine-readable rights config consumed by the promotion gate; the capture side of the same clause is C1 row E-13 | Contractual | Gate fixture test: unrighted content is blocked from the shared shelf |
Acceptance
- Pin and overlay load green with referential integrity intact.
- The stage map is complete in both directions, with unmapped client stages recorded as triage outcomes (truth, overlay, or conscious contradiction on the Decision Register).
- The rights config is machine-readable and the promotion-gate fixture test passes.