Verify the participant
Resolve identity information and check the evidence required by the application. Authentication should be bound to the request and its intended recipient.
Identity and authorization
Ask who. Then ask what they may do.
Aegis connects identity verification to authorization decisions. Build services that inspect the participant, its authority, and the policy for the requested action.
AegisIllustrated study
Defined scope / checked / bounded
A permission is a condition, not a blank cheque.
Aegis
01 / Built for a purpose
A signature is the beginning of a decision.
Recognizing a key is different from granting access. Aegis brings identity, challenge-response authentication, lineage checks, and policy evaluation into the service boundary where a request is handled.
Inspect the authority
Root and lineage information help a verifier understand the relationship behind an agent. Relevant revocation and network activation checks remain part of the decision.
Evaluate the action
Policies decide whether this participant can perform this action on this resource. Identity alone should not become blanket permission.
Keep the boundary explicit
Aegis is a verification and authorization framework. It works with credentials and chain records; it is not a replacement for the chain executor.
Keep exploringOne capability.