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.
The request path
- The agent presents its credential and requests a tool call.
- The gateway validates the request, enforces the body-size limit, and proxies to the coordinator.
- The coordinator resolves the agent’s identity and asks the policy engine to evaluate the call.
- The engine checks tool known-ness and risk, the data tier, and any matching policy.
- The decision — ALLOW, DENY, AUDIT or NO_POLICY, with a reason — is written to the audit chain.
- 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.