Epic Architecture Template

Use this team template to write an epic's architecture description in the Epic Architectures wiki page.

Replace the existing heading and pending text for your epic with the section below. Keep the epic heading at level 2 (##) and its internal headings at level 3 (###) so the wiki navigation stays consistent. Replace all bracketed prompts before publishing.

---

Copyable Template

## Epic [number]: [exact epic name]

### Purpose and scope
[Explain which users this epic serves, what they can achieve, and which responsibilities belong to this epic. Mention any important boundary with another epic. Describe the intended design without implying it has already been implemented.]

### System components
[Describe the screens or forms users will interact with, the responsibilities of the backend components (Django views/models), and the records that will be read or updated. Reuse the team's shared components and data models where possible. State the access rules and where the server will enforce them.]

### [Workflow name beginning with a verb]
[Explain the workflow in a short paragraph: who starts it, what they submit or select, what the server checks, which data it reads or changes, and what the user sees when it succeeds. Explain relevant failure cases, such as invalid input, missing records, insufficient permission, or conflicting changes. State what error the user sees and how the existing data remains consistent.]

### Dependencies
[Identify the other epics this workflow relies on and what it needs from each, such as authenticated identity, park records, event ownership, or review data. Explain the shared relationship without duplicating another epic's responsibility.]

### Validation
[Describe how the design will be checked against the epic's acceptance criteria. Cover successful workflows and relevant permission, validation, and consistency checks. Keep these checks specific to the epic.]

### For team review
[List only unresolved decisions. For each, state the question, your proposed approach if you have one, and any affected epic.]
- **[Decision]:** [Question or proposal requiring team alignment.]
*(Once agreed, incorporate the final decisions into the relevant sections and remove this section).*

### References
- [Epic requirements](https://github.com/gcivil-nyu-org/team3-mon-fall26/issues/[number])