> 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/getting-started/core-concepts.md).

# Core Concepts

Map Concurrence's conceptual model to Platform and Classic resources, keeping authentication, version selection, conversations, and evidence distinct.

The two APIs use some of the same product names, but each has its own identifiers, credentials, payloads, and lifecycle rules. Use this map to find the correct implementation contract. For the relationships between data, configuration, execution, and evidence, read the conceptual [Core Concepts](https://docs.concurrence.com/platform-overview/core-concepts).

## Platform API

### Setup

| Concept                      | Implementation role                                                                                                    | Continue here                                                                 |
| ---------------------------- | ---------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------- |
| Workspace                    | Boundary for workspace resources, data, and access; account and identity routes have their own scope                   | [Workspaces](/developer-guide/platform-api/workspaces.md)                     |
| Agent                        | Versioned identity, general guidance, and communication style                                                          | [Agents](/developer-guide/platform-api/workspaces/agents.md)                  |
| Context Graph                | Authored states, transitions, objectives, and state tool bindings; the service selects the graph used at runtime       | [Context Graphs](https://docs.concurrence.com/agent/context-graphs)           |
| Skill                        | A companion definition with its own prompt and declared tools; the state binding governs execution and result handling | [Skills](/developer-guide/platform-api/workspaces/skills.md)                  |
| Service and version set      | Deployment configuration and the selected component versions and supported preferences                                 | [Services](/developer-guide/platform-api/workspaces/services.md)              |
| Channel use case and binding | Provisioned channel route connected to the service that handles it                                                     | [Use Cases & Bindings](/developer-guide/platform-api/workspaces/use-cases.md) |

A version selection is not a separate tenant or a snapshot of all source data. Agent and Context Graph instructions guide model behavior; authorization and tool validation enforce operation boundaries.

### Voice and Operations

| Concept      | Implementation role                                                                                                 | Continue here                                                         |
| ------------ | ------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------- |
| Conversation | Interaction history and lifecycle on a supported channel                                                            | [Conversations](/developer-guide/platform-api/conversations.md)       |
| Session      | Runtime context and protocol for processing an interaction; resumption and configuration loading depend on the path | [Sessions](/developer-guide/platform-api/platform-api/sessions.md)    |
| Run          | Channel-neutral inventory and detail for supported execution records                                                | [Runs](/developer-guide/platform-api/conversations/runs.md)           |
| Operator     | An authorized person using the controls supported by the channel                                                    | [Operators](/developer-guide/platform-api/conversations/operators.md) |

Platform supports text and messaging as well as phone calls. Operator joining on the current voice path uses a phone number; browser microphone joining has been removed. Listen, takeover, handback, external transfer, and integration-write approval are distinct operations.

### Data

| Concept          | Implementation role                                                           | Continue here                                                                          |
| ---------------- | ----------------------------------------------------------------------------- | -------------------------------------------------------------------------------------- |
| World model      | Source-attributed observations, entities, and derived read views              | [Data & World Model](/developer-guide/platform-api/data-world-model.md)                |
| Connector        | Supported source ingestion and separately controlled outbound delivery        | [Connector Runner](/developer-guide/platform-api/data-world-model/connector-runner.md) |
| Intake           | Authenticated submission to supported dataset sources                         | [Customer Data Intake](/developer-guide/platform-api/data-world-model/intake.md)       |
| Generated memory | Bounded observations and narrative context derived from previous interactions | [Memory](https://docs.concurrence.com/agent/memory)                                    |

Event acceptance, projection freshness, generated memory, and external delivery have different lifecycles. A recognized caller binding can locate an entity; it does not replace the verification required by the workflow.

## Classic API

### Setup

The Classic API scopes resources to an organization and acts through an authenticated user. A service and its selected version set determine the configured agent experience. Classic Tools, also called Actions, are versioned code packages. Dynamic Behaviors are a separate Classic feature; they are not Platform Skills or Platform triggers.

Continue with [Services](/developer-guide/classic-api/core-api/services.md), [Agents & Context Graphs](/developer-guide/classic-api/core-api/agents-and-context-graphs.md), [Tools](/developer-guide/classic-api/core-api/tools.md), and [Dynamic Behaviors](/developer-guide/classic-api/core-api/dynamic-behaviors.md).

### Users

A Classic user has an identifier, role-based permissions, and associated context. A user model is generated or maintained context used for personalization; it is not an authoritative copy of every clinical or scheduling fact.

See [Users](/developer-guide/classic-api/core-api/users.md), [User Models](/developer-guide/classic-api/core-api/users/user-models.md), and [Permissions](/developer-guide/classic-api/permissions.md).

### Conversations

Classic conversation creation and interaction use incremental NDJSON event streams on their streaming paths. A conversation contains interactions and retained messages. Consumers must process the documented event variants, distinguish errors from completion, and finish or resume the conversation under the relevant lifecycle contract.

Voice-note and realtime paths have their own media and protocol rules. See [Conversations](/developer-guide/classic-api/core-api/conversations.md), [Events](/developer-guide/classic-api/core-api/conversations/conversations-events.md), and [Lifecycle & Finish](/developer-guide/classic-api/core-api/conversations/conversations-lifecycle.md).

## Choosing the Right Contract

Use the API named in your service configuration and integration agreement. Do not assume a shared concept name implies shared storage, automatic migration, credential compatibility, or the same event format. [Terminology Mapping](/developer-guide/operations/reference/terminology-mapping.md) records the product-to-schema names; [Choose Credentials](/developer-guide/getting-started/credentials.md) explain the separate credential flows.


---

# 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.concurrence.com/developer-guide/getting-started/core-concepts.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.