Ticket
person concept tool org talk claim — click a node to jump to its page; hover an arrow for the relation
A ticket is a structured, folder-based unit of work used to manage long-running agent tasks, serving as a persistent memory and execution record that allows work to be interrupted and resumed. In Alex Damis's workspace architecture, tickets live inside a Roadmap Folder and grow from small, scoped tasks into rich artifacts capturing the full lifecycle of a piece of work.
Structure and composition
Tickets are designed as folders containing several sub-components, each addressing a different aspect of long-running work:
- Journal Entries: As the agent works through a problem, it makes "structured additions to the ticket," creating a running diary of progress and decisions. 17:10
- Found Work: Unexpected work discovered during execution gets placed in "a special folder for that called found work," preventing scope creep from being lost or silently absorbed. 22:03
- Proof Receipts: A dedicated field where the agent records evidence that it actually verified its outputs — "essentially proving that it verified things." 13:25
- Resolution: A closing section capturing how the ticket ended, including agent-recorded verifications: "how did the ticket end? the agent can put the verifications." 22:58
Tickets "start small" and are visible on a roadmap view, scaling in complexity as work progresses. 15:54
Motivation: solving the memory problem
Alex Damis advocates for tickets explicitly because they solve the problem of continuity in long-running agent work — "work can be interrupted and resumed" — a critical requirement for what he calls "messy forever work." 24:04
Points of disagreement
Tickets vs. Feature Ledger
The ticket system emerged as a replacement for an earlier approach using a Feature Ledger — a single large document tracking all work. Damis abandoned this approach because the ledger became unmanageable at scale: "My feature ledger ended up being like 4,000 lines, 8,000 lines. My agent just could not make sense of it." 8:45 The ticket model addresses this by decomposing work into discrete, bounded units rather than accumulating everything in one growing document.