docs: specify cost-shape boundaries for whole-task budgets (#56) #94
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "issue-56-task-cost-shapes"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Scope
This is the explicitly permitted parallel specification slice for #56. It records the current, source-grounded Kernel cost shapes (
BudgetPolicy,UsageObservation,export_outcomes,QuotaSnapshot) and the boundaries between admission counts, usage observations, quota snapshots, and Router #184's strict no-PAYG admission evidence versus actual billing.The planned composition rules preserve units, provenance, receipt corrections, Attempt lineage and unknowns. This does not implement an aggregator, whole-task budget enforcement, route/call correlation, streaming process bounds, numeric thresholds, or provider billing claims. #52 and producer evidence remain prerequisites for those portions; issue #56 stays open and this PR does not satisfy its full acceptance criteria.
Validation
make check: 1457 passed, 85 skipped, 106 subtests; formatting, Ruff, basedpyright, import boundaries, secret scan and diff checks passed.make package-check: reproducible wheel/sdist, isolated install and CLI/intake/source smoke checks passed.Refs
Refs #56
Base:
a7da7c788503edcec85af9485b1f72913be0e632Head:
a2f910b87aadb79543f1df101eb9c16273834866No live inference, telemetry, Router operation or external effect was used.