Tyrell Build 20 R10 passed its short physical-footprint gate on this designated canary while Time Machine remained actively copying; the canary stays isolated for the long gates.

Scope and verification

• Host: rdmbair15m5 only; no additional fleet host changed.
• Exact Build 20 daemon PID/start/path and exact daemon/app hashes remained unchanged.
• Guard and caffeinate parentage, both sleep assertions, AC/open state, both status planes, all permission samples, additive database integrity, libproc descriptor evidence, and two TCP sockets remained healthy.
• The guard receipt and independent recomputation matched across 31 post-warmup samples over 1,800.274337 seconds.
• Physical endpoint was 58.594986 MiB; delta -0.035412 MiB/min; regression slope -0.009733 MiB/min; descriptor range 25–27; maximum gap 60.046557 seconds; zero endpoint failures or 503 responses.
• R10 exceeded R9's prior lsof failure interval during the still-active backup, validating guard v1.5's mount-independent libproc replacement and resolving ISSUE-20260914-09.

Evidence and recovery

• Canonical receipt: /Users/richh/dev/_handoff/tyrell-build20-memory-20260912/canary-r10-short-gate-20260914-1205/README.md.
• Receipt SHA-256: e73c2ce894f95f58495dd6e5dbdb00f9e9bbd0facc3640ec8c010438cc6002ca.
• Exact Build 15 daemon and Build 17 app rollback payload remains complete.
• Never restore the pinned database over the additive live database.
• R10 is not release-accepted; six-hour, fixed 24-hour, repeat-inventory, CPU, app, and reboot gates remain pending, with no fleet expansion authorized.