Decionis

Concept

Permission Fatigue

Because at volume, approving stops being a decision. Anthropic measured that Claude Code users approve 93% of permission prompts and shipped classifiers to cut permission fatigue (Anthropic Engineering, 25 March 2026); a separate 40,000-run study by Scale X found people missed 1 in 3 genuine threats while clicking through. That leaves two bad defaults — approve everything by hand and get nothing done, or skip permissions entirely and hope. Policy-based gating is the third: a deterministic control plane answers on the common path, and a named person is pulled in only when the rules require one, so the approvals someone does see are rare enough to deserve attention.

Why doesn't approving every AI agent action work?

Because at volume, approving stops being a decision. Anthropic measured that Claude Code users approve 93% of permission prompts and shipped classifiers to cut permission fatigue (Anthropic Engineering, 25 March 2026); a separate 40,000-run study by Scale X found people missed 1 in 3 genuine threats while clicking through. That leaves two bad defaults — approve everything by hand and get nothing done, or skip permissions entirely and hope. Policy-based gating is the third: a deterministic control plane answers on the common path, and a named person is pulled in only when the rules require one, so the approvals someone does see are rare enough to deserve attention.

Where this fits

Decionis is the deterministic decision layer between intent and execution. This concept is one way in; the architecture behind it is the same in every case.

Why Decionis existsHow the protocol worksGlossary