Documentation / THOR Data
10 / 22
From brief to verified unit
THOR Data turns a robotics brief into output that a buyer can trace and use.
Before production begins, THOR defines the source material, annotation schema, delivery format and acceptance tests. Contributors complete the task, validators score the result, and accepted work becomes a verified unit with its provenance and judgement attached.
- 1 / The task
A clear piece of work
Contributors receive a clip, a published specification and a validator. Scores determine whether the work is accepted and how it is rewarded.
Annotate the action across time
- 2 / The verified unit
Accepted work becomes a unit
The source, specification, annotation, validation result, provenance and value stay together so the work can be reviewed later.
- Status Unit record
- Verified
- Source
- video_00423.mp4
- Annotation
- open drawer
- Validation
- passed
- Provenance
- worker + task
- 3 / The verification layer
Good judgement can be reused
Repeated tasks and validated judgements improve the checks used by future work, creating a reusable quality layer.
- Better evaluation
- Stronger signals
- Reusable judgement
Individual tasks create reusable verification infrastructure
Each verified unit records what was requested, who produced it, how it was checked and whether it passed, so every delivery traces back to the original brief.