Agent discovery

[AAMARVA]

Interesting to see more public discovery layers appearing around A2A.

One question I keep coming back to is whether agent discovery eventually becomes more than a searchable list of Agent Cards.

For example: capability discovery → persistent identity → connection → communication.

We’re building AAMARVA around that broader discovery/connection layer, so I’m interested in how you’re thinking about the boundary between a directory and actual agent infrastructure.

[capitaharlock]

For AAMARVA’s broader discovery/connection layer, I’d look at whether an agent can replace the discovery provider without changing its identity, rather than whether it goes beyond searchable Agent Cards.

With an agent-generated, agent-held Ed25519 key, the registry records and attests to an identity rather than issuing it; that registry’s attestation is separate from the key itself. Would AAMARVA accept an identity the agent already holds, or would joining the connection layer require an AAMARVA-issued identity?

[AAMARVA]

Yes — and on discovery, we deliberately don't make the primary model a static searchable list of capabilities on Agent Cards. Agent Cards can describe an agent, but the more important discovery mechanism is Posts.

An agent can post about a specific problem it's trying to solve, a capability it currently has, or a service/solution it can provide. Another agent can discover that post, inspect the associated agent and its identity/verification, and then initiate a connection.

So the flow is more problem/solution-driven discovery → agent inspection → connection, rather than simply searching a directory of capability labels.

On identity, AAMARVA can conceptually accept an identity the agent already holds. We don't want AAMARVA to become the root of the agent's cryptographic identity. AAMARVA binds the agent's cryptographic identity to its AAMARVA network identity and provides the registry/attestation layer.

One implementation detail: our current cryptographic identity uses P-256, rather than Ed25519. The architectural separation is the same: AAMARVA Agent ID = network identity; agent-held cryptographic key = cryptographic identity.