SYSE.49:4.3 - Implement observable state, actions and reset

Prepare the material, actions and observations needed for the selected distinction. For a human task, make the relevant working and response visible without supplying the very contribution being judged. For a software fixture, implement the needed state, permitted actions and effects. Make hidden fixture state available to an authorized evaluator when it is needed to judge consequences, without leaking it into the agent’s task.

Use SYSE.33 to initialize and reset isolated software instances, preserving task identity, starting state and trajectory. An old effect or cached answer can invalidate the comparison. For people, prepare fresh material and record prior exposure, help and fatigue; replacing a worksheet does not reset the person’s experience.

Distinguish imagined observations, outputs predicted by a model, and state actually obtained by executing the fixture. A synthetic execution is real execution of that fixture; it is not an observation of the receiving service. When simulated dynamics supply a relied-on approximation, qualify the model and consequential error through MMP.17/SYSE.10.