Record enough to repeat the input
Write the installed version, selected Zen slot, game environment, equipped jumper and shooting method. Add whether the shot was standing, moving or an L2 / LT fade. The point is to identify the test you performed, not to create a long equipment checklist.
For OneTap, include RELEASE PT and INSTA TEMPO. For a manual rhythm path, record RHYTHM TIME and the physical release gesture. For Button Shooting, record the selected Set/Move/Fade field and its environment bank. Use values shown by the active device.
Keep secondary settings steady
Human Mode, Human Tempo and Human Variation can influence scripted motion and processed waits in this base V6 snapshot. HUMAN LOGIC is the separate optional Button hold variation. Record their state rather than silently changing them between groups.
A different jumper, a moving shot or a new environment is a new condition. An interrupted attempt or an input you are unsure about should be marked in the note. Repeating a clean group is more informative than treating every attempt as equally comparable.
Treat the record as an observation
The lab records what you enter. It cannot read the game, detect a green window, inspect a compiled customer build or prove that the Zen ran the note's values. Keep those checks separate from the result table.
Once the conditions are written, change one timing field for a small comparison and repeat the same shot type. The saved record then answers a bounded question: what feedback was reported under these conditions before and after this edit?