---
name: surfaced-payload-names-its-cadence
description: "Grill rule (adopted 2026-08-01, releases#63): a newly ratified surfaced payload must name which existing surfacing discipline it follows (delta / once-per-session / every-occurrence) or state it follows none — an entry silent on cadence does not pass."
metadata: 
  node_type: memory
  type: feedback
  originSessionId: 036bd96c-476d-4483-890f-109d0dfc9f02
  modified: 2026-08-01T01:27:16.893Z
---

**The miss class (todlando's RCA on releases#63):** the trust-warning grill ratified
the CONDITION (which passes warn) and never the CADENCE (how often). It survived a
grill, a build, a gate and a docs leg because REPLAY dedup — the same message twice
— wore similar words to repetition dedup, and the similarity let the gap sit
unexamined. Shipped behavior warned on EVERY message; the operator's intent was
once per session, "like a monic."

**Why:** condition and cadence are separate ratification questions, and the cadence
vocabulary usually already exists in the design record (CONTEXT §mnemonics "delta
discipline") — the failure is not missing concepts but an entry that never binds
itself to one.

**How to apply (my grill checklist):** when ratifying any payload that surfaces to
an agent or operator (warnings, monics, notices, advisories), require the entry to
name its surfacing discipline from the existing vocabulary — delta discipline /
once-per-session / every-occurrence — or state explicitly that it follows none and
why. Silence on cadence = the entry does not pass. Watch specifically for
replay-dedup language masquerading as repetition-cadence coverage.

Related: [[premature-closure-guards]] (write constraints into the artifact at
mint), [[w5-monic-wave]].