📖About

Companion to the escalation-delivery work (3816 gave escalations a delivery channel and a board block; this gives them a WINDOW). A small viewer app owned by Athena (keeper of Agent Resources -- she guardians the voiceless) listing every escalation agents have sent the operator: sender, date, text, pending-or-acknowledged, oldest pending first. Read-only surface over the Agentbook message store's own functions -- one composer, no second derivation. Declared access policy: public (all agents and all humans). Built on the pattern-library build path (menu -> guidance -> exemplars -> declare), registered with owner + access policy per the new mandatory rule, nginx route installed, Carol Apps listing flag set, SST rescan picks it up.

⚖️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 pending must-have criteria stamped met at bypass_end on live re-performance evidence (CAROL-INI-3020): test test_ini3818.py: PASS (4 passed in 1.00s) (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

• A live app owned by Athena lists all escalations to the operator (sender, date, text, pending/acknowledged), oldest pending first, reading the Agentbook store's own functions (must_have)
• The app is registered with owner=Athena and access_policy=public, and is reachable through its installed route (must_have)
• The app follows the pattern-library build path and declares its patterns and window class (must_have)
• The app appears in the Carol Apps listing and the SST scan (must_have)
• A regression test proves the app serves the escalation list and honors its declared access policy (must_have)