# Module Design Document — tours

**Status:** Legacy / Superseded (directory empty)  
**URL (planned):** `/tours/`  
**Current state:** Directory exists but is empty

---

## Summary

The `/var/www/360lm/tours/` directory is empty — no code, no migration files, no registration.

The `tours` **table** (used by tour-planner for saving optimized tour plans) exists in the **`installation.tours`** schema and is documented in `MDD_tour_planner.md`. The `/tours/` *directory* appears to be a placeholder or legacy stub; it was likely never built as a separate PWA module.

**No implementation, no schema, no hub registration for this directory.**

---

## Evidence

| Finding | Source |
|---|---|
| Directory empty | `ls /var/www/360lm/tours/` → zero files, only `.` and `..` |
| No hub registration | `grep -rn "tours" /var/www/360lm/hub/*.sql \| grep -iv "tour-pg\|tour-planner"` → zero results for a `tours` PWA tile |
| tours table location | `installation.tours` (documented in `MDD_installation.md` §4.2 and referenced by `/tour-planner/index.html` line 1225) |
| Related MDDs | See `MDD_tour_planner.md` (PWA that writes to `installation.tours`) |

---

## Distinction: tours directory vs tours table

- **`/tours/` directory:** empty placeholder, no PWA code
- **`tours` table:** lives at `installation.tours`, used by tour-planner PWA (see `MDD_tour_planner.md` Integration section)

---

## ADRs governing this module

None — no code exists at `/tours/` (empty directory). The `installation.tours` table it would have owned is governed by whatever ADRs apply to its actual writers (`tour-planner`, `hub`, `sales`) — see their MDDs.

---

**MDD Version:** 1 · **Date:** 2026-07-03 · **Verified:** Directory listing confirmed empty; no schema found