📖About

Audit the current blueprint implementation (app, records, client->account->project model, experimentation/industrialization split) against the BLOOM methodology phase by phase, record the gaps, and produce a roadmap for the blueprint service - phases, modules, milestones - with every gap mapped to a roadmap module. The roadmap lives as a record, not prose in a memory file.

⚖️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=dispatcher_transition | dispatcher state change (ds-s1)
• [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] reviewing -> closed | event=operator_signoff | Auto-accepted (CAROL-INI-1859): Orion-initiated, >2 days in reviewing with no objection. (el-srac-01)

✅Success criteria

• Every BLOOM phase is checked against the current blueprint implementation with per-phase findings recorded (covered / partial / missing, with evidence). (must_have)
• A roadmap for the blueprint service exists as a record with phases, modules and milestones, and every identified gap maps to a roadmap module. (must_have)
• The gap analysis and roadmap are visible on an appropriate surface (the BLOOM app or the blueprint app), rendered from the record. (must_have)
• The five BLOOM phases are registered as the building blocks of the blueprint service's tracks — one isolated functionality each, chained Blueprint->Learn->Orchestrate->Optimize->Manage, replacing the four legacy blueprint blocks — and render on the block surfaces. (must_have)
• The blueprint roadmap is aligned with BLOOM: each roadmap phase maps to exactly one BLOOM phase and the rendered surface shows that mapping. (must_have)