EduOS Lad: the university operating system
EduOS Lad connects events, tasks, people, competencies, AI agents, data and resources so that changes in one part of a university can inform work elsewhere.
Each task carries its context, responsible participants, necessary resources, outcome criteria and links to competence development. Rules determine what information may be accessed and which actions are authorised.
Within University 5.0 the purpose of EduOS is to coordinate research, education, technology and project work. This is a proposed architecture, illustrated by a research prototype, not a claim of university-wide deployment.
Changes inside and beyond the university.
The university as a coordinated system of action
A university teaches, researches, runs projects and makes management decisions at the same time. Each field produces events, tasks, roles, constraints, data and results. EduOS gives those elements shared rules and structures.
The operating layer describes how an event becomes a task, who takes responsibility, which resources are available, how work is performed and its results recorded, and how those results influence subsequent decisions.
Learning pathways connect to practical tasks, competencies to evidence, timetables to resources, analytics to observable activity, and agents to defined functions and boundaries.
- 01Record the context
- 02Define a task
- 03Assign roles and resources
- 04Produce a result
- 05Update system state
Each cycle changes the state of people, processes and data. That state becomes part of the context for the next action.
Explore the EduOS mechanism
Examine the relationships between tasks, roles, data and the university's digital services in the separate prototype environment.
Open mechanismSeven layers of EduOS Lad
EduOS consists of connected layers. Each addresses a distinct group of tasks and provides information to other parts of the system.
Context and events
Recognising changes that call for a response.
Core entities of EduOS
Coordinated work needs a shared descriptive language. EduOS connects processes through defined entities and the relationships between them.
Event
A change requiring interpretation or action.
How one task moves through EduOS
Consider a demonstration scenario: a university needs rules for using AI agents in student project teams. The example explains how the architecture could coordinate real activities; it is not a report of completed institutional deployment.
A new class of AI tools
Agents capable of analysing material, proposing decisions and supporting projects become available in the educational environment.
Roles within the operating system
EduOS describes participation through roles, authority, accessible data and responsibility for results. One person may have different roles in different processes.
Student
Who makes which decisions
Change a student's learning pathway
Responsibilities remain attached to roles. The provenance of data, recommendations and decisions must remain available for review.
AI agents within EduOS
The agent environment divides support functions among specialised assistants. Each agent operates with task-specific context, authorised information, a defined scope of action and an expected result.
Coordination separates navigation, learning support, analysis, critique and scheduling. Agent outputs inform people and other EduOS layers; an agent's recommendation does not in itself grant authority to decide.
Navigator
Shows a person's position, available actions and the next step.
Agent orchestration in practical situations
- 01Navigator
- 02Coordinator
- 03Tutor
Data as the state of the system
Processes produce information about context, actions, outcomes, resources and relationships. EduOS proposes to connect those observations into an up-to-date model of university activity.
The digital twin describes the relationships between people, educational programmes, competencies, projects, spaces, equipment, timetables and tasks. This model can support an analysis of constraints and proposed changes.
Participants
Rules, authority and accountability
EduOS includes rules for information, agents, roles and decisions. Its governance layer defines permitted actions, access boundaries, approval routes and the responsibilities of the participants.
Role governance
What must remain observable
- 01Data source
- 02Quality check
- 03Aggregation
- 04Publishing state
The origins of information, recommendations, decisions and changes must be traceable for the system to remain accountable.
EduOS within the University 5.0 architecture
University 5.0 connects four recurring areas: research, technology, education and projects. EduOS coordinates tasks, data and outcomes between them.
Research
Creates knowledge and methods
What EduOS Lad defines
- 01
A shared language for processes
Events, tasks, roles, actions, results and data are described using shared entities.
- 02
Actions linked to competencies
Competencies are supported by observable actions and verified results.
- 03
Distributed agent support
Specialised agents support navigation, tutoring, analysis, review and coordination.
- 04
Observable system state
Process data informs a model of participants, resources, projects and learning pathways.
- 05
Explicit responsibility
Recommendations, decisions and actions remain connected to roles and governance rules.
EduOS Lad provides the proposed operating foundation for University 5.0. Through it the university can coordinate events, knowledge, people, competencies, agents, resources and data according to stated rules.
About the authorial model
EduOS Lad is being developed by Sergey Shatokhin within the IWXA laboratory as part of the University 5.0 research model. It draws on organisational systems research, teaching practice, digital tool design and artificial intelligence.
The current work includes the conceptual architecture, an interactive prototype and related research materials on the model's individual mechanisms.