WorkStay API And Persistence Surface
Purpose
This document maps the current route/API and persistence surfaces that are most relevant to a future WorkStay-style platform.
It keeps these distinctions explicit:
- accommodation route/API surface
- vacancy / worker route/API surface
- booking / reservation surface
- persistence / read-model surface
- compatibility residue
1. Accommodation route / API surface
| Surface | Current module(s) | Classification | Notes |
| --- | --- | --- | --- |
| Public accommodation list/detail/quote | services/svc-tenders/src/routes/registerAccommodationRoutes.ts, services/api/src/routes/accommodations.ts | VERIFIED stable route surface | Backend is real and public gateway seam already exists through . |
| Owner accommodation listing reads | , | | Owner reads already have accommodation-specific gateway seam. |
| Owner accommodation reservation reads | , | | Reservation reads are real and route-backed. |
| Accommodation listing mutations | , | | Backend write path is real, but gateway still targets only . |
| Accommodation booking mutations | , | | Durable backend flow exists, but extraction seam is incomplete at the gateway. |
| My accommodation bookings | , | | Backend read is real; gateway still points only at . |