Claim reconciliation
Where does claim status come from, and what has it not reached?Reading the sample flag from the URL…
MonitorReconciliation
demoThis build is a demo. The catalog and detections are a fixed sample.Scopereading…Sound is used for one thing: a short tone when a long scan finishes while this tab is in the background. The A/B listening check plays audio either way, because there the sound is the evidence.Reading the sample flag from the URL…
MonitorReconciliation
demoThis build is a demo. The catalog and detections are a fixed sample.Scopereading…Sound is used for one thing: a short tone when a long scan finishes while this tab is in the background. The A/B listening check plays audio either way, because there the sound is the evidence.Reading the reconciliation history…
Reading the headline basis…
§13.13's match-rate breakdown cannot be rendered: two of its three groups have no field.
The worked example splits matched rows into matched to catalog, no ISRC — matched on title + artist and unmatched — no recording in scope. GET /api/monitor/reconciliation returns rows_read, rows_parsed and rows_matched and nothing else. The last two groups are not zero and not empty — there is no column they could be stored in, so nothing has ever been measured about them. §13.13 names the unmatched group as the one that matters, because those are claims the customer has that Choon cannot see.
import_claims, and a row with an ISRC but no video id is skipped rather than matched. Rendered rather than reconciled here: the endpoint’s rule is what a file has to satisfy, and which of the two should change is not this page’s call.