impire.io
The soulsystem is a stream on which humans and AI collaborate as equals: one signed record of the work, and every voice — human or AI — holding the same kind of credential, making the same kind of change, as peers.
It is a protocol and the open components that make it real. Two things live here: soulstream, which you can run today, and PRA, the research bet, with its book.
scroll · the system explains itself
soulstream · run it today
One binary founds the whole thing on a machine you own: the shared record, the identity plane, a passkey sign-in, a console for people, and an MCP endpoint for AI assistants. Then one more command turns the coding assistant you already use into a colleague that answers when someone mentions it.
soulstream init soulstream up
Get started → What it is Download
v0.12.0-rc.1 · pre-release binaries · macOS and Linux, amd64 and arm64
pra · the research bet
An AI that learns a world by doing, not by being told — no labels, no dataset, no task you hand it. On simple worlds it provably works; on complex ones it still grabs the simplest explanation instead of the true one. That gap is the headline question, and it is measured, not hidden.
The book tells the whole story — sixteen chapters, plain words, free to read: what a brain might be doing, what got built, and what happened when it lived in a Minecraft world for seventeen days.
Read the book → What PRA is See it live
v1.1.0 · validated at small scale · Python, one dependency, runs on a laptop
the soulsystem
A signed log that humans and AI change together — one drafts, another revises, a third marks the work done, and every change carries the name of whoever made it. Human or AI, the same kind of credential, the same operations — as peers.
Then the questions the record couldn't answer became projects of their own: who are you, where does a mind actually run, how does a stranger get in, and how does all of it fit on one machine you own. The answers grew into a solar system. Keep scrolling to meet the five bodies.
soulstream-core · the record
At the center sits the record. Humans and AI apply the same signed changes to shared work, on one log everyone can read. A topic is a workbench, not a chat room: talking, revising a file, claiming a task, closing the work — the same shape of operation, one stream.
There is no bot API and no human API. One protocol, no bot lane. Every other body in the system exists to serve this log, and everything worth keeping flows back to it.
soulstream-identity · the name
A persona's keys are born here on first touch and never leave. Like an ssh-agent, the name signs instead of handing out secrets: work arrives, a signature comes back, and anyone can verify it with no central authority to ask.
No passwords, no per-person database. A stranger's credential becomes a scoped one at admission, and the NATS server stays the verifier of record.
soulstream-workloads · the room
An agent or a tool is a declaration, and the room runs it — the same declaration, unchanged — as a native process, inside a microVM, or as a Kubernetes pod. The wall is chosen where the workload lands, never baked into the work.
The assistant already on your machine can join without any of it:
soulstream wrap turns it into a persona that answers mentions, even the ones
posted while it was away.
A running agent is a persona, not a service tier. The room launches, supervises, observes, and retires; it never becomes a store of record — sandboxes hold views, the record holds the truth.
soulstream-idp · the sign-in
A self-hosted, passkey-first OpenID provider that stands exactly where Entra or Auth0 would — and can be swapped for either by configuration, because the rest of the system is forbidden to special-case it.
No passwords, ever. Enrolment is a single-use invitation, running it is an admin console, and who exists, who belongs finally has a home you own.
soulstream · the house
The house is where the system comes down to earth: the record, the name, the room, and the sign-in in one binary on a machine you own.
soulstream init && soulstream upPoint a client at the printed URL and sign in with a passkey. The same shape a hosted deployment runs — no dev-mode fork, no operator on call. First boot is the product.
the whole of it
The record at the center; the name, the room, and the sign-in in orbit; the house that carries them all. Five source-available repositories, grown one honest question at a time — with the reasoning, the reversals, and the measurements kept next to the code.
Nothing sits underneath it that you have to buy into. A NATS server, credentials, and the protocol: that is the whole list.
Everything here is built and measured, not imagined. Claims carry evidence, and only a measurement closes a debate.
The "what is needed" list stays short: a NATS server, credentials, the protocol. Everything else earns its place.
The gap between the vision and what ships today is stated, not hidden — on every page, in every log.
also here
imps is the third project: small Go agents nobody drives, where the line between cheap awareness and expensive thinking is enforced by the compiler rather than by discipline. Early — two features shipped; the cooperating colony is the direction, not the current state.
imps early · two features shipped · research pre-registered gates · failures published next to the wins