SYSE.46:4.3 - Observe attempts and localize failures

Run the configured task under its stated permissions and stopping rules. Retain inputs, configuration, supplied support, selected action/call, actual return, next working material, continuation, effects and result use to the extent needed to reconstruct the comparison. These observable records need no hidden chain of reasoning. A missing observation is a measurement gap, not an unsuccessful or successful event inferred from silence.

Choose repetition from the variability and consequence of the intended reliance. Distinguish “succeeded at least once in several attempts” from “succeeded on every required repetition”; report the unit and attempt policy. Do not count a successful retry without its failed attempts and effects.

Use the support contrast and trace together. Supplied-support success with agent-selected failure can mean a skipped necessary call, malformed arguments, a return lost from the next input, or a good return ignored by the procedure. These need different repairs. Failure even with supplied support leaves support quality, actual availability, binding and use open before an intrinsic-capability conclusion.

Read the other failures at their actual location: missing write, retrieval miss, wrong target, effect uncertainty, bad integration or an unsupported environment judgement. A trace can narrow these questions without revealing a unique hidden cause. Return unresolved causation as such.