Work stops living in a chat window that is about to close
A decision settles what you claim. A ticket asks someone to act on it.
The Problem
Chats end, and the to-do list in someone's head does not survive that.
The plan was in a conversation that is closed. Nobody picked it up, or somebody did, from a summary that left out the one thing that mattered.
How Stompy Helps
Keep decisions and requests apart. A decision settles what you claim or do. A ticket is a request to act on something already settled, and it sits on a board.
The request outlives the chat that created it. Any person, or any model in any tool, can pick it up days later. The person picking it up has none of the original reasoning, so each ticket carries what they need: where, the exact content, why in one line, and what must not change. It closes with a note saying what was actually done, including where the result differs from the request.
One session can act as lead. It files tickets and hands them to worker sessions that may be running in other tools. The lead reads the state of the board itself rather than waiting to be told, because a worker that reports "done" is not the same as work that is done.
Nothing here is automatic. No agent watches the board. Work starts when someone opens the project. The limit, plainly: only what you lock is kept.
Integration Walkthrough
Settle the decision first
The ticket will point at it, so the worker does not need the original conversation.
lock_context(project="my-project",topic="decision_export_format",content="""Decision: exports are CSV with a header row.Why: finance imports it directly.""")
File the request with what the worker needs
Where, the exact change, why in one line, and what must not change.
ticket(action="create",project="my-project",title="Add CSV export to the reports page",description="""Where: reports/export. Exact change: add a CSV button using the format in decision_export_format.Why: finance needs it for month end. Must not change: the existing PDF export.""")
The lead reads the board, not a report
The board shows what is actually open, in progress and done.
ticket_board(project="my-project", view="kanban")
A worker picks one up and closes it with what was done
Append the note first, including where the result differs from the request, then close.
ticket(action="claim", project="my-project", ticket_id="...")ticket(action="append", project="my-project", ticket_id="...", description="Done: CSV button added. Differs: the header names are lower case.")ticket(action="close", project="my-project", ticket_id="...")
What You Get
- Requests outlive the chat that created them
- Each ticket carries what a stranger needs: where, what, why, and what must not change
- The lead reads the board itself instead of trusting a report of done
- Works across tools: the person or model picking it up can be in a different one
Start your own record
Join the waitlist and we will tell you when your place is ready.