rdmpw3275m-changelog-20260913-2144-tyrell-r7-project-index
Updated the shared project index to record the evidence-backed Tyrell Build 20 R7 canary launch and to remove the stale claim that Build 16 and the first stable-path canary were still pending.
Detailed changelog
Scope
- Host performing the change:
rdmpw3275m. - Shared file changed:
/Users/richh/Library/Mobile Documents/com~apple~CloudDocs/Codex/projects/AGENTS.md principles/PROJECTS.md. - Project entry changed: Tyrell only.
- Canonical Tyrell source was not edited.
- No application, daemon, database, credential, ticket state, or fleet-host runtime was changed by this project-index update.
Change
- Replaced the stale 2026-09-06 Tyrell status line with the verified 2026-09-13 Build 20 R7 canary state.
- Recorded the original mutable-build-path outage root cause and durable hash-addressed lifecycle.
- Preserved the separate rejection states of Builds 16, 18, and 19.
- Recorded exact Build 20 source, daemon, app, canary, rollback, and validation identities.
- Recorded
ISSUE-20260913-09, the R6 rollback-payload root cause, and the hardened R7 ordering fix. - Recorded the R7 launch time and short, six-hour-after-warmup, and fixed 24-hour boundaries.
- Kept the result explicitly
SOAKING_NOT_ACCEPTEDand prohibited fleet expansion until all remaining gates pass.
Commands and verification
- Read the existing Tyrell line and checked the shared file for active open-file writers; none were reported.
- Applied a one-line replacement through the required patch mechanism.
- Re-read the exact Tyrell entry with an anchored search and confirmed there is one matching project line at line 26.
- Verified the shared file mtime advanced and the new line contains
the canonical R7 receipt SHA-256
c34f2b99aa407370925b51e1605eb65a4e088498f65ee16818735dd1ab7590d3. - The R7 runtime itself was independently rechecked at 2026-09-13
21:43:46 EDT: same daemon PID/start/path across 27 samples, maximum gap
60.041460 seconds, AC/open envelope only, zero status or permission
failures, both APIs HTTP 200 valid JSON, database quick-check
ok, exact daemon and app hashes, and no guard failure artifact.
Backups and durable evidence
- Canonical R7 launch receipt:
rdmsm4x:/Users/richh/dev/_handoff/tyrell-build20-memory-20260912/canary-r7-launch-20260913-2117/README.md, SHA-256c34f2b99aa407370925b51e1605eb65a4e088498f65ee16818735dd1ab7590d3. - Exact Build 15/17 rollback remains retained inside the canary R7 stage.
- Retained Build 17 application rollback:
rdmbair15m5:/Applications/.tyrell-rollbacks/20260913-211712-2c5ca2a674fe/Tyrell.app. - This changelog is additive. No user data was deleted or overwritten.
Undo
Restore only the prior Tyrell project-index line from the immediately preceding iCloud file version if the status entry itself must be reverted. Do not roll back any Tyrell runtime or database merely to undo documentation. The runtime remains governed by the R7 guard and its separately verified rollback payload.
Outstanding work
- R7 short gate: 2026-09-13 21:57:44 EDT.
- R7 six-hour-after-warmup gate: 2026-09-14 03:27:44 EDT.
- R7 fixed 24-hour gate: 2026-09-14 21:17:44 EDT.
- Repeated inventory, CPU, fresh-app, and controlled-reboot proof remain required before any release acceptance or fleet expansion.