Ramion

Daily operations leave room for avoidable mistakes — a wrong price, a missed detail, work done twice. Most of it is avoidable when the software is designed around how the business actually runs.

A business-agnostic platform that starts with restaurants. Identity, business, membership and authorization know nothing about restaurants; the restaurant module is the first product on top.

• Monolith first, with explicit module boundaries — services extracted later, if there is a reason
• One global identity per person; every login is its own session with rotating refresh tokens
• Active business held on the session by the backend, never trusted from the client
• Central authorization: role + responsibilities + overrides, resolved deterministically; deny wins
• PostgreSQL first: constraints, functions and immutable migrations carry integrity

• Keeping defaults, business overrides and individual exceptions predictable — and explainable.
• Being honest about scope: built today are identity, memberships, authorization, catalog, menus and team management; orders, kitchen, inventory and payments are not built yet.

Everything — architecture, data model, product and the decision records behind them.

In progress. Restaurants are the entry point, not the boundary.