Robotics evidence guide · automated editorial preparation, not expert review

Separate plans, control and authority

A task plan, an actuator command and permission to execute are distinct records. Maha’s first robotics integration should observe and verify evidence offline, not sit inside a motion-control or emergency-stop loop.

Evidence and interpretation

Our architecture proposal gives the planner a desired task, the controller a bounded action interface, and the evidence collector a record of what happened. A permission record describes what was authorized; it does not prove the selected action was physically appropriate. Likewise an execution receipt may show that a command was accepted without proving it completed. Preserve these distinctions when connecting agent tools to robots. Existing package-quality declarations help document software responsibilities, but do not establish a whole-system safety case.

Proposed evidence workflow

  1. Identify the planner, controller, operator and evidence collector as separate roles.
  2. Record command request, acknowledgement and observed outcome without equating them.
  3. Keep emergency stopping and physical safety controls independent of Maha’s network service.

Worked illustration

Our offline simulator compares a direct-path controller with an obstacle-aware controller. Both receive the same planned cases. The verifier can replay their discrete decisions, but has no interface for commanding a robot or overriding its safeguards.

Limits

This is an integration design boundary, not a functional-safety architecture or authorization to operate hardware. No real-time-control performance claim is made.

Sources and review

ROS REP 2004: Package quality categories

Locator: Level 1 / Package Requirements: Version Policy, Change Control Process, Documentation, Testing

Quality declarations connect package-quality claims to versioning, documented interfaces, review and testing requirements.

Boundary: Package quality is not whole-robot certification. Maha has not been assessed at a ROS quality level.

Inspection and reuse basis

Selected sections inspected 2026-09-14. Original explanation and link; no source redistribution. This is not independent expert review of this article.

Continue reading