Chapter 13 of 19

13. Annex A: MVP Control Checklist (Informative)

The following checklist identifies useful entry points for a first DACS evaluation. It is a selected checklist, not a complete conformance assessment or execution sequence. Evaluate all controls applicable to the claimed scope, including those not listed here. CORE-001 and CORE-002 precede profile selection; use the Dependency Map for the remaining evaluation order.

Core

  • CORE-001 - Decision Scope Is Declared
  • CORE-004 - Semantic Contract Exists
  • CORE-003 - Applicable Profiles Are Declared
  • CORE-007 - Business Identity Anchors Exist Where Required
  • CORE-008 - Semantic Grain Is Declared for Identity-Bearing Evidence
  • CORE-005 - Physical Attribution or Boundary Evidence Anchor Is Recorded Where Required
  • CORE-006 - Logical-to-Conceptual Binding Exists Where Required
  • CORE-013 - Context, Version, and Causal Order Are Preserved
  • CORE-014 - Gate Record Is Created
  • CORE-025 - Decision Path Is Reconstructable
  • CORE-018 - Conformance Record Exists
  • CORE-019 - Conformance Record Is Structured
  • CORE-023 - Material Semantic Binding Change Triggers Forward Reassessment
  • CORE-010 - Identity Resolution Produces Determinate Results
  • CORE-009 - Business Concept Is Not Assumed to Be Business Identity
  • CORE-011 - Discovered Evidence Is Quarantined Until Governed
  • CORE-015 - Gate Record Is Structured
  • CORE-016 - Readiness Validity Is Declared and Enforced
  • CORE-002 - Materiality and Conditional Applicability Are Bound Before Dependent Controls

Completion checks omitted from this starter list remain applicable where their rules require them: CORE-012 (DACS version), CORE-017 (runtime failure), CORE-020 (integrity), CORE-021 (rule changes), CORE-022 (history), and CORE-024 (lawful preservation/deletion). A starter review does not waive them.

Extended Taxonomy

  • ET-001 - Taxonomy Scope and Purpose Are Declared
  • ET-003 - Taxonomy Node Type Is Declared
  • ET-004 - Business Meaning Is Recorded
  • ET-005 - Controlled Label and Language Evidence Are Recorded
  • ET-006 - Semantic Domain and Boundary Are Declared
  • ET-007 - Semantic Grain Is Declared Where Material
  • ET-009 - Physical Semantic Anchors Are Recorded Where Required
  • ET-011 - Business Identifier or Key Evidence Is Recorded Where Applicable
  • ET-010 - Source-System Representation Is Recorded Where Required
  • ET-012 - Resolution or Mastering Rule Is Recorded Where Applicable
  • ET-002 - Ownership and Stewardship Are Recorded
  • ET-013 - Governance Constraints, Jurisdiction, and Usage Boundaries Are Recorded
  • ET-008 - Provenance Is Recorded
  • ET-016 - Readiness State Is Declared
  • ET-014 - Semantic Risk Is Recorded Where Present
  • ET-015 - Relationship Seeds Are Not Treated as Decision-Ready Relationships
  • ET-017 - Taxonomy Change Triggers Reassessment

Extended Ontology

  • EO-001 - Relationship Candidate Is Not Treated as Decision-Ready
  • EO-002 - Relationship Type Is Governed
  • EO-003 - Relationship Orientation Is Declared
  • EO-004 - Relationship Assertion Provenance Is Recorded
  • EO-005 - Physical Relationship Representation or Boundary Evidence Anchor Is Recorded Where Required
  • EO-006 - Related Identifier Alignment and Semantic Grain Are Tested
  • EO-007 - Discovery, Inference, or Declaration Method Is Recorded
  • EO-009 - Relationship Vector Is Recorded for Material Relationships
  • EO-008 - Minimum Relationship Vector Criteria Are Defined
  • EO-010 - Relationship Vector Meets Decision-Scope Criteria
  • EO-011 - Permitted and Prohibited Relationship Paths Are Declared
  • EO-013 - Relationship Constraints Are Applied
  • EO-016 - Relationship Readiness State Is Declared
  • EO-012 - Relationship Conflict and Jurisdiction Resolution Rule Exists Where Applicable
  • EO-017 - Ontology Change Triggers Forward Reassessment
  • EO-015 - Traversal Path Is Determinate Where Used
  • EO-014 - Cross-Domain Semantic Compatibility Is Declared Where Applicable

AI Context Contract

  • AI-001 - Binding AI Context Contract Exists
  • AI-002 - AI Inputs Conform to the Semantic Contract
  • AI-003 - AI Output Terms Conform to Extended Taxonomy or Are Quarantined
  • AI-004 - AI Output Relationships Conform to Extended Ontology or Are Quarantined
  • AI-005 - AI Inference and Output Drift Are Tested
  • AI-006 - AI Context Contract Violation Has Consequence
  • AI-007 - Context Enforcement Point or Equivalent Control Is Declared
  • AI-010 - Decision Execution Trace Is Recorded Where AI or Automation Is Material
  • AI-008 - Agentic Action Authority Is Declared Where AI Acts
  • AI-009 - Material Agentic Action Requires Gate-Before-Action
  • AI-011 - AI-Generated Evidence Is Not Treated as Decision-Ready Without Gate Evidence

Back to document overview

DACS Strategic Insights

Direct, zero-fluff updates on DACS controls, defensibility practices, and framework releases.

By subscribing, you’re asking DataVaultAlliance to send you DACS controls, defensibility practices, and framework releases. You can unsubscribe at any time. See our Privacy Policy. This site is protected by reCAPTCHA and the Google Privacy Policy
and Terms of Service apply.

Access This DACS Document

Verify your email to access the document. No account or password is required. You may need to verify again if you change devices, use private browsing, or clear your cookies.

We will use your email to provide access to the requested document. Marketing communications are optional.