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

Constitutional Alignment

DCN is one component of the Advatar architecture. Cross-component ownership is governed by the Advatar Architecture Constitution v2, which is maintained in the Align repository (ARCHITECTURE_CONSTITUTION.md, machine-readable contract contracts/architecture-constitution-v1.json, contract version 2). It is accompanied by these Architecture Decision Records:

ADRSubjectEffect on this book
ADR-0001Kline ↔ DCN bidirectional capability compositionK-lines consume DCN-selected capabilities; DCN may select Kline-provided capabilities. Superseded in part by ADR-0002.
ADR-0002Cognitive routing, contextual authorization, point-of-effect enforcementDefines Constitution v2: Kernel routing vs Kline qualification vs DCN selection; Auctor facts vs Decide authorization; Causal observation vs Action release; Effect/attempt/evidence identities.
ADR-0003Exact-artifact qualification evidenceA SolutionOffer is not qualification evidence. Qualified reuse needs an authenticated Qualification Evidence Reference bound to the exact artifact digest.
ADR-0004Governed Execution Manifest /1 (additive, proposed)Binds an immutable workflow/build and its source commitments to an exact Effect Instance without changing ownership.
ADR-0005Provider statements are not hosted-service qualification (additive, proposed)Authenticated provider statements are not qualification and give a hosted service no qualified-reuse admission.

Precedence. The constitution sits above every volume of this book. Where a volume uses older terms or describes a responsibility differently, the constitution governs and the volume should be read in its light. This book does not move ownership. A change that appears to need a boundary moved requires an accepted Align ADR and a constitution version change before any dependent specification or code.

Responsibility map

Logical responsibilityOwnerBoundary
Canonical semantic transition identityEffectWHAT consequential transition is proposed; distinct from attempt and evidence identities
Reusable solution / K-line qualification and lifecycleKlineapplicability, qualified offers, evaluation, promotion, lifecycle
Contextual System 1 / System 2 routingMind-local Cognitive Kernelreuse, deliberate, defer or escalate now
Distributed capability fabricDCNdiscovery, admissibility, composition, provider/location selection and placement
Authority facts and constraintsAuctordelegation, membership, authority facts and evidence
Contextual authorizationDecidewhether the exact Effect/attempt is authorized now
Safety / containment restrictionDefendernegative-only: preserve, restrict, step up, block; never widen
Independent observation and specialized enforcementCausalobserved context/evidence and enforcement-provider mechanisms
Point-of-effect enforcement and releaseActionfinal generic release boundary and execution coordination
Cross-component architecture and orchestrationAligncontracts and governance; does not absorb component semantics

Kline, or another target that DCN selects, performs the computation. Computation, model output and successful execution never create authority.

The two roles hosted in this repository

The DCN repository hosts two logically distinct concerns. They must be kept distinct even though they share a codebase:

  1. The Mind-local Cognitive Kernel (Volume V) owns contextual System 1 / System 2 routing. Given the current request and Mind context, it decides whether a qualified offer from Kline should be reused, or whether to deliberate, defer or escalate.
  2. The DCN capability fabric (Volumes III, VII, XI) owns distributed discovery, admissibility, composition, selection and placement of capabilities. Either System 1 or System 2 may send it capability requirements.

Capability selection cannot promote, demote, activate or otherwise mutate K-line lifecycle state.

Hosted semantics. Some code in this repository implements K-line composition, promotion and lifecycle. That is Kline-owned semantics hosted in DCN, pending an architectural disposition. Where Volumes II, IV and VI describe promotion, evaluation and lifecycle, they describe Kline's responsibilities, whichever repository the code currently lives in. Repository location does not determine logical ownership.

Cognitive plane

New request + current Mind context
              │
   Mind-local Cognitive Kernel
              │
   Kline retrieval / qualification
              │
   contextual cognitive routing
       ┌──────┴──────┐
    System 1       System 2
  qualified       deliberate / discover /
  reuse           compose / synthesize
       └──────┬──────┘
     capability requirements
              │
      DCN capability fabric
              │
      admissible bindings
  • Kline supplies qualified reusable-solution offers. The Kernel decides whether a qualified offer is appropriate in the current context.
  • System 2 is not synonymous with synthesis. It may also reuse, discover and compose.
  • A successful System-2 trajectory is at most a candidate. It becomes a K-line only after Kline evaluates and qualifies it and finds the promotion evidence valid.
  • "No adequate qualified solution" and "lookup or infrastructure failure" are distinct outcomes. A failure never silently justifies weaker constraints or a fall back to System 2.
  • Nested Kline/DCN resolution is cycle-bounded. It propagates invocation context, budgets, deadlines and provenance.

Consequential-action plane

canonical Effect + exact attempt
   + Auctor authority facts/constraints
   + Causal observations/context
   + required evidence
              │
            Decide      contextual authorization of the exact attempt, now
              │
           Defender     negative-only restrictions
              │
            Action      point-of-effect enforcement / release
              │         (+ applicable enforcement providers, incl. Causal)
          execution
              │
       observed outcome

Throughout this book, cognition produces proposals, for example Patch Proposals (Volume V). Wherever a volume describes a proposal moving from "validated" to "authorized" to "committed", the authorization step belongs to Decide and the commit or release step belongs to Action. Neither belongs to DCN, Kline or the Kernel. Actum records Acts and evidence. A recorded Act, receipt or settlement is evidence, not permission.

Identity model

  1. Effect identity: the canonical semantic identity of the proposed transition (WHAT).
  2. Attempt identity: one concrete execution attempt under a particular context, authorization and evidence set (THIS attempt).
  3. Evidence commitments: facts and observations that support qualification, review, authorization or enforcement.

These three are distinct. Every contract binds the exact identities it consumes, and none may stand in for another. DCN identifiers such as episode_id, act_id, correlation IDs and artifact hashes are evidence or lineage identifiers. They are never a competing Effect or action identity.

Constitutional invariants (summary)

  1. Qualified reuse is not permission. A qualified K-line cannot authorize its consequential Effects.
  2. Qualification, cognitive routing, provider selection, computation, contextual authorization and point-of-effect release are distinct responsibilities.
  3. DCN selection cannot mutate or promote K-line lifecycle state.
  4. System-2 success creates at most a candidate. Promotion requires valid evaluation evidence.
  5. No solution ≠ lookup or infrastructure failure.
  6. Kline/DCN recursion is cycle-bounded and propagates context, budgets, deadlines and provenance.
  7. Recognition, selection, computation, model output, review, consensus, confidence and receipts cannot manufacture authority.
  8. Auctor supplies authority facts and constraints. Decide owns complete contextual authorization of the exact attempt.
  9. Human step-up cannot substitute for unresolved required authority facts.
  10. Authorization is scoped to its context and must be re-evaluated after relevant changes.
  11. Observation and evidence precede the review, authorization or enforcement that depends on them. Relevant changes invalidate dependent decisions.
  12. Action owns generic point-of-effect release. It verifies the exact attempt binding, authorization freshness and required enforcement evidence.
  13. Causal owns independent observation and specialized enforcement mechanisms, not the generic release boundary.
  14. Effect identity, attempt identity and evidence commitments remain distinct and exactly bound.
  15. Failure, timeout, stale state, missing evidence or unavailable infrastructure never widens permission.
  16. Repository location does not determine logical ownership.
  17. Align orchestrates and governs architecture but does not absorb component semantics.
  18. Ownership changes require an accepted Align ADR and a constitution version change before dependent feature code.

Selection ≠ execution ≠ admission. Receipts and evidence ≠ permission.

Qualification evidence (ADR-0003)

A SolutionOffer or K-line advertisement is not qualification evidence. A qualified-reuse claim must carry an authenticated, canonical Qualification Evidence Reference that is bound to authenticated evidence and to the exact immutable executable artifact or build digest. A multi-file package uses a canonical closed manifest root. The admitting consumer verifies independently:

  • offer protection;
  • evidence authenticity and integrity;
  • the exact measured subject;
  • an acceptable, current profile and issuer;
  • the qualified result;
  • freshness and revocation.

Source revision, test name, workflow, branch, K-line identity or semantic equivalence cannot replace the artifact digest. No rebuild equivalence is defined. A valid reference permits qualified-reuse admission only. It never grants authorization or approval, and it never releases an Effect or attempt.

For this book, a KLineArtifact hash (Volume II), a PromotionAct (Volume IV) or a compiled artifact (Volume VI) does not on its own make an artifact qualified for reuse in another Mind. Qualification is established through Kline's qualification contract and verified by the consumer.

Governed Execution Manifest (ADR-0004, proposed)

GEM /1 is an additive, closed reference contract. It binds an immutable workflow/build and its source-native commitments to an exact Effect Instance, and Action's protected profile binds the GEM digest into the signed execution request. The checker's only success is manifest_bindings_only. A manifest does not establish live enforcement, qualification or outcome, and no ownership moves.

Provider statements (ADR-0005, proposed)

advatar.provider-statements/1 authenticates an assessor's statements about a hosted provider: identity, entitlement, processing and commercial terms, and optional attestation. Its only success is authenticated_provider_statements_only. It is not a hosted-service qualification format. Until Kline defines a hosted-service qualification subject and profile, a hosted service has no qualified-reuse admission. DCN may compose statement authentication with a separate, mandatory, trusted qualification-and-source verifier. It cannot skip or synthesize that verifier, weaken caller requirements, or change route availability. Statement admission never permits credential lookup, payment, network egress, clinical use, an Effect or an Action attempt. This constrains how Volumes III, IX and the Verifiable Inference profile treat provider evidence: authenticated provider evidence (TLSNotary, attestation) supports claims and admissibility, but it does not qualify the remote service.

Mapping book concepts to owners

Book conceptWhereConstitutional owner / reading
Cognitive Kernel, System 1/System 2 routingVolumes I, VMind-local Cognitive Kernel (hosted in DCN)
KLineTemplate / Episode / Artifact, evaluation, promotion, decay, supersessionVolumes II, IV, VIKline (some lifecycle code is hosted semantics in DCN)
Cognitive Compiler / Compiler SocietyVolume VIProduces artifacts and candidates. Promotion and qualification are Kline's.
CapabilityRequirement resolution, admissibility, provider selection, federation placementVolumes III, VII, XIDCN capability fabric
Actum Compute markets, pricing, matching, settlementVolumes III, IXProcurement and economics. A market outcome is not authority.
Actum Acts, evidence graph, finalityVolume IVEvidence and lineage. Acts are not permission.
PatchProposal validation → authorization → commitVolume VProposal from cognition. Authorization belongs to Decide, release or commit to Action.
Authority, delegation, credentialsVolume XFacts and constraints from Auctor, contextual decision by Decide
Safety review, containment, blockingVolumes V, XDefender (negative-only)
Independent execution observation, pre-effect gatesVolumes IV, X, XIICausal (observation and specialized enforcement providers)
Cross-component contracts and conformance fixturesVolume XIIAlign

Conformance claims

Align owns the normative contracts and shared fixtures. Every participating repository, DCN included, must run the applicable conformance tests against its real implementation in component CI. A conformance claim names:

  • the constitution version;
  • the fixture version;
  • the real implementation entry point;
  • the guarantees exercised;
  • the failures and refusals exercised.

Documentation consistency alone, including this book, is not executable conformance.