📖About

Services are currently a dual source of truth: the registry table carolverse_services AND per-service services//service_meta.json files, which Midas and Carolopedia read for display. They drift (e.g. the Security service owner was Heimdall in the registry but Radagast in the JSON). Make the REGISTRY the single canonical source, matching every other entity (agents, apps, droids, blocks). Steps: (1) extend carolverse_services with the presentation fields the JSON carries but the table lacks (icon, color, url_prefix, category, readiness, project) and backfill them from the existing JSON; (2) ensure every service has a registry row (registry authoritative); (3) build a generator that writes service_meta.json from carolverse_services + service_agents (registry -> JSON), so the JSON becomes a derived export, never hand-edited; (4) register the generator as a nightly run-audited droid and run it once to regenerate all service JSONs; (5) update the SST: rescan the SST app and record (cookbook/concept) that the registry is the canonical source for services and the JSON is a generated cache. Net: one place to edit, no drift.

⚖️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 -> active | event=bypass_active | bypass transition (or-bx-01)
• Reconciled to: registry carolverse_services (+ service_agents) is the SINGLE source for services; service_meta.json is a derived export regenerated by Midas Service Catalog Export (tools/export_service_meta.py, nightly run-audited droid). Added 6 presentation columns to carolverse_services + backfilled from JSON (5 services inserted, 17 backfilled, 22 total). Chose generated-export over refactoring Midas/Carolopedia to read the registry directly — lower risk, same outcome (registry canonical, JSON a faithful cache). Cookbook 346 records the rule; SST rescanned. (orion)
• [status-router] active -> 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

• carolverse_services holds all service fields (incl. icon/color/url_prefix/category/readiness/project), backfilled from JSON; every service has a registry row. (must_have)
• A generator produces every services/<id>/service_meta.json from the registry (carolverse_services + service_agents); JSON is a derived export. (must_have)
• The generator is a registered, run-audited nightly droid; running it reproduces the JSONs with no manual edits. (must_have)
• SST rescanned and the canonical-source rule for services recorded (cookbook/concept); Midas + Carolopedia still render correctly from the generated JSON. (must_have)