# [Service Name] Architecture Reference
Last updated: YYYY-MM-DD | This document is the reference point for all technical decisions.

## 1. Service in one sentence
[Who] does [what] and gets [what result]

## 2. Component map (draw it as a restaurant)
- Dining room (frontend): [technology] — deployed on: [platform]
- Kitchen (backend): [technology] — deployed on: [platform]
- Chef (AI): [model family] — called from: [where]
- Refrigerator (DB): [technology]
- Entrance (auth): [service name]
- Dishwasher (worker): [present / absent — if present, technology name]
- Payments: [service name]

## 3. Data flow (one core scenario)
User [action] → [dining room] → [kitchen] → [chef / refrigerator] → user receives [result]

## 4. Module contracts (interfaces)
| Sender | Receiver | What is exchanged (format) |
|---|---|---|
| (sender module) | (receiver module) | (data exchanged) |

## 5. Structural decisions log (add an entry each time something changes)
| Date | Decision | Reason |
|---|---|---|
| (date) | (decision) | (reason) |