WriteTarget#

class ansys.fluent.mcp.solve.lib.active_path.WriteTarget#

Canonical resolution of “where should a write to requested_path land”.

The three consumers of active-path knowledge (the validator’s inactive_path diagnostic, the resolve_active_path tool surfaced to clients, and the recipe URF stagers) historically each maintained their OWN version of the classify → reroute → fetch-alternate-path pipeline. That triplication is the reason the same live case could produce three DIFFERENT answers for “where does this URF write actually go” — the validator said inactive_path, the tool said “no reroute needed”, and the recipe went ahead and wrote the wrong family.

resolve_write_target() is the single deterministic resolver they all consult. The result carries:

  • requested_path — the input, verbatim.

  • active_path — the correct path to write under mode, which equals requested_path when the input is already active (needs_reroute=False).

  • needs_reroute — True iff active_path != requested_path.

  • group / active_family — for messaging and telemetry.

  • reason — short human-readable explanation suitable for a

    validator diagnostic and the client-facing tool response.

  • classified — True iff the requested path was recognized as belonging to a known multi-path class. When False, the resolver is conservative: it returns needs_reroute=False and active_path=requested_path so an ordinary write is never false-blocked.

Overview#

requested_path

active_path

needs_reroute

group

active_family

reason

classified

Import detail#

from ansys.fluent.mcp.solve.lib.active_path import WriteTarget

Attribute detail#

WriteTarget.requested_path: str#
WriteTarget.active_path: str#
WriteTarget.needs_reroute: bool#
WriteTarget.group: str | None = None#
WriteTarget.active_family: str | None = None#
WriteTarget.reason: str = ''#
WriteTarget.classified: bool = False#