Architecture

How AWARE is put together

This diagram is drawn from the shipped source, not from an aspiration. Where a component exists but is not wired into the running path, it is marked as such.

AWARE component architecture An agent issues a tool call to the gateway. The gateway proxies to the coordinator. The coordinator evaluates the call against the identity registry and the policy engine, which reads the policy store and tool catalogue. A decision is written to the audit chain, and revocation can invalidate an agent's credential. The kill switch can halt the gateway. Agenttool call Gatewaythin BFF — implemented Coordinatordecision routing Identity registryhash, rotate, revoke Policy enginedeny by default Policy storehot reload Tool cataloguerisk & data tier Kill switchgateway 503 Audit chain — hash-linked, independently verifiable ALLOW / DENY / AUDIT recorded, failures included Delegation graph roadmap Commit Guard roadmap
Solid outline and green fill mark components in the shipped runtime path. Dashed outline marks roadmap components that exist in the design but not in the code.

The request path

  1. The agent presents its credential and requests a tool call.
  2. The gateway validates the request, enforces the body-size limit, and proxies to the coordinator.
  3. The coordinator resolves the agent’s identity and asks the policy engine to evaluate the call.
  4. The engine checks tool known-ness and risk, the data tier, and any matching policy.
  5. The decision — ALLOW, DENY, AUDIT or NO_POLICY, with a reason — is written to the audit chain.
  6. Revocation can invalidate the agent’s credential at any point; the kill switch can halt the gateway entirely.
Deployment shapes AWARE ships Dockerfiles for the service, gateway, coordinator and training components, two compose topologies, a Kubernetes manifest and an nginx configuration for the operator UI. The operator UI is a React application served behind nginx, proxying /api to the v2 gateway.