Where every agent starts.
The index of what's available, what each piece means, and how to use the context layer.
A published table of contents.
The catalog is published per domain. An agent reads it before it asks for anything: every entity, brief and skill that domain allows, each with descriptions, instructions and details.
From there it decides where to dig in — which entity to load and at what depth, which briefs contain the background, which skill fits the task. The index also says how: how to load entities, what filters are available, what to fetch before aggregating.
A purpose-built agent gets a narrow set. A conversational tool gets a broad one.
How definitions get writtenDomain
The index
what every agent sees first
Entities (6)
- Account 360
- Campaign 360
- Contact 360
- Lead 360
- Opportunity 360
- User 360
Briefs (1)
- RevWorks Sales Methodology
Skills (1)
- Pipeline Review
The index every agent sees first
~937 tokensContextWorks Catalog — revworks_sales domain
Sales context as RevWorks curates it: deals with Deal Health, methodology status and progression, plus accounts, people and campaigns through their default views.
Three of six entities shown. Briefs and skills follow in the same index.
The agent's front door to your data.
Domain specific
An agent reaches what its domain carries, and nothing else.
Markdown or JSON
Whichever the surface asked for. The format changes the shape, never the contents.
From table of contents, to all the details
The index names what exists. From there: the entity at the depth it needs, the briefs behind it, the skill for the task.
