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

# Propose

> Mark a Patch ready for accountable review without publishing it or changing its audience.

# Propose a Patch

## Sources

Docs: [Patch](/ponder/parables/publishing/patch)

Web App: Open the active Patch in **Publish** and use **Propose** when the
readiness control is enabled.

**Propose** marks a Patch as ready for accountable review. It preserves the
exact changes being reviewed so later edits cannot silently alter the proposal.
It does not publish, push, deploy, or widen the audience.
The selected Patch and its status refresh after the command finishes, so the
next action uses the resulting state.

## Before proposing

Confirm that:

* the Patch contains the intended changes and no unrelated work;
* the affected Pages and Panes render in supported states and viewports;
* Plots and data meaning have been previewed or proved as appropriate;
* the audience and responsibilities are correct;
* important failures and recovery paths are documented; and
* the supporting Proofs are available to the reviewer.

## Read the readiness explanation

The first publication can use the content already built in Personal mode. You
do not need to make an extra edit after enabling Versions: Propose preserves
that existing definition for review.

A Patch can change only the source of an inherited Page, Pane, or Plot.
Propose retains that source edit without copying its unchanged upstream owner
into your Workspace.

When editing a Patch based on a published Workspace Version, the preview includes
that Version's inherited Pieces and your saved changes. A later upstream update
does not replace the Patch's recorded starting point.

A Pull preview includes the exact incoming definition and your saved changes.
Propose freezes that preview; a later Delivery does not replace it. The current
Workspace definition stays active until publication, and current permissions
still govern access to the preview.

After a published baseline exists, an empty Patch has nothing to propose.
The control also remains disabled when the Patch is stale, conflicted,
already closed, or otherwise not ready. Use the visible explanation to repair
the actual condition. Do not recreate the Patch merely to turn the button on.

After proposing, the accountable reviewer can accept, request changes, or use
the available lifecycle action. If more work is needed, return through the
supported Patch flow so the review history remains understandable.