01
Anatomy
Project
A project maps Overlord to a repository and working directory so work always has a concrete execution target.
Anatomy Diagram
Eight parts, one durable workflow.
The overlord workflow, described in one image.
A Project 01 anchors the repository. A Ticket 02 carries the durable work record. Inside it, each agent prompt becomes an Objective 03, executed through an Agent Session 04 via a Connector 05, against a configured Project Resource 06. The resulting work accumulates into Shared Context 07, with Change Rationales 08 to explain why files changed.
Setup
Configured once per project before ticket work starts.
06
Anatomy
Project Resource
Resources define where an agent can operate, such as a local directory, SSH host, or other typed execution surface.
05
Anatomy
Connector
Connectors translate the same Overlord protocol into Codex, Claude Code, Cursor, OpenCode, and similar agent environments.
Define and Execute
Repeated for each ticket as objectives move from prompt to delivery.
02
Anatomy
Ticket
A ticket is the durable work record. It holds the shared context, prompt history, progress, delivery, and review.
03
Anatomy
Objective
Objectives are sequential steps inside a ticket. Each agent prompt becomes one objective with its own lifecycle.
04
Anatomy
Agent Session
The attached session is the live execution thread for one objective, including updates, questions, and delivery.
Persist
Information that stays durable so handoffs and follow-up work do not reset context.
07
Anatomy
Shared Context
Shared context survives across objectives so the next agent inherits prior decisions, files, artifacts, and discussion.
08
Anatomy
Change Rationale
Every meaningful file change can carry a rationale that records what changed, why it changed, and the expected impact.