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

The ContextWorks model: a domain carries entities; an entity curates fields by level, instructions, related lists, references, and elements drawn from a shared library

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, and exactly one per object is the default — used 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 prior version. → Versions

Levels

Every entity is defined 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. Changing a domain’s roster changes what deployed tools return 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. Two questions resolve separately: whether a write may happen — an AND of org, domain, entity, and field — and whether a human must approve it first, which one setting answers depending on whether the call named a domain. → Write access

Payloads

  • Semantics — labels, instructions, and synonyms, at every scope The same assembly renders as markdown (default, for reading and grounding) or JSON (for chaining). Format never changes what is included. → Payloads

What’s next