Semantics
Semantics are what you tell the agent about a thing: what to call it, what it means, and what people call it. You edit them the same way everywhere, behind the same glyph.
The three slots
| Slot | Answers | Travels |
|---|---|---|
| Label | What to call it in payloads and the catalog | Get Catalog and every payload |
| Instruction | What it means here, in your org’s terms | Rendered inline with the value |
| Synonyms | What people call it | Get Catalog, so the agent recognizes the word |
Where you set them
The same editor appears at four scopes:
| Scope | Where |
|---|---|
| Entity | Builder → Meaning |
| Domain | Domains → edit a domain → Meaning |
| Field | Field picker → the Meaning column |
| Element | Element library → the element’s Details tab |
The glyph is filled when something is declared and bare when nothing is, so you can see coverage without opening anything.
Labels
A label renames a field for the agent. “Amount” can read as Contract Value if that is what your org calls it.
The API name never changes. Both catalog formats show it in its own column beside the label, because filters and writes still speak API names. The Studio tab shows the Salesforce label next to any override, so you don’t lose your bearings against setup.
Instructions
Write what the value means, not what the field is. “List price — for net ARR use the ARR field” earns its place; “The amount field” does not.
Field instructions layer on top of the field’s own help text rather than replacing it.
Semantics are versioned
Entity and field semantics are catalog contract, so they ship with a version: edit them and the change waits for Activate like any other. Element and domain semantics apply the moment you save, because they are shared rather than versioned.
What’s next
- Instructions — writing good ones.
- Fields — where field semantics live.