M04 — Context-sensitivity and history
Time: ~45–60 min · Depends on: M03 · Unlocks: M05
The idea in one minute
Context is not optional decoration. Context-dependent constraints couple parts so that what happens depends on neighbors, place, and path. Complex systems carry their history: past couplings sediment into structure and become load-bearing (entrenchment). Same parts, different constraint history → different system.
Why this matters
Parts lists fail. Org charts with the same boxes behave differently. The same drug dose affects subgroups differently. Juarrero’s slogan Context Changes Everything is a causal claim, not a mood.
Core teaching
1. Context-independent vs context-dependent (quick recall)
- Context-independent: changes overall odds; components need not be deeply interdependent (letter frequencies; many gradients).
- Context-dependent: creates conditional probabilities — what A does depends on B, history, location. Mechanisms include catalysts, feedback, entrainment, recursive coupling.
2. Context as objective-relational
Context here is not “my subjective take.” It is the relational constraint structure the process is embedded in. Strip relations out of your ontology, and coherence and meaning look unreal.
3. Worked example: public health (CCE ch. 5 spirit)
A town-average infection risk can mislead if subgroups are different attractors — different contact patterns, housing, prior exposure. Acontextual rates erase the constraint structure that actually drives outcomes.
4. History: sedimentation and entrenchment
- Sedimentation: the past is stored in structure (memory, records, habits, code, culture).
- Entrenchment / generative entrenchment: some past constraints become load-bearing for everything built later; changing them is costly or transformative.
Spoken application: platforms and organizations that “forget” their past mismanage complexity.
5. Temporal constraints
Timing and tempo matter: rate differences can demarcate wholes (think of a tornado’s edge as a rate boundary, not a brick wall). Melodies are path-dependent temporal wholes — order of notes is not a bag of frequencies.
Must-get summary
- Context-dependent constraints couple parts and import history
- Context is structural, not merely subjective
- History sediments and can entrench
- Same inventory of parts ≠ same system
Key terms
Claims this module locks in
Check questions
- Same components, different organization — what changes, in Juarrero’s terms?
- Why is “history matters” more than storytelling for her?
- Give one example from biology, health, or organizations.
If you’re stuck
Two kitchens, same ingredients, different recipes and tools → different meals. Constraints + sequence, not just the inventory.
Go deeper (optional)
- REPORT §§3.2, 4.1, 4.4
- Talks: BI 174
nVmz3r1dSzg; Pronovix “remember their past”I5cqPct3yXQ - Book: CCE chs. 5–6, 9–10