- POST /offsite/window-open answered 200 on a body it could not parse and
decided the window on „count 0”; now 400 (the empty body of the oldest boxes
is still „no count”).
- Every answer carries accepts_ended, granted or not: a box sends its end
records only to a hub that said so, so a new box never sends a large request
to an older hub that reads 4 KiB.
Carries the red-proof of both halves (the controller's is the next commit
there). Tests seen red; 3 hub mutations seen red, 1 after a redo.
Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS
The key was the display string cut after ten names, so two different app sets
with the same first ten names shared one wait and one operator mail.
largeSetKey is a SHA-256 of the full sorted set; the display string is only
shown. Test seen red; 2 mutations seen red (redproof-review-s2.txt).
Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS
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
- 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
host_disk_warning and host_disk_critical join the operator-only register, so a
household that already has the type saved gets no mail. The type leaves the
claim seed list. storage_fill_* is split by storage kind: a drive the household
can free (usb, local-dir, nfs, cifs) still reaches the household; the thin pool,
a PBS store, an unknown kind and a missing kind go to the operator only.
Tests: TestD68_HostDiskIsOperatorOnly_EvenWhenTheHouseholdSavedIt,
TestD68_StorageFillReachesAHouseholdOnlyForADriveItCanFree,
TestD68_RegisterAndGate, TestD68_SeedHoldsNoOperatorOnlyType. Red seen three
times (register lines out; gate reading the register only; type back in the seed).
No hub build, no deploy. Also: dated lines on R-1368 and R-1371 for the agent
(776025c8) and controller (844f19f1) commits, and the filesystem-identity
measurement the controller commit cites.
Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS
The host layer's reboot-needed run is cut at the host's last boot (crash guard
last_boot_at, one minute skew margin): the kernel step's reboot is reported on the
kernel layer, so the flag outlived it until the next night. Feeds the System page
and the 14-day alarm. Test TestRebootNeeded_ClearedByAHostBootAfterTheClaim, red on
two mutants.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS
Traefik's memory on 9202: v3.7.16 18.7 -> 79.0 MiB after 920 connections, not released; v3.7.17 flat near 25 MiB for 25,116 connections.
Golden 0.350.0 waits for its fresh-install proof and the operator's vouch. Not 0.349.0.
Tests red before the fix: TestR1255_TheCarryTakesTheNewestPackageThatHasAHash,
TestR1255_APurgeNeverDeletesAPackageAReusedPathStillNeeds, TestR1255_TwoSetAsidesOnOneDayGetTwoNames.
Commit only; rides the next hub release.
The Backup card's off-site part shows the window state (weekly switch, the normal cap, a waiting grant, the last
window) and a form: optional limit -> a confirm step that names the customer and the limit -> the SAME route and
rule as the script address (POST /offsite/window-grant/<customer>, wr(grpOffsite), the page's CSRF). A waiting grant
can be cancelled. A raised limit above the store's measured snapshot count is refused (the 500 ceiling stays). Every
grant and cancel: a log line and an operator-only info event offsite_window_grant (who, customer, limit).
Tests TestR1299_* (five), red-proved by five mutations.