Start with crm event. The entry pairs “Validate identifier” with “Source”. That pairing is useful only when it is clear why the context supports the state. A connection diagram can show endpoints while omitting the meaning of the fields that cross between them.
Begin with the constraint
State the source of truth and transformation rule for each critical field. Document what happens when a dependency is unavailable.
Example: CRM event
The illustrative record contains validate identifier. Its state is source. Ask what evidence supports that state, which detail is still uncertain and whether the next person could understand it without reading a separate message thread.
Questions for a working review
- Define the decision the reader needs to make. For crm event, use “Validate identifier” as the starting context.
- Find the source behind the example record. For crm event, use “Validate identifier” as the starting context.
- Write down the open question before choosing a state. For crm event, use “Validate identifier” as the starting context.
A small exercise
Take one recent integration planning example from your own process. Write its context without using a status label, then add the label separately. If the two contradict each other, investigate the source before updating the record. Compare the result with “Mapping step” in the demonstration to see which distinctions your process needs.
These are planning notes. The specimen is illustrative, and the preview does not process live work.
More practical notes →