> ## 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. Commands that start with `pctx` mean the Port of Context platform CLI installed from pctx.ai, not the open-source tool of the same name. # Curation > Build and maintain the context map: who can change it, what it accepts, and how suggestions are reviewed. Curation is the work of keeping the context map accurate. Admins do most of it from the **Curation** tab in the dashboard, which only admins see. The rules for what the map accepts are under **Admin** → **Map rules**. ## Who can change the map ```mermaid theme={null} %%{init: {'flowchart': {'nodeSpacing': 28, 'rankSpacing': 34}}}%% flowchart TD W(Someone wants to change a node) --> E(Can they edit it?) E -- Yes --> C(They make the change) E -- No --> S(They suggest a change) S --> R(An admin or the owner reviews it) R -- Approve --> C R -- Not now --> D(Dismissed) C --> K(Does it follow the map rules?) K -- Yes --> M(On the map):::hub K -- No --> X(Rejected, with the rule named) ``` Every node can have an owner. The person who creates a node owns it, and an admin can assign a different owner. | Action | Who can do it | | - | - | | Add an entity or a domain | Admins and members | | Edit an entity | Admins, the entity's owner, and the person the entity represents | | Delete an entity or change who can see it | Admins and the entity's owner | | Add, change, or remove a connection | Admins, and the owner of the entity at either end | | Suggest a change | Anyone except readers | | Approve a suggestion | Admins, and the owner of the entity it changes | | Change the map rules | Admins | Readers can view the map but cannot change it or suggest changes. Assigning owners and limiting who can see a node need the Team or Enterprise plan. On the Free plan, admins manage every node. Open a node to see your own access under **Your access**, shown as **Can edit** or **View only**. ## Add to the map On the map, select **Add context** and choose what to add. | Choice | What it adds | | - | - | | **Entity** | A node: one of the kinds below | | **Connection** | A named link between two entities | | **Group** | A domain: a labelled set of entities that can span teams and systems | | **Indexed source** | A document collection, placed on the entity it documents | Admins also see **Use the Admin MCP** and **Use the API** for adding many records at once. ### Entity kinds | Kind | Use it for | | - | - | | Organization | A company or business unit | | Portfolio | A group of products, platforms, or initiatives | | Team | A squad, team, or guild | | Person | An individual | | Application | A service or product that people use | | Repository | A source code repository | | Datastore | A database, warehouse, lake, or queue | | External System | A third-party system you depend on | | Resource | A wiki page, runbook, dashboard, or other document | | External Agent | A third-party AI agent your organization uses | Every entity has a name, summary, description, tags, and links. Some kinds add their own fields: a person has a role and an email, and applications, repositories, datastores, and systems can record a URL, technologies, and owners. ### Connections | Connection | Allowed between | | - | - | | contains | An organization and its organizations, teams, or portfolios; a portfolio and its portfolios, teams, or applications; a team and its teams | | owns | A team or organization and a repository, application, datastore, or system; an organization and a portfolio; any of these and a resource | | belongs to | A person and a team, organization, or portfolio; a team and an organization | | manages | A person and a person or team | | collaborates with | Two teams, two organizations, or two people | | depends on | A team, application, repository, system, or external agent, and an application, repository, datastore, system, or external agent | | documents | A resource and anything | | is related to | Anything and anything | The map also enforces these rules: * Nothing connects to itself. * contains, owns, belongs to, and manages run one way. You cannot add the reverse of an existing connection. * A repository, application, datastore, or system has at most one owner. * contains cannot form a loop. A write that breaks a rule is rejected, and the error names the rule. When no specific connection fits, use **is related to**. ## Set your own map rules Open **Admin** → **Map rules** to add your organization's vocabulary on top of the built-in rules. * **Add a field to a kind.** Choose the kind, name the field, and pick a type: text, a fixed list of values, number, URL, email, yes/no, or date. You can make the field required. * **Allow a connection.** Choose two kinds and the connection between them, then select **Allow**. You cannot add new entity kinds or change the built-in rules. Removing a custom field leaves its existing values in place. The **Built-in rules** tab shows each kind's fields and the connections it can take part in. To check the existing map against the rules, ask an agent connected to the [admin MCP](https://docs.pctx.ai/administration/admin-mcp.md) to audit it. The audit lists every record that breaks a rule and changes nothing. ## Review suggestions A member who cannot edit a node sees **Suggest a change** on it, and **Suggest link** or **Suggest removal** on its connections. Integrations can submit suggestions through the API. Suggestions wait for review in three places: * **Curation** → **Review** * The **Suggestions** tab on the home page, with a count of the ones you can approve * A **Suggestion to review** notification Each suggestion reads as a sentence, such as a new entity, a new link, a link to remove, or a new group. Approve it with the button on the card, or select **Not now** to dismiss it. A suggested new entity opens in an editor first, so you can correct it before it goes on the map. The person who made the suggestion sees **Waiting for review** and can withdraw it. ## Fill gaps ```mermaid theme={null} flowchart LR A(An agent searches the map) --> B(Nothing matches) B --> C(The search appears under Fill gaps) C --> D(An admin adds it to the map):::hub ``` The **Curation** page shows what share of map searches found an answer over the last 14 days. Under **Fill gaps** it lists the searches that found nothing, with how many times each was asked. * Select **Add to map** to create the missing entity from the search. * Select **Not now** to hide the search until someone runs it again. The **Insights** page shows the other side: the most-used nodes, nodes nobody has used in the period, and searches that came back empty. Use it to decide what to remove. Nothing is removed automatically. ## Provenance Each record keeps where it came from. Open a node and look under **Provenance**. | Field | Meaning | | - | - | | Source | Who or what wrote the record, such as a person in the dashboard or the admin MCP | | Ref | A link or path back to the origin | | Trust | A confidence percentage | | Observed | When the fact was recorded | | Status | Shows **locked** once a person has edited the record or approved it from a suggestion | ## Domains A domain groups the entities needed for one area of work. Create one with **Add context** → **Group**. You can filter the map by domain, and agents can limit a search to a domain by name. To rename a domain, change its members, or delete it, ask an agent connected to the admin MCP. Deleting a domain removes only the grouping; its entities and connections stay. ## Point to context outside the map Do not copy a large or fast-changing system into the map. Add one Resource entity for it, and mark the connection to that resource as a pointer: 1. Create the Resource and connect the owning team or organization to it. 2. On the connection, select **Additional Context Pointer**. 3. In **Context Pointer Instructions**, write one sentence telling an agent how to use it, such as which folder holds the deal room. An agent that reads the owning entity is then told where to look when the answer is not on the map. ## What Port of Context adds for you * Every workspace member appears on the map as a Person. * Every service an admin enables appears as an External System. * A new workspace starts with a root Organization entity. These do not count toward your plan's node limit. ## The sample map A new workspace opens on a sample map of a fictional company so you can explore before adding your own. Sample records are read-only. * Select **Show my map** to switch to your own map, and **Show sample** to go back. * An admin can select **Remove sample**. This cannot be undone. The sample is also removed when the trial ends. ## Keep the map current from your own systems Under **Curation** → **Automate** there are step-by-step guides, each with a prompt you can copy into an agent: * **Sync your systems into the context map** creates and updates entities and connections from a script or CI job. * **Suggest changes for review** submits changes that a person approves before they reach the map. * **Publish a searchable knowledge base** publishes documents as an [indexed source](https://docs.pctx.ai/concepts/indexed-sources.md). Each guide lists the service account scopes it needs. ## Limits | Plan | Entities you can add | | - | - | | Free | 100 | | Team | 1,000 | | Enterprise | Unlimited | This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.