> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cortex-labs.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Trace a published result to its evidence and decisions

> Follow one published exact version through approval, method and source records without changing the result.

Choose one published output you are authorised to inspect. You need access to the publication record, reviewed version and supporting evidence.

The goal is an explainable record of production and decision-making. Traceability enables checking; it does not establish that every claim is correct.

<Steps>
  <Step title="Identify the publication">
    Open the published result and its receipt. Record workspace, edition if applicable, artefact identity, exact version and publication time.

    Check whether it was later withdrawn or corrected. An uncertain external acknowledgement remains an unresolved delivery outcome.
  </Step>

  <Step title="Inspect the reviewed bundle">
    Open the exact source content, supporting assets and final export. Compare them with the approved version.

    Check rendering inputs and retained asset integrity. A newer draft must not replace the version under inspection.
  </Step>

  <Step title="Follow human decisions">
    Open the relevant review item or configured workflow decision. Check subject version, required passes, assignees, actor, time and recorded outcome.

    Confirm that the applicable final publication pass is human. Keep comments and advisory agent checks distinct from approval.
  </Step>

  <Step title="Trace a material claim">
    Select one substantive claim and open its citation. Follow the exact fragment version, source locator and producing enrichment result.

    Inspect the retained source, ingestion run or upload provenance. Check modality, time, processing gaps and conflicting evidence.
  </Step>

  <Step title="Inspect the method and complete inputs">
    Follow the run's evidence selection and definition/dependency versions. The complete input set can include context beyond visible citations.

    Record the actual model/output and any declared computation. A model identity alone does not promise identical regeneration.
  </Step>

  <Step title="Record the limits of verification">
    Separate missing, expired, erased and inaccessible evidence. A tombstone preserves the provenance path while indicating that the bytes are gone.

    Save the inspected identities, supported findings and unresolved gaps within the permitted audit scope. Leave the original output and decisions unchanged.
  </Step>
</Steps>

Repeat the claim check for the material findings needed by your inspection. A citation resolving successfully is the start of evidence assessment, rather than its conclusion.

Use [Inspect audit events within a granted scope](/audit-and-compliance/inspect-audit-events) for the corresponding actor and operation records.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.