Claude Code
6d11c54a50
R-86 (NEXT, operator ruling 2026-07-27): backup-ALIGNED restore-test scheduling — test a tier ~1 day after ITS OWN backup. R-85 schedules on a free-running interval, which cannot express 'the day after the PBS backup': any fixed offset drifts, so alignment would be luck. Shape: trigger from the tier's own last successful backup rather than a clock. Interim in force: 302400s (3.5d), which lands each tier ~weekly — the cadence half of the ruling, not the alignment half. R-87: the restic app-data offsite tier is NEVER restore-tested. R-85 covers whole-guest vzdump tiers only; the agent has no restic surface. That is arguably the tier that matters most — the only one that survives losing the box AND carries the customer's app data, since the whole-guest snapshot excludes the bind-mounted drives. Exactly the state PBS was in before R-85. REPORT.md: the full R-80 -> R-85 arc, including a section on the seven mistakes I made and the two recurring shapes behind them (inferring behaviour from an artifact instead of the code that consumes it; reading a result without its exit code). Records demo-felhom's restore-test as IN FLIGHT at close, with the manual recovery step if the deferred restart watcher does not complete. Hub gate green (17 packages, rc=0).
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.