audits: the Endings list (2026-11-10) — 67 endings, 536 answers, 22 not found in 6 classes
gates / gates (push) Successful in 2m1s
gates / gates (push) Successful in 2m1s
What every thing a customer can end leaves behind, and who is told. - documentation/audits/endings-list-2026-11-10/: README (one page), TABLE (67 endings x 8 questions, each answer with a mark and a pointer), MATRIX, the search list with controls, the helpers' raw answers, and the ageing drill on scratch guest 9202 (five rounds, put back). - Marks: A 499, D 0, K 15, N 22. 9 endings are not named in the architecture folder. - Register: six new rows, one per class (R-1373 … R-1378); 230 -> 236 open rows. Nine existing rows get a dated pointer line; none is closed, merged or re-ranked. - STATUS.md: four decisions for the operator (D71 … D74). No code change. No release. Machines: scratch guest 9202 only, put back. Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS
This commit is contained in:
1 parent
449b065fbd
commit
807175c27d
147 files changed
+32315
-13
No files matched your search
@@ -32,6 +32,10 @@ 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 |
|
||||
|---|---|---|---|---|---|---|
|
||||
| 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 |
|
||||
| D71 | R-1375 | Shall the hub keep the record of an off-site account after you untick the tier, and take the account down on RESET and delete? | **Yes** (an account can not be forgotten; one hub change) | a hand step in a runbook: it depends on memory | an unticked household that is reset or deleted leaves a paid account with no record | R-1375 |
|
||||
| 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 | — |
|
||||
|
||||
Reference in new issue
Block a user