Factory docs, home
Page navigation

See the input → responsibility → output diagram.

Status: Decoded subscription routing. Build review records accepted snapshots and current verification gates. Live client/contact qualification remains separate.

An authenticated server can list the available Branch health event, subscribe a callback or stop a subscription. This adapter routes those three requests to the existing private subscription host and returns only the public result. The caller supplies authentication, the host and transport. It never sends an application event or starts a server by itself.

A slim azure bob wearing a simple headset.

Meet the operator. Three methods, nothing more. Offers three decoded methods over the existing host, and nothing more. Meet the whole Plumb family.

A reply ID only connects a response to its original request. Repeating a subscription request can renew it; the same ID does not make that a replay. If a reply is lost, the adapter cannot safely infer that nothing happened. Closing a connection also does not cancel a verification already offered by the host. Late responses stay with their original request and session.

Honest limits:

  • The caller owns raw request parsing, current authentication, private storage/contact qualification, safe response correlation and quiet maintenance.
  • Generic metadata/progress support, a real MCP or ChatGPT client, public connector and application delivery remain unqualified.
  • Current source, installed-package and CI evidence is scoped in the build review; live-client qualification is separate.

Source: docs/guide/provider-events-rpc.md