Evaluate the intent
The local V12.6 engine checks identity, delegation, policy, destination, sensitivity and impact.
V12.7 · Agent Trust Gateway & Verified Execution
The gateway turns an eligible Intent Firewall decision into a short-lived execution permit that is bound to one verified agent, one audience and one exact payload.
Four guarded steps
Each step closes a different trust gap. A permit cannot silently change target, payload, identity or expiry after it is signed.
The local V12.6 engine checks identity, delegation, policy, destination, sensitivity and impact.
An eligible result becomes a signed, short-lived authorization with explicit restrictions.
The caller presents the one-time nonce, payload SHA-256, audience and idempotency key.
The gateway checks signature, binding, expiry, revocation, replay and use limits before returning allow or deny.
Permit anatomy
These fields make the authorization narrow, inspectable and unsuitable for reuse in another context.
Safety boundaries
Authorization is separated from execution so a website control plane never becomes an unrestricted remote-action system.
It never runs the requested agent action.
It rejects consumed, revoked and replayed permits.
It rejects payload or audience changes.
It rejects expired and overused permits.
It requires a verified identity and eligible intent decision.
It records privacy-safe, tamper-evident authorization evidence.
V12.8 · Nexus Trust Exchange
V12.8 adds the first bounded Nexus Trust Exchange above the execution gateway.