-
Notifications
You must be signed in to change notification settings - Fork 1
Build A2A-to-LDP bridge example #9
Copy link
Copy link
Open
Labels
exampleUsage examples and tutorialsUsage examples and tutorialsprotocolProtocol specification changesProtocol specification changes
Description
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
A2aLdpBridgeclass 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
- A2A protocol: https://github.com/a2aproject/A2A
- A2A Python SDK: https://github.com/a2aproject/a2a-python
- LDP delegate base class:
sdk/python/src/ldp_protocol/delegate.py
Acceptance criteria
- Bridge wraps a real or simulated A2A agent
- LDP identity card includes quality scores, model family, cost hints
- Provenance is attached to every result
- README with setup and run instructions
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
exampleUsage examples and tutorialsUsage examples and tutorialsprotocolProtocol specification changesProtocol specification changes