Definitions: visible_at_end

220 gate-passed questions · 20 cells · 10 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)

yes: px_end / CLEAR_PX; no: one bin · measurable on 134 questions

margin binnumeric range
near-edge [1,1.25)[−∞, 1.25)
bin0[1.25, 22.96)
bin1[22.96, ∞)
state:gone(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)

min queried-object peak area (frac of frame) · floor 0.0007716

salience binnumeric range
<floor (0.0008)[−∞, 0.0007716)
bin0[0.0007716, 0.01262)
bin1[0.01262, 0.02451)
bin2[0.02451, 0.04429)
bin3[0.04429, ∞)

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

answer (branch 1) · labels: no, yes

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

Answer distribution (gate-passed)

answern
yes134
no86

Type-level verdict