Last updated: 2026-11-06
Lab 4: Emergence Hunting
Three rules, applied to every cell on a grid, every step, with no cell aware of the pattern it's part of — and gliders, oscillators, and self-replicating structures appear, unplanned. This lab starts from the cleanest possible proof that emergence is real and not a metaphor, then asks you to find the same shape in a system that was never built on a grid at all.
Learning Objectives FoundationalKnowledge that endures for decades — core principles
- Demonstrate emergence directly, by hand or in code, from simple local rules.
- Identify the same pattern — local rule, interaction, feedback, emergent result — in a real software or social system.
- Explain why "which part caused this?" is often the wrong question to ask about an emergent outcome.
Pre-Lab Reading FoundationalKnowledge that endures for decades — core principles
Read Artificial Life and Emergent Systems and the "What No One Designed: Emergence" section of Software Meets Reality.
Materials
- Grid paper or a laptop with a Game of Life implementation (a browser-based one is fine; no installation needed).
- A short list of candidate real-world cases for the second half: a traffic jam forming with no driver intending to cause one, an open-source project's contribution norms, a social platform's echo chamber, an online marketplace's pricing behaviour, or an AI system's observed-but-untrained-for behaviour once deployed at scale.
Session Plan (120 minutes) Applied / MethodologicalKnowledge with a 5–10 year half-life — stable practice
| Time | Block | Activity |
|---|---|---|
| 0:00–0:15 | Briefing | Recap the three Game of Life rules and cellular automata generally. |
| 0:15–0:50 | Run the automaton | By hand on grid paper, or in a running implementation: start from a blinker, then a glider, and track state by state. At each step, write down which of the three rules fired for which cells — then write down, separately, what pattern a observer with no access to the rules would report seeing. |
| 0:50–1:00 | Break | — |
| 1:00–1:35 | Find the real case | Pick one real system from the candidate list (or your own). Identify its components, its local interaction rule (what does one component actually do, with only local information?), and the feedback loop that closes the cycle. Draw it as the same four-stage diagram used for the Game of Life: components → interactions → feedback → emergence. |
| 1:35–1:50 | Break the "whose fault" question | For your real case, identify the component everyone would instinctively blame for the emergent outcome. Then explain, concretely, why that component behaving differently wouldn't have prevented the outcome — only changed which component happened to be where the pattern first became visible. |
| 1:50–2:00 | Write the register row anyway | Try to write your emergent outcome as a single row in a risk register — one named risk, one likelihood, one impact, one owner — in the style of Risk Management & Mitigation's own taxonomy, which already names "emergent" risk as its own category. Note specifically which column (the name, the owner, or the score) was hardest to fill in honestly, and why. |
Deliverable Applied / MethodologicalKnowledge with a 5–10 year half-life — stable practice
The step-by-step Game of Life trace, the four-stage diagram for your chosen real system, the "whose fault" paragraph, and the attempted risk-register row with its hardest-column note.
Related Topics
- Software Meets Reality: Systems Thinking, Frame Analysis, and the Future Software Engineer — the argument this lab puts into practice.
- Artificial Life and Emergent Systems — Daisyworld and Grey Walter's tortoises, two more demonstrations of the same mechanism.
- Software Engineering as Systemic Anatomy & Pathology — Perrow's "normal accidents" and Leveson's systems-safety work, the "whose fault" question worked through for real production incidents.
- Risk Management & Mitigation and Risk Management: Lessons from Testing Real Systems — the register format and "emergent" risk category this lab's final block tries to apply directly.
- Lab 3: Wicked Problem Framing — previous in the series.
- Lab 5: AI-Proof Skills Audit — next in the series.
References
-
Gardner, M. (1970). The fantastic combinations of John Conway's new solitaire game "life". Scientific American, 223(4), 120–123. https://doi.org/10.1038/scientificamerican1070-120
-
Perrow, C. (1984). Normal Accidents: Living with High-Risk Technologies. Basic Books. Held by the University of Reading Library (the 1999 revised edition, Princeton University Press).
Graduate Attributes
Directly developed
- Critical Thinker: Readers trace a step-by-step Game of Life simulation to observe how simple rules generate complex patterns.
- Subject Specialist: Readers construct a four-stage diagram to map emergent behaviour in a real-world system that lacks a grid structure.
Modelled on this page
- Reflective: The assignment requires a written analysis of responsibility within emergent systems to examine underlying assumptions.
- Confident Communicator: Complex concepts like emergence are explained through concrete examples such as gliders and oscillators.
University of Reading Graduate Attributes framework.