vh
0bbdaf9083
I described ea:f6:0a:ca:f5:b4 as "locally administered, no OUI" and treated it as the class of MAC that may regenerate at boot. ha-dev corrected it and the correction verifies: the device advertises e8:f6:0a:ca:f5:b4 over mDNS, which differs in exactly the locally-administered bit, and E8:F6:0A is registered to Espressif Inc. in the IEEE registry while EA:F6:0A resolves to nothing. That is the standard ESP32 pattern — one factory base MAC in eFuse, sibling interface MACs derived deterministically — so the reservation is keyed correctly and cannot drift on its own. The PoE-cycle test still stands and is now corroborating evidence rather than the only evidence. The residual risk narrows to a firmware change to the derivation scheme. Also from ha-dev: tcp/7638 is open alongside 6638; mDNS crosses the VLAN boundary so HA rediscovers without help; and HA's pending smlight config flow is keyed on the mDNS service name, which did not change, so a stale flow may still hold the dead 10.0.10.58 and should be dismissed rather than confirmed. ha-dev declined the dns: resolver fix on their stack — configuring by IP costs them nothing and the entry would couple HA name resolution to AdGuard uptime for no present benefit.
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/.