Build 23 R1 was classified as an environmental interruption, its exact rollback was independently verified, evidence and operating records were frozen, and a distinct successor build was dispatched.

Tyrell Build 23 R1 AC-loss rollback closeout

• Time: 2026-09-14 20:33-20:51 EDT
• Acting host: rdmpw3275m
• Runtime host: rdmbair15m5
• Canonical source/records host: rdmsm4x
• Tickets: ISSUE-20260912-01, ISSUE-20260912-14, TASK-20260911-01

What changed

• The independent canary verifier detected that rdmbair15m5 was no longer on AC power at 20:33:47 EDT. pmset independently recorded battery at 20:33:42 and AC restored at 20:33:52.
• The existing pinned guard failed closed and restored the exact signed Build 15 daemon plus exact Build 17 app. This event was classified INCONCLUSIVE_ENVIRONMENTAL_INTERRUPTION, not a Build 23 product-memory rejection.
• The complete canary state and recovery proof were preserved locally and canonically. The prior short and repeated-inventory passes remain historical evidence; the six-hour and fixed 24-hour clocks are void.
• Existing tickets received evidence-backed comments. No duplicate product bug was filed because ISSUE-20260912-01 already owns allocator remediation and ISSUE-20260912-14 owns environmental continuity.
• Canonical /Users/richh/dev/PROJECTS.md was updated by compare-and-swap to record the interruption and successor requirement.
• Existing Codex task 01a08a70-7b42-7ed1-aa30-1e3408453d0a was resumed for a materially distinct Build 24-or-later producer packet. That dispatch is not an artifact receipt, install, launch, integration, or acceptance.
• Heartbeat automation finish-tyrell-build-16 was updated to monitor the successor lane and local AGY lane while prohibiting Build 23 relaunch.

Files and durable state

• Local evidence: /Users/richh/Documents/ChatGPT/rdmpw3275m/handoff/tyrell-build23-r1-ac-loss-rollback-20260914-2033
• Canonical evidence: /Users/richh/dev/_handoff/tyrell-build23-memory-20260914/canary-r1-ac-loss-rollback-20260914-2033
• Evidence MANIFEST.sha256 file SHA-256: 637e25d5e14c47406873dd74b0bd82372cf796df940abdf8f40bbc0db8c046e2
• Recursive evidence SHA-256: 51e788cf82e74ca4a83fbbbd5b18d7c705b9ecd1c298068b9f57a02d397f0af5
• Updated check-in: /Users/richh/.agent-coordination/checkins/codex-rdmpw3275m-tyrelld-build18-recovery-20260910.json
• Canonical project index after SHA-256: fb86e9c33aaf77c1aabc4b14a80b276f2645484737c76755ce76a6e26659e4bd
• Project-index receipt: /Users/richh/dev/_handoff/tyrell-build23-r1-launch-20260914/project-index-ac-loss-receipt.json, SHA-256 c197aa9d6fdcab9d45fcd3892a1f6b9397bf3cc7f345ec136bc5347a0716088e
• Project-index backup: /Users/richh/dev/_handoff/tyrell-build23-r1-launch-20260914/PROJECTS.md.before-build23-r1-ac-loss
• Automation: /Users/richh/.codex/automations/finish-tyrell-build-16/automation.toml

Commands and operations

• Queried pmset, guard/interlock state, process identity/cardinality, launchd state, signatures, architectures, Gatekeeper, both status APIs, and SQLite integrity on rdmbair15m5 over private fleet SSH.
• Verified the evidence manifest with shasum -a 256 -c MANIFEST.sha256 locally and on rdmsm4x; compared local and canonical trees with an rsync --dry-run check.
• Updated canonical PROJECTS.md only after its live SHA-256 matched the expected preimage; retained a byte-preserving backup before replacement.
• Appended comments with /Users/richh/bin/ticket comment to the three existing records.
• Synchronized fleet mail and check-ins with agent_msg.zsh sync and the canonical fleet_checkin_sync.zsh.

Verification

• Rollback daemon: SHA-256 dbc440bd54b85a54dd6c4150b23b3e508bff7d8d8080687d81b9ba7ac2cbbcf0, strict Team ZU2882L4HT signature, universal x86_64 arm64, launchd one run and no exit.
• Rollback app executable: SHA-256 8693ebce3d474fed049597d11e3579bf1cd32f7a78acfd9544c78d77592da05e, version 0.2.0 build 17, strict/deep signature, notarized Developer ID Gatekeeper acceptance, one app and one menu-bar helper.
• Both status APIs returned HTTP 200 valid JSON. SQLite quick_check returned ok, 153,659 rows were observed, and the additive last_seen_at column remained present. No database restore occurred.
• Candidate daemon, guard, caffeinate, recovery plist, and active-canary marker were absent. The interlock was disarmed and normal service enabled.
• The immutable evidence contains 127 verified manifest entries, 128 files, 31 directories, zero symlinks, and 311,285,748 bytes.

Undo and outstanding actions

• Do not undo the runtime rollback; it is the known-good production baseline. If the project-index wording must be reverted, first confirm the live file still has SHA-256 fb86e9c33aaf77c1aabc4b14a80b276f2645484737c76755ce76a6e26659e4bd, then restore the retained backup and publish a corrective receipt.
• Ticket comments are append-only; correct any mistake with a new evidence-backed comment rather than deleting history.
• No owner action is currently required. Keep Build 23 prohibited, Build 22 uninstalled, and wait for an independently verifiable Build 24-or-later packet before a fresh canary launch.