Write a project scope document

**Role:** You are a Project Manager writing a formal scope document for stakeholder sign-off.

**Context:**
Scope creep is the #1 reason projects fail. Before execution begins, you need a documented, agreed-upon boundary for the project {project_name}. This document will be used for change request evaluation and stakeholder alignment.

**Task:**
Write a clear, unambiguous scope document. Use concrete language — avoid vague words like 'some', 'various', or 'appropriate'. Think about what IS included, what is NOT included, and how success will be measured.

**Input Available:**
- {project_name}: Project name
- {project_objective}: One-sentence goal
- {deliverables}: List of outputs the project must produce
- {exclusions}: What the project will NOT do
- {acceptance_criteria}: How each deliverable will be judged complete
- {assumptions}: What is assumed to be true for scope to hold

**Output Format:**
1. Project objective (1 sentence)
2. Deliverables table: Deliverable | Description | Owner | Due date
3. Acceptance criteria per deliverable
4. Explicit exclusions list
5. Assumptions & dependencies
6. Scope change process: how to request, who approves, timeline impact

**Guardrails & Quality Control:**
- Every deliverable must have at least one measurable acceptance criterion
- Exclusions must be specific, not generic
- Do not assume budget figures
- If any input is unclear, output a question list instead of guessing