📖About

On the Carolopedia agents landing page the lead can appear at the bottom of a service group: the security team has Heimdall (owner/lead) at level 6 but his four reports at level 5, so a pure level sort drops him below them. Fix: (1) the security level data is inverted - set Heimdalls four direct reports below him so the hierarchy number is correct; (2) within each service group, pin the service owner (lead) first, then order the rest by org hierarchy (level, display order, name). Audit all services for the same owner-not-senior pattern. Verify Heimdall leads the security group on the landing page, the service page, and Midas.

⚖️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=operator_complete | CAROL-INI-1949 bypass: code+data changes complete and verified (Heimdall leads security; audit clean). bypass_end hung on the plangenerator.db lock storm; routing to reviewing via the relay per the documented recovery. (orion)
• [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

• Security level data corrected so Heimdall is senior to his four direct reports (must_have)
• Agents landing page pins the service owner first, then orders by org hierarchy (must_have)
• Heimdall leads the security group on the landing page (must_have)
• No other service has the owner-not-senior ordering problem (audited) (must_have)