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 ...

The aspace:cap/content-swarm capability (srad/large-networks-bulk-data.md): a signed manifest names a large artifact by the root of its pieces, leased holdings make the replicated space the provider index, and pieces move over capability ...

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 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 ...