Platform

Revocation

The moment an agent is compromised, the credential it holds must stop working. Not eventually, and not after a cache expiry window you forgot to set.

What happens on revoke

  1. The agent’s state flips, so its credential no longer verifies.
  2. A blast-radius penalty is applied to its trail, so it is deprioritised in scoring.
  3. The decision is written to the audit trail.

Emergency control

For a whole-service stop, the gateway honours AWARE_GATEWAY_KILL_SWITCH=1 and returns 503 immediately. For a coordinated stop across nodes, AWARE ships Raft-based kill-signal propagation and leader-election components, with a leader-only guard on propagation.

Cascade is not implemented Revoking a parent does not currently revoke its children. The revocation service applies to exactly one agent. The blast-radius logic applies a penalty to that same agent rather than traversing to derived agents. An earlier version of the AWARE README said otherwise; it was corrected in release 2.12.2 because the source did not support it.
Component, not distributed guarantee The Raft propagation and election code is implemented and tested as components, but the running service constructs the revocation service marked pending Raft setup. Treat multi-node propagation as an integration you would complete, not a property you switch on.