Architecture

AWARE’s request path, from the agent to the recorded decision.

  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. It is deliberately a thin BFF.
  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 level, the data tier, and any matching policy in the policy store. The tool catalogue supplies risk levels and data-tier permissions.
  5. The decision — ALLOW, DENY, AUDIT or NO_POLICY, with a reason — is written to the audit chain.

Components

ModulePathResponsibility
Policy enginesrc/policies/engine.jsDecision logic. Default deny.
Tool cataloguesrc/policies/tool-catalog.jsRisk levels, approval requirements, data-tier permissions.
Policy storesrc/policies/store.jsPolicy persistence and hot reload.
Identitysrc/api/models/Agent.js, src/agents/registry.jsCredentials, hashing, rotation, state.
Sessionssrc/agents/identity-provider-v2.jsJWT sessions with trust-domain claims.
Revocationsrc/kill-switch/revocation-service.jsRevoke an agent; apply blast radius.
Emergencysrc/emergency/Kill-signal propagation, shutdown control.
Auditsrc/audit/, src/disclosure/Hash chain, verifier, exportable windows.
Compliancesrc/compliance/framework-mapper.jsFramework and control mapping.
Gatewaysrc/gateway/server.jsThin BFF, kill switch, body limit.