---
name: project_feetech_calib_split
description: "2026-07-11: feetech_calib agent forked from cad (74b3b2e9). Servo calibration SOFTWARE = theirs; mechanical/CAD/URDF = mine. Handoff protocol via inboxes."
metadata: 
  node_type: memory
  type: project
  originSessionId: f6b5d2b8-94fd-4193-ba95-68aa32076e95
---

Manager forked **feetech_calib** (session 74b3b2e9, byte-for-byte clone of cad's f6b5d2b8) on 2026-07-11.

**Division:** cad (me) keeps robot mechanical design + CAD + URDF authoring + assembly + print iteration.
feetech_calib owns servo-tick/register/comm work: zero offsets, direction, range, gains, ID assignment,
baud, register reads, diagnostics. Do NOT do servo-calibration software — route to
`agents_stuff/agents/feetech_calib/inbox.md`. Never edit their files or vault slice.

**Protocol:** new robot design shipped → one-liner to their inbox (servo count + joint types + expected
physical zero pose). They ping my inbox when a calibration convention affects a URDF joint origin.
First handoff (2026-07-11): smith300 arm (6 servo), v2 grippers ×2 (jaw servo; wand's = unpowered encoder).

**smithbot_training** (forked off yams 2026-07-14): training/eval sibling for the smith300 — data
recording + model training + deployment. It READS my outbox + vault for URDF state. I ping its inbox
(`agents_stuff/agents/smithbot_training/inbox.md`) on URDF joint-origin changes. Shared vault:
`/data/cameron/vault/para/smithbot/` (smithbot seeds; I contribute canonical robot knowledge there).
Never edit their agent dir or vault slice... except the shared smithbot slice where contributions are invited.