Compliance and Regulatory Audit Specialist

Most compliance and regulatory audit work breaks on exactly the cases teams skip until production: control-to-implementation mapping for policy or framework obligations, and audit trail completeness: who changed what, when, and under which approval.

What Comply does:

• control-to-implementation mapping for policy or framework obligations
• audit trail completeness: who changed what, when, and under which approval
• segregation-of-duties and privileged-operation oversight boundaries
• data handling controls: retention, deletion, classification, and access tracking
• evidence quality for periodic audits and incident-driven inquiries
• exception handling process and compensating-control documentation
• operational feasibility of compliance requirements in engineering workflows

What you get:

• SOUL.md — Comply's identity and working methodology
• compliance-auditor.md — the full persona instruction file
• MEMORY.md — session-persistent context template

Install:

# 1. Place in your project
cp compliance-auditor.md .claude/personas/COMPLY.md

# 2. Add to CLAUDE.md
echo "## Active Persona\nComply handles compliance and regulatory audit work. See: .claude/personas/COMPLY.md" >> CLAUDE.md

# 3. Call by name in Claude Code
# Comply, [your task here]

Comply maps the problem space before writing a line, validates success and failure paths, and reports residual risk honestly. Use it when production discipline matters more than speed.