Pibot recording brief
Editable template — not a published Request or a Dataset offer.
Replace every bracketed field before sharing. Examples are suggestions, not requirements.

1. Task
Training use: [what your pipeline will learn from this Dataset]
Human-video fit: [confirm your pipeline accepts human recordings rather than robot demonstrations]
Required data channels: [RGB video, labels, or measured robot observations/actions; distinguish required from optional]
Ordinary human phone video does not measure robot joint states, actuator commands or force feedback.
If robot telemetry is required, specify the robot, equipment and synchronization explicitly.
Task: [one precise gesture, e.g. loading a dishwasher, one plate at a time]
Start state: [where the objects and hands begin]
Steps: [what the person does, in order]
Success condition: [the visible end state]
Failures and interruptions: [whether to include them and how to label them]

2. Setting
Setting: [home / workshop / factory]
Details: [room, surfaces, lighting, objects and sizes]
Variations: [which objects or places should change, and how many]
Permission: [confirm you may record at this location]

3. Sensors and capture
Equipment and mount: [e.g. head-mounted phone camera]
Resolution and frame rate: [e.g. 1080p; agree a frame rate]
View: [which hands, objects and interactions must stay visible]
Audio: [needed / not needed; avoid private conversations]
File format: [agree with the Buyer]
Additional sensors: [none, or specify devices and any synchronization needs]
Phone video alone does not provide robot actions, depth or force measurements.

4. Quantity and deadline
Usable recording duration: [hours]
Episode count, if needed: [number]
Episode boundaries: [when each recording starts and stops]
Delivery deadline: [day month year]
Delivery method: [agree a link or transfer method in Messages]

5. Sample and acceptance
Sample clip: [public link showing the task and proposed camera setup]
Agree a representative sample before full collection.
Quality checks: [hands/objects visible; task checkable; no unusable blur or missing frames]
Delivery checks: [usable duration, variations, filenames and task/outcome labels]
Review window: [how long the Buyer has to check delivered files]
Corrections: [what happens if files fail the agreed checks]
These checks are agreed between Buyer and Producer; Pibot does not verify Dataset quality.

6. Price and permitted use
Producer's fixed Dataset price: [amount] EUR
Permitted uses: [training, evaluation, commercial use; agree restrictions and recording rights]
Payment arrangements: [agree directly between Buyer and Producer]
The Buyer pays the Producer directly, outside Pibot.
After delivery, both parties confirm delivery and the amount on Pibot.
The Buyer then pays Pibot's Accord fee, set by Fee band:
https://pibot.nanocorp.app/fees
Do not put banking details, private contacts or private delivery links in a public Request.

7. Self-recording rule
The Producer must appear alone in the recordings. No one else may be filmed.
Check mirrors, screens and backgrounds before recording.
Remove personal information and workplace-confidential material from view.
Only record a task and location you have permission to record.

Worked example: loading a dishwasher
Fictional example — not a live Request, Dataset offer or validated training specification.
All capture and acceptance choices below are proposals for Buyer and Producer to agree.
They are not universal quality standards or a promise of training results.

Training use: studying visible human plate-handling sequences in a pipeline that accepts human RGB video.
Required channels: RGB video and agreed task/outcome labels; no measured robot actions or joint states.
The Buyer must confirm this fit before commissioning any recordings.

Task: loading a dishwasher, one plate at a time.
Start state: dishwasher open, rack accessible, one plate on the agreed kitchen surface.
Steps: pick up the plate, move it to an agreed rack slot, release it.
Success condition: the plate remains supported in the slot after release.
Label unsuccessful placements, drops and interruptions separately.
Exclude unloading, detergent handling and wash cycles from this example.

Setting: home kitchen, standard dishwasher, daylight.
Variations: agree plate sizes, rack positions and locations after reviewing the sample.
Do not introduce unsafe placements or deliberately drop plates for a failure clip.

Sensors: head-mounted phone camera, 1080p.
Agree frame rate and file format; audio is not requested in this example.
Hands, plate contact, rack placement and the final state must be visible enough to judge.
Check the proposed mount in a representative Sample clip before full collection.
This setup does not supply calibrated depth, force feedback or robot telemetry.

Quantity: 5 h of accepted task footage, not 5 h of time spent recording.
Exclude breaks, off-task resets and clips that fail the agreed checks.
Agree whether useful unsuccessful attempts count toward the duration.
Episode boundaries: begin at the agreed start state; stop after the placement outcome is visible.
Do not derive an episode count from the duration alone.
The Buyer must choose a feasible delivery deadline before previewing their Request.

Acceptance: the task, hand–plate interaction and outcome can be checked from each accepted clip.
Reject clips where blur, occlusion or missing frames prevent those checks.
Deliver an agreed manifest listing episode identifiers, durations, variations and outcome labels.
Agree the review window and correction process in Messages before the Accord.
Pibot does not inspect or validate the Dataset.

Rights: only the Producer appears; they have permission to record in the kitchen.
Check reflections and remove private documents or screens from view.
Agree training, evaluation and commercial-use permissions explicitly.
Price: not set by this example; the Producer proposes their fixed Dataset price in EUR.
Dataset payment and delivery arrangements remain directly between Buyer and Producer.
Pibot's Accord fee is due only after both parties confirm delivery and the amount.

Adapt this example in the real Request form:
https://pibot.nanocorp.app/requests/new?example=dishwasher
The form is prefilled but editable; nothing is published until the Buyer signs in and publishes.
Put only the public task summary in the Request; settle detailed terms privately in Messages.

Next step
Put the task, setting, sensors, duration and deadline into a Request:
https://pibot.nanocorp.app/requests/new
Agree detailed acceptance checks, usage rights and delivery terms in Messages before the Accord.
Posting a Request is free. Producers answer with a Sample clip and their fixed Dataset price.

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