Commands  ›   ›  Connector Ops Connect Into Nearest Terminal Via Flex

Connector Ops Connect Into Nearest Terminal Via Flex

writes to model Public API · not yet exposed

Coming soon

Before you run this

Active document; source + terminal resolvable; same Domain; both connectors currently unconnected.

After it runs

Exactly one FlexDuct or FlexPipe created inside one Transaction.

When to use this

Don't use this when

Rigid pipe runs — use the 3D or 2D connect commands.

Decision flow

1) source unique id + terminal unique id required.
2) Resolve source + terminal elements + pick one unconnected connector each (by Resolver_*ConnectorId or single-unconnected rule).
3) MatchSystemByName.Evaluate on the pair; abort if Abort.
4) Build 4-point waypoints: source.Origin, source.Origin + source.BasisZ * stub, terminal.Origin - terminal.BasisZ * stub, terminal.Origin.
5) Transaction "ConnectorOps::FlexTerminal"; per Domain, call FlexDuct.Create / FlexPipe.Create with waypoints and type defaults. Commit on success.
6) Emit flex_element_id, length_mm, waypoints_ft.

What you'll see in the chat

on start
Routing flex between source and nearest terminal…
thinking
Resolving both elements + connectors…
Building 4-point flex waypoints…
Creating FlexDuct or FlexPipe…
on success
Flex created, id={flex_element_id} length={length_mm} mm.
on failure
Flex terminal connect failed: {error}

REST API

Not yet exposed

This command does not carry a [RestApi] attribute today. Once tagged, this section will auto-populate with:

  • POST /api/v1/commands/connector_ops_connect_into_nearest_terminal_via_flex
  • Request body schema (from [RestApiParam])
  • Response schema (from [RestApiResponse])
  • curl / JS / Python code examples

Keywords & intent patterns

connectoropsconnectintonearestterminalviaflex · flex terminal connect · grille link via flex

Pillar