Getting started

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

This local beta evaluates reported states. It does not connect to a live device, establish physical ground truth or certify safety.

Use the recording workspace without signing in. Files stay in the browser tab: they are not uploaded and do not consume verification credits. This is separate from the hosted browser workflow.

Open recorded evidence.

Start with a simulated example

1. Open Explore simulated examples and select Broken handoff, Corrected handoff or Missing device evidence.
2. Review the asset, task, completion deadline and any assets that must stay unchanged.
3. Read the declared recording coverage and confirm that you reviewed it. Select Verify recording.
4. Inspect the findings and cited source events. Missing coverage produces an inconclusive result rather than a pass.

Supported input

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. This beta does not save cloud history. Export before closing the tab.

JSON format example

This is simulated data from the corrected handoff example. Download format example in the workspace for the same supported shape.

{
  "schemaVersion": 1,
  "runId": "simulation-corrected",
  "buildId": "sim-build-002",
  "clock": "unix-ms",
  "window": {
    "startMs": 1791194400000,
    "endMs": 1791194412000
  },
  "coverage": [
    {
      "source": "control",
      "startMs": 1791194400000,
      "endMs": 1791194412000
    },
    {
      "source": "service",
      "startMs": 1791194400000,
      "endMs": 1791194412000
    },
    {
      "source": "device",
      "startMs": 1791194400000,
      "endMs": 1791194412000
    }
  ],
  "events": [
    {
      "id": "b-baseline",
      "timeMs": 1791194400000,
      "source": "device",
      "assetId": "Robot B",
      "taskId": "standby-b",
      "state": "idle"
    },
    {
      "id": "requested",
      "timeMs": 1791194401000,
      "source": "control",
      "assetId": "Robot A",
      "taskId": "task-104",
      "state": "requested"
    },
    {
      "id": "accepted",
      "timeMs": 1791194401200,
      "source": "service",
      "assetId": "Robot A",
      "taskId": "task-104",
      "state": "accepted"
    },
    {
      "id": "ui-completed",
      "timeMs": 1791194406500,
      "source": "control",
      "assetId": "Robot A",
      "taskId": "task-104",
      "state": "completed"
    },
    {
      "id": "b-final",
      "timeMs": 1791194411000,
      "source": "device",
      "assetId": "Robot B",
      "taskId": "standby-b",
      "state": "idle"
    },
    {
      "id": "device-completed",
      "timeMs": 1791194406000,
      "source": "device",
      "assetId": "Robot A",
      "taskId": "task-104",
      "state": "completed"
    }
  ]
}

Related

• Getting started with Vraelis →
• Verify, approve, run, re-check →