Jev search time window

Map a freshness request to a supported search window

Describe the requested recency to choose day, week, month or anytime. Keep unsupported exact windows and conflicting constraints separate instead of silently rounding them to a different period.

search time windowLive API
Try an example

The requested interval matches a supported window.

Source: API-collected workflow inspiration; original demonstration below

Source and example scope

This original text demonstration adapts a decision in a repository linked by the cited X post. The examples and explicit uncertainty outcomes are ours. The post is a directory reference, not proof that its author built every linked project. No third-party benchmark, business outcome or external action is reproduced.

Choose the requested search window: Day for the last 24 hours; Week for the past seven days; Month for the past month; Anytime for no recency constraint or an explicit any-time request.

Decision rules and labels
DayWeekMonthAnytimeUnsupported
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 query can contain dates for different reasons. Searching about an old event does not necessarily mean searching for pages published during that event. The input must make the intended freshness requirement clear.

This label only prepares a search parameter. The application must check that the selected search provider supports it and validate the dates of returned results. No search runs in this example.

This original text demonstration adapts a decision in a repository linked by the cited X post. The examples and explicit uncertainty outcomes are ours. The post is a directory reference, not proof that its author built every linked project. No third-party benchmark, business outcome or external action is reproduced.

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 search recency windows.

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

    Add the information to check

    Describe the requested recency to choose day, week, month or anytime.

  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 Day, Week, Month, Anytime, Unsupported. 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 uncertain or unexpected results 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
Last dayDay100%
Weekly updateWeek100%
Monthly readingMonth100%
Historical subjectAnytime100%
Exact two daysUnsupported99.0%
No requestUnsupported97.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

Search recency windows: 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

  • Interpreting explicit freshness preferences
  • Separating topic dates from publication windows
  • Detecting unsupported search intervals

Outside this demonstration

  • Fetching or validating search results
  • Exact date arithmetic
  • Claiming every provider supports each window
Example FAQ

Using this example

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

What does latest mean without a defined interval?

Clarify the desired period or define a policy before using it. The fixed window menu should not silently promise an interval the user did not specify.

Will this ensure all results are recent?

No. The output is only a proposed parameter. The provider and result-date checks determine what is actually returned.

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.