You are debugging a production incident. The message queue is backing up. Consumers cannot keep up with producers. Six months ago you saw the same pattern: a database connection pool exhausted, queries queuing behind it. A year before that, a thread pool that could not drain fast enough. Three different systems, three different on-call alerts, one structure: work arriving faster than capacity to process it.
If you had named the pattern the first time, you would have recognised all three as the same problem. The solution space is also the same: bound the queue depth, add consumers, or slow the producer. You spent three separate incident nights reinventing the same answer.
The twelve threads are names for the patterns that recur across every layer of the computing stack. Name them, and you stop reinventing. Name them, and you navigate between layers without getting lost.
This is the first chapter where all twelve threads appear explicitly. Each thread is introduced here by name, root form, and cross-stack manifestation. Every subsequent chapter in this book, and every chapter in all seven series books, will reference one or more of these threads by number.