narada

Install

One command installs narada — a self-contained bundle whose agent session runtime runs natively in Rust; nothing is resolved from a package registry on your machine. Delivery is via npm, so Node.js 22+ on PATH is the only prerequisite. The scripts are plain text served from this domain — read them before you run them. Source builds: install-source.ps1, install-source.sh.

# Windows (PowerShell)
PS> irm https://narada.systems/install.ps1 | iex
PS> narada demo # no credentials, no config, no files created
# macOS / Linux
$ curl -fsSL https://narada.systems/install.sh | bash
$ narada demo

Agent frameworks gave models hands. Nothing gave them a leash — or a way to catch their own mistakes.

Today, a model's judgment flows straight into effect: a prompt becomes a send, a delete, a purchase. When something goes wrong there is no durable record of what was decided, by whom, under which permission — and no way to replay what happened.

A smarter model does not close this gap. The gap has two independent sources, and either one is enough to make ungoverned agency unsafe.

Entropy. Natural language has null spaces — regions where several readings are valid and the model cannot tell it is standing in one. Chain enough interpretation→decision→action steps and a null-space hit stops being a risk and becomes a near-certainty.

Fallibility. Reasoning is conjectural. A model can be fluent, confident, and wrong even when the premises are clear — and it cannot detect its own bad inference from inside it. Every deduction, generalization, and plan is a guess that survives until something external checks it.

Together these are the Entropy and Fallibility Conjectures: even an arbitrarily smart model, reading and reasoning in language, will eventually drift into a null space or a bad inference; if the resulting actions are irreversible, the consequences are unbounded. That is why Narada separates intelligence (what the model thinks) from authority (what the system may do), and makes every step between the two durable, explicit, and inspectable.

Every boundary blocks a named collapse

Narada pipelines every operation through one fixed sequence. Each arrow is a governed crossing that prevents a specific failure mode.

sourcefactcontextworkpolicyintentexecutionconfirmationobservation
source → factWorld state becoming prompt memory
fact → contextUnbounded reality becoming arbitrary model context
context → workAttention becoming informal task selection
work → policyInference becoming permission
policy → intentApproval becoming direct effect
intent → executionExecution inventing its own reasons
execution → confirmationAPI success becoming assumed truth
confirmation → observationHidden state becoming uninspectable consequence

This is the core of Narada: not a policy document, but a running system in which a model's output cannot skip a step — there is no code path around the pipeline.

One control plane for everything an agent touches

A deterministic kernel plus a governed tool fabric, designed for operators who run agentic work for real.

Intelligence–Authority Separation

Models contribute judgment, but they never own truth, lifecycle, permission, effects, or confirmation. Their interpretations and inferences are candidates; Narada's control plane is the criticism apparatus that admits, checks, and authorizes what becomes real.

Deterministic state compiler

Remote source deltas become local canonical state you can inspect, diff, back up, and replay. SQLite-backed durable stores, not prompt memory. Identical input compiles to identical output.

Vertical-agnostic kernel

Mailboxes, timers, webhooks, filesystems, and processes all travel the same pipeline: source → fact → policy → intent → execution → observation. Exchange/Graph is simply the first vertical.

Governed tool fabric

Dozens of MCP tool surfaces — git, filesystem, tasks, inbox, scheduler, mail — give any connected agent the same admitted, policy-checked capabilities. Capabilities are declared and admitted, never inferred from a prompt.

Operator-grade continuity

Tasks, checkpoints, and an operator console keep multi-session work resumable, reviewable, and auditable. Crash at any point; the system converges back to correct state.

Native Rust runtime — same governance

The agent session runtime runs natively in Rust. Session authority, lifecycle, evidence, and tool semantics are contractual — the runtime is an implementation detail, never a governance lever.

You stay the operator. Narada does the remembering.

Narada is designed around ops repos — private repositories that hold your operations, their knowledge, and their local configuration. You shape what runs; the daemon executes it under governance.

1

Try it with zero setup

narada demo shows synthetic mailbox data and what Narada does with it. No credentials, no config, no files created.

2

Bootstrap an ops repo

narada init-repo ~/src/my-ops creates a private repository for your operations, their knowledge, and their local configuration.

3

Declare an operation

narada want-mailbox help@company.com sets up a governed mailbox operation with safe, draft-first defaults.

4

Set the safety posture

narada want-posture chooses how much authority the operation gets — from observe-only to autonomous.

5

Verify before anything runs

narada preflight checks credentials, connectivity, and policy. narada explain shows what the operation will do — and why it might be blocked.

6

Activate and run

narada activate, then pnpm daemon. Narada syncs, evaluates, drafts, and reconciles — logging durable evidence as it goes.

Prefer a personal assistant first?

The User Site path starts one resident assistant on your own machine with no project setup. After installing the CLI (above): narada install windows-user-site, then narada onboarding start --scope user-site --interactive.

Authority is a dial, not a leap of faith

Every operation runs under an explicit posture you choose — and can tighten or loosen at any time.

observe-onlyWatch and report. Nothing else.
draft-onlyPrepare replies and proposals; never send.
review-requiredAct only after explicit human approval.
autonomousExecute within the declared policy envelope — still with full evidence and reconciliation.

The default for a new mailbox operation is draft-only. You grant more authority only when the evidence has earned it.

Proof, not promises

The governance claims on this page are checkable in the repo — the kernel invariants behind them are enforced in code and covered by CI tests and lints, not written in a whitepaper and left as an exercise for the reader.

Replay safety

Applying the same event twice yields the same final state. Idempotency is enforced at durable boundaries, not hoped for.

Crash tolerance

The compiler can stop at any point and converge back to correct state. No loss after commit.

Two-stage confirmation

A side effect counts as done only when inbound reconciliation observes the result — not when the API accepts the request.

Draft-first delivery

Agents and workers never send directly. Every effect begins as a durable, reviewable intent.

Read-only observation

Dashboards and consoles project from durable stores. The UI layer holds no write path into canonical state — kept that way by design and by a standing read-model audit.

Running in the open

These public sites run as Narada sites — what they publish passes through governed admission and promotion, with evidence, before it reaches the web.

Three programs, no shared charter — yet all three mark evidence the same way: perimeters on marici, gaps as first-class data on cintamani, confidence classes on the space ledger. The convergence is structural, not instructed: each site publishes through the same governed tool surfaces, which make a claim without its evidence class a non-operation. We tested this rather than assert it: an unbriefed agent, handed nothing but the surfaces, discovered the epistemic gate on its own and produced perimeter-marked work — the gate refused anything else — while a control agent without the surfaces produced equally good research with no perimeter marks at all. Form-level emergence: observed. The honest caveat: the gates govern publication through surfaces, not writing itself — the wall has an escape hatch, and knowing that is part of the finding.Full record.

Intelligence supplies candidate meaning and candidate reasoning. Narada decides what counts, what may change, what may be done — and how consequence is confirmed, criticized, and corrected.

Narada is open source under the Apache-2.0 license. Intelligence supplies judgment. Narada supplies the criticism apparatus that keeps judgment from becoming ungoverned effect.