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

# Operations

- [Best Practices](https://docs.concurrence.com/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.concurrence.com/developer-guide/operations/devops/multi-org-tenancy.md): Create and operate multiple Concurrence organizations by region and project for tenant isolation.
- [Version Sets & Promotion](https://docs.concurrence.com/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.concurrence.com/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 Concurrence service version sets.
- [Channel Tagging System](https://docs.concurrence.com/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.concurrence.com/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.concurrence.com/developer-guide/operations/devops/information-ingestion-and-exchange.md): Choose external events, stored user context, or tool retrieval for Classic conversations, with links to the separate Platform data and session contracts.
- [Reference](https://docs.concurrence.com/developer-guide/operations/reference.md): Technical reference for rate limits, memory architecture, terminology mapping, common patterns, and architecture decisions.
- [Terminology Mapping](https://docs.concurrence.com/developer-guide/operations/reference/terminology-mapping.md): Map product terms to Classic API names and distinguish the separate Platform API contracts without renaming compatibility fields.
- [Rate Limits](https://docs.concurrence.com/developer-guide/operations/reference/rate-limits.md): Per-endpoint Classic API rate limits, response headers, and retry guidance.
- [Memory Architecture & API Mapping](https://docs.concurrence.com/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.concurrence.com/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.concurrence.com/developer-guide/operations/reference/architecture-decisions.md): Key architectural decisions in the Concurrence 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.concurrence.com/developer-guide/operations.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.