Five pillars, shipped as one operating model.
Nomos is not a set of features bolted together. Each pillar assumes the others exist — which is what makes the whole thing an operating system rather than a toolkit.
Work gets a shape before it gets a model.
A chat list is not an information architecture. Nomos gives work the same containers organizations already think in — projects, sessions, documents — so a thread of work can be found, resumed, and handed off.
One workspace. Every model reachable.
Routing is a policy, not a preference. Task class, data sensitivity, and cost decide which model runs — and the same request can move to a local runtime without the operator changing how they work.
Memory that outlives the session and the vendor.
Nomos keeps three things that chat interfaces throw away: the decision, the source it rested on, and the constraint that shaped it. Retrieval is scoped by permission, so memory can be shared without being leaked.
Authority is data, not a setting screen.
Every capability an AI holds is an explicit, inspectable grant: who gave it, what it covers, when it expires, and what was done under it. That record is what makes autonomy deployable in a regulated organization.
Work that finishes, not output that needs a human to finish it.
Agents and scheduled jobs act inside the same scope, memory, and authority as the operator. Execution is observable while it runs, and every step is attributable afterward.
See the layer beneath the pillars.
The architecture page documents the stack, the request lifecycle, and the deployment posture behind everything on this page.
Stage 01 is in active development: a complete personal operating system, with the organizational pillars defined in the architecture.