Files
felhom.eu/documentation
admin c8100aad6b
gates / gates (push) Failing after 17s
Housekeeping + R-397/R-398 filed
Compresses the six rows closed today into CLOSED-ITEMS, keeping title, shipping
version, evidence paths and every sentence that states a RULE. Full original:
`git show e027b5d9 -- documentation/backlog/OPEN-ITEMS.md`. No open row touched.
Register 165 -> 167 -> 161.

Files two rows that would otherwise have died in an overwritten REPORT.md, which
is what the controller's observations gate exists to prevent:

R-397 -- NotifyIntegrityOK/NotifyIntegrityFailed have no caller anywhere and the
controller runs no integrity check at all. The part that actively misleads is not
the dead code: config.Monitoring.PingUUIDs carries a backup_integrity field and
the monitoring page renders "Mentes integritas -- Hetente (vasarnap)", so the
operator is told a weekly check runs. Decide WHETHER one is wanted, then delete
or build -- do not leave the third state.

R-398 -- resticStep is not a seam, so no test can drive any restic-backed path.
Felt directly in v0.226.0: R-358's safety property is an ORDER (clear the marker
before restic, write it after) and with no seam it could only be pinned by an AST
walk. The contrast is the argument -- offboxLatestSnapshot got a seam in the same
release, in four lines, because a correctness gate could not otherwise be proven.

This push used `git push --no-verify`. golden-currency remains CONVICTED and
remains right: three controller releases today, golden still 0.223.0. Bypass, not
waiver, on the operator's standing ruling, re-checked for this release rather
than reused blindly. Tracked on R-242; one bake carrying 0.226.0 covers all three.
2026-08-30 19:51:31 +02:00
..
2026-08-30 19:51:31 +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.