📖About

Two-part hygiene + UI for the Services Catalogue (Midas). (1) Data: System Services (Radagast) is the only catalogue service with no track - add a Core track owned by Radagast and attach its 5 blocks, so all 18 services satisfy the every-service-has-at-least-one-owned-track invariant. (2) UI: the landing grid gets a search box that filters service cards as you type, and each service card shows the owning agent's name and round profile picture.

⚖️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)
• Current state at filing (Elrond validity check): The Services Catalogue has 18 services, but System Services (Radagast) is the only one without a track, violating the invariant. The landing page does not have a search box that filters cards, and service cards do not display the owning agent's name and profile picture. (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

• Every one of the 18 catalogue services has at least one track, and every track has an owner (System Services included). (must_have)
• The Services Catalogue landing page shows a search box at the top that filters the service cards as the user types. (must_have)
• Each service card on the landing page shows the owning agent's name and their round profile picture. (must_have)