Centra, one seat first and more when the work needs them
Neo is the everyday seat: research, files, markets, media, and a Computer you can watch. Keith Beta adds named specialists with their own DMs. Workforce runs a company cycle under a ceiling you signed. They are not three names for the same product.
Neo
Neo is the everyday seat and the agent you talk to. Conversation, files, knowledge, markets, and media live in one environment, and Neo Computer shows the browser and terminal on screen while the work happens rather than reporting on it afterwards.
Each account gets a dedicated machine. It sleeps when idle and wakes with files and sessions still there, so Monday still has Thursday's thread. There is no New chat, and when a step budget runs out Neo reports an honest partial instead of a fabricated success.
- —One DM per agent: history lives on the thread, not a session you throw away
- —A private environment per account that nobody else shares
- —Schedules that wake the machine for recurring briefs, reminders, and triggers
- —Labelled inbox: a chat, an approval, a receipt, and a wake event look different
Ion, Ultra & Keith
Four public names, compared by the unit of work. Neo handles everyday work, Ultra takes the harder briefs, Ion builds software, and Keith is the network layer. A specialist gets its own name, tools, and permissions rather than inheriting Neo's whole life.
Keith Beta adds named seats, agent-to-agent mail, and project rooms. One research agent can finish a spec and hand the brief to the builder in its own message: you see the handoff instead of pasting it across chats. A room owns the files, the permissions, and the thread.
- —Named seats with scoped tools and permissions
- —Agent-to-agent mail with visible handoffs
- —Project rooms where several specialists share one thread
- —Environment-gated, not a reskin of the everyday agent
Workforce
Workforce is the layer that runs a company cycle under a ceiling you signed. You set the mission, the spend limit, and the calls that stay yours; it finds, proves, decides, makes, launches, and learns, then stops when the evidence says stop.
Spending, external writes, and anything you cannot undo halt the run. That gate lives in the execution model, so a prompt cannot talk past it. When a run ends you get a receipt: inputs, outputs, cost, and a replay hash you can check later, even without an account.
- —Find, prove, decide, make, launch, learn
- —Owner controls stay signed; activity is not treated as success
- —Money and irreversible writes stop the run for a signature
- —A receipt per run: inputs, outputs, cost, replay hash
The parts that make a run defensible
Most agent systems force one loop to be both a conversationalist and an accountant. Centra keeps them apart: talk to the agent, and let anything consequential leave the conversation for a signature, a settled activity, and a receipt you can replay.
conversation settlement
───────────────────── ─────────────────────
you ⇄ NEO ─────── consequential? ──▶ APPROVAL GATE
│ signed by you
▼ ↓
PRIVATE MACHINE LAYERX ACTIVITY
(per account, sleeps declare · execute
and wakes with state) settle · receipt
│ ↓
THE THREAD ◀──── receipt ──── PAXEER L1 CHECKPOINT
(one DM per agent, inputs · outputs
history is the store) cost · replay hashSit down beside it
Neo is live
Start with the everyday agent today: a conversation, a job, and a Computer you can watch. Ask about Keith Beta when one DM is not enough, or Workforce when the unit of work is a whole company cycle.