The backend.py module#
Summary#
Common interface for all backends. |
Description#
Backend abstraction.
Every leaf has one or more backends. A backend is the thing that actually talks to a Fluids product (Fluent solver, Fluent meshing, Discovery, Prime, or the Fluids One service). Tools are MCP-client-facing; backends are implementation-facing.
A backend implements only the operations its product supports. Unsupported operations raise BackendUnavailableError so the typed-error guard converts them to a clean error code instead of a 500.