📖About

Ninad 2026-07-02: keep a SINGLE RSI dashboard app for all measures. Landing page lists all services in Services-Catalogue tile style; clicking a service opens its page with each RSI measure as a tab, every chart in the IDENTICAL Pipeline-RSI layout (line vs target + volume bars + week->day->item drilldowns where the metric supports it; the CPU dashboard had drifted). Owner: Prometheus. The four standalone RSI apps (pipeline-rsi 7260, infra-rsi 7262, blueprint-rsi 7264, process-rsi 7267) are decommissioned; all internal links (metric catalogue, both scorecards, Hermione's improvement engine) repoint to the new app. Computation stays in the owning agents' metric modules; the app is a thin window.

⚖️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)
• Orion verified: RSI consolidation live — Evidence: /dev/rsi/ app healthy on 7268 with catalogue (23 services, 4 with measures), trend/weekly/day/scoreboard APIs all returning real data; both scorecards link into it; 4 old apps stopped + deregistered + out of start.sh; rsi in start.sh. nginx route install runs via Radagast right after close (needs the reviewed initiative). (orion)
• [status-router] executing -> reviewing | event=bypass_reviewing | bypass transition (or-bx-01)
• Elrond re-scoped success criterion 999900471 (replace) on Albus's prescription — Policy P.01.02.04.16 (Elrond edits the initiative definition ONLY on Albus's prescription). Albus diagnosis: Original criterion was too vague — 'keep a SINGLE RSI dashboard app for all measures' has no artifact boundary. Without concrete deliverables, Forge cannot produce verifiable output and ir-s1 cannot review. The replacement defines file structure, framework, feature set, and review gate — bounded target for a single execution cycle. (elrond)
• Elrond re-scoped success criterion 999900471 (replace) on Albus's prescription — Policy P.01.02.04.16 (Elrond edits the initiative definition ONLY on Albus's prescription). Albus diagnosis: Original criterion was too vague — 'keep a SINGLE RSI dashboard app for all measures' has no artifact boundary. Without concrete deliverables, Forge cannot produce verifiable output and ir-s1 cannot review. The replacement defines file structure, framework, feature set, and review gate — bounded target for a single execution cycle. (elrond)
• [status-router] reviewing -> executing | event=bypass_executing | bypass transition (or-bx-01)
• Orion verified: CPU drilldown + sorted landing live — Evidence: /api/weekly?measure=infra_cpu returns the per-day outcome split; /api/day returns per-hour buckets (avg/peak, 95 samples on 2026-07-01); catalogue orders services by measure count; card badge shows the count. (orion)
• [status-router] executing -> reviewing | event=bypass_reviewing | bypass transition (or-bx-01)
• [status-router] reviewing -> executing | event=bypass_executing | bypass transition (or-bx-01)
• [status-router] executing -> reviewing | event=bypass_reviewing | bypass transition (or-bx-01)
• Elrond re-scoped success criterion 1 (replace) on Albus's prescription — Policy P.01.02.04.16 (Elrond edits the initiative definition ONLY on Albus's prescription). Albus diagnosis: The current criteria lack a measurable, bounded, verifiable outcome — they are vague aspirational text that cannot gate progress. Without bounded criteria, the dispatcher has no signal to declare the step done and loops on calling the troubleshooter. (elrond)
• Elrond re-scoped success criterion 1 (replace) on Albus's prescription — Policy P.01.02.04.16 (Elrond edits the initiative definition ONLY on Albus's prescription). Albus diagnosis: The current criteria lack a measurable, bounded, verifiable outcome — they are vague aspirational text that cannot gate progress. Without bounded criteria, the dispatcher has no signal to declare the step done and loops on calling the troubleshooter. (elrond)
• [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 single RSI Dashboard app (owner Prometheus, /dev/rsi/) serves ALL RSI measures; the landing page lists all services as catalogue-style tiles with measure chips (must_have)
• Each service page shows its measures as tabs, every trend chart in the identical Pipeline-RSI layout (line vs dashed target, volume bars, drilldowns where the metric supports them); CPU health now renders in this same layout (must_have)
• The four standalone RSI apps are decommissioned (processes stopped, registry rows removed, routes regenerated) and every internal link repoints to the new app (must_have)
• CPU health supports the same week-to-day-to-detail drilldown as the other trends (per-day below/above-50% split, per-hour detail), and the landing tiles are sorted by measure count with the count shown on each card (must_have)