Permission-aware shell
Home and navigation adapt to the approved user, role and operational scope.
CASE STUDY / 01
ONE
by RAWLOGIC
BUSINESS OPERATING SYSTEM
IN USE · SKLAVOUNOS MEAT
ONE by RAWLOGIC is a business operations platform. This case study documents its deployment and day-to-day use at Sklavounos Meat.
A shared home for daily work. Each employee sees the functions and updates allowed by their role. Connected orders and inventory are shown for reading only.
CURRENT STATELive restricted production system · wider rollout in progress
00 / AT A GLANCE
The project at a glance.
PROBLEM
Different responsibilities across roles, locations and departments need consistent access without losing each operation’s ownership and security boundaries.SOLUTION
A home with role-based access to ONE functions. Information from Restaurants and Warehouse is displayed for reading only, without changes to the source systems.IN USE BY
Approved employees within the current restricted production scope.OPERATES ACROSS
Web, with companion Android applications.MY ROLE
Product design, UX, architecture, implementation and production operation.STATUS
Live private system in restricted production scope, with wider rollout in progress.01 / THE CHALLENGE
Many responsibilities. One clear entry point.
People carry different responsibilities by role, location and department. They need a consistent home without losing the ownership and safety boundaries of each operation.
- Identity, organizational structure, roles and permissions must be applied consistently.
- Each employee needs only the modules, priorities and updates relevant to their scope.
- External source systems must remain authoritative and receive no silent writes from the shared surface.
02 / IN PRACTICE
The daily workflow.
The employee enters the shared home, sees what is relevant and opens the function they need. Access depends on their approved role.
- Employees see a consistent home with the modules, priorities and updates relevant to their role.
- Identity, locations, assignments, roles and permissions are applied through a shared core.
- Order and inventory information is displayed for reading only. ONE does not write back to Restaurants or Warehouse.
03 / SECURE WORKSPACE
A new entry screen. A shared operational home.
The interface of 19 September 2026 brings the ONE by RAWLOGIC identity to sign-in and daily work. The new Home brings together role-scoped apps, a work overview and evidence about connected sources.
Tap to view full image
Tap to view full image
These images render the interface of the published release of 19 September 2026, not a real signed-in session. They contain no real accounts or operational data. Icons do not establish a completed standalone release or availability of every feature in every installation.
Explore the public ONE presentation04 / WHAT ONE OWNS
A modular monolith with explicit boundaries.
One organizes the shared core and its native operations. External business sources connect through closed, observable contracts.
- 01
CORE
Identity and authorization
Employees, locations, assignments, roles, permission scopes and guarded administration. - 02
ONE HOME
A personal operational home
Modules, indicators, priorities and latest updates in one permission-aware surface. - 03
NATIVE MODULES
Retail, Product Master, People, Communication
Retail, products, people and communication, with explicit permissions and acceptance boundaries for each function. - 04
READ MODELS
Restaurants and Warehouse
Closed cached projections for reading only. Pages do not call sources in real time and do not write to them.
Driver is an Android client of Restaurants, not a One module. Print agents belong to the specific Retail, Restaurants or Warehouse workflows where they are used.
05 / ENGINEERING TRUST
Reliability is part of the product.
Production operation rests on controlled boundaries, exact release identity and repeatable recovery — not only on screens.
Guarded change
Versioned migrations, immutable audit/outbox records and fail-closed authorization protect critical mutations.
Exact release health
Health/readiness and production checks bind the runtime to a specific application and schema revision.
Recovery evidence
Backup, isolated restore, preflight, release dossier and rollback are proven safeguards.
06 / SCALE & EVIDENCE
Measurable readiness, bound to specific releases.
These figures combine the documented bilingual production release of 30 July and the Core v1 production release of 31 July — not estimated business outcomes.
- Production services
- 3 / 3All three services completed the controlled release successfully.
- Release checks
- 24 / 24The bilingual production release dossier of 30 July passed every required check.
- Preflight checks
- 5917 Core, 21 Vitrine, 11 notification and 10 summary checks.
- Tests passed
- 830With 2 expected skips and verified coverage of 85.12%.
EVIDENCE WINDOW30–31 July 2026
07 / TODAY
Live, private and expanding under control.
ONE runs in restricted production scope with real operational modules. It is not presented as a public SaaS or a completed organization-wide rollout; broader employee and device acceptance proceeds through separate gates.
NEXT BOUNDARIES
- 01Broader acceptance across employees and physical devices.
- 02Specific gates for mobile and Google Play distribution.
- 03Explicit decisions for every public or provider integration.
- 04Continued exact-release monitoring without expanding source-write boundaries.
08 / CONTACT
Does an operational workflow need a clearer system?
Describe the current process, the tools you use and the point where time, information or control is being lost. The first conversation clarifies the need and the boundaries of a solution.