📖About

Root gap exposed by the health-check-bot incident (2026-07-20): a process (the CAROL-INI-416 web-chat smoke test) runs and affects production but is not a registered droid, so nothing catches it. Build (1) a Themis-owned scheduled droid that audits every running/scheduled process on carol-vm (crontab entries, systemd units, and known live loops) against the registered droids table and records any process that runs but is not registered as a droid; (2) Themis's WEEKLY compliance report (none exists today - only a monthly LLM report) that surfaces the auditor's findings plus Themis's standing compliance posture, published to a discoverable surface. Both new droids must be registered in the registry, owned by Themis, emit run-audit so the Process Health Scorecard and RSI Dashboard pick them up, and have Carolopedia profiles. Follow the update-carolverse-processes contract.

⚖️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)
• [delivery-check] 4 must-have criteria remain pending at bypass_end — delivery has no mechanical re-performance lane; UAT must grade on live evidence, not checklist silence (CAROL-INI-3020): (no detail) (orion)
• [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

• A weekly Themis audit runs and its report lists every process that is running or scheduled on the VM but has no registered droid; the smoke-test health-check bot appears as a finding until registered or excluded. (must_have)
• Themis publishes a weekly report to a surface the admin can open and read; it shows the unregistered-process findings and Themis's compliance posture. (must_have)
• Both new droids appear on the Process Health Scorecard and RSI Dashboard because they are registered and emit run-audit. (must_have)
• Each new droid has a Carolopedia profile page rendered in the Themis team. (must_have)