Roadmap
Ledger is building upward in deliberate layers. Provider cost calculation must be correct first. Business attribution then moves published cost through explicit entities, measurements, and rules without reopening provider billing logic.
Import provider evidence, normalize financial fields, calculate service and resource costs, reconcile totals, publish Cost Pools, and explain every amount.
Model services, products, customers, teams, and features. Use measured denominators and explicit allocation rules to move already-calculated cost.
Answer cost-per-unit and margin questions with a complete path back through allocation, Cost Pools, calculations, normalized charges, and evidence.
The boundary that matters
AWS, Azure, Google Cloud, AI providers, payroll, support, and SaaS calculators each own their source economics. They publish normalized Cost Pools. Attribution consumes those immutable facts alongside business entities and measurements.
Initial attribution model
The graph will describe cost flow through a business, not become a workflow engine or general programming environment.
Services, products, features, customers, plans, teams, regions, and business units, introduced only when the product needs them.
Requests, transactions, seats, usage, revenue, or another measured quantity tied to a period and source.
Direct assignment, proportional allocation, and carefully defined shared-cost treatment rather than arbitrary scripts.
Every result retains rule, inputs, assumptions, allocation path, source Cost Pools, and raw evidence lineage.
The destination
A useful answer includes the amount, denominator, direct costs, allocated shared costs, unallocated remainder, rule versions, and confidence in the underlying mappings.
What will not change
Open development
Significant decisions are recorded as ADRs, public interfaces are documented, and the architecture favors a small number of concepts that founders can explain to finance and engineering.