Which scenario, at which threshold. Live.

Every figure on this page comes from the sealed public record of cascade-monitoring: cases the repository wrote itself, benign look-alikes included, measured by its own scenarios. No client data exists here, nothing enters and nothing leaves, and the page checks its own arithmetic before your eyes.

cascade monitoring · the public record, live

$ cascade screen --live

Pick a cell: each shows recall on confirmed suspicious cases over false alerts on benign look-alikes, at that scenario and threshold
scenario \ threshold	0.50	0.60	0.70	0.80	0.85	0.90	0.95	1.00
amount
velocity
structuring
round
zscore
passthrough
peer

pick a cell: recall over false alerts, with n and its 95 % interval

$ cascade optimise --recall

$ cascade verify --sealed

checking…

What this rests on

The sealed public record. releve-public.json in the repository, fingerprint 692d499018e53e07, measured at commit 2fa9f51 on 2026-09-05. The extractor that feeds this page verifies the seal, then recomposes witness cells with the tool’s own interval code, and refuses to emit if a single figure disagrees.
Cases the repository wrote. The labelled half is authored: archetypes of suspicion (structuring, rapid movement, a dormant account that wakes, round-tripping) and benign look-alikes (payroll, seasonal trade, loan repayments) that resemble them. The labels ship with the cases, debatable ones with their reasons.
Synthetic variants, kept apart. Generated from the written cases, nature by nature, and never merged with the authored half: the toggle above switches the whole grid, it never blends.
The tool’s selection rule. The slider holds your recall floor at the Wilson lower bound, exactly as npm run optimise does: a point estimate never clears a floor here.

What this refuses

Your data. This page cannot read it: no network requests leave it (connect-src ‘none’), no third-party resource is loaded, and there is no input field to paste a name into.
Bare rates. Every cell carries its n and its 95 % interval; every scenario of the registry is present tonight; an absent one would be a named row, never a guessed column.

Measure your own alert history

The instrument shows our record. Yours is measured at home, by the tool, and nothing about your file leaves your machine.

The three commands, exactly as they run

$ git clone https://github.com/ArslaneSempai-ui/cascade-monitoring.git

$ npm ci --ignore-scripts

$ npm run measure:yours -- --alerts=your-alerts.csv --transactions=your-transactions.csv

the report and the sealed record are written next to your file, and nowhere else