Nieme
THE SYSTEM OF RECORD FOR AI WORK

Work can start with a person,
or with a change.

TWO ENTRY PATHS, ONE LOOP
Someone asks
Prepare the quarterly board report.
Something changes
A document changed in a connected Drive folder.
START A person delegates an outcome — or a connected system is observed to change
RUNTIME Runtime assembles the right context
VAULT Vault supplies governed sources, with provenance intact
EXECUTOR A model, an agent, an external system or a person does the work
RESULT A result is produced, with the Evidence supporting it
REVIEW A person accepts, requests changes, or rejects
RECORD The decision is preserved with the work it judged
STATE Accepted outcomes can strengthen future context

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 system of record for AI work.

TWO WAYS WORK STARTS

The work starts before the prompt.

Work does not have to begin in a chat. Nieme is already there when something changes.

YOU ASK
in plain language
OR NIEME NOTICES
“approved” · “cancelled” · “scope changed”
and proposes the work for you to approve
DIRECT WORK, MOST OF THE DAY
changes the code and opens the pull request · writes the document · builds the spreadsheet · makes the deck
WHEN ONE ASK IS MANY PIECES
execution queue retries handovers
You approve the candidateand it lands in the system where the work lives
Every piece comes back for a decisionand each goes on to the destination system
WHAT YOU ACTUALLY DO

Three moves. Then it compounds.

Nieme is not a model and not another assistant. It is the layer your company keeps: the knowledge, the authority and the record that every model you use is missing.

Prepare the work

Everything Nieme does draws on what you connect. This part happens once.

  1. Connect your knowledge

    Bring in the files and documentation your company already depends on. Upload files and folders, connect cloud storage such as Google Drive and OneDrive, and build a governed Vault of institutional Sources.

    Google Drive OneDrive Files & folders Vault

  2. Connect your work systems

    Bring in the activity happening around the company. Nieme turns relevant external activity into Signals rather than leaving it scattered across apps.

    • Slack
    • WhatsApp
    • Gmail
    • Google Chat
    • GitHub
    • Google Ads
    • GA4
    • Search Console
    • Google Business Profile

  3. Connect your workforce

    Connect the models, coding agents and agent runtimes your company already uses. Nieme sits above them. You do not have to standardize on one model, vendor or agent harness.

    • ChatGPT / OpenAI
    • Claude
    • Gemini
    • Codex
    • Claude Code
    • Cursor
    • OpenClaw
    • Hermes
    • AWS
    • Microsoft
    • Google
    • NVIDIA

    As integrations expand.

  4. Connect your policies

    Bring the AI governance, operating rules and approval policies you already have. Or let Nieme draft a proposed institutional constitution from your existing work and Sources, for human review and ratification.

    Human ratification Versioned Enforced before execution

Start working

Work enters the same loop whether a person asked for it or a system changed.

  1. Create Projects

    Organize work around real company goals. Projects connect Operations, Sources, Signals, Artifacts, Evidence, Decisions and results without inventing a new silo for the work.

  2. Monitor Signals

    Let connected systems tell Nieme when something relevant changes: a customer email, a Slack thread, a repository event, a traffic anomaly, a new document, a campaign change or another event worth attention.

  3. Direct Ship

    Work that does not need to go through the queue. Ask for one bounded thing and get it now — start from a Signal, or just tell Theon through the Composer. Change the H1 on a page and Nieme opens the pull request. Analyze something, prepare a response, produce an Artifact, or take an explicitly authorized action in a connected system. As connectors expand, so does where a Direct Ship can land.

    Skips the queue Delivers into connected systems One bounded ask

  4. Start an Operation

    When one ask means many pieces of work, hand it to the Runtime. Operations can coordinate multiple tasks and outputs, use governed context, queue work, delegate to agents, retry failures, continue in the background and preserve Evidence and Decisions as they run.

    Governed context Delegates to agents Retries Runs in background DOCX · XLSX · PDF · PPTX · diagrams

  5. Program recurring work

    Turn repeated responsibilities into governed scheduled or continuous work. Nieme can watch for changes, queue the next action and keep the work running under the same institutional context and controls.

    Scheduled Continuous Same controls

Build Institutional Intelligence

Everything above compounds into something that belongs to the company rather than to a vendor.

  1. Talk to Theon normally

    Use one conversational interface across your institutional knowledge, connected systems, models and agents. Ask questions the way you would ask ChatGPT or Claude, while Nieme assembles the relevant governed context from your Sources, Signals, Projects and previous work.

  2. Use the right intelligence for the job

    Ask different models or agents for their perspectives, compare their outputs, or route work to specialized executors — without moving the institutional context into a different silo.

  3. Brainstorm with your workforce

    Bring multiple agents into the same problem. Explore ideas, Projects, Operations, policies and decisions while preserving the discussion and its outcomes as institutional knowledge.

DELEGATE WITHOUT LOSING CONTROL

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.

RUNS ON ITS OWN Pre-authorized by policy Routine, reversible work a Policy already admits. Nobody gets woken up.
RUNS WHILE YOU WATCH Continuous consent Standing permission you granted and can revoke, one execution at a time.
STOPS FOR A PERSON Requires a decision Consequential work waits. The approval is recorded against that exact work.

You set where each line falls, in advance. Nothing moves itself up a band.

The durable core
EVERY OPERATION, ON THE RECORD

What the Runtime writes down,
as the work happens.

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.

OPERATIONAL TIMELINE
Created Operation initiated by a person
Prepared Context assembled, evidence gathered
Executed AI models reason and produce artifacts
Approved Person reviews and signs off
Governed work keeps its record.
Results traceable to their Evidence.
Decisions preserved with what they judged.
GOVERNED SOURCES, WITH PROVENANCE

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.

CONTEXT BEFORE INTELLIGENCE

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.

Context package

What this Operation was allowed to know — decided before anything ran, and kept.

Frozen · bddb9c53ce
INCLUDED6 passages · 3 sources
  • Q4 Campaign Brief.docxadmitted Source · v4
  • Brand Guidelinesadmitted Source · v11
  • Renewal terms, accepted 12 Sepaccepted Decision
EXCLUDED9 passages
  • #launch-q4 · 4 messagesobservation, not authority
  • Draft pricing sheetnot an admitted Source
  • 3 older passagesbelow the relevance bar
Budget 3,180 / 8,192 tokens The exclusions are part of the record too. What a model was not allowed to see is as durable as what it was.
EXECUTION IS NOT THE END

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.

FIRST RUN Renewal position brief ★★★★★ Board sent it back. The risk was not on page one.
SECOND RUN Renewal position brief ★★★★★ Approved in the meeting. Renewal signed 11 days later.
THIRD RUN Renewal position brief ★★★★★ Signed in the same call. Same shape every quarter since.

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.

Attached to the exact workThe outcome binds to one Artifact and one Execution, never to “the project” in general.
Append-onlyA later opinion is a new entry. Nothing overwrites what somebody thought at the time.
Evidence, never instructionIt reaches future work as evidence about quality — it never becomes an order, and it never grants authority.
HOW THE RUNTIME IS BUILT

Nieme separates the parts most AI products fuse together: what you work in is the Workspace, and what persists behind it is the Runtime.

The kernel

Runtime

Schedules operations, composes context, applies policy. It decides what each model should see.

Reasoning

Models

Interchangeable reasoning providers. Swap them without losing your context, your record, or anything that matters.

Governed sources

Vault

The governed sources and material the Runtime may draw from, with provenance intact. Not the whole of institutional state — one substrate within it.

Observation

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.

The interface

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.

Consequential work

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.

NATIVE SYSTEM OBJECTS

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.

HOW WORK CONNECTS

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.