Explanation
Background on Everruns, why durable execution, why events are the primary store, how the agentic loop and capability layering fit together.
These pages discuss why Everruns is shaped the way it is. They don’t tell you how to do anything (see How-to guides) and they aren’t lookup tables (see Reference). They’re here to give you a mental model so the other docs make sense.
Read these when:
- You’re evaluating Everruns and want to understand the design.
- A reference page tells you what something is but you want to know why it exists.
- You’re about to make an architectural decision and want to know which guarantees you can rely on.
Topics
Section titled “Topics”- Concepts, a glossary of the entity model: harnesses, agents, sessions, capabilities, and how they compose into a runtime.
- The agentic loop, the reason–act cycle, execution phases, and why turns are bounded.
- Architecture, control plane, workers, and the API-first design.
- How Everruns differs, where Everruns sits next to hosted agent services, graph frameworks, TypeScript frameworks and general durable execution engines.
- Durable execution, why agents survive crashes, and the trade-offs of a PostgreSQL-backed engine.
- Events as the primary store, why an append-only event log is the source of truth, not a side-channel.
- Command path, how the REST API, CLI, MCP and agents all reach the same platform commands, and where they differ.