My personal AI activity
Control what an agent may buy, access or execute on your behalf.
The same protocol, pointed at decisions you make for yourself rather than ones an enterprise makes at scale. Shield governs disputed charges and protection limits; Sense is where you see what your agents are doing and why something was stopped.
What goes wrong
The specific actions teams tell us they are afraid of. Each one is a decision that happens faster than a human can review it.
- An agent buying something you did not approve
- An assistant reaching an account it should not
- A subscription renewing past a limit you set
- A disputed charge you need evidence for
Where the decision goes
One deterministic check between the intent and the effect — ALLOW, ESCALATE or BLOCK, with a signed record either way.
Shield is live on iPhone and in Chrome. Sense is live at sense.decionis.com.
What to do next
The same five steps every time. Nothing else on this page competes for your attention.
- Simulate this recipe
Run the policy against a realistic action in the browser. Push it past what the rules allow and watch the verdict come back. No account.
- View the signed Decision Dossier
See exactly what was decided and why: the rule that fired, the evidence it read, the policy version in force, and an Ed25519 signature you can verify yourself.
- Deploy in shadow mode
Measure what the policy would have caught on your own traffic without touching the live path. Every recipe defaults to shadow, so the first deployment carries no execution risk.
- Connect a real workflow
Point the same policy at the system where the action actually originates — a checkout, an ERP posting, a Zap, an agent's tool call.
- Share the verified result
Publish the proof: a public verification link, an embeddable badge, a PR comment, or an anonymized shadow-mode finding. This is how the next person discovers Decionis.
