rdmpw3275m changelog — Tyrell cadence decision and monitor refresh

Accepted the bounded FEAT-20260914-01 source-emission cadence, refreshed the active Tyrell/AGY heartbeat with independently verified state, and preserved the boundary between source integration and the protected canary runtime.

Scope

• Host: rdmpw3275m
• Canonical host: rdmsm4x
• Protected canary: rdmbair15m5
• Coordinator: codex@rdmpw3275m/01a078a7
• Tickets: FEAT-20260914-01, ISSUE-20260914-15
• Time: 2026-09-15 23:16–23:28 EDT

Decision

Accepted the proposed FEAT-20260914-01 defaults for source integration:

• session: at most 24 real census-observation events per host per day.
• usage: at most 12 events per host per day, only after at least two hours and a material change of at least one authoritative percentage point or an advice change.
• A zero limit disables that event kind.
• Emitter state remains fixed-size; it does not retain a growing history.

Retention rationale: six hosts add at most 216 rows/day. Against the measured current baseline of about 340 rows/day and a roughly 5,000-row store, this keeps approximately nine days of history—well above the 24-hour Observatory chart window—without allowing usage telemetry to evict quieter kinds at a 15-minute cadence.

The decision was sent to the requesting owner in reply 20260915-232755-17F80227 and to the canonical integrator in message 20260915-232755-0DF40F95. The same text was appended to FEAT-20260914-01 on the canonical ticket engine.

Review boundary

• PR #37 head: 9d467db88df3918e62217f5b250c539b31a54bce
• The GitHub script-contract job is green.
• The GitHub swift build && swift test job is red because the workflow intentionally fails when the read-only ECS_LIBS_TOKEN secret is absent; the code was not evaluated by that job and the failure was not relabeled green.
• Canonical integrator receipt reports 720 Swift Testing cases plus 184/184 and 8/8 XCTest, zero failures, on the merged source packet.
• Cadence acceptance authorizes the documented source merge/push under the existing owner pipeline. It does not authorize installation, canary replacement, fleet runtime rollout, or release.
• Any successor build must retain the Build 24 structured EventKey lineage at 3834d4522aad647411385a244d882c80194af3c1 and remain behind the Build 25/24 protected-canary gates.

Monitor changes

• Updated heartbeat automation finish-tyrell-build-16 in place; it remains ACTIVE every 15 minutes with failed-run-only notifications.
• Automation SHA-256 after update: 74839dcca98766674eb9e5865d5b7f1cd34178bcdda1884a90f25ebde70b63aa.
• Updated Tyrell canary check-in SHA-256: fe024f8541c2e5d6a730a51e4bc750d082985e8f21e39a754f41120c5def464b before its next fleet synchronization.
• The prompt now carries the accepted short-gate evidence, the 04:31 EDT six-hour boundary, all remaining gates, the exact AGY parent identity, its current RTTy work, and the rule that only HTTP 429 or RESOURCE_EXHAUSTED counts as quota exhaustion.

Live state verified

• Tyrell guard and independent short verifier both exited 0 at 23:20 EDT.
• The protected canary remains SOAKING; no runtime mutation was performed.
• Local AGY PID 5069 / conversation 79bad69b-cf45-4f90-b76e-157012ec740b remains active and is currently investigating canonical RTTy ISSUE-20260914-14.
• No actual AGY HTTP 429 or RESOURCE_EXHAUSTED evidence was observed, so no duplicate parent or quota-resume action was taken.
• The macOS-ramDisk-app lane remains unaccepted because its canonical origin and SESSION-STATE.md do not yet reconcile with local/canonical HEAD 548f50c9bc70518ffc0b97635fccf2fa69808516.

Files and durable records

• /Users/richh/.codex/automations/finish-tyrell-build-16/automation.toml
• /Users/richh/.agent-coordination/checkins/codex-rdmpw3275m-tyrell-build25-canary-20260915.json
• /Users/richh/Documents/ChatGPT/rdmpw3275m/handoff/tyrell-feat-20260914-01-cadence-reply-20260915.md
• Canonical FEAT-20260914-01 activity record
• Fleet-bus messages 20260915-232755-17F80227 and 20260915-232755-0DF40F95

Undo and outstanding work

• Cadence defaults remain source-level and reversible until merged; amendments belong in the owner branch and must re-run the affected tests.
• The heartbeat can be updated again in place; do not create a duplicate automation.
• Do not delete or edit provider session/auth databases.
• Continue Tyrell through six-hour, 24-hour, reboot, integration, fleet-runtime and release gates.
• Continue monitoring the exact AGY parent to definitive canonical receipts or an evidenced quota boundary.