Track provenance of an agent-generated report

When to use this guide

An agent produces a report with cited sources, then a user edits the conclusion before exporting it to a client.

This is a fictional implementation scenario. The procedure below is Article 50 Hub's suggested working method, not a prescribed legal form, a customer result or a claim that every step is an additional statutory requirement.

Review procedure

1. Record the generated output version and relevant source references without unnecessary private prompts.

2. Track substantive edits and the person or process responsible for them.

3. Record any review decision against the exact final content version.

4. Verify that the export preserves the intended attribution and applicable labels.

What the example review finds

• The exported conclusion differs from the reviewed version.

• A citation is presented as support for a claim absent from its source.

Keep these example observations separate from your own results. An unknown or untested state should stay open until the relevant evidence has been inspected.

Fields for your working record

• Generated version

• Source reference

• Substantive edit

• Reviewed version

• Export evidence

Use the downloadable blank worksheet linked on this page to connect the observed behavior with the deployed system. Add a reviewer, date, evidence reference, unresolved questions and a next action. The worksheet is editable locally and does not upload your records to Article 50 Hub.

Completion and handoff

Close the task only for the scope actually reviewed. Preserve the result that another authorized reviewer can reproduce, identify the owner of remaining work, and record a retest when the implementation changes. A completed worksheet is not a substitute for the underlying evidence.

Decision boundary

Provenance records describe a workflow; they do not establish the truth of every claim or a legal labeling exception.

The official references below provide legal or technical context. Resolve applicability and exception questions with the responsible qualified reviewer; use the product's tools to organize implementation work within that assessment.