The beta
The beta.
Start with supported task recordings. Compare control-panel, service and device reports, inspect the source events, and see where the supplied evidence falls short.
The work
What you can work with today.
The recording beta is a local report-review workflow. The website’s mission-console example is a separate simulation, not an operational defense system.
Supported JSON and MCAP
Import recordings that match the documented formats. Files remain in your browser; the recording workflow does not upload them to a cloud evidence store.
Task and asset comparisons
Look for conflicting state, missing completion and unexpected changes to assets required to stay unchanged. Findings refer back to supplied events.
An explicitly simulated case
Explore the homepage mission-console example or the simulated robot reports. These examples demonstrate software behavior and are not customer deployment evidence.
Current recorded-report workflow
One task. Every available report.
Define the intended asset, completion window and assets that must stay unchanged. Compare the captured reports against that requirement, then inspect the source events.
01 / Define the requirement
- Intended asset
- Robot A
- Task
- task-104
- Completion window
- 10 seconds
- Keep unchanged
- Robot B
02 / Bring the captured reports
- Control panelRequested and displayed state
- Task serviceAccepted and reported state
- Device reportRecorded device state
03 / Compare against the requirement
Same task. Intended asset. Declared coverage.Check source events on a shared timestamp basis, within the captured intervals.
Reports describe recorded state. They do not establish physical ground truth. Live device connections are not available.
What comes next
Help shape the next release.
Bring a concrete failure, a representative recording and the evidence an engineer would need to decide what happened.
Start with a reproducible problem
Share the format and behavior you need supported. Use synthetic or permitted test material and describe the expected outcome.
Measure useful findings
Compare the result against engineer-reviewed failures. Track missed cases, false positives and incomplete evidence before broadening the scope.
Keep unfinished work visible
Live device connections, physical ground truth, automatic hardware repair and certified safety judgments are not current beta capabilities.