The protected Tyrell Build 23 R1 canary briefly lost AC power and automatically returned rdmbair15m5 to the exact verified Build 15 daemon / Build 17 app production baseline.

Tyrell Build 23 R1 canary environmental rollback

• Event time: 2026-09-14 20:33:42-20:33:58 EDT
• Host: rdmbair15m5
• Scope: Tyrell canary runtime only
• Classification: INCONCLUSIVE_ENVIRONMENTAL_INTERRUPTION

What changed

• pmset recorded a transition to battery at 20:33:42 EDT and back to AC at 20:33:52. An independent verifier observed the non-AC state at 20:33:47.
• The identity-pinned canary guard detected the power-envelope violation, failed closed, and restored the retained exact Build 15 daemon and Build 17 app.
• The guard disarmed the reboot interlock, re-enabled the normal service, and removed the candidate guard, caffeinate, recovery plist, and active-canary marker. The live healthy database was not restored or replaced.
• Build 23 R1 is prohibited from relaunch or fleet expansion. Its short and repeated-inventory passes remain historical evidence; its long-gate clocks are void.

Files and evidence

• Runtime stage: /Users/richh/.tyrell/build23-canary-r1-20260914-093d653
• Canonical immutable copy: /Users/richh/dev/_handoff/tyrell-build23-memory-20260914/canary-r1-ac-loss-rollback-20260914-2033
• MANIFEST.sha256 file SHA-256: 637e25d5e14c47406873dd74b0bd82372cf796df940abdf8f40bbc0db8c046e2
• Recursive content SHA-256: 51e788cf82e74ca4a83fbbbd5b18d7c705b9ecd1c298068b9f57a02d397f0af5
• Evidence includes README.md, ENVIRONMENTAL-INTERRUPTION.json, POWER-EVENT.log, ROLLBACK-VERIFICATION.json, guard state, interlock state, candidate samples, and recovery checks.

Verification

• Exact Build 15 daemon SHA-256: dbc440bd54b85a54dd6c4150b23b3e508bff7d8d8080687d81b9ba7ac2cbbcf0; strict Team ZU2882L4HT signature; universal x86_64 arm64; launchd one run, no exit.
• Exact Build 17 app executable SHA-256: 8693ebce3d474fed049597d11e3579bf1cd32f7a78acfd9544c78d77592da05e; version 0.2.0 build 17; strict/deep signature; notarized Developer ID Gatekeeper acceptance; one app plus one menu-bar helper.
• Both status APIs returned HTTP 200 valid JSON. SQLite quick_check=ok, 153,659 rows, and one last_seen_at column were observed. No database restore occurred.
• Candidate daemon count zero, guard count zero, caffeinate count zero, active-canary marker absent, recovery plist absent, interlock disarmed, service enabled.

Commands and undo

• The coordinator used read-only pmset, launchctl, process, hash, codesign, spctl, HTTP, and SQLite checks over private fleet SSH after the automatic guard rollback.
• Do not undo this rollback. The current exact Build 15/17 baseline is the recovery target. A later Build 24-or-newer candidate may be installed only after a fresh complete preflight and must restart every canary gate from zero.
• No owner action is currently required beyond keeping the canary on stable AC/open conditions for any future explicitly gated run.