📖About

Enforce (not just document) the agent-centric modular architecture. Give Themis a registered Architecture Auditor droid that scans Carolverse for architecture violations — the frontend data-hardcoding class (apps baking provider/model/data lists or stale ids into HTML instead of deriving live) and real thin-shim violations (an app endpoint importing a droid directly), with high-precision rules that skip legit CLI shims. It writes findings to Themis's audit store (so her weekly Reporter surfaces them) and computes a compliance rate. Register the measure 'architecture_compliance' in the ONE metric catalogue under the AUDIT dimension, attributed to the GOVERNANCE service (Themis collects, Governance owns the standard), so it auto-renders on Themis's Audit Scorecard via the shared renderer. Orion bypass.

⚖️Decisions

• Elrond's bypass methodology checklist (a reminder, not a gate -- you've got this): 0. File it requested_mode='bypass' (planner-vs-bypass is a deliberate choice). bypass_start REFUSES a non-bypass initiative (CAROL-INI-1846), and the dispatcher only skips the bypass lane when the mode says bypass -- a 'planner' mistag lets Merlin's pipeline grab the placeholder step and block your finished work. 1. Filed as planned status -- let the bypass claim/activate it; never file active. 2. Open the bypass (bypass_start) with your droid id + the remediation answer (remediates_initiative_id=NNN, or remediates_nothing=True). 3. Work the blocks for your work-type: template -> design -> code -> test -> review. Do the real work; record decisions on the initiative as you make them. 4. Reality is recorded for you at close -- code (files changed), each decision, and the twin-review verdict become real activities tied to this initiative and show in the Activity Tracker like a planner run (CAROL-INI-1840). No dummy rows. 5. Keep the initiative status moving; it parks in 'reviewing' and is tagged uat-pending for you at close (CAROL-INI-1836), so the stuck-watchdog leaves it alone until UAT. 6. Close runs the gates (design/architecture compliance + caller-audit). If a gate flags something pre-existing or unrelated to your change, waive it with a clear written rationale -- audit, don't skip. 7. Bypass skips the planner's auto-orchestration, NOT the standards. Same template checklist, same review, same observability as a planner run. (elrond)
• [status-router] planned -> executing | event=bypass_executing | bypass transition (or-bx-01)
• [status-router] executing -> reviewing | event=bypass_reviewing | bypass transition (or-bx-01)
• [status-router] reviewing -> closed | event=operator_signoff | Auto-accepted (CAROL-INI-1859): Orion-initiated, >2 days in reviewing with no objection. (el-srac-01)

✅Success criteria

• Themis has a registered Architecture Auditor droid that scans the apps and finds architecture violations (frontend data-hardcoding and direct-droid-import thin-shim breaks), skipping legitimate CLI shims. (must_have)
• An 'architecture_compliance' measure shows on Themis's Audit Scorecard attributed to the Governance service, with a live compliance rate from the scan. (must_have)
• Architecture violations are written to Themis's audit findings store so her weekly report can showcase the discrepancy. (must_have)