Skills

Ship an Autonomous Robot Task

6 weeks · 0 milestones

Combine your robot and on-device model to complete a task on its own, with a pass mark set in advance and a live demo under a condition your verifiers choose.

Part of: Engineering · Proves for: Engineers

Milestone map

3 milestones

Define the task and success test

1 week

Pick one task your robot will do on its own using its on-device model — for example, sort objects, respond to a spoken command, or follow a person. Write down exactly what counts as success before building.

Proof required

Submit a one-page task spec: the task, the test setup, how many trials, and the pass mark, dated before the build.

What gets checked

Success is measurable
Trial count and pass mark set in advance
Uses both sensing and the on-device model

Common mistakes

Success defined after seeing results
A task that needs no model
No trial count

Powstik Guide

A dated test plan for an autonomous task.

Steps

Choose one task.
Describe the test setup.
Set trials (10+) and a pass mark.
Date it.
Share it with your verifiers before building.

Template

Task spec
Task:
Setup:
Trials:
Pass mark:
Date:

What gets sent back

Undated spec.
No pass mark.
No model in the loop.

Resources

Foundationstart here

What a verifier looks for

Checked by the verifiers you invite to your panel (up to 3). Pick people who can judge the work, not friends.
Check the date comes before build work
Ask why this pass mark is fair

You'll sign in first, then come straight back here.

Build and run the trials

3–4 weeks

Combine your robot and model to do the task with no human help. Run every planned trial and record each result, including failures.

Proof required

Link unedited video of all trials and a results table (trial, outcome, note) against your pass mark.

What gets checked

Every planned trial shown, failures included
No human touches the robot mid-trial
Result compared to the pre-set pass mark

Common mistakes

Showing only successes
Nudging the robot mid-trial
Changing the pass mark after

Powstik Guide

A full set of recorded autonomous trials.

Steps

Integrate model and control.
Dry-run until stable.
Run every planned trial on camera.
Log each result.
Compare to the pass mark honestly.

Template

Trial | pass/fail | note

Total:
Pass mark met? Y/N

What gets sent back

Edited highlights only.
Human help mid-trial.
Moved goalposts.

Resources

Foundationstart here

Depthgo deeper

What a verifier looks for

Checked by the verifiers you invite to your panel (up to 3). Pick people who can judge the work, not friends.
Count trials against the spec
Check failures are included

You'll sign in first, then come straight back here.

Demo it live and defend it

1 week

Run the task live for your verifiers, who pick at least one new condition (a new object, a new voice, a different floor). Explain design choices and one thing you would change.

Proof required

Submit the live demo video including the verifier's new condition, and the review log with their challenges and your answers.

What gets checked

Live, not recorded earlier
At least one unseen condition from the verifier
Honest about limits

Common mistakes

Demo only in the tested setting
No verifier-chosen condition
Hiding a known failure

Powstik Guide

A live demo under a new condition.

Steps

Book a live session with your verifiers.
Let them choose a new condition.
Run the task.
Answer their questions.
Log what changed afterward.

Template

Review session log
Date:            Duration:
Reviewer name:
Reviewer role and experience:

Challenge 1 (autonomous task under a new condition):
  What they asked:
  My answer:
Challenge 2:
  What they asked:
  My answer:

Change I made after the session:

What gets sent back

Pre-recorded demo.
No new condition.
No review log.

Resources

Foundationstart here

Depthgo deeper

What a verifier looks for

Checked by the verifiers you invite to your panel (up to 3). Pick people who can judge the work, not friends.
Introduce one condition they have not tested
Ask what fails first and why

You'll sign in first, then come straight back here.

Part of

Robotics & Embedded AI →

Related outcomes

Milestone map

3 milestones

Define the task and success test

1 week

Proof required

Submit a one-page task spec: the task, the test setup, how many trials, and the pass mark, dated before the build.

What gets checked

Success is measurable
Trial count and pass mark set in advance
Uses both sensing and the on-device model

Common mistakes

Success defined after seeing results
A task that needs no model
No trial count

Powstik Guide

A dated test plan for an autonomous task.

Steps

Choose one task.
Describe the test setup.
Set trials (10+) and a pass mark.
Date it.
Share it with your verifiers before building.

Template

Task spec
Task:
Setup:
Trials:
Pass mark:
Date:

What gets sent back

Undated spec.
No pass mark.
No model in the loop.

Resources

Foundationstart here

What a verifier looks for

Checked by the verifiers you invite to your panel (up to 3). Pick people who can judge the work, not friends.
Check the date comes before build work
Ask why this pass mark is fair

You'll sign in first, then come straight back here.

Build and run the trials

3–4 weeks

Combine your robot and model to do the task with no human help. Run every planned trial and record each result, including failures.

Proof required

Link unedited video of all trials and a results table (trial, outcome, note) against your pass mark.

What gets checked

Every planned trial shown, failures included
No human touches the robot mid-trial
Result compared to the pre-set pass mark

Common mistakes

Showing only successes
Nudging the robot mid-trial
Changing the pass mark after

Powstik Guide

A full set of recorded autonomous trials.

Steps

Integrate model and control.
Dry-run until stable.
Run every planned trial on camera.
Log each result.
Compare to the pass mark honestly.

Template

Trial | pass/fail | note

Total:
Pass mark met? Y/N

What gets sent back

Edited highlights only.
Human help mid-trial.
Moved goalposts.

Resources

Foundationstart here

Depthgo deeper

What a verifier looks for

Checked by the verifiers you invite to your panel (up to 3). Pick people who can judge the work, not friends.
Count trials against the spec
Check failures are included

You'll sign in first, then come straight back here.

Demo it live and defend it

1 week

Run the task live for your verifiers, who pick at least one new condition (a new object, a new voice, a different floor). Explain design choices and one thing you would change.

Proof required

Submit the live demo video including the verifier's new condition, and the review log with their challenges and your answers.

What gets checked

Live, not recorded earlier
At least one unseen condition from the verifier
Honest about limits

Common mistakes

Demo only in the tested setting
No verifier-chosen condition
Hiding a known failure

Powstik Guide

A live demo under a new condition.

Steps

Book a live session with your verifiers.
Let them choose a new condition.
Run the task.
Answer their questions.
Log what changed afterward.

Template

Review session log
Date:            Duration:
Reviewer name:
Reviewer role and experience:

Challenge 1 (autonomous task under a new condition):
  What they asked:
  My answer:
Challenge 2:
  What they asked:
  My answer:

Change I made after the session:

What gets sent back

Pre-recorded demo.
No new condition.
No review log.

Resources

Foundationstart here

Depthgo deeper

What a verifier looks for

Checked by the verifiers you invite to your panel (up to 3). Pick people who can judge the work, not friends.
Introduce one condition they have not tested
Ask what fails first and why

You'll sign in first, then come straight back here.