# Suite Boundary Decision Template

Use this artifact to capture the suite-shaping decision before pack scaffolding. Prefer the smallest clean suite that still preserves clean ownership and implementability.

## Recommended suite

| Field | Value |
| --- | --- |
| Recommended suite size | `<count>` |
| Intended deliverables | `<document list>` |
| Smallest-clean-suite rationale | `<why this split is minimal but sufficient>` |

## Document boundary table

| Working short name | Proposed title | Normative heart section | Owns | Explicitly does not own | Depends on | Depended on by | Required clean-room capabilities | Key edge cases / review traps |
| --- | --- | --- | --- | --- | --- | --- | --- | --- |
| `<short-name>` | `<title>` | `<section>` | `<topics>` | `<non-ownership>` | `<dependencies>` | `<reverse-dependencies>` | `<capabilities>` | `<edge cases>` |

## Rejected, merged, or dependent candidates

| Candidate | Disposition | Reason |
| --- | --- | --- |
| `<candidate>` | `rejected | merged | dependent | out-of-scope` | `<why>` |

## Cross-document rules

- Terminology owners: `<term family -> owning document>`
- Dependency rules: `<cross-document rules>`
- Suite-wide in-scope topics: `<scope>`
- Suite-wide out-of-scope topics: `<non-goals>`
- Open metadata questions for pack scaffolding: `<questions or none>`