Skip to main content

ADR-0012: Place remote invocation behind a WIT-native transport abstraction

  • Status: Accepted
  • Date: 2026-08-17

Current implementation​

All six client SDKs use the authenticated standalone invocation and management APIs. Guest-to-guest calls resolve within the same node under conserved authority, deadlines and budgets. Cross-node service routing and cluster identity remain planned; the external client listener does not implement that transport.

Context​

Local and remote bindings need equivalent typed semantics without freezing the runtime to one network library.

Decision​

Define RemoteInvocationClient, RemoteInvocationServer, and wire seams suitable for wRPC-like transports.

Consequences​

Transport implementation and broker topology remain open while identity, deadline, budget, and revision pinning are mandatory.