📖About

Ninad ruling: Orion (the human-in-loop operator) should own no service. Re-own the Governance service from Orion to Clara. Since Clara already owns Status Reporting and policy forbids one agent owning two services, retire Status Reporting as a standalone service and re-create it as a block of Governance (owned by Clara); its 5 member agents (Clara + aggregators Aurora, Cassius, Rhea, Odin) move under the block. Repoint all collateral (service_agents, artifact_service_tags, service_architecture, RSI/audit metrics) from status-reporting to governance. Update the Services Catalogue, Carolopedia, and the service-driven scorecards (Prometheus Quality Scorecard/RSI Dashboard, Themis Audit Scorecard, Hermione Process Health Scorecard) plus any app that references these services. Also tag Carolopedia to Governance (done).

⚖️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 -> 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

• Governance service is owned by Clara; Orion owns no service (must_have)
• Status Reporting is a block of Governance (not a standalone service) with its 5 member agents moved under it (must_have)
• No agent owns two services after the change (must_have)
• All collateral (service_agents, artifact_service_tags, service_architecture, RSI/audit metrics) repointed from status-reporting to governance (must_have)
• Services Catalogue, Carolopedia, and the Prometheus/Themis/Hermione scorecards reflect the new structure with no dangling status-reporting service (must_have)
• Carolopedia is tagged to the Governance service (must_have)