admin
0d1cf0f732
Data document, no design. Parts A-G plus Unknowns/Contradictions/Observations. Headlines: - A: 12 restore paths. 7 are customer-unassisted (all app-level); every whole-guest and host-level path is operator-SSH-only. - B: independent catalog enumeration gives Tier-2 file-leg coverage 7/53 and Tier-3 mandatory coverage 4/53; does not reproduce the shipped C9-F1 figure of 9/53. Tier-3 captures named-volume tars on every run and no offsite action unpacks them. - C: three circular dependencies, incl. app-tier restore being conditioned on the whole-guest tier (encryption.key), and break-glass credentials reachable only through the hub that DooPlex hosts. - D1: host state is in no backup of any kind; no host has ever been rebuilt as itself. - D2: hosts.dr_record_json, host_escrow.directive_json and dr_recipe drives[] are all empty on the live fleet, and dr_recipe records the PBS namespace as 'root'. - E: local vzdump shares its physical disk with the guest it backs up (both hosts); hub.felhom.eu resolves straight to DooPlex's own public IP, not a CF tunnel. - F: every measured RTO extracted; the unmeasured ones listed, none estimated. Nothing was changed, deployed or restarted; peti-felhom untouched.
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.