Review recorded task reports
Compare supplied control-panel, service and device reports for one task. Inspect disagreements, missing evidence and changes to another asset.
- Outcome
- You have evaluated a supplied recording against reviewed criteria and inspected the source events.
- Does not do
- The private evaluator evaluates reported states. It does not connect to a live device, establish physical ground truth or certify safety.
This reference describes the recorded-evidence component in private development. Public workspace access is closed. The component compares supplied events with reviewed criteria; it does not run a live investigation or protect a device.
Evaluation sequence
- Supply a supported recording and review its asset, task and capture identity.
- Define the required events, deadline and any assets that must remain unchanged.
- Review declared coverage before evaluating the supplied reports.
- Inspect findings and their cited source events. Insufficient coverage remains inconclusive.
Supported input
| Format | Current support |
|---|---|
| JSON | Normalized version 1 recordings, up to 1 MB and 2,000 events. Each event names its source, asset, task, timestamp and supported state. |
| MCAP | Uncompressed files up to 5 MB, with flat JSON task-event messages. Map each supported topic to control, service or device, then supply a capture manifest. |
| Not supported | ROS CDR, LZ4 or Zstandard compression, arbitrary nested message schemas, sensor interpretation and live device streams. |
For MCAP, event time comes from the payload’s timeMs field, not the container timestamp. Review run and build identity, topic mapping, clock and captured intervals before evaluation. Declared coverage describes the supplied recording; it is not proof that a device’s report is authentic.
What the result means
- Passed: the supplied reports meet the reviewed criteria, within the declared capture window.
- Failed: a required event is absent from declared full coverage, arrives too late, reports a contradictory state or changes an asset that should remain unchanged.
- Inconclusive: the required identity, baseline, source event or capture coverage is insufficient to establish the result.
Compare a change
Keep an evaluated result as the baseline, load the next recording and use the same reviewed criteria. The comparison shows changed findings. Changing a requirement changes the question; it does not demonstrate that a repair succeeded.
Export and persistence
Export the evidence to keep the criteria, evaluator version, findings and source references. Source hashes identify the supplied bytes; they do not authenticate a device. The component does not save cloud history. Export before closing the tab.