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

+4
View File
@@ -375,6 +375,10 @@ Decisions made, architectural state, what's next.
> "waiting on the operator" list. **The report names which of the three it did.** The poster is drawn
> in Claude Design and nothing here renders it, so `scripts/poster_facts_gate.py` only WARNS when the
> facts outrun the drawing — it never fails a push. Same wording in `.claude/rules/unprompted-work.md` §6.
> **A place that holds data.** A task that adds a place that holds data on a box, or changes a place's limit, its
> cleaner or its alarm, updates the "disk space" section (§14) of `architecture/16-storage-physical-identity.md` in the
> same session (D69, `09` §3 decision 288).
If the task **changed what the platform can do** (new/removed capability, a capability moved status,
or **what is open changed**), update **all four** in the SAME session:
- **`architecture/00-capability-map.md`** — add/adjust the affected *scenario* row with the correct