Tyrell Build 26 R4 short gate accepted

Tyrell Build 26 R4 independently passed the unchanged physical-footprint-v2.1 short gate on rdmbair15m5; the protected canary remains live and unmodified while it continues toward the six-hour and fixed 24-hour gates.

Scope

• Coordinator and documentation host: rdmpw3275m.
• Canary host: rdmbair15m5.
• Coordination propagation: all six fleet hosts through the canonical check-in sync on rdmsm4x.
• Product source, release branch, app bundle, daemon binary, guard, assertion, database, and canary stage were not modified by this milestone closeout.
• Local AGY work remains terminal or safely contained. No AGY process or conversation was resumed, and no provider quota-reset event occurred.

Gate result

• R4 stage: /Users/richh/.tyrell/build26-postdeploy-r4-20260917-014653-40145fd.
• Short gate accepted at 2026-09-17 02:37:59 EDT.
• Independent 31-sample window: 1800.3503642082214 seconds.
• Ending physical footprint: 26.251258850097656 MiB.
• Endpoint growth: 0.04530444457509065 MiB/min.
• Least-squares slope: 0.058262195072996265 MiB/min.
• Policy limit: 0.20 MiB/min.
• Descriptor range: 26 through 27.
• TCP baseline/minimum/maximum: 2/2/2; zero excursions.
• Maximum all-sample gap: 60.06115508079529 seconds.
• Identity remained guard PID 78016, exact guard-owned assertion PID 78091, and daemon PID 78205 started Thu Sep 17 01:57:52 2026.
• AC power, closed clamshell, and exact assertion ownership were verified throughout. Closed clamshell is allowed under the protected assertion policy.
• Saved guard receipt and independent recomputation matched. The short gate only is accepted; this is not six-hour, 24-hour, rollout, or release acceptance.
• Diagnostic allocation sidecar PID 78090 completed normally after nine planned attribution snapshots around the first inventory pass and was not restarted.

Immutable evidence

• Canary packet: /Users/richh/.tyrell/verification/tyrell-build26-r4-short-gate-evidence-20260917-0240.
• Coordinator packet: /Users/richh/Documents/ChatGPT/rdmpw3275m/handoff/tyrell-build26-r4-short-gate-evidence-20260917-0240.
• Canonical packet: /Users/richh/dev/_handoff/tyrell-build26-release-20260916/postdeploy-r4-short-gate-evidence-20260917-0240 on rdmsm4x.
• Snapshot manifest file SHA-256: 08bc757b28ffe1ea84c029c897c7d48f510a432c889accd1340da7f3c80c71c6.
• Recursive packet SHA-256: b35618f05e001b57cadbd759a6e4a9c4b3ae1181ccae86f4c9819af253fe4501.
• Packet census: 89 files, 17 directories, zero symlinks, 155,934,028 bytes.
• Saved receipt SHA-256: 20962f42c6b2901b6446d9665d5ae403936d66129821784245a97f0a287cf531.
• Independent verifier output SHA-256: 79eda4f2654854d057fd6ddd5f9de53dfcfaa0ef2ed6b17450241d826262f072.
• Independent verifier tool SHA-256: c6b10b9f41b9bfe2c77f07d2116111e433ce8d56f91d02737497fdd40f29ffec.
• Frozen samples SHA-256: 6267aa5e15978041cb326ed33ea8dc4b8c768facb7be3d3572fe27181f42dc02.
• Runtime verification SHA-256: bca5d94c64bbc34d96322430eba428fec143ed23aa87d2d0122b45d74f936d3f.

State changed

• Updated /Users/richh/.codex/automations/finish-tyrell-build-16/automation.toml through the Codex automation API so future heartbeats treat the short gate as accepted and watch the six-hour gate next. Resulting SHA-256: 89b737d35c1ff967f79405b85bbf7ce0051e60d08974764b7152d97c916dec56.
• Appended the independent pass evidence to ISSUE-20260917-01; the high-severity issue remains in-progress because the six-hour and 24-hour acceptance gates are open.
• Extended the authoritative ticket lease for codex-rdmpw3275m@rdmpw3275m/tyrell-build26-r4 through 2026-09-17 04:44:52 EDT.
• Updated /Users/richh/.agent-coordination/checkins/codex-rdmpw3275m-tyrell-build25-canary-20260915.json with the accepted short gate, evidence hashes, completed sidecar state, live process identity, and next-gate boundary.
• Synced that check-in through /Users/richh/dev/fleet/maintenance/scripts/fleet_checkin_sync.zsh; all six fleet copies independently matched SHA-256 89e03a03916615c769f37938f88721f924636f3c24a070509f3b75dde30616a9.
• The first Apple Notes attempt remained blocked in an AppleEvent while Notes was busy. After Notes became responsive, the required per-host entry was filed and independently verified at 04:16 EDT: folder rdmpw3275m, title rdmpw3275m-changelog-20260917-0416-tyrell-build26-r4-short-gate-pass, record x-coredata://3FF396ED-1AC8-466D-B5F9-AB1CC765F15A/ICNote/p255929, one exact-title match, and all three verification markers present. No Notes action remains pending for this milestone.

Commands and verification

• Read-only remote inspection with ssh, zsh r4_status.zsh, jq, ps, pmset, launchctl, shasum, HTTP status probes, and SQLite PRAGMA quick_check.
• Independent frozen-packet verification with verify_r4_gate_v21.py; result matched the saved guard receipt.
• ticket heartbeat ISSUE-20260917-01 --as codex-rdmpw3275m@rdmpw3275m/tyrell-build26-r4 --ttl 2h.
• ticket comment ISSUE-20260917-01 ... with exact metrics and immutable evidence identifiers.
• Canonical fleet check-in sync invoked on rdmsm4x, followed by independent SHA-256 reads on rdmsm4x, rdmbair13m5, rdmbair15m5, rdmpw3265m, rdmpw3275m, and jdmbair13m5.
• Latest read-only status at 02:44:33 EDT: state soaking, 47 samples, elapsed 2761.2547030448914 seconds, physical footprint 27,526,416 bytes, descriptors 27, TCP 2, completed inventory pass 1, both API planes HTTP 200 with valid JSON, and database quick check ok.

Post-gate investigation update

• The immutable short-gate pass is unchanged, but the same R4 daemon later reproduced step-shaped physical growth: 27,542,824 bytes at elapsed 3001.300 seconds; 37,356,840 bytes at 3061.311 seconds; 43,205,928 bytes at 3181.334 seconds; and 44,565,800 bytes at 3421.380 seconds.
• RSS simultaneously fell from 418,624 KiB to roughly 209,000 KiB. Descriptors remained 27 and TCP remained 2. Exact daemon PID/start, AC power, assertion PID 78091, both API planes, database integrity, and the armed interlock remained healthy.
• The Tyrell unified log records [TCC DRIFT ALERT] at 02:48:00.745 EDT, about 54 seconds before the first stepped sample. Port 43118 connection starts remained at the ordinary four per complete minute, so the prior doubled-sync-burst correlation was not reproduced.
• This strengthens the TCC drift/permissions-scan association and shows R3-like steps can recur with later timing. It does not yet establish monotonic leakage or fail a current gate. The observation was appended to ISSUE-20260917-01 and sent to the canary and canonical owners as message 20260917-025524-7AA470F7; the canary remains unchanged for the six-hour verdict.

Recovery and undo

• No product rollback is warranted by a passing short gate. The active guard retains its prevalidated exact Build 17 app and Build 15 daemon rollback payload plus reboot/guard-loss recovery interlock.
• If the canary fails, allow the guard to execute its built-in exact rollback and preserve the generated failure packet before any source change or relaunch.
• Documentation-only rollback, if an entry is found factually incorrect, is to restore the preceding check-in version from another fleet copy or Git-backed coordination history, amend the open ticket with a corrective comment, and update the automation through its API. Do not delete immutable gate evidence.

Outstanding gates and owner actions

• Same-process six-hour gate: not before 2026-09-17 08:07:53 EDT.
• Fixed 24-hour gate: not before 2026-09-18 01:57:53 EDT.
• Require the same daemon PID and start identity, continuous power/assertion/sample envelope, unchanged repeated inventory where required, healthy API and database checks, and a fresh independent recomputation at each gate.
• Canonical PROJECTS.md remains owner-controlled on rdmsm4x; its owner has been asked to record the R4 short-pass milestone without altering source or main.
• Do not resolve ISSUE-20260917-01, expand rollout, merge the release branch, restart the completed sidecar, or resume any terminal AGY lane from this evidence alone.