Prompt
"Revenue by store last month"
page:use cases
tracks:3
scope:shipped code
Govern your data, rather than constraining it.
Authoring governed packages, putting an agent or UI in front of the API, and debugging why the planner picked the path it did. Check out the workflows below.
Author graph-first packages without flattening the semantic model.
For teams moving from ad hoc metrics files or SQL-first marts toward explicit semantic packages with entities, model-level measures, time roles, and thin curated metric layers.
- Directory packages:
package.yml,graph.yml,models/**,metrics/**. - Measures live close to the tables that own their grain.
- Keep derived metrics thin so the planner has strong primitives.
package.yml
->
graph.yml
->
models/
->
metrics/
| Authoring concern | Runtime support | Why it matters |
|---|---|---|
| Graph-first identity | Strongly supported | Stable roots and safe traversal policy |
| Historical joins | Supported with guardrails | Preserve semantic meaning across validity windows |
| Clock variants and comparison families | Demonstrated in the active package | Helps callers compare ordered versus delivered or peer metrics cleanly |
Build agent and UI query flows on top of the same public API.
A guided builder path for internal apps, exploration tools, and LLM agents — without turning each caller into a mini planner. Same surface for HTTP/JSON and MCP.
- Start from business language:
capabilitiesfor orientation, thendiscoverfor object matches. - Inspect stable object cards before suggesting dimensions, values, or clocks.
build-optionsandvalid-valueskeep the next move legal.
Discovery
discover ranks candidate metrics, measures, and dimensions.
Builder
build-options returns recommended patches and blocked alternatives.
Execution
validate, compile, and execute finalize the flow; compile includes the explain payload.
Debug semantic behavior with concrete planner artifacts.
When the problem is not just returning rows but understanding why a query was legal, illegal, rewritten, or blocked.
inspect— semantic provenance and starter query patches.compile’s explain payload — chosen paths, rewrites, rendered SQL.- Anchor product discussions in inspectable planner output, not screenshots.
Inspect
Check object summaries, clocks, comparison metadata, and recommended next actions.
Explain
Trace alias resolution, path selection, rewrite strategy, and SQL lowering.
Compare
Use the semantic-layer comparison pack to show where native support stops and workarounds begin.