- Purpose
- Bring a request made of another party to a close that both sides have agreed.
- Operational principle
- If a requester asks a performer for something and says what would count as done, and the performer promises it, the conversation stays open until the performer reports it done and the requester declares the condition met.
- State
requester: Conversation -> one Partyperformer: Conversation -> one Partycondition: Conversation -> one Textby: Conversation -> opt Datestatus: Conversation -> one Status
- Actions
request A requester asks a performer for something and states the condition that would count as done.promise The performer agrees to meet the condition.counter The performer offers a different condition or date in place of the one asked for.decline The performer refuses, which closes the conversation.withdraw The requester takes the request back, which closes the conversation.reportComplete The performer says the condition has been met.declareSatisfied The requester accepts the report, which closes the conversation.declareUnsatisfied The requester rejects the report, which returns the conversation to the performer.
- Misfits
- The condition is agreed in words and judged by one side; the requester can declare unsatisfied what the performer reported done, and nothing in the concept settles who is right.
- The loop closes only by explicit acts, so a promise nobody follows up and a report nobody declares on stay open, and a system fills with conversations no one is in.
- Most systems run the loop with the promise left out; an assignee field records that the requester chose someone, not that the performer agreed, and the first the performer hears of it is a notification.
- Also called
- request and promise, commitment loop, action workflow, delegation
- Appears in
- GitHub pull-request review, Jira and Linear, as reporter and assignee with reopen, expense and leave approval flows, coding agents such as Claude Code, asked for something and reporting back