Spend and residency reported on the same ledger
The ledger reports spend, serving region, the team or key making the request, and the policy applied.
- 5
- Query dimensions
- Exportable
- Residency evidence
- Counted
- Refusals, alongside traffic
Day, model, key, team, jurisdiction
01
Design
How this part works
Spend queries
Cost is queryable by day, model, provider, key, team and jurisdiction.
Residency as an exportable record
Every request produces a row naming its jurisdiction decision, the provider that served it and the region that ran it. The export provides the record for review.
Refusal counts
Requests refused for residency reasons are counted alongside successful ones. Refusal counts show coverage gaps.
Spend ceilings and team overrides
Spend ceilings and per-team overrides operate at the policy layer. Cost controls cannot break a residency guarantee.
02
Comparison
Boundary-first routing
Example cost-only dashboard
- Answers what was spent
- Region is inferred from provider name
- Refusals appear as errors
- Answers what was spent and where it ran
- Region is recorded per request
- Refusals are a measured outcome
03
Elsewhere on the platform
Other platform features
Start