Loading…
Execution pattern
Gate agent memory and retrieval
Decide what an agent may read, and what it may keep.
What executes
An agent retrieves documents into context, or writes what it learned into durable memory.
What normally goes wrong
Retrieval quietly widens the blast radius of every later action. Data the actor was never entitled to read becomes data the agent can act on — and, once written to memory, data it carries into unrelated sessions.
The decision
The signals available at the moment of the action, and the rule that judges them.
Signals
- Entitlement of the requesting actor to the source
- Classification of the retrieved content
- Whether the write is durable or session-scoped
- Purpose declared for the retrieval
The gate
Restrict retrieval to what the actor is entitled to read, and refuse durable writes of classified content.
ALLOW
Retrieval proceeds within the actor's entitlement.
ESCALATE
A broader scope waits on the data owner.
BLOCK
The retrieval or the memory write does not happen.
Four stages left to right. Input signals — user or agent identity, context and data, tools and resources, spend and budget, policies, history and reputation, and environment — enter the Decionis Protocol. Inside, the protocol normalizes context and intent, evaluates policies and rules, runs a deterministic risk and policy engine, and explains the reason and evidence. It emits a verdict: ALLOW (authorized), ESCALATE (needs approval or more info), or BLOCK (high risk or out of policy). The verdict drives an enforcement action: allow, block, require approval, or throttle and limit. Every decision is recorded for audit, learning, and continuous improvement.
6 policies implement this pattern
Fork one and change the thresholds. Available today on 5 platforms.
LangChain Regulated-Data RAG Gate
Gates retrieval and external API calls that touch regulated records — restricted subjects never leave the boundary.
langchain
HIPAA-Grade Access Change Gate
Privileged-access and production-change controls for ServiceNow ITSM — proving every change followed the approved path.
servicenow
IT Ops Pack
Access, change, and procurement gates for internal automation — prove every sensitive change followed the approved path.
servicenow
SaaS Ops Pack
Cloud spend, discount, and entitlement gates — stop runaway burn, margin leakage, and unsupported entitlement changes.
sdk
Salesforce Regulated-Account Action Gate
Holds account changes on regulated or restricted customers until the right reviewer signs the record.
salesforce
Workday Offboarding Access Guard
When a termination event lands, prove access and payroll were actually revoked — not just ticketed.
workday
Related concepts
This pattern is one answer to each of these.
What to do next
The same five steps for every pattern in the library.
- 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.