- Who it helps
- Data teams with a warehouse and someone responsible for metric definitions.
- Availability
- The Apache 2.0 repository is public. It requires an agent host, warehouse access and a domain expert; model and warehouse charges can still apply.
Make ambiguity explicit
A metric can have several plausible definitions. Nodal records confirmed meanings, filters and join rules in Markdown and YAML, then asks for a plan before generating SQL.
Use a controlled fixture
The linked Shorelane warehouse is fictional and deliberately contains ambiguous revenue measures. It is maintained by Nodal, so it is a useful test fixture without constituting independent validation.
Nodal Analytics: agree on business definitions before SQL ↗Shorelane synthetic analytics fixture ↗
What you can do
- Review a single metric and its exclusions with the domain owner before allowing broader analytics tasks. Open reference ↗
Where the evidence stops
No warehouse query was executed. The agent provider can process material it reads; local context files alone do not establish an entirely local workflow.
Sources read. Sources checked October 28, 2026. No installation, model inference or end-to-end workflow was executed.
Sources & further reading
GitHub · official
Nodal Analytics: agree on business definitions before SQL ↗
Establishes the subject, discovery context or stated verification limit.
Nodal Data · page checked 2026-10-28
GitHub · implementation
Shorelane synthetic analytics fixture ↗
Establishes the subject, discovery context or stated verification limit.
Nodal Data · page checked 2026-10-28
Coverage note: No qualifying current independent attention sample; original X posts unavailable. Reported outcomes were not independently reproduced.
The record over time (1)
Dated source checks and published explanations. An observation date can differ from the original release date.
- · Added to Current
Nodal Analytics interviews a domain expert to build reviewable business context for analytics agents.