Under the objective Create effective system-level instructions (Domain 5: Configuration and Knowledge Management), engineering project-level system instructions follows a top-down operational framework.

Before authoring specific formatting rules, edge-case handlers, or role prompts, the author must first establish the high-level boundary architecture: defining the core objective and purpose of the Project, the target audience, and the explicit constraints/guardrails the model must respect (Option C). These foundational boundaries dictate what the model should do, what it must refuse or escalate, and how it must interact with attached reference knowledge. Attempting to validate instructions against test requests (Option B) or iteratively refine them (Option A) requires a drafted system prompt to exist first. Distributing instructions to team collaborators (Option D) is the final operational rollout step after validation is complete.