Each industry below has one candidate judgement written out. Only one is worked through in full. The rest are sketches. The point of listing them is that the shape repeats.
Is this inbound fault report caused by the network, rather than billing or the customer's own device?
32 judgements inventoried across the fault workflow. Only six to eight turn out to be genuine System One tasks, and the specification says so rather than inflating the count.
Can this motor claim be settled without sending an assessor?
High volume, a fixed answer set, and a cost asymmetry that is easy to price: an unnecessary inspection costs a known amount, a missed one costs a great deal more.
Is this denied claim worth appealing, and what is it likely to recover?
Judgement was rationed here because appeals cost staff minutes, so teams work the queue in the order it arrived rather than by what each case is worth.
Does this alert warrant a human review, or is it the pattern we have cleared a thousand times?
A very low base rate, which is exactly where accuracy misleads and calibration decides whether anything can be automated at all.
Does this supplier bid meet the mandatory criteria of the tender?
A closed answer set, documents that already exist, and a decision currently made by reading every submission in full.
Is this shipment going to miss its window, early enough that someone can still act?
The judgement is cheap. The bottleneck moves immediately to physical execution, which no model accelerates.
What kind of clause is this, and does it deviate from our standard position?
Around 100 clause types, long inputs, and a public dataset (LEDGAR) that makes it testable before any client is involved.
Pick one, then say where you think the bottleneck would sit. Your choice appears on your dashboard.