Worked case · Failure and stress · 12 figures

Signal semantics

Use signals with known meaning

Figure 01 / 12

The evaluated population

The evaluated population — Signal semantics. Count; one closed observation cohort. Exact values are in the figure data below.
Count; one closed observation cohort

The cohort contains 19,500 scored payment attempts, of which 429 have the defined synthetic outcome: Synthetic transaction fraud. The outcome is known by construction here. In production, label uncertainty and selection must be recorded separately.

Figure data and text version
OutcomeCount
Synthetic transaction fraud429
Other labeled outcomes19,071

A model consumes device, behavior, and transaction evidence from several producers. A syntactically valid value can still mean the wrong thing.

Missing device history is coerced into a measured zero.

All amounts, rates, capacity limits, and outcomes in this case are synthetic. The three conditions are separate assumptions for comparison. A better result in the response condition is not measured proof that the proposed control causes that improvement. The figures expose the calculation and its limits; a real deployment needs its own evidence.

Read the result

The rule flags 1,255 of 19,500 scored payment attempts. Of those flags, 206 meet the synthetic target, giving 16.41% precision. It misses 223 target events. Under the stated cost assumptions, residual loss and operating friction total $79,395. The important result is the connection between the population, action, capacity, and outcome—not one isolated score.

Model inputs and calculated values

Inputs below are the case-specific values. Each figure states the condition-specific assumptions and units used in its calculation. Calculated values are rounded for display.

InputValue
population19,500
prevalence0.022
severity310
reviewCost4
Calculated valueResult
population19,500
positive429
negative19,071
tp206
fp1,049
fn223
tn18,022
loss69,130
severity310
precision16.41
recall48.02
Figure 02 / 12

Four outcomes of the rule

Four outcomes of the rule — Signal semantics. Counts; rows are actual labels, columns are actions. Exact values are in the figure data below.
Counts; rows are actual labels, columns are actions

The rule flags 206 synthetic positives and 1,049 negatives. It misses 223 positives. A flagged item is a decision to intervene; it is not proof of fraud, a legal prohibition, or any other real-world conclusion.

Figure data and text version
Known outcomeFlaggedNot flagged
Synthetic transaction fraud206223
Other outcome1,04918,022
Figure 03 / 12

Three rates with different denominators

Three rates with different denominators — Signal semantics. Rates within this cohort. Exact values are in the figure data below.
Rates within this cohort

Precision is 16.41%, recall is 48.02%, and the false-positive rate is 5.5%. Changing the denominator changes the meaning. This record keeps each numerator attached to the population from which it came.

Figure data and text version
MetricNumeratorDenominatorResult
Precision2061,25516.41%
Recall20642948.02%
False-positive rate1,04919,0715.5%
Figure 04 / 12

Precision changes with prevalence

Precision changes with prevalence — Signal semantics. Percent; fixed conditional detection rates. Exact values are in the figure data below.
Percent; fixed conditional detection rates

This sensitivity plot holds recall at 48% and false-positive rate at 5.5%, then changes prevalence. It is an algebraic comparison, not a forecast. Even unchanged detection quality can produce a very different review queue when the base rate changes. Horizontal positions are the labeled observations or scenarios; equal spacing does not imply equal numerical increments.

Figure data and text version
Assumed prevalencePrecision %
0.1%0.87
0.5%4.2
1%8.1
2%15.12
5%31.48
10%49.23
Figure 05 / 12

The threshold trade-off

The threshold trade-off — Signal semantics. Count in the same cohort. Exact values are in the figure data below.
Count in the same cohort

Six illustrative score bands use a stated pair of detection rates. Lower sensitivity can reduce false alarms but miss more target events. These points do not come from a trained model and do not establish the best operating threshold. Horizontal positions are the labeled observations or scenarios; equal spacing does not imply equal numerical increments.

Figure data and text version
Score bandTrue positivesFalse positives
Band 14202,861
Band 24031,526
Band 3369667
Band 4309229
Band 521476
Band 610719
Figure 06 / 12

A transparent loss-and-friction calculation

A transparent loss-and-friction calculation — Signal semantics. Illustrative USD; expected cost under stated intervention assumptions. Exact values are in the figure data below.
Illustrative USD; expected cost under stated intervention assumptions

At $310 severity per missed synthetic positive, residual loss is $69,130. Review costs $5,020; lost contribution on false alarms is $5,245. The calculation assumes intervention prevents all flagged-positive loss and each false alarm loses the stated contribution. Relax those assumptions before applying it to a real policy.

Figure data and text version
Cost componentUSD
Missed-positive loss69,130
Review cost5,020
False-alarm contribution5,245
Figure 07 / 12

Observed outcomes mature over time

Observed outcomes mature over time — Signal semantics. Count; final outcome fixed. Exact values are in the figure data below.
Count; final outcome fixed

The final synthetic positive count is 429. Earlier observations reveal only a stated fraction. Comparing a day-1 cohort with a day-30 cohort would confuse label age with control quality. This curve models observation delay only; it does not change the final outcome. Horizontal positions are the labeled observations or scenarios; equal spacing does not imply equal numerical increments.

Figure data and text version
Days after eventObserved positives
177
3150
7257
14352
30429
Figure 08 / 12

Review demand and available capacity

Review demand and available capacity — Signal semantics. Items in the cohort window. Exact values are in the figure data below.
Items in the cohort window

The flag count is 1,255. The comparison capacity is an illustrative 780 reviews per cohort window. A mathematical rule can be coherent while its resulting workload exceeds the operating team’s capacity. Capacity is not permission to ignore an applicable mandatory control.

Figure data and text version
Queue measureItems
Flagged for review1,255
Available capacity780
Excess demand475
Figure 09 / 12

A feature is an observation with provenance

A feature is an observation with provenance — Signal semantics. Illustrative data contract. Exact values are in the figure data below.
Illustrative data contract

This evidence contract supports use signals with known meaning. A value needs its event time, arrival time, scope, and source. Keeping unavailable evidence distinct from a measured zero prevents an outage from becoming a falsely reassuring feature.

Figure data and text version
FieldExampleMeaning
entity_refSignal semanticsSubject of this case
event_time2026-09-18T09:00:00ZWhen the event occurred
received_time2026-09-18T09:00:02ZWhen the system learned it
signal_statuslateEvidence quality, not an outcome
label_definitionSynthetic transaction fraudThe target used in these calculations
Figure 10 / 12

Missing evidence changes the observed population

Missing evidence changes the observed population — Signal semantics. Count; each row is the same cohort. Exact values are in the figure data below.
Count; each row is the same cohort

The cells show an explicitly constructed completeness profile for three signal groups. The stress condition removes more history and device evidence. Missingness does not prove the target outcome; it changes what the decision process knows.

Figure data and text version
Signal groupAvailableMissing
Identity evidence17,1602,340
Activity history14,0405,460
Context signal11,7007,800
Figure 11 / 12

Evidence, score, and action remain separate

Evidence, score, and action remain separate — Signal semantics. Decision lifecycle. Exact values are in the figure data below.
Decision lifecycle

The policy can use use signals with known meaning only within its approved scope. The action record must retain which evidence was available, which model or rule ran, and which action was actually applied. The final action can differ from the score recommendation when a separate constraint applies.

Figure data and text version
StageRecord
ObserveSignal semantics: evidence as of the decision time
EvaluateRule flags 1,255 of 19,500 scored payment attempts
ApplyRecord action, reason, owner, and expiry
ReconcileJoin the action to later outcomes without overwriting history
Figure 12 / 12

What the result cannot establish

What the result cannot establish — Signal semantics. Interpretation boundary. Exact values are in the figure data below.
Interpretation boundary

Observed classifications do not reveal every counterfactual. The synthetic labels make arithmetic possible, but production decline data is selected by prior policy. Keep measured outcomes, assumed prevention, and unknown alternatives separate when reporting impact.

Figure data and text version
ClaimEvidence in this caseLimit
Detected target206 known synthetic positives flaggedProduction labels may be delayed or wrong
Prevented lossAssumed 63,860 USDRequires an intervention-effect assumption
Customer impact1049 synthetic negatives flaggedNot every flag causes abandonment
Unobserved alternativeOutcome without the actionNeeds a valid evaluation design

Connect the result to the system

Preserve missingness and versioned feature definitions, then evaluate the action-level impact.

Check the population, evidence, permitted action, and actual effect together. A balanced calculation can still use the wrong population; a successful response can still leave an unknown financial outcome. The case’s numerical result applies only to its stated assumptions.

Sources and further reading

The chapter sources support the concepts and scope. They do not prescribe the synthetic model rates.

  1. NIST: AI Risk Management Framework
  2. Stripe: PaymentIntent lifecycle (provider example)