Triggering Event vs. Underlying Cause

In self-organized critical systems, the triggering event — the specific grain that initiates an avalanche, the earthquake's final stress increment, the blog post that crashes a stock price — is almost irrelevant compared to the system's underlying critical state. The trigger is what happened. The cause is the global configuration that made a large cascade possible. Per Bak insisted on this distinction to counter the human tendency to attribute causation to the most temporally proximate event. When Anthropic's COBOL blog post triggered IBM's largest single-day stock decline in twenty-five years, the blog post was the trigger. The cause was the accumulated market anxiety about AI-driven software obsolescence, the critical state of investor confidence, the correlated repricing mechanisms across the sector. Understanding this distinction prevents the error of focusing on grain-level interventions (controlling which blog posts get published) when pile-level dynamics (the market's critical state) determine outcomes.