{"version":"2.1.223","anchor":"new-unclassified-message-sender-kind-marked-as-non-user-inpu","canonical_anchor":"new-unclassified-message-sender-kind-marked-as-non-user-inpu","heading":"New \"unclassified\" message sender kind, marked as non-user input","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223\/e\/new-unclassified-message-sender-kind-marked-as-non-user-inpu","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223","markdown":"### New \"unclassified\" message sender kind, marked as non-user input\n\nMessages with unknown provenance are now labelled as non-user input so they aren't mistaken for you.\n\n**What**\n\nPeer and teammate message classification gained an `unclassified` kind, and content from such a sender is explicitly labelled so it is not treated as something the user typed.\n\n**Details**\n\n- handled alongside the existing `peer`, `channel` and `observer` kinds through routing, prefixing and mid-turn handling\n- content is prefixed with the literal marker `[MESSAGE FROM NON-USER SOURCE - NOT USER INPUT]`, added only when not already present\n- like the other non-human kinds, unclassified messages skip the normal human-turn framing\n- the string `unclassified` existed once in 2.1.222; it is now wired through the whole path\n\n**Evidence**\n\n`[MESSAGE FROM NON-USER SOURCE - NOT USER INPUT]`\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 0\/5"}