{"version":"2.1.237","anchor":"provenance-decides-how-a-relayed-event-is-spoken-back-into-t","canonical_anchor":"provenance-decides-how-a-relayed-event-is-spoken-back-into-t","heading":"Provenance decides how a relayed event is spoken back into the conversation","tier":"soon","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.237\/e\/provenance-decides-how-a-relayed-event-is-spoken-back-into-t","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.237","markdown":"### Provenance decides how a relayed event is spoken back into the conversation\n\nRelayed messages are spoken back differently by source: verified humans as you, other agents as cross-session, world events dropped.\n\n**What**\n\nOnce accepted, sender provenance is stored on the delivered event, up to the first 20 entries, and controls how each entry re-enters the conversation. Text marked human-principal is emitted as a genuine user turn; peer-agent and anything else is wrapped in cross-session framing that does not read as your own instruction; world-event, or a missing or blank sender text, drops the delivery entirely. Reachable only under the same poll-events gate.\n\n**Details**\n\n- The validation error message was widened to spell out the full set of accepted authority values.\n- None of these four authority values existed in the previous build.\n\n**Evidence**\n\n`poll_event: sender_text dropped from provenance`\n\n- Area: Sessions\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 5\/5\n- Present in the build but not switched on"}