The week's run tracked agent authorization as it fell through the stack: from UI to policy to token to a procurement line item. Today it crosses the last threshold. With ChatGPT Wallet, the agent becomes a transacting entity. Purchase authority now sits at the human-agent interface, scoped by approval thresholds and card protections rather than a separate checkout flow. This is the move the earlier briefs priced as inevitable once authorization reached the token. It arrived.
What moved since Friday is the asymmetry between the capability and the controls meant to hold it. OpenAI shipped spend. On the same days, Onyx Security integrated runtime governance into Glean, treating each agent's permission set as a live object with audit evidence per interaction, and AWS published a reference architecture where every action passes a governance gate before output ships, mapped to EU AI Act obligations. The governance layer was built before the spend surface opened. The question for principals is whether your own stack matches that sequence or inverts it.
Most do not match it. The Thomson Reuters numbers are the tell: 49% of companies expect a shadow AI incident within twelve months, and 18% have a documented usage policy. That 31-point gap is the deficit the 2026-W46 index registers as a Brand score of 44, the lowest dimension. Wallet-enabled agents widen it. An employee who already runs an unsanctioned tool can now hand that tool a payment surface, and the spend lands before anyone has named which agents may initiate it.
The instruction is concrete. Treat a wallet-enabled agent as a new class of non-human identity with financial permissions, and scope it before you enable ChatGPT Work access, not after the first disputed charge. The controls already exist as vendor patterns: runtime permission monitoring, intent-aware checks on prompts and responses, per-action audit trails. Ask whether these are native to your agent vendor or bolted on. The AWS five-pillar layer gives architects a model-neutral checklist, and the EU AI Act dates, December 2027 and August 2028 under the Digital Omnibus, mean teams building agents today are building against a live deadline. Early adopters convert that compliance work into recoverable infrastructure.
The spend surface is the easy part to ship and the expensive part to govern. The firms that priced the authorization logic down to the token this week should now price it one layer up, into procurement policy, before the agent does the pricing for them.
Watch item: Gemini 4 Carbon is generally available in GitHub Copilot across Pro+, Max, Business, and Enterprise plans, with token rates set to double on December 1, 2026, per GitHub Docs via NeoTeo. Validate Copilot budget allocations before the rate change lands.
Index Reference · Applied AI Index 2026-W46, the latest published issue (Sunday, November 15, 2026)
WatchGemini 4 Carbon is now generally available in GitHub Copilot across Pro+, Max, Business, and Enterprise plans, with token rates scheduled to double on December 1, 2026, according to GitHub Docs via NeoTeo. Enterprises on affected Copilot plans should validate budget allocations before the rate change takes effect.