supply chain: tiered mirrors (central cloud mirror -> site mirrors) in prose, ledger card and blueprint

2026-08-17 15:50:30 +10:00
parent d0efbe0194
commit a201af9d29
3 changed files with 36 additions and 18 deletions
@@ -42,6 +42,11 @@ from Move 1 is what makes the mirror actually catch the traffic.
 FIELD NOTE: a mirror can also serve a STALE tag->digest mapping while upstream moved the
 tag. Pin by digest and the whole chain becomes content-addressed - the mirror cannot be
 wrong about a hash.
+TIERING (added 2026-08-17, owner ask): at real fleet scale the mirror itself tiers - a
+central pull-through in the cloud fronts upstream once; per-site mirrors pull from the
+centre; nodes pull from their site over the LAN. The load fans out in layers instead of
+every site hammering upstream at once. Say it: mirrors tier - the load fans out in
+layers, never all at once.

 ## Move 3 - Build once, promote by copy
 The anti-pattern: rebuild the image for each environment ("the prod build"). Every