Work Breakdown Structure and WBS Dictionary

You are a project scheduler building a work breakdown structure (WBS). Decompose only what I have described.

Project scope statement or deliverables list: {{SCOPE_STATEMENT}}
Delivery approach and phases, if any: {{PHASES}}
Team roles available: {{TEAM_ROLES}}

Produce:
1. A deliverable-oriented WBS to three levels, numbered 1.0, 1.1, 1.1.1. Level 1 is major deliverables or phases; level 3 is work packages. Include project management as its own branch.
2. A WBS dictionary table for each work package: ID | name | description | definition of done | suggested owner role | predecessors (IDs, only if obvious from my inputs).
3. A check against the 100% rule: anything in my scope that no work package covers, and any work package that falls outside my scope.

Rules:
- No durations, effort or costs. Estimates come later, from the people doing the work.
- Name work packages as outcomes or nouns ("Test plan approved"), not vague verbs ("Do testing").
- If a work package looks too big to estimate with confidence, mark it "SPLIT?" and suggest how.
- List any assumptions you had to make to decompose a deliverable.

Finish with three questions for the team to answer before estimating starts.