A Student's Day in EduOS Lad
A project day connects the student's own work with a team, educators, specialist agents, resources, decisions and reviewed outcomes.
This interactive day is an illustrative research scenario. It is not a live deployment or a record of a real student's competence.
08:30: Morning context
- Action
- Review changes, tasks and dependencies
- Participants
- Student, navigator
- Result
- Daily priorities
- Recorded data
- Current tasks and dependencies
A day is organised around tasks and dependencies
- 01
Context
This element connects the participant's actions and the next phase of the shared project.
- 02
Priority
This element connects the participant's actions and the next phase of the shared project.
- 03
Role
This element connects the participant's actions and the next phase of the shared project.
- 04
Resources
This element connects the participant's actions and the next phase of the shared project.
- 05
Interactions
This element connects the participant's actions and the next phase of the shared project.
- 06
Result
This element connects the participant's actions and the next phase of the shared project.
- 07
Feedback
This element connects the participant's actions and the next phase of the shared project.
Nine connected stages of one project day
08:30 · Morning context
- Action
- Review changes, tasks and dependencies
- People
- Student, navigator
- Output
- Daily priorities
- New data
- Current tasks and dependencies
08:30 · Morning context
At the start of the day, the student reviews changes, project deadlines, dependencies, new sensor data, expert availability and the evidence required by the lecturer.
- Engineer needs a revised model before the team session.
- Economist awaits the baseline figures.
- Lecturer adds a transparency-of-assumptions criterion.
- New sensor measurements arrive.
- Expert is available only in the afternoon.
Interactive: select the morning priorities
Choose up to three in sequence. Each choice retains its dependent role, expected result and time condition.
09:00 · Personal assignment
Project objective: create a defensible plan to reduce building energy use. Student responsibility: compare three scenarios using updated measurements and document the limitations of each.
- Data completeness
- Explicit assumptions
- Distinct alternatives
- Technical constraints
- Inputs needed by economist
- Grounds for expert review
Specialist agents support distinct tasks
- 01
Navigator
Next actions, dependencies and related materials
- 02
Tutor
Explanations, examples and methods
- 03
Analyst
Data structure, changes and comparisons
- 04
Critic
Contradictions, assumptions and weak grounds
- 05
Coordinator
Roles, dependencies and handoff checkpoints
- 06
Competence agent
Proposed evidence links and gaps for human review
- Agent
- Tutor
- Input
- Task and prior knowledge
- Prepared output
- Explanation and practice
- Decision belongs to
- Student
10:30 · Individual analytical work
- Validate readings
- Record changes
- Select scenario parameters
- Make assumptions explicit
- Build three alternatives
- Compare constraints
- Visualise differences
- Prepare handoff questions
Intermediate artefacts include cleaned data, a table of assumptions, scenarios, constraints, questions and a preliminary conclusion.
12:00 · Team synchronisation
The analytical model becomes input to engineering, economic assessment and project coordination. Each handoff has an object, receiving role and acceptance criteria.
- Object
- Scenario analysis
- Criteria
- Assumptions and constraints
- Dependent result
- Engineering alternatives
- Possible disagreement
- Conflicting optimisation criteria
13:30 · Revised measurements change the task
A higher evening load may change the baseline, technical parameters, projected financial effects and what can be reviewed before the expert session.
- Validate measurement quality
- Reconsider scenario assumptions
- Check technical feasibility
- Revisit expected financial effects
- Record unresolved questions
An event changes the afternoon schedule
Fresh evening-load readings invalidate some assumptions. Compare three possible changes; the responsible participants must agree before the schedule is applied.
A: Verify data first
- Verify new readings
- Recalculate baseline
- Expert review
- Economic appraisal
- Record result
- Benefit
- Lower risk of invalid data
- Constraint
- Less time for economics
- Responsible for decision
- Coordinator and lecturer
15:30 · Expert review
The expert examines data, assumptions, feasibility and the grounds for pilot use. The critic agent helps prepare questions but cannot authorise professional acceptance.
- Evening demand is missing from one scenario.
- Equipment reconfiguration costs are excluded.
- Assumptions about user behaviour need review.
Review output: changes requested, revised criteria, open questions and conditions for further verification.
Feedback forms evidence for review
Data analysis, scenario design, uncertainty and interdisciplinary handoffs can create new material for competence review. Neither agent advice nor an example scenario automatically confirms an ability.
- Data analysis
- Visualisation
- Basic systems reasoning
- Teamwork
16:30-17:00 · Outcomes and the next state
- 01
Project
Revised scenarios with their assumptions and open questions.
- 02
Individual
A traceable analytical contribution.
- 03
Team
An integrated account of technical and economic dependencies.
- 04
Educational
Material for review and a proposed next learning task.
- 05
Research
Questions about the drivers of evening energy demand.
The resulting data include task status, actions, assumptions, handoffs, resource changes, reviewers and the grounds for next decisions.
One day, different accountable perspectives
- Sees
- Own tasks, results and feedback
- Outcome and decisions
- Next task and learning pathway
The complete fourteen-stage day
1. Enter the work environment
Review task dependencies and availability.
Rules for one educational-project day
- 01
Context before action
Record the task, responsible participants, evidence, decision grounds and resulting change.
- 02
Individual responsibility
Record the task, responsible participants, evidence, decision grounds and resulting change.
- 03
Link each task to development
Record the task, responsible participants, evidence, decision grounds and resulting change.
- 04
Bounded agent support
Record the task, responsible participants, evidence, decision grounds and resulting change.
- 05
Observable handoffs
Record the task, responsible participants, evidence, decision grounds and resulting change.
- 06
Event-based replanning
Record the task, responsible participants, evidence, decision grounds and resulting change.
- 07
Accountable approval
Record the task, responsible participants, evidence, decision grounds and resulting change.
- 08
Reviewed result and evidence
Record the task, responsible participants, evidence, decision grounds and resulting change.
- 09
Updated next-stage context
Record the task, responsible participants, evidence, decision grounds and resulting change.
About the research model
This scenario is developed by Sergey Shatokhin within University 5.0 and EduOS Lad at IWXA. It describes how a possible system can connect individual learning, team projects, specialised agents, schedules, accountable decisions and verifiable outcomes.
Explore the separate demonstration ↗