vllm-omni/docs/design/module/omni_connector.md

title, kind, status, owners, primary_code_paths, related_code_paths, depends_on, validation_paths, upstream_refs, last_reviewed

title	kind	status	owners	primary_code_paths	related_code_paths	depends_on	validation_paths	upstream_refs	last_reviewed
OmniConnector	module	draft	@princepride @yuanheng-zhao @xuechendi @natureofnature @fake0fan	vllm_omni/distributed/omni_connectors/**	vllm_omni/platforms/*/omni_connectors/**	input_output_modality_contracts.md vllm_omni_config.md	tests/distributed/omni_connectors/**	vllm.distributed	2026-07-16

OmniConnector

OmniConnector defines model-agnostic transport and synchronization contracts for data exchanged across stages, processes, devices, and nodes.

Candidate invariants

CONNECTOR-INV-001: Connectors transport but do not route

Rule: A connector MUST NOT select the next stage or implement model-specific execution policy.

CONNECTOR-INV-002: Producer and consumer contracts agree

Rule: Both ends MUST agree on data identity, shape, dtype, placement, ownership, and completion semantics.

CONNECTOR-INV-003: Resources have deterministic cleanup

Rule: Connections, buffers, handles, and background work MUST be released on normal completion, cancellation, failure, and shutdown.

Safe-change guide

Test setup, transfer, synchronization, timeout, cancellation, failure, and cleanup across every affected backend.