Keep the rework
Professionals do not always get it right on the first attempt. Useful trajectories preserve failed calls, revised assumptions, and deliberate undo actions, without silently overwriting earlier attempts.
Capture reasoning at key decisions
When an action changes the judgment or task state, record a short rationale. At the end, ask participants how they verified completion, where failure was most likely, and what could create a false appearance of success.
Store decision rationales separately from tool arguments: arguments describe what was done; rationales explain why.
Review before release
Machine checks verify structure and constraints. Professional reviewers also assess whether the reasoning is sufficient, the evidence is reliable, and the final communication meets domain expectations.
This is a draft collection protocol. It does not imply that a formal expert dataset has already been created.