{"version":"2.1.277","anchor":"project-context-reload-now-triggered-by-policy-verdict-arriv","canonical_anchor":"project-context-reload-now-triggered-by-policy-verdict-arriv","heading":"Project-context reload now triggered by policy verdict arriving","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/project-context-reload-now-triggered-by-policy-verdict-arriv","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### Project-context reload now triggered by policy verdict arriving\n\nProject context now reloads automatically once an organization's policy verdict arrives\n\n**What**\n\nThe loader that reads a project's context now triggers a reload when the project context comes back empty, tagged with a new reason, `policy_verdict`. A matching status message, \"after the organization's policy arrived,\" was added alongside the existing reload reasons such as `session_start`, `compaction`, and `directory_added`.\n\n**Why**\n\nThis ensures project context gets refreshed as soon as an organization's policy decision comes in, rather than staying stale until one of the other reload triggers fires.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}