Jev analytics question clarity

Find missing definitions in an analytics question

Supply the question, schema and known business definitions. Check whether the metric, population and relevant comparison are clear before anyone calculates an answer.

analytics question clarityLive API
Try an example

Spending, order count and recency could select different customers.

Source: API-collected workflow inspiration; original demonstration below

Source and example scope

This original question-review exercise adapts the clarity check in the linked Natural Language Data Analyst Agent. Schemas, questions and labels are authored examples. The demo neither queries a database nor chooses business metrics on the user’s behalf.

Using the complete supplied schema and known policies, choose Ready if the question has a defined metric, population, period and comparison where relevant.

Decision rules and labels
ReadyClarifyNeedSchema
A real response from the Jev API

Edit any input to explore a different decision. No request is sent until you run it.

Your next decision

Not run yet

Choose an example or write your own input, then run it to see the ranked choices.

Results are not stored by this site. Your submitted text is processed by the API provider.

The decision

What the decision checks

A question can be grammatically clear but analytically incomplete. Terms such as active, best or improved can refer to several calculations unless the question or an existing policy defines them.

Ready concerns interpretability from supplied data definitions. It does not mean the query has run, the data is complete, or the requested business decision is appropriate.

This original question-review exercise adapts the clarity check in the linked Natural Language Data Analyst Agent. Schemas, questions and labels are authored examples. The demo neither queries a database nor chooses business metrics on the user’s behalf.

Illustration of one spreadsheet row producing two separate classification results
Illustration of the decision flow.
How it works

Try the example in four steps

Use the sample to understand the rule, then test your own input for analytics question clarity.

  1. Illustration of adding the text or evidence for a decision

    Add the information to check

    Supply the question, schema and known business definitions.

  2. Illustration of defining a question and its allowed choices

    Confirm the question and labels

    Open the decision rules and keep the intended distinction between Ready, Clarify, NeedSchema. Edit the choices only when testing your own rule.

  3. Illustration of sending one input and comparing the returned choices

    Run the decision

    Use a sample first, then try your own input. Compare the selected label with the other returned probabilities.

  4. Illustration of reviewing a result and an uncertain item before using it

    Review the next step

    Review NeedSchema before using a result. The label is a decision about the supplied information, not an executed action.

Our API test

Recorded API observations

Recorded API observations
Original inputObserved labelLeading probability
Best is undefinedClarify100%
Metric and period suppliedReady90.0%
All-time requestReady95.0%
Active lacks policyClarify99.0%
Comparison absentClarify100%
Schema missingNeedSchema89.0%

These are six original synthetic inputs, tested once per request revision. The percentage is the leading option probability, not measured accuracy. Authored expectations and any disagreements remain in the downloadable evidence. 6 of 6 results matched the authored fixture expectations.Verified

Understand the results

Analytics question clarity: six recorded examples

The downloads contain six original inputs, their expected labels and one recorded API observation per input revision. Disagreements stay visible.

Using the result in your application

The single-request SDK runner uses your private TYPESAFE_API_KEY. The offline consumer reads saved observations, checks request hashes and prints a pending output. It does not call the model or change any external system.

Replay options

Inspect saved outputs or request a new decision

View the code example
Two independent commands
# Offline: inspect the downloaded saved observations. No API key is needed.
python preview_choice_workflow.py samples.json saved-api-results.json

# Optional live request: install the SDK and set TYPESAFE_API_KEY privately.
npm install @typesafe-ai/sdk@0.6.0
node run-choice-sample.mjs samples.json case-1
# The live response prints to the terminal; it does not update saved-api-results.json.
Scope of this demo

Where this decision fits

Useful scope

  • Reviewing questions before text-to-SQL
  • Making metric definitions explicit
  • Preserving all-time and policy-defined requests

Outside this demonstration

  • Choosing business priorities
  • Calculating results
  • Guessing hidden schema relationships
Example FAQ

Using this example

The input contract and these limits define what the result means.

Must every question specify a date range?

No. An all-time count or a task unrelated to time can already be complete. The question needs only the definitions that materially affect its answer.

Does Clarify generate a follow-up question?

No. It returns a label. A separate interface can present the missing definition and ask the user for it.

Does the leading probability measure accuracy?

It describes the distribution over the supplied choices for this request. These six synthetic examples are functional tests with authored expectations, not a production accuracy benchmark.

Will a result change an external system?

No. The demo displays a label and distribution. The downloadable consumer produces a pending preview packet. Application code and a separate authorization policy would control any real action.

Test a different input

Edit the example above to see how a changed fact affects the decision, or open the Playground for another task.