Skip to content

How to Run a Compliance Report

The Compliance Report is the final validation artifact — a comprehensive audit of all DLC controls across your project’s artifacts.

  • Before declaring a feature or sprint complete
  • When preparing for a compliance audit or review
  • After completing all validation checks for a release
  • Ideally, all four DLC phases should have artifacts (Intent → Architecture → Construction → Validation)
  • At minimum, an Intent Brief and ARC should exist
cat-compliance-report

Vera, the QA Lead, scans all artifacts in _cat/artifacts/ and produces a 10-control compliance matrix.

#ControlWhat It Checks
1Intent CaptureIntent Statement or Brief exists with required fields
2Scope DefinitionIn/out scope clearly defined with measurable criteria
3Architecture ContractARC exists with enforceable constraints
4AI GovernanceAI governance section present in ARC
5Constraint TraceabilityARC constraints trace to business needs
6Bolt DecompositionFeatures decomposed into bolts with ARC mapping
7Construction ComplianceBolt executions reference and satisfy ARC constraints
8Code ReviewCode reviews completed against ARC and AI governance
9Adherence VerificationARC adherence check completed post-construction
10AcceptanceWork acceptance validates against intent criteria

The report shows each control as:

  • Pass — Control fully satisfied with evidence
  • ⚠️ Partial — Some evidence exists but gaps remain
  • Fail — No evidence or critical gaps
  • N/A — Not applicable (with justification)

Output: _cat/artifacts/validation/compliance-report.md

If controls show gaps:

GapFix
Missing Intent artifactsRun cat-intent-statement or cat-quick-intent
No ARCRun cat-arc-builder or cat-quick-arc
Missing AI governanceRun cat-arc-edit to add AI governance section
No adherence checkRun cat-arc-adherence-check
No work acceptanceRun cat-work-acceptance

See Also: Compliance Controls · Run ARC Adherence Check · Validation Phase