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.
Supply the senior-role policy and complete activity record. Distinguish a direct contribution from being mentioned, copied or merely present.
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.

Use the sample to understand the rule, then test your own input for executive participation.

Supply the senior-role policy and complete activity record.

Open the decision rules and keep the intended distinction between Active, Mentioned, None, Unclear. Edit the choices only when testing your own rule.

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

Review Unclear before using a result. The label is a decision about the supplied information, not an executed action.
| Original input | Observed label | Leading probability |
|---|---|---|
| Direct decision | Active | 100% |
| Copied recipient | Mentioned | 100% |
| Attendance only | Mentioned | 100% |
| Analyst feedback | None | 97.0% |
| Role unknown | Unclear | 98.0% |
| Policy unknown | Unclear | 79.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
The downloads contain six original inputs, their expected labels and one recorded API observation per input revision. Disagreements stay visible.
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.
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.jsonThe input contract and these limits define what the result means.
A listing without a recorded contribution returns Mentioned. This policy is about observed activity, not invitations or presumed attendance.
Yes. Put that definition in the input and retest examples. The page does not impose a universal seniority hierarchy.
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.
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.
Edit the example above to see how a changed fact affects the decision, or open the Playground for another task.