If a label requires the user to understand the architecture, it’s wrong
A non-technical household admin must never need to know what a container, a CRD or a namespace is. The translation is absolute — and the worst leaks hit the least technical person at their most anxious moment.
Nexus has two non-negotiables, and one of them is non-technical operability. Its UI principle follows: abstract the infrastructure, expose the intent; three mental models — people, services, infrastructure — not five. The test I apply to every surface, including my own: find the place where the wording degrades into platform vocabulary. It is usually exactly where the principle mattered most — a first-time owner staring at a stalled bootstrap.
The same instinct governs how I write architecture for ministries: if a principle can only be read by the people who wrote it, it will not be enforced.