Event-driven Learning: Bringing Current Change into Education

A change becomes the grounds for a new question

Scientific results, professional practice, technologies, social processes and rules change what people need to know and do. Event-driven learning relates such changes to the university's existing knowledge and work, without mistaking novelty for verified significance.

1. 01

   Signal

   Initial information about change in the external or internal environment.

2. 02

   Verification

   Establish sources, observed facts and limits of reliability.

3. 03

   Context

   Relate the change to a field, time, participants and processes.

4. 04

   Significance

   Assess its relevance to programmes, competencies and research.

5. 05

   System problem

   Identify a connected question requiring coordinated work.

6. 06

   Tasks

   Divide the problem into distinct actions with reviewable results.

7. 07

   Temporary team

   Bring together the disciplines needed for the task.

8. 08

   Result

   Produce a model, scenario, prototype, research result or operating rule.

9. 09

   Update

   Return reviewed outcomes to programmes, research and the digital twin.

Eight functional layers of event-driven learning

Nine steps describe the work sequence. Eight layers group its functions: source monitoring, verification, context, significance, task design, coordination, review and authorised update.

The university observes several kinds of change

Source records need a title, type, author, publication date, intended use, scope, related tasks and limits on interpretation.

Check the claim before building a learning task

Illustrative initial claim: autonomous agents can perform linked professional tasks. The review must distinguish demonstrated capabilities from experimental claims and forecasts.

Significance depends on the scope of the impact

An event may change what is researched, which tools are available, how professional roles work or what a programme should teach. Different implications need different forms of response.

1. 01

   Scientific

   Creates new research questions, methods or data.

2. 02

   Technological

   Changes available tools and ways of working.

3. 03

   Professional

   Changes tasks, roles and required skills.

4. 04

   Educational

   May require changes to modules, assignments or criteria.

5. 05

   Project

   Creates design, implementation or testing questions.

6. 06

   Institutional

   Affects university processes, resources and rules.

7. 07

   Social

   Touches participants' interests, behaviour and responsibilities.

Four events, different subject areas and participants

Select an event and inspect possible research, educational and project implications. These are hypotheses for examination, not already adopted modules.

The event is framed as a system problem

A useful problem connects observed facts, affected people, contradictions, constraints and the consequences requiring coordinated work.

• What changed?
• Which processes are affected?
• Whose problem is it?
• Which interests interact?
• What knowledge is required?
• Which constraints apply?
• What may happen next?
• What result is needed?

Choose the elements of a problem statement

Select the change, the people affected, the conflicting requirements and the kinds of results to prepare. Missing information remains visibly missing.

One connected problem requires several kinds of work

Technical, analytical, economic, organisational, legal and ethical questions are not interchangeable. Each needs an owner, a method and a reviewable output.

1. 01

   Research

   What functions and limits do agents have across connected workflows? Result: Analytical model and research findings.

2. 02

   Technology

   How can agent cooperation remain governed and controlled? Result: Prototype or technical architecture.

3. 03

   Economic

   What benefits, costs and risks arise from the proposed system? Result: Economic model.

4. 04

   Legal and ethical

   How are authority, responsibility and data access allocated? Result: Rule and constraint map.

5. 05

   Organisational

   How do human roles and processes change? Result: Organisational change scenario.

How results move between roles

The role handoffs form a dependency network, not an instruction to make every specialist wait for unrelated work. Economic and organisational analysis can proceed in parallel where the prerequisites allow.

A temporary team is built around the event

The composition follows the problem, desired result, available competencies and relevance window. People remain responsible for decisions; agents supply bounded analytical or coordination support.

Assemble a team for responsible agent-system design

Choose the roles to include. The model shows contributions and all areas not yet covered. It does not infer that the people or their authority are actually available.

Event tasks enter existing programmes and individual pathways

An event may become a case in an existing course, a temporary module, a research programme, an applied project or the participant's next task.

1. 01

   Existing learning module

   • Case study
   • Assignment
   • Discussion
   • Dataset
   • Method example
2. 02

   Temporary learning module

   • Short course
   • Interdisciplinary team
   • Project assignment
   • Final defence
3. 03

   Research

   • Question
   • Hypothesis
   • Method
   • Experiment
   • Publication material
4. 04

   Project

   • Scenario
   • Prototype
   • Analysis
   • Procedure
   • Pilot
5. 05

   Individual learning pathway

   • New task
   • New role
   • Broader context
   • Project verification
   • Research direction

Individual tasks connect to reviewed evidence, a participant's development goal and realistic access to a role or project.

Example pathways from the autonomous-agent event

Recent changes must be interpreted through established knowledge

Foundational theories, current research, methods, professional standards and practical data jointly determine which questions can be answered responsibly.

1. 01

   Foundational

   • Systems theory
   • Control theory
   • Economics
   • Law
   • Ethics
   • Research methods
2. 02

   Domain-specific

   • Artificial intelligence
   • Data analysis
   • Software architecture
   • Organisational design
3. 03

   Methodological

   • Systems analysis
   • Scenario design
   • Risk assessment
   • Comparative analysis
   • Modelling
4. 04

   Current

   • Recent research
   • Technical documentation
   • Professional cases
   • Standards
   • Regulatory changes
5. 05

   Project-specific

   • Organisational data
   • Constraints
   • Resources
   • User requirements
   • Pilot outcomes

Every source should retain its author, date, purpose, applicability and limits of interpretation. News-driven learning is a research label for this link between current change and educational tasks.

An event-driven task has its own time horizon

An event may change while teams are working. Tasks must be scoped so the result is still relevant and new sources can trigger re-evaluation.

1. 01

   Record the signal

   Cycle stage 1

2. 02

   Check sources

   Cycle stage 2

3. 03

   Interpret the event

   Cycle stage 3

4. 04

   Formulate tasks

   Cycle stage 4

5. 05

   Prepare learning materials

   Cycle stage 5

6. 06

   Team work

   Cycle stage 6

7. 07

   Intermediate review

   Cycle stage 7

8. 08

   Final output

   Cycle stage 8

9. 09

   Reassess the event

   Cycle stage 9

10. 10

    Update the programme

    Cycle stage 10

One event can produce different learning modules

The format is a proposal until the programme owner confirms criteria, participants and resources.

Specialist agents prepare bounded contributions

Agents can collect, structure, compare and question information. They do not decide that a signal is true, enrol students or approve a curriculum change independently.

1. 01

   Source-monitoring agent

   Collect candidate signals in authorised fields. Output: Structured source list.

2. 02

   Verification agent

   Compare evidence, facts and contradictions. Output: Corroboration and open-questions map.

3. 03

   Analyst agent

   Relate the event to processes, programmes and roles. Output: Possible interpretations.

4. 04

   Critic agent

   Test grounds, alternative explanations and limits. Output: Questions for expert review.

5. 05

   Competence agent

   Associate proposed event tasks with reviewed participant evidence. Output: Possible individual participation routes.

6. 06

   Coordinator agent

   Prepare roles, stages, deadlines and handoffs. Output: Proposed module plan.

7. 07

   Governance agent

   Check rules, authority and permitted data use. Output: Approval route and action boundaries.

How source information moves between agents and responsible people

Event-driven work can produce several result types

Programme materials, competency evidence, research questions, prototypes, revised rules and management options are different kinds of output. Each must have criteria and an accountable recipient.

1. 01

   Educational

   • New case
   • Assignment
   • Module
   • Criteria
   • Materials
2. 02

   Competence evidence

   • Material for review
   • Transfer questions
   • Evidence for a proposed role
   • New context
3. 03

   Research

   • Question
   • Hypothesis
   • Method
   • Data
   • Publication material
4. 04

   Project

   • Model
   • Scenario
   • Prototype
   • Procedure
   • Pilot
5. 05

   Organisational

   • New role
   • Process
   • Rule
   • Allocation of responsibility
6. 06

   Technological

   • Architecture
   • Interface
   • Technical solution
   • Tool
7. 07

   Governance

   • Decision alternatives
   • Impact map
   • Resource scenario
   • Change plan

Reviewed results return to the university's systems

A completed module may inform a programme, research, applied work, individual pathways and the digital twin. No change to confirmed competence or institutional rules follows automatically from a submitted example.

1. 01

   Educational programme

   • Interdisciplinary case
   • Assignment
   • Criteria for analysis
   • Learning materials
2. 02

   Research

   • Question about responsibility
   • Hypothesis
   • Data collection plan
3. 03

   Applied project work

   • Prototype
   • Role map
   • Operating rules
   • Pilot scenario
4. 04

   Competence graph

   • Evidence for systems analysis
   • Work involving risk
   • Interdisciplinary communication to review
   • Digital-system design to assess
5. 05

   University digital twin

   • Project
   • Participants
   • Reviewed outcomes
   • Approved rules
   • Next tasks

The same event creates different questions for five participants

From an AI-agent signal to a reviewable educational module

Sixteen stages show how the proposed event is verified, connected to university goals, decomposed into work, critically reviewed and returned to ongoing processes.

Conditions for event-driven learning

• Every event needs an identifiable source and bounded description.
• Significance is judged by effects on programmes, research, projects and competencies.
• Define the connected problem before distributing tasks.
• Each role receives an action and an expected, reviewable result.
• A temporary team must cover the necessary aspects of the problem.
• Event tasks connect with individual goals and reviewed evidence.
• Fundamental knowledge provides the basis for interpreting a recent signal.
• Resources and timing must fit the relevance window.
• AI agents provide bounded support; educational and substantive decisions remain with people.
• Changes to programmes, competence records and the digital twin require the corresponding review and authority.

A repeatable route from change to authorised action

1. 01

   From signal to bounded event

   Verification distinguishes supported facts from experimental capabilities and conjecture.

2. 02

   From event to tasks

   Context and significance determine the educational or research problem.

3. 03

   Temporary interdisciplinary work

   Roles, resources and expert oversight assemble around a concrete question.

4. 04

   Verifiable results

   Knowledge, prototypes, research and participant work remain linked to criteria and evidence.

5. 05

   Revisions under authority

   Approved changes return to programmes, trajectories, research and the university's state model.

The proposed event cycle links current evidence to established knowledge and educational needs. Its results become useful when their grounds, review and effects remain visible to the people responsible for subsequent decisions.

About the model

Event-driven Learning is developed by Sergey Shatokhin within University 5.0 and EduOS Lad at IWXA. It connects sources, subject interpretation, interdisciplinary tasks, specialist agents, reviewed evidence and the revision of university processes.

The scenarios are research illustrations. They do not assert production use of EduOS Lad or verified abilities of actual participants.