Skip to content

[I1][I8] Define base-arm readiness and travel inhibition contract #7

Open

Description

@BotshareAI

Owners

Om Mangesh Jagtap and Adnan Khalid

Contributors

Tushar Goel and Abhiroop Bhavsar

Cross-team reviewer

Evans Kwashie, with Mohamed Sayed

Context

The navigation contract must consume base/arm readiness information without owning manipulation states or safety behavior.

Scope

Define and document:

  • BASE_SETTLING;
  • MANIPULATION_READY;
  • configurable readiness thresholds and hold times;
  • ARM_MOTION_ACTIVE;
  • ARMS_NOT_IN_TRAVEL_POSE;
  • deterministic travel-inhibition reasons;
  • ownership of each state between I1, I8, manipulation and navigation;
  • safe rejection behavior for unsupported arm/device capabilities.

Non-goals

  • Do not add drawer-specific or arm-action fields to PR ci: add lightweight repository quality checks #5.
  • Do not implement physical E-stop, brake or watchdog logic in the interface repository.
  • Do not duplicate the Device Package or tool/contact contract.

Acceptance criteria

  • State ownership and transitions are documented.
  • Navigation can receive a deterministic reason when travel is inhibited.
  • The contract is compatible with the Device Package and base-controller work.
  • Simulation examples and a negative test for travel during arm motion are attached.

Activity

  1. Evans-Kwashie commented on Nov 17, 2026

    @Evans-Kwashie

    Following the I8 lift-interlock coordination on openAMRobot/openamrobot-interfaces#38, I need to close the manipulation-side ArmStatus contract before the base-controller lift permit can be finalised.

    The agreed ownership direction is:

    • Manipulation publishes the authoritative, validated measured arm status through a separate ArmStatus interface.
    • I8/base-controller firmware is the sole producer of lift_permit.
    • Build 1 treats STOWED as the only defined safe arm configuration.
    • CTL-017 remains the final local lift-actuator enforcement point.
    • Missing, stale, invalid, inconsistent, wrong-session or unsupported arm feedback must deny the permit.

    Could the manipulation owners please define or confirm:

    1. The exact per-arm fields and pose enumeration (measured pose, validity, motion/trajectory-active state and any required fault/health state).
    2. How the two arm states are aggregated; both arms must independently satisfy the approved safe state.
    3. Publisher boot/session ID and monotonically increasing sequence semantics.
    4. The freshness threshold and how consumers determine expiry using local receipt time.
    5. The approved STOWED joint-space definition, including the accountable owner who signs off the joint-space values.

    Please also confirm whether the separate ArmStatus interface will be published by manipulation directly and identify the message/package location. I will keep the I8 contract Proposed until these dependencies are defined.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions