Skip to content

docs: align decision register with P-03 rev19.4 - #51

Closed
BotshareAI wants to merge 1 commit into
mainfrom
audit/p03-rev19-4-register-2026-10-16
Closed

BotshareAI wants to merge 1 commit into
mainfrom
audit/p03-rev19-4-register-2026-10-16

Conversation

@BotshareAI

Copy link
Copy Markdown
Contributor

Summary

Update the approved decision register to match P-03 rev19.4 item 19.

  • Set the in-force P-03 source to rev19.4 dated 16 October 2026.
  • Record P-03 rev19.4 as the source for the CAD Rev B updates.
  • Update FRAMES-REP105 to imu_link (0.0544, 0, 0.1210) m, yaw -90 deg, raw sensor-frame values with URDF axis mapping, and 219.04 mm above the floor.
  • Preserve the superseded 0.133 and 0.195 values as traceable history.

This PR updates the register only. Consumer repositories and Drive documents remain separate follow-up work and should be reconciled after review.

Copy link
Copy Markdown
Contributor Author

Superseded by #52 (rebuilt on main after #50, signed off).


Generated by Claude Code

@BotshareAI BotshareAI closed this Oct 16, 2026
BotshareAI added a commit that referenced this pull request Oct 19, 2026
…GX11CAC, item 22 I/O) (#52)

* decisions: P-03 rev19.4 in force; item 19 D3, D4 and D5 cite rev19.4

Replaces #51, rebuilt on main after #50. decisions.yaml only:
- in_force: P-03-rev19.2 (2026-10-15) to P-03-rev19.4 (2026-10-16)
- source "Alex decision 2026-10-16": recorded in P-03 rev19.4 item 19
  D3, D4 and D5
- new source P-03-rev19.4 after P-03-rev19.2
- the base camera (D3), LiDAR mount (D4) and imu_link (D5) decisions cite
  P-03-rev19.4 item 19 instead of "P-03 next revision"

The FRAMES-REP105 imu_link text from #50 and every rev19.2 item 20
citation are unchanged.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01RtnAs3hZ9W2iEfaMcCvWng
Signed-off-by: Alex Reznichenko <info@botshare.ai>

* decisions: P-03 rev19.6 and BOM Issue 7.10 in force; Gigavac GX11CAC and item 22 I/O

- in_force is P-03 rev19.6 (18 October 2026). Sources P-03-rev19.6,
  E-01-rev1.3 and BOM-Issue-7.10 are added; P-03 rev19.4, rev19.2 and BOM
  Issue 7.8 are marked earlier.
- BOM-ISSUE-IN-FORCE: Issue 7.10; Issue 7.8 moves to supersedes.
- SAFETY-PROCUREMENT: K1 and K2 are Gigavac GX11CAC (150 A, 24 V coil with
  internal suppression), each with one mechanically linked SPST-NC
  auxiliary in the PNOZ reset loop (P-03 rev19.6 item 22); BUY-32 is gated
  on the datasheet checks. LEV100H and the EDM-STOP gate move to
  supersedes, and so does separate K1/K2 feedback read by the firmware.
  New check flags LEV100H outside superseded or historical context.
- New entry SAFETY-CHAIN-IO (item 22 I/O): Y32 through one ISO1212, base
  E-stop spare NO diagnostic, RESET NC, charger fault input, TPL7407L
  outputs for the RESET lamp and KCHG. Its check flags K1/K2 or contactor
  feedback to the firmware outside superseded or historical context.
- MAIN-PROTECTION: F-LIFT 15 A with 2.5 mm2 cable.
- Owner electrical-owner, reviewer platform-lead throughout.

Tests: the BOM test moves to 7.10; the automotive-relay negative example
names the GX11CAC; new tests for the GX11CAC EDM wording, LEV100H and
K1/K2 firmware feedback, each with a superseded negative case. The four
new or changed tests fail against f20cfea. The WATCHDOG.md accepted-words
table is regenerated with tools/watchdog.py --accepted-words.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TPiK6pUmmjNhPceECkKpR2
Signed-off-by: Alex Reznichenko <info@botshare.ai>

---------

Signed-off-by: Alex Reznichenko <info@botshare.ai>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant