📖About
Compliance Auditor is a droid that helps check whether Carol’s constitution, policies and code agree. Its purpose is to identify gaps and contradictions that need review.
It detects issues but does not fix them.
📖Usage
Readers would meet Compliance Auditor when reviewing compliance findings. Its findings help Themis decide what needs fixing and direct the work to the appropriate team.
📖Purpose
By running checks every morning and recording findings in a database, the droid gives Themis the information she needs to direct the team. Instead of manually reading through thousands of lines of code and configuration every day, Themis gets a report of what's out of sync. She can then decide what needs fixing and send it to the right team.
📖Duties
- Runs ten daily checks: constitution-to-policy alignment, constitution and policy coverage gaps, code-to-policy alignment, code coverage, internal contradictions in the constitution and policies, deployment drift between development and production, design documentation sync, memory file sync, and production endpoint monitoring.
- Pulls current constitution, policies, approved design documents, and code samples from Carol's systems.
- Uses Claude to analyze and spot alignments, gaps, and contradictions.
- Stores findings in a database for review and decision-making.
📖Constraints
The droid finds issues but does not fix them. All remediation happens through a separate pipeline. It runs once daily, so it cannot catch changes between runs. It reviews a selection of code files, not everything in the system. It only checks approved design documents, not drafts or rejected ones.
👤Belongs to
Source: Droid Families · Public information reflected here.