Argentina twin set — ITBA hardware handoff

The ITBA Buenos Aires research team (Raul Marino PI, plus Carlos Bibian, Rodrigo Díaz, Esteban Roitberg, Cristian Maximilian Mateos Diaz, Rodrigo Ramele) receives a pre-flashed Jetson + 1 bench camera on Thursday 2026-05-15 when Sophia + Armando fly through Buenos Aires en route to Pereira. The Jetson is the same SKU as the LBZF unit, pre-loaded in California per ADR-006 with the full Phase I software stack, so ITBA can replicate the inference pipeline end-to-end (camera → RTSP → YOLO → SQLite → dashboard) without waiting for LBZF on-site results.

This doc nails down what ships, what software state it ships in, how ITBA gets onto the tailnet, and how the two Jetsons stay in sync.

What ships

Item	Qty	Source	Notes
Jetson Orin Nano Super Dev Kit (in Waveshare Case A with PWM fan + NVMe heatsink)	1	New, CA purchase	Same SKU as LBZF Jetson
1TB NVMe SSD (M.2 2280; pre-installed in the Jetson)	1	New, CA purchase	Smaller than LBZF’s 4TB — ITBA has no long rolling-buffer requirement
SanDisk 64GB Extreme microSD with restore image	1	New, CA purchase	Single-point-of-failure mitigation per ADR-006
Amcrest IP8M-2779EW-AI camera	1	New, CA purchase	Bench camera for end-to-end RTSP testing; doubles as the CA smoke-test camera pre-flight
Argentina Type-I plug adapter	1	New, CA purchase	Jetson PSU is auto-ranging; adapter for the AR outlet shape only
Printed setup notes (Spanish + English)	1	Printed	Single-page handoff + Tailscale auth walkthrough

No PoE switch ships to ITBA. They power the bench camera from a PoE injector or their lab switch — Argentina-side lab infrastructure is theirs to supply.

Total: ~1.5 kg. Fits in Sophia’s carry-on. Strongly NOT checked — checked-bag loss = trip-defeating.

Pre-loaded software state

The ITBA Jetson ships with the same software state as the LBZF Jetson, with three deltas:

Hostname is itba-jetson-01 (not lbzf-jetson-01).
Tailscale is installed and configured to auto-start, but not yet authenticated. ITBA brings it up on the shared LBZF tailnet under tag:itba-dev (ADR-005) on first boot in BA, gated by Andrew or Sophia approving the device in the Tailscale admin console.
No LBZF-specific data in /data/db/ — SQLite starts empty with the same schema. No camera credentials baked in.

Concretely, the pre-load is:

JetPack 6.0 or 6.1 flashed to NVMe (per ADR-003; not 6.2) — root migrated to NVMe via jetsonhacks/bootFromExternalStorage.
/opt/lbzf/venv/ Python venv with all packages from jetson-edge-compute.md.
/opt/lbzf/app/ cloned from the project repo at the same commit as LBZF.
/data/models/yolov8n.pt (source weights) — yolov8n.engine is rebuilt on the ITBA Jetson since TensorRT engines are not portable across devices, even identical SKUs (ADR-003, ADR-006). Sophia does this build in CA before flight so ITBA gets a working engine.
lbzf-monitor.service enabled but not started.
tailscaled enabled, not yet authed.
SSH hardened, default nvidia/ubuntu removed, itba user created with Sophia + Andrew + each ITBA member’s SSH public keys in ~itba/.ssh/authorized_keys.

Pre-flight SSH key collection

Pre-Thursday action: email ITBA team for SSH public keys (ed25519 preferred, rsa-4096 acceptable). One key per member.
Bake into ~itba/.ssh/authorized_keys on the BA Jetson during the CA pre-flash.
If a key arrives late, provision via Tailscale SSH after the device is online in BA.

Tracked at the G1 gate (ITBA team's SSH public keys collected (≥3 keys)).

Customs and logistics

Argentina customs (AFIP) treats imported electronics over ~$300 USD as commercial. A single $500 Jetson plus accessories is just over that line. Mitigations:

Carry on as personal research equipment, not commercial shipment.
Bilingual customs letters — one from Mariana (LBZF) and one from ITBA PI Raul Marino, both confirming the equipment is non-commercial academic research collaboration with no resale. Tracked at the G1 gate.
Be prepared to pay duty. Have ~$500 USD in pesos / cards available.
Split between Sophia + Armando bags so no single bag has a commercial-cargo profile.

Same drill again Friday/Saturday for the Colombia leg with the LBZF Jetson + 2 Amcrest cameras.

Software sync model (post-handoff)

ITBA and LBZF work on the same GitHub repo (sophiamann/lbzfai). Both Jetsons pull main:

LBZF Jetson updates only on manual SSH session from Sophia or Andrew (cron-driven autopull is appealing but a bad merge breaks production).
ITBA Jetson is a research / dev machine; ITBA pulls / commits / pushes freely.
Branch strategy: ITBA experiments on feature branches; merged into main after Andrew + Sophia review.

ITBA needs collaborator access to the repo. If it’s still private, Sophia adds them before flight.

On-arrival in Buenos Aires (handoff session, ~2 hours)

Monday session at ITBA’s lab, before the Tuesday presentation:

Sophia + Armando hand over the Jetson + microSD + Amcrest camera + plug adapter + printed notes.
Survive-the-flight check — power up the Jetson, verify it boots, verify NVMe still mounts, verify lbzf-monitor.service enables cleanly. A device that boots fine in CA can fail in BA if the NVMe seat shook loose.
Walk through this doc + jetson-edge-compute.md + the bench-test results.
ITBA brings up Tailscale on the BA Jetson:
Terminal window
```
sudo tailscale up --ssh --hostname=itba-jetson-01 --advertise-tags=tag:itba-dev
```
Andrew or Sophia approves the device in the admin console.
From an ITBA team member’s laptop on cellular: SSH to itba-jetson-01 over Tailscale → confirm remote access.
git pull on the Jetson — confirm ITBA can sync code as the repo evolves.
Demo: plug the bundled Amcrest camera into ITBA’s PoE injector / lab switch; configure the camera’s static IP + password (already done in CA — verify here); confirm lbzf-monitor picks up the RTSP stream, runs inference, writes events to SQLite, renders the dashboard.
Q&A on architecture; queue “we should change X” items for Andrew + Sophia.

Tuesday ITBA presentation (separate session)

The Tuesday demo to the wider ITBA group shows:

The pre-recorded 90-second bench-demo video (recorded in CA — see pre-argentina-testing.md and the G1 gate).
The architecture diagram (one-pager prepared per the G1 gate).
A design-doc tour of docs/design/.
The ITBA Jetson running on stage if Monday’s handoff went well — otherwise the recorded video is the fallback.

This is a design-presentation event, not a working-system event. Andrew’s framing: set expectations accordingly; the design docs are the substantive content; the live demo is illustrative.

Cross-bucket dependencies

BOM (bom.md) — ITBA twin is a subset; updates propagate.
Jetson spec (jetson-edge-compute.md) — ITBA Jetson uses the same image.
Network (network-and-tailscale.md) — Tailscale ACL has the tag:itba-dev rule.
Pre-Argentina testing (pre-argentina-testing.md) — both Jetsons bench-tested in parallel.
G1 gate (../../10-gates/G1-argentina-demo.md) — canonical pre-flight checklist; customs letters and SSH key collection tracked there.
Business bucket — confidentiality of LBZF data on the BA Jetson. None ships, but repo content (operator names, station names) needs sanitization before ITBA collaborates.

Rollout

Tracked at the G1 gate. Summary:

Pre-flight (CA) — flash + smoke-test the BA Jetson alongside the LBZF one; bake in ITBA SSH keys; differentiate hostname / Tailscale auth.
2026-05-14 evening — pack the BA Jetson + microSD + bench Amcrest camera + adapter + printed notes; print bilingual customs letter.
2026-05-15 — fly CA → BA with both Jetsons in carry-on. Split bags for customs profile.
2026-05-18 (Monday) — handoff session at ITBA lab; Tailscale auth in BA.
2026-05-19 (Tuesday) — ITBA presentation to wider research team.
2026-05-20 onwards — Sophia + Armando fly BA → Bogotá → Pereira with the LBZF set. ITBA begins independent research.
Post-handoff — weekly async sync on what ITBA found vs. what LBZF is hitting.