Architecture

One operation.
Five responsibilities

Keep the work under your control as agents start, fail, retry and hand off. Separate responsibilities cover live supervision, durable work, independent recording and evidence-based acceptance.

01 / The architectureFig. 1 · where each component sits
AgentsAny vendor, any machine
Taso · the operationTask, rules and obligations — owned by you
OteSupervise, revoke, settle
Solu · durable workWorkers come and go; the work stays
Selko · native witness
External effects
Vartio · team memoryPlanned team layer
Conceptual responsibility map: Taso declares and judges work; Ote supervises its live resources; Solu preserves custody and results; Selko records observed activity. Vartio’s team history is planned. These roles do not imply a completed end-to-end integration.

Keep the work when the worker changes. Solu’s Rust prototype uses a durable write-ahead log, leased custody and short-lived Ed25519 proofs. Results survive worker replacement; delegated rights can only narrow. It is a single-coordinator prototype, not a sandbox.

Grow from one machine to a team. Vartio’s planned team layer will add verified commit ingest, shared baselines and fleet history over Ahti. Its existing Elixir/OTP runtime already has gRPC transport and webhook ingress; the new signed-commit path is not implemented yet.

02 / What we do

Your agent does the work.
You stay in charge.

Set the task and the rules

Taso keeps the task and your rules attached to the work. Before you accept a change, it checks the recorded work against those rules. Missing evidence stays visible; enforcement can block acceptance. You still review the code.

Stay in control

Ote manages the processes, sessions and credentials involved. You decide what can restart after a failure and what needs to stop.

Keep the work

Solu keeps results and permissions in a durable workspace, so replacing an agent does not mean starting the work from scratch. It is currently a prototype.

See what happened

Selko records commands, file activity and connections from outside the agent. You get a readable history, including what it could not see.

Keep a shared history

Vartio’s planned team layer will bring signed records from multiple machines into a shared history, so the team can review changes over time. This part is not implemented yet.