Café Fausse — developer system map

Plain-English map of the restaurant app a software developer needs to orient fast. Inventory tip: App 73d202d (New Bot stack / API / schema / FE/BE cut). Same React → Flask → Postgres design locally and on staging.

Related: Stack · Local vs AWS · Part 4 coding overview · Quantic · Honesty · SRS freeze

Honesty locks: Local (dev) + Docker cafe-pg (postgres:16) · on-box Postgres on MSAIE staging (not a shared RDS; no florist Path B) · routes are app-factory @app.get / @app.post — not Flask Blueprints · no /api/gallery · newsletter store-only unless SES env is set · fail-closed if DB is down · on camera say MSAIE staging · HTTP only (no event bus).

1. Stack, versions, rationale

New Bot inventory at tip 73d202d (pinned range + observed install). Do not treat a hostname as a version probe.

Rationale (short): one freeze file for official copy; React for the public UX; Flask in the middle; Postgres for bookings/customers with fail-closed writes; staging proves the same design over HTTPS without claiming forever hosting.

2. Frontend / backend segmentation

Browser (React SPA)
  ├── Home / Menu / About / Gallery — import shared/freeze.json (not GET /api/menu)
  ├── Reservations / Newsletter forms → fetch /api/*
  └── /operator → read-only demo snapshot
         │
         ▼
Flask app factory (`create_app` — @app.get / @app.post, not Blueprints)
  ├── /api/* JSON
  ├── /images/<file> allowlisted gallery assets
  └── /unsubscribe HTML
         │
         ▼
PostgreSQL (on-box)
  ├── customers
  └── reservations  UNIQUE(time_slot, table_number)

SPA routes: / · /menu · /reservations · /about · /gallery · /operator Gallery = FE page + static /images/… — not an API resource. /api/gallery does not exist.

3. API endpoints

Registered on the Flask app factory in backend/cafe_fausse/__init__.py (@app.get / @app.post). Not Flask Blueprints (Hiren’s cut uses Blueprints; this repo does not).

4. DB schema (backend/schema.sql)

customers

• customer_id, customer_name, email_address UNIQUE, phone_number
• newsletter_signup, created_at / updated_at

reservations

• reservation_id, customer_id FK → customers
• time_slot TIMESTAMPTZ, table_number 1–30, guest_count 1–20, created_at
• UNIQUE (time_slot, table_number) — one table per slot (capacity honesty)

No florist Path B tables. Staging DB is on-box Postgres (MSAIE staging) — not a shared RDS.

5. Methods / modules overview (developer map)

Not every helper — the map:

6. Event / listener map (runtime)

There is no app event bus, WebSocket, or server-sent event stream. Runtime is classic HTTP request/response only.

7. Local (dev) + Docker vs MSAIE staging (same design)

Do not name a developer workstation as the product. Local (dev) is Vite + Flask + Postgres on a clone.

Same design on both deploy targets: React + JSX → Flask → PostgreSQL. Fail-closed without a database. Newsletter is store-only until SES env is set. On camera: cafe.artof.link = MSAIE staging (temporary — not production forever). Deploy table: Local vs AWS.

8. Gotchas checklist

1. No /api/gallery — gallery is SPA + /images/….
2. Newsletter grade floor = store-only until SES env is set (email_delivery.status=skipped when unset). Not a Coverage send claim.
3. On-box Postgres only on staging — not a shared RDS; no florist Path B.
4. Fail-closed if DB missing/unreachable (no pretend writes). Full slot (30 tables) → honest error (FR-9).
5. No event bus — HTTP only.
6. Routes are @app.get / @app.post on the app factory — not Flask Blueprints.
7. /api/operator is a demo/recording helper, not FR-19.
8. On camera: MSAIE staging, not Lightsail jargon.
9. Local (dev) + Docker — Docker here is postgres:16 as cafe-pg (or a local install). Not the product name.

Sources: New Bot App inventory tip 73d202d; backend/schema.sql; frontend/src/pages/; Flask app factory in backend/cafe_fausse/__init__.py (@app.get/@app.post, not Blueprints); README Docker cafe-pg. Unknown until probed stays labeled if anything drifts after tip. Parts 3–5 materials · Handoff mapping (not spoken on camera).