09 §3 decisions 172-173 (kernel lane yes, option A + C; R-32 leftovers left, P4) recorded before the work
gates / gates (push) Successful in 3m10s
gates / gates (push) Successful in 3m10s
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS
This commit is contained in:
@@ -915,6 +915,19 @@ its length, and both fixes cost something the household would notice — operato
|
||||
127. **The agent's three by-design abilities (`03` §3.1) stay for now**; revisited before the first paying customer.
|
||||
*Operator ruling 2026-10-05.* (R-861)
|
||||
|
||||
### 2026-10-07 (14:43) — operator rulings on the kernel lane and R-32 (recorded before the work)
|
||||
|
||||
172. **The kernel lane: yes — design option A (the one-shot flag on the ESP), with option C on the one-shot entry**
|
||||
(`audits/kernel-spike-2026-10-07/DESIGN-kernel-lane.md`). A box may restart at night for a kernel update. **The
|
||||
household is told by mail the day before**, with what to do if the box is not back by morning (unplug it, plug it
|
||||
back in). Each kernel set is approved by the operator after ring 0 ran it, as the Docker and Proxmox sets. **A
|
||||
frozen new kernel needing a person's power cycle is accepted** for the first customers, because the household is
|
||||
told what to do. *Operator ruling 2026-10-07 14:43.* (R-836)
|
||||
173. **R-32's old off-site leftovers (about 2.7 GB): leave them for now.** They were computed (box total minus live
|
||||
customers), never listed; deleting them needs the pool box's main login, which reaches every customer's data.
|
||||
R-32 stays open only for the leftovers, re-ranked P4, blocked on „a safe main-account path". This supersedes the
|
||||
„delete the old RESET leftovers once" half of decision 167. *Operator ruling 2026-10-07 14:43.* (R-32)
|
||||
|
||||
### 2026-10-07 (07:58) — operator rulings on the night designs (recorded before the work)
|
||||
|
||||
162. **Hub releases at night: NO.** A hub image build or hub deploy happens only in a session the operator attends.
|
||||
|
||||
Reference in New Issue
Block a user