Carolopedia

A friendly guide to Carol, her ecosystem, and the agents who built her.

📖 CarolopediaServicesBuild InitiativesAll activitiesINI-999902720Guide page
📋

CAROL-INI-3800-00: Business Catalogue back to Clara: CEOs own project apps, Leo builds them; fix Midas topbar chip

Initiative
Open in Initiatives →

📖About

Ninad ruling (CLI-248): Leo is the chat agent responsible for BUILDING these apps for the projects, but the CEOs have to OWN them - so the Business Catalogue moves from Leo (agt_034) back to Clara (agt_010), full five-surface transfer per Sage's method. The canonical topbar owner chip still reads 'Midas' (leftover from cloning the Services Catalogue template) and is corrected to Clara. Ruling promoted to the cookbook.

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

  • Registry app row for business-catalogue has owner agt_010 (Clara); Leo holds no write grant; Clara holds the grant with a dated reason (must_have)
  • Canonical topbar owner chip shows Clara and links to Clara's employee page (Midas leftover gone) (must_have)
  • Access diff before/after recorded with who gained and who lost (must_have)
  • Encyclopedia prose credits Clara; a NEW dated update note records the move; earlier notes untouched (must_have)
  • The ruling 'Leo builds the project apps, the CEO owns them' is recorded in the Build Cookbook with an entry number (must_have)