Repository navigation
Expand file tree
/
Copy pathdecisions.yaml
More file actions
1841 lines (1787 loc) · 141 KB
/
Copy pathdecisions.yaml
File metadata and controls
1841 lines (1787 loc) · 141 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
# OpenAMRobot register of approved technical decisions.
#
# Two layers, kept separate:
# - AGENTS.md and CONTRIBUTING.md hold process: how a decision is proposed,
# reviewed, recorded, changed, tested and propagated.
# - This file holds the approved technical decisions repositories follow:
# values with units, allowed configurations, limits, exclusions and
# semantic distinctions.
#
# CI evaluates only this pinned, version-controlled file. No check fetches a
# plan document, a drive or the documentation site. Source documents are
# provenance: when a source and this register disagree, a human resolves it
# (the entry's owner) and no tool rewrites either side. tools/check_decisions.py
# only reads files and reports.
#
# What the scan proves: that a scanned file does not contain a listed
# contradicting phrase. It proves textual consistency only, never mechanical,
# electrical or safety correctness. Each entry's `verification.human` names
# the reviewer and the evidence that the scan cannot provide.
#
# Schema (schema_version 1), one entry per decision:
# id unique, upper case, stable
# title one line
# summary optional; the decision in one line of at most 120 characters,
# printed with each finding (the long value stays here)
# fix_hint optional; how to fix a finding, one line of at most 120 characters
# kind value | configuration | limit | exclusion | distinction
# status recorded (scanned and reported) | open (not decided; not scanned) |
# superseded (replaced by a later decision; only its citation is scanned)
# value/values exactly as the source states it; nothing invented
# unit SI unit or none
# date date the decision was taken (null when the source gives none)
# review_by review date; six weeks after date, or six weeks after this register update when date is null
# source document (a key under sources) and item
# supersedes earlier values with their source; optional `citation`, a
# pattern that finds text still citing the superseded source
# applies_to repositories (globs) and files (globs); exclude optional
# check patterns; each has a (?P<found>...) group, optional files
# (globs narrowing this pattern), optional line-level `unless`
# exemption and a message
# verification machine: what the scan detects; human: reviewer role and
# the evidence they need
# owner role in maintainers.yaml who approves changes to this entry
# superseded_by for status superseded: document (a key under sources), item,
# optional decision (the replacing entry), citation (a pattern
# with a (?P<found>...) group for text still presenting the
# superseded value as current) and optional unless; `check`
# is then not used
#
# Changing an entry follows "Changing a decision" in AGENTS.md: change request
# issue, source document first, then one reviewed PR that updates this file and
# every affected consumer together.
schema_version: 1
in_force:
source: P-03-rev20.6
date: 2026-11-08
note: P-03 rev20.6 item 30 records the Build 1 decision baseline of 8 November 2026 (decisions D-01 to D-34, platform-lead rulings A1 to A9); P-03 rev20.4 item 28 and rev20.5 item 29 stay in force where item 30 does not change them; the roadmap model (openamrobot-docs) is the reference for component selection and placement; mass is under ledger review (MASS-LEDGER)
sources:
P-03-rev20.4:
title: "OpenAMRobot 2.0 Decision Addendum rev20.4, 8 November 2026 (the addendum in force; item 27: K1/K2 GX11CAC under a sourcing exception, 4 Nov; item 28: owner decisions of 2, 3 and 8 Nov 2026: two battery trays, rear power module, K1/K2 without the Siemens fallback, receiver 15 mm offset, second E-stop on the adapter plate, fixed portrait ZX80 55 mm lower, head camera 60 mm, DOLD supplier CAD, arch backing plate, wiring rules)"
evidence: plan-set document, not held in any repository; provenance only, CI never reads it
P-03-rev20.5:
title: "OpenAMRobot 2.0 Decision Addendum rev20.5, 8 November 2026 (item 29: owner decisions of 8 Nov 2026, among them the receiver plastic frame, 20 mm on the sides and 15 mm above, the cable keep-out at the slot band without an inward band, and the two lift cable openings)"
evidence: plan-set document, not held in any repository; provenance only, CI never reads it
P-03-rev20.6:
title: "OpenAMRobot 2.0 Decision Addendum rev20.6, 8 November 2026 (item 30: Build 1 decision baseline, decisions D-01 to D-34 and platform-lead rulings A1 to A9: compute, IMU topic, speed ceiling, stop release, UI link loss, lift fixing and backing plate, CTL-017, mass ledger, battery trays, schedule; supersedes item 28 on lift fixing, receiver keep-out and slot band)"
evidence: plan-set document, not held in any repository; provenance only, CI never reads it
Alex decision 2026-11-08:
title: Platform decision of 8 November 2026 (ZX80 15 mm lower again, head camera 60 mm, receiver 15 mm offset from any side, DOLD supplier CAD dimensions, arch backing plate, no cable in the slot between the base panels and the cover skirt); entered in P-03 rev20.4 item 28
evidence: decision record, not held in any repository; provenance only, CI never reads it
P-03-rev20.2:
title: "OpenAMRobot 2.0 Decision Addendum rev20.2, 1 November 2026 (the addendum in force; item 26: BOM Issue 7.14, component availability, tablet mount, SAFE 24 V converter, EV_ICM-42688-P IMU board, hub-motor brake data, DOLD holding confirmation)"
evidence: plan-set document, not held in any repository; provenance only, CI never reads it; values entered from the owner's summary of item 26 (change request openAMRobot/.github#77)
BOM-Issue-7.14:
title: OpenAMRobot 2.0 Detailed Hardware BOM, Issue 7.14, 27 October 2026, with the 1 November 2026 changes (canonical per P-03 rev20.2)
evidence: not held in any repository; provenance only, CI never reads it
BOM-Issue-7.15:
title: "OpenAMRobot 2.0 Detailed Hardware BOM, Issue 7.15 (9 November 2026 workbook: LFT-008 lift foot fasteners, MEC-022 arch backing plate, 21 changed rows): source of the public roadmap parts extract in openamrobot-docs (hardware page PARTS, bom_coverage.csv); not the canonical procurement baseline until the BOM owner confirms it"
evidence: not held in any repository; provenance only, CI never reads it; imported by openamrobot-docs scripts/roadmap_model/bom715.py (openamrobot-docs #84)
P-03-rev20.1:
title: "OpenAMRobot 2.0 Decision Addendum rev20.1, with the platform lead's decisions of 30 October 2026 (earlier revision; superseded by rev20.2 as the addendum in force; carries the rev20.0 items 15, 17 and 18 head-camera values; item 24: whole chest layout, including the ZX80 operator panel correction of 28 October 2026)"
evidence: plan-set document, not held in any repository; provenance only, CI never reads it
Alex decision 2026-11-03:
title: Platform decision of 3 November 2026 (rear power module per the rear power owner's layout report rev 2 with busbars; BMS in the right side gap; FB-A Blue Sea 5046 and FB-B SafetyHub 150; K1/K2 option A GX11CAC decided, option B rejected on fit; 15 mm gap above the wireless-charging receiver with non-metal parts within 20 mm; flag rod guide on the static column), modelled in openamrobot-docs #71
evidence: decision record and the rear power owner's layout report rev 2 (3 Nov 2026), not held in any repository; provenance only, CI never reads it; to be entered in P-03 (in_force stays P-03-rev20.2)
Alex decision 2026-11-02:
title: Platform decision of 2 November 2026 (wireless charging prepared in 2.0 with the receiver installed later, manual SB50 charging, docking approach; ZX80 portrait only on a fixed mount; head camera 57 mm; second E-stop on the adapter plate; battery trays; lift sensors, adapter plate and base plate; tyre compression); change request openAMRobot/.github#83
evidence: decision record, not held in any repository; provenance only, CI never reads it; to be entered in P-03 (in_force stays P-03-rev20.2)
Alex decision 2026-10-30:
title: Platform decision of 30 October 2026 (UI manual velocity input and stop lock, status vocabulary, stop scope, UI Gate A date); change request openAMRobot/.github#72
evidence: decision record, not held in any repository; provenance only, CI never reads it; recorded with P-03 rev20.1
E-01-rev1.5:
title: E-01 Safety and Power Distribution Baseline rev1.5 ("E-stop" means only the hardwired buttons)
evidence: plan-set document, not held in any repository; provenance only, CI never reads it
P-03-rev20.0:
title: "OpenAMRobot 2.0 Decision Addendum rev20.0, 27 October 2026, with the 28 October 2026 corrections (earlier revision; superseded by rev20.1 as the addendum in force; items 15, 17 and 18: head-camera lens 42 mm ahead of the shoulder, baseline pitch 30 degrees, hp30; item 24: second E-stop on the static lift column)"
evidence: plan-set document, not held in any repository; provenance only, CI never reads it
Alex decision 2026-10-20:
title: Platform decision of 20 October 2026 (TF-Luna cliff pitch 10 degrees; WCM-500-24 on release 001 and 2.0; embodied-AI repository; platform-sw pin for the combined model)
evidence: decision record, not held in any repository; provenance only, CI never reads it; to be recorded in the next P-03 revision
Alex decision 2026-10-19:
title: Platform decision of 19 October 2026 (one shared base electrical design for release 001 and 2.0)
evidence: decision record, not held in any repository; provenance only, CI never reads it; to be recorded in the next P-03 revision
Alex decision 2026-10-16:
title: Platform decision of 16 October 2026 (base camera pose, imu_link and LiDAR stack as built, from CAD Rev B, platform-hw #20; imu_link pose and orientation from platform-sw #70); recorded in P-03 rev19.4 item 19 D3, D4 and D5
evidence: decision record, not held in any repository; provenance only, CI never reads it
Alex decision 2026-10-12:
title: Platform decision of 12 October 2026 (sensor layout, base camera, IMU, column position, LiDAR mount, drive track); history, recorded in P-03 rev19.0 item 19
evidence: decision record, not held in any repository; provenance only, CI never reads it
P-03-rev18.2:
title: P-03 Decision Addendum, revision 18.2, 28 September 2026 (earlier revision; superseded by revision 18.7 as the addendum in force)
evidence: >-
Not held in any repository. Confirmed by the platform lead on 29 September 2026
as the addendum in force at that date. Values that cite it were seeded from its citation on the
documentation site (openamrobot-docs main e0f2aac,
docs/reference/openamrobot-2/index.md lines 30-39) and from that confirmation.
P-03-rev18.4:
title: P-03 Decision Addendum, revision 18.4 (earlier revision)
evidence: plan-set document, not held in any repository; cited by item
P-03-rev19.6:
title: "OpenAMRobot 2.0 Decision Addendum rev19.6, 18 October 2026 (earlier revision; item 22: Gigavac GX11CAC contactors and the item 22 controller I/O)"
evidence: plan-set document, not held in any repository; cited by item
E-01-rev1.3:
title: E-01 Safety and Power Distribution Baseline rev1.3, 18 October 2026 (detail for P-03 rev19.6 item 22)
evidence: plan-set document, not held in any repository; provenance only, CI never reads it
P-03-rev19.2:
title: "OpenAMRobot 2.0 Decision Addendum rev19.2, 15 October 2026 (earlier revision; item 20: E-stop scope, single RESET button, wireless charging, battery faults)"
evidence: plan-set document, not held in any repository; cited by item
P-03-rev19.4:
title: "OpenAMRobot 2.0 Decision Addendum rev19.4, 16 October 2026 (earlier revision; item 19 updates of 16 October: base camera D3, LiDAR mount D4, imu_link D5, from CAD Rev B)"
evidence: plan-set document, not held in any repository; cited by item
E-01-rev1.1:
title: E-01 Safety and Power Distribution Baseline rev1.1, 15 October 2026 (detail for P-03 item 20)
evidence: plan-set document, not held in any repository; provenance only, CI never reads it
P-03-rev19.0:
title: P-03 Decision Addendum, revision 19.0, 12 October 2026 (earlier revision; item 19 records the 12 October decisions D1 to D6)
evidence: plan-set document, not held in any repository; cited by item
P-03-rev18.9:
title: P-03 Decision Addendum, revision 18.9, 9 October 2026 (earlier revision)
evidence: plan-set document, not held in any repository; cited by item
P-03-rev18.8:
title: P-03 Decision Addendum, revision 18.8, 8 October 2026 (earlier revision)
evidence: plan-set document, not held in any repository; cited by item
P-03-rev18.7:
title: P-03 Decision Addendum, revision 18.7, 6 October 2026 (earlier revision)
evidence: plan-set document, not held in any repository; cited by item
P-03-rev18.6:
title: P-03 Decision Addendum, revision 18.6 (earlier revision)
evidence: plan-set document, not held in any repository; cited by item
P-03-rev18.5:
title: P-03 Decision Addendum, revision 18.5, 6 October 2026 (earlier revision)
evidence: plan-set document, not held in any repository; cited by item
P-03-rev18.3:
title: P-03 Decision Addendum, revision 18.3 (earlier revision)
evidence: plan-set document, not held in any repository; cited by item
P-03-rev18.1:
title: P-03 Decision Addendum, revision 18.1
evidence: plan-set document, not held in any repository; cited by item and line
P-00-rev18.1:
title: P-00 Master Coordination Plan, revision 18.1
evidence: plan-set document, not held in any repository; cited by text line
BOM-Issue-7.10:
title: OpenAMRobot 2.0 Detailed Hardware BOM, Issue 7.10, 18 October 2026 (earlier issue; canonical per P-03 rev19.6)
evidence: not held in any repository; provenance only, CI never reads it
BOM-Issue-7.8:
title: OpenAMRobot 2.0 Detailed Hardware BOM, Issue 7.8, 15 October 2026 (earlier issue; canonical per P-03 rev19.2)
evidence: not held in any repository; provenance only, CI never reads it
BOM-Issue-7.7:
title: OpenAMRobot 2.0 Detailed Hardware BOM, Issue 7.7, 12 October 2026 (earlier issue; canonical per P-03 rev19.0)
evidence: not held in any repository; provenance only, CI never reads it
BOM-Issue-7.6:
title: OpenAMRobot 2.0 Detailed Hardware BOM, Issue 7.6, 9 October 2026 (earlier issue; canonical per P-03 rev18.9)
evidence: not held in any repository; provenance only, CI never reads it
BOM-Issue-7.3:
title: OpenAMRobot 2.0 Detailed Hardware BOM, Issue 7.3 (earlier issue; canonical per P-03 rev18.7)
evidence: not held in any repository; provenance only, CI never reads it
BOM-Issue-7:
title: OpenAMRobot 2.0 Detailed Hardware BOM, Issue 7, 27 September 2026 (earlier issue; canonical per P-03 rev18.2 item 7 until Issue 7.3)
evidence: not held in any repository; provenance only, CI never reads it
I8-WP:
title: I8 base-controller status work package
evidence: plan-set work package, not held in any repository
DOCK-WP:
title: 2.0 docking work package
evidence: plan-set work package, not held in any repository
# Never scanned: this register, checker fixtures, change logs and the Watchdog guide
# (WATCHDOG.md quotes findings and its accepted-words table is generated from this register).
exclude:
- decisions.yaml
- WATCHDOG.md
- tests/fixtures/**
- "**/CHANGELOG.md"
- agent-runs.md
decisions:
- id: BOM-ISSUE-IN-FORCE
title: Canonical hardware BOM issue for OpenAMRobot 2.0
summary: "BOM Issue 7.14 is the canonical 2.0 procurement BOM; Issue 7.15 is the source of the public roadmap parts extract."
fix_hint: "Name Issue 7.14 as canonical; Issue 7.15 only as the roadmap parts extract source; label older issues as superseded."
kind: value
status: recorded
value: OpenAMRobot 2.0 Detailed Hardware BOM, Issue 7.14 (27 October 2026, with the 1 November 2026 changes)
public_extract:
source: BOM-Issue-7.15
scope: "the public roadmap parts extract in openamrobot-docs (hardware page PARTS, embedded part details, bom_coverage.csv, mass_export.yaml bom_issue) is imported from BOM Issue 7.15"
canonical: "no: Issue 7.14 stays the canonical procurement baseline until the BOM owner confirms Issue 7.15 (not recorded in this register as of 2026-11-10)"
unit: none
date: 2026-11-01
review_by: 2026-12-13
source: {document: P-03-rev20.2, item: "item 26 (BOM Issue 7.14)"}
supersedes:
- {value: Issue 7.11, source: "earlier issue; replaced by Issue 7.14 per P-03-rev20.2 item 26"}
- {value: Issue 7.10, source: "P-03-rev19.6 BOM issue in force (BOM Issue 7.10)"}
- {value: Issue 7.8, source: "P-03-rev19.2 BOM issue in force (BOM Issue 7.8)"}
- {value: Issue 7.7, source: "P-03-rev19.0 BOM issue in force (BOM Issue 7.7)"}
- {value: Issue 7.6, source: "P-03-rev18.9 item 16 (BOM Issue 7.6 carries the change)"}
- {value: Issue 7.3, source: P-03-rev18.7 BOM issue in force}
- {value: Issue 7, source: P-03-rev18.2 item 7}
- value: Issue 6, or an explicitly approved successor
source: P-03-rev18.1 line 7
citation: '(?P<found>P-03[^\n]{0,30}(?:rev(?:ision)?\.?\s*)?18\.1[^\n]{0,30}line\s*7)'
- {value: B-01 development BOM and evidence register rev18, source: P-03-rev18.1 line 7}
applies_to: {repositories: ["*"], files: ["**/*.md", "**/*.html", "**/*.yaml", "**/*.yml"]}
check:
- pattern: '(?P<found>(?:canonical|in force|of record)[^\n]{0,40}\bIssue\s*6\b|\bIssue\s*6\b[^\n]{0,40}\b(?:canonical|in force|of record))'
unless: 'supersed|replaced|previous|earlier'
message: BOM Issue 7.14 is the canonical hardware BOM (P-03 rev20.2 item 26)
- pattern: '(?P<found>B-01[^\n]{0,60}\b(?:canonical|current))'
unless: 'supersed'
message: B-01 is superseded
- pattern: '(?P<found>(?:canonical|in force|of record)[^\n]{0,40}\bIssue\s*7(?!\.14\b)(?:\.\d+)?\b|\bIssue\s*7(?!\.14\b)(?:\.\d+)?\b[^\n]{0,40}\b(?:canonical|in force|of record))'
unless: 'supersed|replaced|previous|earlier|historical'
message: BOM Issue 7.14 is the canonical hardware BOM; Issue 7 to 7.13 (including 7.10 and 7.11) are retired, and Issue 7.15 is the roadmap parts extract source, not canonical (P-03 rev20.2 item 26)
verification:
machine: Issue 6, Issue 7 to 7.13 (including 7.10 and 7.11) or B-01 presented as the canonical BOM; citations of P-03 rev18.1 line 7
human: {reviewer: platform-lead, evidence: the BOM file header and issue number in the released BOM}
owner: platform-lead
- id: MAST-INSTALL-HEIGHT
title: Shoulder-axis installation height of the fixed mast (superseded by LIFT)
summary: "Superseded: the fixed-mast 1350 mm installation height was replaced by LIFT."
fix_hint: "Describe the lift (shoulder axis 1000 to 1350 mm), or label the fixed-mast text as superseded or historical."
kind: configuration
status: superseded
value: 1350
unit: mm
configuration_id: mast_1350
date: 2026-09-28
review_by: 2026-11-09
source: {document: P-03-rev18.2, item: shoulder height}
supersedes:
- value: 1400
configuration_id: mast_1400
source: P-03-rev18.1 item 6 line 15
citation: '(?P<found>P-03[^\n]{0,30}(?:rev(?:ision)?\.?\s*)?18\.1[^\n]{0,30}item\s*6)'
- {value: 1300, configuration_id: mast_1300, source: working baseline before P-03-rev18.1 item 6}
applies_to:
repositories: ["*"]
files: ["**/*.md", "**/*.yaml", "**/*.yml", "**/*.xacro", "**/*.urdf", "**/*.launch.py", "**/package.xml", "**/*.html"]
superseded_by:
document: P-03-rev18.7
item: item 8
decision: LIFT
citation: '(?P<found>\bmast_1350\b[^\n]{0,60}\b(?:baseline|installation)|(?:shoulder[- ]axis|installation) height\s*(?:at|of|is|:)?\s*1350\s*mm)'
unless: 'supersed|legacy|historical|earlier|previous|rev ?18\.[1-6]\b|\blift\b|L1350|extended|full stroke'
verification:
machine: text still presenting the superseded fixed-mast value as current (citation pattern)
human: {reviewer: platform-lead, evidence: URDF/Xacro mast configuration and the general arrangement drawing at 1350 mm}
owner: platform-lead
- id: MAST-POSITIONS
title: Indexed mast mounting positions (superseded by LIFT)
summary: "Superseded: the indexed fixed-mast positions were replaced by LIFT."
fix_hint: "Describe the lift positions, or label mast_1300/1400/1450 text as superseded or historical."
kind: configuration
status: superseded
values: [1300, 1350, 1400, 1450]
unit: mm
step_mm: 50
date: 2026-09-28
review_by: 2026-11-09
source: {document: P-03-rev18.2, item: shoulder height}
supersedes:
- {value: nine positions 1300 to 1700 mm (mast_1300 to mast_1700), source: P-00-rev18.1 txt 293-294}
applies_to:
repositories: ["*"]
files: ["**/*.md", "**/*.yaml", "**/*.yml", "**/*.xacro", "**/*.urdf", "**/*.launch.py", "**/*.html"]
superseded_by:
document: P-03-rev18.7
item: item 8
decision: LIFT
citation: '(?P<found>\bmast_1(?:300|400|450)\b|\b(?:four|4) indexed (?:mast )?(?:mounting )?positions|\bindexed mast (?:mounting )?positions)'
unless: 'supersed|legacy|historical|earlier|previous|rev ?18\.[1-6]\b'
verification:
machine: text still presenting the superseded fixed-mast value as current (citation pattern)
human: {reviewer: platform-lead, evidence: mast drawing with index holes}
owner: platform-lead
- id: MAST-TOP-HEIGHT
title: Mast top height above the floor (own COTS mast, one MISUMI HFS6-60120 profile; superseded by LIFT)
summary: "Superseded: the 1500 mm mast top on an HFS6-60120 profile was replaced by LIFT."
fix_hint: "Describe the lift; HFS6-60120 is now the short arm profile on the lift (ARM-MOUNT), not a mast."
kind: value
status: superseded
value: 1500
unit: mm
date: 2026-09-28
review_by: 2026-11-09
source: {document: P-03-rev18.2, item: mast}
supersedes:
- {value: 1554, source: general arrangement before 28 September 2026}
applies_to:
repositories: ["*"]
files: ["**/*.md", "**/*.yaml", "**/*.yml", "**/*.html", "**/*.xacro", "**/*.urdf"]
superseded_by:
document: P-03-rev18.7
item: item 8
decision: LIFT
citation: '(?P<found>\bmast top[^\n]{0,20}\b1500\s*mm|\bHFS6-60120\b[^\n]{0,60}\b(?:mast|centre bracket|center bracket)\b)'
unless: 'supersed|legacy|historical|earlier|previous|rev ?18\.[1-6]\b'
verification:
machine: text still presenting the superseded fixed-mast value as current (citation pattern)
human: {reviewer: platform-lead, evidence: mast drawing and CAD}
owner: platform-lead
- id: MAX-ASSEMBLED-HEIGHT
title: 1700 mm is the maximum assembled-height envelope, not a shoulder-axis height
summary: "1700 mm is the maximum assembled-height envelope, not a shoulder height."
fix_hint: "Use 1700 mm only as the assembled-height envelope; give shoulder heights from the LIFT entry."
kind: distinction
status: recorded
value: 1700
unit: mm
date: null
review_by: 2026-11-18 # six weeks after this register update (2026-10-07)
source: {document: P-03-rev18.7, item: item 8}
note: First recorded in P-03-rev18.1 item 6 line 15 and repeated in rev18.2; kept unchanged by rev18.7 item 8 with the lift. The robot may be lower, never higher.
applies_to:
repositories: ["*"]
files: ["**/*.md", "**/*.yaml", "**/*.yml", "**/*.html", "**/*.xacro", "**/*.urdf"]
check:
- pattern: '(?P<found>max(?:imum)?\s+(?:assembled\s+|robot\s+)?height\s*(?:of|is|:)?\s*(?!1700)1\d{3}\s*mm)'
message: maximum assembled height is 1700 mm
- pattern: '(?P<found>(?:shoulder[- ]axis|shoulder height|mast_)[^\n]{0,20}\b1700\b)'
unless: 'max|envelope|not (?:the )?shoulder|higher|supersed'
message: 1700 mm is the assembled-height envelope, not a shoulder height or mast position
verification:
machine: another maximum-height value, or 1700 mm presented as a shoulder height or mast position
human: {reviewer: platform-lead, evidence: assembled-height measurement on the general arrangement}
owner: platform-lead
- id: DATUM-HEIGHT-STACK
title: Height datum and base height stack
summary: "Floor Z = 0; steel deck top 294 mm; lift base-plate top face 304 mm is the height reference."
fix_hint: "Use 294 mm for the deck top and 304 mm for the base-plate top face, or label old values as historical."
kind: configuration
status: recorded
values:
- floor Z = 0
- steel chassis deck top 294 mm (MMP STEP)
- top cover 2 mm plastic, or optional 0.5 to 0.8 mm sheet metal
- 10 mm aluminium lift base plate bears on the steel deck; the cover is cut out around it
- base-plate top face 304 mm is the reference for lift and shoulder heights
unit: mm
date: 2026-10-06
review_by: 2026-11-17
source: {document: P-03-rev18.7, item: item 15}
applies_to: {repositories: ["*"], files: ["**/*.md", "**/*.yaml", "**/*.yml", "**/*.html", "**/*.xacro", "**/*.urdf"]}
check:
- pattern: '(?P<found>\bdeck top\b[^\n]{0,25}?\b(?!294\b)\d{3}\s*mm)'
unless: 'supersed|historical|legacy|earlier|previous'
message: the steel chassis deck top is 294 mm above the floor (P-03 rev18.7 item 15)
- pattern: '(?P<found>\bbase[- ]plate top(?: face)?\b\s*(?:is\s*|at\s*|of\s*|=\s*|:\s*)?(?:z\s*=?\s*)?(?!304\b)\d{3}\s*mm)'
unless: 'supersed|historical|legacy|earlier|previous'
message: the lift base-plate top face is 304 mm above the floor, the reference for lift and shoulder heights (P-03 rev18.7 item 15)
verification:
machine: a deck-top height other than 294 mm or a base-plate top face other than 304 mm
human: {reviewer: platform-lead, evidence: MMP STEP deck height and the lift base-plate drawing}
owner: platform-lead
- id: FRAMES-REP105
title: Base frames follow REP 105
summary: "REP 105: base_footprint on the floor, base_link at the axle midpoint, imu_link away from motors."
fix_hint: "Place base_footprint on the floor, base_link at axle height, and imu_link on the centreline away from motors."
kind: configuration
status: recorded
values:
- base_footprint on the floor under the drive-axle midpoint
- base_link at the drive-axle midpoint and axle height; x forward, z up
- base_link 0.098 m above the floor (axle height; moved here from CAMERAS on 20 Oct 2026, value unchanged, P-03 rev19.4 item 19 D3)
- "wheel radius 0.100 m with base_link at 0.098 m is intended: 2 mm tyre compression, no suspension (Alex decision 2026-11-02)"
- imu_link on the centreline, away from motor magnetic fields
- "imu_link (0.0544, 0, 0.1210) m from base_link, rpy (0, 0, -pi/2), yaw -90 deg (unchanged): ICM-42688-P on the TDK EV_ICM-42688-P board (replaces MIKROE-4237, P-03 rev20.2 item 26), chip mounted +Y forward, on the electronics bracket MMP.04.00.00.002, centreline, 54.4 mm ahead of the drive axle, chip centre 165.043 mm above the base-plate top, 219.04 mm above the floor"
- "the IMU publishes raw sensor-frame values; the axis mapping is in the URDF (sensor X to base -y, Y to +x, Z to +z); no firmware remap"
unit: none
date: 2026-11-02
review_by: 2026-12-14
source: {document: Alex decision 2026-11-02, item: "wheel radius 0.100 m with base_link 0.098 m (2 mm tyre compression); IMU board per P-03-rev20.2 item 26 (TDK EV_ICM-42688-P, chip +Y forward; pose unchanged); imu_link pose per P-03-rev19.4 item 19 D5 update (Alex decision 16 Oct 2026, platform-sw #70)"}
supersedes:
- {value: "base_link 0.098 m above the floor (axle height); wheel radius and tyre compression not recorded", source: "P-03-rev19.4 item 19 D3; completed by Alex decision 2026-11-02"}
- {value: "imu_link (0.0544, 0, 0.1210), yaw -90 deg: ICM-42688-P on MIKROE-4237", source: "P-03-rev19.4 item 19 D5 update; board replaced by P-03-rev20.2 item 26"}
- {value: "(0.0544, 0, 0.133), rpy 0", source: "measured against a displaced base plate in the CAD; superseded by Alex decision 16 Oct 2026 (platform-sw #70)"}
- {value: "(0.195, 0, -0.044) plus board stack", source: "Alex decision 12 Oct 2026, superseded by Alex decision 16 Oct 2026 (CAD Rev B, platform-hw #20)"}
applies_to: {repositories: ["*"], files: ["**/*.md", "**/*.yaml", "**/*.yml", "**/*.html", "**/*.xacro", "**/*.urdf", "**/*.launch.py"]}
check:
- pattern: '(?P<found>\bbase_link\b[^\n]{0,30}\b(?:on|at) the floor\b)'
unless: 'base_footprint|\bnot\b|never|supersed|historical|legacy'
message: base_link is at the drive-axle midpoint and axle height; base_footprint is on the floor (P-03 rev18.7 item 15)
- pattern: '(?P<found>\bbase_footprint\b[^\n]{0,30}\bat (?:the )?axle height\b)'
unless: '\bnot\b|never|supersed|historical|legacy'
message: base_footprint is on the floor under the drive-axle midpoint (P-03 rev18.7 item 15)
- pattern: '(?P<found>\bimu_link\b[^\n]{0,40}\b(?:next to|beside|on|near|above) the (?:drive |hub |wheel )?motors?\b)'
unless: '\baway\b|\bnot\b|never|supersed|historical|legacy'
message: imu_link sits on the centreline away from motor magnetic fields (P-03 rev18.7 item 15)
# Robot-description files only; BASE-CONTROLLER-GATES carries the same check for text files.
- pattern: '(?P<found>\bMIKROE-?4237\b)'
files: ["**/*.xacro", "**/*.urdf", "**/*.launch.py"]
unless: 'supersed|replac|historical|legacy|earlier|previous|no longer|\bwas\b|instead of'
message: the imu_link board is the TDK EV_ICM-42688-P; MIKROE-4237 is superseded (P-03 rev20.2 item 26)
verification:
machine: base_link placed on the floor, base_footprint at axle height, imu_link next to a motor, or MIKROE-4237 presented as current in a robot-description file
human: {reviewer: robot-description-owner, evidence: URDF frame tree and real TF on the robot matching REP 105}
owner: platform-lead
- id: NEAR-FIELD-FRAMES
title: Near-field ultrasonic and ToF sensor frames on the base panels
summary: "Four MB7060 us_* at x +/-0.390 (panel face), y +/-0.130; two TF-Luna tof_* at x +/-0.399 (lens face), 10 deg down."
fix_hint: "Use the listed frame origins; the ToF pitch is 10 degrees down, confirmed in the bench test."
kind: value
status: recorded
values:
- us_front_left (0.390, +0.130, -0.0066), us_front_right (0.390, -0.130, -0.0066), us_rear_left (-0.390, +0.130, -0.0066, yaw pi), us_rear_right (-0.390, -0.130, -0.0066, yaw pi) from base_link; confirmed flush with the panel outer face (the CAD offsets +0.6 / -1.4 mm only reflect the sensor depth in the lock nut)
- "ultrasonic mounting: MB7060 holes 27.5 mm on the existing centres, sensor centred, 3/4 inch NPS lock nut, tilt 0 until the bench test"
- tof_front (0.399, 0, -0.0066) and tof_rear (-0.399, 0, -0.0066, yaw pi) from base_link: lens face 9 mm ahead of the panel on mount MMP.00.00.00.005, pitched 10 degrees down; in the existing 22.0 mm front centre hole and a new 22.0 mm rear centre hole
- both ToF sensors pitched 10 degrees down; from 91.4 mm above the floor the beam meets the floor about 0.52 m ahead (0.47 to 0.58 m over the 2 degree beam); the bench test confirms the return on real floors
unit: m
date: 2026-10-20
review_by: 2026-12-01
source: {document: Alex decision 2026-10-20, item: "Alex decision 2026-10-20 (ToF pitch) and robot-description owner confirmation 2026-10-20 (frame x values); y and height from P-03 rev19.0 item 19"}
supersedes:
- {value: "both ToF sensors pitched 20 degrees down (screening value)", source: "P-03-rev19.0 item 19 D6"}
- {value: "tof_* at x +/-0.390", source: "P-03-rev19.0 item 19 D6"}
applies_to: {repositories: ["openamr-platform-*", "openamrobot-docs"], files: ["**/*.md", "**/*.yaml", "**/*.yml", "**/*.html", "**/*.xacro", "**/*.urdf"]}
check:
- pattern: '(?P<found>\b(?:tof_(?:front|rear)|TF-Luna)\b[^\n]{0,60}?\b20\s*(?:°|deg(?:rees?)?))'
unless: 'supersed|replac|previous|earlier|historical|instead of|was 20|from 20'
message: the ToF cliff pitch is 10 degrees down, not 20 (Alex decision 20 Oct 2026)
- pattern: '(?P<found>\b(?:tof_(?:front|rear)|TF-Luna)\b[^\n]{0,60}?\b10\s*(?:°|deg(?:rees?)?)[^\n]{0,40}?\b(?:final|validated|confirmed)\b)'
unless: 'bench|until'
message: the 10 degree ToF pitch is confirmed only by the bench test (Alex decision 20 Oct 2026)
verification:
machine: a 20 degree ToF pitch presented as current, or the 10 degree pitch presented as validated before the bench test
human: {reviewer: robot-description-owner, evidence: Rev B panel drawing and URDF joint origins}
owner: platform-lead
- id: BATTERY-PLACEMENT
title: Battery pack and placement
summary: "8 x LF105, 8S, 25.6 V, 105 Ah, in two removable 4-cell trays in the rear side pockets, joined by PWR-018."
fix_hint: "Describe two removable 4-cell trays in the rear side pockets; label the single row of 8 cells as superseded."
kind: value
status: recorded
values:
- 8 x EVE LF105 LiFePO4 cells, 8S, 25.6 V, 105 Ah, in two removable trays of 4 cells in the rear side pockets, joined by the keyed main connector PWR-018
- "rear power module above the wireless-charging receiver position (see CHARGING): F0 (Blue Sea 5007100 holder with the 5112 110 A fuse) across the plate front next to pack +; QS1 (BS-6004B) through the rear panel; BUS+ (PWR-017), K1, K2 and FB-B in one line; short stud-to-stud links as insulated copper busbars"
- "BMS (Daly M-series 8S 150 A, catalogue outline 164 x 66 x 21 mm, to verify on the delivered order code) on edge in the gap between the pack - tray (right) and the right side wall; serviced through the removable right side panel"
- "FB-B (SAFE bus) is the Blue Sea 7748 SafetyHub 150: F-TRAC 40 A, F-ARM-L 30 A, F-ARM-R 30 A (MIDI), F-LIFT 15 A (ATO); FB-A (BAT bus) is a Blue Sea 5046 8-way blade block: F-J401 10 A, F-5V 5 A, F-24V 7.5 A, on a shelf above K1/K2, fuses up"
- nothing on top of the cells
unit: none
date: 2026-11-03
review_by: 2026-12-15
source: {document: Alex decision 2026-11-03, item: "builds on the decision of 2 Nov 2026; battery trays in the rear side pockets; rear power module per the rear power owner's layout report rev 2 (3 Nov 2026), modelled in openamrobot-docs #71; pack per P-03-rev18.7 item 9"}
supersedes:
- {value: "BMS and power distribution on a plate above the wireless-charging receiver position", source: "Alex decision 2026-11-02; refined by the rear power owner's layout report rev 2 (3 Nov 2026)"}
- {value: "One 8S1P EVE LF105 LiFePO4 pack, 25.6 V, 105 Ah, a single row of 8 cells across the robot, placed as close to the rear edge as practical while preserving enclosure, service and safety clearances", source: "P-03-rev18.7 item 9; replaced by Alex decision 2026-11-02"}
- {value: fit the existing battery bay first, source: P-00-rev18.1 txt 77}
- {value: centred at 25 percent of the robot length from the rear, source: P-03-rev18.2 battery}
applies_to: {repositories: ["*"], files: ["**/*.md", "**/*.yaml", "**/*.yml", "**/*.html"]}
check:
- pattern: '(?P<found>battery[^\n]{0,40}\bcent(?:red|ered) at \d+\s*(?:%|percent)|\b25\s*(?:%|percent) of the (?:robot )?length from the rear)'
unless: 'supersed|historical|previous|earlier|rev ?18\.[1-6]\b'
message: the battery is in two removable 4-cell trays in the rear side pockets (Alex decision 2026-11-02)
- pattern: '(?P<found>\b(?:single|one) row of (?:8|eight) (?:LF105 |EVE LF105 )?cells\b|\b(?:8|eight) (?:LF105 |EVE LF105 )?cells (?:in (?:a|one) (?:single )?row|across the robot)\b)'
unless: 'supersed|historical|previous|earlier|replac|\bwas\b|no longer'
message: the 8 LF105 cells are in two removable trays of 4 in the rear side pockets, joined by PWR-018; the single row is superseded (Alex decision 2026-11-02)
verification:
machine: a battery centred at a fixed percentage of the length, including the superseded 25 percent position, or the cells in a single row of 8 presented as current
human: {reviewer: platform-lead, evidence: general arrangement, battery tray drawing with PWR-018 and the mass model}
owner: platform-lead
note: The rev18.1 plan set did not record a placement; P-03 rev18.2 recorded 25 percent; rev18.7 item 9 replaced it with a pack as close to the rear edge as practical; Alex decision 2026-11-02 replaces that with two trays in the rear side pockets.
- id: SPEED-CEILING
title: Build 1 base speed ceiling 0.5 m/s; 1.5 m/s is the analytical command ceiling
summary: "Build 1 base speed ceiling 0.5 m/s until measured stop acceptance; 1.5 m/s is the analytical command ceiling."
fix_hint: "Cap the base at 0.5 m/s until the measured stop tests pass; call 1.5 m/s the analytical command ceiling."
kind: limit
status: recorded
values:
- "Build 1 base speed ceiling 0.5 m/s until the measured stop acceptance (stop distance at most 0.15 m); there is no 0.3 m/s cap"
- "physical stop tests in steps of 0.2, 0.3 and 0.5 m/s; the full delay chain from E-stop to brake grip is measured"
- "the brake coils get a fast quench (TVS or zener), not a plain flyback diode"
- 1.5 m/s stays the command ceiling, treated as an analytical limit, not an accepted operating speed
unit: m/s
date: 2026-11-08
review_by: 2026-12-20
source: {document: P-03-rev20.6, item: "item 30 (decision D-07 and platform-lead ruling A5, 8 Nov 2026); 0.5 m/s ceiling from P-03-rev20.5 item 29; 1.5 m/s command ceiling per P-03-rev18.2"}
supersedes:
- {value: "1.5 m/s command ceiling as the only speed limit", source: "P-03-rev18.2; replaced by P-03-rev20.5 item 29 (0.5 m/s base ceiling until measured stop acceptance)"}
- {value: 1.5 m/s treated as an accepted operating speed, source: P-00-rev18.1 txt 60 and 352}
applies_to: {repositories: ["*"], files: ["**/*.md", "**/*.yaml", "**/*.yml", "**/*.html"]}
check:
- pattern: '(?P<found>software speed limit\s*(?:of\s*)?1\.5\s*m/s)'
unless: 'ceiling|analytical'
message: 1.5 m/s is a command ceiling, not an operating limit
- pattern: '(?P<found>(?:operating|validated|rated) speed\s*(?:of|is|:)?\s*1\.5\s*m/s)'
unless: 'ceiling|analytical|not'
message: 1.5 m/s is not an accepted operating speed
- pattern: '(?P<found>\b0\.3\s*m/s (?:speed |base )?(?:cap|ceiling)\b)'
unless: '\bno\b|\bnot\b|supersed|historical|\bwas\b|earlier|previous'
message: the Build 1 base speed ceiling is 0.5 m/s until measured stop acceptance; there is no 0.3 m/s cap (P-03 rev20.6 item 30, ruling A5)
verification:
machine: 1.5 m/s presented as a software or operating speed limit in text; a 0.3 m/s base cap presented as current
human: {reviewer: platform-lead, evidence: "recorded stop tests at 0.2, 0.3 and 0.5 m/s with the measured delay chain from E-stop to brake grip; configured velocity limits in Nav2, the smoother, the ZLAC8015D and Gazebo at or below 0.5 m/s"}
owner: platform-lead
- id: DRIVETRAIN
title: Drivetrain
summary: "Two ZLTECH ZLLG80ASM250-L-B hub motors with brakes, one ZLAC8015D driver on CAN1."
fix_hint: "Name the ZLLG80ASM250-L-B; brakes 6 Nm per ZLTECH 18 Oct 2026 (5 vs 6 Nm open, D-25); fail-safe needs evidence."
kind: value
status: recorded
values:
- Two ZLTECH ZLLG80ASM250-L-B hub motors with brakes, one ZLAC8015D V4.2 driver on CAN1 (CANopen), 200 mm wheels
- "hub-motor brakes (ZLTECH 18 Oct 2026): 24 V, 12.5 W per motor, 6 Nm holding, release at most 100 ms, engagement at most 30 ms without diode"
- "open question (decision D-25, openamr-platform-hw issue #14): 5 Nm (ZLTECH email 21 Sep 2026) and 100 kg per pair (drawing) against 6 Nm and 120 kg per pair (written answer 18 Oct 2026); the dynamic-stop duty of the brake is not answered; brake release gating is decided by the electrical owner"
unit: none
date: 2026-11-08
review_by: 2026-12-13
source: {document: P-03-rev20.6, item: "item 30 (D-25 evidence hold, 8 Nov 2026); hub-motor brake data per P-03-rev20.2 item 26 (ZLTECH 18 Oct 2026); motors and driver per P-00-rev18.1 txt 16"}
supersedes:
- {value: "brake ratings pending supplier evidence", source: "P-00-rev18.1 txt 16 (register fix_hint until P-03-rev20.2 item 26)"}
applies_to:
repositories: ["openamr-platform-*", "openamr-upperbody-*", "openamrobot-docs", "openamrobot-release", ".github"]
files: ["**/*.md", "**/*.yaml", "**/*.yml", "**/*.html", "**/*.xacro", "**/*.urdf"]
check:
- pattern: '(?P<found>ZLLG80ASM250-L)(?!-B)\b'
message: the selected motor variant is ZLLG80ASM250-L-B
- pattern: '(?P<found>ZL ?TECH[^\n]{0,40}\b(?:alternative|option(?:al)?)\b)'
message: ZLTECH is the selected 2.0 drivetrain, not an option
- pattern: '(?P<found>fail-safe brakes?)'
unless: 'pending|F2A|verif|not yet|unverified'
message: brake ratings are recorded (ZLTECH 18 Oct 2026); the fail-safe behaviour still needs verification evidence
verification:
machine: the unbraked motor variant, ZLTECH described as optional, brakes described as fail-safe
human: {reviewer: platform-lead, evidence: ZLTECH brake data of 18 Oct 2026 and supplier evidence of the fail-safe behaviour}
owner: platform-lead
- id: RS485-NOT-IN-2-0
title: Release 2.0 has no RS485 hardware, fallback, adapter or commissioning path
summary: "Release 2.0 has no RS485 hardware, fallback, adapter or commissioning path."
fix_hint: "Remove RS485 from 2.0 text, or label it as legacy, Gate A or not in 2.0."
kind: exclusion
status: recorded
value: none
unit: none
date: null
review_by: 2026-11-18 # six weeks after this register update (2026-10-07)
source: {document: P-03-rev18.1, item: item 4}
applies_to:
repositories: ["openamr-platform-hw", "openamr-platform-fw", "openamr-upperbody-*", "openamrobot-docs"]
files: ["**/*.md", "**/*.yaml", "**/*.yml", "**/*.html"]
check:
- pattern: '(?P<found>RS-?485)'
unless: 'not used|no RS-?485|not provisioned|without|legacy|Gate A|removed|not in 2\.0'
message: RS485 is not provisioned in 2.0
- pattern: '(?P<found>CAN or serial)'
message: CAN1 and CAN2 are dedicated; no upper-body serial link to the base
verification:
machine: RS485 mentioned without a negation or legacy label; "CAN or serial" links
human: {reviewer: platform-lead, evidence: wiring diagram and BOM without RS485 parts}
owner: platform-lead
- id: BASE-CONTROLLER-GATES
title: Base-controller gates and the 2.0 IMU
summary: "Gate A (Teensy, MPU6500) and Gate B (STM32H723ZG) stay distinct; the 2.0 IMU is the ICM-42688-P on EV_ICM-42688-P."
fix_hint: "Call Teensy and MPU6500 Gate A (legacy); 2.0 IMU board is TDK EV_ICM-42688-P on SPI4; MIKROE-4237 is superseded."
kind: distinction
status: recorded
values:
- Gate A, Jetson with the existing Teensy, ZBLD/PWM drivetrain and MPU6500 (legacy test configuration)
- Gate B, Jetson with the STM32H723ZG (NUCLEO-H723ZG bench board) and the ZLTECH drivers
- the ICM-42688-P on the TDK EV_ICM-42688-P board (SPI4, Mode 0) is the OpenAMRobot 2.0 IMU, WHO_AM_I 0x47 at boot; it replaces the MIKROE-4237 board (same sensor); the MPU6500 stays the Gate A (legacy) IMU
- no click shield on the NUCLEO-H723ZG; the IMU board and the CAN isolator are wired directly to SPI4 and FDCAN2
- STM32 go/no-go 6 November 2026; fallback is the validated legacy Teensy/PWM build behind I8
unit: none
date: 2026-11-01
review_by: 2026-12-13
source: {document: P-03-rev20.2, item: "item 26 (IMU board TDK EV_ICM-42688-P, no click shield); Gate A/B distinction and IMU per P-03-rev19.0 item 19 (base-controller IMU)"}
supersedes:
- {value: "the ICM-42688-P (MIKROE-4237, SPI) is the OpenAMRobot 2.0 IMU", source: "P-03-rev19.0 item 19 (base-controller IMU); board replaced by P-03-rev20.2 item 26"}
- {value: "ICM-42688-P enters the manufacturing BOM only after side-by-side robot evidence; adoption decision 20 November 2026", source: "P-00-rev18.1 txt 63, 101, 106, 344; I8-WP adoption gate"}
applies_to: {repositories: ["*"], files: ["**/*.md", "**/*.yaml", "**/*.yml", "**/*.html"]}
check:
- pattern: '(?P<found>Teensy[^\n]{0,20}\bbench target)'
message: Teensy is the Gate A controller and the release fallback, not a bench target
- pattern: '\b(?P<found>MPU6050)\b'
unless: 'would return|labeled|labelled|assumed|not a real|instead of|USE_MPU6050|driver'
message: the Gate A IMU is the MPU6500
- pattern: '(?P<found>\bMIKROE-?4237\b)'
unless: 'supersed|replac|historical|legacy|earlier|previous|no longer|\bwas\b|instead of'
message: the 2.0 IMU board is the TDK EV_ICM-42688-P on SPI4; MIKROE-4237 is superseded (P-03 rev20.2 item 26)
verification:
machine: Teensy called a bench target, MPU6050 named as the IMU, MIKROE-4237 presented as the current IMU board
human: {reviewer: platform-lead, evidence: "Gate A test log, STM32 go/no-go record, ICM-42688-P WHO_AM_I 0x47 boot log on the EV_ICM-42688-P over SPI4"}
owner: platform-lead
- id: BASE-CONTROLLER-IO
title: Base-controller MCU, sensor and IMU buses, CAN mapping and micro-ROS transport
summary: "STM32H723ZG; MB7060 on dedicated UARTs; CAN1/2/3 split; micro-ROS over UDP on Ethernet."
fix_hint: "Use the STM32H723ZG and MB7060 on UART; label STM32H743 or MB7040 text as superseded; USB is bench only."
kind: configuration
status: recorded
values:
- Base controller STM32H723ZG on NUCLEO-H723ZG
- four MaxBotix MB7060 XL-MaxSonar-WR (-2XX 3/4 inch NPS housing, RS232 output) in the front and back panel left and right edge holes, each on one dedicated STM32 UART at 9600 8N1 with receive inversion and one trigger GPIO
- two Benewake TF-Luna ToF cliff sensors in the front and back panel centre holes, one UART each, pin 5 tied to 3.3 V
- IMU on a dedicated SPI, Mode 0
- "CAN1 traction only, CAN2 BMS, CAN3 (FDCAN3, CANopen 500 kbit/s) to the upper-body controller CTL-017, node 0x10, a separate board (see UPPERBODY-CONTROLLER); no safety function on CAN3"
- MCU to Jetson over Ethernet, micro-ROS over UDP; USB for the bench only
unit: none
date: 2026-11-08
review_by: 2026-12-20
source: {document: P-03-rev20.6, item: "item 30 (decision D-11: CAN3 node CTL-017, 8 Nov 2026); sensor I/O per P-03-rev19.0 item 19"}
supersedes:
- {value: STM32H743 on NUCLEO-H743ZI2, source: P-00-rev18.1 (Gate B bench board)}
- {value: MB7040 one per I2C bus, source: P-03-rev18.5 item 14}
- {value: "TF-Luna on UART, one per UART", source: P-03-rev18.7 item 14}
- {value: "two MaxBotix MB7060 serial sensors, each on one dedicated STM32 UART, 9600 8N1; no sensor I2C off the controller board", source: P-03-rev18.7 item 14}
- {value: "CAN3 reserved for upper-body auxiliary actuators, the lift commanded by the base controller through a CAN-to-lift module", source: "P-03-rev20.2 item 24; replaced by P-03-rev20.5 item 29 (CTL-017, a separate upper-body controller)"}
applies_to: {repositories: ["*"], files: ["**/*.md", "**/*.yaml", "**/*.yml", "**/*.html"]}
check:
- pattern: '(?P<found>NUCLEO-H743ZI2|STM32H743)'
unless: 'supersed|legacy|historical|replaced'
message: the base controller is the STM32H723ZG on the NUCLEO-H723ZG; label STM32H743 / NUCLEO-H743ZI2 material as superseded
- pattern: '(?P<found>\bMB7040\b)'
unless: 'supersed|legacy|historical|replaced'
message: the ultrasonic sensors are four MaxBotix MB7060 on dedicated STM32 UARTs at 9600 8N1; no sensor I2C (P-03 rev19.0 item 19)
- pattern: '(?P<found>\bmicro-?ROS\b[^\n]{0,30}\bover (?:USB|serial)\b)'
unless: 'bench|legacy|Gate A|Teensy|supersed|historical'
message: micro-ROS runs over UDP on Ethernet between MCU and Jetson; USB is for the bench only (P-03 rev18.7 item 14)
- pattern: '(?P<found>\btwo MaxBotix MB7060\b|\b2\s*x\s*MB7060\b|\bfour TF-Luna\b|\b4\s*x\s*TF-Luna\b)'
unless: 'supersed|legacy|historical'
message: the base has four MaxBotix MB7060 (edge holes) and two TF-Luna ToF cliff sensors (centre holes) (P-03 rev19.0 item 19)
verification:
machine: NUCLEO-H743ZI2 or STM32H743 without a superseded, legacy, historical or replaced label; MB7040 without such a label; micro-ROS over USB or serial outside the bench or Gate A; two MB7060 or four TF-Luna as the current count
human: {reviewer: platform-lead, evidence: P-03 rev18.7 item 14 and the MCU I/O allocation in openamr-platform-hw}
owner: platform-lead
- id: IMU-TOPIC-OWNERSHIP
title: IMU topic ownership
summary: "Firmware publishes /imu/data_raw; the EKF reads it directly (yaw rate only); no host IMU filter in 2.0."
fix_hint: "Firmware publishes /imu/data_raw; the EKF imu0 reads /imu/data_raw (angular velocity z only); no host filter."
kind: distinction
status: recorded
values:
- firmware publishes /imu/data_raw
- "the EKF reads /imu/data_raw directly and fuses only angular_velocity.z (robot_localization imu0)"
- no host IMU filter in OpenAMRobot 2.0; nothing publishes /imu/data on the 2.0 robot
- "the Gate A (legacy) Teensy publishes /imu/data; a Gate A run remaps it to /imu/data_raw"
unit: none
date: 2026-11-08
review_by: 2026-12-20
source: {document: P-03-rev20.5, item: "item 29 (restates P-03-rev20.0 item 24, decision D-10): EKF imu0 /imu/data_raw, no filter, angular velocity z only"}
supersedes:
- {value: "the host filter and EKF own /imu/data", source: "P-00-rev18.1 txt 15 and 345, I8-WP line 224; replaced by P-03-rev20.0 item 24 (restated rev20.5 item 29)"}
applies_to:
repositories: ["openamr-platform-*", "openamrobot-docs", "openamrobot-ui"]
files: ["**/*.md", "**/*.yaml", "**/*.yml", "**/*.launch.py", "**/*.launch.xml", "**/*.ino", "**/*.cpp", "**/*.h"]
check:
- pattern: '(?:micro-?ROS agent|Teensy|firmware|MCU|STM32)[^\n]{0,80}(?P<found>/imu/data)(?!_raw)\b'
unless: '\bhost\b|(?<!un)filter|EKF|madgwick|must not|never|outdated|older revisions?|Gate A|legacy'
message: firmware publishes /imu/data_raw and the EKF reads it directly (P-03 rev20.5 item 29)
- pattern: '\bimu0:\s*(?P<found>/?imu/data)(?!_raw)\b'
files: ["**/*.yaml", "**/*.yml"]
message: the EKF imu0 input is /imu/data_raw; there is no host IMU filter in 2.0 (P-03 rev20.5 item 29, D-10)
- pattern: '"(?P<found>/?imu/data)"'
files: ["**/*.ino", "**/*.cpp", "**/*.c", "**/*.h"]
message: firmware must not publish filtered /imu/data
verification:
machine: text attributing /imu/data to firmware outside Gate A or legacy context; firmware sources containing the literal topic imu/data; an EKF imu0 on /imu/data
human: {reviewer: software-lead, evidence: "ros2 topic info on the running bring-up: one publisher of /imu/data_raw (firmware) and the EKF subscribed to it; openamr-platform-sw test_ekf_imu_topic.py"}
owner: software-lead
- id: CAMERAS
title: Cameras
summary: "Base camera Gemini 336L at base_camera_link (0.387, 0, 0.046); pitch from base_tilt bt05/bt10/bt15, default bt10."
fix_hint: "Name the Gemini 336L with an up-tilt of 5, 10 or 15 degrees, or label other cameras as legacy."
kind: value
status: recorded
values:
- base camera Orbbec Gemini 336L, base_camera_link (0.387, 0, 0.046) m from base_link, pitch from base_tilt (bt05, bt10, bt15, default bt10); camera centre 144 mm above the floor (base_link height from FRAMES-REP105 + z 0.046 m); front-panel opening about 126 x 36 mm centred on it; from CAD Rev B (platform-hw #20)
- head camera Stereolabs ZED Mini (SKU ZED-121210) on the lift carriage, see HEAD-CAMERA-IDENTITY
- two in-hand RGB wrist cameras; no separate torso scene camera
unit: none
date: 2026-10-16
review_by: 2026-11-27
source: {document: P-03-rev19.4, item: "item 19 D3 update (Alex decision 16 Oct 2026)"}
supersedes:
- {value: "base camera Orbbec Gemini 336L, housing centre on the old camera centre, 142.5 mm above the floor, base_camera_link (0.376, 0, 0.0445) from base_link; front-panel opening about 126 x 36 mm on that centre; up-tilt 5, 10 or 15 degrees, baseline 10", source: "Alex decision 12 Oct 2026, superseded by Alex decision 16 Oct 2026 (CAD Rev B)"}
- {value: "base camera tilted about 10 degrees upward; head camera identity open", source: P-00-rev18.1 txt 85 and 97}
- {value: "base camera Orbbec Gemini 336L, fixed to base_link on the front face about 243 mm above the floor; up-tilt positions 5, 10 and 15 degrees, baseline 10 degrees", source: P-03-rev18.7 item 15}
applies_to:
repositories: ["openamr-*", "openamrobot-docs", "openamrobot-manipulation", "openamrobot-ui"]
files: ["**/*.md", "**/*.yaml", "**/*.yml", "**/*.html", "**/*.launch.py", "**/*.xacro", "**/*.urdf"]
check:
- pattern: '(?P<found>\b(?:D4[35]5i?|RealSense)\b)'
unless: 'legacy|historical|previous|not used|replaced'
message: the base camera is the Orbbec Gemini 336L
- pattern: '(?P<found>down-tilted depth camera)'
message: the base camera tilts about 10 degrees up
- pattern: '(?P<found>IMX708|Pi Camera Module 3)'
unless: 'legacy|Gate A|historical'
message: the 2.0 base camera is the Orbbec Gemini 336L
- pattern: '(?P<found>Gemini 336L[^\n]{0,60}?\b(?!(?:5|10|15)\b)\d{1,2}\s*(?:°|deg(?:rees?)?)\s*(?:up|upward)\b)'
unless: 'supersed|historical|legacy'
message: the Gemini 336L up-tilt positions are 5, 10 and 15 degrees, baseline 10 (P-03 rev18.7 item 15)
- pattern: '(?P<found>(?:Gemini|base camera)[^\n]{0,60}?\b243\s*mm|\b243\s*mm[^\n]{0,60}?(?:Gemini|base camera))'
unless: 'supersed|historical'
message: the base camera is not at 243 mm; base_camera_link is (0.387, 0, 0.046) from base_link (Alex decision 2026-10-16)
verification:
machine: other camera models without a legacy label; a down-tilted base camera; a Gemini 336L up-tilt other than 5, 10 or 15 degrees; the base camera at 243 mm
human: {reviewer: robot-description-owner, evidence: camera joint rpy in URDF and real TF showing the upward tilt}
owner: platform-lead
- id: HEAD-CAMERA-IDENTITY
title: Head camera commercial identity and mounting
summary: "Head camera: Stereolabs ZED Mini, SKU ZED-121210, on the lift carriage."
fix_hint: "Name the ZED Mini (ZED-121210), or label other ZED models as superseded or legacy."
kind: value
status: recorded
values:
- Stereolabs ZED Mini, SKU ZED-121210, supplied with the OpenArm 2.0 set
- mounted on the lift carriage, held at its ends by the mount supplied with the OpenArm set, on a pitch bracket on the arm-profile top
- lens 0.060 m ahead of and 0.223 m above the arm mount point, centred; 1223 mm at L1000 and 1573 mm at L1350 (height unchanged)
- pitch 15 to 35 degrees down in 5 degree steps about the lens line, baseline 30 degrees
unit: none
date: 2026-11-08
review_by: 2026-12-20
source: {document: P-03-rev20.4, item: "item 28 (owner decision 8 Nov 2026): lens 0.060 m ahead of the arm mount, height unchanged; pitch per P-03-rev20.1 item 15 (value of the P-03-rev20.0 28 Oct 2026 correction, unchanged); camera identity per P-03-rev18.7 item 15"}
supersedes:
- {value: "lens 0.057 m ahead of and 0.223 m above the arm mount point", source: "Alex decision 2026-11-02; replaced by P-03-rev20.4 item 28 (8 Nov 2026)"}
- {value: "lens 0.042 m ahead of and 0.223 m above the arm mount point", source: "P-03-rev20.1 item 18; replaced by Alex decision 2026-11-02"}
- {value: "lens 0.022 m ahead of and 0.223 m above the arm mount point", source: P-03-rev18.9 item 18}
- {value: "pitch 15 to 35 degrees down in 5 degree steps, baseline 25 degrees", source: P-03-rev18.7 item 15}
- {value: "ZED-121210 per the plan; identity open because the general arrangement named a different ZED model", source: P-00-rev18.1 txt 85}
applies_to: {repositories: ["*"], files: ["**/*.md", "**/*.html", "**/*.yaml", "**/*.yml", "**/*.xacro", "**/*.urdf"]}
check:
- pattern: '(?P<found>\bZED[ -]?(?:2i?|X(?:[ -]?Mini)?)\b)'
unless: 'supersed|historical|legacy|replaced|\bnot\b'
message: the head camera is the Stereolabs ZED Mini, SKU ZED-121210 (P-03 rev18.7 item 15)
- pattern: '(?P<found>\b(?:0\.0(?:[24]2|57) m|(?:[24]2|57) mm) ahead\b)'
unless: 'supersed|historical|\bwas\b'
message: the head-camera lens is 0.060 m (60 mm) ahead of the arm mount point (P-03 rev20.4 item 28)
- pattern: '(?P<found>\b(?:head[- ]camera|ZED Mini)\b[^\n]{0,60}\bpitch\b[^\n]{0,40}\bbaseline:?\s*25\b(?!\s*mm))'
unless: 'supersed|historical|\bwas\b'
message: the head-camera baseline pitch is 30 degrees down (P-03 rev20.1 item 15)
verification:
machine: another ZED model (ZED 2, ZED 2i, ZED X, ZED X Mini) without a superseded or legacy label; the lens 0.022 m, 22 mm, 0.042 m or 42 mm ahead; a head-camera pitch baseline of 25 degrees
human: {reviewer: platform-lead, evidence: supplier SKU on the OpenArm 2.0 set and the lift-carriage mount drawing with the pitch steps}
owner: platform-lead
- id: POWER-RAILS
title: Power rails; no 12 V rail
summary: "25.6 V battery bus, regulated 24 V and 5 V branches; there is no 12 V rail."
fix_hint: "Remove the 12 V rail from 2.0 text, or label it as legacy."
kind: exclusion
status: recorded
values:
- main battery bus 25.6 V nominal (not a regulated 24 V rail)
- regulated 24 V branch (safety relay, peripherals); the brake-release supply comes from the actuator side, see ESTOP-SCOPE
- regulated 5 V (includes the navigation LiDAR)
- "SAFE 24 V converter for lift and brake release: MEAN WELL DDR-240B-24 (16.8 to 33.6 V in, 24 V 10 A, 240 W) behind F-LIFT 15 A, 2.5 mm2 (P-03 rev20.2 item 26)"
- no 12 V rail
unit: V
date: null
review_by: 2026-12-13 # six weeks after this register update (2026-11-01)
source: {document: P-03-rev18.1, item: "item 2 line 10; P-03-rev18.4 item 13; brake-release supply per P-03-rev19.2 item 20; SAFE 24 V converter per P-03-rev20.2 item 26"}
supersedes:
- {value: "regulated 24 V branch (safety relay, brake coils, peripherals)", source: "P-03-rev18.4 item 13"}
applies_to:
repositories: ["openamr-platform-*", "openamr-upperbody-*", "openamrobot-docs"]
files: ["**/*.md", "**/*.yaml", "**/*.yml", "**/*.html"]
check:
- pattern: '(?P<found>\b12\s*V\s+rail)'
unless: '\bno 12|not|never|legacy'
message: there is no 12 V rail in 2.0
- pattern: '(?P<found>24\s*V?\s*(?:->|→|to)\s*5\s*V?\s*/\s*12\s*V)'
unless: 'legacy|Gate A'
message: there is no 12 V rail in 2.0
verification:
machine: a 12 V rail or a 24 V to 5/12 V converter in text
human: {reviewer: platform-lead, evidence: "power distribution schematic, including the DDR-240B-24 SAFE 24 V branch behind F-LIFT"}
owner: platform-lead
- id: DOCK-NO-CONTACTS
title: Release 2.0 docking has no dock contacts or dock pilot; wireless charging is prepared in 2.0
summary: "2.0 docking is positioning only: no dock contacts or pilot; wireless charging is prepared in 2.0."
fix_hint: "Say the dock has no contacts or pilot; describe wireless charging as prepared in 2.0 (see CHARGING), not 3.0."
kind: exclusion
status: recorded
value: Positioning only; no dock contacts or dock pilot; wireless charging is prepared in 2.0 and the receiver is installed later (see CHARGING); the docking approach for wireless charging turns 180 degrees at the station and reverses onto the transmitter
unit: none
date: 2026-11-02
review_by: 2026-12-14
source: {document: Alex decision 2026-11-02, item: "wireless charging prepared, docking approach; exclusion per P-03-rev19.2 item 3 as changed by item 20"}
supersedes:
- {value: "Positioning only; no dock contacts or dock pilot; wireless charging belongs to 2.0 (see CHARGING)", source: "P-03-rev19.2 item 3 as changed by item 20; refined by Alex decision 2026-11-02"}
- value: Positioning only; manual wired charging via PWR-019 with independent charge-plug-presence inhibition; no dock contacts or dock pilot; wireless charging belongs to 3.0
source: P-03-rev18.1 item 3 line 11
applies_to:
repositories: ["openamr-platform-*", "openamrobot-docs", "openamrobot-ui", "openamrobot-interfaces"]
files: ["**/*.md", "**/*.yaml", "**/*.yml", "**/*.html", "**/*.launch.py", "**/*.xacro", "**/*.urdf"]
check:
- pattern: '(?P<found>charg(?:e|ing)[ -]contacts?)'
unless: '\bno\b|\bnot\b|without|3\.0|never'
message: 2.0 docking has no dock contacts
- pattern: '(?P<found>(?:charge|charger|dock|DC)\s*\+?\s*pilot)'
unless: '\bno\b'
message: no dock or charge pilot in 2.0
- pattern: '(?P<found>wireless charg\w*[^\n]{0,40}?\b(?:is|belongs to|deferred to|moved to|planned for|reserved for) (?:OpenAMRobot )?3\.0\b|(?:OpenAMRobot )?3\.0 wireless charg\w*)'
unless: 'supersed|legacy|historical|removed|dropped|no longer|earlier|previous|v0\.0\.1'
message: wireless charging belongs to 2.0, not 3.0 (P-03 rev19.2 item 20)
verification:
machine: charge contacts or pilots without a negation; wireless charging presented as 3.0 or deferred to 3.0
human: {reviewer: platform-lead, evidence: dock drawing and harness list without contacts}
owner: platform-lead
- id: DOCKING-NOT-CHARGING
title: Docking success never establishes charging
summary: "Docked means an accepted pose; docking never establishes charging or external power."
fix_hint: "Report docking as a pose result only; never infer charging from it."
kind: distinction
status: recorded
value: Docked means an accepted pose within tolerance; pose success never establishes charging or external power
unit: none
date: null
review_by: 2026-11-18 # six weeks after this register update (2026-10-07)
source: {document: P-03-rev18.1, item: "item 3 line 11; DOCK-WP lines 27 and 70; charge-state inputs per P-03-rev19.2 item 20"}
applies_to:
repositories: ["openamr-platform-*", "openamrobot-docs", "openamrobot-ui", "openamrobot-interfaces"]
files: ["**/*.md", "**/*.yaml", "**/*.yml", "**/*.launch.py", "**/*.py", "**/*.ts", "**/*.tsx", "**/*.js"]
check:
- pattern: '(?P<found>SimpleChargingDock|ready to charge|charging target)'
unless: 'not |never|instead|non-charging|legacy'
message: 2.0 docking is positioning only
- pattern: '(?P<found>isCharging[^\n]{0,20}\breturn\s+true|return\s+true[^\n]{0,20}isCharging)'
message: never report charging from a docking pose
- pattern: '(?P<found>dock(?:ed|ing)?[^\n]{0,60}\b(?:connected to (?:external )?power|is charging|charging (?:started|confirmed)))'
unless: '\bnot\b|never|does not'
message: docking success never establishes charging
verification:
machine: charging dock plugins, forced isCharging, text deriving charging or external power from docking
human: {reviewer: software-lead, evidence: docking state machine and UI source showing charge state comes only from the charging hardware (receiver, charge relay, fault input), never from the docking pose}
owner: platform-lead
- id: TELEMETRY-NOT-SAFETY-EVIDENCE
title: Functional telemetry is never safety evidence
summary: "Telemetry, watchdogs and BMS data are functional, never safety evidence."
fix_hint: "Describe telemetry and watchdogs as functional, not as a safety layer."
kind: distinction
status: recorded
value: Firmware status, watchdogs, collision monitoring and BMS telemetry are functional; E-stop, brake and actuator power removal are hardwired and independent of software
unit: none
date: null
review_by: 2026-11-18 # six weeks after this register update (2026-10-07)
source: {document: P-00-rev18.1, item: txt 70 and 78; I8-WP line 669; DOCK-WP line 110}
applies_to: {repositories: ["*"], files: ["**/*.md", "**/*.html", "**/*.yaml", "**/*.yml"]}
check:
- pattern: '(?P<found>(?:watchdog|collision monitor|telemetry|status message|diagnostic)s?[^\n]{0,40}\bsafety (?:layer|function|evidence|guarantee))'
unless: '\bnot\b|never|functional|no substitute'
message: functional telemetry is not a safety layer or safety evidence
verification:
machine: text calling watchdogs, collision monitoring, telemetry or diagnostics a safety layer, function or evidence
human: {reviewer: platform-lead, evidence: hardwired safety-chain test record; a software PASS is never accepted in its place}
owner: platform-lead
- id: SAFETY-PROCUREMENT
title: Safety-chain procurement boundary (record only; this register implements no safety function)
summary: "Two E-stops into a Pilz PNOZ s3 with monitored reset; K1, K2 Gigavac GX11CAC with linked NC auxiliaries."
fix_hint: "Name the PNOZ s3 and Gigavac GX11CAC K1/K2; label LEV100H and K1/K2 firmware feedback as superseded."
kind: limit
status: recorded
values:
- "exactly two E-stops; base front Schneider XB4BS8445 with one ZBE-102 block; second Schneider XB4BS8445 with ZBE-102 on top of the moving adapter plate, centred, behind the arm post, button up (about 0.90 / 1.08 / 1.25 m above the floor at L1000 / L1175 / L1350); no longer on the static column"
- dual channel into a Pilz PNOZ s3 24 V DC (750103) with monitored manual reset
- K1 and K2 Gigavac GX11CAC (150 A, 24 V coil with internal suppression), normally open, in series; each with one SPST-NC auxiliary, mechanically linked, in the PNOZ reset loop
- "K1/K2 decided: Gigavac GX11CAC (option A); the industrial contactors of option B (Schneider LC1D80BD, 186 mm deep; Siemens 3RT2045, 152 mm deep) are rejected because they do not fit under the cover above the rear power plate (about 165 mm)"
- ordering (BUY-32) is gated on the GX11CAC datasheet checks
- CTL-004 is bench-only until an installed solution is qualified (P-03-rev18.1 item 5, unchanged)
unit: none
date: 2026-11-03
review_by: 2026-12-15
source: {document: Alex decision 2026-11-03, item: "builds on the decision of 2 Nov 2026; second E-stop position on the moving adapter plate; K1/K2 option A decided 3 Nov 2026 on the rear power owner's layout report rev 2 (option B does not fit the plate height); contactors per P-03-rev19.6 item 22; E-stops and PNOZ per P-03-rev19.2 items 5 and 20; detail in E-01-rev1.3"}
supersedes:
- {value: "second E-stop: Schneider XB4BS8445 with ZBE-102 on the rear face of the static lift column, close to its upper edge (placeholder position until M-09)", source: "P-03-rev20.0 item 24; replaced by Alex decision 2026-11-02"}
- {value: "second E-stop: chest button from the OpenArm kit", source: "P-03-rev19.2 items 5 and 20; replaced by P-03-rev20.0 item 24"}
- {value: "K1 and K2 TE KILOVAC LEV100H, normally open, in series; auxiliary NC contacts in the reset circuit (EDM); the linked-auxiliary variant is gate EDM-STOP before ordering", source: "P-03-rev19.2 items 5 and 20, E-01-rev1.1"}
- {value: "separate K1/K2 contactor feedback read by the firmware", source: "earlier contactor design; replaced by the linked auxiliaries in the PNOZ reset loop, P-03-rev19.6 item 22"}
- {value: "two installed E-stops, dual normally-closed channels into a monitored safety relay; K1 and K2 from the LEV100 family, linked-feedback (EDM) variant unselected under one CONTACTOR gate", source: P-03-rev18.1 items 4 and 5 lines 12-13}
applies_to: {repositories: ["*"], files: ["**/*.md", "**/*.yaml", "**/*.yml", "**/*.html"]}
check:
- pattern: '(?P<found>(?:EDM|linked[- ]feedback) variant[^\n]{0,30}\b(?:selected|chosen|decided))'
unless: '\bnot\b|unselected|open|EDM-STOP|GX11CAC|BUY-32'
message: the linked-auxiliary contactor is the Gigavac GX11CAC; ordering (BUY-32) is gated on the datasheet checks (P-03 rev19.6 item 22)
- pattern: '(?P<found>fine for prototyp\w*|single[- ]contact[^\n]{0,30}e-?stop)'
message: no single-channel or uncertified E-stop recommendation
- pattern: '(?P<found>CTL-004[^\n]{0,60}\b(?:installed|robot interface))'
unless: 'bench-only|until'
message: CTL-004 is bench-only
- pattern: '(?P<found>automotive relays?[^\n]{0,40}\b(?:E-?stop|K1|K2|contactors?)\b|\b(?:E-?stop|K1|K2)\b[^\n]{0,40}automotive relays?)'
unless: 'supersed|legacy|historical|removed|dropped|no longer|earlier|previous|v0\.0\.1|\bnot\b|never|Gate A'
message: K1 and K2 are Gigavac GX11CAC contactors; automotive relays are not the 2.0 E-stop (P-03 rev19.6 item 22)
- pattern: '(?P<found>\bLEV100H?\b)'
unless: 'supersed|legacy|historical|replaced|removed|dropped|no longer|earlier|previous|v0\.0\.1'
message: K1 and K2 are Gigavac GX11CAC contactors; label LEV100H material as superseded (P-03 rev19.6 item 22)
- pattern: '(?P<found>\bOpenArm(?:[- ][\w.]+)?[- ]kit\b[^\n]{0,50}\b(?:E-?stop|button)\b|\b(?:chest|second) (?:E-?stop|button)\b[^\n]{0,50}\bOpenArm(?:[- ][\w.]+)?[- ]kit\b)'
unless: 'supersed|historical|\bwas\b|replac'
message: the second E-stop is a Schneider XB4BS8445 with ZBE-102 on the moving adapter plate, not the OpenArm kit button (P-03 rev20.0 item 24, Alex decision 2026-11-02)
- pattern: '(?P<found>\b(?:second|upper|column|lift) E-?stop\b[^\n]{0,80}\bstatic (?:lift )?column\b|\bE-?stop\b[^\n]{0,40}\bon (?:the )?(?:rear face of the )?static (?:lift )?column\b)'
unless: 'supersed|historical|\bwas\b|replac|no longer|earlier|previous|\bnot\b'
message: the second E-stop sits on top of the moving adapter plate, behind the arm post, button up; no longer on the static column (Alex decision 2026-11-02)
verification:
machine: text claiming the EDM variant is chosen without the GX11CAC or BUY-32, recommending a single-channel or uncertified E-stop, presenting CTL-004 as installed, naming automotive relays as the 2.0 E-stop, LEV100H outside superseded or historical context, the OpenArm kit button as the chest or second E-stop, or the second E-stop on the static column
human: {reviewer: platform-lead, evidence: "safety-chain design, GX11CAC datasheet checks for BUY-32 and component certificates; two human approvals per the repository ruleset"}
owner: electrical-owner
- id: SAFETY-CHAIN-IO
title: Controller I/O for the safety chain and charging (item 22)
summary: "Y32 via one ISO1212; E-stop spare NO, RESET NC and charger fault inputs; TPL7407L for RESET lamp and KCHG."
fix_hint: "Read Y32 through the ISO1212; no separate K1/K2 feedback input; label older contactor feedback as superseded."
kind: configuration
status: recorded
values:
- Y32 read through one ISO1212 module
- base E-stop spare NO contact as a diagnostic input
- RESET NC contact input
- charger fault input
- TPL7407L outputs for the RESET lamp and KCHG
- "the driver part is the TI TPL7407LDR on an Adafruit 1207 SOIC-16 breakout, outputs off from power-up; the DFRobot DFR0457 is not used"
- "spare driver channels are not assigned; K2-EN, KPRE-EN and BRAKE-EN wait for the electrical owner's ruling (D-09, D-22, D-25)"
unit: none
date: 2026-11-08
review_by: 2026-12-20
source: {document: P-03-rev20.5, item: "item 29 (decision D-09: TPL7407LDR on Adafruit 1207, platform-lead Slack 4 Nov 2026); controller I/O per P-03-rev19.6 item 22, detail in E-01-rev1.3"}
supersedes:
- {value: "separate K1/K2 contactor feedback read by the firmware", source: "earlier contactor design; replaced by the linked auxiliaries in the PNOZ reset loop, P-03-rev19.6 item 22"}
applies_to: {repositories: ["*"], files: ["**/*.md", "**/*.yaml", "**/*.yml", "**/*.html"]}
check:
- pattern: '(?P<found>\b(?:K1|K2|contactors?)\b[^\n]{0,40}\bfeedback\b[^\n]{0,40}\b(?:firmware|STM32|MCU|GPIO)\b|\b(?:firmware|STM32|MCU)\b[^\n]{0,40}\b(?:K1|K2|contactors?)\b[^\n]{0,20}\bfeedback\b)'
unless: 'supersed|legacy|historical|replaced|removed|dropped|no longer|earlier|previous|v0\.0\.1|\bno\b|\bnot\b|never|without|PNOZ'
message: there is no separate K1/K2 feedback to the firmware; the linked auxiliaries sit in the PNOZ reset loop and the controller reads Y32 (P-03 rev19.6 item 22)
verification:
machine: K1/K2 or contactor feedback wired to the firmware, STM32, MCU or a GPIO outside superseded or historical context
human: {reviewer: platform-lead, evidence: "E-01 rev1.3 controller I/O allocation (ISO1212, TPL7407L) and the safety-chain test record; two human approvals per the repository ruleset"}
owner: electrical-owner
- id: ESTOP-SCOPE
title: E-stop scope; actuator power only
summary: "An E-stop cuts actuator power only (traction, arms, lift); Jetson, 5 V and regulated 24 V stay powered."
fix_hint: "Say the E-stop removes actuator power and engages the brakes; the Jetson and logic rails stay powered."
kind: limit
status: recorded
values:
- an E-stop cuts actuator power only (traction, both arms, lift)
- the Jetson, the 5 V rail and the regulated 24 V rail stay powered
- brake release is fed from the actuator side, so an E-stop engages the brakes
- "the E-stop is Category 0: motor power is cut and the two spring-applied holding brakes stop the robot; normal and software stops are made by the ZLAC8015D"
- "stop distance at most 0.15 m is a physical acceptance test (evidence hold, see SPEED-CEILING)"
unit: none
date: 2026-11-08
review_by: 2026-12-20
source: {document: P-03-rev20.5, item: "item 29 (decision D-07: Category 0 E-stop on the holding brakes); scope per P-03-rev19.2 item 20, detail in E-01-rev1.1"}
supersedes:
- {value: "dynamic stopping on E-stop stays with the ZLAC8015D", source: "P-03-rev20.2 item 21 and E-01 rev1.7 section 4; replaced by P-03-rev20.5 item 29 (Category 0 on the holding brakes)"}
applies_to:
repositories: ["openamr-platform-*", "openamr-upperbody-*", "openamrobot-docs", "openamrobot-ui"]
files: ["**/*.md", "**/*.yaml", "**/*.yml", "**/*.html"]
check:
- pattern: '(?P<found>\bE-?stop\b[^\n]{0,40}\b(?:cuts|removes|kills|disconnects) (?:all|the whole robot|system) power\b|\bE-?stop\b[^\n]{0,40}\b(?:powers? (?:down|off)|shuts? down) the Jetson\b)'
unless: 'supersed|legacy|historical|removed|dropped|no longer|earlier|previous|v0\.0\.1|\bnot\b|never|actuator'
message: an E-stop cuts actuator power only; the Jetson, 5 V and regulated 24 V stay powered (P-03 rev19.2 item 20)
verification:
machine: text saying an E-stop cuts all power or shuts down the Jetson
human: {reviewer: platform-lead, evidence: "E-01 rev1.1 power distribution, the hardwired safety-chain test record and the measured E-stop stop distance and delay chain; two human approvals per the repository ruleset"}
owner: electrical-owner
- id: RESET-BUTTON
title: One RESET button