admin
225afa0f30
gates / gates (push) Successful in 6m4s
The first real tester answered on Prohardver today. His domain is bought in his name (terms 1.1 §4), so his name, address, e-mail and phone leave this house - and the privacy notice did not say so. Now it does, before the purchase. Operator rulings, asked before the work and recorded in CONTEXT.md: - Registrar for a tester's .hu domain: Nethely Kft. - The tester's zone lives in FELHOM's Cloudflare account during the test. This is what the build already assumed (day0-install A.1 + the one-zone token guard of 01 §7 / R-138 option C) and nothing had recorded it; it answers open point 9 of the privacy draft. Privacy notice 1.1: - New §10 "A domained regisztrációja": exactly the four fields the .hu Domainregisztrációs Szabályzat §1.2.2.1 requires of a natural person (the optional mother's name, birth date and ID number are NOT asked for), by e-mail, to Nethely and the .hu registry (both named with seats), why, how long, and what is public - a natural person shows as "Természetes személy" only. - It also states whose Cloudflare account holds the zone and that the domain moves to the tester's own account when he leaves. - §11 (recipients) gained the two new names: a recipients list that omits two recipients is wrong. That is the one change beyond the new section. - 1.0 -> 1.1 diff: the only removed/changed lines are the record's title and derived-on date, the version line, and four renumbered headings. marketing/testers/kit/: five files + README, Hungarian, first person. Questions about the machine and the net (each traced to day0-install Part B or the FAQ), the domain data request, the tester's acceptance e-mail (no domain purchase before it arrives), the welcome e-mail with the recovery-code warning, and the operator's own step list. No personal data in any of it - placeholders only. Also: EMAIL-privacy-1.1.md for the existing testers, the legal README pointing at the 1.1 records, and one plural verb the voice sweep missed in the FAQ.
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.
architecture/where-felhom-stands.html— generated; do not hand-editarchitecture/where-felhom-stands.yaml— the data behind it; every claim cites its source. Gate:scripts/check_stands.py; regenerate withscripts/render_stands.pyarchitecture/where-felhom-stands-2026-08-09-snapshot.html— a dated snapshot, NOT maintained. The original React bundle, kept for the record; its statuses are those of 2026-08-09 before the verification pass
The whole system on one page — architecture/felhom-system-poster.*
A poster for the operator: every machine, path, backup tier, time and key on a single sheet.
architecture/felhom-system-poster.html— the drawing. Made in Claude Design, NOT generated by anything in this repo, so do not expect a renderer; it is self-contained (fonts and scripts are inlined — it opens with no network)architecture/felhom-system-poster.facts.md— the source of every fact on it. Change the facts here first. Rule:.claude/rules/unprompted-work.md§6. Gate:scripts/poster_facts_gate.pyWARNS (never fails) when this file has a newer commit than the drawing
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 referencearchitecture/11-os-updates.md— operating-system updates: host, guest, Docker engine (NOT RATIFIED, 2026-10-04)
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.