Definitions: temporal_order

73 gate-passed questions · 4 cells · 3 occupied · go to this type's cells

Bins were cut on this corpus at 240×135@16 (CLEAR_PX 25, motion floor 19 px). Margin bins: a near-edge band [1, 1.25) above the gate boundary, then corpus quantiles; salience bins: a visibility floor, then quantiles.

Axis 1 — margin (the gate quantity as a clearance ratio; ≥ 1 passes)

onset gap (frames) / 3; 'same': one bin · measurable on 0 questions

margin binnumeric range
near-edge [1,1.25)[−∞, 1.25)
bin0[1.25, ∞)
state:same(state / single bin)

Ask: is this the same quantity the gate certifies on for this type? Are the states (e.g. 'same', 'gone') the right one-bin exceptions? Are the edges where a change in difficulty actually happens?

Axis 2 — salience (how visible / how large the motion is)

motion extent: screen path / W · floor 0.07917

salience binnumeric range
<floor (0.0792)[−∞, 0.07917)
bin0[0.07917, 0.1566)
bin1[0.1566, 0.2364)
bin2[0.2364, ∞)

Ask: does this axis capture what makes a question of this type perceptually hard, independently of the answer? Is the floor the right anti-gaming boundary?

Axis 3 — context

branch 2 spread default: pm_entry_frame (cv) · labels: bin2

Compatible margin bins per context label (cells outside these are definitionally impossible):

Answer distribution (gate-passed)

answern
they start moving at the same time73

Type-level verdict