Studio tour
The Build pages of the Studio tab are where you decide what agents see. Deploying, observing and administering live on their own tabs in the same app.
The Build pages
| Page | What lives there |
|---|---|
| Catalog | The home — what each domain serves, and what needs attention → Catalog |
| Entities | Every entity, as cards or a table → Entities |
| Briefs | How the data should be read — methodology, voice, glossary, policy → Briefs |
| Skills | Packaged procedures agents follow → Skills |
| Domains | Named sets of context that agents ask for by name → Domains |
| Metrics · Formulas · Filters · Enrichments | Four views of one element library |
| Change Log | One history across all three libraries, plus domains → Change Log |
Whatever names something, opens it. A domain’s roster row opens that entity, a brief’s Domains tab opens the domain, an issue in Observe opens the entity it names. Links that leave the Studio tab open a new browser tab, so you keep the page you were reading.
What goes where
| You want the agent to have | Use |
|---|---|
| A field from the record | Fields |
| The meaning of a field or the record | Instructions |
| Child records as rows | Related lists |
| A parent record’s details inline | References |
| A count or total over children | Metrics |
| Arithmetic over this record’s fields | Formulas |
| Something only code can produce | Enrichments |
| A business word agents can filter by | Named filters |
| One name covering several entities | Domains |
| The story of who changed what, and why | Change Log |
| How the data should be read | Briefs |
| A procedure agents follow when the task matches | Skills |
| Permission to filter or update a field | Fields · Turning writes on |
Linking into Studio
Studio pages are URL-addressable. c__nav names a section and c__open an artifact to open:
/lightning/n/ctxl__studio?c__nav=briefs&c__open=brand_voiceA runbook, a ticket or a Slack message can point at exactly one brief. The same works on the Deploy and Observe tabs with their section names.
Clicking an entity, brief or skill record anywhere the platform shows records — a report, a list view, global search — opens its Studio page rather than a bare record detail.
Notes
Entities, elements and domains are records, not metadata. Activate is a record update, so the next call has it. Configuration moves between orgs as data, and package upgrades never overwrite your edits or re-seed.
Best practices
- Curate
listdeliberately. An entity’slistfields are the columns it shows inside other payloads — related lists, Find Records results, records-shaped enrichments. → Levels - Prefer a metric to a related list when the question is “how many” or “how much”. One number costs a fraction of twenty-five rows.