Skip to main content

What is Nooterra?

Nooterra is an AR-first world-runtime for business operations. It turns events from connected systems into a live object graph of customers, invoices, payments, disputes, and governed actions. Today, Stripe is the first live source and receivables is the first active domain. The current product story is: connect live data, materialize company state, rank governed next actions, execute only through the policy gateway, observe outcomes, and expand autonomy only from evidence.

Getting started

Connect Stripe, review board state, and launch the runtime in shadow mode.

Causal assumptions

The current boundary for what the causal layer can honestly claim today.

What the runtime does

The runtime is built to answer five questions in order:
  1. What is true right now?
  2. What is likely to happen next?
  3. What would happen if we act?
  4. What is allowed under policy?
  5. What should happen now, and when should the system abstain?
The key control path is: Event ledger -> object graph -> state estimator -> world model ensemble -> planner -> policy gateway -> execution -> outcome tracking

How it works

1

Connect a live source

Start with Stripe. Nooterra records receivable events into the ledger and begins materializing tenant-scoped company state.
2

Review board state

Customers, invoices, payments, disputes, and collection history appear in the object graph with observed and estimated state separated.
3

Run in shadow mode

The planner ranks actions without sending anything. You can inspect recommendations, support level, and approval posture before enabling execution.
4

Govern execution

Approved actions route through the policy gateway. Unsupported or risky actions are denied or escalated instead of silently proceeding.
5

Measure and learn

Outcomes are tracked against expectations so the runtime can grade recommendations and widen authority only when the evidence supports it.

Read this next

Master build map

The canonical internal definition of the product and control system.

Live vs legacy boundary

What is on the current product path versus older product generations still in the repo.

Legacy docs

Historical worker-team, action-wallet, and collaboration docs preserved for reference.