[BotshareAI]

Summary

Records the platform lead's decisions of 2 November 2026 in decisions.yaml so that roadmap PR openAMRobot/openamrobot-docs#68 no longer contradicts the register. in_force stays P-03-rev20.2, with a note that these owner decisions are to be entered in P-03. Each superseded value is kept in its entry's supersedes history. Scope: decisions.yaml, tests/test_check_decisions.py, WATCHDOG.md (accepted-words table, regenerated), STATE.md.

Source line (added under sources, like "Alex decision 2026-10-30"): Alex decision 2026-11-02: platform decision of 2 November 2026; change request #83; to be entered in P-03.

Changed entries (old, then new):

• CHARGING: "WCM-500-24 is the 2.0 charging path; receiver, SB50, F-CHG, charge relay and fault input designed in; Daly charger bench only with the E-stop pressed", now "WCM-500-24 prepared in 2.0: receiver (170 x 150 x 52 mm, manual V2.5) position reserved at the rear panel on the centre line, bottom 50 mm above the floor, base-sheet cut-out, F-CHG, KCHG and the start and fault lines designed and wired; receiver installed later; manual SB50 charging with the Daly 28.4 V / 20 A charger at any time; docking approaches, turns 180 degrees and reverses onto the transmitter". New check: Daly charger presented as bench only.
• DOCK-NO-CONTACTS: "wireless charging belongs to 2.0", now "wireless charging prepared in 2.0, receiver installed later; docking approach turns 180 degrees and reverses onto the transmitter".
• OPERATOR-PANEL: "ZX80 on a rotatable mount, landscape by default, portrait second", now "ZX80 portrait only (149.8 wide x 234 tall) on a fixed mount; no rotation, no landscape". UI-code check now flags landscape or a rotatable mount.
• TABLET-MOUNT: "rotatable mount, two locked positions, landscape default", now "portrait only on a fixed mount; centre 40 mm lower; head light top edge 10 mm below the Getac bottom edge". Text check now flags landscape or a rotatable mount.
• HEAD-CAMERA-IDENTITY: "lens 0.042 m ahead of the arm mount", now "lens 0.057 m ahead", height unchanged. Check now also flags 0.042 m / 42 mm.
• SAFETY-PROCUREMENT: "second E-stop on the rear face of the static lift column", now "on top of the moving adapter plate, centred, behind the arm post, button up (about 0.90 / 1.08 / 1.25 m at L1000 / L1175 / L1350)". New check: second E-stop on the static column.
• BATTERY-PLACEMENT: "one 8S1P pack, as close to the rear edge as practical (single row of 8 cells)", now "8 x EVE LF105, 8S, in two removable trays of 4 cells in the rear side pockets, joined by PWR-018; BMS and power distribution on a plate above the receiver position; nothing on top of the cells". New check: single row of 8 cells.
• LIFT: "lift approved in principle", now "combined model including the lift implemented and verified in simulation; physical hardware build and acceptance in progress; release gates still open". Adds stop sensors (3 x SICK IME12-04BNSZC0S, rear face of the static column, z 120 / 295 / 470 mm), the flag rod on a rear extension of a one-piece adapter plate (425 x 100 x 10 mm, 6082-T6; supersedes the rear-flush rule, P-03 rev20.1 item 25 D2) and the base plate on the centre-frame arch (doubler, or through-bolts with a backing plate). Check messages reworded.
• FRAMES-REP105: "base_link 0.098 m (axle height)", now also "wheel radius 0.100 m with base_link at 0.098 m is intended: 2 mm tyre compression, no suspension".

I checked DOCKING-NOT-CHARGING, SHARED-BASE and DRIVETRAIN and left them unchanged. They do not contradict these decisions, and base_link height is recorded only in FRAMES-REP105.

Work package

#83 (contract change request). Unblocks openAMRobot/openamrobot-docs#68

Integration Gate

• Overlapping PRs: profile: add OpenAMRobot 2.0 with OpenArm 2.0 block; update lift wording #81 (profile README) is not touched; profile/README.md is unchanged. audit: repository alignment with P-03 rev20.2 and Use Case 1 (1 Nov 2026) #79 and docs: current configuration ID example, 2.0 LiDAR and base controller in the roadmap, profile wording (P-03 rev20.2) #80 are drafts on other branches that do not edit decisions.yaml entries changed here.
• Reused: the existing entry layout, the supersedes convention and the test style of decisions: register the owner decisions of 30 October 2026; P-03 rev20.1 in force #73 and decisions: P-03 rev20.2 item 26 in force (BOM Issue 7.14, availability rule, tablet mount, EV_ICM-42688-P) #78.
• Rejected: changing in_force (the owner keeps P-03-rev20.2) and editing other repositories (consumers update their own text).

Tests

Changed or added in tests/test_check_decisions.py: test_head_camera_lens_57_mm_ahead, test_second_estop_on_the_adapter_plate, test_daly_charger_is_not_bench_only, test_battery_in_two_trays, test_2026_11_02_values_recorded, test_tablet_mount, test_zx80_portrait_only_no_landscape, test_operator_panel_is_the_getac_zx80, test_p03_rev20_1_values_are_cited, test_rev20_2_values_in_force.

• With this change: tests/test_check_decisions.py ran 98 tests, 98 passed, 0 skipped.
• Revert run (main's decisions.yaml with these tests): 9 failed, 89 passed.
• rollout/verify.sh: 293 of 293 tests executed, 0 skipped.

Evidence

Base SHA: a9e229e
Head SHA: 4056b8e

bash rollout/verify.sh                                  -> Tests executed: 293 of 293 (skipped 0); PASS: test; PASS: evidence
python3 tools/check_decisions.py --decisions decisions.yaml --maintainers maintainers.yaml --validate-only  -> 46 loaded, 41 recorded and scanned, 2 open, 3 superseded
python3 tools/check_decisions.py --decisions decisions.yaml --maintainers maintainers.yaml --root . --repository .github  -> 0 contradiction(s)
python3 tools/check_agent_rules.py --canonical agent-rules/SHARED_RULES.md --file AGENTS.md  -> PASS AGENTS.md (v2)
python3 tools/check_public_extract.py --root . --allowlist public-extract-allowlist.yaml --repository .github  -> 0 finding(s)
python3 -m pytest -q tests/test_check_decisions.py      -> 98 passed
python3 tools/watchdog.py --accepted-words              -> WATCHDOG.md table regenerated

Dependencies

None.

Safety impact

Record only, with no change to any safety function. SAFETY-PROCUREMENT changes only the mounting position of the second E-stop. The button, the contact block, the dual channel into the PNOZ s3, K1/K2 and the reset loop are unchanged. CHARGING records KCHG and the start and fault lines as designed and wired, and their function is unchanged. No file under safety_paths is changed. The SAFETY-PROCUREMENT owner (electrical-owner) and the platform lead must review the position change. A text scan is not safety evidence.

STATE.md

Updated: work-package row for #83, the in_force note, the known-gap line for SAFETY-PROCUREMENT and a Not verified line.

Not verified

• Register values against the owner's decision record and P-03. The values are not yet entered in P-03, and the source documents are not in any repository.
• Scans of consumer repositories (openamrobot-docs, openamr-platform-hw, openamr-platform-sw, openamrobot-ui) against the changed patterns. Text there that names a landscape or rotatable ZX80, the 42 mm lens offset, the E-stop on the static column, a single cell row or a bench-only Daly charger will be reported until it is relabelled.
• Mechanical fit of the receiver position, battery trays, adapter plate and E-stop heights. Nothing physical was checked.

AI disclosure

Claude Code produced the register edits, tests, STATE.md update, the regenerated WATCHDOG.md table, contract change request #83 and this description from the owner's summary. The work-package owner must review it and write adopt, adapt or reject.

Contribution terms

• Every commit is signed off under the DCO.
• I am covered by an accepted Contributor Agreement.
• Third-party material is identified with source and licence.
• No confidential, personal, credential or export-controlled information is included.
• No partner, customer or private person is named; the application is Use_Case_1.

🤖 Generated with Claude Code