Jev executive participation evidence

Check whether a senior customer actively participated

Supply the senior-role policy and complete activity record. Distinguish a direct contribution from being mentioned, copied or merely present.

executive participation evidenceLive API
Try an example

The qualifying person directly contributes.

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.

Using the senior-role policy and complete activity record: Active if an identified qualifying customer directly contributes; otherwise Mentioned if one is named, copied or listed without contributing; otherwise None only when the complete record has no qualifying senior person, even by mention.

Decision rules and labels
ActiveMentionedNoneUnclear
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

The decision uses two different facts: whether the person meets your role policy and whether the activity records a direct contribution. A copied executive and a speaking analyst each satisfy only one side.

Active does not establish budget authority, enthusiasm or a purchase commitment. It says only that the stated event contains participation by a person who meets the supplied policy.

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 executive participation.

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

    Add the information to check

    Supply the senior-role policy and complete activity record.

  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 Active, Mentioned, None, Unclear. 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 Unclear 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
Direct decisionActive100%
Copied recipientMentioned100%
Attendance onlyMentioned100%
Analyst feedbackNone97.0%
Role unknownUnclear98.0%
Policy unknownUnclear79.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

Executive participation: 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.

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

  • Reviewing activity notes before an account meeting
  • Separating attendee lists from observed contributions
  • Making missing role evidence visible

Outside this demonstration

  • Verifying organizational authority externally
  • Scoring a person or predicting purchase behavior
  • Inferring unrecorded speech or decisions
Example FAQ

Using this example

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

Does a meeting invitation count?

A listing without a recorded contribution returns Mentioned. This policy is about observed activity, not invitations or presumed attendance.

Can my policy include directors?

Yes. Put that definition in the input and retest examples. The page does not impose a universal seniority hierarchy.

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.