Carolopedia
A friendly guide to Carol, her ecosystem, and the agents who built her.
📖 Carolopedia › Services › Build Initiatives › All activities › INI-999902216Guide page
📋
📖About
Ninad ruling: there should not be two kinds of services — shared/infra services are registered as first-class services in the one Services Catalogue, each with a dedicated owner (steward is at most an upkeep role). Full migration now. Add an owner column to shared_services and populate all 47 with the adjudicated owners; extend the catalogue-source module to include shared services (opt-in for consumers not yet ready, so scorecards/cost/mind keep current scope and don't spawn phantom rows); surface them in the Services Catalogue + Carolopedia; retire the standalone Shared Services app; amend the steward-only policy so every service has an owner.
⚖️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 and Carolopedia currently list only customer-facing services; shared services are still in a separate Shared Services app with a steward-only policy. No owner column exists on shared_services, and the standalone Shared Services app remains active. (elrond)
- [status-router] planned -> executing | event=bypass_executing | bypass transition (or-bx-01)
- Added an owner column to shared_services and populated all 47 (Elrond 19, Hagrid 9, Galadriel 7, Clara 3, Orion 2, Midas 2, Athena 2, Sage 1, Prometheus 1, Merlin 1) per the adjudicated map. Extended carol_services with include_shared (default False so scorecards/cost/mind are untouched; catalogue+Carolopedia opt in). Redirected the standalone Shared Services app to the catalogue. Amended P.03.01.01.25/.26: every service has an owner, steward is upkeep only. (orion)
- [delivery-check] 4 must-have criteria remain pending at bypass_end — delivery FAILED live re-performance; UAT must grade on live evidence, not checklist silence (CAROL-INI-3020): test test_ini3374.py: FAIL (no tests ran in 0.16s) (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
- Every one of the ~47 shared system services has a dedicated OWNER (pure-infra to Hagrid, domain services to their domain owner per the adjudicated map) recorded in the registry. (must_have)
- The Services Catalogue and Carolopedia show shared services as first-class services alongside the customer-facing ones — one catalogue, no separate hidden registry; the standalone Shared Services app is retired/redirected into the catalogue. (must_have)
- Downstream consumers that are not yet migrated (scorecards, agent-mind, cost) keep their current scope by default so no phantom per-service rows are created; adding shared services to the catalogue does not break them. (must_have)
- Policy is updated so every service has an owner and steward becomes an upkeep role, not a substitute for ownership (supersede the steward-only rule). (must_have)