npmctl exists to keep operational truth legible. It is most useful where teams want the public edge to be reviewable before it is changed and reapplicable after it has drifted.
Context
Operational state such as DNS, certificates, and proxy hosts often drifts because the public edge is maintained through hidden dashboard state rather than explicit desired state.
Constraints
Provider state must be expressible declaratively.
Plans must be reviewable before apply.
The tool must work across multiple sites and organizations.
Architecture
Desired-state files define provider-backed resources.
Plan and apply flows separate review from mutation.
Repo ownership keeps infrastructure decisions close to deploy surfaces.
Outcomes
Reviewable DNS and proxy workflows.
Less dependence on dashboard memory.
Clearer provenance for public entry state.