Released 2026-08-24. The 1.66 arc closes: per-label, per-session and per-day USD ceilings, stated once, judged once, enforced identically at whichever door the call arrives — and a test that goes red the day any door starts agreeing by coincidence again.
Added#
- The doors hold the line — chapter three of the 1.66 arc. The gateway's
402,
serve's cost answer andspend_guardover MCP all carry the samepolicyjudgement, produced byjudgeLimits— none of the three does arithmetic of its own.three-doors.test.jsproves the sibling-agreement property the hard way: the same policy, the same measured position and the same call go through all three doors and the judgements must match field for field — then a door is deliberately broken twice (a forged field, andservestarted without its measured side) to show the comparison can fail. The measured side is a usage log:--logonserveandgateway(per-label and per-session spend live in a usage log, not in the store's provider buckets),positionfigures passed explicitly tospend_guard, whoselimitsargument is validated by the config file's own parser so a pasted policy and a committed one cannot mean different things. The gateway readsmetadata.trazum_sessionat the same seam as the label; session identifiers are used to judge and never echoed, recorded or printed, and the suite greps every door's output for the key to prove it. A crossed ceiling is HTTP 402limit-overat the gateway,noat the guard, andpolicy.verdict: "over"in the cost answer. Unpriced records in the--logare counted and announced at startup — money the policy cannot see, said out loud. Also fixed on the way in, reproduced first against the shipped build:servecrashed outright on{"inputTokens": -5}— the core's negative-figure refusal was an uncaught throw inside the request handler, taking the whole oracle down; it is a 400 now. - Refusal is legible, and silencing one leaves a record — chapter four.
Every over-limit refusal names the limit, the measured spend and the
period in one sentence, built once (
limitSentence) and spoken by every door — an agent can log it and a person can audit it without re-running anything. Thewaivemechanism applies to limits unchanged: gateslimits.dayUsd,limits.sessionUsdandlimits.byLabel:<label>, each with the mandatory reason and expiry. A waived ceiling keeps itsover— the measurement is the measurement — but the policy does not refuse it, the waiver rides in the judgement with the reason and end date so every answer from every door is the record of the silence, and the day it expires the ceiling refuses again. - The library judges it — chapter two of the 1.66 arc.
judgeLimitsin@trazum/core: one function takes thelimitspolicy, the measured position and a proposed call, and answers within, over or cannot-tell — one judgement per applicable ceiling, each carrying the limit, the measured spend, the window it covers and where the scope would stand after the call. Nothing is re-derived: every ceiling is judged byanswerCost, the same single-budget semantics every door has used since 1.44, refusals included (negative token counts throw, an unpriced model is a cannot-tell, andrestsOnsays whether the verdict needed the estimate). Two refusals are the module's own and both close the same loophole: per-label ceilings judging a call that names no label, or a session ceiling judging a call with no session, answercannot-tell— a call that omits its label does not slip past the ceiling, it becomes unjudgeable, with the smallest ceiling named as the one it might be dodging. Verdict precedence is the only safe one: over, then cannot-tell, then within, because "within" must mean everything was judged. An empty policy isno-policy, never "within". - The policy has one shape — chapter one of the 1.66 arc. A
limitsblock intrazum.config.json: per-day (dayUsd), per-session (sessionUsd) and per-label (byLabel) USD ceilings — the enforcement policy every door will read, stated once. Deliberately separate fromspend: a report gate is read after the fact over a log, an enforcement ceiling is read before a call is made to refuse it, and two surfaces reading "the same" value from different slices of config is the 1.62 arc's defect waiting for its input. Validation is stricter thanspendin exactly one way: every ceiling must be a positive finite number, because a zero enforcement ceiling refuses every call at that door — an outage dressed as a policy, and the error says what to write instead. Unknown keys insidelimitsare named with the nearest real key rather than ignored. The help documents the block in both locales and the skill names it, both held by the existing derived guards.