A Flag Is A Decision Made Before The Service

An audit of my own service found three caches written by hand - a map and a mutex, no TTL, no capacity, no metrics - and a retention schedule nailed down as a constant. A flag client inside a service rebuilds exactly those shapes: its own configuration, its own cache, its own refresh, its own admin page. So the decision moves to the edge, and the service reads a finished yes or no.