Tyrell Build 25 app + Build 24 daemon R4 short-gate pass

R4's 30-minute post-warm-up physical-footprint gate passed on designated canary rdmbair15m5, and an independent offline recomputation from a frozen copy matched the guard receipt. This matters because the exact Build 24 daemon has cleared the first memory gate while continuing under the same power-protected guard; it is not a fleet deployment or release acceptance.

Scope

• Coordinator host: rdmpw3275m.
• Runtime host: rdmbair15m5 only.
• Canonical evidence/records host: rdmsm4x.
• Exact process: daemon PID 15449, start Wed Sep 16 17:15:45 2026; guard PID 15146; guard-owned caffeinate PID 15230.
• Existing ISSUE-20260914-15 remains in-progress.
• Local AGY work remains completed and was not resumed.

Gate result

• Saved short-gate receipt SHA-256: 79d45f99020baef9114f15e7e49f650156a89a0804d2e27dd92a888a2aed34dc.
• Independent verifier log SHA-256: 5780b4ea62d5f9563581cc82f9dc6b36fd8e5d8da16a04358a8cf2ed30877380; exit zero and saved_receipt_matched=true.
• 31 gate samples over 1,800.269501 seconds.
• Physical footprint at boundary: 33.110565 MiB.
• End-to-end physical delta: 0.135917150 MiB/min.
• Least-squares physical slope: 0.129291416 MiB/min against the 0.2 MiB/min bound.
• RSS at boundary: 156.921875 MiB; RSS delta -1.094107020 MiB/min, diagnostic only.
• Descriptor range: 25–28.
• TCP descriptor counts: exactly [2].
• Maximum full-series sample gap: 60.058385 seconds.
• Total frozen samples: 43.

Files and records changed

• Canary frozen evidence: /Users/richh/.tyrell/verification/tyrell-build25-r4-short-gate-evidence-20260916-1757.
• Coordinator frozen evidence: /Users/richh/Documents/ChatGPT/rdmpw3275m/handoff/tyrell-build25-r4-short-gate-evidence-20260916-1757.
• Canonical frozen evidence: /Users/richh/dev/_handoff/tyrell-build25-r4-short-gate-evidence-20260916-1757.
• Canonical registry recovery packet: /Users/richh/dev/_handoff/tyrell-build25-r4-short-gate-registry-update-20260916-1803.
• Canonical /Users/richh/dev/PROJECTS.md: SHA-256 changed from b2e2130f7db63d97d170c5528c6b2ace0200d6e47090ef8b17de464e9d82ca86 to 668037c29eb9dec27586655e444f59c3c9aa6ade3ad8b9b3c3c752e668201c83 by compare-and-swap.
• Canonical issue /Users/richh/dev/issues/open/ISSUE-20260914-15-tyrell-mergefleetevents-colon-concatenat.md: SHA-256 changed from 18e76a1528cb51cfba70bc32e2f60e30678eb0948fe2c1ef89e7bb69bb6794eb to 600382ee48a757a10b9bdb4a414bcd7fa75b57ba6ecdb810e6f2e36567e8b1c3 by compare-and-swap.
• Active monitor /Users/richh/.codex/automations/finish-tyrell-build-16/automation.toml: SHA-256 a3f97ff9b911f80c0fa019ec900a4f1273630de031a1f6f38e0680c8d9eefac6; it now monitors the same-process six-hour gate and explicitly forbids another AGY resume.

Commands and verification

• Read the guard-produced short-gate.json only after its scheduled appearance.
• Copied a bounded snapshot of the stage without candidate or rollback app/daemon payloads, preserving scripts, runtime state, sample history, allocation attribution, probe/receipt evidence, and gate artifacts.
• Ran PYTHONDONTWRITEBYTECODE=1 /opt/homebrew/bin/python3.14 verify_canary_gate.py <frozen-directory> short on rdmbair15m5; reran it after final manifest promotion without writing to the packet.
• Generated and checked MANIFEST.sha256; ran recursive_manifest.py independently on coordinator, canary, and canonical copies; parsed every JSON/JSONL file.
• Reverified the exact PID/start/path/hash, Build 25 app identity, AC/open power envelope, both sleep assertions, armed reboot/guard-loss interlock, recovery sentinel, disabled normal candidate autoload, two HTTP 200 JSON status planes, database quick_check=ok, and one daemon/app/bar process each.
• Used the packeted apply_registry_cas.zsh on rdmsm4x; it required both live before-hashes, no open file handles, exact staged after-hashes, and a second live-hash check immediately before atomic replacement.

Evidence identities

• Short-gate MANIFEST file SHA-256: 7eca8e2d6ff5e3b0b6b36773063f4b0b0d8f5556de6325a06aa9f7f0cfe8df67.
• Short-gate deterministic recursive SHA-256: 9dff9b957407a97b2373682fb7eb9ab4d253a800eca90a38724fb5a48b931797 across 94 files, five directories, zero symlinks, and 465,772 bytes on coordinator, canary, and canonical hosts.
• Registry packet MANIFEST file SHA-256: 98d48d1bc5e485ac00cc55a66968790066065a6115bee08b0664e3cf369843dd.
• Registry packet deterministic recursive SHA-256: eca80d37fd9e87701baa761e01289680d6594268985e7e649c9bcb229d6c0bb3.

Rollback and recovery

• Exact rollback daemon: Build 15 SHA-256 dbc440bd54b85a54dd6c4150b23b3e508bff7d8d8080687d81b9ba7ac2cbbcf0, CDHash 4344fbe498540b7f8e5a6f46edd7588ec9ed8495.
• Exact rollback app: Build 17 executable SHA-256 8693ebce3d474fed049597d11e3579bf1cd32f7a78acfd9544c78d77592da05e.
• App rollback bundle: /Applications/.tyrell-rollbacks/20260916-170523-2c5ca2a674fe/Tyrell.app on rdmbair15m5.
• Pinned database backup: /Users/richh/Library/Application Support/Tyrell/backups/20260914-2144-build24-r1-preflight-3834d45/tyrell.db, SHA-256 f042ddb7f32ea2fb3b1c48813daae27cc6c343cc7cc3bd934fd0ecbeacc354a6.
• The guard automatically restores these exact identities on power-envelope, lid, process, guard, or health failure. For intentional registry undo, require the recorded live after-hashes and restore from the canonical registry packet by compare-and-swap; otherwise merge newer work.

Outstanding gates

• Same-process six-hour gate not-before: 2026-09-16 23:25:46 EDT.
• Fixed 24-hour gate not-before: 2026-09-17 17:15:46 EDT.
• Repeat-inventory/CPU, fresh-app, controlled-reboot, integration, rollback-protected fleet rollout, and release gates remain open.
• ISSUE-20260915-18 still forbids cutting from current main; no Build 26 cut, tag, integration, fleet expansion, or release was performed.