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.