Coordinated and independently verified the exact Tyrell Build 20 R8 single-host canary launch; the run is healthy and sampling, with all acceptance clocks restarted and no fleet expansion.

Scope and outcome

• Coordinator: rdmpw3275m.
• Changed product host: rdmbair15m5 only.
• Exact Build 20 app and daemon launched under the pinned power-protected R8 guard at 10:15 EDT.
• No local agy work was eligible to resume, no agy CLI was launched, and no other fleet host changed.

Files and commands

• Local receipt source: /Users/richh/Documents/ChatGPT/rdmpw3275m/handoff/tyrell-build20-r8-launch-20260914-1015/README.md.
• Canary stage: /Users/richh/.tyrell/build20-canary-r8-20260913-96a5fc0 on rdmbair15m5.
• Ran agentkit preflight, fleet-mail sync, two fresh AC/open reads, the complete R8 launch preflight, pinned application installer, pinned guarded launcher, independent guard/process/API/database verification, and immutable launch snapshot capture.
• Two local command-construction attempts failed before SSH due unescaped template expressions; they made no remote call and no state change.

Verification

• Daemon PID 39036, exact SHA-256 71bf6122e453315205f3f0dfaf3f1a3a6cf2d99dfe901cda88e7ac79a8112c77, exact hash-addressed release, runs=1, never exited.
• App SHA-256 423871cede8ae6313c486929f544dbee8d1085540b2d37896de6f2c2d4de90fd, Gatekeeper accepted as Notarized Developer ID.
• Guard PID 38849, child caffeinate PID 38910, both system-sleep assertions active.
• Both status APIs returned HTTP 200 valid JSON; live database quick-check returned ok with 153,325 files and one additive last_seen_at column.
• Three initial samples retained the same PID/start/path and AC/open envelope with no endpoint, permission, or 503 failures.

Backup, undo, and pending work

• Exact Build 17 app rollback is retained at /Applications/.tyrell-rollbacks/20260914-101514-2c5ca2a674fe/Tyrell.app on the canary.
• Exact Build 15 daemon and the complete signed rollback payload remain pinned in the R8 stage.
• The guard automatically rolls back on failure; never restore the pinned pre-migration database over the live additive database.
• Short, six-hour, and 24-hour gates remain pending. No fleet expansion is authorized.