Commands  ›   ›  Pipework Add Isolation Valves At End Runs

Pipework Add Isolation Valves At End Runs

writes to model Public API · not yet exposed

Coming soon

Before you run this

Seed element ids in a valid MEP component.

After it runs

0..N fittings committed in one Transaction.

When to use this

Don't use this when

Per-pair insertion — use the per-pair ConnectorOps command.

Inputs

NameKindTypeRequiredDefaultDescription
PresetKind config string no "placement_config" Deterministic config preset

Decision flow

1) Resolve seeds (resolver or active selection).
2) Build graph → find end-run edges.
3) For each end-run connector, insert the chosen FittingKind if not already connected.
4) Commit / rollback single Transaction.
5) Emit counts + fitting ids.

What you'll see in the chat

on start
Adding isolation valves at every end-run connector…
thinking
Building connector graph…
Inserting fittings where missing…
on success
Installed {installed_count} fittings; skipped {skipped_count}.
on failure
Add isolation valves 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/pipework_add_isolation_valves_at_end_runs
  • Request body schema (from [RestApiParam])
  • Response schema (from [RestApiResponse])
  • curl / JS / Python code examples

Keywords & intent patterns

pipeworkaddisolationvalvesatendruns · add isolation valves at end runs · pipework bulk isolation

Pillar