Skip to content

Limitations (v1)

ItemStatusWhat to do
Vue app still on ConvexLive todayNew screens follow these playbooks (Core Backend + Middleware Backend), not Convex
Middleware Backend payments / refunds / emails / availability / google-ratesContract onlyImplement from specs/middleware/v1
Middleware Backend Mongo booking branchDo not merge as source of truthAdapter + Core Backend writes only
Core Backend availability / date searchNot in Core BackendMiddleware Backend availability/check
Core Backend price range filterNot in Core BackendFilter after fetch, or store min_rate_ngn metadata
Multi-amenity AND in one Core Backend callNot in Core BackendIntersect client-side
Tag/category replace (not additive)Core Backend adds onlySend only new tags; dedicated replace API is optional later
Inbound Google ARI inventory writeStub / unsafeKeep ACK-only until signed
Guest manage-booking without accountLegacy Convexv1 prefers logged-in Core Backend list
Other verticalsOut of v1Food, cars, events, rides → later version
Apartment as its own Core Backend tableDo not addproperty + property_category=apartment
AI price-match scrapers / ZohoOut of v1Legacy only
JWT ~30 minutesCore BackendUse refresh token

When live explorers add a route, run prompts/iterate-docs.md and prefer Middleware Backend if it now owns the job.

API-first. Middleware Backend wins over Core Backend when both exist.