Tier L, and it is not the animation that makes it so. Three things in the
report are not presentation: a ritual is an interaction with no command
behind it and must never reach the recording; hand order is not game state
and must not move the state hash; and animating another player's move
needs the page to see a SEQUENCE, not a state.
The obstacle named up front: the page reloads after every accepted
command, which destroys the DOM, and you cannot animate across it. Letting
JS mutate the DOM instead is refused — that is ADR-0007 D5's line. Rust
describes the movement and the reloaded page animates into place, which
keeps the server authoritative and makes the animation a rendering of
facts Rust wrote, exactly like the log. The journal is already the
sequence needed.
The invariant that protects the rest: for the same seed and the same
decisions, the recording is byte-identical in both paces.
Left ready, not active: tier L requires a separate-agent adversarial
review before code, and it has not been done.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
