{"version":"2.1.237","anchor":"resumed-sessions-can-no-longer-inherit-verified-human-status","canonical_anchor":"resumed-sessions-can-no-longer-inherit-verified-human-status","heading":"Resumed sessions can no longer inherit \"verified human\" status","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.237\/e\/resumed-sessions-can-no-longer-inherit-verified-human-status","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.237","markdown":"### Resumed sessions can no longer inherit \"verified human\" status\n\nResuming a saved conversation no longer carries over \"verified human\" trust from the earlier live session.\n\n**What**\n\nLoading a saved conversation, both when resuming normally and when loading by agent ID, now strips authority markers from the replayed messages. Verified-Slack-human flags and classifier metadata lines are deleted, message origins recorded as human or auto-continuation are reset to unclassified, and any stored sender authority of \"human principal\" is downgraded to \"other human\". A replayed transcript can never re-assert authority that was established in an earlier live session.\n\n**Details**\n\n- Runs on every transcript load; there is no flag to disable it.\n\n**Evidence**\n\n`authority: \"human-other\"`\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 4\/5"}