Concept

Pre-Execution Authorization

Name: Decionis
Brand: Decionis

Yes, and the distinction is the entire point. Authorization that happens after execution is reporting: the money has moved, the volume is gone, the order has shipped. Authorization that happens before it is a decision the system can still act on — the call is held, the answer comes from written policy rather than the model’s judgement, and the action either proceeds or it does not.

See the patterns that answer this

Can an action be authorized before it runs rather than reviewed after?

2 patterns answer this

Control MCP egress

An agent calls a tool that reaches a network destination, uploads a file, or posts data to a third party.

8 executable policies

Gate agent memory and retrieval

An agent retrieves documents into context, or writes what it learned into durable memory.

6 executable policies

From this term to a governed action

Control MCP egressThe recurring action behind this term.
Copilot Agent Tool WhitelistAn executable policy that implements it.
Try to break it in the sandboxA real signed verdict, no account.
Deploy on your surfaceAvailable on 6 platforms today.
Verify the proof yourselfCheck the signature without trusting us.
Start in Shadow ModeMeasure on your traffic before enforcing.

Related concepts

Browse the full pattern library

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 exists How the protocol works Glossary

Loading…