Usage Metering & Billing Pipeline · View 17 of 22 · Operations
Decisions
- A price change is treated as a production deployment with a blast-radius preview, a dry run against real usage, and two human approvals. It is the only change in the platform applied uniformly to every affected account at once.
- There is no rollback in place. A wrong price is corrected by a further version plus a restatement of anything already rated under it — which is the same mechanism as every other correction, and that consistency is the point.
- The baseline for anomaly detection is re-armed on activation, so a deliberate price rise does not page everyone for a month.
Assumptions
- 2,000 live plan versions (stated assumption); the dry run samples the last closed period rather than re-rating all of it.
- A second approver is available within the working day. Month-end is exactly when this assumption is under most pressure.
Risks
- Both approvers can be wrong together, and the preview is only as honest as the sample it re-rates. This is named as residual risk in view 22 rather than engineered away.
- Effective-from dates that overlap are the classic defect; the conflict check exists for it, and a gap between versions is just as wrong as an overlap.
