nomosV0.1 · ALPHA
001New category

The operating system for AI work.

Not a chat client. Not a model wrapper. A control plane where work, memory, permission, and execution are held — while the intelligence underneath stays replaceable.

Models
Interchangeable
Context
Persistent
Authority
Explicit
NOMOS · CONTROL PLANELIVE
LAYERSTATE
Interface
people · teams · orgs
ATTACHED
Governance
policy · approval · audit
2 GATES
Memory
semantic · durable
84% RETAINED
Orchestration
routing · agents · jobs
18 ACTIVE
Model substrate
cloud · local · MCP
SWAPPABLE
Work continues across model changes: context, permission, and history belong to Nomos, not to a vendor session.
Substrate
azureopenaianthropicgeminilocal runtimesmcphermes agent
002Failure mode

Fragmentation isn't a UX problem. It's an architecture problem.

Nine tools, nine histories, nine permission models. Context is rebuilt by hand every morning, and no system can say who approved what. Adding another model makes it worse.

SYMPTOM 01
Isolated by default
Each surface is a silo. Work restarts instead of continuing.
→ no shared operating layer
SYMPTOM 02
Context expires
History, constraints, and decisions have to be re-stated to be useful.
→ intelligence without memory
SYMPTOM 03
No accountability
AI can act, but few products can prove what it was permitted to do.
→ capability without authority
003System diagram

One layer between people and every AI system they use.

Actors
Individuals
Teams
Organizations
AI agents
nomosOPERATING LAYER
01
Organize
02
Connect
03
Remember
04
Govern
05
Execute
state: persistentauthority: explicitmodels: swappable
Substrate
Cloud modelsAPI
Local runtimeson-prem
Tools & MCPbridge
Systems of recordERP/CRM
004Pillar specification

Five pillars. Each one useless without the next.

Organization without memory forgets. Memory without governance can't be trusted. Governance without execution is paperwork. Nomos ships them as one operating model.

01OrganizeWork gets a shape: projects and sessions instead of an endless list of chats.projects · folderssessions · knowledge
02ConnectEvery model and system reachable from one workspace, routed per task.openai · anthropic · geminilocal · mcp · hermes · erp
03RememberDecisions, sources, and constraints persist past the session and the vendor.persistent context · semantic memoryunified history
04GovernAuthority is data: what AI may do, who approved it, and what happened.permissions · approvalspolicies · audit trail
05ExecuteWork completes: agents and jobs act, with a human in the loop by default.agents · automationtasks · human oversight
005Design principles

Five positions we won't trade away.

Models change. Your knowledge shouldn't.
Memory belongs to the organization, not to whoever is winning the benchmark this quarter.
Context should persist, not disappear.
Nothing that mattered yesterday should have to be re-typed to matter today.
AI should work for you, not the reverse.
The operator sets intent. The system handles routing, retrieval, and continuity.
Work should be organized, not scattered.
One place where every AI conversation, document, and decision can be found.
Governance should enable innovation.
Clear permission is what makes autonomy deployable instead of theoretical.
These five hold in every stage of the roadmap — from one operator to an organization running an AI workforce.
006Enterprise · Forward scope

Where a personal operating system becomes an organizational one.

The same primitives extend outward: business knowledge instead of personal notes, departments instead of projects, policy instead of preference. Described as intent, not as shipped capability.

status: architecture defined · stages 03–05 · not yet released
01
Business knowledge
SOPs, contracts, reports
02
Systems of record
ERP, CRM, ticketing
03
Policy engine
constraints, approvals
04
Departments
roles, teams, scopes
05
Audit & assurance
who, what, when, why
06
AI workforce
agents under authority
007Sequence
STAGE 01 · NOW
Personal MVP
A complete individual operating system.
STAGE 02
Knowledge layer
Memory across projects and sources.
STAGE 03
Business MVP
Roles, teams, shared context.
STAGE 04
Enterprise
Policy, audit, systems of record.
STAGE 05
Autonomous work
An AI workforce under authority.
008Myraki Labs

We're building the infrastructure layer for intelligent work.

Myraki Labs is an early-stage, founder-led company. Nomos is our first and only product: a foundational operating layer, not another chatbot, model, or point solution.

Open roles are listed explicitly rather than presented as a fictional team.

ROLESTATE
John Phelan
founder · product architecture
ACTIVE
Founding engineer
platform · runtime · integrations
OPEN
Product & experience
interface for governed AI work
OPEN

Everything AI-related runs through Nomos.

That's the position we're building toward — the same way organizations say everything runs through their ERP today.

Investment thesis

Models are becoming commodities. The durable value moves to the platform that organizes, governs, and executes work across them.

01
phase in active development
05
operating pillars, one model
05
stages to autonomous work