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

# Tips and Patterns

> A cross-referenced index of the practical guidance across the Duvo docs, grouped by what you're trying to do.

A running collection of the highest-value tips from across the docs, grouped by what you're trying to do. Each one links to the page with the full detail.

## Building good Agents

* **Write a clear, testable AOP.** It's the highest-leverage thing you control. See [Writing Effective AOPs](/best-practices/writing-effective-aops).
* **Match the model to the job.** Harder reasoning and longer procedures benefit from a stronger model; simple, high-volume tasks don't need one. See [Model Selection](/user-guide/advanced/model-selection).
* **Decide one Agent or several.** When a single AOP is juggling unrelated jobs, split it. See [Multi-Agent Process Decomposition](/user-guide/building-assignments/process-decomposition).
* **Pick how Runs start deliberately.** Schedules, triggers, Queues, and manual Starts each fit a different shape of work. See [Choosing How Your Agent Starts](/best-practices/choosing-how-runs-start).
* **Design Queues so Cases always close.** Every claimed Case should end completed, failed, postponed, or handed over. See [Designing Work Around Queues and Cases](/best-practices/queues-and-cases).
* **Give the Agent the right tools.** Pick the Connection pattern that fits the system you're integrating. See [Choosing the Right Connection Pattern](/user-guide/connections/integration-patterns).

## Running reliably

* **Test in a revision, then promote.** Validate changes safely before they reach production. See [Test Safely Before Going Live](/user-guide/getting-started/test-safely) and [Promote to Production](/user-guide/getting-started/promote-to-production).
* **Watch the first week.** A daily review cadence catches problems while they're cheap to fix. See [Monitor the First Week](/user-guide/getting-started/monitor-first-week).
* **Plan for retries and failures.** Decide what should happen when a step fails or input is malformed. See [Retries, Failures, and Skipped Steps](/user-guide/reliability/retries-and-failures).
* **Use Evaluations to find weak spots.** Duvo scores Runs against criteria derived from the AOP. See the [Runs List](/user-guide/running-assignments/jobs-list).

## Staying safe

* **Gate high-risk actions.** Put caps, thresholds, and hard limits in the AOP for anything financial, irreversible, or outbound. See [Guardrails for High-Risk Automations](/user-guide/security/high-risk-guardrails).
* **Add human approval where it matters.** Define exactly when the Agent should pause for a person. See [Human-in-the-Loop](/user-guide/assignment-features/human-in-the-loop) and [Designing Human-in-the-Loop Workflows](/user-guide/assignment-features/hitl-design).
* **Share Logins, don't keep them personal.** A Run can use a Login that's shared with the team (or owned by the person the Run runs as); a personal Login saved by someone else won't be available to it. If a sign-in "isn't loading," check that the Login is shared. See [Connections and Logins That Don't Break](/best-practices/reliable-connections).

## Scaling

* **Let Agents remember and learn.** Persisted context and feedback make recurring work better over time. See [Agent Memory](/user-guide/assignment-features/assignment-memory) and the [Learning Feature](/user-guide/assignment-features/learning-feature).

<Note>
  We're actively expanding this page. If a tip keeps coming up in support or in your own building, it belongs here.
</Note>