Under the hood
Useful2 Signal0
Org memory now falls back to read-only when write permission is ambiguous, with new logging for why.
What's wrong with this entry?
Anonymous. No account, no email.
What
The 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.
Details
- mirrored or duplicate paths are rejected as "conflicted_mirror"
- rw requires exactly one grouping root at depth 0 with mode rw, otherwise "verdict_failed"
- private candidates are vetoed as "private_candidate_veto"
- 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
- all three event names are new in this build; the path is only reached for org-memory mounts
Evidence
tengu_org_memory_root_write_outcome
Strings lifted out of the shipped bundle, so the claim above can be checked against them.