Skip to content

Back to platform admin

Project docs

00 — The Core LoopWhat the product is, and the scan → menu → order journey traced through the real files. Start here.Documentation Index (README)Master index tying together all 17 bilingual technical specs.01 — System OverviewProduct vision, tech stack, architecture diagram, personas & implementation status.02 — Folder Structure & RoutingAntiGravity folder architecture, full route table, and the proxy.ts subdomain resolver.03 — Platform Admin SpecTenants, Plan Builder, Feature Flags & plan-whitelisting, VIP overrides, Impersonation, Invoicing.04 — Restaurant Dashboard SpecMenu, Orders, Tables/QR, POS, Staff, Inventory, CRM, Reservations, Promos/CMS, Analytics, Settings.05 — Customer Menu & Allergy EngineThe /table QR entry flow, menu browsing, allergy/diet filter engine, cart, and split-bill.06 — Kitchen, Waiter & Rider AppsKDS, pickup screen, waiter app, rider app, and the shared cross-surface real-time order backbone.07 — Database Schema & ERDFull target Prisma schema, Mermaid ERD, RLS policies, indexing, and migration path from mock data.08 — Payment & SMS IntegrationsbKash/Nagad/Stripe IPN webhooks, SMS/WhatsApp dispatch, and ESC/POS thermal KOT printing.09 — Caching & PerformancePer-route rendering strategy, Upstash Redis cache keys/TTLs, and Core Web Vitals targets.10 — DevOps & CI/CD PipelineVercel hosting, Vercel Domains API automation, GitHub Actions, and Prisma migration strategy.11 — Testing & QA StrategyTesting pyramid, Vitest/Playwright/RTL setup, critical user journeys, multi-tenant test data.12 — Security Audit & Rate LimitingThreat model, RLS defense-in-depth, Upstash rate limiting, OWASP Top 10 mapping, launch checklist.13 — Domains, Routing & Every LinkHow a hostname becomes a restaurant, all 47 routes, where every link goes, local and Vercel setup, custom domains, troubleshooting.14 — Supabase SetupProjects, environment variables, the app_server role, row-level security, auth, Storage, Realtime and cron — with the isolation checks the SQL passed.15 — Backend Architecture & ModulesWhere backend code goes: folder structure, 21 modules and their dependency rules, the tenancy wrapper, and how one action is built.16 — Backend Cutover PlanPhase order with done-checks, what replaces every localStorage key and mock read, seeding, and the accounts the business must supply.17 — Production ReadinessWhat ships today with its evidence, what is blocked on the backend, and the operational, legal and design checks before a real restaurant uses it.Master Feature ListEvery feature in the system, grouped by module, with phase tags and build status.Software Requirements SpecificationFunctional & non-functional requirements that define what RestaurantOS must do.Roadmap & PhasesThe phased delivery plan from MVP through enterprise + AI capabilities.

Pick a document from the sidebar

The feature list, SRS, and roadmap are kept in sync with the actual files in this repo's docs/ folder.