Interop is its own section: sessions and the guests
who open them warrant different management from the HTN workloads (ness, 2026-08-26). The
relay already splits it — the gateway owns sessions and tessera; the Henge owns the
hospes holons those sessions cause.
This page is the protocol surface: which wires exist, who is on
them, and what work arrived through them. (The people and agents who arrive are the
guests, and their work lands on the hospes lane below — but the wire
itself is not "guests".)
| A2A | live | Point a client at http://ness-linux3:32180 (JSON-RPC; in-cluster
http://a2a-gateway.cortex.svc.cluster.local) — it discovers the rest
from the agent
card. Streaming + tessera extension. |
|---|---|---|
| OpenAI shim | live | For clients that only speak chat completions:
POST /v1/chat/completions on the same gateway, model
ipsa. |
| ACP | planned | Agent Client Protocol — what Zed speaks (it has no A2A). Same shape of conversation as A2A, different transport: the editor launches an agent process and talks JSON-RPC over stdio, so ipsa needs a thin local bridge binary that Zed spawns and which relays to this gateway. Sessions will be tracked here alongside A2A once it exists. |
Work arriving over any of these lands on the hospes lane
below. In this lane, hitl is usually healthy —
it is the ask-the-requester channel (A2A input-required), a conversation
with the guest, not a stuck task.
Live/total sessions come from the gateway (strip below); each session's work
lands on the hospes lane as holons — this is that lane, newest first.
What each guest may call (tessera grants) and the controls on them live on the gateway; the Henge shows the aggregates until the gateway enumerates per-guest detail.