📖About

Fix per Ninad: budgets become first-class registry entries. New budget_allocations table = single source of truth keyed by scope; thin accessor; daily_budget reads registry-first with JSON fallback (no behavior change). New Midas app Daily Budget Cap Monitor. Built via Sage add-new-app contract. Bypass, initiative owner Orion; app owned by Midas.

⚖️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=bypass_reviewing | bypass transition (or-bx-01)
• [status-router] reviewing -> executing | event=bypass_executing | bypass transition (or-bx-01)
• Handover-watchdog: planner-pending nudge for phase 2 (auto-invoked Elrond planner). (elrond)
• Handover-watchdog: planner-pending nudge for phase 2 (auto-invoked Elrond planner). (elrond)
• [status-router] executing -> reviewing | event=bypass_reviewing | bypass transition (or-bx-01)
• [agt_028.mind] dispatched my droid ca-s2 (sequence next): Run an on-demand compliance audit across the reviewing queue, starting with CAROL-INI-3222-00 (budget allocations as registry entries) and CAROL-INI-3220-00 (making the Carolverse Map public): check each against constitution, budget policy, and privacy rules — public exposure items get privacy scrutiny first. Report findings into Themis Monitor so the reviews are grounded, not rubber-stamped. — My goal is that every build is checked against policy before it ships. Ten initiatives sit in reviewing; two involve budget governance and one publishes an internal map publicly — exactly the class of change that needs an impartial audit before approval. ca-s2 is my on-demand auditor; dispatching it is precisely what I own. (agt_028.mind)
• Orion remediated: INI-999901990 bypass closed — CAROL-INI-696 close-marker: the Orion bypass INI-999901990 filed against this parent reached terminal state (closed). This row's literal prefix Orion remediated: is the canonical signal the cookbook-155 dispatcher gate looks for. (shared.bypass.bypass_end)
• Orion remediated: INI-999901990 bypass closed — CAROL-INI-696 close-marker: the Orion bypass INI-999901990 filed against this parent reached terminal state (closed). This row's literal prefix Orion remediated: is the canonical signal the cookbook-155 dispatcher gate looks for. (shared.bypass.bypass_end)
• [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 Carolverse service and every track has a daily budget stored as a row in the registry that an operator can edit (must_have)
• The new Daily Budget Cap Monitor app lists every service with its owner and basic info, showing each service daily budget versus what it has spent today (must_have)
• The daily caps that gate spend (fleet, providers, per-agent, consciousness) are read from the registry as the source of truth, with json only a synced mirror; effective caps unchanged. (must_have)
• The Token Cost Tracker by-service chart shows each service its real registry budget instead of a share of the fleet cap. (must_have)