Andrew Fribush

fig. 2.6.1: one worker’s weekly cap over ten events: admitted with a hold, refused before upstream, settled

fig. 2.6.1 · one worker’s weekly cap over ten events: admitted with a hold, refused before upstream, settled.
CALL F OVER THE CAP, HOLDS INCLUDED: REFUSED BEFORE UPSTREAMONE BAR IS ONE WORKER’S 1,000¢ WEEKLY CAP: INK SETTLED, GREY HELD IN FLIGHT,ACCENT THE NEW CALL’S ESTIMATE.0CAP 1,000¢SETTLED 135¢IN FLIGHT 650¢THIS CALL 240¢CALL F · 135¢ SETTLED + 650¢ IN FLIGHT + 240¢ ESTIMATE = 1,025¢ > 1,000¢ CAP402 · THIS WORKER'S WEEKLY BUDGET CAP IS REACHED · NO UPSTREAM REQUEST, NO HOLDWORKERWORKERAUTHENTICATEAUTHENTICATEPRE-AUTHORIZEPRE-AUTHORIZEHOLDHOLDUPSTREAMUPSTREAMMETER AT THE WIREMETER AT THE WIRESETTLESETTLE402 · NO UPSTREAM CALL402 · NO UPSTREAM CALLEVENTS IN ORDER · ● A CALL ARRIVES · ○ A CALL SETTLES · DRAG THE AXIS TO REPLAYABACDBEFCFTHE SAME CHECK, IN THE SAME TRANSACTION, RUNS UNDER THE ACCOUNT’S WEEKLY CEILING,THE MINTING TOKEN’S LINEAGE BUDGET AND THE PREPAID BALANCE.

source: Mechanism from creelshed apps/web/server/model-proxy.ts: reserveAndAuthorize lines 103-205 (worker cap branch 154-165, hold written 176-183), estimateCostUcents 611-625, settle 629-665; amounts are a synthetic sequence

View in context: Spending limits for autonomous agents → · All figures

Andrew Fribush, software and computer engineer in Austin. I build consequential systems where software meets institutions: finance, healthcare, commerce, government data, and the mechanisms that govern AI agents. Taking new engagements: hello@andrewfribush.com.