Reading

Twelve pieces on what a commitment is, what running one shows that a drawing cannot, where a promise comes apart, where the idea comes from, what it does to software and to agents, and what it costs a team to take seriously. Starting cold, the first three are the path — what they are, watching them run, and the four ways they break. The rest go deeper and can be read in any order, or not at all.

1. Only a person can promise A machine can do the doing. Asking, being free to refuse, and saying yes, that was it are the parts that stay with people — and they are what holds a business together.
2. Run it before anybody lives in it A drawing is read once. Running it shows whose day it is, who is waiting on whom, and what the design quietly asks of the people in it.
3. Where a promise comes apart The vague request, the agreement nobody actually made, the silence in the middle, and the closure that never comes — one failure for each quarter of the loop.
4. Two people agreed to different things Marketing heard we'll deliver these features. Development meant we'll try if technically feasible. What a map can hold of that, and what it cannot.
5. When the only answer is yes A yes is only a commitment if no was available. The moves that keep an agreement honest, and how they quietly disappear.
6. What it costs and what it buys Fewer stalls, clearer ownership, less rework — and the honest account of what goes wrong when this is imposed rather than offered.
7. Business runs on commitments Hiring, offers, roadmaps and support are all promises between people — and most of them are never said out loud.
8. Language is how commitments get made Speech acts, conditions of satisfaction, and the conversation for action — where this comes from, and the objection worth taking seriously.
9. The vocabulary Thirty-six terms, defined the way this notation uses them: request, offer, decline, revoke, conditions of satisfaction, breakdown.
10. What a process diagram leaves out BPMN says what happens and in what order. It is silent about who asked, who was free to refuse, and who says it was what they wanted.
11. What it does to software Data models track payloads; commitment models track who owes what to whom. The Coordinator, ActionWorkflow, agent protocols, and what changes in a schema.
12. The drawing says what to build Every moment is somebody's affordance or a delegation — and that partition is a specification.