# Should the settled pose come from each element's rest(), or from the SCREEN's
# settle instant? 2026-08-30. examples/rest_vs_settle.rs
#
bundles skipped as never-settling (window < 10 units): 896

CONTROL — elements where rest() takes the SOUND plateau path:
  8171 plateau elements in settling bundles
  4796 of them HOLD ACROSS the settle instant — the fair control
  pose_at(settle) agrees with rest() on 3748 of those (78.1 %)

TEST — elements where the unsound dwell fallback decides:
  2249 elements
    rest()          returns a VISIBLE pose on 1655 (73.6 %)
    pose_at(settle) returns a VISIBLE pose on 781 (34.7 %)

--- END (if this line is missing, the run did not finish) ---
#
# THE PROPOSAL: pose every element at UiBuild::settle_time() -- the midpoint of
# the longest keyframe-free interval ACROSS THE BUILD -- instead of asking each
# element for its own resting pose. That is the port agent's 're-key on the
# screen's span rather than the element's', and its shipped path already does it.
#
# WHAT THE TEST SHOWS: on the 2 249 fallback elements in settling bundles, the
# visible-pose rate falls 73.6 % -> 34.7 %. Consistent with the proposal
# removing transient peaks.
#
# 🔴 BUT MY CONTROL CANNOT VALIDATE IT, and that is the finding.
#
#   naive control, all plateau elements:                46.6 % agreement
#   fair control, only those HOLDING ACROSS the settle:  78.1 %
#
# The naive one was misspecified and I caught it by asking what 46.6 % means
# physically: rest() finds *a* held pose, many elements hold one during the
# build-in and then move on, and pose_at(settle) asks what is on screen when
# the screen has SETTLED. Different questions; disagreement proves nothing.
#
# The fair control's 78.1 % is still not a pass -- and worse, its 21.9 %
# residual is AMBIGUOUS BY CONSTRUCTION. rest_plateau() picks one plateau; an
# element with two, whose settle instant falls in the other, will disagree --
# and there pose_at(settle) is RIGHT and rest() is wrong. So the control
# cannot separate 'the candidate is wrong' from 'the incumbent is wrong'.
#
# ⚠️ COMPARING A CANDIDATE TO THE INCUMBENT CANNOT ADJUDICATE WHEN THE
# INCUMBENT IS THE THING UNDER SUSPICION. No amount of care with this control
# fixes that; it is the wrong shape of experiment.
#
# ✅ WHAT DOES ADJUDICATE IS THE ORACLE, AND IT IS NOT MINE. The port measured
# its publisher splash against a committed capture in both poses:
#   timeline (settle-instant) pose   RMSE 2.17   0.01 % differing
#   --pose=rest                      RMSE 9.05   0.75 % differing
# 75x the differing area, against the game. That is the evidence for the
# proposal. My numbers describe its effect; they do not establish it.