The engine is what acts.
Separate machine, separate job. The brain holds the data; the engine is a set of agents that arrive already loaded — skills installed, MCP servers connected, workflows agreed in advance — and work that data on a schedule, then report back.
- preloaded skills
- MCP connections
- predetermined workflows
- scheduled runs
- approval gate
- reports back
-
Plate 01 · The feed
It reads from the brain, not the internet.
Every run starts with your own structured records as context. That's the whole reason the brain comes first.
-
Plate 02 · MCP servers
The systems it can touch, wired in advance.
Email, calendar, CRM, billing, databases, internal tools — each exposed as a defined set of callable operations. Nothing improvised, nothing undocumented.
-
Plate 03 · Skills
Your playbooks, installed as capabilities.
"Triage the shared inbox." "Reconcile these invoices." Written once, reviewed like code, then permanently available to the agent.
-
Plate 04 · The agents
One operator, helpers for the big jobs.
The operator plans and delegates; helper agents run the parallel work. They arrive configured — there is no setup phase on your side.
-
Plate 05 · The approval gate
It reads, analyzes and drafts on its own.
Sending, publishing, buying, deleting — every outbound action waits for your one-word approval. It never types your passwords.
-
Plate 06 · The report
It tells you what it did.
Each run ends with a written account — what ran, what it found, what's waiting on you — in the chat app you already use.
-
Engine running
Assembled, it runs unattended.
On your server, on a schedule, on your data. You approve what leaves.
NE-02 · §01Day to day
What it actually does.
Inbox & comms
Reads, triages, summarizes, drafts replies — where you already work.
Documents → structured data
Turns PDFs, spreadsheets, whole folders into clean records; compares figures — "is this quote better than what we pay?"
Scheduled, unattended work
Recurring reports, digests, reminders in plain language — "every weekday 9am, post an inbox summary to Slack."
Monitoring & alerts
Watches inboxes, portals, feeds, systems; surfaces only what changed and needs you.
Business-app upkeep
Connects to email, calendar, CRM, docs, billing, databases; looks things up, logs activity, keeps records current.
Playbooks on real tools
Researches with sources, operates a browser like a person (portals with no API), runs code to crunch data, drafts documents — end to end.
Memory that compounds
Permanent memory of your business + a log of everything it's done; proven methods become reusable skills, so it gets faster the longer it runs.
NE-02 · §02The gate
Human-in-the-loop by default.
It reads, analyzes, and drafts on its own. Sending, publishing, buying, or deleting waits for your one-word approval.
Every outbound action queues at the gate. You say "send" — it sends. You say nothing — it waits. And it never types your passwords.
Autonomy line
- RUNSread · analyze · draft · monitor · log
- WAITSsend · publish · buy · delete
- NEVERyour passwords
NE-02 · §03The headroom
We're early on purpose.
Built on an open, self-hosted runtime that runs on your server: dozens of built-in tools, one operator plus helper agents for big jobs, provider-agnostic, a memory engine that keeps itself tidy overnight.
Most owners switch on a handful of workflows at first. New skills and integrations are configuration, not a rebuild — the agent gains an ability the day you connect a system, and keeps it. No lock-in: the brain and the playbooks are yours.