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

# Mappings

> Curate how each source's raw values roll up into your canonical entities — review proposals, approve them, and manage your master records.

**Mappings** is where the context layer is actually shaped. Sources name things their
own way. In Mappings, you decide that `COCA COLA CLASSIC 330ML` and `Coke Classic 330`
are both your one [canonical entity](/context-layer/ontology) for Coca-Cola Classic.
Once mapped, every AI tool that queries your data via MCP rolls those values up the
same way.

You curate one [concept](/context-layer/ontology) at a time and can select the concept
from the switcher at the top. The module has two tabs.

## Canonical entities tab

Your master records for the selected concept. Here, you can see every
[canonical entity](/context-layer/ontology) with its attributes and how many sources
map to it. You can create a new entity, edit an entity's name and attributes, and
deprecate one you no longer use.

## Mappings tab

The curation queue. It has two parts:

* **Proposed** — raw source values waiting for a decision.
* **Approved** — the ledger of decisions already made.

Each proposed row shows the **source** it came from, the **raw value**, a **suggested
entity**, the **volume** (how many rows carry that value), and how the suggestion was
made:

| Match method | How the suggestion was found                         |
| ------------ | ---------------------------------------------------- |
| **Exact**    | The raw value matched a canonical value outright     |
| **Rule**     | A configured rule mapped it                          |
| **Fuzzy**    | A close textual match, shown with a confidence score |
| **AI**       | An AI-proposed match, shown with a confidence score  |

Each row also carries a status:

* **New** — no suggestion yet; needs a canonical entity chosen or created.
* **Review** — one confident suggestion to confirm.
* **Conflict** — more than one candidate; pick the right one.

### What you can do

* **Approve** a proposal onto its suggested entity or pick a different one.
* **Create a new canonical entity** inline and approve the value onto it in one step.
* **Reject** a proposal that shouldn't map.
* **Remap** an already-approved value to a different entity.
* **Bulk-approve** many proposals at once.

<Note>
  Curating mappings — approve, reject, remap, create, and bulk-approve — requires
  **admin** access. Members can view the queue and the ledger but not change them. See
  [Governance](/context-layer/governance) for roles.
</Note>

<Note>
  Curation is available to your AI tools so the same actions via the UI are also
  available to agents over MCP. The UI and your agents draw on one governed mapping
  path. As fresh sources arrive, additional "New" proposals will surface here.
</Note>