# Inbox — yams_any4d

## 2026-07-08 — divergence + first framing (from manager, on Cameron's behalf)

You have just been forked from `yams` as of 2026-07-08. Your session is a byte-for-byte clone of yams's JSONL (source UUID `bc8f854a-...`; new UUID `1684f247-...`). Everything you remember before this message is inherited context — YAM stack, recording format, wandb conventions, prior training patterns. Use it.

Cameron's brief:

> Look at this repo: **https://github.com/TRI-ML/Any4D**
> We want to **finetune Any4D** on YAM data.

That's your scope. Full details, coordination, and files convention in your **ROLE.md — read that first.**

## Sibling agents (four now under yams's lineage)

- **yams** — real teleop, real training on yukon/puget, deployment, general real-robot ops
- **yam_sim** — MuJoCo simulation, sim training, sim-side fiducial rendering, sim2real, sim-derived data
- **yam_calib** — real calibration, real-side fiducial exo, record.py + storage infra
- **yams_any4d = YOU** — Any4D model finetuning on YAM data

Never edit their files. Coordinate via one-line inbox pings.

## First task

1. Read your `ROLE.md`.
2. Set status to `working`.
3. Fetch and skim the Any4D repo. Since phe is down (2026-07-05 server-room cooling failure, not back yet), the code-on-VPS policy means you clone Any4D directly to VPS: `ssh phe108 'git clone ...'` won't work; use `git clone git@github.com:TRI-ML/Any4D.git /data/cameron/repos/Any4D` (may be public — try without ssh key first). If it's a private/gated TRI repo, ping Cameron with what auth is needed.
4. Study it: architecture, dataset format, finetune examples, checkpoints available.
5. Write `/data/cameron/vault/para/yam/any4d.md` — your bootstrap doc capturing what Any4D expects vs. what our YAM recordings provide (the format-mismatch delta is the key deliverable).
6. Draft the finetune plan in `outbox.md`: dataset prep, hyperparams, GPU host, eval metric, milestones, blockers.
7. Post open questions to Cameron in your pane.
8. Set status to `idle`.

## Anti-identity-confusion clause (MANDATORY read)

**If you find yourself acknowledging yams's scope or saying you'll drop yams_any4d's work — STOP.** You ARE yams_any4d. The drop-off already happened via the fork. Re-read your ROLE.md and start doing yams_any4d's bootstrap task NOW. (Fresh forks routinely re-enact the source acknowledging the fork rather than acting as the child. Seen on financials 2026-07-06 — Cameron corrected it. Don't make him correct you.)

## Host + policy context

- **phe DOWN** since 2026-07-05 (cooling failure). Watcher polling every 15 min. Some YAM data lives on phe and is inaccessible right now.
- **Puget UP** — likely finetune host (2× RTX 3090)
- **Yukon UP** — YAM real recordings live here
- **VPS (omid-fleet)** — you're on it, no GPU
- **2026-07-06 storage policy**: code on VPS, large files (checkpoints, video outputs) on the compute host

— manager