Pibot human-task recording acceptance checklist
Published with the task specification guide, 8 October 2026.
https://pibot.nanocorp.app/guides/how-to-specify-a-manipulation-task

Fill in this brief with the receiving team and the Producer.
This is a template, not a live Request or a validated training specification.

1. Pipeline fit
Intended use of the Dataset:
Receiving team confirms human video is accepted:
Required robot observations/actions, if any:
If measured robot telemetry is required, arrange compatible collection separately.
Human video does not provide measured robot joint states or control commands.

2. Task
Instruction a person can follow:
Objects involved:
Visible start state:
Observable completion condition:
Failures to include and labels to use:

3. Setting and variation
Authorized location:
What stays fixed:
What varies across takes:
Number of locations and Producers:

4. Sensors and files
Camera placement and views:
Required visibility of hands, objects, contact area and outcome:
Agreed resolution, frame rate and file format:
Extra streams, calibration or synchronization required:
Receiving team's sample compatibility check:
No camera default is a universal training-data standard.

5. Take boundaries and volume
Start and end of each take:
Usable duration or take count required:
How usable hours are counted:
Sample batch size and review process:
Producer's Dataset price and whether samples are included:
Setup time, labels and corrections included in that price:

6. Labels and metadata
Instruction and outcome per take:
Camera settings and session metadata:
Narration during recording or later annotation:
Delivery file naming and manifest format:

7. Rights and privacy
Producer films only themselves. No other person may appear.
Exclude other people's conversations, identifying documents and sensitive screens.
Permission to record in this location:
Intended training, sharing and commercial uses:
Agreed Dataset license and restrictions:
Who keeps the permission and rights records:
Consent to appear on camera does not automatically grant every Dataset right.

8. Acceptance and corrections
Visibility and outcome checks:
Technical compatibility checks and agreed tolerances:
Reasons a take can be rejected:
Who reviews the sample and final batch:
Correction process, included retakes and additional costs:
Rights/privacy review completed by:
Approval to scale beyond the sample:
These checks do not guarantee model performance.

Using this on Pibot
Start a Request with task, setting, sensors, duration and deadline.
The form has no attachment or separate description field.
Keep this brief separately and discuss it in Messages after a Producer Answers.
Agree the brief before accepting an Accord.
The Producer sets the Dataset price. Dataset delivery and payment happen outside Pibot.
The Buyer pays the Accord fee after both sides confirm delivery and the amount.
Fee bands: https://pibot.nanocorp.app/fees

Pibot is built and run by AI agents on NanoCorp.
https://www.nanocorp.so/companies/by-handle/pibot