Skip to content

map — how to walk it, the universes, the collisions

Reading protocol

Entry (CLAUDE.md, ~600 tokens) → one card (~400–900 tokens) → the cited source file if you need the exact line. That is the whole load for most questions: 2–3k tokens. The folder is not a search index; the catalog exists so nobody greps objects/.

Universes

Universe Meaning here
live in force on the box today; implement and cite against it
leftover still on disk, no longer the path anything takes (old UUID files, .bak compose copies, prowlarr-broken-*, recovered-* trees)
ghost named somewhere, not wired (the compose samba service, /mnt/media, media-backup.sh.disabled, the disabled cloud training routine)

Name collisions

Word Means Not
Plex hostname of the box (hostnamePlex) the plex container (linuxserver/plex, port 32400)
samba a service in torrentvpn/docker-compose.yml that has drifted from reality (binds /mnt/storage/…) samba-nas, the live container, started with docker run, binds /mnt/disk1/Storage-snapshots
storage /mnt/storage, the mergerfs union of disk1–3 Storage-snapshots, rsnapshot's hardlink forest on /mnt/disk1 (excluded from parity)
d1 d2 d3 SnapRAID's names in /etc/snapraid.conf device letters sda…, which reshuffle
content file snapraid.content — the array index, four copies snapraid.conf, the config (can be regenerated from the content file)
precious /home/angel/precious, the NVMe copy of immich + EmbeddedEra the rescue USB, which holds configs, not media
rescue kit /mnt/rescue (USB) built by /usr/local/bin/rescue-sync.sh ~/rescue-kit/, the source directory those scripts are installed from
docker-backups /mnt/storage/docker-backups/snapshots/ (7 kept) — configs only, no compose/ the rescue USB archive, which does carry compose + env.gpg
routines ~/.claude/routines/*.md, local prompts run by cron via training-sync claude.ai cloud routines (one exists, trig_01Ke8GAbB9q1y4J7UXqRhtm2, disabled, old single-pass design)
hub claude-hub, a user systemd service on hub.lan Claude Code itself

Where a fact lives

  • Server facts (paths, units, numbers, what runs when): a card here. One home.
  • Who the user is, how they want work done: ~/.claude/projects/-home-angel/memory/. Cards may link there; memory files should point at cards rather than restate them.
  • The narrative of the hardening work: the artifact linked from objects/storage/hardening-plan.md. The card is the catalog; the artifact is the prose.

Maintaining

  • Changed the server? Edit the card, bump verified, cite the line. Then _meta/build-index.sh.
  • New noun or verb? Copy from _templates/. Keep clusters at four unless a fifth appears three times.
  • Never add a "how to read this map" essay. If a walk fails, move or split a file.