Set Constraints and Boundaries

Work through the explanation, apply it to the example, and complete the quick check before continuing.

Constraints define acceptable work

A constraint is a condition the result must follow.

Useful constraints may cover:

• Length or level of detail.
• Language and reading level.
• Required or forbidden content.
• Time period or geographic scope.
• Tools or sources that may be used.
• Privacy, confidentiality, copyright, or security limits.
• Actions the system may not take.
• Human approval required before use.

Constraints should serve a real purpose. A long list of arbitrary rules can create conflict and hide what matters.

Boundaries say where the task stops

Suppose the task is to draft questions for a staff survey.

A boundary might say:

Do not collect names, contact details, health information, or allegations about individuals. Do not publish or send the survey. Return a draft for the research lead to review.

The task creates a draft. It does not collect data or make a decision.

State what to do with uncertainty

Do not force the system to invent an answer.

Useful instructions include:

• Mark missing information as Not provided.
• Ask up to three clarification questions before drafting.
• Separate facts from assumptions.
• Stop if the sources disagree on a material detail.
• Do not calculate when a required value is absent.

These instructions make uncertainty visible.

Avoid impossible or conflicting constraints

This request conflicts with itself:

Explain every technical detail in no more than 50 words for a complete beginner.

The author must choose a priority or reduce the scope.

Another weak instruction is:

Be completely accurate.

Accuracy is a goal, not a method. Name the approved sources, checks, and reviewer.

Positive and negative boundaries

Negative instruction:

Do not be too technical.

Positive version:

Use everyday language. Define the terms model and training in one sentence each. Do not include equations or code.

Use positive guidance where possible, then add important exclusions.

Remember

• Constraints define acceptable work.
• Boundaries define where the task stops.
• Make missing information and conflicts visible.
• Replace vague wishes with sources, methods, and review.
• Keep the critical constraints clear and consistent.

Next, we will define the output so it can be inspected efficiently.