The system is organised by task, not by technical structure.
- Work
- An operating system for restaurants, six roles and one flow
- Role
- Co-founder, two partners
- Period
- 2026 — Present
- NestJS
- Prisma
- PostgreSQL
- multi-tenant
- Next.js
The brief
A restaurant at peak hour does not navigate, it operates. The problem was not missing modules: it was having to jump between them to finish a single task. I designed the architecture and built the whole system, six modules that work as one and a different interface per job, because the cook does not need to see the balance and the accountant does not need to touch an order.
How it is built
POS, kitchen, register, BI, accounting and staff in one system, with six roles seeing different interfaces. NestJS 11 and Prisma 5 over multi-tenant PostgreSQL, with permissions, audit and Lima time resolved in the core: the permissions guard is reached from 315 places in the code.
Guided mode reached v4 because a restaurant owner tested v3 and the verdict was that it was a skippable slideshow, not a tutorial. A tutorial makes you perform the real action; a slideshow gets skipped and teaches nothing.
Pagination was not an improvement, it was a requirement measured against the code: 274 findMany calls and 161 list endpoints without an identifier. No list in the system returns everything.
One caveat
This is the piece I am proud of. The figures come from the repository's code graph, not from memory.
Where it breaks
Unsounded: this case does not yet declare where it breaks. The line goes down and touches no bottom until he publishes it.