Question: json-render interoperability with Google A2UI (agent-to-UI protocol)

Hi json-render team — thanks for open-sourcing this project.

I’m currently evaluating different “AI → JSON → UI” approaches, and I came across both vercel-labs/json-render and google/a2ui (Agent-to-User Interface). I’m not an A2UI maintainer, but I’m trying to understand how these two efforts relate and whether there’s a sensible interoperability path.

From what I can tell, there’s conceptual overlap:

• constrained component catalog / guardrails
• JSON-driven UI generation
• actions + data binding
• streaming/progressive rendering

A2UI seems to emphasize a standardized streaming protocol (createSurface, updateComponents, updateDataModel, deleteSurface) and cross-framework portability, while json-render appears to focus on a React renderer + catalog/schema constraints.

Questions

1. Are you aware of A2UI? Is there any intended relationship (inspiration, planned alignment, or intentionally different direction)?
2. Would you be open to (or already planning) an interoperability layer, e.g.:
   • accept A2UI messages as an input format (adapter/translator), or
   • provide guidance / examples on mapping between the formats?
3. How do you see the long-term status of json-render’s JSON format:
   • is it intended to be a “protocol” others build against, or mainly an internal library API?
4. Any tips on mapping between:
   • A2UI-style JSON Pointer bindings vs json-render valuePath bindings,
   • A2UI action dispatch vs json-render action handling (confirm/onSuccess/onError)?

References:

• json-render: https://github.com/vercel-labs/json-render
• A2UI: https://github.com/google/a2ui

Thanks — any direction would help me choose the right approach.