Policy Enforcement
How Nomiqon validates spend requests synchronously at the gateway.
Runtime
Nomiqon enforces policies at the gateway edge, before any outbound transaction is initiated. Enforcement is synchronous and adds <8 ms median latency to the spend-token validation path.
Enforcement sequence diagram
plaintextnomiqon.com
Agent SDK / API client
│
│ POST /v1/spend/authorise
│ { agentId, amount, recipient }
▼
┌─────────────────────────────────────┐
│ Nomiqon Gateway │
│ 1. Verify spend-token signature │
│ 2. Load agent policy (cached) │
│ 3. Run evaluation chain (≤8ms) │
│ 4. Debit committed balance │
│ 5. Return authorised spend receipt │
└─────────────────────────────────────┘
│
▼
Agent initiates external API call
│
▼
Nomiqon Ledger Service
↳ on receipt confirmation: settle on Solana
↳ on timeout (60s): void committed amountKill switch
Setting frozen: true on a policy halts all spends for that agent in under 100 ms globally. Useful for incident response.
typescriptnomiqon.com
// Emergency halt — all subsequent spend requests return 403 agent_frozen
await nomiqon.agents.update(agentId, { policy: { frozen: true } });
// Resume
await nomiqon.agents.update(agentId, { policy: { frozen: false } });