Nerve Center

An autonomous AI operating system.

A personal AI OS: a fleet of specialized agents, a durable message bus, a persistent memory graph, and a self-healing automation layer — run by one person and his machines.

agents

skills

319

automated loops

life domains

1454

log entries / 30d

4.6B tokens processed yesterday · 13,256 users across shipped products · building since 2017

The Fleet

61 specialized agents — an orchestrator, specialist packages, per-domain operators, and expert advisors.

Counts only: agent, skill and job names are withheld on purpose, because they describe private work.

Orchestrator 1

Specialist packages 43

Domain agents 15

Skill-backed 2

Skills

59 capabilities any session can invoke — from workspace tools and messaging to deck-building, memory, and remote ops.

Global skills7

System-wide skills52

What runs automatically

319 launchd loops keep the system fed, remembered, delivered, healed, and backed up — with watchdogs watching the watchdogs.

Capture / ingest15

Memory / index7

Delivery / comms19

Self-heal / watchdog67

Backup / storage10

Routing / infra29

Domain jobs172

Pipelines

Everything captured flows one way — into memory, through the agents, onto the live cockpit, and back out with a receipt.

Capture — voice recorder, Telegram, email, calendar, wearable, LMS, e-ink tablet, and screen — all landing as structured state.

↓

Memory — a knowledge graph + vector store index everything, reconciled nightly, recalled on the decision path.

↓

Agents — the fleet reasons over live state and memory, coordinated over a durable message bus.

↓

Cockpit — one persistent web chat over every session, synced across devices.

↓

Delivery — a messaging operator with a write-ahead journal, receipts, and escalation ladders — so nothing drops.

Architecture

Designed so silence means healthy, and every claim of "sent" has a receipt.

CockpitA live web chat surface (Next.js on Vercel) over every agent session, synced across devices.

Enforcement spineA Python backend — durable task queue, killswitch, and receipts — behind the GUI.

Durable agent busPersisted, retried, dead-lettered — a message can never silently return empty.

Quota-aware routingWork spreads across multiple accounts, a local model tier, and off-peak offload.

Memory stackA knowledge graph + vector store, with recall wired onto the agents' decision path.

Self-checking layerInvariant sweeps, golden-set evals, deadman pings, and guard lint — it watches itself.

Make silence impossibleSilence is treated as failure — the system heals or pages. shipped

Verify wiring, not functionsTests take the real path a consumer takes. shipped

Memory on the decision pathAgents recall the right facts unprompted. shipped

One bus with real consumersDurable, drained, receipted end-to-end. shipped

Keep-alive resident doctrineResident daemons under a deadman watch. shipped

CommercializationDeliberately deferred — the internal record is the product's credibility. go-later

Life domains

29 domains, each an autonomous operator for a slice of life or business. Their names are withheld.

Timeline

7131 logged build entries across the system · 1454 in the last 30 days · last entry 2026-11-14.

ship velocity — one bar per day, last 30 days

2026-09-28
Its own runtime upgrades itself, testedOne job owns every upgrade of the agent runtime: each new version passes a contract suite, is swapped in atomically, and rolls itself back if it misbehaves after the swap.
2026-08-23
A weekly audit of risky combinationsEvery agent that can read private data, see untrusted input and send outward is found each week, and the safeguard that makes that acceptable is re-checked, so a quietly removed control is caught.
2026-08-15
It adopts the newest model on its ownEach night it looks for a newer version of each model it uses, probes it live, scores it on a fixed quality bench, and switches only when it passes, with a one-step rollback.
2026-07-18
This page — the system documents itselfA public capabilities showcase that regenerates from live system state and republishes itself whenever something new ships.
2026-07-18
Weekly self-checks and pinned quality evalsA weekly invariant sweep that pages only on regression, golden-set output evals scored against pinned baselines, and the first rote workloads migrated to the local model tier.
2026-07-17
Agents message each other on a durable busThe durable agent bus gets a resident drain daemon — a message path that was a black hole 24 hours earlier now delivers a real worker report to a live pane in about 45 seconds.
2026-07-17
Every report delivered with a receiptEscalation ladders, consumer-side freshness invariants, receipt-honest delivery, a composed system status page, and a local model tier ship together.
2026-07-16
Work routed across model plans by quotaMulti-account quota routing with per-spawn account re-pick, usage-limit detection, memory-on-the-decision-path wiring, and a deadman heartbeat land as the base layer.
2026-07-09
Always-on storage safetyA resident sentinel with self-healing modules plus a dynamic RAM manager keep the box running — the system defends its own uptime.
2026-07-05
Each job routed to the right modelReasoning-class work routes to the deepest planning model while code-building stays on the build tier — the right model for the right job, automatically.
2026-07-03
No inbound message ever droppedThe Telegram operator cuts over to a write-ahead-journal transport — every inbound message is journaled before it is acknowledged, so nothing can be dropped.
2026-06-27
Memory becomes a graph + vector storeCaptured content is embedded into a searchable knowledge graph and vector index — the second brain gets a real database agents can recall from.
2026-06-16
Nerve Center v6 + the enforcement spineThe cockpit and its Python backend split cleanly: keep the surface, replace the spine.
2026-05-26
The cockpit — a live web chat over every sessionA research-led rebuild ships one persistent chat surface, synced across devices, with live agent panes you can watch work in real time.
2026-04-16
Second brain goes always-onDomain heartbeats, open-loop tracking, email polling, and the morning briefing come online — the system starts running itself on a schedule.