> ## 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. # Proofs > Check what each Parable shows: each Plot and how its answer came to be, each Perception card by card, and the Proofs that a Patch must meet before Publish. # Proofs ## Sources Docs: [The subject](https://docs.parable.work/ponder/parables/execution-context.md#the-subject), [Rows about a Parable](https://docs.parable.work/ponder/parables/pieces/preferences.md#rows-about-a-parable), [Plotted Path in Pane code](https://docs.parable.work/ponder/parables/sandbox-design-system.md), [Propose](https://docs.parable.work/ponder/parables/publishing/propose.md) Proofs is a Platform Parable. It opens on a page of its own, or as a tab beside a Parable. It has three tabs: **Plots**, **Perceptions** and **Publishing**. ## Where Proofs opens * **Full page.** The list at the left shows the Parables of this Workspace. Choose one, and every tab reads that Parable. **Every Parable** reads none. A reload starts with **Every Parable** again. * **Beside a Parable.** The Proofs tab in the Ponder header reads the Parable on screen: its Release, or the Patch on screen. The Parable that Proofs reads is its subject ([The subject](https://docs.parable.work/ponder/parables/execution-context.md#the-subject)). The subject grants nothing. The server checks it on every read, and it refuses a Parable that the person cannot read. The list shows the Parables that the Workspace holds a seat on. A Parable that one person keeps private does not show. ## Plots The Plots tab lists each Plot of the subject by name. Open a Plot to see its Plotted Path: how its answer came to be, from the tools its information comes from up to the Plot's Pane. A Plot's path is its Pane's path, so a Plot and its Pane share one explanation. A Plot that a Page owns has no Pane, so it shows that it has no Plotted Path. The person's own seat on the subject decides what the path shows, as in the Pane menu. The path never names a Pane that the person may not view. Under View as, Proofs offers no Plotted Path. ## Perceptions 1. Pick a Perception: a Concept, a Relationship or an Action. 2. Pick a category of a Category set, or an Estimate. 3. Judge each card: **Right**, **Wrong** or **Unsure**. The buttons, the arrow keys and a swipe do the same. **Undo** takes back the last verdict. Each card is one row that the claim holds. A card of an Estimate shows the Estimate's value. Each verdict saves as your own row: only you read it, and it stays after a reload. Perceptions does not run its rules yet. Proofs runs the rules of the four examples that Perceptions shipped on 2026-10-24 (Functions, Team Size, Meeting Kinds and Person Hours) over Perceptions' People and Meetings. A Meeting is external when Perceptions links it to a CRM account. A Workspace's own Category sets and Estimates do not show yet: Perceptions keeps them as one setting and shares no list of them with other Parables. ## Publishing A Proof is a check that a proposed Patch must meet before Publish. | Kind | Who adds it | Where it applies | | - | - | - | | Default Proof | Parable staff, as Default rows on the source Deployment | Every Parable of every Workspace. No Workspace can change it. | | Workspace Proof | Primary on Proofs | Every Parable of the Workspace | | Your Proof | Any member, for themselves | Every Parable where they hold Primary | The three Default Proofs are **Clear Words**, **Loading, Sound And Motion** and **Plots That Scale**. Each asks for one review by Ponder and is marked to hold Publish. The mark says what the Proof will do: a Proof does not hold Publish yet (see [Not built yet](#not-built-yet)). * Beside a Patch, **Processing Proofs** lists each Proof that applies, with people's reviews. A person with Pinging or above on Proofs saves a review: **Pass**, or **Patch** with what to fix. The server signs it with the person who saved it, and only that person changes it ([Rows about a Parable](https://docs.parable.work/ponder/parables/pieces/preferences.md#rows-about-a-parable)). * Beside a Release, **Previous Proofs** says that Proofs run when a Patch is proposed. * A Personal Parable saves changes directly, so it has no Patches to prove. ### Not built yet * Ponder does not review a Patch yet. * A Proof does not hold Publish yet, and nothing records a Publish past a Proof with a reason. * Previous Proofs cannot read the reviews of earlier Patches yet. The Proofs program builds these. Until then, Processing Proofs shows people's reviews only. ## Security * Proofs reads and saves at the person's own seat on Proofs. The mode that the person picked on the Parable beside it does not narrow Proofs. * Only a Platform Parable's own page chooses its subject. Parable staff write that code. On any other Parable the choice is refused. * A verdict in the Perceptions tab is a Me row. A review is a signed row about the Patch: a person who cannot read that Patch cannot read the review. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.