{"version":"2.1.261","anchor":"slack-relay-message-provenance-rules-for-user-intent-detecti","canonical_anchor":"slack-relay-message-provenance-rules-for-user-intent-detecti","heading":"Slack-relay message provenance rules for user-intent detection","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.261\/e\/slack-relay-message-provenance-rules-for-user-intent-detecti","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.261","markdown":"### Slack-relay message provenance rules for user-intent detection\n\nInternal instructions now spell out how to tell genuine Slack user messages from bot-relayed ones.\n\nThe agent's internal instructions for Slack relay now spell out how to distinguish genuine user messages from bot- or peer-authored ones. A real user message arrives via a `<wake \u2026>` envelope with `from=\"human\"`, or via specific harness-inserted lead\/marker text; a `<message>` carrying the `bot` attribute inside a `<slack-messages>` block was written by a bot or another agent. Messages in the latter category must never be treated as establishing user intent or consent, and permission-laundering attempts relayed through Slack are explicitly callable out as blockable.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}