📖About

Carol Intelligence renders only the One Model per Block compliance banner; the One Subscription per Track check (policy P.01.03.07.03, already computed by the compliance module) is missing from the app. Fix: the intelligence API augments its snapshot with the live per-track subscription check, and the page renders a second banner - green tick when every track runs on one subscription, red with the violating service/track/provider list otherwise. Fail-open: if the check errors the banner hides rather than blocking the page.

⚖️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)
• The intelligence API augments the provider snapshot with the live one-subscription-per-track compliance result (single source: the compliance module; a check error nulls the field and the page hides the banner, fail-open); the page renders it as a second policy banner alongside one-model-per-block. (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 Carol Intelligence page shows a One Subscription per Track banner: a green tick when every track runs on one subscription, or the violating tracks with their providers when not. (must_have)
• The banner reads the SAME live check the compliance module computes (no second derivation), and an error in the check hides the banner instead of breaking the page. (must_have)
• A registered regression test proves the API carries the check and the page renders it. (must_have)