Developer and model-facing operation description.
Named binary metadata contracts.
Named input contracts.
Registered operation name.
Named output contracts.
Output ports mapped to tool-result JSON fields.
Map an output into a JSON field, or $ as the whole result value.
Validate names, contracts, reserved ports, and output mappings.
StaticcreateConstruct and validate a schema before registering it.
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.