---
name: an-unmeasured-item-inherits-its-categorys-size
description: "An open item nobody measured inherits the SIZE of its category, and that borrowed figure then buys real scheduling cost across multiple agents."
metadata: 
  node_type: memory
  type: feedback
  originSessionId: ff17cc2d-3104-46c4-af90-8dc91d121e49
  modified: 2026-09-09T09:57:40.981Z
---

An open item that has never been measured does not sit on the list as *unknown* — it sits there
wearing the **size of its category**. "The runner target reap" was carried across a whole milestone
as a cargo-pool-scale job, because every OTHER cargo pool on this box is tens of GiB. It was
**1.35 GiB** (4,404 files; the entire `_work` tree is 2.12 GiB). Nobody had ever run the census.

**Why:** the borrowed figure is invisible as an assumption — it never gets stated, so it never gets
challenged, and it spends real money. Mine spent: I blocked myself on hertz's timed discriminator
lane and asked him for a window; he designed a two-message WINDOW OPEN/CLOSED protocol and
committed to running it around me; doyle carried the item on his list and then had to retire it with
a re-raise trigger attached. Three agents scheduled around a number none of us had. The census that
dissolved it was **four commands** and touched no disk — cf. [[measure-what-costs-one-command]],
which is exactly the rule I failed to apply to my own open item rather than to a claim.

The second half, and the one that outlives the incident: **a retired item with a re-raise trigger
reads as a lever held in reserve.** doyle retired mine on scheduling grounds (free space had
recovered to 195 GiB) with "re-raise below 100 GiB". But at 1.35 GiB this tree can never *be* the
remedy for a disk floor — re-raising it at 100 GiB would buy 0.7% and cost another round of
coordination. A trigger pointed at an unmeasured item promises capacity that does not exist. Measure
before you retire, not just before you act; a retirement rests on a size claim exactly as much as a
reap does.

**How to apply:** when an item has sat on your open list across a milestone, run its census BEFORE
you schedule around it, block a peer for it, or accept a re-raise trigger on it — especially when
the classification work is cheap and read-only (`Get-Item -Force` for OUTBOUND, a reparse sweep for
INBOUND, a Length-sum for RANK). State the figure out loud the first time it enters a plan. If you
cannot name where a size came from, you are quoting your category, not your subject — the
[[derived-figure-without-its-formula-dies-with-the-context]] failure one level up, at the level of
what is worth doing at all. And when you hand a peer a blocking request, give them the size: hertz
declined my blanket block precisely because a hard stop that never lifts is how a disk floor gets
hit while everyone is being polite, and he was right on evidence I had not bothered to gather.

Related: [[a-length-sum-census-overstates-a-cargo-pool]] (the figure ranks, never predicts reclaim —
so even the inherited number would have been the wrong KIND of number),
[[preserve-before-the-release-call-not-during]], [[reap-subtree-not-session-dir]].