A saved run is an immutable answer to a particular bounded query at its local evidence cutoff. Use it to preserve the evidence available at that point, with current source disclosure still enforced.
Find the exact run
Open Saved investigations and select the intended identity. Check source instance and generation, kind, namespace, code, selected datasets, relationship mode, direction and temporal view. Similar display codes can refer to unrelated entities.
Read the related tables, timeline, local identity bridges, source coverage and limitations together. A partial result is not a complete trace or proof of unaffected stock. Use coverage and results before relying on it.
Compare time boundaries
A later source import, late event, correction or identity decision affects a new investigation. It does not silently rewrite a saved run. A historical as-known query uses the local sequence cutoff, which is different from occurrence time in the source.
When comparing two results, keep both run identities and explain what changed in admitted evidence or query scope. Do not label a changed related set a software inconsistency before checking those boundaries.
Download with current authority
Use the run's permitted JSON export and retain its exact identity and coverage reasons. Current dataset rights are rechecked for saved views, downloads and receipt disclosure. Permission that existed when the run was created is not permanent permission to read it now.
A missing grant can withhold the retained report rather than giving a partial leak. A case can become inaccessible when its complete required dataset union is no longer readable. Ask the Supervisor to review legitimate source access; do not request another person's sign-in or unrestricted archive.
Already downloaded files outside the product cannot be recalled by later reader removal. Store and share them under the source owner's agreed process.
Inspect decisions separately
Use the identity link's full decision history for approval, withdrawal and reapproval provenance. Earlier saved runs can reflect earlier valid decisions at their cutoff. Case history records the local review, not source containment.
The current workflow provides investigation JSON and source-scoped retained-record export. Do not promise a private printed evidence pack or PDF case bundle. Use exports and recovery for site-wide records.
Append an investigation note
A Supervisor with current disclosure of the run can enter New note under Investigation notes and choose Add a note. Use up to 500 Unicode characters without control characters. Record the observation, its basis and any handover clearly enough to be understood beside the retained run.
Read the newly recorded note and time before leaving. A note appends a local observation; it cannot amend source events, change the saved query result or issue an operational instruction in another product. If facts need correction, use the authorised source and intake process rather than describing a note as repaired evidence.