feature · access-vs-authority
5 tags · 32 out · 32 in · 3 artifacts · 0 gaps · 1 corpus docs
Access vs authority separates two questions: Can this actor see the information? vs May this actor cause this effect? Read clearance and execution policy are different engines. Authority is multi-dimensional (project, amount threshold, decision class, HR scope) — not a single 0–5 number.
Policy gate before execute; stalled vs slow approvals; financing thresholds. Humans keep judgment; OS enforces bounds.
Graph edges for this feature — technologies, category lens, companies, DM.
features/access-vs-authority/README.md
No open gaps for this entity.
Access vs Authority Separation · ok
features/access-vs-authority/README.md
Research path: features/access-vs-authority