How STACK works

Most agent deployments today are assembled from several separate systems: an identity provider, a secrets manager, an API gateway, policy checks and logging. Those products can all perform their own function correctly without sharing a common view of the work the agent was authorised to do. A request may therefore be valid at the gateway, and a credential may be valid at the secrets manager, even though the action itself has moved beyond the original job.

STACK gives each agent a Passport that carries its permitted services and actions, with references to the work and authority behind them. For an automated fleet, an operator approves the available access once. Each Mission then requests the part needed for a particular job, and STACK issues a Passport within those limits. Credential use, runtime decisions and the resulting record stay connected while the agent works. The same records can be used to stop the work or reconstruct what happened.