Encode decision constraints

Constraints answer whether a complete configuration is allowed under this decision’s actual conditions. They are not a substitute for compatibility. Use typed clauses with equals, not-equals, one-of, or none-of operators.

• Require checks that required selections are present.
• Exclude rejects configurations matching a forbidden pattern.
• Conditional applies a typed “when … then …” rule.
• Custom records advisory text and is never computationally hard.

A rule may be advisory or hard. Only an active, human-confirmed, executable hard rule can exclude. AI-proposed rules enter as advisory and unconfirmed; human confirmation is a separate action. Explain why the rule exists, cite its source, and review assumptions. Avoid encoding preferences as hard rules: “we prefer direct sales” belongs in evaluation, while “this channel is legally unavailable in the selected region” may be a constraint.