You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[I1][I8] Define base-arm readiness and travel inhibition contract #7
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:
The exact per-arm fields and pose enumeration (measured pose, validity, motion/trajectory-active state and any required fault/health state).
How the two arm states are aggregated; both arms must independently satisfy the approved safe state.
Publisher boot/session ID and monotonically increasing sequence semantics.
The freshness threshold and how consumers determine expiry using local receipt time.
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.
Activity
Evans-Kwashie commentedon Nov 17, 2026
Following the I8 lift-interlock coordination on openAMRobot/openamrobot-interfaces#38, I need to close the manipulation-side
ArmStatuscontract before the base-controller lift permit can be finalised.The agreed ownership direction is:
ArmStatusinterface.lift_permit.STOWEDas the only defined safe arm configuration.Could the manipulation owners please define or confirm:
Please also confirm whether the separate
ArmStatusinterface will be published by manipulation directly and identify the message/package location. I will keep the I8 contract Proposed until these dependencies are defined.