A clean Tyrell Build 20 R6 canary stage was prepared on rdmbair15m5 after the R5 AC-loss rollback, but deliberately left inert while the Mac remains on battery power.

Tyrell Build 20 R6 prepared stage

Date: 2026-09-13 17:13-17:17 EDT
Host changed: rdmbair15m5 only
State: PREPARED_NOT_INSTALLED_OR_LAUNCHED

Changes

• Created /Users/richh/.tyrell/build20-canary-r6-20260913-96a5fc0 with only the immutable Build 20 candidate, daemon, guard, launcher, verifier, policy, memory validator, installers, lifecycle libraries, service template, and fresh prior.json/state.json.
• Copied no R5 samples, inventory, gate, failure, footprint, vmmap, migration, logs, PIDs, or other runtime evidence.
• Recorded the exact currently healthy Build 15 daemon, Build 17 app, pinned database backup, and preparation-time daemon PID as rollback provenance.
• Performed only read-only verification and installer dry-run after staging. Build 20 was not installed or launched; exact Build 15/17 remained active.

Verification

• state.json SHA-256: d6e1ca07dc3fb7228b56b824f37ea6feff2482d13d98940cc65c086fab7cdf73
• prior.json SHA-256: 6e7d638721c07d6ed5c59e60ed13eaa60604545e35c1382691975ec3d5a8f327
• Candidate app executable SHA-256: 423871cede8ae6313c486929f544dbee8d1085540b2d37896de6f2c2d4de90fd
• Candidate arm64 CandidateCDHashFull: 37a0081b06af970866e84877cc74524cdac750580d5fad22fb83d92d0eb0aa5c
• Candidate daemon SHA-256: 71bf6122e453315205f3f0dfaf3f1a3a6cf2d99dfe901cda88e7ac79a8112c77
• Guard, launcher, verifier, policy, validator, and every dependency matched pinned hashes.
• App passed strict deep signature and Gatekeeper assessment as notarized Developer ID; daemon passed strict signature and universal x86_64 arm64 verification.
• Python compilation and zsh syntax passed.
• App installer dry-run preserved designated requirement and found one current rollback process, no legacy process, and no retired process.
• Pinned backup: quick_check=ok, 152805 rows, exact SHA-256.
• Live database: quick_check=ok, one additive last_seen_at, 153176 rows.
• Both status ports returned HTTP 200 valid JSON; exact Build 15/17 hashes remained installed; no R6 guard existed.
• Canonical receipt: /Users/richh/dev/_handoff/tyrell-build20-memory-20260912/canary-r6-prepared/R6-PREP.md
• Receipt SHA-256: 85224f5c81f1a3c6035eae2a76bff55cc02891c9c84a81f3e9305ad21225a205

Rollback and next action

• No rollback is needed because R6 is inert and Build 15/17 remain active.
• Deleting the prepared R6 stage is not required and was not performed; it is isolated and non-running.
• The Mac was battery-powered with open lid at final verification. Reconnect it to AC before any launch.
• Launch requires two fresh AC/open reads plus exact prepared-state, hash, signature, Gatekeeper, rollback, API, database, and no-writer checks. Every acceptance clock restarts from zero.
• No fleet expansion, database restore, deployment, or release action occurred.