Knowledge on a board
The Context item in the sidebar is Calypso Context, the knowledge layer, seen from the dashboard. This page is the bridge: what it means for a board. Everything deeper — ingestion routes, readiness, the API — is documented under Context itself.
What a board knows
A board's knowledge is a set of sources grouped into a bucket. On the board you see it as a short summary: how many catalogues, how many price sheets, how many pages, how many photos, and a total.
That summary is the answer to "what can this agent possibly say?" If a fact is not in there, the agent should not be producing it.
Adding a source
From Context, add the file, the website, or the page and put it in the bucket the board reads. Four families are accepted:
| Family | Examples |
|---|---|
| Documents | PDF, Word, Markdown, plain text |
| Data | CSV and JSON — export spreadsheets to CSV first |
| Websites | Your site, your help centre, a delivery-zones page |
| Images | PNG and JPEG, read for what they depict |
Exact types, size limits and behaviour are in Files and Websites.
Ready, not just uploaded
Adding a source does not make it answerable immediately — it is stored and queued, then indexed. Until a source is ready, an agent will not answer from it. If you have just added something and the agent does not know it yet, check readiness before assuming anything is wrong. See Ingest.
Scoping is the point
Give each board only what it needs. Scoping is not tidiness — it is what makes the Support agent unable to quote a price and the Sales agent unable to improvise a returns policy.
Continue in Context
| Context overview | The knowledge layer end to end |
| Ingest | Every route that puts a source in a bucket |
| Buckets | Creating and managing buckets |
| Agents | Binding an agent to the buckets it may read |