[BotshareAI]

Summary

Text-only alignment of three files with the decisions register (P-03 rev20.2 in force). These are the class A and B findings for this repository in the audit #79.

• CONFIG-IDS, LIFT: the contract change request template now uses base_plate bp050 as its example configuration ID (replacing the retired mast_1350) and LIFT / none as its register-entry placeholder (replacing the superseded MAST-INSTALL-HEIGHT).
• NAV-LIDAR, BASE-CONTROLLER-GATES: ROADMAP.md names the navigation LiDAR (SLAMTEC RPLIDAR S3, S3M1-R2) instead of "3D LiDAR". It names the STM32H723ZG base controller for 2.0, with Teensy only in the Gate A legacy configuration and as the release fallback. The file's CRLF line endings are kept.
• profile/README.md:
  • ARM-MOUNT: the "arm mount point" is 180 mm ahead of the column axis (was "arm profile").
  • DRIVETRAIN: holding brakes; their fail-safe behaviour still needs verification evidence.
  • ESTOP-SCOPE: two hardwired E-stops that cut actuator power (traction, both arms, lift); the Jetson, 5 V and regulated 24 V rails stay powered.
  • CHARGING: the included Daly charger is for bench charging only, with the E-stop pressed.

Work package

#79 (repository alignment audit, 1 Nov 2026).

Integration Gate

• Open PRs ci: add baseline ROS 2 CI image #41, watchdog: daily software-health report (CI, open PRs, rc.1 issues) and openamrobot-embodied-ai in the scan #69, harness: autonomous improvement loop and decisions.yaml lifecycle (design, off until founder approval on #43) #70, decisions: PLATFORM-PIN moves to platform-sw 131e500 (2.0 base) #74 and fix(harness): enforce publish guard against unsafe commit history and tier bypass #76 do not touch these three files. audit: repository alignment with P-03 rev20.2 and Use Case 1 (1 Nov 2026) #79 (the audit) changes only AUDIT-2026-11-01.md and STATE.md.
• Rejected: the register's own gaps and conflicts (class D and E, S1 to S17 in the audit) are owner decisions and are not edited. The allowlisted prices in README.md and profile/README.md are unchanged.

Decisions impact

Consumer of CONFIG-IDS, LIFT, NAV-LIDAR, BASE-CONTROLLER-GATES, ARM-MOUNT, DRIVETRAIN, ESTOP-SCOPE and CHARGING. No register entry changes.

Tests

No behaviour change and no test change. Repository suite: bash rollout/verify.sh ran 289 tests, 0 skipped, PASS.

Evidence

Base SHA: 1678735
Head SHA: 304b29c

git rev-parse origin/main                                     # 1678735 (audited SHA)
bash rollout/verify.sh                                        # Tests executed: 289 of 289 (skipped 0); PASS
python3 tools/check_decisions.py --decisions decisions.yaml --maintainers maintainers.yaml --validate-only   # exit 0; 46 loaded
python3 tools/check_agent_rules.py --canonical agent-rules/SHARED_RULES.md --file AGENTS.md                  # PASS AGENTS.md (v2)
python3 tools/check_decisions.py --decisions decisions.yaml --maintainers maintainers.yaml --root . --repository .github --changed-files changed.txt   # 0 contradiction(s), scope 3 changed file(s)
python3 tools/check_public_extract.py --root . --repository .github --allowlist public-extract-allowlist.yaml --changed-files changed.txt   # 0 finding(s)

Dependencies

None.

Safety impact

None: text only, no safety function changed. profile/README.md now describes the E-stop scope (ESTOP-SCOPE) and the bench-only Daly charger (CHARGING) in public wording. The platform lead should approve that wording.

STATE.md

No change in this PR: STATE.md is updated in the audit PR #79, and a second edit would conflict.

Not verified

• No rendering check of the profile page.
• This is text consistency only.

AI disclosure

Claude Code produced the edits and this description from the audit rows in #79. The lead reviewed the diff. This PR stays a draft until the work-package owner writes 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 by Claude Code