NIEME
ARTIFICIAL INTELLIGENCE, MADE INSTITUTIONAL

Automate more work.
Keep your company
in control.

AI can already read your systems. What it cannot do is act with authority, or leave a record of who decided what. Nieme is the layer that is missing.

See how it works →
87 governed operations
56 executions
130 artifacts

Nieme is built by Nieme — including the operations that built this page. September 2026.

Rather talk to a person? Email the founder.

← Back Quick actions, search… ⌘K NiemeQueueSignalsRuntime
Chat · Current conversation
Nieme◈ 2 vault docs

Use the composer below to talk to Theon.

Commands

Context No turn trace yet Theon remembers your projects and decisions
Type / to choose a command

Everything here runs in your browser. Nothing typed is sent anywhere.

WHAT IT LOOKS LIKE IN THE PRODUCT

Observed. Governed. Executed.

01ObservedA change becomes institutional context.
Signals

What Nieme has observed in the systems you connected. Observations, not instructions — nothing here has been authorized.

SignalsMost recent 11 · newest first by when Nieme received them.
A document changed4h ago

A document changed in a connected Drive folder.

Google Drive · Brand Guidelines · happened Sep 12, 09:41

No ProjectWatching only
A message arrived6h ago

A message was observed in a selected Slack channel.

Slack · #launch-q4 · happened Sep 12, 07:58

Project: Coffee Subscription LaunchRaised as a Signal
A message changed9h ago

A message changed in a selected Slack channel.

Slack · #launch-q4 · happened Sep 12, 05:12

Project: Coffee Subscription LaunchWatching only
A document changed19h ago

A document changed in a scoped OneDrive folder.

OneDrive · Matter 4471 · happened Sep 12, 04:41

No ProjectWatching only

A message arrived

A message was observed in a selected Slack channel.

Slack · #launch-q4 · happened Sep 12, 07:58 AM · Nieme saw it Sep 12, 07:58 AM

Raised as a Signal

Observed event

Source
Slack
Where
#launch-q4
What happened
A message arrived
When it happened
9/12/2026, 7:58:06 AM · the provider's own time
When Nieme saw it
9/12/2026, 7:58:11 AM

Nieme recorded that this event happened. It did not keep or read the content of anything the event names.

Why it matters

Nieme's reason

the channel is a selected Source for this Project

Status

Raised as a Signal in the Runtime.

Related

Project · Coffee Subscription Launch

Settled — nobody has to decide this.

02GovernedContext becomes governed work with explicit authority.
DRAFT.ON · OPERATION.ON
Rebuild the Q4 subscription page before the campaign
Workforce · RolesBudget · —Deadline · —Assurance · —Outputs · —
Save Draft
OPERATION DRAFTSaved draft · fe7aefb7
Ready to approveReady for Review.
OUTCOME
Rebuild the Q4 subscription page before the campaign

This title is independent of the Objective.

Refresh the Q4 subscription page: who we are targeting, the keywords to win, the page copy itself, and a brief the team can run on.
One or more files — documents, specs, or code files

Produces each declared file as a governed Artifact of this one Operation, reviewed together.

SOURCE PACKAGE

Project: Coffee Subscription Launch

From Signal · a message in #launch-q4

Selected Operation Sources (5) — explicitly chosen

GOOGLE DRIVE
Q4 Campaign Brief.docxPreview

Drive · Coffee Subscription Launch · changed Sep 12, 09:41 AM · admitted Source

GOOGLE DRIVE
Brand GuidelinesPreview

Drive folder · 12 documents in scope · admitted Source

SLACK
#launch-q4Preview

Selected channel · observed since Aug 28 · admitted Source

SLACK
#mkt-researchPreview

Selected channel · observed since Jul 02 · admitted Source

GITHUB
northwind-coffee/webPreview

GitHub · branch main · /src/pages/subscribe · admitted Source

Editable — freezes when you Approve & Queue.

03ExecutedWork runs. The deliverables arrive with their evidence, and a person decides.
Rebuild the Q4 subscription page

Coffee Subscription Launch · operation.on

REVIEW Immutable approved Operation
Outcome
Five ready-to-use files: audience research, a keyword map, the page copy, a launch brief — and the subscription page itself.
Role
Nieme Generalist v1Governed Role · generic.work
Success criteria
Each declared file is complete on its own, the five are consistent with each other, and the page stands alone.
DELIVERABLES5 produced
  • MDaudience-research.md11 KBproduced
  • XLSXkeyword-map.xlsx28 KBproduced
  • DOCXlanding-page-copy.docx34 KBproduced
  • PDFlaunch-brief.pdf96 KBproduced
  • HTMLq4-subscription.html52 KBproduced
Preview liveServed on this machine only. It disappears when the Runtime restarts, and reopens at no cost. 127.0.0.1:61495 Open again End
Evidence 19ec5315 · one decision pending AcceptRequest changesReject
One thread. From change to governed outcome.
THE PROBLEM UNDERNEATH

The task got automated.
The coordination didn't.

AI can produce the answer. People still carry everything around it.

TODAY
#dealsAcme Payments renewal
You

is Acme actually renewing? board call is Thursday

Tue 09:12
Sales

pretty sure yes — terms changed last month though

Tue 09:26
You

changed how?

Tue 09:31
Sales

Legal has the redline. it's in Drive somewhere

Tue 11:04
Finance

which version are we pricing off?

Tue 16:40
WEDNESDAY
Sales

chasing Legal

Wed 08:15
You

still need this. board call is tomorrow

Wed 10:52
Finance

and who signs off on the final number?

Wed 14:20

Two days. Eight messages. The question is still open — and the board call is tomorrow.

WITH NIEME
OPERATION.ON Ready for your decision
Is Acme renewing, and on what terms?
Context
Acme MSA · Renewal redline v43 Drive documents, at the versions it read
Result
Renewal position briefevery number traceable to the clause it came from
Authority
Finance signs offdecided once — the work arrived here on its own
Accept Return with a change

The same question, asked once. Everything it needed arrived with it.

Two days of chasing One decision

Nobody assembled it. Nobody hunted for the right version. The only thing that needed a person was the part that actually needed a person.

Nieme carries the coordination. Your people keep the judgment.

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
WITH PROCESS, WHEN THE WORK DEMANDS IT
execution queue approvals handovers
It arrives finishedand lands in the system where the work lives
It arrives reviewedand goes on to the destination system
KEEP THE WORK WHERE IT ALREADY WORKS

Don't move the work. Connect it.

Your teams stay where they already are, and agents stay in their own runtimes. Nieme preserves the context, authority, evidence and outcomes across all of it.

A diagram: what the company already uses — Slack, Gmail, Google Chat, WhatsApp, Google Drive, OneDrive, GitHub, Analytics, Search Console, Business Profile, ChatGPT and Claude — streams in from the left into the Nieme Runtime, which returns governed work, Operations, Automations, Policies, artifacts, evidence, decisions, outcomes, continuity and institutional memory on the right.

Everything goes in where it already lives. What comes back out is governed, evidenced and decided.

Nieme-native capabilities are there when you want them. External tools are first-class participants, not migration targets. Connect what you use, as each connector becomes available.

WHEN THE WORK MATTERS

Work you can hand to someone else.

Consequential work gets a durable identity, so your team manages an outcome instead of a chain of prompts — and nobody has to rebuild the story later.

A month later, the work still explains itself. To a colleague, to an auditor, or to you.
What it was for, what ran, what it produced and who decided stay attached to the work itself. Nothing has to be reconstructed from a chat afterwards.
ONE PIECE OF GOVERNED WORK
ProposedAn objective, with boundaries
AuthorizedA person or a policy permits it
ExecutedBy whichever executor fits
DecidedAccepted, returned, or rejected
EXECUTOR NEUTRALITY

One control plane. Any executor.

Nieme can launch work through its own capabilities, AI models, specialized agents, people, or external execution systems. The executor can change without changing the institutional identity of the work.

NIEME'S OWN · NONE OF THIS SWAPS
  • Runtime identity and governance
  • Live ingestion and context resolution
  • Rules, policies and accepted decisions
  • Vault and governed sources
  • Queue, scheduling and handovers
  • Evidence, review and attested outcome
EXECUTION LAYER · EVERYTHING HERE PLUGS IN AND OUT
Frontier models as the interactive provider
Frontier models as the governed executor
Specialised agents and deterministic tools
External execution systems
People, executors like any other

The work keeps its objective, its authority and its record whichever one does it.

NOTHING SHIPS ON NIEME'S SAY-SO

Execution is not the end of the work.

AI finishing is not the same as the company accepting. Nieme keeps what was produced, the record behind it, and the person's decision as three separate things — so "we approved this" is something you can still stand behind months later.

RESULT

What the execution produced.

Not yet the company's answer.

EVIDENCE

The record that explains that result.

Not a judgment on it.

DECISION

A person accepts, returns or rejects it.

This is where the work becomes the company's.

ORGANIZATIONS COMPOUND

The first run costs what it always cost.
The tenth costs almost nothing.

Most AI work still reconstructs context the company already settled. Nieme carries it forward. What a person accepted is durable state — so it is already there the next time the work comes round, until reality changes it.

The same work, with less left to settle each time
Accepted context, authority and method carry forward — so repeated work starts with fewer open questions
ILLUSTRATIVE
AI without durable state Nieme
EverythingHalfAlmost nothingWhat still needs human settlementWhat the company settled no longer needs to be re-asked.1231st2nd3rd4th5th6th7th8th9th10thWhat still needs human settlementEverythingAlmost nothing1231st5th10th
  1. 1
    The source is settledcarried forward with its provenance
  2. 2
    The authority is settledwork reaches the right decision-maker
  3. 3
    The method is settledaccepted outcomes shape the next run

Not a benchmark — the shape of the difference. The line falls because an accepted decision becomes durable state, not a note somebody has to find. And it never reaches zero: the judgment stays with a person, on purpose.

Organizations don't become smarter because they have better AI. They become smarter because what they decided is still there the next time it matters.

What compounds over time needs a persistent layer.

UNDER IT ALL

The Workspace is the surface.
The Runtime is the layer behind it.

Your team works in the Workspace. The Runtime persists underneath — and reaches the systems the work already lives in. See the architecture →

Runtime

The layer the Workspace sits on. It is running whether or not anyone has it open.

LIVE RUNTIME
Idle
0 of 2 execution slots active · 3 queued
SYSTEM HEALTHHealthy
Runtime healthy · Guardian healthy · database ok
NEEDS A PERSON
3QUEUED
2REVIEW
1BLOCKED

Nothing moves past these on Nieme's say-so.

CONNECTORS
  • Slack
  • Google Drive
  • OneDrive
RUNTIME ACTIVITY
  • Execution succeededCoffee Subscription Launch · 14:22
  • Signal raisedCoffee Subscription Launch · 07:58
  • Decision recordedAcme Payments · 09:31

Governed work · Evidence that travels with the outcome · Context that survives the model

Delegate work.
Keep Control.

Nieme helps teams direct consequential AI work across the systems they already use, trace results to their evidence, and carry accepted outcomes forward. We are opening to a small group of operators.