Café Fausse knowledge map

Not the restaurant. MVP = official SRS freeze.


title: Part 3 present — diagrams only nav: hide


Part 3 — Present (diagrams only)

Claude · Architecture · supporting deck Script: NATURAL · Live: cafe.artof.link Use this page while speaking — one beat per section. No FR/NFR IDs on camera. Say MSAIE staging for cafe.artof.link.


Part 3 title

Beat 1 — Why these boundaries (~0:00–0:25)

Product surface: Reservations on MSAIE staging (or still).

Why these boundaries

Reservations still


Beat 2 — How the request flows (~0:25–0:55)

React → Flask → Postgres (what Meghna clicks vs what hits the API).

How the request flows

FE ↔ BE flow

Stack


Beat 3 — Why two deploy targets (~0:55–1:35)

Same design · local vs MSAIE staging · on-box Postgres on staging.

Why two deploy targets

Local vs MSAIE staging rationale

Local HLD
MSAIE staging HLD

Beat 4 — How quality is encoded (~1:35–2:10)

Fail-closed · unique slot+table · freeze/CI.

How quality is encoded

Boxes

Sensors


Beat 5 — Why these tradeoffs (~2:10–2:45)

Two targets · Knowledge ≠ App · newsletter store-only · staging temporary.

Why these tradeoffs

Staging card


Beat 6 — Handoff → Coding (~2:45–3:00)

Handoff → Coding

Handoff

Hiren’s cut is teammate architecture — not ours. Ours is cafe.artof.link at MSAIE staging. Side page: Teammate HLD (Hiren) — labeled teammate, never our MSAIE map.

Teammate HLD next