{"version":"2.1.237","anchor":"claimed-sender-text-must-actually-appear-in-the-event","canonical_anchor":"claimed-sender-text-must-actually-appear-in-the-event","heading":"Claimed sender text must actually appear in the event","tier":"internal","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.237\/e\/claimed-sender-text-must-actually-appear-in-the-event","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.237","markdown":"### Claimed sender text must actually appear in the event\n\nA pushed message can no longer claim words it never actually delivered; mismatched sender text gets stripped.\n\n**What**\n\nIf a pushed event says who sent it and quotes their text, the harness checks that the escaped form of that text really appears inside the event body. If it does not, the sender text is stripped from the recorded provenance and a warning is logged, so provenance cannot claim a sender string the delivered event never contained.\n\n**Details**\n\n- Same poll-events gating as the rest of this path; the event itself is still delivered, only the unverifiable sender text is removed.\n\n**Evidence**\n\n`poll_event: sender_text dropped from provenance \\u2014 its escaped form is not embedded in the event element (derivation contract violated)`\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}