Systems
What should a record retain to make an action reviewable?
Connect task context, operator decisions, intended actions and observed outcomes in a reviewable structure.
An understandable record format, consistent identifiers and an explicit distinction between intention and observation.
A record is useful when someone who was absent can identify the object, version, evidence and reason for stopping. More fields do not automatically improve that understanding. The research asks which links help reconstruct the task and which simply add reading effort.
The local software demonstration already makes evidence and review states tangible. Assessing traceability still needs cases with known outcomes and independent readers. A well-linked record can explain a rejected action; it cannot turn that rejection into a completed physical task.