mobium verdict
This tool on every surface: CLI · MCP · Python · JavaScript · Go · Java · .NET
Give a verdict on a claim about a recording, held to the verifier's rules
Checks a verdict the way check checks its model's: passed or failed needs
evidence citing at least one call the recording holds, by id (call@3); at
most 12 observations; inconclusive when the recording cannot settle it.
Read the recording with recording first.
Usage
mobium verdict <claim> -i <recording.zip> --status passed|failed|inconclusive --summary TEXT --evidence TEXT... [flags]
Flags
| Flag | Type | Default | What it does |
|---|---|---|---|
--evidence | stringArray | One observation, citing its call (repeat, at most 12) | |
--input -i | string | The recording the claim was judged on | |
--status | string | passed, failed or inconclusive | |
--summary | string | The verdict in a sentence or two |
And the global flags.
Examples
Judge a claim yourself, citing the call it rests on
mobium verdict "After card 3 was tapped, it was shown face up as the Blue Morpho." --input card.zip --status passed --summary "Card 3 reads Blue Morpho after the tap" --evidence "call@7: the screen after the tap shows Card 3, Blue Morpho"
More, from mobium verdict --help
mobium verdict "the terms box was ticked" -i form.zip --status passed \
--summary "Accept terms is checked after the tap" \
--evidence "call@3: the screen shows Accept terms (checkbox, checked)"
No screenshot: it judges a recording, not a device, and needs no screen at all.
The tool
verdict calls app_verdict; its arguments and what every client calls it are there.