Slice 1 changes no behaviour at all: the derivation runs, the metrics appear,
and the scanner keeps reading the old list. Its acceptance is a number already
known by hand — 24 missing, 2 orphaned, coverage near 0.52. If the derivation
disagrees, the derivation is wrong, not the hand count stale.
Rolling out is a handover, not a step of mine. Port 2248 on the operating host
answers from the matrix node and agent forwarding carries, but the key is not
authorised there, so the procedure written after this very stack applies:
whoever builds hands over, whoever deploys verifies and writes the AAR. The
quantities that procedure demands are in the doc: about 65 targets instead of
29, about 90 registry requests per derivation, and up to 65 possible messages a
round where yesterday brought 12.
Slice 2 sets the missing-targets rule above the current value on purpose and
only pulls it to zero in slice 3, so the room never learns to live with a red
alert. Slice 5 is where this can still fail quietly: if cAdvisor only shows what
runs, a stopped service is absent from the desired set and coverage still reads
100 percent.
Thore Cimbal
e316193f9c