228dac4c06
Part 0 (live): flash apps on 9201 were down due to an operator pct reboot at 10:26 UTC + a boot-ordering race — dockerd auto-starts unless-stopped flash apps ~18s before the agent re-binds felhom-flash, so the create-time bind mkdir fails (permission denied) and RestartCount=0 never retries. Drive healthy, data intact, no USB drop, durable-id fine, drive-gate uninvolved. v0.70.0 self-restart RULED OUT (container restart, not a guest reboot; +38min after exits). Fix: restarted the 7 apps via the controller (drive present) — all Up. Flagged the intermediary mount app-start race as an architectural gap. Parts 1-3 (cited): characterized escrow (K + identity under recovery code R, fingerprint-gated, hub zero-knowledge) + PBS whole-CT contents (rootfs/secrets in, external drives out) + capstone DONE vs PENDING (agent-side recovery orchestration not wired, syncer.go:92). Defined the secret-free DR recipe (guest sizing + drive durable-id/role inventory + PVE storage + app bindings + PBS coords), sourced from facts the agent/controller already hold, landing in the reserved WireDesiredState.storage_manifest placeholder. Field-by-field boundary proof + a no-secrets test spec. Fork list + recommendation: spec/emit/store the recipe now, defer re-enrollment auth to slice 10D, never touch the escrow/PBS secret path. No code changes, no version bump. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Felhom — Documentation
Felhom is a managed home-server service for Hungarian households, built on a three-component model over Proxmox:
- Hub — operator backend on k3s (
hub.felhom.eu). Repo:felhom.eu/hub/. - Host agent — one per Proxmox host; operator-tier; owns all Proxmox interaction. Repo:
felhom-agent/. - In-guest controller — one per customer LXC; Docker-only; manages the customer's apps. Repo:
felhom-controller/.
This directory is the central, code-verified documentation home for all three components plus the platform and the security-audit record.
Sections
Controller (in-guest) — controller/
The Docker-only app-domain controller. Full per-area docs grounded in current source (v0.59.0).
→ controller/README.md: module map, deploy & stack lifecycle, backup
architecture, storage/monitoring/metrics, auth/hub/sync/integrations.
Host agent & platform — architecture/, proxmox-platform.md
The operator-tier agent and the Proxmox platform.
architecture/01-topology-and-trust.md— topology & trust modelarchitecture/03-host-agent.md— the host agent (Go; v0.29.1)architecture/04-control-plane-authorization.md— signing, escrow, authzarchitecture/02-controller-module-map.md— historical v0.33 planning map; the live map iscontroller/module-map.mdproxmox-platform.md— Proxmox platform reference
Hub (operator backend) — architecture/05
architecture/05-hub-architecture.md— hub architecture (v0.11.0)
Security audits & remediation — audits/
audits/deep-sweep-2026-06-13.md— cross-repo deep audit (controller + agent) with remediation statusaudits/bughunt-reconcile-2026-06-13.md— reconciliation of the v0.30.3 BUGHUNT against current code + merged fix list
Spike & test findings — tests/
Per-slice spike/validation findings (phases 0–5, slices 7–10). See tests/.
Conventions
- Code-verified, not memory-derived. Architectural claims here are checked against the actual current source; if a claim can't be verified it is omitted and flagged, not guessed.
- Per-repo operational working files (
CLAUDE.md,CONTEXT.md,CHANGELOG.md,BUGHUNT.md,REPORT.md,TASK.md) live in their own repos — they are operational, not published docs. - Authoritative versions at last refresh: controller v0.59.0, agent v0.29.1, hub v0.11.0.