Group: Badmonkey Agentspaces

Sort by:Popular▼

✓Popular✓Newest

Testing utilities shared by all modules and by applications: a mutable TestClock, the SimNetwork deterministic in-memory transport fabric with partition control, and common test fixtures.

Shared foundations: hybrid logical clocks, identifiers and the aspace URI scheme, Base58/multibase encoding, the canonical CBOR codec, and Ed25519 crypto helpers.

The public API and SPI: the Space interface and template DSL, leases, entry records, the advertisement family, and the extension points implementations plug into. Applications program against this module; implementation modules stay ...

Layer 0 of the spec: Ed25519 peer identity with keystore persistence, PeerID derivation, message signing and verification, and advertisement signing.

Layer 1 of the spec: signed CBOR wire envelopes, peer nodes with per-group runtimes, leased membership with SWIM-style ping and indirect ping-req, the two-channel gossip bus (rumor plus anti-entropy), and the TCP reference transport.

Layer 3 of the spec: the AgentSpace tuple space. Ships LocalSpace, a complete single-JVM implementation of the Space API with leases and notifications, plus the delta-CRDT core (OR-Set entry state, LWW lease registers) on which the ...

The framework-neutral annotation model and binder: @SpaceTake, @SpaceNotify, and @BidFunction on plain objects, virtual-thread worker loops with crash-equals-lease-lapse semantics, and automatic AgentCards generated from annotations and ...

Layer 4 of the spec: the capability-service runtime (publish, refresh, and discover CapabilityAdvertisements) and the shipped capabilities: push-sum aggregate, vote, the ordered-log (Raft) coordinator behind ORDERED takes, ...

Spring Boot autoconfiguration for AgentSpaces: properties-driven peer, group, and space wiring, a SmartLifecycle for ticking and card refresh, and a bean post-processor that binds annotated agent beans. Compiles against the provided-scope ...

Layer 2 of the spec: the signature-verifying, TTL-evicting advertisement cache fed by gossip, local-first find, and hop-budgeted remote queries.

Locators that find a beacon through the enterprise's own directory: a DNS name with several addresses, SRV, DNS-SD under the network's domain, a TXT pointer, a well-known HTTPS beacon document, a Kubernetes headless service; the ...

The open connector SDK behind the AssetCard model (ENTERPRISE §6, COMPETITIVE §7 boundary: the SPI and protocol stay Apache 2 so anyone can build a connector; the finished enterprise connectors and the console are the commercial layer). ...

The fleet console as a served surface: a read-only observability peer presenting membership, discovery, and space state over HTTP. A HAL+JSON API (application/hal+json links, Spring HATEOAS compatible), a Server-Sent Events activity ...

The pieces every attesting transport binding shares (spec §5.6): one key manager that serves the channel credential, one trust manager that defers the trust decision to attestation, and one attestation call over a presented chain. The tls ...

A peer in plain Java from the agentspaces.* configuration the Spring Boot starter and the Micronaut library read, with the lifecycle, a fleet context, participants, take propagation across threads, and the framework-neutral tool catalogue ...

The HTTP bindings of the Transport SPI (spec §5.5, SRAD srad/agentspaces-js.md §3.3): ws and wss (RFC 6455, one binary message per frame, subprotocol aspace.1) and the http and https request and response exchange (appendix C), on Netty's ...

Translates AgentSpaces AgentCards to A2A agent cards and serves them over HTTP, so A2A clients can discover a fleet's agents through one gateway.

The OidcAuthorizer (security remediation plan §6): privileged-operation authorization deferred to JWT scopes minted by the organization's identity provider, validated with Nimbus JOSE+JWT against a cached JWKS. Optional: fleets on the ...

Micronaut beans for AgentSpaces: the fabric from agentspaces.* properties, annotated beans enrolled as AgentCards, AssetProvider beans and the embedded server served as AssetCards, a fleet-backed DiscoveryClient, health, info, and ...

The wire records of the fleet model service, chat memory snapshots, and usage entries: plain Java with no framework type, in the package the space names them by, so a Spring AI peer and a Micronaut LangChain4j peer serve each other's ...