Storage Tiering Service  ·  View 24 of 31  ·  6 · Operations

The Placement Bet Lifecycle

How every placement is made, held, measured against the prediction that justified it, and fed back into the next policy version.

Editable source SVG draw.io All views
Observe access aggregates Decide break-even recorded Move copy · verify · commit Dwell ≥ 14 days Measure reads · charges Score predicted vs realised Tune new version · shadow Placement bet window elapsed decision id committed dwell over day 30 · day 90 per version shadow passes A Placement Is a Bet — Made, Held, Scored, Improved Application we own Decision point Security / platform Data store Opportunity v 1.0 · owner Storage Platform Architecture · date 2026-09

Decisions

  • Every placement carries the decision that made it, and every decision carries its predicted read probability and break-even instant. A placement that cannot be scored afterwards should not have been made.
  • Dwell of at least 14 days per tier, and promotion must clear three times the demotion margin. Together they stop an object oscillating while each individual decision looks locally right (ADR-20).
  • Scoring happens at day 30 and day 90 per policy version: realised against predicted break-even, and charges attributed to the version.

Why it is a ring

  • A tiering platform that does not score its own decisions will keep making the same wrong one at the same margin forever, and its bill will show it only as a vague shortfall.

Omitted

  • Promotion on read. It enters the ring at Decide, like any other move, with its own higher bar and a first read never enough on its own.