Work can start with a person,
or with a change.
Observe → Understand → Govern → Execute → Attest → Learn. Whether the work began with a request or an observation, it runs the same loop — which is what makes Nieme the control plane for AI work.
Human authority where it matters.
You decide in advance what Nieme may do on its own. Work can be explicitly pre-authorized by policy — or by continuous consent — where that is appropriate, so routine and reversible work is not gated on a person being awake. Consequential decisions can require human approval, and the approval is recorded against the exact work it authorized.
Authority is stated before the work runs, not reconstructed afterwards.
You set where each line falls, in advance. Nothing moves itself up a band.
Anyone can claim their AI remembers.
Nieme keeps the record.
Governed work is recorded: the context it drew on, what it produced, the Evidence supporting it, who decided, and when. The record is durable, it belongs to you, and it is not an audit feature bolted on afterward. It is how a decision can still be explained months later.
A result is what execution produced. Evidence is the record used to evaluate it. A Decision is what a person accepted. Keeping the three distinct is what makes the history worth having.
Vault preserves what the work is allowed to draw on.
Vault preserves the governed sources and material your Runtime can draw from, with provenance intact — so what informed a piece of work can be named, not guessed at.
Vault is not the whole of what your organization knows. Durable institutional state also exists through Nieme's canonical records and relationships: Signals, Operations, Evidence, Decisions and Policies each persist in their own right.
Nieme decides what the models should know.
Before any AI begins working, the Runtime works out what the request actually is, what knowledge is relevant, what policies apply, and what past work matters. Only then is the right context assembled and handed to a model. Your whole organization never gets shipped wholesale to a model. Models reason. The Runtime decides what they should see.
What this Operation was allowed to know — decided before anything ran, and kept.
- Q4 Campaign Brief.docxadmitted Source · v4
- Brand Guidelinesadmitted Source · v11
- Renewal terms, accepted 12 Sepaccepted Decision
- #launch-q4 · 4 messagesobservation, not authority
- Draft pricing sheetnot an admitted Source
- 3 older passagesbelow the relevance bar
Allowed is not the same as worked.
A flawless run — every checkpoint kept, every step on the record — is worth nothing if it did not meet the objective. Effort that produces no result is still effort that produced no result.
So the loop does not close at execution. It closes when a person attests what the work actually produced — the deal closed, the page converted, the client renewed. Governance proves the work was allowed to run. Only the outcome proves it was worth running, and that is not a matter of taste. Attesting it is the most authoritative thing anyone does here.
Three runs later the work is predictable, and the record says so in outcomes rather than opinions. Now you can move it up a band — because it earned the move, not because the system promoted itself.
Every operation leaves proof.
Organizations improve the way science does, through evidence rather than intuition. Most organizations are terrible at keeping theirs. Knowledge lives in people's heads and walks out the door when they leave. Decisions get made on folklore. Nieme records every operation, keeps the evidence, and applies it to the next one.
Execution produces a result. Evidence is the record used to evaluate it. A person decides what is accepted — and an accepted outcome can strengthen the state the next operation starts from.
Decision quality emerges from evidence. Evidence emerges from work that was actually governed.
Nieme separates the parts most AI products fuse together. The control plane is what you operate; internally it is an institutional runtime — what you work in is the Workspace, and what persists behind it is the Runtime.
Runtime
Schedules operations, composes context, applies policy. It decides what each model should see.
Models
Interchangeable reasoning providers. Swap them without losing your context, your record, or anything that matters.
Vault
The governed sources and material the Runtime may draw from, with provenance intact. Not the whole of institutional state — one substrate within it.
Signals
What a connected system was observed to do. A Signal is an observation, not an instruction — and observing something never authorizes acting on it.
Theon
Nieme's persistent generalist interface to the Runtime. It helps people delegate work, assemble context and review outcomes. Theon is how you reach the Runtime — not the Runtime itself, and not bound to any one model.
Operations
The durable identity of consequential work, keeping objective, authority, execution, Evidence and outcome connected wherever the work happens. Evidence, Review and Decision travel with it.
Built on .on.
Nieme's durable institutional representation. Signals, Operations, Executions, Artifacts, Evidence, Decisions, Policies, Roles and the relationships between them become .on state with stable identity and provenance. External APIs and agent payloads are translated into Nieme-owned state rather than stored as someone else's payload.
Swap the model, the agent or the executor — reached over MCP servers, a provider API or an external agent runtime; keep everything that makes the work yours.
Work connects. It does not get filed away.
Most tools file work into folders, where an artifact lives in one project and dies there. Nieme keeps the relationships instead: an Artifact stays connected to the Operation that produced it, the Sources it drew on, the Evidence behind it and the Decision that accepted it.
Nothing is copied, so nothing loses its history. When the same work comes round, what the company accepted is reachable — not because somebody filed it in the right folder, but because the relationship is part of the record.
This is what makes Nieme a runtime, not a wrapper.
See it run.
Nieme is opening to a small group of operators.