Skip to main content

​
Propose a Patch

​
Sources

Docs: 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. Proposing changes nothing readers see: their Pages keep reading the published definition while the Patch waits. Before its first Prepare, a proposed Pull shows the conflicts that Prepare will record. This includes a Workspace’s first Delivery of a Parable, before the Workspace has published a Version of it. After a published baseline exists, an empty Patch has nothing to propose. An edit to a Report or to one of its schedules counts as a change, so a Patch that only reschedules a Report can be proposed and published on its own. 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. The Propose control runs Prepare after proposing: it checks the Patch against the published line and records what it found. A Prepare holds only while the Patch and the line stay as they were when it ran. Proposing the Patch again runs Prepare for the new fingerprint. If Prepare did not finish, or another Patch publishes afterward, the Publish panel asks for a fresh Prepare and Publish stays disabled until it runs; Publish refuses a stale Prepare by the same rule. If the Changes are already published, Prepare refuses them with a 409 explaining that there is nothing left to prepare. To prepare Changes still being edited, Propose them first. Retrying the same command key keeps the invalid-transition refusal and asks for a new key; it does not turn that refusal into a server error. A Pane can propose too. When someone saves a Versioned setting that the Pane’s Policies let them change but who does not hold Publishing, the server puts that one change in a set of Changes of its own, authored by them, and proposes it. It appears with the other Changes for a Publishing participant to publish; the saver sees Saved to your Changes. After proposing, the accountable reviewer can accept, request changes, or use the available lifecycle action. Any participant in the Parable may open the Patch, before and after it is proposed; once it is pocketed, only its author may. Opening it never shows anyone more than the Parable’s current Policies allow: if the Patch removes or loosens a filter Policy, its readers stay filtered until it is published. A Plot the Patch adds reads for its author and for every Publishing or Primary participant whom its Pane’s Policies allow to create Plots and view its settings, so the people who may publish it can check its rows first. If more work is needed, return through the supported Patch flow so the review history remains understandable.