How rudy-123/heizen_engg_round works
Fernleaf Kitchen is an internal admin panel for operating corporate meal programmes; employees are stored as customers and do not sign in. Staff configure dishes, menus, companies and pricing, then create and validate orders, run kitchen preparation, dispatch and delivery, and invoice companies. The Next.js client calls the NestJS API, which owns business rules and persists operational data in PostgreSQL. The graph reflects documented capabilities and sampled controller-to-service calls; unsampled feature internals are represented by their existing module paths.
Main entry points: api.ts API client · prisma.service.ts Database access · orders.service.ts Order lifecycle · (app) Admin screens
Components 21
Admin experience
- Admin screens
apps/web/src/app/(app) - API client
apps/web/src/lib/api.ts - Sign-in UI
apps/web/src/app/login/login-form.tsx
Programme setup
- Dish catalogue
apps/api/src/catalogue/dishes.service.ts - Menus
apps/api/src/menu/menu.service.ts - Companies and employees
apps/api/src/companies/companies.service.ts - Price tiers
apps/api/src/pricing/pricing.service.ts - Programme settings
apps/api/src/settings/settings.service.ts
Order fulfillment
- Order lifecycle
apps/api/src/orders/orders.service.ts - Menu resolver
apps/api/src/domain/menu.ts - Cut-off scheduling
apps/api/src/orders/cutoff.service.ts - Kitchen operations
apps/api/src/kitchen/kitchen.service.ts - Dispatch and delivery
apps/api/src/dispatch/dispatch.service.ts - Billing
apps/api/src/billing/billing.service.ts - Operations dashboards
apps/api/src/dashboard/dashboard.service.ts
API and data
- Authentication and access
apps/api/src/auth/session.service.ts - Shared schemas and DTOs
packages/shared/src/orders.ts - Kitchen clock
apps/api/src/common/clock/clock.service.ts - Database access
apps/api/src/prisma/prisma.service.ts
Other components
- Kitchen staff
- PostgreSQL
Connections 27
- Kitchen staff → Admin screens: uses
README.md - Admin screens → API client: requests data
README.md - API client → Authentication and access: signs in
README.md - API client → Dish catalogue: manages dishes
README.md - API client → Menus: manages menus
README.md - API client → Companies and employees: manages customers
README.md - API client → Price tiers: manages tiers
README.md - API client → Programme settings: configures programme
README.md - API client → Order lifecycle: creates orders
- Order lifecycle → Menu resolver: resolves ordering menu
README.md - API client → Cut-off scheduling: manages cut-offs
README.md - API client → Kitchen operations: runs kitchen board
- API client → Dispatch and delivery: dispatches drops
- API client → Billing: invoices companies
- API client → Operations dashboards: views operations
README.md - Sign-in UI → API client: submits credentials
README.md - API client → Shared schemas and DTOs: uses contracts
- Order lifecycle → Database access: persists orders
README.md - Dish catalogue → Database access: reads and writes
apps/api/src/catalogue/dishes.service.ts - Companies and employees → Database access: reads and writes
- Billing → Database access: reads and writes
apps/api/src/billing/billing.service.ts - Kitchen operations → Database access: reads and writes
README.md - Dispatch and delivery → Database access: reads and writes
README.md - Authentication and access → Database access: reloads user access
apps/api/src/auth/session.service.ts - Database access → PostgreSQL: queries
README.md - Order lifecycle → Kitchen clock: checks kitchen time
- Cut-off scheduling → Kitchen clock: uses kitchen time