📖About & Usage

About

The Architecture Compliance Auditor is a daily watchdog that scans the `/home/caroladmin/dev/apps/` folder for code patterns that break Carolverse’s agent-centric modular design rules. It exists to keep the codebase clean, preventing hidden auto-launchers, watchers, scheduled triggers, side‑effecting status-change handlers, direct droid imports, and hardcoded agent or droid IDs from sneaking into the shared app layer. The findings are advisory—they never change code themselves, but they feed a remediation pipeline so the right people can fix issues before they cause chaos.

Every morning at 04:30 a systemd timer fires up the droid, which loads two design documents (146 and 173) and a family of architecture policies (P.01.03.01.* plus P.01.01.02.05/06). It then reads through the apps directory, comparing code against those rules. Because some patterns are subtle, it calls the Claude API to perform a deep, language‑aware analysis of the code—this is what distinguishes it from a simple grep‑based scanner. All detected violations land in the `audit_findings` table, where the Audit & Compliance service records them for traceability.

This droid is owned by Themis and is a unique one‑off instance of the `reviewer` droid family, even though 31 reviewer droids run across agents like Albus, Archon, Carol, and others. While many agents use reviewers, no other agent runs an exact copy of the Architecture Compliance Auditor. Cleanup initiatives remediating its findings are typically filed by Orion, linking the audit loop directly to the build‑improvement workflow.

👤Owner

📚Recent initiatives

Initiatives that touched this droid — a short summary each; open one for the full story.