Claude Code
b802a9e7de
Written against verified state, not assumption. Records three gaps the original Phase 5 ordering does not cover: 1. hub v0.77.0 is COMMITTED BUT NOT DEPLOYED — manifest pins 0.76.0 and the pod runs 0.76.0, so the R-85 signal exists only in git. The original Phase 5 only mentions the agent. 2. R-85 has no ROADMAP row. 3. The agent CHANGELOG says v0.104.0-dev; an ldflags version disagreeing with the CHANGELOG is the reconciliation problem hub 0.73.2 already caused. One ordering correction: THE HUB GOES FIRST. Agent v0.104.0 makes the offsite tier testable; hub v0.77.0 makes a failure audible. Agent-first means rotation begins with nothing listening — two tiers able to fail silently instead of one, which is the fault R-85 exists to end. Also drops the retired drill box, so the rollout is demo-hp -> demo-felhom. Names the phase's most likely SILENT failure: the new rotation state lands at /var/lib/felhom-agent/restore-test-state.json and the agent is non-root. If that is not writable, RecordSuccess warns and continues — a quiet return to one tier being starved, not a crash. Flags for operator judgement: demo-felhom's 14.46 GB offsite archive makes its unattended restore-test a ~2h operation every other day, holding the heavy-op gate throughout. Ruled when the only measured restore was demo-hp's 4 minutes.
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.