Skip to content

Handle lineage when an old input can no longer be opened

Preserve permitted operational metadata without recreating evidence beyond its retention boundary.

Guides

Handle lineage when an old input can no longer be opened — what should the operator record?

An old artifact can remain part of a table's historical lineage even after its underlying evidence is no longer available for inspection. The right response is not to reconstruct the missing content from memory or another unauthorized copy. Keep permitted metadata and explain the resulting verification limitation to current users.

Practical operations check
Preserve permitted operational metadata without recreating evidence beyond its retention boundary.
Record input_revision, current_access_state and the actual supported retention or availability condition. Avoid storing the old source identity in a general diagnostic if current rules no longer permit that identifying detail to be retained or shared.
State that the lineage reference is historical and that the old input cannot currently be reopened through this workflow. Do not claim continued factual verification, indefinite retention or full reproducibility where the necessary evidence is unavailable under current policy.
01 / Guides

Identify the unavailable dependency

Record input_revision, current_access_state and the actual supported retention or availability condition. Avoid storing the old source identity in a general diagnostic if current rules no longer permit that identifying detail to be retained or shared.

02 / Guides

Separate history from content

Where allowed, retain nonidentifying operation references such as filter revision and prior validation date. These can explain how a table was produced without implying that the original content remains accessible or that it may be restored for convenience.

03 / Guides

Test current reproducibility

Determine which transformation checks can still run from permitted artifacts and which require the unavailable input. Mark the latter unverified rather than rerunning against unrelated newer evidence and calling that an exact reproduction of the historical table.

04 / Guides

Gate inappropriate reuse

If a new task requires current source validation, the old signoff may be insufficient. Route the task for a fresh authorized decision or bounded new evidence rather than treating historical provenance metadata as a substitute for present access.

05 / Guides

Publish the limitation

State that the lineage reference is historical and that the old input cannot currently be reopened through this workflow. Do not claim continued factual verification, indefinite retention or full reproducibility where the necessary evidence is unavailable under current policy.

Keep the boundaries clear.

  • Preserve permitted operational metadata without recreating evidence beyond its retention boundary.
  • Operational record: Identify the unavailable dependency. Context badges do not certify access.

Start with a read-only check: ask your agent to report actual source coverage before collecting records or exporting an audience.

Primary references

Documentation reviewed 2026-11-15. Product capabilities, client availability and plans can change. Third-party marks identify their products, not an affiliation.

Know what social media shows about you.
Start with a question.

Get started
montage