{"wiki":{"id":579,"slug":"cw-arch-01","entity_type":"droid","entity_id":"cw-arch-01","title":"Architecture Compliance Auditor","prose_md":"## About\n\nThe 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.\n\nEvery 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]] service records them for traceability.\n\nThis droid is owned by [[agt_028]] and is a unique one‑off instance of the `reviewer` droid family, even though 31 reviewer droids run across agents like [[agt_001]], [[agt_002]], [[agt_008]], 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 [[agt_023]], linking the audit loop directly to the build‑improvement workflow.","namesake_json":"{\"engine\": \"claude\", \"model\": null, \"claude_purpose\": \"analyzes code for forbidden patterns\", \"family\": \"reviewer\", \"family_size\": 31, \"is_unique\": true}","profile_pic_path":"avatars/droid/cw-arch-01.png","source_hash":"ea026aca9ff639f6ed8d23c429b8cf1434dab284e016390c99cb0ebf47ee490b","status":"active","last_generated_at":"2026-07-25 03:38:14","created_at":"2026-07-25 03:38:14","updated_at":"2026-08-01 03:38:03"},"facts":{"id":"cw-arch-01","name":"Architecture Compliance Auditor","machine_name":"CW-ARCH-01","owner":"agt_028","function":"Daily scan of apps/ for agent-centric modular architecture violations","process_type":"scheduled","schedule":"daily 04:30","process_name":"architecture_compliance_audit","avatar_color":"#06b6d4","created_for":"Themis owns Carol's compliance audit lane. Review and audit are separate processes (cookbook #61 Carol Glossary). This droid is the audit-side counterpart that catches architectural drift independent of any specific build.","purpose":"Loads Designs 146 + 173 and policy family P.01.03.01.* + P.01.01.02.05/06 at run time. Scans /home/caroladmin/dev/apps/ for forbidden patterns: auto-launchers, watchers, scheduled triggers, status-change handlers with side-effects, direct droid imports, hardcoded agent/droid IDs. Writes findings to audit_findings table for remediation pipeline.","duties":"- Reads only. Never invoked by Elrond's reviewer or any build path.\n- Findings are advisory: remediation is filed as separate cleanup initiatives by Orion.\n- Runs once daily via systemd timer; on-demand invocation also allowed.","constraints":"Audits read-only; never executes fixes. Independent of build pipeline.","status":"running","gender":"male","archetype":"reviewer","building_block":"build_gates","service_override":null,"enabled":1,"task_key":"audit.scheduled_audit","model_free":0},"page":{"type":"droid","page_class":"main","class_label":"Main page","kind_label":"Droid","kind_gloss":"","listed":true}}