Jev meeting decision presence

Check whether meeting notes record a decision

Read a meeting excerpt to distinguish an adopted decision from a proposal, a deferred choice or a discussion with no decision topic. Keep unresolved context separate from an actual resolution.

Does this excerpt record an actual decision?Live API
Try an example

Original input for the Decision recorded 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.

Read the stated status of the discussed issue.

Decision rules and labels
Decision recordedProposal onlyDecision deferredNo decision topicNeed 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

A suggestion is not an adopted decision.

The proposal fixture names an option without an acceptance statement. Calling it a decision would add a commitment the notes do not contain. Decision deferred preserves an explicit postponement.

An adopted alternative can follow a rejected proposal. The fifth sample records the final CSV resolution, so the earlier rejected XML suggestion does not make the excerpt unresolved.

The source proposes checking meeting notes before summarization. This adaptation labels the supplied excerpt; it does not attend a meeting, infer consensus from silence or write minutes.

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 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 decisions in meeting notes.

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

    Add the information to check

    Read a meeting excerpt to distinguish an adopted decision from a proposal, a deferred choice or a discussion with no decision topic.

  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 Decision recorded, Proposal only, Decision deferred, No decision topic, 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
Accepted formatDecision recorded100%
Suggested formatProposal only100%
Choice postponedDecision deferred100%
Status reportNo decision topic96.0%
Rejected proposal, accepted alternativeDecision recorded100%
No excerptNeed 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

  • Checking proposal versus resolution wording
  • Avoiding invented commitments in meeting summaries
  • Replaying the exact synthetic requests and inspecting their distributions

Outside this demonstration

  • Inferring consensus from silence or omitted minutes
  • Creating assignments or commitments automatically
  • Treating six fixture expectations as measured production accuracy
Example FAQ

Questions about meeting decision presence.

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

Does an action verb prove a decision was made?

No. A suggestion can describe an action without adopting it. The excerpt needs wording that establishes a resolution.

What if different issues have different statuses?

Review one named issue at a time or use multiple questions. This one-label fixture assumes one primary issue and should not erase other decisions.

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 meeting decision presence input

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