📖About

New app owned by Athena (Head of Agent Resources) showing droid FAMILIES — functions replicated across multiple agents (e.g. App Steward x17, Twin Reviewer, Failure Watcher, Reporter, Spec-Writer). Each family lists the main/canonical droid, its function, the agents that run a copy, and any agent-specific customization. Also lists POTENTIAL families: single-agent droids whose function many agents will likely need later (RSI, consciousness/self-knowledge, data-quality/context-currency). Agent-centric: thin app window + shared shim + Athena's droid computes the view from a curated family taxonomy joined live to the droids/agents registry. Must satisfy the 8 Carol App Design System conventions.

⚖️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=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

• App lists droid families (functions replicated across >=2 agents) with main droid, function, member agents, and per-agent customizations (must_have)
• App lists potential families (single-agent droids likely needed by many agents later), incl RSI/consciousness/data-quality themes (must_have)
• App is owned by Athena, registered in the registry, on a free port, reachable through the dev gateway (must_have)
• App satisfies the 8 Carol App Design System conventions (canonical topbar, clickable app-header, responsive, palette, typography, layout, 44px targets, WCAG-AA) (must_have)
• Agent-centric: thin app window + shared shim + Athena droid does the computation (designs 146/173) (must_have)