Tyrell Build 25 app + Build 24 daemon R3 short-gate pass

The distinct rdmbair15m5 R3 protected canary passed its independently recomputed 30-minute post-warm-up physical-footprint gate while retaining the exact candidate identity and fail-closed protection. This is a short-gate milestone only: the same-process six-hour, fixed 24-hour, repeat-inventory, CPU, fresh-app, controlled-reboot, integration, fleet, and release gates remain open.

Scope

• Coordinator host: rdmpw3275m
• Canary host: rdmbair15m5
• Canonical evidence and registry host: rdmsm4x
• Ticket: ISSUE-20260914-15 remains in-progress
• Active canary: Build 25 app executable SHA-256 d7bb71eba28f812b53f787e1d2020add0d6b99aa258b396a1a0c7f2adeab8de7 plus Build 24 daemon SHA-256 220f6eac4298ca32faf866d0edc6308924482d2980730368faf12bb355fce949
• Runtime identity: daemon PID 20671, process start Wed Sep 16 09:40:52 2026, guard PID 20320, caffeinate PID 20433

Gate result

• Guard receipt SHA-256: dad25077e51880c60657d0b49e631f308b0ed433a099659e969b6599c9d812b7
• Independent verifier exit: 0
• Saved receipt matched: true
• Gate samples: 31 over 1800.228558063507 seconds
• Physical footprint at boundary: 24.59491729736328 MiB
• End-to-end physical delta: 0.022392989945323315 MiB/min
• Least-squares physical slope: 0.0262817013938616 MiB/min, below the 0.2 MiB/min bound
• Descriptor range: 26 to 28
• TCP counts: [2]
• Maximum full-series sample gap: 60.031713008880615 seconds
• RSS remained diagnostic only: end 143.921875 MiB, delta 0.04791058313883128 MiB/min

At the final post-record observation, the guard verifier still passed with AC power, the clamshell open, both sleep assertions active, the reboot interlock armed, and a fresh heartbeat. Sample 46 at elapsed 2701.208039045334 seconds retained physical footprint 25,887,944 bytes, 26 descriptors, two TCP descriptors, valid JSON status planes, and no unchanged-repeat condition.

Files and records changed

• Created bounded local evidence at /Users/richh/Documents/ChatGPT/rdmpw3275m/handoff/tyrell-build25-r3-short-gate-evidence-20260916-1021.
• Created a frozen verifier copy at /Users/richh/.tyrell/verification/tyrell-build25-r3-short-gate-evidence-20260916-1021 on rdmbair15m5.
• Promoted the evidence to /Users/richh/dev/_handoff/tyrell-build25-r3-short-gate-evidence-20260916-1021 on rdmsm4x.
• Added the gate milestone to /Users/richh/dev/issues/open/ISSUE-20260914-15-tyrell-mergefleetevents-colon-concatenat.md through the ticket CLI without resolving the issue.
• Updated /Users/richh/.agent-coordination/checkins/codex-rdmpw3275m-tyrell-build25-canary-20260915.json to record the R3 short gate and next six-hour gate.
• Updated canonical /Users/richh/dev/PROJECTS.md by compare-and-swap. Before SHA-256: 5cdded38f04d4ea54bab756df7c630af57ab457166253930376f90e512462167. After SHA-256: a5ac7512799bcd7f0d57489807520d6965fce00ff992ca4e24c30dcc74b3c290. Recovery copies are in /Users/richh/dev/_handoff/tyrell-build25-r3-short-gate-registry-update-20260916-1027.
• Updated /Users/richh/.codex/automations/finish-tyrell-build-16/automation.toml so later heartbeats treat the short gate as accepted and wait for the same-process six-hour receipt. Current SHA-256: 3d38c7d0c2095c826b68273f5e79051bbba42e8f7df33c08c9b67fe20da5cf69.
• Created this changelog at /Users/richh/dev/LLM/Claude/changelogs/rdmpw3275m-changelog-20260916-1029-tyrell-build25-r3-short-gate-pass.md and promoted an identical copy to the canonical rdmsm4x path.

The initial broad evidence transfer also copied the candidate and rollback app bundles. Those redundant local copies were moved, not destroyed, to /Users/richh/.Trash/tyrell-evidence-oversize-20260916-1021; all evidence needed to reproduce the short gate remains in the bounded packet.

Verification and commands

• Re-pinned rdmbair15m5 to ED25519 fingerprint SHA256:HDXZpExLTrlJconcMTpEfnH+t9xRbzygqdpKMmyF5KU before remote evidence writes.
• Re-pinned rdmsm4x to ED25519 fingerprint SHA256:3D5x0tqX2D3EBA8UBJFr/JjZxNIpVjC3TLltySf0Erk before canonical writes and confirmed it differs from the local host fingerprint.
• Ran verify_guard_power_protected.zsh against the live R3 stage.
• Ran verify_canary_gate.py <stage> short first against the live canary stage and again against the frozen canary-host copy with PYTHONDONTWRITEBYTECODE=1; both returned exit 0 and the same saved-receipt result.
• Validated every listed evidence file with shasum -a 256 -c MANIFEST.sha256 locally, on the frozen canary copy, and on the canonical copy.
• Evidence MANIFEST.sha256 SHA-256: 3a71c80fa2ecb3879907e6fd49fdd68177a736dc6b3e394460a33ac149941ecb.
• Deterministic recursive evidence SHA-256: a7586bfb9a8bb8a0ab376689ab40fd22f700ee3aad87533069e963132200860d; 85 files, five nested directories, zero symlinks, 452,208 bytes.
• Verified all copied JSON and the independent verifier log parse, and confirmed local, canary-frozen, and canonical recursive summaries match.
• The canonical registry write was accepted only after the live before-hash exactly matched the captured before-copy; owner/group/mode after the atomic replacement are richh:staff 0644.

Recovery and undo

• Do not restart or alter the live R3 process to undo documentation. Its clock and same-process identity are acceptance evidence.
• To undo only the registry wording, restore PROJECTS.before.md from the registry packet only if live /Users/richh/dev/PROJECTS.md still has the exact after SHA-256 above. If it has changed, merge intentionally instead of overwriting another writer.
• The evidence packet is additive and should remain immutable. The redundant app-bundle copies can be recovered from the Trash path above if needed.
• If the guard fails or rolls back, verify exact Build 15 daemon SHA-256 dbc440bd54b85a54dd6c4150b23b3e508bff7d8d8080687d81b9ba7ac2cbbcf0, exact Build 17 app SHA-256 8693ebce3d474fed049597d11e3579bf1cd32f7a78acfd9544c78d77592da05e, both APIs, recovery-agent removal, and interlock state before making any acceptance claim.

Outstanding actions

• Keep rdmbair15m5 on AC power with its lid open.
• Preserve daemon PID 20671, guard PID 20320, and the current stage without restart.
• Wait for the policy-generated same-process six-hour receipt; independently recompute it before acceptance.
• Do not expand the fleet, integrate to the release line, tag, or release from this short-gate pass.
• Do not resume the already completed local AGY parent; its canonical RTTy work remains verified at commit c723b4f2b74f131272c832e134354b6e0a184a0e.