The OS defines the organization. The runtime makes it work.
Long workflows, queues, retries, approvals, evidence and recovery: the part of an OS that keeps the work moving when nobody is typing.
01 Runtime
Not a configuration your host reads.
A tool catalog hands your host a list. The host reads it and improvises.
An organization needs more: work that outlasts a chat, steps that wait for a person, failures that recover without doing the same thing twice, and a record of what happened.
That is a runtime. It is why an OS is more than a catalog.
02 Control plane
Control plane. Execution layer.
Agentik holds the control plane: the organization, its rules, its approvals, its state and its record.
The execution layer does the work through your host's model. Isolated runners will take selected work onto machines you choose.
The control plane decides what may run. The execution layer runs it. Neither pretends to be the other.
03 Capabilities
Twelve runtime capabilities.
- Approvals
- Formal work waits for your decision. External writes need a human.
- Long-running workflows
- Runs will be saved step by step, so they can pause, resume and cancel across days.
- Queues
- Jobs wait until a worker can take them.
- Retries
- Bounded. When a result is uncertain, the runtime checks before it retries.
- Evidence
- Each step leaves a receipt that says what was reported, and no more.
- Recovery
- Stalled steps will be picked up again. Cancelling will stop the run without undoing actions taken outside.
- Agent-to-agent work
- A Director will delegate to specialists in parallel and merge the result.
- CLI execution
- Work will run through your own command-line agents, on your machine.
- Automations
- Declared in every package, and off until you consent.
- Schedules
- Schedules will run on your timezone, with your consent.
- Evals
- Three checks travel with every package: structure, quality, safety.
- Browser and computer use
- Browser work will reach the apps without an API.
04 Effects
Check the effect. Do not run it again.
A step sends an email and the answer never comes back. Did it go out?
A careless system sends it twice. The runtime marks the effect unknown and checks it first. Then it resumes, or it stops and asks you.
- 01
Step sent
The step calls the outside world, here an email.
- 02
No answer
The reply is lost. The effect is marked unknown, not failed.
- 03
Check
The runtime looks for the effect before it does anything else.
- 04
Resume or ask
It resumes when the effect is confirmed, or stops and asks you.
05 Step limits
A step knows its limits.
Every step names its role, its inputs, its dependencies, its rights, its budget, its timeout, its retry rule, its check and its escalation.
A workflow is a versioned graph. An automation is that graph in time.
Stability is shown by tests, by evals and by production data, never by where the platform runs.