v1.1 Release Candidate
Aligned to DACS Specification v1.13 Release Candidate
Available at: https://dacs.datavaultalliance.com/documents/dacs-pass-fail-and-remediation-catalog/
| Purpose This catalog helps practitioners inspect DACS evidence, assess each control, diagnose failed conditions, plan corrective work, apply the recorded Gate disposition, and retest for closure. |
| Normative boundary DACS Specification v1.13 defines the mandatory controls and governing assessment rules. This catalog is informative companion guidance aligned to that version. It adds no requirement and grants no authorization. The exact Specification version used by an assessment governs; a later version does not rewrite historical results. |
Published by DataVaultAlliance Holdings LLC
DataVaultAlliance maintains the authoritative DACS Specification and official DACS publications. Redistributed copies may become outdated. Verify the current authoritative version at dacs.datavaultalliance.com before relying on this publication.
Table of Contents
1. Purpose and operating boundary 3
3. Testable, implementable, and executable controls 5
5. Controlled disposition guidance 6
6. Reusable remediation patterns 8
7. Core Decision-Scope Controls 9
8. Extended Taxonomy Controls 61
9. Extended Ontology Controls 96
10. AI Context Contract Controls 131
11. Remediation record template 157
1. Purpose and operating boundary
The DACS Pass/Fail and Remediation Catalog is an operational companion to the Defensible Analytics Control Specification. It answers a narrow practitioner question: when a control is evaluated, what evidence should be inspected, what constitutes Pass or Fail, and what must happen next when the control does not pass?
DACS defines the controls and evidence requirements used to determine whether evidence is ready for stated use within a stated decision scope. It does not establish universal truth, prove that a decision is correct, or replace the governance, data-management, risk, audit, security, privacy, or AI-management disciplines that may supply evidence to the control process.
This catalog preserves the DACS distinction between control result and Gate readiness state. A control result is Pass, Fail, or Not Applicable. A Gate readiness state is Proceed, Caution, Stop, or Quarantined. An exception may permit constrained use, but an exception does not convert a failed control into a passed control.
Primary operating question
What does the reader need to do next, and what evidence must exist when they are done?
Document responsibility and depth boundary
This catalog covers the control-assessment boundary. It tells a practitioner how to inspect evidence, execute the assessment, determine Pass, Fail, or Not Applicable, remediate a failed condition, apply a controlled disposition while unresolved, and retest for closure. It does not prescribe organizational rollout, team design, workshop methods, operating cadence, or broader implementation architecture. Those belong in the DACS Practitioner Playbook and Adoption Guide. Worked evidence packages, sampling exercises, and assessor practice belong in the DACS Assessment Guide and Example Workbook. First-adoption sequencing belongs in the DACS First Look Pilot Kit.