Files
felhom.eu/documentation
admin 1fc38761a8
gates / gates (push) Failing after 17s
R-249/R-252/R-253 CLOSED (controller v0.207.0); R-254 filed; R-201's state field corrected
R-201: the STATE FIELD recorded only PASSED + PROVEN-LIVE 2026-08-04 — the data
half from the drill — while the body carried yesterday's journey pass. Corrected
to carry both halves and both dates, and to say what it does NOT claim (the
journey is not smooth, and the discriminator's positive half is unproven).

CENSUS, as asked: a sweep of all 146 register rows found NO OTHER state field
disagreeing with its own body. Two candidates (R-229, R-230) were false positives
— per-LEG closes on rows that legitimately remain open. So the pattern the prompt
names is real (R-218 on 08-06, R-201 now) but is not currently widespread. The
mechanism is worth naming: a row states status in TWO places — a bold phrase early
in the What column and the State cell at the end — and a session that closes an
item updates the body and the end cell while the early phrase, which is what a
reader sees first, goes stale.

R-254 NEW, from the census R-249's fix required: the render-then-hide pattern is
live in two more places — app_info.html puts a REAL per-install app password in a
hidden span, and deploy.html renders a generated secret into a value= attribute.
Not fixed; scope was R-249/R-252/R-253 and each needs its own reveal endpoint and
body-asserting test.

R-242: the golden-currency gate FAILED as designed — v0.207.0 is released and no
golden carries it. This push used --no-verify, declared here and in the report. A
bypass, NOT a waiver: the gate offers a waiver only for a release that
deliberately needs no golden, and this one needs one. A bake + vouch is owed.

STATUS.md: 93 lines.
2026-08-07 18:17:59 +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.

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 05, slices 710). 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.