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

# Pondering

> Use a Parable to work through one durable Problem with AI, teammates, context, and proof.

# Ponder with a Parable

## Sources

Docs: [Ponder Primer](/ponder/primer)

Web App: Open **Ponder** from your Workspace sidebar, then select or create a
Problem and open the Parable or Piece that should provide context.

A Parable in Ponder supports work that begins with a question, decision, risk,
or desired outcome. It keeps the conversation attached to the material being
considered so the result can be reviewed later.

## Start one durable Problem

<Steps>
  <Step title="Name the outcome">
    Create a Problem whose title another Workspace member can recognize.
  </Step>

  <Step title="Open the relevant context">
    Select the Parable, version, Patch, or Piece that the next request should
    consider.
  </Step>

  <Step title="Choose an approach">
    Select a Persona, response profile, and any Powers needed for this request.
  </Step>

  <Step title="Send a clear Message">
    State the outcome, constraints, and evidence that would make the result
    trustworthy.
  </Step>

  <Step title="Review before acting">
    Check sources, proposed actions, audience, and Proofs. Approve only the
    exact action you intend.
  </Step>
</Steps>

<Image src="/images/ponder/cohesive-composer.png" alt="Ponder composer with Persona, response profile, message, and optional context controls" />

<Image src="/images/ponder/cohesive-composer-narrow.png" alt="The same Ponder composer at a narrow viewport, with the controls stacked beneath the message" />

## Keep context and conversation together

Opening a different Piece can sharpen the next request without erasing earlier
Messages. Each part of the Problem remains reviewable with the context used at
that moment. Keep the same Problem while refining one outcome; create another
when the outcome, owner, or review path changes.

Use a Ping when another person should consult or be informed. Use Proofs when a
claim needs evidence. Neither mentions nor Pings bypass Workspace access.

## Recover without losing the thread

| What happened                      | Recovery                                                                                             |
| ---------------------------------- | ---------------------------------------------------------------------------------------------------- |
| The response is too broad          | Open a more specific Piece and clarify the request in the same Problem.                              |
| Ponder requests approval           | Read the target and effect; approve or decline that action explicitly.                               |
| A Persona or Power is unavailable  | Choose an available approach or ask a Workspace manager about availability.                          |
| A teammate cannot open the context | Ask the owner to review ordinary Workspace access; do not paste restricted content into the Message. |
| Work stops before completion       | Keep the Problem, read the visible error, correct the context or request, and try again.             |

## Related guides

* [Ponder Primer](/ponder/primer)
* [Personas](/ponder/personas)
* [Powers](/ponder/agent-skills)
* [Pinging](/ponder/parables/permissions/pinging)