A schema is the stable boundary between callers and handlers: it names the
operation, defines input/output AsyncNodes, declares metadata headers, and
optionally maps outputs into an LLM/tool JSON result. Registries use the
schema to instantiate local handlers. A remote call sends the action name
and port mappings, not this schema; the peer resolves its own registration,
so caller and receiver schemas must agree on the wire-facing contract.
Typed port and header contract for an Action.
A schema is the stable boundary between callers and handlers: it names the operation, defines input/output AsyncNodes, declares metadata headers, and optionally maps outputs into an LLM/tool JSON result. Registries use the schema to instantiate local handlers. A remote call sends the action name and port mappings, not this schema; the peer resolves its own registration, so caller and receiver schemas must agree on the wire-facing contract.