vh
af5582c96d
Claude Code holds an inbound cross-session message unless the sender's permission-mode class matches the receiver's, and holds any sender that asserts no class. The herald is a daemon and asserts none, so on a default-configured seat every cc poke is held at first contact and the notice goes to whoever is watching the pane rather than to the session. The seat still reports declared, reachable and healthy throughout — the same failure shape as the SessionStart hook that was never deployed, where every check was green and nothing arrived. That is what makes it worth a surface of its own rather than a footnote. deploy-althing.sh now reads crossSessionInbound from ~/.claude/settings.json and reports it on every run and on --check. It deliberately does NOT set it: that file is the operator's permission configuration, and a deploy script that edits it is a deploy script granting itself trust. Also records surface 5 (the per-seat route declare), which had been implicit, and why no attestation exists for the herald to send instead — CC reads a sender's live runtime permission mode from the session registry, which a daemon does not appear in.
docs/
Navigation map for the documentation tree. New session? Read
orientation.md first — it's the narrative overview
of the fleet, backup architecture, governing principles, and gotchas,
and it points at everything else.
Tree
docs/
├── orientation.md # start here — fleet overview + where-to-look guide
├── runbooks/ # ops runbooks (recovery, deployment phases)
│ ├── disaster-recovery.md
│ ├── nh3-prune-ritual.md
│ └── pbs-deployment.md
└── pfi/ # PFI-specific reference (services, models, VMs)
├── docker-stack.md
├── model-list.md
├── proxmox-vms.md
├── recommended-model-settings.md
├── vm-102-matrix-appservice.md
└── vm-102-matrix-synapse.md
What goes where
runbooks/— step-by-step ops procedures. Anything you'd reach for during an incident or while standing up new infrastructure. Examples: disaster recovery (blast-radius tiers + restoration steps), PBS deployment (9-phase rollout). New runbook → new file here.pfi/— PFI-specific reference material that's too narrow for the top-level CLAUDE.md but doesn't change incident response. AI model inventory, recommended inference settings, Matrix bridge config, Proxmox VM map. New stable reference → new file here.- Top-level (
docs/orientation.md,docs/README.md) — narrative guides about the workspace itself, not about specific infra.
Cross-references
- Fleet topology + servers table: top-level
CLAUDE.md. - Open work + recent milestones: top-level
STATUS.md. - Durable cross-session facts:
~/.claude/projects/-home-lkraven-development-eshpfi-management/memory/.
Conventions
- Markdown, GitHub-flavored. CommonMark renders fine in most viewers.
- File names are lowercase-kebab-case, descriptive. No dates in filenames — git history covers that.
- One topic per file. If a file grows past ~500 lines, look for a natural split before adding more.
- No checked-in binaries or checksums. Build/release artifacts belong
in a build pipeline or
tools/, notdocs/.