Summary
LDP positions itself as complementary to A2A. The strongest proof of that is a working bridge that wraps an A2A agent with LDP identity and provenance — showing the two protocols working together.
What to do
- Create
examples/a2a_bridge/ with a Python implementation
- Build an
A2aLdpBridge class that:
- Wraps an existing A2A agent endpoint
- Serves LDP identity card at
/ldp/identity (enriching A2A's Agent Card with quality scores, model family, etc.)
- Proxies task submissions through LDP session management
- Attaches provenance metadata to A2A task results
- Include a README showing how to run it
Architecture
The A2A agent doesn't need modification. The bridge adds LDP's delegation intelligence on top:
- Client speaks LDP to the bridge
- Bridge translates to A2A for the downstream agent
- Bridge attaches provenance + identity metadata on the way back
Why this matters
This is the single most important demo for LDP's strategy. It proves LDP and A2A are complementary, not competing. Framework builders and A2A community members need to see this working.
References
Acceptance criteria
Summary
LDP positions itself as complementary to A2A. The strongest proof of that is a working bridge that wraps an A2A agent with LDP identity and provenance — showing the two protocols working together.
What to do
examples/a2a_bridge/with a Python implementationA2aLdpBridgeclass that:/ldp/identity(enriching A2A's Agent Card with quality scores, model family, etc.)Architecture
The A2A agent doesn't need modification. The bridge adds LDP's delegation intelligence on top:
Why this matters
This is the single most important demo for LDP's strategy. It proves LDP and A2A are complementary, not competing. Framework builders and A2A community members need to see this working.
References
sdk/python/src/ldp_protocol/delegate.pyAcceptance criteria