PROCESS: Workshop equipment request — fictional example v1
SOURCE: Original six-node diagram accompanying this guide.
START: A request arrives.
REQUIRED DETAILS: requested item, event date, contact.
N1 Receive request -> N2.
N2 Are all required details present?
  No -> N3 Ask for the missing details.
  Yes -> N4 Check whether the requested equipment is available.
N3 Wait for a revised request. On receipt -> N2, not N4.
N4 Is the requested equipment available for that event date?
  Yes -> N5 Send reservation confirmation. END: confirmed.
  No -> N6 Send unavailable reply. END: unavailable.

CONNECTIONS:
N1 -> N2 [request received]
N2 -> N3 [No: incomplete]
N3 -> N2 [revised request received]
N2 -> N4 [Yes: complete]
N4 -> N5 [Yes: available]
N4 -> N6 [No: unavailable]

CASES:
A. Complete + available: N1, N2 Yes, N4 Yes, N5.
B. Incomplete, then complete + available:
   N1, N2 No, N3, N2 Yes, N4 Yes, N5.
C. Complete + unavailable: N1, N2 Yes, N4 No, N6.

UNDEFINED IN THIS DIAGRAM:
No-response timeout; availability changing during review;
who may override an unavailable result.
Do not add these rules without the process owner's decision.