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

# Patterns

> Familiar ways to review, compare, decide, and keep work moving.

Choose a way of working that people recognise, then use it inside your
workflow. One model does the work, another reviews it, and a judge decides
whether another revision is worth doing. A person makes the calls you
leave to them. The same patterns fit a research summary, a translated
passage or a code change.

| When you want to... | Read |
| - | - |
| Give a writer useful notes from another model | [Get a Second Opinion](/docs/patterns/writer-and-reviewer) |
| Make sure every requirement in the brief is done before the reviews | [Check the Brief Was Met](/docs/patterns/check-the-brief) |
| Decide whether another review round is worth it | [Know When to Stop](/docs/patterns/judge-stops-the-loop) |
| Hear from several reviewers before accepting work | [Ask a Panel](/docs/patterns/review-panel) |
| Try several approaches and keep the best-scoring pass | [Compare Different Approaches](/docs/patterns/tournament) |
| Run a test or check and use its result | [Automate the Routine Work](/docs/patterns/command-kickback) |
| Stop for a person's decision | [Ask a Person](/docs/patterns/approval) |
| Approve exact file bytes and check the result | [Check Before Acting](/docs/patterns/safe-change) |
| Let team members ask and answer during a run | [Bring the Team Together](/docs/patterns/team-conversation) |
| Brief a colleague with relevant context | [Prepare context](/docs/memory/mechanics) |
| Continue after an interruption | [Pick up unfinished work](/docs/concepts/record) |
| Set the order, checks and decisions | [Follow a process](/docs/concepts/workflows) |

The [feature team](/docs/workflows/feature-team) gives Jev the decision about
another revision. `judge()` from `@obversa/runtime` sets the stopping rule:

```ts examples/teams/feature-delivery.ts (excerpt) theme={null}
      maxKickbacks: { build: judge(judgeSeat) },
```

The judge weighs every finding, a blocking one included, against the work
and its revision history, and the run ends when it stops the rounds or the
review passes. [Know when to stop](/docs/patterns/judge-stops-the-loop)
shows the questions and a complete writing example.

The [literature watch](/docs/workflows/research/literature-watch) combines
summaries, a person's selection and a question answered from the kept
notes. [Feature delivery](/docs/workflows/feature-team) combines tests, a goal
check, a review battery, a judge and approval. Start with the patterns that fit
your work and combine them around the result you need.

## Next steps

* **See complete teams:** [Examples](/docs/workflows) has runnable workflows across several fields.
* **Start your own:** [Installation](/docs/get-started/installation) gets a project ready to run one.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.