Run
The run is the execution envelope. It records which capability was invoked, which agent version executed, which spec and recipe versions were pinned, which deployment supplied the bindings, what input was received, what mode was used, when execution started, what work occurred, what decisions were made, what outputs were produced, what failed, what required attention, and how execution ended. A run should be understandable in business language. It should not require you to interpret a wall of model messages or tool-call logs.Epic
An epic is the work graph materialized for a particular run. The recipe is reusable. The epic is run-specific. The epic represents the complete body of work for the run: the stories to be completed, their dependencies, their current states, their outputs, and their relationship to the overall outcome. An epic can evolve during a run as bounded decisions, escalations, and additional work become necessary. It stays traceable to the recipe it was instantiated from.Story
A story is an individual work item within an epic — one meaningful unit of executable work. A story may carry a title, purpose, description, required skill or executor, dependencies, inputs, expected output, acceptance criteria, error policy, retry policy, timeout, status, output, evidence, and failure details.Ticket
A ticket is the durable, business-readable collaboration and accountability object around work. A story belongs to the execution graph. A ticket belongs to the human and AI team operating the capability.
A ticket may represent work requested, work in progress, work completed, an approval required, an exception, an escalation, a failed story, a human follow-up, an unresolved dependency, or an improvement request.
Examples: Create Jane’s Google Workspace account. Manager approval required for Salesforce access. Could not complete the security review because evidence was missing. Update the onboarding recipe to handle contractors.
Today a story and a ticket are often one to one. They stay distinct in the model because they serve different purposes: tickets are what make agentic work visible, accountable, collaborative, assignable, discussable, and operable by people.
Every run leaves an inspectable work graph
A run is not represented only as messages and tool calls. Its epic and stories make the work inspectable, resumable, reviewable, and understandable. The primary operating experience describes what was requested, what work occurred, what changed, what succeeded, what failed, and what needs attention. Technical traces exist underneath, not in front.In the product today
Next
Run an agent
Trigger a run and follow it.
Review runs and tickets
Read what a run produced.