Use /knowledge to create and edit documents. The agent structures content consistently, validates SQL, and adds wiki links between related documents. You can also edit documents directly in the knowledge base UI.
/knowledge requires the Developer role. Explorers can use the analytics agent but cannot modify the knowledge base.
Creating documents
Document a table:
The agent creates a document at sales/table/orders with schema, relationships, common filters, and usage notes.
Create a metric:
The agent creates a document at finance/metric/mrr with the business definition, tested SQL, source tables, and filters.
Create a business rule:
Create a note:
Providing better context
The more context you give, the better the documentation. Compare:
vs:
Letting Delphina investigate
You don’t have to hand the agent a complete definition — ask it to investigate. In a /knowledge chat the agent can query your warehouse, mine your query history for how your analysts actually compute things, read uploaded source files under raw/, and check documents pulled in from MCP connections, then ground the new documentation in that evidence:
Point it at whatever you know: the tables to look at, the users or dashboards whose SQL to trust, the uploaded files to read. The agent reports what it found — the dominant SQL pattern, conflicting definitions across dashboards, edge-case filters — for you to confirm before anything is documented, and validates the final SQL against your warehouse.
This works for updates too:
Automating maintenance with workflows
The same investigation can run on a schedule. Create a workflow in Knowledge mode and give it a recurring maintenance job. Two patterns work well:
Find gaps from real usage — periodically compare what people actually ask in chats against what the knowledge base covers:
Turns the critic agent flagged for missing context are ready-made candidates for this review — the workflow can start from them instead of scanning every chat.
Keep documentation in sync with sources — check whether the configured knowledge sources changed and propose updates:
Start with a modest cadence, e.g. weekly, and let the workflow deliver its findings as issues or a Slack summary rather than acting silently.
Namespace structure
Documents are organized hierarchically: {domain}/table/{name}, {domain}/metric/{name}, {domain}/rule/{name}, {domain}/note/{name}. Documents reference each other with wiki links like [[sales/table/orders]].
Keeping documentation current
Schema changes — when tables are renamed or columns change:
Fix incorrect SQL:
Update business definitions:
Validate periodically:
Add new documentation as your data grows:
For larger additions, configure new sources at Context Layer > Sources, then start a knowledge update from chat:
The agent detects what changed, proposes a plan, and builds the documentation in a guided session. See the Onboarding guide.
Whichever path you take, the agent shows you what it plans to write before it writes it, and every edit is versioned so you can see what changed and roll it back. 
