VISION DOMAIN
Usage
Owns CONSUMPTION — meters define what to measure, records capture events, aggregations roll up into billing-period totals. 19 nodes in the knowledge graph — the smallest domain.
Per-product metering exists for Workers, R2, and Stream. Each has its own metering path. Usage data flows from product services to Stripe via usage records. No unified pipeline exists.
Nothing directly. Usage has no Q2 workstream. It's the one domain that waits — it needs the domain clock before it can land on domain invoices.
Centrally registered meter definitions — API calls, bandwidth, storage, seats. Currently per-product.
Every product meters independently, aggregates independently, and reports to Stripe independently. The gap is a single pipeline making metering a platform capability.
Threshold billing is deferred — it requires live payment, clean invoices, and Stripe migration capabilities that don't exist yet. The problem: usage-based products have an unbounded consumption window between billing cycles. R2 storage and Workers invocations are fraud targets. The solution needs real-time usage data flowing into the billing system.
Every product meters independently today. The vision is a single pipeline that makes metering a platform capability.