06Questions
Questions owners ask before they call
Plain answers, in the order owners ask them. Each answer stands alone, so you can quote it.
What is an agent execution boundary?
An agent execution boundary is the layer between an AI agent's decision and its action. Before the action runs, it returns 1 of 3 signed answers: allow, deny or escalate. The answer is recorded by something other than the agent, so later you can show what the agent was cleared to do.
What is TrustGate?
TrustGate, from Cyber Warrior Network, is an agent execution boundary. TrustGate returns a signed allow, deny or escalate decision before the action runs, for actions that go through it. An outcome we cannot confirm is reported as unknown, never as success.
How is this different from logs and observability?
Logs are the agent's own account. They are useful, and sometimes they are enough. A boundary adds a decision recorded before the action, in a record the agent does not write. If your logs already settle it for your auditor, you do not need us.
Does it stop an agent from doing something?
A signed decision shows what was cleared. It is as strong as the paths you route through it. Signatures prove and detect. They do not prevent.
What happens when the result cannot be confirmed?
It is reported as unknown, never as success. TrustGate also keeps 'could not check' apart from 'checked and found nothing', because they mean different things.
What does a decision record contain?
The receipt binds the agent, action, target and exact arguments that were evaluated. It records whether approval was asserted. It does not prove who approved.
How are decisions signed?
Every decision receipt is Ed25519-signed; production also adds an ML-DSA-65 (FIPS 204) co-signature. Public keys are published at /.well-known/did.json. Not every earlier receipt was signed under a published key.
Does TrustGate make us compliant or insurable?
No. TrustGate does not certify compliance, give legal or audit opinions, or lower a premium. It produces a record you can show.
If an agent causes harm, can the company blame the agent?
Not in California. Since January 1, 2026, Civil Code section 1714.46(b) says it “shall not be a defense, and the defendant may not assert, that the artificial intelligence autonomously caused the harm to the plaintiff.” The UK data regulator says agents are not legal entities. This is a quote of public sources, not legal advice.
Who is this for?
The person who owns a workflow where an AI agent acts, and the people who must sign off: risk, audit, security, claims and program owners. It is not for anyone looking for a certificate or a lower premium.
Who is it not for?
Teams whose own logs already settle it for their auditor. Anyone who wants a certificate, a lower premium or another dashboard to watch. Anyone with no agent near release. Anyone who expects a signature alone to stop an agent.
What happens on the call?
You describe 1 workflow where an agent acts. We ask what shows it worked and who signs. Afterwards you keep a 1-page recap of what you told us. It is free. Nothing in it is checked against your systems, and it is not a rating.
What does it cost?
TrustGate starts with a fixed-fee engagement. The price, the payment schedule and what is included are on the pricing page.
Is there an MCP server?
An MCP server exposing gate_decision, verify_receipt and check_policy. Install the package: pip install trust-gate-mcp.
Who builds TrustGate?
Cyber Warrior Network. Write to [email protected] or bring us a workflow.
Sources
Each source was read on October 2, 2026. Wording in quotation marks is exact; the rest is paraphrase.
- California Civil Code section 1714.46 · California Legislative Information · Effective 2026-01-01 (added by AB 316, Stats. 2025, Ch. 672)
- UK Information Commissioner's Office, Tech Futures: Agentic AI, data protection and privacy risks · UK Information Commissioner's Office · No publication date shown on the page