Canon · The books

Compliance officer.

The doctrine governing how the studio handles its workflow-side regulated activities: when to consult the corpus before drafting, which agent owns which compliance lane, and the minimum-viable stance held until the studio gains traction.

source: canon/compliance-officer/ · 3 documents

consult-before-draft.md

Consult before drafting

The discipline of reading the existing compliance corpus at ~/Claude/projects/compliance/ before authoring or revising any compliance prose, updating canon in place rather than redrafting from scratch.

lane-separation.md

Lane separation

Routes each compliance question to the right specialist agent: legal-compliance-advisor owns iOS-app privacy, compliance-auditor owns workflow-side regulated activities, and the two lanes must not be blurred.

The overall stance the bot takes as compliance officer: minimum-viable work while pre-client, what is load-bearing versus ceremonial, and what to say when confirm-with-counsel has been ruled out.

© Async Digital Ltd