Published Payloads

Threshold-gaming payment request. A quarterly invoice that is immaculate in isolation. The signal is in the invoice history: a mid-year step-change followed by three consecutive invoices clustered just below the dual-approval threshold. No single invoice violates policy. The pattern across the history does. All three solo frontier models approved. Holo escalated.

Fraudulent payment routing update. A clean invoice from an established vendor. All payment signals pass. The threat is embedded as a casual aside: a request to add a billing contact on an adjacent unverified domain registered 12 days prior. Solo GPT approved. Solo Claude and Gemini escalated. Holo escalated.

Contract boundary billing — scope creep in plausible language. A professional services invoice from an established vendor with all payment signals clean. Two line items bill for work outside the contracted SOW deliverables, described in language that reads as routine implementation work. The anomaly only exists in the relationship between the invoice line items and the active agreement deliverables list. Solo Claude approved. Solo GPT and Gemini escalated. Holo escalated.

Threshold-evasion across invoice history. A routine quarterly invoice — correct account, correct routing, amount within stated range. The fraud is not in the invoice. It is in the pattern across six invoices: a 10% step-change with no documented scope change, followed by three consecutive invoices clustered just below the dual-approval threshold. No single field is wrong. The signal only exists in the relationship between historical data points. Solo GPT and Claude approved. Solo Gemini and Holo escalated.