Route the conversation
Map every conversation the slice requires to a channel, an owner and a cadence, and name the record each one lands in.
Channel map
A conversation is not a decision until it lands in a record
Every decision in the map names the record that will hold it.
Supplied engagementMeridian Payments · Idempotent refund submissionheadless sliceStages 6 and 7 leave the fixture and use an engagement you run yourself.
Why this stage exists
A decision made in a call and never recorded is not a decision. Each conversation has a channel, an owner, a rhythm and a record it lands in.
There are exactly three systems of record. Anything that does not land in one of them did not happen.
What you start from
Work from these inputs only. Anything not on this list is either a later stage’s concern or a decision you do not own.
- Gate register
- Your completed gates from stage 2.
- The cadence table
- Section 04 of the operating process, 12 conversations in three clusters.
- The engagement
- A distributed client and pod with a 24-hour domain response commitment.
A conversation is not a decision until it lands in a record
One worked pass, so the shape of the work is visible before you do it on your own.
- Sort the conversations this slice needs into live conversation, written record and decision.
- Give each an owner and a cadence, and name its destination record.
- Route the domain question about retry behavior that only payments operations can answer.
- Define the exception path and the response commitment that triggers it.
What this turns onThe stand-up is coordination only. It carries no decisions and no evidence, which is what keeps it short and what makes the records load-bearing.
Do the work
- Complete the channel map for the supplied slice.
- Write the escalation path for a domain question that breaches its 24-hour commitment.
- Identify which unanswered question becomes a logged assumption, and who owns it.
- Find the conversation in the supplied engagement that currently has no record.
You produce
Channel map
- Conversation
- Channel
- Owner
- Cadence
- Record it lands in
- Visible to
Challenge your own result
The counterparty approves the scope on a call. Is the scope agreed?
Show how this resolves
Not yet. It is agreed when the spec owner records it against the Spec ID and the counterparty countersigns. Until then it is an intention, and intentions do not survive a disagreement six weeks later.
Ready to continue when
- Every decision in the map names the record that will hold it.
- The exception path has an owner and a stated response time.
What transfersAudit any engagement by asking where its last three decisions are written down.
Source · 04 Operating cadence