Usage
Usage now carries the Day 4 commercial trace: subscription-funded credits stay visible through reservation, accepted execution, terminal usage, and later settlement holds on one shared control-plane surface.
Ledger Workbench
Usage now traces accepted execution through one commercial ledger
Day 4 makes the relationship explicit: subscription posture funds credits, accepted execution reserves them, usage records the commercial trace, and later settlement must derive from that same ledger instead of a parallel hidden path.
Service boundary: cloudflare-d1 · demo:error
Available
--
Reserved
--
Included plan
--
Settlement hold
--
Ledger state
Ledger data could not be loaded
This error-state demo stands in for a future billing or ledger API failure.
We need a stable error shell here before real credit transactions move into D1 and contract-checked API responses.