maqbuuul/African-pos

# African Hospitality OS AI-powered Hospitality and Commerce Operating System for Africa. This repository is being rebuilt around a restaurant-first strategy: 1. Build the shared platform foundation. 2. Ship Restaurant OS first. 3. Add AI, ML, BI, and operational depth. 4. Add Hotel OS later. 5. Add Retail OS later. The old scaffold and research docs are preserved in `archive/legacy-2026-07-17/`. ## Canonical Plan Read ENGINEERING_CHARTER.md first — it explains how this document set fits together and the standing rules every other document and every line of code must follow. Then HOSPITALITY_OS_MASTER_PLAN.md. Supporting development docs: - PROJECT_STRUCTURE.md - CONTRIBUTING.md — local setup, branch/commit conventions, docstrings, PR/code review workflow for anyone joining the project - DATA_MODEL.md - BUILD_WORKFLOW.md — Restaurant OS phase-by-phase build order and acceptance gates (P0–P19), including table ordering, Kenya tax compliance (eTIMS), Shopify, WooCommerce, delivery platform integrations, and the public developer platform (API, OAuth apps, webhooks, marketplace) - BUILD_WORKFLOW_HOTEL.md (`H1`–`H9`) and BUILD_WORKFLOW_RETAIL.md (`R1`–`R7`) — same format, for Hotel OS and Retail OS once they enter the build queue - docs/adr/ — Architecture Decision Records, starting with 0001-tech-stack.md - docs/prd/ — one Product Requirements Document per `BUILD_WORKFLOW.md` phase (P1–P19): workflows, screen-by-screen UI behavior, permissions, business rules, edge cases, events, and acceptance criteria for every Restaurant OS module, plus docs/prd/hotel/ and docs/prd/retail/ for those verticals, phase- sequenced by the two build workflow docs above but still lower confidence than Restaurant OS since neither vertical has been built yet (see `docs/prd/README.md`). Start at docs/prd/README.md for the index and template. - docs/frontend-plan.md — the canonical frontend build plan: role→app surface matrix, per-app screen flows, and build order for every FOH and BOH …