nomosV0.1 · ALPHA
A00Architecture

The stack that makes models replaceable.

State, authority, and history live above the model boundary. Everything below it is substrate — swappable per task, per tenant, per data class.

State
Owned by Nomos
Model boundary
One adapter contract
Deployment
Cloud · hybrid · on-prem
Posture
Deny by default
001Layer stack

Seven layers, one boundary that matters.

The layers above the model boundary hold everything that is expensive to rebuild: identity, structure, memory, policy, and the execution record. Providers change often. Those five do not.

rule: no layer above the boundary may hold a provider-specific assumption
L7
Interface
workspace, sessions, review surfaces
web · desktop · api
L6
Identity & scope
people, teams, orgs, agents as principals
sso · scim · roles
L5
Work model
projects, sessions, documents, tasks
structured, queryable
L4
Memory & knowledge
durable context, semantic index, lineage
scoped retrieval
L3
Governance
permissions, approvals, policy, audit
enforced in-path
L2
Orchestration
routing, agents, jobs, tool calls
policy-driven
MODEL BOUNDARY
L1
Model substrate
cloud APIs, local runtimes, MCP, systems of record
swappable
002Request lifecycle

Every request passes through governance before it reaches a model.

Policy is not a wrapper around the output — it sits in the path. A request that violates a constraint never reaches the substrate, and the attempt is still recorded.

01
Intent
Operator or agent states what should happen, inside a session.
02
Resolve scope
Principal, project, and data class are attached to the request.
03
Policy check
Permission, constraint, and approval requirement evaluated.
04
Assemble context
Memory retrieved within scope; nothing outside it is visible.
05
Route & execute
Task class selects the runner; tools called under the same grant.
06
Commit & record
Result, lineage, and authority written to durable state.
denied at 03 → request never leaves the boundary · attempt still audited
held at 03 → queued for a named approver, with full request context
003Core objects

A data model, not a transcript format.

Because work is modelled as objects with relationships, it can be queried, permissioned, exported, and reasoned about by other systems — including the ones an organization already runs on.

PrincipalAnything that can act: a person, a team, an org, or an agent.holds → grantsbelongs to → orgtenant
ProjectThe scoped container for a body of work and its knowledge.contains → sessions, documentscarries → constraintsorg / team
SessionA resumable unit of work with its own history and sources.references → memoryproduces → artifacts, actionsproject
Memory recordA decision, source, or constraint with lineage and validity.derived from → sourcesupersedes → recordproject / org
GrantAn explicit capability: scope, expiry, and approval requirement.issued by → principalconstrains → actionexplicit
ActionSomething that happened in the world, and what permitted it.authorized by → grantrecorded in → audit trailimmutable
004Deployment & data posture
MODE 01
Cloud
Managed on Azure. Fastest path for individuals and small teams; provider APIs used directly under policy.
tenant-isolated stateprovider APIs in-pathstage 01–02
MODE 02
Hybrid
Control plane managed; sensitive task classes pinned to local runtimes. The routing table decides what may leave the perimeter.
per-class data residencylocal runtime for restricted datastage 03–04
MODE 03
Self-hosted
Entire operating layer inside the customer perimeter, including memory and audit. Intended for regulated deployments.
no egress by defaultcustomer-held keysstage 04+ · architecture defined
status: modes 02–03 are defined in the architecture and sequenced on the roadmap · not yet released
005Integration surface

Nomos is addressable by the systems around it.

An operating layer that can't be integrated is just another silo. Work, memory, and authority are reachable through the same contracts the interface uses.

INBOUND
Work API
Create projects, sessions, and tasks from existing tools.
TOOLS
MCP bridge
Tool servers exposed to agents under the same grants.
MODELS
Adapter contract
One interface for cloud APIs and local runtimes alike.
RECORDS
System connectors
ERP, CRM, and ticketing as read and gated-write targets.
IDENTITY
SSO & provisioning
Principals and roles synced from the org directory.
OUTBOUND
Audit export
Actions and approvals streamed to the customer's SIEM.

Built to be read before it's bought.

We'd rather be evaluated on the architecture than on a demo. The technical brief goes deeper than this page.

Request the technical brief See the sequence
Design constraints

Three rules the architecture is not allowed to break, at any stage.

01State above the model boundary is never provider-specific.
02No action executes without a grant that can be named.
03Every stage of the roadmap runs on the same object model.