Jev calendar edit intent

Identify the calendar change a message requests

Give a scheduling message and whether the event already exists. Distinguish adding, modifying and removing an event from a request for information.

What edit does this scheduling message request?Live API
Try an example

Original input for the Add event outcome. Edit the evidence to send a new request.

Source: Background discussion on X

Source and example scope

These fictional inputs and decision rules were written for this page. The linked X discussion provides background; the technical implementation follows TypeSafe's Choice contract.

Classify the explicitly requested calendar operation.

Decision rules and labels
Add eventModify eventRemove eventNo edit requestedNeed evidence
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

Classify the edit before resolving event fields.

Rescheduling an existing event is a modification, not a new event, when the request explicitly preserves its identity. The read-only fixture asks for information and forbids a change.

This question does not select which existing event a vague reference means. It also does not calculate time zones, extract a date or confirm that a slot is available. Those fields need separate validation.

The source describes a computer-use calendar demonstration. These original messages expose one text decision only; no calendar window is opened and no event is created.

These fictional inputs and decision rules were written for this page. The linked X discussion provides background; the technical implementation follows TypeSafe's Choice contract.

Illustration of routing a message into one of several label groups
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 calendar edit intent.

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

    Add the information to check

    Give a scheduling message and whether the event already exists.

  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 Add event, Modify event, Remove event, No edit requested, Need evidence. 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 Need evidence 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
New meetingAdd event99.0%
Change existing titleModify event100%
Cancel eventRemove event100%
Read onlyNo edit requested99.0%
Reschedule remains modificationModify event100%
No scheduling messageNeed evidence100%

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

Source and example scope

Compare each saved result with its authored expectation. A disagreement remains in the fixture review; the call is not repeated to obtain a preferred label.

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.

Runnable offline example

Run one sample, then inspect the local packet

View the code example
Single-request replay
npm install @typesafe-ai/sdk@0.6.0
# Set TYPESAFE_API_KEY privately in your shell.
node run-choice-sample.mjs samples.json case-1
python preview_choice_workflow.py samples.json saved-api-results.json
Scope of this demo

Where this decision fits

Useful scope

  • Classifying a scheduling request before field handling
  • Separating a read-only question from an edit
  • Replaying the exact synthetic requests and inspecting their distributions

Outside this demonstration

  • Resolving an ambiguous event ID from missing history
  • Changing a calendar or computing time zones with this label
  • Treating six fixture expectations as measured production accuracy
Example FAQ

Questions about calendar edit intent.

The rubric explains the decision; the application owns the next step.

Does Modify event identify the event?

No. It describes the operation. The application must resolve the intended event and validate permissions before any edit.

Can Add event establish the meeting time?

No. Time extraction, normalization and availability checks are outside this question. Missing or ambiguous times must remain unresolved.

Does the leading probability measure production accuracy?

No. It is the model distribution for this one request. The six examples are functional checks with authored expectations, not a representative benchmark. Inspect disagreements and evaluate your own examples before using the label.

What happens when the API fails?

The window shows an error and supplies no fresh judgment. The downloadable runner sends one request without retries. Need evidence is a valid outcome about incomplete input; it does not stand in for a network or provider failure.

Try your own calendar edit intent input

Edit the evidence above or use the Playground to test another bounded question.