Mappings

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 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 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 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: 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.