Files
felhom.eu/documentation
admin 5f2ccec64c
gates / gates (push) Successful in 19s
CHAOS NIGHT: household seeded, escrow done, round 1 measured
Phase 0 finished: all twelve apps deployed one at a time (the parallel burst was
my error and is recorded as such), escrow ceremony completed after the box
converged the PBS descriptor by itself (~17 min), and the R-543 bar disappeared
for good once escrowed.

Round 1 (offsite-run, control round, no accident):
- the run started on the button's own endpoint and walked every app with real
  per-volume byte counts (stop -> dump -> restart)
- three alarms fired, all TRUE and precise: app_start_failed named the one
  crash-looping app, backup_run_failures said "1 of 12 ... nextcloud", and
  offbox_repo_orphaned reported the documented rebuild behaviour rather than
  claiming a successful copy
- nextcloud's crash loop is MY damage (image layers written while the thin pool
  was 100% full -> "invalid ELF header"), not a product defect, and is recorded
  that way

The catalog bump was prepared and then REVERTED UNPUSHED: the catalog repo's own
gates returned INCONCLUSIVE (the volume-persistence prober failed its own
canary), and undetermined is never a pass. Round 7's `update` therefore becomes
`use`, decided now rather than improvised at 02:00.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS
2026-09-16 23:10:37 +02:00
..

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.

Where we stand — architecture/where-felhom-stands.*

The operator's one-page picture of what is proven, built, partial and missing.

Host agent & platform — architecture/, proxmox-platform.md

The operator-tier agent and the Proxmox platform.

Hub (operator backend) — architecture/05

Security audits & remediation — audits/

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.