RESHUFFLE An interactive companion to the book
Causal Cascade Reader ▸ For explorers - structural tracing

Trace what could downstream follow.

Pick a structural shift - AI commoditization, ecosystem control, the right to coordinate - and follow the typed causal edges across all four chains.

The map shows what's connected. The pathways guide a reader through curated questions. Cascade does something different - it picks a starting concept and traces the typed causal edges (enables, causes, produces, cross-layer-driver) outward, surfacing failure-modes, counter-strategies, and gates that may bind along the way. Each cascade reads across all four chains: worker · workflow · firm · industry.

What this is. Structural cascade reading: what could follow if this fires. Edge directions are causal; timing, magnitude, and conjunction logic (AND/OR) are not encoded. Not a prediction or simulation.

359 typed primitives 1,967 directed edges 4 causal chains

How to read a cascade

  1. Start node — the structural shift the cascade traces from. Could be a mechanism (AI commoditization), an outcome (the wrapper trap), a meta-capability (Right to Coordinate), or a gate (legacy-workflow rigidity).
  2. Hops by depth — what fires within 1 hop, 2 hops, 3 hops. Each step is an edge with a typed causal direction. Stage-transitions (e.g. [W3→W4]) and cross-chain jumps (🔀 workflow→org) are tagged.
  3. Failure modes & counter-strategies — red callouts for failure-modes the cascade reaches (wrapper, lock-in, encroachment), green callouts for counter-strategies that contradicts them.
  4. Gates that may bind — if the cascade touches any gating-condition, the rate-mismatch binding mechanism (D-RM) is surfaced. This is why the cascade may stall in practice.
  5. Chain × stage table — reads the cascade as coverage across the four chains. A healthy cascade typically touches 3-4 of the 4 chains.