Overview
Every concept in ContextWorks, defined in a sentence or two, with a link to the page that covers it in full.
The ContextWorks model
Entities
An entity is a curated view of one Salesforce object: which fields, in what order, with what meaning. An object can have several entities. Exactly one of them is the default: it answers when a caller names the object but not an entity. → Entities
Versions
Versions work like Flow versions: edit the draft, then activate to publish. Nothing you save reaches an agent until you activate, and you can roll back to any earlier version. → Versions
Levels
You curate every entity at three depths — list, standard, and detailed — and the caller picks one per request. Levels keep a 25-row list from carrying 30 fields per record. → Levels
Elements
Metrics, formulas, and enrichments live in a shared library. Define an element once, add it to any number of entities by API name. Editing it changes every entity that uses it. → Elements
Domains
A domain groups entities into a named set that agents call by name. Each object appears once per domain. Change a domain’s roster and deployed tools return the new set on their next call, no code changes. → Domains
- Domain access — who gets which catalog: sharing, the default domain, and grants
Domain management
Optional. Home an entity in a domain and that domain’s managers maintain it, and nothing else. If admins configure everything, none of this appears. → Domain management
Security
Every query runs as the calling user: object permissions, field-level security, and record sharing all apply. → Security
Write access
Agents can change records, not just read them. A write happens only when org, domain, entity, and field all allow it. Whether a human must approve it first is a separate question. One setting answers it, depending on whether the call named a domain. → Write access
Create access
Agents can add records too, through a separate chain: its own org switch, domain flag, entity toggle, and field list. Turning writes on does not turn creating on. An org can let agents log a task and never touch a deal. → Create access
Payloads
The same assembly renders as markdown (default, for reading and grounding) or JSON (for chaining). Format never changes what a payload contains. → Payloads
- Semantics — labels, instructions, and synonyms, at every scope