Domains
A domain groups context into a named set that agents ask for by name: entities, the briefs it delivers, the skills it carries, and the Info it turns on. Domains are the one access model in ContextWorks: whoever holds a domain receives what it carries.
What a domain is for
Teams need different context from the same objects. A domain is one team’s access point: Sales Desk carries Account, Opportunity and Contact curated for pipeline work, while Finance carries the same accounts plus payment terms and invoice history.
A “Sales Desk Context” tool names the sales_desk domain, and the agent’s planner picks it by purpose. What the domain carries lives in its record, so you change the tool’s coverage without touching the tool.
Which entity answers for an object
A domain usually carries one entity per object:
| Object | Sales Desk | Finance |
|---|---|---|
| Account | account_360 | account_360 |
| Opportunity | opportunity_360 | finance_view |
Both domains point at the same account_360. A domain references entities rather than owning them, so editing that entity changes both.
A domain can also carry two readings of one object: the deals as sales runs them, and the same deals in contract terms. An agent that names the object gets the primary reading. To reach the other, an agent names the entity too.
The Roster tab’s Primary for Object column marks the primary entity, and appears only where an object has more than one row.
An entity’s home is a separate setting: the domain whose managers maintain that entity. Home matters only under domain management.
Change it anytime
Add or remove entities from either side: a domain’s Roster tab, or an entity’s own Domains tab. Either door edits the same list. Every tool naming the domain picks up the change on its next call, with no redeploy.
ContextWorks does not version what a domain carries. Each entity still serves whatever version it has active.
Studio shows rows you have no rights over, marked and read-only, so the list always names everyone who receives a domain.
Ask for an object the domain does not cover, and the response names what it does cover, so the agent can re-plan.
When to add one
Install creates General, and every agent call names a domain, so you always have one. Add another when a second team needs its own view of an object, or when a tool should be named for a job so an agent’s planner picks it by intent.
Notes
-
Record sharing on a domain decides who can discover it. Install shares General with everyone; share another domain with someone and they stop receiving General. → Domain access
-
A domain never grants or restricts data access. Every query runs as the calling user, so a domain widens what an agent may ask for, never what its user may see. → Security
-
Each domain has a color and an icon, both cosmetic. ContextWorks never tells an agent about either.
-
Deleting a domain leaves its entities alone, though they reach nobody until another domain carries them. You cannot delete the default domain.
What’s next
- Domain access — who sees which catalog
- Building domains — the how-to