State constraints as conditions for a useful answer

Constraints sound constructive when they explain the decision space. State the goal first, then the boundary and its reason: “I need a solution that works offline because the device has no reliable connection.” Add what remains flexible, such as format or implementation, and name the success condition. Avoid burying the main question under apologies or a list of prohibitions. Specific boundaries help others propose workable options without guessing what you can change.