The storage economics lead is the customer: the service exists to turn a bill that grows with everything ever uploaded into one that grows with what is used. Every other actor constrains how that saving may be earned.
Product engineers must never need to know a tier exists. Their only exposure is a recall class and, for a small fraction of reads, a job handle.
Legal operations and the security officer hold vetoes. A hold outranks any saving, and a bulk recall is a security event as well as a cost event.
Machines with obligations
The ML training pipeline is listed as an actor because its reads look exactly like a corpus warming up. Unless it declares itself non-promoting, a single training run reclassifies everything as hot and undoes a quarter's saving.
The reconciler is an actor because it has a goal nobody else holds: finding bytes the catalogue does not name.
Journeys mapped
View 04: rolling out a demotion policy. View 05: recalling a custodian's archive for a court date. View 06: reversing a classifier regression at night.
