Where secrets go
A store gives a secret a place to rest, but the value itself still has to arrive: enter under control, reach the runtime, build, deployment, and local-development surfaces, and leave evidence that live state still matches what was declared. This series names that route as one delivery transaction, reviewable before it scatters across console clicks, scripts, and build credentials nobody wants to call the authority.
- A secret has to arrive
One logical credential slot becomes a delivery problem when production, local development, build automation, and deployment code all need it in different forms, and the route has to be recorded as state