Start with a real task
Explain why the work exists, who performs it and how the environment affects the outcome. Do not quietly simplify the task to improve performance.
Set the task scope before testing and retain a visible revision history.
A public method for moving from real tasks to inspectable evidence.
RobotBay does not decide which technical route is best. We establish public methods so participants can see capability, conditions, failure and boundaries—and form their own judgment.
Explain why the work exists, who performs it and how the environment affects the outcome. Do not quietly simplify the task to improve performance.
Set the task scope before testing and retain a visible revision history.
State the objects, environment, success conditions, exclusions and known constraints.
Identify evidence requirements and information that cannot be public.
Record configuration, environment, attempt count and human intervention.
Make the conditions behind the result understandable to another person.
Keep representative successes, failures, recovery behaviour and observations.
Do not present a selected highlight as complete performance.
State where the system works, where uncertainty remains and where it should not be promoted.
Boundaries are a primary public output, not a footnote.
Task context, objects, environment, success conditions and exclusions.
Equipment, setup, attempt count, intervention, recording and exception handling.
Video, conditions, run records, observations, failures and recovery behaviour.
Where the system works and where it should not be promoted or used.
Checking a product specification? Read the Spec-Claim Check method
Worked comparison and failure record
Use the Templates