{"artifact":{"apiPath":"/api/reports/agent-treasury-controls-2026/charts","byteLength":3529,"description":"Structured chart payload backing the inline report visuals and machine-readable consumers.","format":"charts","label":"Chart data artifact","mimeType":"application/json; charset=utf-8","priceUsdc":0,"sha256":"6d1f8e2038072ff2b5fda2bed92ac39bb23213d6ef6d1527e17cbcb66a91f40e","status":"live"},"document":{"charts":[{"caption":"Routine spend should stay runtime-policy heavy. Refill, rebalance, payout, and scope release shift toward custody, finance approval, and owner step-up.","chartType":"bar","points":[{"label":"Routine API or tool spend","note":"Quiet recurring work should mostly stay inside caps, allowlists, and policy checks while the delegated envelope is still valid.","values":[4,1,1,0]},{"label":"Wallet top-up or refill","note":"A refill extends what the system may keep doing later, so finance approval and custody policy should dominate more than runtime convenience.","values":[2,3,4,0]},{"label":"Cross-rail rebalance or bridge","note":"Rebalancing changes rail exposure and counterparties, so custody controls and treasury review should outweigh ordinary spend logic.","values":[1,4,3,1]},{"label":"Customer payout or refund","note":"Outbound value transfer needs named accountability, destination review, and sometimes fresh user presence.","values":[1,2,4,2]},{"label":"Private-route or policy expansion","note":"Changing what the system may touch is a governance event, so runtime delegation should give way to release review and fresh owner presence.","values":[0,1,2,4]}],"series":["runtime policy","custody policy","finance approval","fresh owner step-up"],"title":"Which treasury control surface should dominate each action","unit":"relative control weight"},{"caption":"Routine spend usually belongs to the product lane. As money movement gets less reversible or more authority-extending, treasury and owner lanes should take over.","chartType":"bar","points":[{"label":"Routine API or tool spend","note":"Quiet product execution should stay close to the operator as long as policy, budget, and destination rules remain valid.","values":[4,1,0]},{"label":"Wallet top-up or refill","note":"Refills should usually be a treasury decision because they extend future authority more than they resolve a product workflow question.","values":[1,4,1]},{"label":"Cross-rail rebalance or bridge","note":"Rebalancing often needs treasury judgment plus stronger review because it changes rail exposure and recovery assumptions.","values":[1,3,2]},{"label":"Customer payout or refund","note":"Outbound transfers need finance ownership and, when the movement is sensitive enough, a stronger owner or compliance checkpoint.","values":[1,3,3]},{"label":"Private-route or policy expansion","note":"Release and scope expansion should be dominated by owner or security review, not by day-to-day product operators.","values":[0,1,4]}],"series":["product operator","treasury or finance owner","security or executive owner"],"title":"Who should own the final decision for each treasury action","unit":"relative ownership weight"}],"generatedAt":"2026-03-24T00:00:00.000Z","slug":"agent-treasury-controls-2026"},"generatedAt":"2026-05-04T00:12:23.138Z","kind":"deep_report_charts","operatorAccess":null,"payer":null}