The wait of a large removed-app request was timed from a search of the
windows' refusal text, which also held names a box had claimed. A box could
plant the marker in a claimed name a week ahead and skip the wait and the mail.
- offsite_large_requests (household, key of the app set, first_seen): written
only by the hub; at most 50 rows per household; it goes with the household.
No text is searched any more.
- A claimed name that has not the shape of an app name is written nowhere: the
ledger, the answer and the operator's message carry a fixed placeholder.
Tests seen red; 6 mutations seen red (redproof-review-s1.txt).
Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS
offsite_end_scheduled bypasses the household's switches and went through the
ordinary customer leg: subject and body were the box's own sentence, and 50
invented subjects gave 50 mails.
- processReceipt: the details must name a checked app (app-name shape, not
reserved) and two parsed dates; the mail is rendered only from the hub's
bundle with that app and the parsed end date — never the box's message.
- The cooldown key is the checked app + the parsed time of the press.
- At most 5 receipts per household in 24 hours, counted in the hub's sent log;
drops are said once a day; old receipt keys leave the cooldown map.
- Pinned: a blocked household and a household with no address get none.
Tests seen red before the fix; 12 mutations seen red, 3 after a redo
(documentation/audits/build-release-4-2026-11-15/A/redproof-review-4.txt).
Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS
The hub's 30-day check rests on the box's own reports: a box could name an app
that never existed, or stop listing a living one, wait 30 days, and get every
snapshot agreed beside the cap, with no operator signal.
- One window agrees to at most the size of its own cap, from the hub's OWN
count of the store; the oldest files first; the rest waits for the next
window. A narrowing of D84, decided by CC unattended — the operator may
reverse it (07 §8.2f holds the question, both options and their cost).
- offsite_end_claim_unseen (warning, mailed, operator-only): a box first names
an app the hub never saw installed — once per household and app, at most 8
per household, 30 days before anything can be agreed.
- offsite_ended_large_agreement (warning, mailed, operator-only): a request
for more than half of the store waits one week; that window agrees to none.
- 07 §8.2f: the limit rewritten (no honest ended app is needed, only 30 days),
what bounds it, what is still open. 08 §6.5: the two events.
Also carries the red-proof outputs of the controller's review fixes 2 and 3
(felhom-controller 3928c3d and the next commit).
Tests seen red on bb226f23; 15 mutations seen red (redproof-review-1.txt).
Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS
Upstream's logo at v0.18.0 and three screenshots of Securo 0.18.0 in Hungarian, taken on bench 9401 with
made-up example data. Not linked anywhere until the app is published; not on the public site until the
next Cloudflare publish run.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012qRErfCoiTkvDK9N5XHbzb
- 07 §8.2f: [FACT — built, not released]; D84 ruled (decision 309); the five
parts as built, the allowance, the audit, the mail; every edge case with the
test that pins it; what differs from the design; the limit (the hub cannot
read a snapshot's tags); every household text as built, Hungarian and
English, with the mail; what a box must show before a release. A household
with no notification address gets the page only.
- 08 §6.5 and §8.1: the receipt offsite_end_scheduled and the two operator
records.
- 05: the app record's table in the delete rules; the window API's new fields.
- The controller's red-proof outputs (56 mutations).
- hub tests: the English fixture sentence uses the box's quote marks.
Nothing is released and no box has run it.
Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS
A box could send 300 new invented app names in every report and the
household's presence rows grew with no end.
- At most 400 names per household. A new name above that takes the place of
the oldest ABSENT name the same report does not claim; when there is none it
is not stored. Said once in the hub's log, not per report.
- A name is stored only when it is shaped like an app name (64 characters,
letters, digits, . _ -) and is not reserved (_shares, the marker, the box's
infrastructure stacks) — from the app list and from an end record alike.
The same check decides what a window may agree to.
- No age limit on a row, on purpose: an aged-out row would start a real ended
app's 30 days again. Making room never makes an app eligible earlier.
Tests TestD72_AppRecord_* (a box that sends new names in 40 reports);
10 mutations seen red, 2 after a redo.
Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS
Built, not deployed. `07-backup-architecture.md` §8.2f parts 3-4 and decision 309.
- store: the hub's own record of which apps a box runs, by the hub's clock
(offsite_app_presence, fed by every controller report); it goes with the household.
- offsitekeys: window-open takes the box's due end records and answers
ended_allowed / ended_refused. An app is agreed only after 30 days of absence
in the hub's record; an id only when the hub's own listing holds it, uploaded
before that absence. The cap (max_remove) is unchanged; the close keeps only
agreed ids from removed_for_ended_apps and allows them beside the cap.
- The 07:10 audit explains the ended apps' vanished files by name and still
raises for every other vanished file.
- notify: offsite_end_scheduled is a household receipt — one mail per press to
the household's own address, whatever its switches; the operator is not mailed.
- Two operator-only hub records: offsite_ended_app_removed (info),
offsite_ended_app_refused (warning).
Tests TestD72_*, TestD84_*; 44 mutations seen red, 5 after a redo
(documentation/audits/build-release-4-2026-11-15/A/redproof-hub-*.txt).
Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS
A hub daily check skipped while the hub was down; an operator mail that was never sent; a signed job a box did not
take; a signed job a box refused, and the guest-power watchdog's give-up (both from the agent). Operator-only.
No new table. Not deployed.
Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS
The host report's new sent_at (the box clock at the moment of sending) is compared with the hub's clock at arrival.
Both directions; told once; clears within 30 s. A report that waited on the box raises nothing (reported_at is not
read). A second box off in the same direction points at the hub's own clock. Operator-only. Not deployed.
Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS
- R-528: NOT closed. demo-felhom's night oom_check failed once (2026-11-11 04:40 UTC, Docker 29.9.3,
containerd 2.4.2-3); 56 others passed; all four app_oom events since 10-12 explained. Due date 2026-11-28.
This clears the due-checks gate that kept nightly CI red (runs 2628, 2630, 2632).
- R-1391: Go 1.27.3 (hub, controller, agent) has GO-2026-6859; fixed in 1.27.4.
- R-1392: the hub's "root files behind" compares the whole bundle sha, which moves with every agent release
even when configs/ did not change; the os_config_bundle_behind alarm is due ~11-17 on all three boxes.
- STATUS: D81 + the 11-14 do line; old Updated paragraph moved to STATUS-HISTORY. REPORT overwritten.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS
The helper answered any server git asked about. It now reads protocol and host and answers one server.
Test: scripts/test_git_credential_sec.py (7 cases; red-proofed, 4 fail against the old helper).
Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS
- Golden 0.352.0: bake, publish, one fresh install, the operator's vouch (R-468).
- No clone holds a login in its address; the credential helper script is in the repository (R-925, R-1390).
- N100 clock: a stale cached AppArmor profile stops chrony (R-1301, new R-1388). Read only.
- Certificate pin spike on demo-hp (R-1380): the break, the proven hand repair (runbook), the CA-file test,
03-host-agent.md 12a, decision D80.
- Rulings of 13:17 written down (09 decisions 297-302). Register 245 -> 248 (R-1388, R-1389, R-1390).
- Docs, evidence and one helper script. No release, no floor change, no hub deploy.
Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS
Read-only review of every job on a timer and of everything that ends on a date,
with measurements from the three test boxes. Nothing ends in the next 14 days.
Register 236 -> 245 (R-1379..R-1387), pointer lines on twelve rows, D76-D79 in
STATUS.md. Part C: felhom-agent's clone address holds no token now; the other
clones wait for the operator's yes. R-1035's 4-week check moved to 2026-11-18
(operator read needed).
Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS
The close-out of the attended release run of 2026-11-10 (afternoon).
- Evidence: documentation/audits/release-space-fixes-2026-11-10/ (agent, controller, hub) and the hub row after the
fallback-kernel test.
- Rows: dated lines on R-1368, R-1371, R-1301, R-1353. 236 open before and after; opened 0, closed 0.
- Capability map: dated notes under C13 and G5; no status changed.
- disk-full runbook and 16 §14: the self-update folder is PROVEN as a product path on three test boxes.
- STATUS: new "Updated" paragraph; the old one moved to STATUS-HISTORY.
- REPORT-release-space-fixes-2026-11-10.md: wrong claims first, one deviation (the hub deploy ran before CI for the
manifest-bump commit was read), what stays not proven.
Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS