docs: the disk-space section (16 §14), the runbook "a disk is full", the run's report
gates / gates (push) Successful in 2m7s

C4: documentation/runbooks/disk-full.md (R-1369). Five disks; each hand step
is PROVEN with its date and evidence, or NOT PROVEN.
C5: 16-storage-physical-identity.md §14 (D69, decision 288). 45 places, each
with limit, cleaner and alarm; the rulings behind "no limit"; the host disk
budget; the open design points. PROMPT-TEMPLATE §N.5 gets the keep-it-true line.
Close-out: STATUS (D75 new), CONTEXT, dated lines on R-1369, R-1370, R-1371,
three small stale-document fixes, the report of the run.

Documents only. No release, no build, no deploy.

Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS
This commit is contained in:
admin committed 2026-11-10 14:47:25 +01:00
1 parent b14eb0fad4
commit 025a1bcd40
11 files changed
+504 -8

No files matched your search

+2 -1
View File
@@ -2,7 +2,7 @@
**Ready for Tester 2? Yes — tell the friend go (`documentation/pilot/TESTER2-handover.md`).**
**Updated 2026-11-10.** CC listed every place that holds data on a box — 45 places, read-only on the three test boxes — and asked eight questions of each: 47 answers were „nobody asked”, now in five new rows (R-1368…R-1372). The worst one: nothing removes old kernels from the host; a ring-0 box holds 8 of them (8 GB) and gets about one more each week. You ruled on its four questions at 12:22 (D67–D70: yes, operator only, yes, yes — `09` §3 decisions 286–290); the list is in `documentation/audits/space-list-2026-11-10/README.md`.
**Updated 2026-11-10 (afternoon).** CC listed every way a thing ends on a box or in the hub (74 endings, eight questions each): 22 answers were „nobody asked”, now in six new rows (R-1373…R-1378) and four questions for you (D71–D74). CC removed six old kernels from the HP box by hand with the keep rule you ruled (8 → 2, 6.4 GB back, one restart, all apps healthy after 5 minutes); nothing is built for it yet. Three first space fixes wait in source for a release, the disk-space design (`documentation/architecture/16-storage-physical-identity.md` §14) and the runbook `documentation/runbooks/disk-full.md` (R-1369) are written, and D75 is one more question for you; the report is `REPORT-endings-kernels-fixes-2026-11-10.md`.
## What works
- **The Plex attack did not reach Felhom's secrets** (R-1241).
@@ -32,6 +32,7 @@ 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 |
|---|---|---|---|---|---|---|
| D75 | R-1370 | What is the smallest system disk Felhom accepts? Measured: the host's own files need about 14 GB when the whole-box copies go to a backup drive, and 28–54 GB when they stay on the system disk. | **128 GB only with a backup drive; 200 GB without one** (a 128 GB disk gives the host 41 GB: enough for 14, not for three local copies of a box with many apps) | 128 GB always, as today: a box with many apps and no backup drive stops its local whole-box copies | the installer accepts any disk; a small box can lose its local copies | R-1370 |
| D74 | R-1375 | Shall CC write the runbook „a household or a tester leaves” now? | **Yes** (five code doors exist; documents only, one evening) | wait for the first leaver: the first run is by memory | no runbook; a leaver is handled by hand | — |
| D73 | R-1376 | When you delete a household or a box in the hub, shall the hub delete every record of it? Today 13 tables keep rows. | **Yes** (add the tables to the purge; one hub change) | keep them as history: say so in the privacy text | rows of deleted households and boxes stay in the hub for ever | R-1376 |
| D72 | R-1374 | Shall the off-site snapshots of a removed app end after a fixed time, with a notice first? Today they stay for ever. | **Yes — give the number of days** (paid space stops growing) | keep for ever: the household can restore a removed app at any time; paid space only grows | they stay for ever | R-1374 |