diff --git a/FABRIC.md b/FABRIC.md
index e2d9320..d696eab 100644
--- a/FABRIC.md
+++ b/FABRIC.md
@@ -2102,10 +2102,26 @@ document and committing that amendment as its own item.*
   > regression guard — but it is not evidence for 2.1.
 
 - [ ] **2.2 — Bound the VM registry.**
-  The registry is a `kmalloc`-backed unbounded list, which makes fleet K an identity that
-  cannot fail (§20.2). Give it the hard bound decided in 1.5.
-  *Done when:* the population is bounded and `VM-CONSERVED?` can, in principle, fail.
-  *Refs:* §2, §20.2.
+  The registry is a `kmalloc`-backed unbounded list (`capsule_vm_physics.c:71-72`). Give it
+  the hard bound decided in 1.5.
+  *Done when:* the population is bounded, birth at the bound behaves as 1.5 specifies, and
+  the three-architecture boot is unaffected.
+  *Refs:* §2, §13, §19.2, §20.2.
+
+  > **Justification corrected.** This item previously read that the registry "makes fleet K
+  > an identity that cannot fail" and accepted on `VM-CONSERVED?` becoming able to fail.
+  > Both were wrong, and the reason is now in §20.2: heat is **transferred**, not
+  > renormalised, so conservation is already a real invariant and already falsifiable —
+  > by the dropped-remainder path at `:240-244` and by integer truncation at `:304-305`.
+  > Bounding the population changes neither.
+  >
+  > The bound is still needed, on the two grounds §2 now states: **finite state** for §13's
+  > induction and model checking, and **density requires a capacity to be dense within**
+  > (§19.2), without which §19.3's admission rule has nothing to compare against. Those are
+  > the honest justifications and this item now rests on them.
+  >
+  > Making conservation *more* falsifiable is a different and larger piece of work — fixing
+  > the truncation leak — and is recorded in §25.7 rather than folded in here.
 
 ---