NOMOS rethinks local agent distribution

This is a smart attack on the real bottleneck: setup friction, not model capability. The catch is that once the runtime owns auth, model bootstrap, and agent routing, the runtime becomes the product, so security and upgrade policy matter as much as packaging.

• –A single-file install flow is exactly what non-technical users need; `ollama pull` in a terminal is where adoption dies.
• –Shared credentials and state simplify onboarding, but they also create one security boundary for every agent in the environment.
• –The trust model needs signed manifests, capability scopes, process isolation, and destructive-action prompts or it will feel safer than it is.
• –The strongest version of this idea includes escape hatches for advanced users, so standalone agents can still register without forcing everyone through one stack.