Carol — back to Apps ← Apps

Carolopedia

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

📖 CarolopediaServicesBuild InitiativesAll activitiesINI-999900169
📋

CAROL-INI-1951-00: Sprint planning observability and dispatch wiring

Initiative
Open in Initiatives →

📖About

Make the Backlog tab observability-only (remove the Rebuild button + build endpoint), have the Sprint Builder create 10 rolling sprints nightly, and surface the current-day sprint as dispatched in the Dispatch Queue card for Orion to push.

⚖️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-1951 bypass: 3 changes done + verified (observability-only backlog tab, 10 rolling sprints, today dispatched). bypass_end hung on the plangenerator.db lock storm; routing via the relay. (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

  • Backlog tab has no Rebuild button and the build POST endpoint is removed (observability-only) (must_have)
  • Sprint Builder creates exactly 10 rolling sprints and runs nightly (must_have)
  • Current-day sprint initiatives are marked dispatched and appear in the Dispatch Queue card (must_have)
  • Dispatched items do not auto-execute; they await Orion push (must_have)