Reproducible technical method
Provenance and Evidence-Preservation Methodology
This method preserves what a system produced, when it was captured, and how later reviewers can verify the artifact. It does not treat a model output as a signature, commitment, agreement, or statement by the provider.
Scope boundary
A hash can demonstrate that two files are byte-for-byte identical. A timestamp can corroborate when a record existed. Neither, by itself, proves authorship, truth, legal assent, or the evidentiary weight a court will assign.
Capture the original output
Export or preserve the output in a stable file format together with the visible prompt, response, capture time, account or workspace context, and the tool version when available.
Normalize without changing substance
Keep the original artifact. If a normalized copy is needed for comparison, record the transformation rules, file name, byte length, and relationship to the original.
Compute a content hash
Calculate a modern cryptographic digest over the exact preserved bytes. Record the algorithm and digest so another party can recompute it from the same artifact.
Record an independently checkable time
Attach a timestamp source and its status. A local clock is context only; a provider receipt, signed service record, or completed public anchoring receipt provides stronger independent corroboration.
Cross-reference related artifacts
Link prompts, outputs, exports, receipts, review notes, and later versions by identifiers and hashes. Cross-references show provenance relationships; they do not prove that a tool provider accepted contractual terms.
Minimum verification package
Verification rule
Publish only the verification status supported by the retained record. If an anchor, receipt, signature, or external reference cannot be independently checked, label it pending or internal rather than verified.