From b07e4af0c197e8483ecd6e3a3999cc3969482b9a Mon Sep 17 00:00:00 2001 From: kisfenyo Date: Sun, 15 Nov 2026 15:52:02 +0100 Subject: [PATCH] =?UTF-8?q?09=20=C2=A73=20decisions=20313-316:=20D86=20rem?= =?UTF-8?q?ove,=20D87=20keep,=20the=20notice=20lock,=20the=20text=20change?= =?UTF-8?q?s=20(operator,=202026-11-15=20evening)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS --- STATUS.md | 2 -- .../architecture/09-update-architecture.md | 27 +++++++++++++++++++ documentation/backlog/OPEN-ITEMS.md | 4 +-- 3 files changed, 29 insertions(+), 4 deletions(-) diff --git a/STATUS.md b/STATUS.md index e6b1c5ce..e53b1099 100644 --- a/STATUS.md +++ b/STATUS.md @@ -32,8 +32,6 @@ Newest first. CC's pick is in the „Pick" column. Each row also has its full te | # | Row | Question | Pick (why) | The other option costs | If you do nothing | Blocked | |---|---|---|---|---|---|---| -| D87 | R-1374 | CC narrowed your D84 by itself: one weekly window removes at most the cap's size of a removed app's off-site copies, and a removal of more than half of the store waits one week and mails you first. Keep it? | **Keep** (a review showed that without it a taken-over box empties the whole store after 30 days, in one window, with no mail) | reverse: a large removed app goes in one window; the 30 days are then the only brake | it stays as built | — | -| D86 | R-1376 | After a household is deleted, the delete journal keeps its id for ever, and an id can be a name. After one year: remove the id, or put a code in its place? | **Remove it** (the privacy sentence is then short and true; nothing in the hub reads the id after the year) | a code: you can still ask „was this id deleted?”, but a code made from a name is still that person's data, and the hub must keep a key | the id stays for ever and the privacy sentence stays unpublished | the privacy sentence | | D66 | R-1365 | Should a security-watch source that stays down mail again every 7 days, as an open notice does? Today it mails once, then only the Monday summary lists it. | **Yes** (a real outage then cannot be forgotten; the seven pins that can never be read no longer count, so it stays quiet when all is well) | no: one line in a long Monday mail stays the only reminder | a source that stays down mails once; the Monday list still shows it | — | | D38 | R-1235 | Put the newest golden (637 MB) into the nightly release copy on ep0 too? | **Yes** (a new install after a DooPlex loss needs it; it fits under the 3 GB cap) | leave it out: after a loss, no new install until a golden is rebuilt and vouched | the same | — | | D37 | R-1236 | Raise Gitea's memory limit from 1 GiB to 2 GiB? It was killed for memory 4 times in 17 days, once during today's release. | **Yes** (DooPlex has the RAM; a DooPlex change, so yours) | keep 1 GiB: a restart in release hours fails box updates and CI for a minute | the same | — | diff --git a/documentation/architecture/09-update-architecture.md b/documentation/architecture/09-update-architecture.md index 9d8513ad..6e5953aa 100644 --- a/documentation/architecture/09-update-architecture.md +++ b/documentation/architecture/09-update-architecture.md @@ -1265,6 +1265,33 @@ Recorded before the work (`audits/space-list-2026-11-10/README.md` §5 held the Hetzner and the mail service are read from source and documents only: no hub database read, no account call. *Operator, 2026-11-10 12:22.* +### 2026-11-15 (evening, operator, the start line of the second build of release 4) — D86, D87, the notice lock, the text changes + +The operator's line, word for word: „D86 remove. D87 keep. Notice lock yes. Text changes yes.” + +313. **D87 = keep: CC's narrowing of D84 stands.** One weekly window removes at most the cap's size of removed apps' + off-site copies beside the cap, and a removal of more than half of the store waits one week after a mail to the + operator (`07-backup-architecture.md` §8.2f). **Cost of the other option (reverse):** a large removed app goes in + one window, and the 30 days are the only brake against a taken-over box. R-1374. *Operator, 2026-11-15 evening.* +314. **D86 = remove: after the one-year prune the id columns of the two delete-journal tables hold no id** + (`05-hub-architecture.md` §14.3, option A). **Cost of the other option (a code in its place):** a code made from + a name is still that person's data, and the hub must keep a key. The privacy sentence is still NOT published: it + goes to the operator with the lawyer rows (R-802, R-813). R-1376. *Operator, 2026-11-15 evening.* +315. **The notice lock = yes: no notice, no deletion.** The hub sends the household's notice itself, from its own + state, until it has gone; and the hub agrees to remove an app's off-site copies only when its own record says the + household was told at least 30 days ago, by the hub's clock — beside the 30 days of absence, not in place of + them (`07` §8.2f). **Cost of the other option:** the mail D84 promises is not a condition of the deletion: a lost + event of the box, a failed send or the daily limit, and the copies go all the same. R-1374. + *Operator, 2026-11-15 evening.* +316. **The text changes = yes:** the notice says what to do „if this was not you”; its subject names the deletion and + its day; the remove dialog does not show the older sentence about the nightly snapshots where the new line shows + (`07` §8.2f, the text table). Built and listed for the operator; not published by CC. R-1374. + *Operator, 2026-11-15 evening.* + +**Accepted without a question in the same line's brief (the reviewer read them; the operator may still reverse):** the +receipt ignores the household's notification switches; no end record on a box whose off-site target is the +household's own NAS; „delete in 30 days” is offered for every removed app with copies and no mark. + ### 2026-11-15 (12:49, operator, planning chat) — D83, D84, D85; CC's unattended decision accepted; the privacy sentence waits 308. **D83 = refuse, with one named flag for the operator.** An appliance install on a system disk below 200 GB diff --git a/documentation/backlog/OPEN-ITEMS.md b/documentation/backlog/OPEN-ITEMS.md index 122bd342..c0c3374b 100644 --- a/documentation/backlog/OPEN-ITEMS.md +++ b/documentation/backlog/OPEN-ITEMS.md @@ -219,7 +219,7 @@ stopping line that lies. | **R-1263** | Backup & restore | P4 | **Small items from review round 2:** a LOCAL restore's put-back mails the operator „its off-site restore FAILED” (`felhom-controller/controller/cmd/controller/main.go:1514-1518`, shared via `restore_unit.go:517-518`); Remove — even „keep my data” — deletes undeclared volumes labelled with the app's project, which no tier holds (`internal/stacks/delete.go:763-764`, R-1117); the capped copy's `--delete` reads the source in the daemon's mount view, the emptiness check in the controller's (`tier2.go:834` vs `:464`); stale comments — `felhom-agent/internal/localapi/backup_cap.go:15` („keep-last”) and `restore_crash_putback.go:32` (names a test file that does not exist); the qBittorrent password goes to whatever answers the DNS name `qbittorrent` (`upwatch/explain.go:94,108-113`); kept-copy Remove has a check-to-remove gap (`tier2_kept.go:92-111`); the release-copy restore check trusts hashes stored on ep0 (`runbooks/total-loss-of-dooplex.md`); rrsync without `-munge`/`-wo` (`audits/day-2026-10-23/08-release-copy-D33.txt:6`). | OPEN | — | fix in each repo's next attended pass | CC | | **R-1294** | Backup & restore | P3 | **demo-hp's weekly off-site clean-up was refused by its own guard on 2026-10-26 (window 16): the plan would remove 209 of 359 snapshots, above the week's cap (179) — nothing was deleted, and each refused week adds to the next plan.** Seen in the operator mailbox during the 2026-10-26 release run (03:17Z, `offsite_prune_guard_refused`, error; details `count_before 359, count_after 359, outcome guard-refused`). The cap refusal is kept on purpose (R-824, R-867 closed the false ones); the open question is whether a store that once exceeds the cap can ever prune again by itself, or refuses every week while it grows. demo-hp is the Tier-0 box with many hand-made backups (sweeps, probes). Earlier cap refusals: demo-hp 2026-10-03 (window 1), demo-felhom 2026-10-05 (window 3). **2026-11-11:** the End-dates list leans on this row (`documentation/audits/end-dates-list-2026-11-11/TABLE.md` DB05). | **OPEN — the grant is SET (D55 = 260, `09` §3 decision 268)**: 2026-10-26 19:10:31Z through the operator's one-purpose token `cc-d55-window`, read back `max:260`; it is used at demo-hp's next window request (after its nightly off-site run, ~03:15Z). Close when that window prunes; then the operator revokes the token. **Earlier:** WAITING-ON-OPERATOR — 2026-10-26 evening: CC could NOT set the D54 grant — `POST /offsite/window-grant/demo-hp` (`max_remove=220`) with CC's hub token answered **403 „missing scope offsite:write"** (the hub log shows the refusal; nothing granted). The plan also grows: restic's dry-run 2026-10-26 18:56Z still 359 copies / plan 209 / default cap 179 (before tonight's run); a simulation of the keep rule adds ~14 per night (14 of 18 groups back up nightly), so ~223 at the night of 10-27 and ~237 at 10-28 — a cap of 220 would be refused again. STATUS D55: the operator grants it, with the cap. The grant opens the box's NEXT window request, which comes after its next nightly off-site run. Ruled D54 = prune once (`09` §3 decision 266). **Earlier:** WAITING-ON-OPERATOR — 2026-10-26 (read only, `audits/r1294-offsite-cap-2026-10-26/`): the plan is HONEST (restic's own dry-run: keep 150, remove 209; every removal 7–30 days old; every app keeps ≥ 9 or its last copies; the bulk is one test day, 2026-10-16, 152 snapshots). It can NOT recover by itself: the cap is half the store and grows ~49/week while the plan grows ~84/week. Only demo-hp has this shape (demo-felhom and Tester 1 pruned normally 10-26). The pick is STATUS D54. **Earlier:** OPEN **2026-11-10 (space list, `documentation/audits/space-list-2026-11-10/TABLE.md`):** place O1, listed from documents only (the off-site box was not read in this run — second pass). **2026-11-10:** the endings list leans on this row (`documentation/audits/endings-list-2026-11-10/TABLE.md` EC23-7). | — | read the guard's cap rule (controller off-site prune) against demo-hp's snapshot list: is the plan honest (old, superseded) or not; if honest, say how such a store gets back under the cap (an attended one-time prune, or a cap that follows the store) — a design question for the operator if it changes what a box may delete | CC | | **R-1362** | Backup & restore | P3 | **With the internet down, the Backups page takes over 2 minutes (135 s and 145 s measured; 5 s with only the hub down).** Walked 2026-11-03 on Tester 1: every other page answers at once on the home network. The page waits on something off-site inside its handler; a household that lost its line and opens exactly this page sees a hang. `audits/security-2026-11-02/part5/outage-wan.log` | OPEN — filed 2026-11-03 | — | name the wait with a timing, then give it a short deadline and show „the off-site state could not be read" | CC | -| **R-1374** | Backup & restore | P3 | **Four kinds of copy are kept with no end named, and nobody is reminded of them.** Found 2026-11-10 (the endings list, `documentation/audits/endings-list-2026-11-10/TABLE.md` endings EC02, EC23, EC18, EC27; read in source; 9202 has no off-site store, so not measured). (1) **Off-site snapshots of a removed app**: the removal keeps them by ruling (closed R-474), and the weekly clean-up keeps the last snapshots of each app for ever (`internal/backup/offbox_window.go:80-82`), also for an app that is gone. No rule says when they end. (2) **A whole restore from the second drive** moves the old files beside the restored ones (`internal/backup/tier2_whole.go:52`, `:132`, `:345`); nothing removes them later and no page lists them. (3) **Exported app files** stay in the export folder of the drive; the pages can start, list and read an export, none deletes one, and nothing ages it (`internal/web/handler_export.go:30-87`). **Members (answers marked N):** EC02-4, EC23-4, EC18-4, EC27-4. | NARROWED — **2026-11-15 (build of release 4): part (1) is BUILT on both sides, not released** (controller `main` after 0.353.0, hub `main` after 0.182.0; `07-backup-architecture.md` §8.2f `[FACT — built, not released]`). The record, the date before the press, the take-back, the hub's agreement by its own clock, the deletion inside the weekly window by id, the audit's explanation, one mail to the household at the press. An independent review found five defects, all fixed with tests seen red (a box could have the hub agree to the whole store; a take-back or an install during the window still deleted; an import kept the record; a box could word and flood the household's mail; a version skew stalled the clean-up). **Decided by CC unattended (D87 asks the operator):** one window removes at most the cap's size of ended-app snapshots beside the cap, and a request for more than half of the store waits one week with a mail to the operator. **Open limits, said in §8.2f:** a box that stops listing a living app looks like an honest removal (bounded by the cap per week, and by the 30 days); an install during the forget itself loses the copies; a box that names agreed ids but removes others is caught at 07:10, not at the close. **Nothing ran on a box or against a real store.** Parts (2) and (3) are not touched. Earlier: OPEN — **2026-11-15 12:49 — RULED (D84 = yes; `09` §3 decision 309).** Fix shape for part (1): the five parts of `07` §8.2f, with the ended apps' own allowance outside the weekly cap (only for ids the hub agreed to) and ONE mail to the household at the press of „delete backup data” (the app, the end date, how to take it back). Earlier: OPEN — **2026-11-14 (night build):** the design for part (1) is written, not built: `07-backup-architecture.md` §8.2f (the record, the date shown before the press, the take-back button, the deletion inside the weekly window after the hub agrees, 14 edge cases, the texts in Hungarian and English as a proposal). One open decision is in it: do the ended apps' snapshots count toward the window's weekly cap (CC's pick: no). Parts (2) and (3) are not touched. OPEN — filed 2026-11-10 (endings list) **2026-11-10 15:19 — RULED (D72 = yes, by the household's own choice; `09` §3 decision 292).** Not built. | — | Controller (D72): when the household pressed „delete backup data” for an app, its off-site copies end 30 days later, at the next clean-up after that day (the number of a restore copy, D62); when the household kept the backups, the off-site copies stay. The page shows the end date before anything is deleted — write that into `07-backup-architecture.md` before the build. Parts (2) and (3): a delete on the export page; a line on the kept-data page for the files a whole restore set aside. | CC | +| **R-1374** | Backup & restore | P3 | **Four kinds of copy are kept with no end named, and nobody is reminded of them.** Found 2026-11-10 (the endings list, `documentation/audits/endings-list-2026-11-10/TABLE.md` endings EC02, EC23, EC18, EC27; read in source; 9202 has no off-site store, so not measured). (1) **Off-site snapshots of a removed app**: the removal keeps them by ruling (closed R-474), and the weekly clean-up keeps the last snapshots of each app for ever (`internal/backup/offbox_window.go:80-82`), also for an app that is gone. No rule says when they end. (2) **A whole restore from the second drive** moves the old files beside the restored ones (`internal/backup/tier2_whole.go:52`, `:132`, `:345`); nothing removes them later and no page lists them. (3) **Exported app files** stay in the export folder of the drive; the pages can start, list and read an export, none deletes one, and nothing ages it (`internal/web/handler_export.go:30-87`). **Members (answers marked N):** EC02-4, EC23-4, EC18-4, EC27-4. | NARROWED — **2026-11-15 evening — RULED: D87 = keep (decision 313); the notice lock = yes (315); the text changes = yes (316).** Fix shape of the lock: the hub mails the household itself, from its own state, when a report first names an app in the box's pending end records, and tries again until its record says „told”; the hub agrees to an app only 30 days after that record, by its own clock, beside the 30 days of absence; no address → the operator is told once and that starts the 30 days; a take-back or an install voids the notice. Earlier: NARROWED — **2026-11-15 (build of release 4): part (1) is BUILT on both sides, not released** (controller `main` after 0.353.0, hub `main` after 0.182.0; `07-backup-architecture.md` §8.2f `[FACT — built, not released]`). The record, the date before the press, the take-back, the hub's agreement by its own clock, the deletion inside the weekly window by id, the audit's explanation, one mail to the household at the press. An independent review found five defects, all fixed with tests seen red (a box could have the hub agree to the whole store; a take-back or an install during the window still deleted; an import kept the record; a box could word and flood the household's mail; a version skew stalled the clean-up). **Decided by CC unattended (D87 asks the operator):** one window removes at most the cap's size of ended-app snapshots beside the cap, and a request for more than half of the store waits one week with a mail to the operator. **Open limits, said in §8.2f:** a box that stops listing a living app looks like an honest removal (bounded by the cap per week, and by the 30 days); an install during the forget itself loses the copies; a box that names agreed ids but removes others is caught at 07:10, not at the close. **Nothing ran on a box or against a real store.** Parts (2) and (3) are not touched. Earlier: OPEN — **2026-11-15 12:49 — RULED (D84 = yes; `09` §3 decision 309).** Fix shape for part (1): the five parts of `07` §8.2f, with the ended apps' own allowance outside the weekly cap (only for ids the hub agreed to) and ONE mail to the household at the press of „delete backup data” (the app, the end date, how to take it back). Earlier: OPEN — **2026-11-14 (night build):** the design for part (1) is written, not built: `07-backup-architecture.md` §8.2f (the record, the date shown before the press, the take-back button, the deletion inside the weekly window after the hub agrees, 14 edge cases, the texts in Hungarian and English as a proposal). One open decision is in it: do the ended apps' snapshots count toward the window's weekly cap (CC's pick: no). Parts (2) and (3) are not touched. OPEN — filed 2026-11-10 (endings list) **2026-11-10 15:19 — RULED (D72 = yes, by the household's own choice; `09` §3 decision 292).** Not built. | — | Controller (D72): when the household pressed „delete backup data” for an app, its off-site copies end 30 days later, at the next clean-up after that day (the number of a restore copy, D62); when the household kept the backups, the off-site copies stay. The page shows the end date before anything is deleted — write that into `07-backup-architecture.md` before the build. Parts (2) and (3): a delete on the export page; a line on the kept-data page for the files a whole restore set aside. | CC | | **R-1401** | Backup & restore | P4 | **The controller's fixture tool rewrites unrelated files.** Found 2026-11-15: `-update-i18n-golden` writes `?v=ASSET` where 20 stored page fixtures hold `?v=test`, so a regeneration changes files that the change did not touch; the D72 build patched its 143 fixtures by hand, one line each. Cost: the next change of a shared page string does the same by hand, or commits noise. | OPEN — filed 2026-11-15 | — | make the tool and the stored fixtures agree on the asset version word, then regenerate once | CC | | **R-1385** | Backup & restore | P3 | **Two timed jobs can meet with no lock and no order (12 answers).** Found 2026-11-11 (the Clock list, class W3, `documentation/audits/clock-list-2026-11-11/TABLE.md`). MEASURED on the night of 2026-11-11: on Tester 1 and the N100 the whole-guest backup started at about 05:30 local, the minute of the off-site proof restore (CC09-5); on demo-hp one whole-guest backup started at 02:30:38, with the dump leg; on the N100 the whole-guest backup starts about 5 minutes later each day. From source: the controller's auto-update default is the minute the whole-guest gate opens (CC11-5); the second-drive copy and the abandon sweep wait only for the clock (CC02-5, CC19-5, CC21-5); the PBS verify can run beside a backup (CA13-5, CA04-5); the timers on DooPlex and ep0 are not ordered against the hub's copies (CH05-8, CH24-5, CH25-3, CH26-5, CH26-6; from documents only, not measured). No harm was seen; the durations are from small test stores. | OPEN — filed 2026-11-11 (clock list) | — | Measure one night with a large store on Tier 0 (as a task), then decide per pair: a shared flag, a fixed offset, or „harmless, written down”. | CC | @@ -355,7 +355,7 @@ stopping line that lies. | **R-1345** | Hub & operator | P4 | **An access token's scopes cannot be changed after it is made — widening or narrowing one means a new token (and a new secret).** The operator, 2026-10-29: to give CC `hosts:read` + `hosts:write` for the live proofs he had to make `CC_HOSTS` (now in `sec`) beside `cc-releases-2`. Wanted: edit a token's scopes in the session (an audit line per change), so a scope can also be taken away after a session without retiring the secret. | OPEN | — | design + build the scope edit (session only), red-first test that an unticked scope is refused at once | CC | | **R-1353** | Hub & operator | P4 | **Statements still over 1 s, named by the new slow-statement line (hub 0.178.0) in its first hour:** a background deadline/restore-test check reading days of full host-report JSON (`GetHostReportsSince`, `store.go`; 1.5–9.2 s cold, from `monitor/deadline.go` and `monitor/restoretest.go` — no page waits on it); the start-up prune of `events` and `app_log_issues` (1.1 s and 1.8 s; no index on `created_at` / `last_seen`); the customer page's newest-report read (`GetCustomer`, 1.3 s cold in the pod probe). With the 1 GiB limit most of this should come from the cache once warm. Evidence: the hub log 2026-10-30 09:22–10:05 UTC; `audits/release-2026-10-30/p2-r1346/`. | OPEN **2026-11-02 read (`audits/security-2026-11-02/part4/hub-slow-lines-2026-11-01-02.txt`; the log covers only the 31 h since DooPlex restarted on 2026-11-01 16:11 CET, the lines from 10-30 are gone with the old pod):** 35 lines, 15 statements. What repeats: `VACUUM INTO` 5× (avg 110 s, the 6-hourly snapshot, expected); `GetHostReportsSince` 9× (avg 7.9 s, max 26.6 s); `GetCustomer`'s newest report 3× (1.1 s). Once, at the cold start: the prune of `events` (10.4 s) and `app_log_issues` (21 s, again 04:30), the OS-release and host lists (2–22 s). No fix before the full week (11-06). **2026-11-10 read (the hub's start after a deploy, `audits/release-space-fixes-2026-11-10/hub/10-watch.txt`):** 11 slow lines in the first 2 minutes of the new pod, the longest 19.1 s (`GetHostReportsSince`), then the OS-report reads (3–4 s) and the two prunes (2.7 s, 4.2 s); none in the 28 minutes after. The 13:02 UTC snapshot's `VACUUM INTO` took 127.8 s. The same statements as the 11-02 read; no new one. | — | read a week of slow-statement lines; index or narrow what still repeats (the history read needs only a few fields, not the whole JSON) | CC | | **R-1375** | Hub & operator | P2 | **The outside part of three endings is done by hand or not at all — the worst: an off-site account can stay at the provider with no record in the hub.** Found 2026-11-10 (the endings list, `documentation/audits/endings-list-2026-11-10/TABLE.md` endings EH06, EH01, EA21 and the ending "a tester ends"; read in source and documents; no account was called). (1) **Unticking the off-site tier** of a household takes nothing down and leaves no reminder (`hub/internal/web/configs.go:1737-1743`). A later RESET takes the account down only when the tier is ticked (`hub/internal/web/customer_reset.go:203-245`), so the sub-account and its data stay, are paid for, and the hub holds no record that they exist. (2) **Switching the second off-site tier off** takes nothing down: storage entry, token and copies stay; the source calls the teardown 'a deliberate future op' (agent `internal/pbsdr/manager.go:274`). (3) **A tester ends**: no handler and no runbook; done by hand once (2026-09-25); no list says what to collect. **Members (answers marked N):** EH06-4, EH01-4, EA21-4, and 'a tester ends' in the table's head. Related: R-810 (a household leaves), R-32. | NARROWED — **2026-11-15: part 1 is LIVE** (hub 0.182.0). The record of an off-site account now outlives an untick. **Tests only:** the provider path (no call to the provider was made today; no household was unticked). The operator's one-time label check at the provider is still to do. Earlier: NARROWED — part 1 (D71) is built, not released. **2026-11-14 (night build):** the hub keeps the record of an off-site account after the tier is unticked; RESET and delete take the account down when a record exists; an untick alone takes nothing down (pinned by a test); the config form says that the account still exists (`05` §14.1). The runbook „a household or a tester leaves” is written (D74, `runbooks/household-leaves.md`). **For the operator, once, after the release:** at the provider's page read each sub-account's label `felhom-customer=`; for a household whose tier is unticked in the hub, tick it again and save — the account's record comes back. LEFT: part (2) has no fault (the second tier keeps its record, read in source and its test); part (3) is the runbook; a household mail at leaving stays R-810. OPEN — filed 2026-11-10 (endings list) **2026-11-10 15:19 — RULED (D71 = yes, D74 = yes; `09` §3 decisions 291, 294).** Not built. | — | Hub (D71): keep the account record after an untick; RESET and delete take the account down, ticked or not. Docs (D74): the runbook 'a household or a tester leaves', from the five code doors, in a later documents-only session. Parts (2) and (3) of this row have no ruling of their own. | CC | -| **R-1376** | Hub & operator | P3 | **Records of a thing that is gone stay in six places.** Found 2026-11-10 (the endings list, `documentation/audits/endings-list-2026-11-10/TABLE.md` endings EH00, EH02, EH21, EA00, EA11, EA27; read in source, `documentation/audits/endings-list-2026-11-10/evidence/hub-delete-statements.txt`; no hub database was read). (1) **Hub:** thirteen tables have no delete statement anywhere. Deleting a box leaves its update settings, its update reports and its kernel notices; deleting a household leaves its off-site key rows, off-site window rows and abandon requests. Most are small; the update reports of each box grow with time. (2) **Host uninstall** leaves the mount units and host mounts of household drives (said when R-179 closed; no open row carried it). (3) **A drive wiped by a signed job** keeps a record and a mount unit that name the old filesystem (agent `internal/signedjobs/wipe.go:61-110`). (4) **The token of a destroyed guest** stays valid until a new guest takes its number: the token store has no remove (agent `internal/localapi/tokenstore.go:127-210`). **Members (answers marked N):** EH00-4, EH02-4, EH21-4, EA00-4, EA11-4, EA27-4. | NARROWED — **2026-11-15: two more hub marks are not removed at a household's delete** — `offsite_snapshot_listing:` and `offsite_window_grant:` in `hub_settings` (found while building D72; the same shape as the alarm marks). To add to the delete and to the sweep. Earlier: NARROWED — **2026-11-15: part 1 is LIVE** (hub 0.182.0). The first sweep at the start deleted 26 rows (old update reports of 13 boxes deleted earlier), the same count as the preview on a copy; the ids are kept off git. A box delete by the operator at 11:29 ran with the new code. **One thing the sweep does not cover:** the hub's own alarm marks of a box deleted BEFORE the release (4 marks of one such box were read today) — a delete now removes them, the sweep of old ones does not. Small; to add to the sweep. Earlier: NARROWED — part 1 (the hub, D73) is built, not released. **2026-11-14 (night build):** deleting a box removes its update settings, update reports, kernel notices and the hub's alarm marks that name it; deleting a household removes its off-site key, window and abandon rows; the operator's action log of a deleted household goes one year after the deletion with the other audit rows (decided by CC unattended — the operator may reverse); the delete journal stays; a daily sweep removes what earlier deletes left (`05` §14.2). The privacy sentence is proposed in the report, not published. LEFT: the agent part (a destroyed guest's token), parts (2) and (3), and an age limit for a LIVE box's update reports (needs a design: the kernel lane reads old reports). OPEN — filed 2026-11-10 (endings list) **2026-11-10 15:19 — RULED (D73 = yes, with one exception; `09` §3 decision 293).** Not built. | — | Hub (D73): add the tables with no delete to the two purges and to the daily clean-up; the delete journal (`host_deletions`, `customer_resets`) stays on purpose, and the privacy text says so. Agent: remove a guest's token when the guest is destroyed. Parts (2) and (3) have no ruling of their own. | CC | +| **R-1376** | Hub & operator | P3 | **Records of a thing that is gone stay in six places.** Found 2026-11-10 (the endings list, `documentation/audits/endings-list-2026-11-10/TABLE.md` endings EH00, EH02, EH21, EA00, EA11, EA27; read in source, `documentation/audits/endings-list-2026-11-10/evidence/hub-delete-statements.txt`; no hub database was read). (1) **Hub:** thirteen tables have no delete statement anywhere. Deleting a box leaves its update settings, its update reports and its kernel notices; deleting a household leaves its off-site key rows, off-site window rows and abandon requests. Most are small; the update reports of each box grow with time. (2) **Host uninstall** leaves the mount units and host mounts of household drives (said when R-179 closed; no open row carried it). (3) **A drive wiped by a signed job** keeps a record and a mount unit that name the old filesystem (agent `internal/signedjobs/wipe.go:61-110`). (4) **The token of a destroyed guest** stays valid until a new guest takes its number: the token store has no remove (agent `internal/localapi/tokenstore.go:127-210`). **Members (answers marked N):** EH00-4, EH02-4, EH21-4, EA00-4, EA11-4, EA27-4. | NARROWED — **2026-11-15 evening — RULED: D86 = remove (decision 314).** Fix shape: one more statement in the one-year prune of a deleted household, in the same transaction — the id columns of `host_deletions` and `customer_resets` of that household hold no id after it (`05` §14.3, option A, its six rules and its test list). Earlier: NARROWED — **2026-11-15: two more hub marks are not removed at a household's delete** — `offsite_snapshot_listing:` and `offsite_window_grant:` in `hub_settings` (found while building D72; the same shape as the alarm marks). To add to the delete and to the sweep. Earlier: NARROWED — **2026-11-15: part 1 is LIVE** (hub 0.182.0). The first sweep at the start deleted 26 rows (old update reports of 13 boxes deleted earlier), the same count as the preview on a copy; the ids are kept off git. A box delete by the operator at 11:29 ran with the new code. **One thing the sweep does not cover:** the hub's own alarm marks of a box deleted BEFORE the release (4 marks of one such box were read today) — a delete now removes them, the sweep of old ones does not. Small; to add to the sweep. Earlier: NARROWED — part 1 (the hub, D73) is built, not released. **2026-11-14 (night build):** deleting a box removes its update settings, update reports, kernel notices and the hub's alarm marks that name it; deleting a household removes its off-site key, window and abandon rows; the operator's action log of a deleted household goes one year after the deletion with the other audit rows (decided by CC unattended — the operator may reverse); the delete journal stays; a daily sweep removes what earlier deletes left (`05` §14.2). The privacy sentence is proposed in the report, not published. LEFT: the agent part (a destroyed guest's token), parts (2) and (3), and an age limit for a LIVE box's update reports (needs a design: the kernel lane reads old reports). OPEN — filed 2026-11-10 (endings list) **2026-11-10 15:19 — RULED (D73 = yes, with one exception; `09` §3 decision 293).** Not built. | — | Hub (D73): add the tables with no delete to the two purges and to the daily clean-up; the delete journal (`host_deletions`, `customer_resets`) stays on purpose, and the privacy text says so. Agent: remove a guest's token when the guest is destroyed. Parts (2) and (3) have no ruling of their own. | CC | | **R-1386** | Hub & operator | P3 | **Timed jobs with no time limit and no measured duration (25 answers).** Found 2026-11-11 (the Clock list, class W4, `documentation/audits/clock-list-2026-11-11/TABLE.md`; read in source; the hub was not measured, by ruling). The hub's 60-second sweep runs its checks one after the other with no limit for each: one slow check delays all the others, the liveness check too (CH19-3, CH19-8, CH01-3, CH08-3, CH08-8, CH10-3, CH13-8, CH18-3, CH06-8, CH02-3); the 07:10 audit has 10 minutes, measured with three boxes only (CH11-3, CH11-8). On the box: the interval jobs have no limit of their own (CC11-3, CC12-3, CC13-3, CC14-3, CC15-3, CC16-3, CC20-3, CA06-3, CA10-3, CA10-8, CA13-8, CA15-3, CA19-3). Every measured duration is from a small test store. | OPEN — filed 2026-11-11 (clock list) | — | Hub: log each sweep step's duration and alarm when one sweep takes longer than its interval; then read a week of numbers and set limits. Box: the same for the controller's interval jobs. | CC | | **R-1393** | Hub & operator | P4 | **For about 8 minutes after a hub restart its database statements take 1 to 32 seconds; the System page took 12.7 s and a box's enrolment 11.4 s.** Measured 2026-11-14 at the 0.181.0 deploy (`audits/release-1-dates-2026-11-14/hub/05-watch.txt`): 24 `slow statement` lines from 09:58 to 10:06 UTC, none in the 20 minutes after. The database file is 678 MB; the slow ones read `host_reports`, `os_reports` and `events` (whole report JSON per row). One 32-second statement ran while CC copied the database out of the pod for a read (CC's own load). No report was lost that CC could see; not measured: whether a box's report timed out in that window. | OPEN — filed 2026-11-14 | — | measure a restart with no copy running; then decide: an index or a shorter keep on `host_reports`/`os_reports`, or accept | CC |