Toll
Spend. Ownership. Utilization. Evidence.
- Problem
- Cost without engineering ownership.
- Input
- FOCUS evidence and identified utilization samples.
- Outcome
- Spend and utilization tied to engineering context — evidence, not an invoice.
- Availability
- In development. Spend and waste execution still run in Repave.
by OpsDevCode
Job
Connect spend and utilization evidence back to engineering ownership and decisions — as evidence, not as an invoice.
Toll is the engineering economics product: it connects cost and utilization evidence to ownership without becoming a billing warehouse or a savings engine.
FOCUS ingest, persistence, and utilization sampling run in Toll. Spend attribution and waste recommendation still execute in Repave until later extraction. Toll does not invoice, execute purchases, or claim savings percentages.
The policy direction is economic context: attributed spend, budgets, and thresholds as constraints that can require approvals or evidence near a cost boundary. Toll does not enforce spend in real time today.
Current state
In development. FOCUS ingest/persistence and utilization are implemented in Toll. Spend attribution and waste recommendation still execute in Repave. Not generally available. No savings percentages.
Owns
- FOCUS ingest and persistence as cost evidence
- Utilization sampling from identified sources
- Engineering identity for ownership correlation
- Product authority for spend-to-ownership questions; spend/waste execution still in Repave
- Refusal to treat missing utilization as zero
- Period capture without invoice authority
Boundaries
- Invoicing and purchase execution
- Autonomous commitment purchases
- A full billing warehouse
- Software delivery (Repave) or state custody (Overpass)