An open-source restaurant-operations ecosystem by Andrii Omelchuk — I work operations in a Warsaw milk-bar chain and build software for the problems I see on the floor.
Every project runs from a clean clone in minutes with no accounts and no paid dependencies, has green CI, and an honest Limitations section. Built end-to-end with an agentic workflow (Claude Code), orchestrated and directed by me.
flowchart TB
subgraph domain[Shared domain: Bar Mleczny Nowa menu + operators]
direction LR
M[menu · orders · reservations · stock]
end
AGENT["restos-agent (P1)\nAI ops assistant · RAG · eval harness"]
CORE["restos-core (P3)\nreservations & menu API · Java/Spring"]
WEB["restos-web (P2)\nordering & reservations UI · Angular"]
PORTAL["restos-portal (P4)\nloyalty API + GraphQL · NestJS"]
DATA["restos-data (P5)\nDelta Lake medallion · PySpark/dbt"]
LEDGER["restos-ledger (P6)\nRaft-replicated ledger · C++20"]
COURIER["restos-courier (P8)\nkitchen display · Flutter"]
PLATFORM["restos-platform (P7)\nDevSecOps · in progress"]
M --> AGENT & CORE & PORTAL & DATA & LEDGER & COURIER
WEB -->|REST + mock fallback| CORE
COURIER -.->|offline queue → sync| PORTAL
AGENT -.->|LLM interface pattern reused| CORE & PORTAL
DATA -.->|POS events| CORE
PLATFORM -.->|CI/security retrofit| AGENT & CORE & WEB & PORTAL & DATA & LEDGER & COURIER
C4-style container view. Dashed = pattern reuse / eventual integration; solid = direct dependency.
| Role family | Answered by |
|---|
Tailored, paste-ready paragraphs per role live in the private career vault; the mapping is public here.