the size rule: a small finding is fixed in the session, not filed; reports state four register numbers (burn-down Part D)

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS

documentation/PROMPT-TEMPLATE.md

@@ -257,7 +257,9 @@ Then:  [exact refusal — HTTP status, error, and the proven non-effect, e.g. "m
    typecheck; do not accumulate compile errors.
 2. **Minimal changes:** build only what's listed. No "while I'm here" refactors. Note anything worth
    fixing under "Observations" (§15) — don't act on it, but **do file it**: §15.9's marker rule means
-   "not acted on" never means "not recorded".
+   "not acted on" never means "not recorded". **Exception — the size rule (2026-10-05):** a finding that is cosmetic
+   or small (about 30 minutes, in a repo this session may change) is FIXED in the session with a test and listed under
+   „fixed without a row" — not filed (`OPEN-ITEMS.md` „How a row is filed").
 3. **No silent failures:** never swallow a parse/exec error — log it. Check a subprocess's **own** exit
    code; never pipe in a way that hides a 127. (The silent `.felhom.yml` quoting bug + the spike's
    exit-swallow lesson.)
@@ -423,8 +425,9 @@ inside an entry about something else, and a finding rediscovered because nobody
    shape `[DESIGN]` in the architecture document and point it at the log entry** (§4's map).
    **Losing a reason is how a deliberate design becomes a bug in someone's eyes** — that cost four
    mis-filed defect reports in August 2026 (R-370, R-376).
-3. **State the register's size in the report, before and after.** A number every session is what makes
-   growth visible; prose about tidiness is not a mechanism.
+3. **State the register's size in the report as FOUR numbers: rows before, rows after, rows opened, rows closed**
+   (2026-10-05). A number every session is what makes growth visible; prose about tidiness is not a mechanism.
+   Before/after alone hid that sessions closed some and opened as many.
 
 ---
 

documentation/audits/hub-db-offsite-2026-10-05/partD/alarm-drill.txt

@@ -1,3 +1,4 @@
+## operator confirmation (inbox screenshot): [FIRING] HubDBBackupStale 16:22 CEST; [RESOLVED] HubDBBackupStale 16:27 CEST
 ## alarm drill start 2026-10-05T13:51:46Z: success file moved aside (absent case)
 backup_freshness.prom
 fan_metrics.prom

documentation/backlog/OPEN-ITEMS.md

@@ -13,6 +13,17 @@ a non-overwritten `REPORT-<topic>.md` sibling instead (`CLAUDE.md:82-87`), of wh
 belongs inside backticks), whose **Category** is not one of the eleven below, or whose **Sev** is not
 `P1`–`P4`. **A new row goes into its category's section**, in severity order.
 
+**Fix small, do not file (the size rule — operator brief 2026-10-05, the burn-down).** The register grew because every
+session closed a few rows and filed a few small new ones. So: **a finding that is cosmetic or small — fixable in the
+session in about 30 minutes, in a repo the session may change — is FIXED in that session, with a test where it changes
+behaviour, and NOT filed.** It is recorded in that repo's `CHANGELOG.md` and in the session report under „fixed without
+a row". **Only a finding that needs a decision, a design, a larger build, or a change the session may not make** (a
+protected machine, a repo out of scope, a release budget already spent) **becomes a row.** This narrows — it does not
+repeal — „an enumerated gap becomes a row": a small gap leaves the session fixed, which is a record too.
+
+**Every session report states four numbers:** rows before, rows after, rows opened, rows closed — counted the way
+`register_shape_gate.py` counts (`| **R-n** |` lines in this file).
+
 **Sev — one scale for this file and `ROADMAP.md`:**
 - **P1 — now.** A household can lose or leak data, a box can stop or be taken over, or a promise we make is
   false — today. A P1 row says in one sentence what the harm is.