01 · Truth modes
Authoritative state and presentation state are different products.
Authoritative state is the exact normalized state supplied by a validated replay artifact at an ordered replay coordinate. It includes discrete changes, event order, provenance, and confidence.
Presentation state is the image shown between authoritative samples. Positions may be visually interpolated for smooth motion. Health, weapon state, event order, and research conclusions do not interpolate.
02 · Time model
Subtick is an ordering problem before it is a rendering problem.
The target replay coordinate is ordered by (server_tick, phase_q32, ordinal). The server tick anchors the interval. The fixed-point phase locates the instant inside the interval. The ordinal resolves multiple authoritative changes at the same coordinate.
“Next subtick” therefore means advance to the next authoritative coordinate present in the artifact. It does not mean add an invented 1/N slice of a tick.
03 · Evidence
Derived claims arrive as versioned tracks.
Visibility, navigation, peek timing, reaction windows, utility effectiveness, and suspicious-behavior metrics are not silently recalculated from simplified browser geometry. They are produced server-side, versioned, and delivered with evidence references and declared dependencies.
- Direct observations stay separate from inferred results.
- Every analytical layer identifies its model or ruleset.
- Experimental overlays never overwrite canonical replay state.
- Missing evidence is represented explicitly rather than converted into zero.
04 · Uncertainty
A visual anomaly is not a verdict.
Subticked can make timing, ordering, visibility, and reconstruction evidence easier to inspect. It cannot turn incomplete evidence into certainty. Cheating, desynchronization, hit registration, server fault, and game-bug claims require separate, explicit standards of proof.
The product must always permit “unsupported,” “not observed,” “partial,” “conflicting,” and “unclear” outcomes.
05 · Reproducibility
The same coordinate must reconstruct the same state.
Direct seek, forward playback, pause/resume, different playback rates, and seeking from another point must converge on the same canonical state hash at a target coordinate. Pixel output can differ across graphics hardware; replay state cannot.