Research · Work in progress
Interpretation before execution. A technical note in preparation.
We are documenting why business questions need an explicit interpretation layer between natural language and execution. This page states the intended scope—and the current publication boundary—without presenting unfinished work as evidence.
Publication status
The scope is public. The final paper is not.
We are keeping this page available for evaluators while the technical note is in preparation.
Current state
Research note in preparation
No download is gated behind this page, and no final publication date is promised. Product evaluation remains available through the proof journey.
Planned chapters
Six parts of the interpretation problem.
The note follows the path from an underspecified question to an inspectable analysis and its supporting evidence.
01
Why the question is not the specification
Business language leaves choices about definitions, scope, grain, filters, and comparison periods. The note starts with that semantic gap rather than with SQL generation.
02
How analysts compose an answer
Analysts connect familiar concepts, calculations, segments, and analysis patterns. The note makes those intermediate choices explicit.
03
What an analytical plan represents
A visible plan is a review surface for selected meaning. It helps a person inspect the intended analysis before execution without pretending to prove correctness.
04
How context contributes
Models, metadata, team-supplied definitions, reusable patterns, and prior artifacts can inform a plan when their origin remains visible.
05
Where clarification belongs
If a missing business choice materially changes the analysis, the system can ask instead of silently selecting a convenient interpretation.
06
What evidence should accompany an answer
The evaluation surface includes the plan, human interventions, generated logic or SQL, sources, and result artifacts—not a confidence label alone.
Current boundaries
A research page should not overstate the evidence.
The final paper is not published yet.
This route describes the scope of the work in progress. It does not present a downloadable paper as if it were complete.
A visible plan is not a correctness guarantee.
Interpretability creates a review point. It does not remove the need to inspect source permissions, logic, results, and environment-specific behavior.
Product behavior must be tested directly.
No benchmark, deterministic output, or customer outcome is implied here. Those claims require dated, reproducible evidence.
Read the implemented product path
Continue with the mechanism, context, and evaluation method.
Mechanism
Intent Algebra
See how the analytical plan represents selected meaning before execution.
Context
Context Graph
Review the types of context used to ground business concepts and reusable patterns.
Evaluation
Evidence journey
Compare the current path with Spotonix using the same questions and recorded interventions.
Evaluate directly
Evaluate the thesis before the paper is finished.
Bring representative questions and a real model. We will show the plan, clarifications, generated logic, sources, and result artifacts so your team can test the product behavior directly.
Book DemoSee how it works