Skip to main content

Module capability

Module capability 

Source
Expand description

Capability bits advertised by agents in their JWS-signed agent card.

Per ADR-0018, new protocol features ship as capability bits — not as breaking wire-format bumps. An agent declares what it supports; senders pick the highest mutually-supported feature at negotiation time.

The bit-vector representation lets agent cards stay small while keeping room for ~64 future capabilities. A new capability is added by introducing a variant here; the variant’s as_bit() discriminant must never be reused or renumbered — capability bits are part of the signed card payload and any reuse breaks historical signatures.

§Serialization

On the wire (inside JWS-signed agent cards), a CapabilitySet is serialized as a JSON array of capability string names (not bit positions) — see to_string_array / from_string_array. This keeps cards human-readable and lets future readers ignore unknown capabilities forward-compatibly.

Structs§

CapabilitySet
Bitset of advertised capabilities.

Enums§

Capability
A protocol capability advertised by an agent.