> For the complete documentation index, see [llms.txt](https://docs.amigo.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.amigo.ai/developer-guide/operations.md).

# Operations

- [Best Practices](https://docs.amigo.ai/developer-guide/operations/devops.md): Operational best practices for version sets, channel tagging, multi-org tenancy, PHI isolation, and information ingestion.
- [Multi-Org Strategy (Region x Project)](https://docs.amigo.ai/developer-guide/operations/devops/multi-org-tenancy.md): Create and operate multiple Amigo organizations by region and project for tenant isolation.
- [Version Sets & Promotion](https://docs.amigo.ai/developer-guide/operations/devops/version-sets-best-practices.md): Manage version sets for safe deployment promotion from development through production.
- [Version Set CLI Reference](https://docs.amigo.ai/developer-guide/operations/devops/version-sets-best-practices/version-set-cli.md): Complete forge version-set, forge service, and forge asset command reference for listing, pinning, promoting, and rolling back Amigo service version sets.
- [Channel Tagging System](https://docs.amigo.ai/developer-guide/operations/devops/channel-tagging.md): Configure services for deployment channels (voice, text, async) with LLM preset validation.
- [PHI Isolation & Selective Sharing](https://docs.amigo.ai/developer-guide/operations/devops/phi-isolation-and-selective-sharing.md): Design patterns for PHI isolation and controlled cross-user data sharing.
- [Information Ingestion & Exchange](https://docs.amigo.ai/developer-guide/operations/devops/information-ingestion-and-exchange.md): Three paths for getting external information into ongoing conversations or user models.
- [Reference](https://docs.amigo.ai/developer-guide/operations/reference.md): Technical reference for rate limits, memory architecture, terminology mapping, common patterns, and architecture decisions.
- [Terminology Mapping](https://docs.amigo.ai/developer-guide/operations/reference/terminology-mapping.md): Complete mapping between platform documentation names and REST API field names.
- [Rate Limits](https://docs.amigo.ai/developer-guide/operations/reference/rate-limits.md): Per-endpoint Classic API rate limits, response headers, and retry guidance.
- [Memory Architecture & API Mapping](https://docs.amigo.ai/developer-guide/operations/reference/memory-architecture.md): Classic API L0-L3 memory labels mapped to their endpoints, plus the separate Platform API memory and world-model resources.
- [Common Patterns](https://docs.amigo.ai/developer-guide/operations/reference/common-patterns.md): Production-ready Classic API patterns for conversation lifecycle, user models, webhooks, routing, and CI simulation gates.
- [Architecture Decisions](https://docs.amigo.ai/developer-guide/operations/reference/architecture-decisions.md): Key architectural decisions in the Amigo API design and their rationale.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.amigo.ai/developer-guide/operations.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.