Incident impact scope: six recorded examples
The downloads contain six original inputs, their expected labels and one recorded API observation per input revision. Disagreements stay visible.
Supply affected instances and services together with monitoring coverage. Distinguish a single-instance issue, one affected service and cross-service impact without inferring scope from severity alone.
The result summarizes supplied observations. It does not discover failing services or establish the cause of an incident.
Missing coverage matters: a log from one worker can coexist with an outage elsewhere. The Review outcome keeps that uncertainty visible.
The linked log-triage project asks about impact scope among several signals. This original demo isolates scope and leaves alerts, thresholds and execution to application policy.
This is an independently authored text demonstration inspired by the linked X discussion. Its rules and synthetic inputs are ours. It does not reproduce the author’s application, verify reported outcomes, or perform an external action.

Use the sample to understand the rule, then test your own input for incident impact scope.

Supply affected instances and services together with monitoring coverage.

Open the decision rules and keep the intended distinction between Single instance, One service, Multiple services, Review. 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 Review before using a result. The label is a decision about the supplied information, not an executed action.
| Original input | Observed label | Leading probability |
|---|---|---|
| Isolated worker | Single instance | 97.0% |
| Search service | One service | 89.0% |
| Two services | Multiple services | 91.0% |
| Only one log feed | Review | 70.0% |
| Dependency warning | Review | 98.0% |
| Conflicting checks | Review | 94.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.
# 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.The input contract and these limits define what the result means.
No. Severity and scope are separate. A severe failure can affect one instance, and a widespread symptom can appear in low-severity logs.
They support claims that impact is limited. Without coverage, the example returns Review rather than assuming the rest of the system is healthy.
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.