Tyrell Build 20 R5 passed its independently reproduced 40-minute physical-footprint gate on the designated canary; the exact guarded soak continues and no fleet expansion is authorised.

Tyrell Build 20 R5 short-gate milestone

Date: 2026-09-13 16:47-16:52 EDT
Host: rdmbair15m5
State: SHORT_GATE_PASSED_LONG_WINDOWS_PENDING

Scope and files produced

The running R5 guard produced these new gate artifacts under /Users/richh/.tyrell/build20-canary-r5-20260913-96a5fc0/:

• short-gate.json
• short-gate-footprint.txt
• short-gate-vmmap.txt

No executable, app, launchd configuration, database, user data, or fleet host was changed by the independent verification pass. The existing Build 20 app/daemon and exact Build 15/17 rollback were left running/retained as designed.

Commands and verification

• Loaded exact staged memory_gate.py and independently called validate_window over the receipt's 31-row post-warmup prefix.
• Re-verified process identity and start, resolved daemon path and hash, app hash and CandidateCDHashFull, launchd state, guard/caffeinate parentage, power assertions, AC/open-clamshell envelope, both API planes, live SQLite integrity, rollback hashes, sample gaps, permissions, descriptors, and sockets.
• Copied an immutable 43-sample snapshot plus gate artifacts to the canonical evidence directory.

Independent result exactly matched the guard receipt:

• 31 samples over 1800.3316264152527 seconds.
• Physical endpoint 58.67308807373047 MiB versus the 300 MiB ceiling.
• Endpoint growth +0.006248085932580202 MiB/min.
• Regression slope +0.006286512401231427 MiB/min versus the +0.20 limit.
• Same daemon PID 24460, process start, and hash-addressed path throughout.
• Maximum gap 60.03900599479675 seconds.
• lsof_rows 40 to 40; TCP descriptors 2.
• Zero invalid status probes, zero invalid permission probes, and zero permission 503 responses.
• Every gate-window sample recorded exact host rdmbair15m5, AC power, and open clamshell.

At the post-gate read, launchd was still running with runs 1 and never exited; both status planes were HTTP 200 valid JSON; database PRAGMA quick_check was ok with exactly one additive files.last_seen_at column; guard PID 24314 and assertion PID 24335 remained correctly paired.

Evidence

• Canonical directory: /Users/richh/dev/_handoff/tyrell-build20-memory-20260912/canary-r5-short-gate-20260913-1647/
• Canonical README SHA-256: 91824c81186aebdc63a262fa227ff4b4184ff3750615441e7221e0366a9fe477
• Gate receipt SHA-256: ed585dc6d43224cfd042b241d7c4582392f32bd0c60a4f69121bb4873f371203
• Validator SHA-256: 4e8f5bb7bf7fba1cd3649bb2746e2bb628af34290b976a28bb53faf1c3482076
• Sample snapshot SHA-256: 2dd48d796243d409dd0e9d52a8d1841980bbb508e485ecb3fb272fd4df0f7333

Rollback and outstanding work

• Build 17 app rollback SHA-256 remains 8693ebce3d474fed049597d11e3579bf1cd32f7a78acfd9544c78d77592da05e.
• Build 15 daemon rollback SHA-256 remains dbc440bd54b85a54dd6c4150b23b3e508bff7d8d8080687d81b9ba7ac2cbbcf0.
• Database backup SHA-256 remains db29432be4fc962a18436f15f29d1677b10bc7c541d7f78eab6c00f7ecce3c8f; never restore it over the healthy live additive database.
• Undo is not applicable to a read-only verification receipt. If the continuing soak violates an invariant, allow the exact guard to perform its bounded rollback and independently verify the retained identities and live database afterward.
• Six-hour-after-warmup gate is due 2026-09-13 22:16:58 EDT.
• Fixed 24-hour gate is due 2026-09-14 16:06:58 EDT.
• A second unchanged complete inventory, CPU review, fresh app canary, controlled reboot proof, fleet decision, and release acceptance remain pending.