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

> ## Agent Instructions
> Use the exact commands, endpoints, and product terms in these docs. Check the context map before connected services or the web.

# Context map

> Model what exists in your organization, how it relates, and who owns it.

The context map is a typed graph. Entities represent durable things in your organization; relations describe how those things work together.

## Entities

Your workspace defines the entity types that match its work. Common examples include:

> [card] People and teams
>
> Who does the work, their roles, and the groups they belong to.

> [card] Systems and repositories
>
> Where work happens, what each system is for, and who owns it.

> [card] Customers and partners
>
> External organizations and the internal teams responsible for them.

> [card] Domains
>
> Curated groupings that give an agent the right slice of the map for a task.

Each entity can carry a name, description, aliases, tags, and provenance.

## Relations

Relations connect two entities with a named direction.

```text Example context theme={null}
Payments team
  owns → Billing service
  maintains → payments-api
  uses → Stripe
  supports → Finance
```

Use relations that answer questions an agent will actually ask: who owns this, what depends on it, where is it documented, and which team should handle it?

## Domains

A domain groups the entities needed for a recurring area of work. It can represent a business unit, operational surface, customer portfolio, or another useful boundary.

> [!TIP]
>
> Keep a domain purposeful. Include the smallest set of entities that gives an agent enough context to act.

## Provenance and curation

Map entries retain their source so people can distinguish curated facts from imported proposals. Connector mappers can propose changes; a curator decides what becomes part of the shared model.

* Prefer stable organizational facts over transient activity.
* Use aliases for the names people actually type.
* Write descriptions for an agent deciding whether an entity is relevant.
* Remove duplicate or stale relationships instead of adding exceptions around them.

Ask the context map first

Check the context map first. Who owns customer identity, which systems are involved, and where should I look for implementation detail?

> [card] [Next: Connected services](https://docs.pctx.ai/concepts/connected-services.md)
>
> Give agents governed access to the tools your organization already uses.


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