rdmpw3275m changelog — Tyrell Build 25 R2 short-gate pass

The protected rdmbair15m5 Tyrell Build 25 app plus Build 24 daemon R2 canary passed its first post-warm-up physical-footprint gate; the result is now frozen, independently reproduced, promoted to the canonical development estate, and recorded without expanding rollout or claiming release acceptance.

Scope

• Coordinator host: rdmpw3275m
• Canonical archive host: rdmsm4x
• Protected canary host: rdmbair15m5
• Ticket: ISSUE-20260914-15
• Coordinator identity: codex@rdmpw3275m/01a078a7
• Canary stage: /Users/richh/.tyrell/build25-canary-r2-20260915-4818529
• Milestone time: 2026-09-15 23:10–23:21 EDT

What changed

1. Froze the gate inputs and receipts locally at:
   • /Users/richh/Documents/ChatGPT/rdmpw3275m/handoff/tyrell-build25-r2-short-gate-evidence-20260915-2308
2. Promoted the byte-equivalent evidence packet to:
   • /Users/richh/dev/_handoff/tyrell-build25-r2-short-gate-evidence-20260915-2308 on rdmsm4x
3. Appended the accepted short-gate state to canonical /Users/richh/dev/PROJECTS.md after an exact before-hash guard.
4. Appended a rerunnable, scope-limited receipt to ISSUE-20260914-15 and extended the coordinator lease through 2026-09-16 23:18:21 EDT.
5. Updated and synchronized /Users/richh/.agent-coordination/checkins/codex-rdmpw3275m-tyrell-build25-canary-20260915.json to short-gate-passed-six-hour-soak-active.
6. Left the protected canary runtime, rollback payloads, database, installed app, stable daemon, guard, and interlock unchanged.

Exact identity and evidence

• App source: f97f4cea5fe16cb66fe69929f670fce40a11d450
• App executable SHA-256: d7bb71eba28f812b53f787e1d2020add0d6b99aa258b396a1a0c7f2adeab8de7
• App full arm64 CodeDirectory SHA-256: 2b3336065acd6998f83797a2a31614d3ab7350ce36dd4250febb92aacb29dac8
• Daemon source: 3834d4522aad647411385a244d882c80194af3c1
• Daemon SHA-256: 220f6eac4298ca32faf866d0edc6308924482d2980730368faf12bb355fce949
• Gate receipt SHA-256: 28290b03524b035b525f4deaad36a13f1f806f2b3a5e74a8b3b301bde7d9301b
• Frozen evidence recursive SHA-256: c45876abd151332a2ca3a8da8998c9f493de6ae7b983a31a9591ee8347f837d9
• Evidence shape: 30 files, one nested directory, zero symlinks, 342,617 bytes
• Frozen sample-history SHA-256: a1eae57590371002f5e1e5ed75204a28e6dfc380d3c7e7f2fed4e75678b85c2d
• Independent verifier-log SHA-256: 1c897a55e7b2891d282cf13912627c0d036288337993c59667173b3d3f66ab91

Gate result

• Independent verifier exit: 0
• Saved receipt matched independent recomputation: yes
• Gate samples: 31
• Post-warm-up gate duration: 1,800.326777 seconds
• Physical footprint at boundary: 67.766815 MiB
• Physical-footprint end-to-end delta: -2.288650 MiB/min
• Physical-footprint least-squares slope: -1.169379 MiB/min
• RSS at boundary: 138.578125 MiB, diagnostic only
• RSS end-to-end delta: -0.855574 MiB/min, diagnostic only
• Descriptor range: 26–28
• TCP descriptor counts: exactly 2
• Maximum all-sample gap: 60.131892 seconds

The first corrected replay from rdmpw3275m failed closed with stable daemon hash differs from policy, as expected because that host is not the protected canary. The same frozen directory was then copied unchanged to a temporary path on rdmbair15m5; the verifier found the exact installed stable daemon and executable-path identity and exited 0. An earlier invocation that omitted the required stage argument is separately retained as a caller error. Neither failed invocation is a gate failure.

Verification commands and evidence

Representative commands run:

PYTHONDONTWRITEBYTECODE=1 python3.14 verify_canary_gate.py "$FROZEN_STAGE" short
PYTHONDONTWRITEBYTECODE=1 python3.14 recursive_manifest.py "$EVIDENCE_DIR"
shasum -a 256 short-gate.json samples.jsonl verify-short-independent.log
verify_guard_power_protected.zsh "$CANARY_STAGE"
ticket comment ISSUE-20260914-15 "<frozen receipt>" --author codex@rdmpw3275m/01a078a7
ticket heartbeat ISSUE-20260914-15 --as codex@rdmpw3275m/01a078a7 --ttl 24h
/Users/richh/dev/fleet/maintenance/scripts/fleet_checkin_sync.zsh

Fresh post-freeze verification at 23:18–23:20 EDT returned:

• Guard verification exit 0: AC power, open clamshell, active PreventSystemSleep and PreventUserIdleSystemSleep, armed identity-pinned reboot interlock, heartbeat age 20 seconds.
• Short verifier exit 0 with the same gate receipt; 59 total live samples by the probe, current elapsed 3,483.742126 seconds, current physical footprint 70,878,408 bytes.
• Exact stable daemon and installed app executable hashes still matched policy.
• Both status endpoints returned HTTP 200.
• Live database PRAGMA quick_check returned ok; 158,445 rows; exactly one last_seen_at column.
• Canonical and local frozen evidence manifests matched exactly.

Canonical registry recovery pair

• Before SHA-256: 4f2749e6a88f1f8ae3b1324c8e62171c026787e3ffbd29ece687534daecf5d34
• After SHA-256: 28913b8091ea84ce3a374ac0dcfd2c838f7fe1929b6e01d109502a627ad5f918
• Recovery copies:
  • /Users/richh/dev/_handoff/tyrell-build25-r2-short-gate-evidence-20260915-2308/registry/PROJECTS.before.md
  • /Users/richh/dev/_handoff/tyrell-build25-r2-short-gate-evidence-20260915-2308/registry/PROJECTS.after.md

AGY monitor state

The one local AGY parent remains live as PID 5069, TTY ttys011, conversation 79bad69b-cf45-4f90-b76e-157012ec740b. Its transcript, conversation database, and task steps were actively advancing at 23:19 EDT with no observed HTTP 429 or RESOURCE_EXHAUSTED evidence, so no duplicate parent was created and no quota-resume action was taken. It advanced the local macOS-ramDisk-app repository to 548f50c9bc70518ffc0b97635fccf2fa69808516, but the canonical hub still reports origin/main at 8f9a114b8fad07d384daf4adf637ebbf02fdd28e and SESSION-STATE.md still names 06174e3...; AGY completion is therefore not accepted. The same parent is now actively investigating claimed RTTy ticket ISSUE-20260914-14 on the canonical host.

Rollback and undo

• Do not delete the frozen evidence; it is the audit and rollback record.
• To undo only the canonical registry edit, first verify /Users/richh/dev/PROJECTS.md still has the exact after SHA-256 28913b8091ea84ce3a374ac0dcfd2c838f7fe1929b6e01d109502a627ad5f918. Only then replace it with registry/PROJECTS.before.md. If the live hash differs, merge intentionally instead of overwriting.
• No canary runtime change was made in this milestone, so there is no runtime rollback to execute.
• Existing exact Build 15 daemon and Build 17 app rollback payloads remain armed and protected by the canary guard.

Outstanding gates and owner actions

• Continue uninterrupted same-PID observation through the six-hour boundary at or after 2026-09-16 04:31 EDT.
• Then complete the fixed 24-hour, repeated-inventory, CPU, fresh-app, controlled-reboot, integration, rollback-protected fleet, and release gates in order.
• Do not expand the canary or claim release acceptance from this short-gate receipt.
• Keep monitoring the existing AGY parent; only treat actual HTTP 429 or RESOURCE_EXHAUSTED as quota exhaustion, and resume that exact parent after the evidenced reset rather than creating a duplicate.