Chapter 3 of 12

3. Testable, implementable, and executable controls

At a completed assessment, record Pass only when every applicable mandatory criterion and required evidence element is satisfied, including the listed prerequisite statuses. Otherwise record Fail. Record Not Applicable only when a recorded Applicability Rule evaluates false, with its reason, rule reference, and supporting facts. Unresolved applicability is Fail, not Not Applicable. Evidence collection, evaluation, Gate authorization, and record completion are separate activities under Specification Section 3.2.6; no later completion reference creates an earlier circular prerequisite.

TestableThe required evidence can be inspected and compared against the Requirement, Pass condition, Fail condition, decision scope, authority, rule, threshold, version, or Gate readiness state.
ImplementableA real team can satisfy the control through a manual procedure, workflow, governed record, rule engine, metadata repository, catalog, semantic layer, data-quality process, identity process, stewardship process, API, automation, or hybrid mechanism.
ExecutableThe control has a repeatable evaluation path, recorded evidence, an accountable authority, an approved rule reference where applicable, and the required control result and Gate readiness state where applicable. Executable does not require software code.

Do not use executable to imply that AI output is inherently deterministic, that a prompt is sufficient as a control, or that a model can establish its own DACS conformance.

Preferred operating statement

DACS controls may be executed manually, procedurally, automatically, or through hybrid workflows. The requirement is not the implementation mechanism. The requirement is testable evidence, a recorded control result, and a Gate readiness state for the stated decision scope.

Authority and execution in the control cards. Every card identifies the accountable authority for the control. Execution guidance appears only when timing, repeatability, enforcement, sequencing, or evidence capture is material to the control. If no Execution entry appears, the universal execution rule above applies. Generic tool lists are intentionally not repeated in every card.

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.