Uses of Package
ai.badmonkey.agentspaces.api.security
Packages that use ai.badmonkey.agentspaces.api.security
Package
Description
The A2A gateway: mechanical translation of AgentSpaces
AgentCards to A2A agent cards, served over HTTP so A2A clients discover a
fleet through one standard surface.
The advertisement family: typed, TTL-bearing discovery documents and their signed wrapper (spec §6).
Extension points implementations plug into: transports, conflict strategies, membership validators, capability providers, schema registries, peer samplers.
The Layer 4 capability runtime: sign/publish/refresh CapabilityAdvertisements, discover providers, and multiplex direct capability frames (spec §8).
The aspace:cap/vote capability: auditable QUORUM ballots as space entries and
approximate MAJORITY_GOSSIP preferences over push-sum (spec §8).
The fleet console as a served surface (stability: API for
ConsoleView,
FleetConsoleServer, and the
ConsolePanel SPI).Layer 2 (spec §6): the signature-verifying, TTL-evicting advertisement cache
and local-first discovery with hop-budgeted remote queries.
Layer 0 (spec §4): peer identity with keystore persistence, PeerID derivation
from the Ed25519 public key, and advertisement signing.
Leased group membership with SWIM-style probing (spec §5.2).
The peer node and per-group runtimes: the assembly point of Layer 1 (spec §5).
The replicated space: the Space API over the delta-CRDT replica and gossip,
with LEASE_RACE take claims as a deterministic lattice (spec §7.3-§7.4).
Spring Boot autoconfiguration for AgentSpaces (spec §10.1): properties-driven
peer, group, and space wiring behind the fluent facade, with lifecycle-driven
ticking and annotation-driven bean enrollment.
-
Classes in ai.badmonkey.agentspaces.api.security used by ai.badmonkey.agentspaces.a2aClassDescriptionAuthenticates a bearer token presented to one of the fabric's HTTP surfaces (the fleet console's command routes, the A2A gateway's JSON-RPC surface) and names the principal behind it.
-
Classes in ai.badmonkey.agentspaces.api.security used by ai.badmonkey.agentspaces.api.adClassDescriptionThe peer vouches that a key belongs to one of its agents (spec §4.2, QA4 A4-7).
-
Classes in ai.badmonkey.agentspaces.api.security used by ai.badmonkey.agentspaces.api.securityClassDescriptionThe peer vouches that a key belongs to one of its agents (spec §4.2, QA4 A4-7).Authenticates a bearer token presented to one of the fabric's HTTP surfaces (the fleet console's command routes, the A2A gateway's JSON-RPC surface) and names the principal behind it.The authenticated holder of a bearer token.One group's accepted revocations as every enforcement point asks about them (SPEC §6.1, v0.1.13): peers by identity, and agents and agent keys under the freeze rule of
CredentialRevocation.One named security posture for a whole deployment (security remediation plan §4): an operator selects a profile and gets a coherent combination of transport, channel authentication, and authorization, rather than assembling individual flags and hoping they compose safely. -
Classes in ai.badmonkey.agentspaces.api.security used by ai.badmonkey.agentspaces.api.spiClassDescriptionThe peer vouches that a key belongs to one of its agents (spec §4.2, QA4 A4-7).
-
Classes in ai.badmonkey.agentspaces.api.security used by ai.badmonkey.agentspaces.auth.oidcClassDescriptionAuthenticates a bearer token presented to one of the fabric's HTTP surfaces (the fleet console's command routes, the A2A gateway's JSON-RPC surface) and names the principal behind it.The authenticated holder of a bearer token.
-
Classes in ai.badmonkey.agentspaces.api.security used by ai.badmonkey.agentspaces.capabilities.runtimeClassDescriptionOne group's accepted revocations as every enforcement point asks about them (SPEC §6.1, v0.1.13): peers by identity, and agents and agent keys under the freeze rule of
CredentialRevocation. -
Classes in ai.badmonkey.agentspaces.api.security used by ai.badmonkey.agentspaces.capabilities.voteClassDescriptionOne group's accepted revocations as every enforcement point asks about them (SPEC §6.1, v0.1.13): peers by identity, and agents and agent keys under the freeze rule of
CredentialRevocation. -
Classes in ai.badmonkey.agentspaces.api.security used by ai.badmonkey.agentspaces.consoleClassDescriptionAuthenticates a bearer token presented to one of the fabric's HTTP surfaces (the fleet console's command routes, the A2A gateway's JSON-RPC surface) and names the principal behind it.
-
Classes in ai.badmonkey.agentspaces.api.security used by ai.badmonkey.agentspaces.discoveryClassDescriptionOne group's accepted revocations as every enforcement point asks about them (SPEC §6.1, v0.1.13): peers by identity, and agents and agent keys under the freeze rule of
CredentialRevocation. -
Classes in ai.badmonkey.agentspaces.api.security used by ai.badmonkey.agentspaces.identityClassDescriptionThe peer vouches that a key belongs to one of its agents (spec §4.2, QA4 A4-7).
-
Classes in ai.badmonkey.agentspaces.api.security used by ai.badmonkey.agentspaces.peering.membershipClassDescriptionOne group's accepted revocations as every enforcement point asks about them (SPEC §6.1, v0.1.13): peers by identity, and agents and agent keys under the freeze rule of
CredentialRevocation. -
Classes in ai.badmonkey.agentspaces.api.security used by ai.badmonkey.agentspaces.peering.nodeClassDescriptionOne group's accepted revocations as every enforcement point asks about them (SPEC §6.1, v0.1.13): peers by identity, and agents and agent keys under the freeze rule of
CredentialRevocation. -
Classes in ai.badmonkey.agentspaces.api.security used by ai.badmonkey.agentspaces.space.replicatedClassDescriptionThe peer vouches that a key belongs to one of its agents (spec §4.2, QA4 A4-7).One group's accepted revocations as every enforcement point asks about them (SPEC §6.1, v0.1.13): peers by identity, and agents and agent keys under the freeze rule of
CredentialRevocation. -
Classes in ai.badmonkey.agentspaces.api.security used by ai.badmonkey.agentspaces.springClassDescriptionOne named security posture for a whole deployment (security remediation plan §4): an operator selects a profile and gets a coherent combination of transport, channel authentication, and authorization, rather than assembling individual flags and hoping they compose safely.