> ## 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.

# Publish or withdraw an approved artefact

> Verify the approved version, current publication authority and retained delivery or withdrawal record.

Use this procedure after the intended review path approves an exact output version. You need publication authority in the workspace and on the destination.

## Check the approved output

1. Open the version named by the completed review.
2. Inspect source content, required assets, evidence references and rendering inputs.
3. Compare its preview and final export with the reviewed output.
4. Confirm that approval still applies to those exact bytes and inputs.

Any material change requires a new version and new approval. Missing or corrupt assets block complete publication.

## Publish and inspect the receipt

Use the authorised publication action or the configured approval-only workflow route. Confirm destination, version and current authority.

In a workflow, the approval exit must deliver the unchanged reviewed subject to Publish. Model-generated JSON cannot supply a human decision. Inspect other incoming edges before relying on the gate.

After the action, open the workspace artefact library and publication record. Check the exact version, publication time, retained assets and approving decision.

Run completion and draft generation are separate outcomes. Approval alone is also insufficient evidence of publication.

## Treat uncertain delivery as unresolved

For an external destination, inspect the configured delivery record and acknowledgement. A timeout does not establish that the recipient received nothing.

Reconcile the intended delivery before retrying it. Repeated delivery of the same intended output must not create duplicate business actions.

Retain the unresolved state when the destination outcome cannot be established. Do not label it successful to complete a workflow.

## Withdraw a publication

A workspace Owner can use the authorised withdrawal action. Select the published version, state the reason and confirm the intended scope.

Inspect the withdrawal record and current library state. The approved version, decisions and publication history remain retained.

Withdrawal cannot recall bytes already received outside Cortex. Record any separate external follow-up under the destination's procedure.

For the full inspection path, use [Trace a published result to its evidence and decisions](/audit-and-compliance/trace-published-result).


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