rdmpw3275m-changelog-20260911-1900-tyrell-build19-early-memory-gate

Tyrell Build 19 passed its independently reproduced 40-minute physical-memory early rejection gate on rdmbair15m5; the same protected canary continues toward the mandatory six-hour and 24-hour boundaries.

Scope and state

• Coordinator: rdmpw3275m, ticket holder codex@rdmpw3275m/01a078a7.
• Canary: rdmbair15m5 only.
• Stage: /Users/richh/.tyrell/build19-canary-20260911-ec03697.
• Guard PID 69716; daemon PID 69804; process start Fri Sep 11 18:18:18 2026.
• No restart, rollback, app replacement, or fleet expansion occurred in this checkpoint.
• Local agy process count remained zero; manifest and status metadata were unchanged.

Early-gate evidence

• The guard wrote short-gate.json after 31 post-warm-up samples spanning 1800.1648228168488 seconds.
• SHA-256 of short-gate.json: be6a08b44cfece5dd6c0797946663b0a84186c7d79f49d5e2679ea8282f22a71.
• Physical footprint at the gate: 99.43903350830078 MiB, below the 300 MiB early bound.
• Endpoint physical-footprint growth: +0.03489187540655263 MiB/min, below the +0.20 MiB/min limit.
• Least-squares physical-footprint slope: -2.3925734047232883 MiB/min.
• Diagnostic RSS: 535.609375 MiB, declining at -7.363909033205627 MiB/min; RSS is retained as diagnostic evidence and is not the charged-memory pass/fail field.
• Maximum observed gap between post-warm-up samples: 60.032161235809326 seconds, below the 90-second missing-evidence threshold.
• Every post-warm-up row retained the same PID, process-start identity, and release executable path.
• Exact daemon SHA-256 remained 03e365cec1b8219b3d4cc12384b42313936b850748a97727366e6595f4ee390b.
• Exact app executable SHA-256 remained cfb51c67602f9cf6047e4b6bf609ee1a5e24fe99d907269fcf0548d7c5c2c072.
• Both /api/status planes returned HTTP 200. Permission probes remained valid and successful.
• Inventory pass 1 completed; the required unchanged repeated inventory was not yet available.

Commands and records

• Read the live guard state, latest sample, sample series, inventory log, and boundary receipt over fleet SSH.
• Re-ran the reviewed validate_window calculation against the live 31-row post-warm-up series with bytecode generation disabled.
• Re-read the live PID start time, lsof executable identity, app and daemon hashes, and both API status planes.
• Updated TASK-20260911-01, ISSUE-20260905-23, and ISSUE-20260911-15 with bounded evidence.
• Updated heartbeat automation finish-tyrell-build-16 with the early-gate receipt and unchanged remaining gates.

Rollback and remaining gates

• Exact signed universal Build 15 rollback SHA-256 dbc440bd54b85a54dd6c4150b23b3e508bff7d8d8080687d81b9ba7ac2cbbcf0 and the prior Build 17 app remain retained in the canary stage.
• Any later identity, health, evidence-gap, resource, memory, or inventory failure must still roll back automatically.
• Earliest six-hour-after-warm-up gate remains approximately 2026-09-12 00:28:19 EDT.
• Required 24-hour boundary remains approximately 2026-09-12 18:18:19 EDT.
• A passing early gate is not runtime acceptance. CPU review, unchanged repeated inventory, fresh app functional proof, reboot stable-path continuity, controller install, and staged fleet decisions remain outstanding.