A send to a working member is accepted and returns a ticket, then is never
delivered. That happened three times in one session here, and the member was
released still executing a brief that had been retracted twice. The receipt is
true — it is a fact about the mailbox, when what was needed was a fact about the
pane.
The fleet01 lead named the mechanism: a push delivery needs the recipient free at
send time, while a pull channel needs only that they look before acting. So the
ticket is not more reliable than the mailbox, it is a different direction, and its
success depends on the member's procedure rather than on the timing of the send.
Both halves have to be written down, because each is useless alone:
- Member (turn contract, new item 4): re-read the ticket before acting on anything
told earlier, and again before committing. A ticket comment that contradicts the
brief is newer and wins.
- Lead (step 5): all corrections go to the ticket, and the brief is write-once.
The member cannot check which source is newer — it just always prefers the
ticket — so revising a brief in place makes it obey the rule and do the wrong
thing. A first brief for a unit not yet running is not a correction.
wiki/7-Use-Cases.md is updated to keep the canonical block byte-identical; the
sync check passes. The wiki submodule pointer is deliberately left unstaged.
Dai Ha