Reference
The Dashies contract: the spec schema, every tile type, runtime attributes, theme tokens, limits, SQL dialects, errors and the URL rules.
Reference answers "what are the exact parameters". It states the contract and nothing else: no walkthroughs, no rationale. When a page here needs to explain why, it links to Core concepts; when it needs to show you how, it links to Guides.
Most of this section is checked against the code it documents. A build guard reads the live MCP tool list, the exported size constants, and the published spec schema, and fails this site when a page disagrees with any of them.
The authoring contract
| Page | What it holds |
|---|---|
| Dashboard spec (v1) | Every field of the YAML document you publish, with its type and bounds. |
| Tile types | All eighteen tiles, their required bindings, and what each one does rather than draw a wrong picture. |
| Limits | Every size ceiling, by name, including the per-engine caps. |
| SQL dialect notes | What changes about your cube SQL per warehouse engine. |
The published artifact
| Page | What it holds |
|---|---|
| Runtime attributes | The data-dash roles and every data-* attribute the runtime reads. |
| Theme tokens | The --drt-* custom properties, their default values, and the colours that are not tokenized. |
| URLs, slugs and reserved names | Where a dashboard lives, what a slug may be, and which names are taken. |
When something goes wrong
| Page | What it holds |
|---|---|
| Errors | The publish finding envelope, the refresh failure classes, and the named refusals. |
The MCP surface
MCP tools is its own subsection: eighteen tool pages plus the protocol and the shared rules they all inherit.