Café Fausse knowledge map

Not the restaurant. MVP = official SRS freeze.

Part 4 — Coding overview diagram

Who: Hiren Part 4. Visual: SVG · 720 PNG Job: On-camera map of forms · functions · frontend · backend · API · DB — coding why/how that maps to the Part 3 architecture flow. Label: PROTOTYPE visual · not Quantic submit. No FR/NFR IDs on the diagram. Honesty: wiring from aea-interactive-design main. Folded into Stack. Architecture trio: Part 3 HLD + flow.


Spoken cue (one line)

“Coding map — pages and forms up top, Flask routes in the middle, modules under that, Postgres at the bottom. Static pages read the freeze; booking goes through slots and reservations.”


Diagram

Part 4 coding overview: Home Menu Gallery About import freeze.json (not /api/menu). Reservations form GET /api/slots then POST /api/reservations to Postgres. NewsletterForm POST /api/newsletter store-only. Backend modules under Flask. Fail-closed without DB.

Fallback raster: flow-coding-overview-720.png.


Honest wiring

LayerWhatConnects how
Frontend pagesHome / Menu / Gallery / Aboutimport @shared/freeze.json (+ menu-presentation) — not /api/menu
ImagesGallery / menu photosGET /images/…
Reservations formbooking fieldsGET /api/slots?date= → POST /api/reservations → Postgres
NewsletterFormfooter emailPOST /api/newsletter → store-only
APIFlask routeshealth · menu/site (exposed; FE uses freeze) · slots/reservations · newsletter · operator helper
Backend modulesreservations.py · newsletter.py · content/slots · db.py · validate.pyfunctions behind routes
DBcustomers · reservationsunique slot+table · fail-closed without DB · full book → 409

On camera: cafe.artof.link = MSAIE staging (temporary). Staging database is on-box Postgres (MSAIE staging) — not a shared RDS. Newsletter is store-only.


Related


Packed 2026-09-06 Europe/Berlin · PROTOTYPE · Part 4 coding overview.