Connection Routes¶

Supported outbound nodes and connectors can choose how SchemAlign reaches their destination.

A Connection Route is typically either:

Direct
SchemaDock: <Dock Name>

Direct¶

Use Direct when the destination is reachable from the normal SchemAlign execution environment.

SchemaDock¶

Select a named SchemaDock when the destination must be reached through that Dock's private network.

Before execution, SchemAlign validates that the selected Dock is enrolled, enabled, authorized for the pipeline organization, online, and permitted to reach the requested destination.

If validation fails, the node fails.

No silent fallback

A node configured for SchemaDock does not silently retry through Direct. This preserves the intended network and security boundary.

Current built-in support¶

Node	Connection Route
HTTP Get	Direct or authorized SchemaDock
Ethos Get	Direct or authorized SchemaDock
File Get	Direct or authorized SchemaDock
File Put	Direct or authorized SchemaDock

Installed outbound Extend Source connectors can also use SchemaDock when the connector configuration exposes the SchemAlign-owned Connection Route capability.

Intentionally unsupported steps¶

SchemaDock is not used for internal transformation or inbound-response behavior.

Step	Why SchemaDock is not used
SQL Loader	Internal Compose/data transformation behavior.
SQL Transform	Internal Compose/data transformation behavior.
Inbound HTTP Request / API trigger	Inbound request handling is SchemAlign functionality, not outbound customer-network connectivity.
HTTP Response	Returns a response to an inbound caller; it is not a private-network destination dial.

A stale or tampered schemadock_id does not turn an unsupported/internal node into a SchemaDock-routed step.

Extend connectors¶

SchemaDock transport is provided beneath the governed Extend runtime boundary.

Connector code continues to execute in the SchemAlign isolated connector runtime. SchemaDock does not receive or execute the connector source code.

For an outbound Extend Source connector, the path is conceptually:

isolated connector runtime in SchemAlign
        -> SchemaDock transport
        -> private destination