Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Specification Map

This appendix identifies the canonical home of the major DCN concepts and prevents later volumes from silently redefining them.

ConceptCanonical homeRelated volumes
Cross-component ownership and boundariesAdvatar Architecture Constitution v2 (Align), summarized in Constitutional Alignmentall
Architectural invariantsArchitectural Principlesall
Mind and system boundariesVolume IV, X, XI
KLineTemplate / Episode / ArtifactVolume IIVI, VII, IX
CapabilityRequirementVolume II + Cognitive ABI schemaIII, VII, VIII
Actum ComputeVolume IIIIX, XII
Execution/evaluation/promotion ActsVolume IV (promotion and qualification semantics owned by Kline)IX, X
Cognitive KernelVolume VVII, VIII, XII
Agencies and PatchProposalVolume VVII, VIII
World model and memoryVolume VVIII, XII
Compiler SocietyVolume VIIX, XII
Cognitive ABIVolume VII + executable schemasVIII–XII
Computation attestationComputation Attestation Profile + schemaVII, X, XII
Verifiable inference / proof backendsVerifiable Inference + backend contractVI, X, XII
Programming modelVolume VIIIXII
Cognitive Capital economicsVolume IXI, VI, XIII
Trust, authority, securityVolume X (authority facts: Auctor; contextual authorization: Decide; restriction: Defender; release: Action)IV, VII, XI
FederationVolume XIIII, VII, X
Reference implementationVolume XIIall implementation-facing volumes
Public synthesisVolume XIIIall

Normative precedence

When prose conflicts, the following order SHOULD guide editorial resolution:

  1. The Advatar Architecture Constitution v2 and accepted Align ADRs for cross-component ownership, identities and invariants. The book cannot override them.
  2. Architectural Principles for cross-cutting DCN invariants.
  3. The volume designated as canonical home above for concept semantics.
  4. Cognitive ABI and computation-attestation machine-readable schemas for wire structure.
  5. Later implementation guidance only where it does not redefine higher-level semantics.

A newer document does not automatically supersede an earlier canonical definition unless it explicitly records that change.