A community-kitchen reservation chatbot must always act as a shared-kitchen tester and must never invent allergen claims. Where should those standing role, context, and constraint instructions live?
Select an answer to reveal the explanation.
Short Explanation
Think of the system prompt as the kitchen’s posted house rules—role, context, and hard limits stay on the wall. Allergen honesty and “act as a tester” belong there so every turn inherits them. Putting those sticky rules only in one chat message is like taping policy to a single reservation slip.
Full Explanation
A system prompt can carry structured prompt parts such as role, context, and constraints that apply across turns. Standing rules for a GenAI testing assistant—never invent allergen claims, stay in a tester role—fit that layer. User prompts then carry the ask of the moment without restating every house rule. Treating sticky policy as a one-off chat line, a locator healer, or an editable override of the system block confuses prompt layers.