whet publish

Marks an artifact as published in the workbench. If the pipeline has auto-fanout enabled, publication to the destination is handled by the downstream job runner; this command records the operator's decision.

Usage

whet publish <artifact_id> [--reason <text>] [--final-text <text>]

Example

$ whet publish rf_4f5g --reason "approved by team lead"
✓ Published · run rn_98zy → status=published

Flags

Flag	Type	Description
--reason	string	Short note for the history. Useful for auditing.
--final-text	string	Override the final text. If omitted, uses the artifact's current text as it is in the inbox.

Publication policy

Whet does not auto-publish in the background. The command kicks off the publish flow in the deployment — but content generation and the decision to mark something as published always originate from an explicit action (in the UI, CLI, or MCP). There is no scheduler that picks up ready artifacts and publishes them without human intervention.

If your deployment needs scheduled publishing with prior confirmation, wrap whet publish in your own external workflow that asks for confirmation first and only then invokes the command.

Common errors

Error	Cause	How to fix
409 artifact already published	The artifact has already been marked as published.	Check the state with whet inbox.
422 artifact in pending state	A refinement is in progress on this artifact.	Wait for it to finish; the inbox shows the child variant once it's ready.
400 fanout target not configured	The pipeline has auto-fanout enabled but the destination surface is not connected.	Configure credentials in Settings → Connections.