{"version":"2.1.225","anchor":"org-memory-discovery-can-be-re-decided-after-an-account-chan","canonical_anchor":"org-memory-discovery-can-be-re-decided-after-an-account-chan","heading":"Org-memory discovery can be re-decided after an account change","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225\/e\/org-memory-discovery-can-be-re-decided-after-an-account-chan","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225","markdown":"### Org-memory discovery can be re-decided after an account change\n\nOrganization memory can be rediscovered after you switch accounts, and it refuses in untrusted folders.\n\n**What**\n\nNew serialized entry points re-run org-memory discovery and report how the decision moved.\n\n**Details**\n\n- refuses to run in an untrusted workspace or when the account boundary changed, returning a refusal with a reason\n- on success it clears the discovery cache, re-runs discovery and reports both the previous and current state\n\n**Evidence**\n\n`{ kind: \"refused\", reason: \"untrusted_workspace\" }`\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 0\/5"}