Write Before Show
Visible state is a projection. The board, cockpit, winner card, and queue badge are views assembled from durable facts. If a screen changes before the fact is written, a crash can leave the user remembering a state the system cannot prove ever existed.
Write-before-show reverses the temptation. Validate a transition, append the event and artifact address in one durable boundary, commit, then publish the projection. A client may be briefly stale, but it can refresh into truth. A client shown unwritten success can only refresh into contradiction.
This matters most at exciting moments: seat acceptance, submission, judge selection, verdict, unseal. Those are exactly where optimistic UI feels attractive and where losing an event destroys trust. Optimism may show 'sending' or 'pending'; it must not show a terminal fact before persistence succeeds.
The trail therefore is not an audit feature added later. It is the source from which operational state can be rebuilt and UI truth can be explained.