Tyrell Build 24 was independently accepted as a signed and notarized canary candidate, a fresh rollback-safe database backup and inert launch packet were prepared, and the live Build 17/15 baseline was intentionally left unchanged pending explicit runtime-owner acknowledgment.

Tyrell Build 24 independent acceptance and inert canary preparation

• Time: 2026-09-14 21:18-21:55 EDT
• Acting and verification host: rdmpw3275m
• Canonical source and evidence host: rdmsm4x
• Designated canary and backup host: rdmbair15m5
• Tickets: ISSUE-20260914-15, ISSUE-20260912-01, TASK-20260906-01

What changed

• Independently verified the complete frozen Build 24 producer packet from source commit 3834d4522aad647411385a244d882c80194af3c1. The product fix replaces the delimiter-concatenated merge key with a structured EventKey, preventing distinct events whose field boundaries differ from colliding and being discarded. This is a correctness fix and is not evidence that allocator growth is cured.
• Ran the complete Swift test suite from a fresh extraction on rdmsm4x: 553 XCTest cases, 2 environmental skips, 0 failures; 669 Swift Testing cases, 0 failures.
• Independently checked all 117 frozen-manifest entries, app and daemon hashes, universal architectures, strict/deep Developer ID signatures, hardened runtime and timestamp, notarization receipts, stapling, and Gatekeeper acceptance.
• Prepared an inert protected-canary packet locally and mirrored it to the canonical handoff area. The packet contains the exact Build 24 ZIPs, rollback payloads, policy, guard, launcher, allocation sidecar, and test receipts. It was not transferred to the canary and nothing was installed or launched.
• Created a new consistent SQLite backup on rdmbair15m5 without mutating the live database. It passed quick_check, contains 153,929 file rows, retains the additive schema column, and is mode 600.
• Updated canonical /Users/richh/dev/PROJECTS.md by compare-and-swap to record independent Build 24 preflight acceptance while preserving the explicit not launched and zero-clock boundary.
• Updated tickets and the fleet coordination check-in with independent acceptance evidence and the pending runtime-owner gate.
• Sent runtime-freeze requests 20260914-212614-8BFD1B72 and 20260914-213416-818FC7BD to the active claude@rdmbair15m5/dev-a7 source lane. No explicit acknowledgment was present at closeout, so the candidate remains inert.
• Rechecked local AGY state. No agy CLI process exists, all discovered parent runs are complete or closed, no eligible unfinished parent exists, and no real provider quota failure or reset boundary was observed. No AGY process was launched.

Files and durable state

• Frozen producer packet: /Users/richh/dev/_handoff/tyrell-build24-event-key-20260914/frozen-handoff
• Frozen manifest file SHA-256: f79e52f0c05acb5efb6e565d8c86c0f1053e0f80bbfdbb73d424a6bf5fe9c456
• Frozen recursive SHA-256: a04f1c543d75b5661e32e85996eca515a5aaa8fc91f6472bd860c4a902dac882
• Independent verification: /Users/richh/dev/_handoff/tyrell-build24-independent-verification-20260914
• Independent receipt SHA-256: 58ae3d69e000ab295b6259ef1c9f42046d95fd65c403701c0de8fbca9643a6da
• Independent full-suite log SHA-256: f74da590893fc76c212d8855b92dd74cfb856f7f6eb8bf7c66c09c74533ef771
• Local inert prep: /Users/richh/Documents/ChatGPT/rdmpw3275m/handoff/tyrell-build24-r1-launch-20260914
• Canonical inert prep: /Users/richh/dev/_handoff/tyrell-build24-r1-launch-20260914
• Prep receipt SHA-256: e98053fdb0412ca92adf82ca7e2ba113d5a8530a907c522b387354fac6b8ae4c
• Prep recursive SHA-256: 72354234cce95cbd6864c7cce78a2eab7c5e2d06a736dd1e2ba0db2b414466e3
• Canary database backup: /Users/richh/Library/Application Support/Tyrell/backups/20260914-2144-build24-r1-preflight-3834d45/tyrell.db on rdmbair15m5
• Backup SHA-256: f042ddb7f32ea2fb3b1c48813daae27cc6c343cc7cc3bd934fd0ecbeacc354a6
• Updated check-in: /Users/richh/.agent-coordination/checkins/codex-rdmpw3275m-tyrelld-build18-recovery-20260910.json
• Canonical project index after SHA-256: 2e9b130dfd373cc6cf75332d2e55809187e51fd5eab55b3ba2e91ad4ebb3ff36
• Project-index backup: /Users/richh/dev/_handoff/tyrell-build24-r1-launch-20260914/PROJECTS.md.before-build24-independent-acceptance
• Heartbeat automation: /Users/richh/.codex/automations/finish-tyrell-build-16/automation.toml

Artifact identity

• App executable SHA-256: 9298390eeb542cb4f99e380a4fb0f105c334c8099ce427e3e24b0f68762dbafb
• Daemon SHA-256: 220f6eac4298ca32faf866d0edc6308924482d2980730368faf12bb355fce949
• App ZIP SHA-256: 864d1a748129afe82693e3f858214d8af6628e1df48126c208040ac947ed1e12
• Daemon ZIP SHA-256: fc86afd6abd24d2eb47993c409e5c285b5002a25bf935f47910686e43c9a60c0
• App notarization: 1775ea77-4073-459e-a650-cad729cf7157, Accepted
• Daemon notarization: c9ea750b-2a10-4bf0-83f3-a80dcaf60876, Accepted
• Exact source patch SHA-256: 8e24e7e04e33c8bab38bc66d1c5d45d69adc5f46d5cccceeaf7219dba0a10258

Commands and verification

• Verified the frozen producer manifest with shasum -a 256 -c MANIFEST.sha256 and independently matched 117 entries.
• Extracted the source into a fresh canonical handoff directory and ran swift test; the captured log exited zero and has the SHA-256 recorded above.
• Re-extracted the app ZIP into a non-FileProvider temporary directory with ditto --noextattr --noqtn, then ran strict/deep codesign, spctl, stapler validate, architecture, Team ID, hardened-runtime, and timestamp checks. A prior Documents extraction inherited FileProvider extended attributes; the same verified ZIP passed from the clean temporary extraction, establishing an environmental extraction artifact rather than packet corruption.
• Ran 30 iterations of the libproc descriptor probe, 9 reboot-interlock unit tests, the disposable launchd interlock test, the allocation-sidecar self-test, and syntax checks; all passed.
• Queried the canary baseline, service APIs, live database, process cardinality, recovery sentinels, AC power, and open-lid state read-only. The exact Build 15 daemon and Build 17 app remained healthy and unchanged.
• Synchronized fleet mail and check-ins with agent_msg.zsh sync and the canonical fleet_checkin_sync.zsh.

Undo and outstanding actions

• The live canary needs no rollback because Build 24 was not installed or launched. Keep the exact Build 15 daemon and Build 17 app in place.
• The inert handoff directories and database backup are additive evidence. If they are later retired, preserve their manifests and receipts first; no cleanup was performed during this closeout.
• If the canonical project-index wording must be reverted, first verify the live file still has SHA-256 2e9b130dfd373cc6cf75332d2e55809187e51fd5eab55b3ba2e91ad4ebb3ff36, then restore the retained backup and publish a corrective receipt.
• Launch remains blocked only on explicit runtime-freeze acknowledgment from claude@rdmbair15m5/dev-a7, followed by fresh no-writer, AC/open, exact baseline, API/database, interlock, clean-extraction, signing, dry-run, rollback-preflight, and guarded-launch checks. Every Build 24 memory gate starts from zero after launch.
• Canary-host Apple Notes filing for the new database backup remains pending from an Aqua session on rdmbair15m5; the Markdown record is retained locally, canonically, and on that host.
• AGY remains under monitoring. Resume only an exact genuinely unfinished parent after the inactivity and duplicate-writer gates; treat quota as exhausted only after a real provider response supplies a reset boundary.