Ecosystem review / A2A
A2A: review and next steps
Internal principal-to-principal communication and external A2A interoperability solve different problems. Both matter, but a locally accepted request must not be mistaken for a completed remote task or a standards-compatible external interaction.
What the evidence supports
The reviewed records describe delivered bridge intake and a successor arrival-wake packet. That successor explicitly leaves automatic completion replies and live cross-principal acceptance outstanding. A separate DzupAgent admission scopes external protocol work and preserves deliberate legacy compatibility.
Reevaluation: Arrival wake and completion reply are separate milestones. Treat the existing wake and interoperability packets as owned work, not fresh unassigned features.
The next useful outcome
One principal sends a request, the recipient executes within its authority, and the sender receives one correlated terminal reply without manual copy/paste.
Separate workstream plan
A2A-01 · Proposed / reuse existing work
Qualify delivered intake on hosts
Verify the installed intake and arrival-wake route against the current owner and executable.
Acceptance: A valid request reaches the intended recipient and duplicate delivery remains idempotent.
A2A-02 · Proposed / reuse existing work
Close the terminal reply loop
Finish the existing request lifecycle so recipient completion is correlated back to the sender.
Acceptance: Wake, execution, reply and sender settlement share the same request identity.
A2A-03 · Proposed / reuse existing work
Qualify shared enforcement
Exercise shared PostgreSQL coordination, cross-principal obligations and fencing.
Acceptance: Identity and lease checks reject cross-principal authority leakage.
A2A-04 · Proposed / reuse existing work
Accept the selected external dialect
Reuse the current interoperability packet and independently verify its selected modern protocol contract.
Acceptance: Version, authentication, errors, task state and streaming behavior pass the stated independent-client tests.
A2A-05 · Proposed / reuse existing work
Exercise cross-host recovery
Test interruption, retry, duplicate request and bounded terminal recovery across hosts.
Acceptance: No duplicate accepted effect or silently abandoned request remains after recovery.
Dependencies and sequence
Principal identity, shared coordination enforcement, recipient supervision and qualified adapter routes.
Start with the first eligible unfinished task above, after checking its existing owner and admission. Later tasks depend on the preceding proof where applicable; this ordering does not override a current implementation plan.
Deferred work
Unselected protocol versions and transport variants until the chosen contract and internal completion loop pass.
Evidence and updates
This article combines the supplied 8 November ecosystem review with selected current source and retained planning records. It is an editorial snapshot, not a live service census. Detailed revision bindings and task authority remain in Workspace Docs and private execution records. Publish subsequent accepted changes as linked engineering or release notes rather than silently rewriting this baseline.
