Permission-aware shell
Home and navigation adapt to the approved user, role and operational scope.
CASE STUDY / 01
Sklavounos One
BUSINESS OPERATING SYSTEM
A permission-aware employee entry point for One-native operational modules and controlled, read-only views of authoritative source systems.
CURRENT STATELive restricted production system · wider rollout in progress
ONE OWNS
Core identity, One Home, People, Communication / One Talk, Retail, Product Master, Vitrine and Administration.PRODUCTION
A private production system with exact-version health, guarded migrations and operational modules in restricted scope.BOUNDARY
Restaurants and Warehouse remain authoritative systems. One shows permission-scoped cached read models with no page-time source calls or source writes.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 / 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
People, Communication, Retail, Vitrine
One-native workflows plus Product Master and Administration, each with its own acceptance boundary. - 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.
03 / 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.
04 / SECURE WORKSPACE
The secure entry point sets the tone.
The public login immediately presents One as a controlled operational environment: clear product identity, approved Google access and an explicit boundary around who may enter.
A local render of the exact production-runtime login UI. The Google button is a safe local stub and the old creator card was replaced only in the render with RAW LOGIC. REAL SYSTEMS. — Created by Christos Fragoulis. No change or access was made to production One.
05 / TODAY
Live, private and expanding under control.
Sklavounos 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.
Sklavounos One retains its own independent product identity. Christos Fragoulis is its sole creator and sole legal owner, as well as the owner of the original source code, designs, documentation, assets and deliverables he has created for it. RAW LOGIC serves only as his personal creator/portfolio identity.
06 / CONTACT
Does an operational workflow need a clearer system?
Describe the current process and the point where time, information or control is being lost.