Architecture · 11.05
The Six Primitives, As a Framework
Agent, Subject, Connection, Orchestration, Experiment, Interface — the backing systems behind each, and why there's no seventh.
One spine, six projections
| Primitive | Backing systems |
|---|---|
| Agent | The agents table, sessions, and residency — identity with memory and runtime routing. |
| Subject | A Durable Entity of kind subject — a per-person or per-device actor. |
| Connection | Channels, peer identities, integrations, MCP, A2A — every way an agent reaches something outside itself. |
| Orchestration | Workflows, runs, snapshots, and plans — the graphs and their execution. |
| Experiment | Experiments and their assignments — measurement, feeding trust and learning. |
| Interface | Apps, collections, records, and surfaces — what a human or another program actually sees. |
The discipline is refusing a seventh
The design rule that keeps this small isn't that six happened to be enough once — it's an ongoing constraint applied to every new capability going forward: when Agentis needs to do something new, the first question is which of the six primitives it's actually a composition of, never whether it needs its own new top-level concept. A new feature that needs durable state gets modeled as a Durable Entity or one of the six; it never gets a parallel subsystem with its own separate rules, storage shape, and mental model to learn.
Continue
How recoverInterruptedRuns rehydrates mid-flight work at boot, and why snapshots are content-hashed for safe, cheap resume.
The monorepo layout across apps and packages, and the dependency-free boundary checker that fails CI on illegal cross-layer imports.