---
name: russet-abandoned-2026-06-08
description: russet (TRI robot-lab YAM rig at 100.123.182.78) is no longer in active use as of 2026-06-08 — yukon is the live YAM rig
metadata: 
  node_type: memory
  type: project
  originSessionId: cd07777c-8add-4afc-9cb9-9113caa0331f
---

russet is abandoned as of 2026-06-08. **yukon is the active YAM rig**; russet is not being used anymore.

**Why:** Confirmed by a rescue-agent message on 2026-06-08 while resolving a stale yukon sshfs mount: *"Do NOT touch or remount russet; we are not using that machine anymore."* Earlier vault content (`vault/tri/overview.md`, [[feedback_vault_references]]) had russet documented as a co-equal YAM station with yukon. That snapshot is stale.

**How to apply:**
- Don't dispatch tasks to the russet machine. Don't touch the russet tmux window (`agents:russet_yam`) — it can stay empty.
- Don't set up SSH keys for russet (the prior "russet → yukon → mount" plan is dead).
- When dispatching YAM/TRI work, route to **yukon** (mount at `/home/cameronsmith/mnt/yukon` → `/data/cameron/yukon_remote`).
- When updating vault/tri/overview.md or vault/para/robot/yam/, demote russet to "abandoned" (don't delete the historical references — they're useful context for handoff data still on russet).
- The robot-lab mount (`/home/cameronsmith/mnt/robot-lab` → puget) is unrelated and still healthy.

**Tripwires for re-checking:** if Cameron mentions russet positively (e.g., "the russet run" or "russet has the…"), confirm before assuming this still holds — could be a context shift.