{"version":"2.1.221","anchor":"org-memory-write-grants-get-stricter-verdicts-and-new-teleme","canonical_anchor":"org-memory-write-grants-get-stricter-verdicts-and-new-teleme","heading":"Org-memory write grants get stricter verdicts and new telemetry","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221\/e\/org-memory-write-grants-get-stricter-verdicts-and-new-teleme","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221","markdown":"### Org-memory write grants get stricter verdicts and new telemetry\n\nOrg memory now falls back to read-only when write permission is ambiguous, with new logging for why.\n\n**What**\n\nThe org-memory mount computes an explicit verdict before granting rw and clamps to ro whenever that verdict fails, with three new telemetry events recording why.\n\n**Details**\n\n- mirrored or duplicate paths are rejected as \"conflicted_mirror\"\n- rw requires exactly one grouping root at depth 0 with mode rw, otherwise \"verdict_failed\"\n- private candidates are vetoed as \"private_candidate_veto\"\n- the org_memory_writes gate event now reports those reasons, tengu_org_memory_root_write_outcome records the outcome per mount, and tengu_org_memory_token_discarded fires when a stale token is dropped\n- all three event names are new in this build; the path is only reached for org-memory mounts\n\n**Evidence**\n\n`tengu_org_memory_root_write_outcome`\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 0\/5"}