Cost Allocation & Showback Platform  ·  View 18 of 22  ·  6 · Operations

Policy Promotion Pipeline

A rule change moves money, so it ships like code — authored, simulated against a closed period, reviewed, and reversible.

Editable source SVG draw.io All views
Author Rule change in Git declarative, reviewable Schema & lint gate Simulate Re-run closed period candidate vs current Per-team delta report who moves, by how much Review FinOps + affected owners over 2% delta Finance sign-off if chargeback on Adopt New policy version effective-dated Published to tenants before it applies Apply Next allocation run pinned to version Statement notes the version Reverse Roll back to prior version one command Re-run affected periods 45 min p95 Policy Promotion — A Rule Change Moves Money, So It Ships Like Code Application we own Decision point Data store Person or role Security / platform Interface / broker Application code deploys the same way, but policy ships on its own pipeline because its blast radius is every team's number. A delta the reviewers reject never reaches Adopt; a delta that surprises after adoption is reversed at Reverse, and the affected periods are re-run. v 1.0 · owner Platform Architecture · date 2026-09

Why policy has its own pipeline

  • Its blast radius is every team's number, not one endpoint's error rate
  • The simulation step reports the per-team delta before adoption, which is the only honest way to review it
  • Rollback is one command plus a re-run, because the allocation function is pure

Gates

  • Affected owners review any change moving a team by more than 2% (stated assumption)
  • Finance sign-off is required only when chargeback is enabled
  • The new rule is published to tenants before the run that applies it

Deliberately omitted

  • Application code delivery, which uses the organisation's standard pipeline and is not architecturally interesting here