# STATUS — what works, what's broken, what's next **Updated 2026-08-08 (overnight — Campaign 12).** > **A view, not a source.** `documentation/backlog/OPEN-ITEMS.md` is the authority; this page restates > part of it in plain words, and **nothing may exist only here**. Not `CONTEXT.md`, which is technical > state written for Claude Code. **Items, not paragraphs. One screen.** If it does not fit, something > belongs in the register instead. > > *Rebuilt from the register on 2026-08-07, from 258 lines. The old "what shipped recently" log is what > the per-repo `CHANGELOG.md` files and the register are for, and is not restated here.* ## What works A blank machine boots the Felhom disc, installs itself unattended, and is claimed by the customer, who sets their own password. They install apps from a catalogue of fifty-three, share files over the home network, and open apps from a launcher or a shared link. Backups run on their own to three places — the machine's drive, a second drive, and an encrypted off-site copy. **The backup promise is proved, and so is getting the data back yourself.** A machine has been destroyed on purpose and its files came back byte for byte identical — four times now, including a filename with Hungarian accents. On **2026-08-07 the household's own journey passed for the first time**: someone with a browser and their recovery code got everything back with **no command line inside the machine at any point**. From logging in to seeing what is in the store took **72 seconds**. *(R-201 — closed.)* **And the two rough edges that walk found are gone** — after a rebuild the restore used to stop dead twice; both refusals now say what happened, that nothing is lost, and link to the screen that fixes it. *(R-252, R-253 — closed 2026-08-08.)* ## What's broken - **Nothing new is broken.** All three secret-in-page faults are fixed; what remains is that the *check* against a fourth covers 4 pages of 27, and the cheap one covering all of them is blind to the shape that actually shipped. *(R-255)* - **The machine's own screen keeps telling an already-paired box to pair itself** — 25 minutes after it was paired, on a screen that promises it refreshes itself. *(R-214, R-235)* - **A rebuilt machine cannot create a new recovery code at all.** *(R-221)* - **A backup that covered nothing still calls itself „Sikeres".** The state is honest; the word is not. *(R-240)* - **A machine waiting for its recovery code can stop backing up off-site without alarming us.** After a *rebuild* we ARE told; the gap is a box reaching that state with no working tier behind it. *(R-243)* - **The card offering to reopen set-aside backups promises more than we can deliver** — we keep the old sealed package, but nothing can open it. *(R-202)* - **Deleting a customer leaves rows behind** on every test machine ever torn down, while reporting a clean teardown. No secrets involved, but it accumulates with each walk. *(R-244)* - **Putting restored files back where they belong is still a manual step.** *(R-213)* ## Found overnight — we went looking for siblings, on purpose Every fault this month came in one of seven shapes; overnight we looked for the others **by shape** — reading and counting only, nothing changed or deployed, no machine touched. Eight new items, none urgent. Full working: `audits/CAMPAIGN-12-class-sweep-2026-08-08.md`. - **The one that matters.** The machine tells us whether your engineer's emergency key is really installed — and **we throw that sentence away before reading it**, so a box can read as "we can get in" when nobody can. Same shape in seven other places. *(R-260)* - **A green tick meaning only "a backup exists"** — any age counts, and it reddens on a problem measured across all apps rather than that one. *(R-258)* - **A disk we failed to measure is drawn as an empty, healthy one** — "0.0 GB / 0.0 GB (0%)" in the normal colour, while the right pattern sits two files away. *(R-259)* - **Two comments promise more than the code does** (one guarded by a test that cannot fail on the thing it names), and **two refusals still stop at "no"**, one in half-English. *(R-262, R-263, R-256, R-257)* - **Which shapes can a machine catch from now on?** That mattered more than the list: **one is cheap and worth doing** (the thrown-away-sentence one, which would have caught every instance on the day it was written), two need a small decision first, and **two are honestly not automatable** — including the one that looked most automatable, where the standard tool was tested and found blind. Recorded, not built. *(ROADMAP G-1…G-8)* ## What we're working on - **Widening the check** so a fourth secret-in-a-page is caught by a machine, not by someone. *(R-255)* - **Proving the hub really keeps the old sealed key** when a machine re-seals — needs its own session and a second deliberate wipe. *(R-198)* ## Waiting on you - **One approval: the new base image.** Tonight's release is baked, published and byte-checked, and **installations still receive yesterday's version until you press Save.** Hub → Configuration → Day-0 artifacts → Golden **0.208.0** → Save. One field moves; the other two are already right and were checked. Reversible — re-select 0.207.0 and Save. *(R-242)* - **Third time in three days, so worth a minute.** A check now catches the *baking* being forgotten; **nothing catches the approval being forgotten** — tonight's bake proved it, going green before the approval existed. Two ways to close it are written up, neither built. *(ROADMAP G-8)* ## DooPlex infrastructure — separate from the product *Kept under its own heading rather than dropped: these are real asks that need you, but they concern the machine all this is built on, not what a customer receives. Mixing them in is why the page stopped being readable.* - **DooPlex's own backup keeps every copy inside the same box, and is silent when it fails.** *(R-232)* - **193 old images exist only on this machine**, ~27 GB against 199 GB free — clutter, not space. *(R-210)* - **The hub password needs rotating** — a diagnostic printed it into a session log; nothing suggests anyone else saw it. *(R-132)* - **One thing to read after DooPlex next restarts** — the second-SSD move has never survived a reboot; it writes PASS/FAIL to `/var/log/felhom-store-postboot-check.log`. On PASS, 34 GB comes back. *(R-209a)* - **Backup scripts on DooPlex are unversioned host state** *(R-231)*, and the instruction-file follow-ups each need a decision rather than an edit *(R-229, R-230)*.