Record the five moments that change the work
Run history is the part of an AI harness that lets a reader reconstruct the job without relying on a vendor session.
Start with the job definition. Name the requested artifact, intended reader, source set, exclusions, and stopping rule.
Next, record which source notes were selected. Then preserve the first brief, the separate review finding, the corrected final brief, and the final export state. Each stage needs a date, an owner role, and a link to the relevant artifact.
Leave out account details, machine information, private locations, credentials, raw traces, and provider telemetry. Those details do not help a reader understand the work and can create a second privacy problem.
Read the fabricated example as a sequence
The fixed run starts with workshop notes for independent consultants. They confirm a two-hour planning session and require confirmed details only.
The first brief adds “Saturday sessions are available.” Review records the unsupported claim, correction removes it, and the final checkpoint leaves schedule and price unknown.
The history preserves both versions. That makes the change inspectable and prevents the Saturday sentence from returning as an approved fact.
Keep the record smaller than the work
Store decisions that change the artifact. Do not copy every intermediate thought. A reader should be able to answer what the job used, what changed, who remained responsible, and what the final file can prove.
This method fits recurring briefs, research comparisons, operating guides, and other work that may be resumed or reused. It adds little value to disposable text with no future decision attached.