/dr-compliance

Overview

/dr-compliance is the final quality gate before archiving. It resolves the target task, detects the task type — code, documentation, research, legal, content, or infrastructure — and applies the appropriate verification checklist. Unlike /dr-qa which checks implementation against plan, compliance checks the output against domain-specific standards.

Usage

/dr-compliance

What It Does

1. Task Resolution — applies the Task Resolution Rule to determine which task to verify (from argument or disambiguation when multiple tasks are active).
2. Detect Task Type — reads tasks.md and activeContext.md to classify the task: code, documentation, research, legal, content, infrastructure, or mixed.
3. Apply Checklist — executes the appropriate domain-specific checks:
   • Code — lint, tests, coverage, CI/CD, dependency audit
   • Documentation — completeness, accuracy, consistency, cross-references, audience fit
   • Research — methodology, citations, argument coherence, scope boundaries
   • Legal — jurisdiction, definitions, structure, rights and obligations
   • Content — fact verification, AI pattern removal, platform requirements, editorial standards
   • Infrastructure — configuration, rollback plan, monitoring, security hardening
   • Mixed — combines relevant sections from each matching type
4. Generate Report — outputs the compliance report following templates/compliance-report-template.md (v2.14.0+, TUNE-0255). Frontmatter: task_id, date, verdict (COMPLIANT / COMPLIANT_WITH_NOTES / NON-COMPLIANT), optional scope. Body: four operator-facing top sections in strict order — «Начальная задача» (one Russian sentence sourced from the operator brief), «Как решили» (single-level bullet list mapping every brief item to a quoted bullet + Russian status word + one or two plain-language sentences; expectations fold into the same list with marker «(уточнение брифа)»), «Артефакты задачи» (what was verified or hardened by the pass), «Следующие шаги» (concrete /dr-* commands or operator actions). Under a --- rule sits the audit addendum with ### Step-by-step verdicts (the 7-step verdict table, wrapped in <!-- gate:literal --> so English column headings bypass the banlist), ### Remaining risks, ### Related. Status words: «выполнено» / «частично» / «не выполнено» / «неприменимо» — never the schema enum.

Arguments

None. Operates on the currently active task (resolved via Task Resolution).

Output

Creates: datarim/reports/compliance-report-{task_id}.md (if the directory exists). Otherwise outputs the report in chat.

Verdicts

• COMPLIANT — all checks pass, ready to archive
• COMPLIANT_WITH_NOTES — passes with minor observations
• NON-COMPLIANT — critical issues found, must fix before archiving

Example Session

> /dr-compliance

Task Resolution: AUTH-0001 (Level 3)
Detected task type: Code + Infrastructure (mixed)

Code checklist:
  [x] Lint passes (0 warnings)
  [x] Tests pass (14/14)
  [x] Coverage: 87% (threshold: 80%)
  [x] No hardcoded secrets
  [x] Dependencies audited (0 vulnerabilities)

Infrastructure checklist:
  [x] Configuration documented
  [x] Rollback plan tested
  [x] Monitoring alerts configured
  [x] SSL certificates valid

Verdict: COMPLIANT
Report saved: datarim/reports/compliance-report-AUTH-0001.md

Next step: /dr-archive (Step 0.5 runs reflection internally)

Related Commands

• /dr-qa — previous stage: quality verification
• /dr-archive — next stage (reflection runs as Step 0.5)