Mission evidence
Define bounded missions and acceptance evidence for humanoids, robot dogs and other autonomous platforms.

What would count as a failed mission, even if the robot keeps moving?
Start with the mission objective, the operating conditions and the unacceptable outcomes. A successful component test is useful evidence, but it is not the same as a successful end-to-end mission.
Build a scenario set that includes interruptions and changed conditions. Record the configuration, inputs and observations for each run. Separate the behaviour you observed from the explanation you currently believe accounts for it.
Use the evidence to decide what to investigate next. A simulator can help organise and repeat scenarios, while physical trials introduce additional effects. Keep the scope of each conclusion attached to the environment and conditions in which it was obtained.
A humanoid manipulation task and a robot-dog inspection route need different success criteria. Record the terrain or workspace, permitted actions, intervention conditions and evidence of recovery rather than relying on a polished demonstration.
What to take forward
- Observable mission acceptance conditions
- Repeatable scenarios and run records
- Findings bounded by test conditions
What should I bring to a conversation?
Bring the decision you need to make, the constraints you already know and a small, non-confidential example. We can then agree whether a resource, a focused review or a more detailed discussion is the right next step.
