- Prefer completing a workflow with the user's supplied values over rejecting

them because they fall outside recommended, UI-advertised, or quality-oriented

limits. If the downstream implementation can consume an input, pass it

through unchanged even when the result may be poor. For example, do not reject

or truncate additional reference images merely because a node advertises a

smaller recommended maximum.

- Do not add validation errors solely to prevent degraded, nonsensical, or

low-quality model output. A bad result is preferable to failing an otherwise

executable workflow.

- Resize, pad, clamp, normalize, or otherwise adapt user input only when passing

it through unchanged would make the existing model or underlying operation

fail. Make the smallest adjustment needed to keep execution running; do not

add a model-level validation failure merely to justify changing the input.

- This permissive policy does not override security boundaries such as path

containment, or integrity checks required to load model formats and

checkpoints safely.