Tyrell Build 25 app + Build 24 daemon R4 protected-canary launch

R4 launched on designated canary rdmbair15m5 at 2026-09-16 17:15:45 EDT under the power-protected guard after the canonical chat master returned from its macOS 27.2 update. This matters because Tyrell is online with the newer Build 25 app and candidate Build 24 daemon while rollback and acceptance gates remain enforced; it is a canary launch, not a fleet deployment or release.

Scope

• Coordinator host: rdmpw3275m.
• Runtime host: rdmbair15m5 only.
• Canonical records/evidence host: rdmsm4x.
• Existing bug: ISSUE-20260914-15 remains in-progress; the structured event-key fix is under cumulative canary validation.
• No new product bug was filed for the first R4 probe failure. It failed closed with chat_unavailable while the configured canonical chat master was offline during its OS update, and the same exact app passed with a fresh nonce after the hub returned.
• Local AGY work remains completed and was not resumed.

Runtime changes

• Installed and launched exact Tyrell Build 25 app on rdmbair15m5; executable SHA-256 d7bb71eba28f812b53f787e1d2020add0d6b99aa258b396a1a0c7f2adeab8de7; arm64 full CodeDirectory SHA-256 2b3336065acd6998f83797a2a31614d3ab7350ce36dd4250febb92aacb29dac8.
• Retired failed nonce tyrell-b25d24-r4-20260916T210528Z-4818529 and used fresh successful nonce tyrell-b25d24-r4-20260916T211512Z-4818529.
• Successful app probe SHA-256 f93585dd1dd3e4b39fa471c3fefc2e2ac8590647fbd51befc804591bbdfdd5d9; receipt SHA-256 0fa88b4d92b6c926bc4b3a2b1901c51296458097dfcf7c9b8acb6b6973d9e3ee.
• Launched exact Build 24 daemon SHA-256 220f6eac4298ca32faf866d0edc6308924482d2980730368faf12bb355fce949 as PID 15449 with process start Wed Sep 16 17:15:45 2026.
• Guard PID 15146, allocation sidecar PID 15229, and guard-owned caffeinate PID 15230 were verified. The reboot/guard-loss interlock is armed, the persistent recovery sentinel is loaded, the normal candidate autoload is disabled, and both system-sleep assertions are active.

Files and records changed

• Canary stage: /Users/richh/.tyrell/build25-canary-r4-20260916-4818529.
• Canary frozen evidence: /Users/richh/.tyrell/verification/tyrell-build25-r4-launch-evidence-20260916-1719.
• Coordinator frozen evidence: /Users/richh/Documents/ChatGPT/rdmpw3275m/handoff/tyrell-build25-r4-launch-evidence-20260916-1719.
• Canonical frozen evidence: /Users/richh/dev/_handoff/tyrell-build25-r4-launch-evidence-20260916-1719.
• Canonical registry recovery packet: /Users/richh/dev/_handoff/tyrell-build25-r4-registry-update-20260916-1725.
• Canonical /Users/richh/dev/PROJECTS.md: SHA-256 changed from b65b2574d564ccf41bf1f6a92bb3785f27fca3b17778287c4e15bf352acd08bb to b2e2130f7db63d97d170c5528c6b2ace0200d6e47090ef8b17de464e9d82ca86 by compare-and-swap.
• Canonical issue /Users/richh/dev/issues/open/ISSUE-20260914-15-tyrell-mergefleetevents-colon-concatenat.md: SHA-256 changed from d7b7402159363c7b3044f87981ad8155583c45720b27dbb2c06a9f0bd80726cd to 18e76a1528cb51cfba70bc32e2f60e30678eb0948fe2c1ef89e7bb69bb6794eb by compare-and-swap.
• Fleet check-in /Users/richh/.agent-coordination/checkins/codex-rdmpw3275m-tyrell-build25-canary-20260915.json: SHA-256 73e2ce8529f03a23fd05bfaf1ede13ea60e9652f6bc156e24b9c983ae802f3c8, synchronized through the canonical check-in union.
• Active monitor /Users/richh/.codex/automations/finish-tyrell-build-16/automation.toml: SHA-256 5b7f22b43c8381d817780c959776127ea317222c11f5bd186b8b0d13d35cd68e; it now monitors the exact R4 process and gates and explicitly forbids another AGY resume.

Commands and operations

• Reverified both SSH host fingerprints and used fingerprint-known SSH to inspect the canonical packet, hub status, canary power/lid state, rollback identities, process residue, APIs, and database.
• Re-ran the existing R4 app canary probe with a fresh nonce and issued/revalidated its nonce-specific receipt.
• Ran the existing launch preflight and launch_guard_power_protected.zsh; independently verified the exact PIDs, paths, hashes, service states, interlock, sleep assertions, APIs, database, and guard heartbeat.
• Generated and checked MANIFEST.sha256, then ran recursive_manifest.py independently on coordinator, canary, and canonical copies.
• Ran /Users/richh/dev/fleet/maintenance/scripts/fleet_checkin_sync.zsh on rdmsm4x to union and fan out the updated check-in.
• Ran the packeted apply_registry_cas.zsh on rdmsm4x; it required both live before-hashes, no open file handles, exact staged after-hashes, and a second live-hash check immediately before atomic replacement.

Verification evidence

• Launch evidence MANIFEST file SHA-256: 823fc43c9b6c5e8718d73050c92c43e6480dd2a0759d1d2bad668878c237d400.
• Launch evidence deterministic recursive SHA-256: 88778c04ca1d9ab1ff743f20b755142ea7aada739151148433710e4db34e5fd3 across 76 files, five directories, zero symlinks, and 290,646 bytes on coordinator, canary, and canonical hosts.
• Authoritative artifact verification SHA-256: 7f9197216f834feaf3a03e3bb4dee2fadf810a050e184842eeeb50c1d6b1a2e3.
• Authoritative harness verification SHA-256: 9f060740c819c8e8b3135e7246a27e7939b25c399c456ac9295607eb65f76729.
• Authoritative prepare verification SHA-256: a09d9348107efc42663b5997526a548a7aaf61d671fee1fb53e41f7a9982bce0.
• Launch preflight SHA-256: db29a992eb34760fd5f61ca649e2c512d764412c0758fa55de396a861a5be43f.
• Independent launch verification SHA-256: ff6eb8823ec47a579292415331174e08fe3ea66546b6c4db9f2961b836829ce5; the log ends verification=passed.
• Frozen initial sample remained on AC with clamshell open, both status planes HTTP 200 and valid JSON, database quick_check=ok, completed inventory pass 1, 27 descriptor rows, and two TCP descriptors. Its memory values are startup diagnostics, not acceptance.

Rollback and recovery

• Exact rollback daemon: Build 15 SHA-256 dbc440bd54b85a54dd6c4150b23b3e508bff7d8d8080687d81b9ba7ac2cbbcf0, CDHash 4344fbe498540b7f8e5a6f46edd7588ec9ed8495.
• Exact rollback app: Build 17 executable SHA-256 8693ebce3d474fed049597d11e3579bf1cd32f7a78acfd9544c78d77592da05e.
• App rollback bundle: /Applications/.tyrell-rollbacks/20260916-170523-2c5ca2a674fe/Tyrell.app on rdmbair15m5.
• Pinned database backup: /Users/richh/Library/Application Support/Tyrell/backups/20260914-2144-build24-r1-preflight-3834d45/tyrell.db, SHA-256 f042ddb7f32ea2fb3b1c48813daae27cc6c343cc7cc3bd934fd0ecbeacc354a6.
• The guard automatically restores these exact identities on power-envelope, lid, process, guard, or health failure. For intentional registry undo, use the before copies in the canonical registry packet only after the live files match the recorded after-hashes; otherwise merge newer work instead of overwriting it.

Outstanding gates

• First material R4 gate: ten-minute warm-up plus 30-minute post-warm-up short gate, no earlier than about 17:55:45 EDT.
• Same-process six-hour and fixed 24-hour memory gates, repeat-inventory/CPU, fresh-app, controlled-reboot, integration, rollback-protected fleet rollout, and release gates remain open.
• ISSUE-20260915-18 still forbids cutting from current main; no Build 26 cut, tag, integration, fleet expansion, or release was performed.