📖About

Phase 4 of the blueprint service roadmap (BLOOM phase: Optimize). Goal: A governed improvement loop with cost truth. Scope is the roadmap record at services/blueprint/bloom_roadmap.json (filed under 3828), rendered live on the BLOOM app; instantiation and ownership rules per design #557 and policy P.01.03.07.08. Cures gaps P1, P2, P3, P4, P5 from the blueprint-vs-BLOOM assessment. Modules: 4.1 Revive blueprint RSI — Register the RSI app, stand up a new engine droid with run-audit, one improvement initiative at a time against this roadmap.; 4.2 Cost truth per project — Compare actual spend to the approved estimate, per project.; 4.3 Docs + service growth — A lane that folds learnings into records and adds new services on their own tracks.; 4.4 Product-to-business conversion — A checklist that packages a delivered project commercially.

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

• The first improvement initiative is filed by the loop itself. (must_have)
• Variance is visible for every live project. (must_have)
• The first added service runs on its own track. (must_have)
• One project is packaged with offering and pricing. (must_have)
• Leo's external chat is wired to this phase's BLOOM actions: every artifact the phase introduces is reachable as a chat action (asked, shown, or executed) through Leo's chat interface, and the app handbook and Leo's agent handbook are updated with the actions possible via Leo's chat. (must_have)