Promises, Kept: From Swarm Theory to an Agent System of Record | AnucleiProductPromises, Kept: From Swarm Theory to an Agent System of Record<br>2026-08-037 min read

Two and a half years ago, we published an essay arguing that two theoretical frameworks -- swarm theory and promise theory -- offered the right lens for building decentralized, resilient software. The argument was simple: systems built from autonomous agents making explicit, verifiable promises outlast systems built on central command and implied obligation.

It was a good essay. It was also just an essay. Theory is cheap, and the industry we work in has never been richer in confident assertions -- agents that "just work," copilots that "understand your codebase," autonomy that is always one demo away. We are skeptical of confident assertions, including our own. So we did the only honest thing we could think of: we built the system that checks.

That system is Multisynapse, our agent system of record. This post is the follow-up the original essay never promised -- what we have built since, what shipped most recently, and where Anuclei is going.

Promise Theory in Production

Promise theory's central move is an inversion: instead of commanding components and hoping they obey, components declare what they will do, and the system's job is to observe whether they keep their word. When we sat down to design Multisynapse, we took that inversion literally. A promise is only worth your ability to observe it, verify it, and revoke it -- so those three verbs became the architecture.

Capability claims are promises, and promises get verified before they are believed. Every agent in the Multisynapse registry carries a declared capability profile, and promotion to production is gated on evaluation -- a regression check against real graded outcomes, not a changelog entry and a nod. No agent approves its own promotion. A verdict computed against stale ground truth is rejected at approval time, because a promise verified against yesterday's world is not verified at all.

Promises are rehearsed before they are kept. Dry-run mode lets an agent reason all the way through a task while every intended action is recorded and nothing executes. You see exactly what it would have done -- the promise in full -- before you let it touch anything.

Broken promises are localized and observable, never silent. Every prompt, tool call, and token of spend lands in a structured trace. Policy is default-deny on every write, eval run, and tool invocation: nothing is implicitly obliged, everything is explicitly permitted. And the audit trail is hash-chained, so the record of who promised what, and what actually happened, is tamper-evident by construction.

None of this is exotic. It is the original essay's argument, load-bearing.

What's New in Multisynapse

The platform moved a great deal recently. Here is the tour, organized around a single theme: an agent platform should be at least as skeptical of itself as we are of the industry's claims.

Evaluation you can trust. Scores are assertions too, and we hold them to the same standard. Promotion gates now refuse verdicts computed against superseded ground truth. LLM judges can abstain on cases they cannot fairly score, rather than quietly dragging an average in either direction -- an honest "I don't know" is worth more than a confident guess. Head-to-head comparison now includes true pairwise judgment: the same item, two candidates, side by side, with win rates backed by proper paired statistics. And the significance behind every comparison -- p-values, confidence intervals -- is surfaced right where the promote-or-don't decision gets made, because a delta without a confidence interval is a vibe, not a result.

Human judgment as a first-class record. When a person overrides a score, that is an event of record, not a margin note. Reviews now carry full provenance -- who scored what, and when -- and can be deliberately undone, with the undo itself on the record. Review campaigns show per-item assignment, so "who is looking at this case" is a query, not a Slack thread.

Observability that answers questions. Traces are only useful if you can interrogate them. You can now search inside a single trace, filter the trace list by tool and agent with your recent filters remembered, and watch new traces arrive in a live tail. You can describe a filter in plain English and have the platform construct it -- constrained to the same vetted filter surface a human would use, never raw query access. The trace list itself got richer: span counts, error counts, duration, and the conversation and user behind each trace, all available as saved custom views with columns you choose. And reviewers can tag spans directly in the trace view, turning observation into curation.

Meeting teams where they work. Multisynapse now speaks Slack: link your account, get notified by direct message, and share trace links that unfurl into previews. The detail we care most...