/ architecture
Connected by design. Clear in responsibility.
SWAPP carries data and user context. UMAY OS Core is designed to coordinate permitted workflows, while Scientist produces evidence-based investigations. People evaluate the advisory; control authority is not delegated to this flow.
01 / Working together
See with SWAPP.Go deeper with UMAY.
SWAPP is the operations workspace. UMAY OS is the umbrella for investigations, specialist agents and durable knowledge.
The operations workspace
Find data with Explorer. Read the context with Trend and Vitals. Connect investigation steps through Event and Plan.
The orchestration layer
In the target architecture, Core coordinates permitted interactions with SWAPP and specialist tasks. Local models, tools and knowledge sources connect through versioned contracts.
Server-side authorization
Local models and tools
Single execution owner
From question to sourced investigation
Scientist is designed to examine permitted data with calculation tools, compare alternative hypotheses and expose missing evidence. A sourced advisory is presented for human review.
Versioned calculations
Alternative hypotheses
Sourced advisory packet
The decision stays with people
A specialist evaluates evidence and uncertainty, then accepts, corrects or rejects the advisory. An investigation becomes durable knowledge through human review and verification.
Review the advisory
Record the decision and rationale
Verify the outcome
Target architecture · Integration and acceptance work is ongoing.
Explore UMAY OSSWAPP’s shared data backbone
Data sources
Permitted historical data, existing approved read sources and synthetic examples. Source, time window and access scope remain traceable throughout the investigation.
Shared service layer
Every module reaches data through the same async clients. Response ceilings, sampling and status-code traps are solved in one place — modules do not rediscover them.
Modules
Each module registers with a self-describing manifest; a catalog endpoint feeds the interface. Modules do not reach into one another.
Interface
A single-page application; module routes load lazily and language catalogs are split per module, so the first paint stays light.
Security and compliance
The target architecture enforces identity and authorization on the server; model output grants no authority. Sensitive data is processed locally. Writing to SCADA/DCS controls, changing setpoints, start/stop actions and alarm-state changes are outside the advisory scope.