---
name: host-shadow
description: "This workspace runs on host `shadow`, which is an observation/utility station rather than the primary dev environment"
metadata:
node_type: memory
type: project
originSessionId: 71d40fa2-b151-4c81-9821-f0dfeb7a0f66
---

The machine at `/home/ubuntu/workspace` is hostname `shadow`
(public 91.200.242.11, tailscale 100.115.94.5). It is **not** the primary
development host — heavy work and the canonical `infra/`, `tools/`, `web/`
trees live on `arcana` (100.125.166.65).

**Why:** Shadow exists to run scheduled monitors, lightweight Ollama
inference, and Claude Code sessions against arcana. The `SETUP_DONE.md` marker
"AI Agent Stack Restored on Shadow" confirms it was rebuilt as a satellite,
not as a workspace clone.

**How to apply:** When the user references files like `infra/tools/...` or
`web/vvv-bots/...`, they mean arcana paths. Don't try to `ls` them locally —
SSH to arcana or ask. Cron entries copied from arcana frequently target
nonexistent local paths; see [[dead-cron-entries]].