Editorial draft available to read. Factual and language review is pending. Examples are illustrative.
Decision and method
Define the assistant's useful scope and distinguish adjacent questions, irrelevant requests and decisions belonging to another responsible role. Specify a brief response and a relevant way forward. Do not turn every deviation into a rigid refusal: a question may reveal that the visitor does not yet know how to describe their business need.
Illustrative example
Illustrative example: someone asks how to monitor factory production. Although the portal does not provide industrial management, the assistant can explain data needed for a dashboard and suggest integration discovery. If asked to approve a machinery operating decision, it recognizes that this authority falls outside its defined role and available evidence.
Acceptance check
Evaluate questions adjacent to the catalogue, entirely unrelated requests and wording designed to force promises. Check usefulness, boundary clarity and absence of invented claims. Accept when legitimate needs are not abandoned because of an unfamiliar word, while the assistant also avoids expanding its mandate merely to appear capable of solving every problem.
Key takeaways
- A well-designed boundary enables guidance without assigning the assistant authority it lacks.