# Robotics task-coverage brief

Version: 1.0.0. Updated: 2026-11-10. Maintainer: Avala Solutions Engineering. Language: English.

Blank planning template, not a completed collection, inventory statement or Avala delivery commitment. All requested quantities, capture modes and conditions require feasibility and rights review. Keep confidential recordings, identifiers and credentials out of public copies.

## Program and data product

| Required decision | Requested value | Agreed value / evidence |
| --- | --- | --- |
| Program owner and review date | | |
| Learning task and intended use | | |
| Data product: human video, instrumented human, robot trajectory, deployment log or synthetic | | |
| Requested collection versus existing inventory | | |
| Target embodiment and operating conditions | | |
| Output-contract version and downstream loader | | |
| Task-catalog edition and source, if used | | |
| Scope exclusions and feasibility constraints | | |

A task specification is not evidence of completed or licensable inventory. Record availability separately for each requested data product. Human video and estimated pose do not establish recorded robot actions or measured joint state.

## Coverage cells

Define a cell as an explicit combination of relevant task and condition values. Do not multiply every possible dimension into a target without checking feasibility and usefulness. Use stable task IDs from the selected catalog edition; retain original IDs when task names change.

| Cell ID | Task ID / edition | Environment | Object / variation | Embodiment / operator cohort | Sensor configuration | Conditions / exclusions | Requested accepted units | Feasibility status / owner |
| --- | --- | --- | --- | --- | --- | --- | --- | --- |
| | | | | | | | | |

Possible dimensions to select, not promised collection capabilities: lighting, weather, background, object material/geometry, task difficulty, interaction stage, occlusion, operator experience and success/failure/recovery outcome. Record when a dimension is unknown or not applicable instead of filling a plausible default.

## Signals and episode definitions

Reference the output contract for measured sensors, recorded commands, estimates, transforms and human annotations. For each required channel, specify units, coordinate frame, timestamps, synchronization tolerance and missing-data behavior. Confirm actual support with a representative recording before scaling collection.

| Decision | Definition / evidence |
| --- | --- |
| Episode start/end and interruption rule | |
| Success, failure and recovery definitions | |
| Technical validity requirements | |
| Required observations, actions and state | |
| Language/action annotation taxonomy | |
| Calibration and synchronization checks | |
| Accepted unit: episode, sequence or hour | |
| Treatment of partial episodes and rejected attempts | |

## Rights and sampling controls

Record the consent, permitted-use and provenance artifacts that must exist, who reviews them and how access is controlled. Do not infer rights from public visibility or from a contributor's possession of a recording.

| Control | Agreed rule / evidence |
| --- | --- |
| Required consent and collection permissions | |
| License / intended-use restrictions and reviewer | |
| Operator, location and object concentration limits | |
| Duplicate / near-duplicate definition and method | |
| Train/evaluation split unit and leakage controls | |
| Excluded identities, environments or sensitive content | |
| Retention and access terms for the program | |

## Delivery coverage and recollection

Complete only after inspecting a specific delivered release. Keep requested, submitted, reviewed and accepted counts separate. Rejected attempts are not accepted volume. State whether durations include pauses and how simultaneous streams are counted.

| Cell ID | Requested | Submitted | Reviewed | Accepted | Rejected / reason | Unknown / unreviewed | Gap and proposed next action |
| --- | --- | --- | --- | --- | --- | --- | --- |
| | | | | | | | |

Record the release ID, counting script/version, units, sampling method, exclusions and reviewer. Evaluate targeted recollection against the missing cells and model needs. Do not represent proposed recollection as scheduled or delivered until agreed and verified.

## Publication of completed results

Public use of completed results approved: **No** until explicitly recorded.

Approver, approved scope/artifacts, rights evidence, customer permission where relevant and review date:


## Related resources

- [Robotics evaluation checklist](https://avala.ai/usecases/robotics)
- [Collection program discussion](https://avala.ai/usecases/data-collection)
- [Workflow catalog](https://avala.ai/coverage/catalog)
- [Output-contract template](https://avala.ai/media/templates/robotics-output-contract-v1.yaml)
- [Discuss a program](https://avala.ai/demo?intent=collection-program)