📖About

Anthropic publishes the plans own usage to the Max sign-in (weekly + five-hour utilization with reset times), so the box joins the read-allowance pattern: euro fee as top-up, the computed euro equivalent of the weekly share left as the balance (dotted computed mark), the read percentages in the card detail. The subscription record also stops claiming measurability Carols ledger does not have.

⚖️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)
• CAROL-INI-3717 D1: the Claude Max balance was derived as fee-minus-ledger while the operator CLI never passes Carols ledger — unmeasured rendered as untouched. Cured by READING the plan: Anthropic publishes weekly + five-hour utilization with resets to the Max sign-in already on the machine.
• CAROL-INI-3717 D2: the box joins the read-allowance pattern — euro fee as top-up, the weekly share left as the computed-euro balance (dotted mark), both percentages in the card detail; exhausted when the week is fully used.
• CAROL-INI-3717 D3: claude left the no-balance excuse list; the subscription record stops claiming measurability (measurable=0) so no surface may again derive this lane from a ledger that cannot see it.
• [delivery-check] 5 pending must-have criteria stamped met at bypass_end on live re-performance evidence (CAROL-INI-3020): test test_ini3717.py: PASS (4 passed in 2.45s) (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)
• CAROL-INI-3717 D4 (UAT rework): the balance slot shows the READ share plain (91% left) — a flat plan publishes no money figure, so the euro equivalent is removed entirely, field and all; the display always comes from the live endpoint reading, never a figure typed in. Design v1.2.
• [status-router] executing -> reviewing | event=bypass_reviewing | bypass transition (or-bx-01)
• [status-router] reviewing -> executing | event=bypass_executing | bypass transition (or-bx-01)
• [recovery] queue row revived in place — the execution had died leaving status=executing with no live queue row; the step-advance sweep relaunches the current step (CAROL-INI-2981) (elrond.handover_watchdog)
• [status-router] executing -> reviewing | event=dispatcher_transition | dispatcher state change (ds-s1)
• CAROL-INI-3717 D5 (UAT rework 2): the flat-plan box lives in the providers weekly window — top-up = the weeks share of the monthly fee, balance = the READ share left of it, both computed-marked; a weekly % is never scaled against the monthly fee. Freshness is the VM-side half-hourly sweep (laptop-independent) with age on the card. Design v1.3.
• [status-router] reviewing -> executing | event=bypass_executing | bypass transition (or-bx-01)
• CAROL-INI-3717 D6 (UAT rework 3): monthly frame — the fee is the real top-up (the monthly invoice), the balance is fee minus each windows MEASURED use accumulated from stored readings over the RUNNING billing cycle (billing-day shift; 10-min reset bucketing against provider jitter), computed-marked and dated; no readings = bare read share, never a guess. Design v1.4.
• [status-router] executing -> reviewing | event=bypass_reviewing | bypass transition (or-bx-01)
• [status-router] reviewing -> executing | event=bypass_executing | bypass transition (or-bx-01)
• Design v1.5.
• [status-router] executing -> reviewing | event=bypass_reviewing | bypass transition (or-bx-01)
• [status-router] reviewing -> executing | event=bypass_executing | bypass transition (or-bx-01)
• CAROL-INI-3717 D8 (UAT rework 5, accuracy pass): floor-bucketing split a jittering reset stamp into two windows and double-charged the Claude week (204.04 -> 208.88 corrected, round-to-nearest bucket); the flat-plan caption now names the WINDOW (weeks allowance used) so it cannot contradict the monthly balance; every box value re-derived and verified against its inputs. Kimi fee discrepancy (sub 17.28 vs billing record 20.00) flagged to Ninad — a money declaration is his to settle. Design v1.6.
• [status-router] executing -> reviewing | event=bypass_reviewing | bypass transition (or-bx-01)
• No box value changes.
• [status-router] reviewing -> executing | event=bypass_executing | bypass transition (or-bx-01)
• CAROL-INI-3717 D10 (UAT rework 6, sync pass): the lower tables had their own second derivation and drifted — Gemini read active-healthy beside an out-of-credit box, and a derived Claude API balance wore the vendor-API label. Status and Balance now QUOTE the boxes composer (one vocabulary, euros, read/computed named); Claude Max stays out of the chart in its Not-charted card; dead OpenCode row dropped (registry decides existence); the browser tests grey rule updated to the composers exhausted flag. Design v1.7.
• [status-router] executing -> reviewing | event=bypass_reviewing | bypass transition (or-bx-01)
• [status-router] reviewing -> executing | event=bypass_executing | bypass transition (or-bx-01)
• CAROL-INI-3717 D11 (UAT rework 7): the chart shows CONSUMED while the boxes show LEFT, which read as mismatched numbers — each chart row now states its boxs balance in the caption from the same composer (verified row-for-row: 14.21 / -0.69 / 9.80 / 0.00 / 16.62), with the two irreconcilable-by-nature cases (list-price bar, vendor-empty) still named. Design v1.8.
• [status-router] executing -> reviewing | event=bypass_reviewing | bypass transition (or-bx-01)
• [status-router] reviewing -> executing | event=bypass_executing | bypass transition (or-bx-01)
• CAROL-INI-3717 D12 (UAT rework 8, Ninad ruling): the summary boxes numbers ARE the chart — each row plots its boxs top-up as the bucket and balance as the bar, verbatim from the one composer (verified row-for-row); consumption moved to the drill and flat-plans table; header, legend and caveat rewritten; Claude Max still only in the Not-charted card. Design v1.9.
• [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

• A Claude Max reader reads the plans weekly utilization and reset from Anthropics own usage endpoint via the Max sign-in already on the machine, failing plainly when the sign-in needs renewing (must_have)
• The Claude Max box shows the euro fee as top-up and the computed euro equivalent of the weekly share left as balance in the computed mark, with the read percentages (weekly and five-hour) in the card detail (must_have)
• Claude leaves the no-balance excuse list — the plan does publish usage (must_have)
• The subscription record no longer claims the CLI lanes consumption is measurable by Carols ledger (must_have)
• A regression test guards the reader contract and the box shape (must_have)