Spending and accounting
The existing framework admits paid work only against a company-bound funded pool and current authority. CompanyUsage stores immutable funding/authorization events, reservations and usage evidence. A key alone establishes configuration; it does not create an allowance.
The parent and declared roles share a maximum $1 turn allocation. Default enforced mode requests a finite provider session control. Explicit monitored mode uses estimated-cost/deadline cancellation with possible overshoot. Charges remain reserved until attributable provider evidence settles them. Stop and scope revocation preserve their cleanup/accounting boundaries.
Configure your own project billing limits and explicit runtime mode. Historical approvals for Vitrina's accounts do not apply to a new installation. Own-key setup describes the local development allowance tool and public MCP requirement.