← All writing

Traffic Engineer: The Album as an Emotional Schematic

*The Traffic Engineer memoir and the album are being released as public R&D.*

The Traffic Engineer memoir and the album are being released as public R&D.

Its primary purpose is to help me understand, anticipate the needs, and improve the experience of future Puretome users. I am “User Zero,” and this project is the case study of my own diagnostic process.

But the album was never part of the original plan. It was an organic, emergent discovery.

While writing the memoir, I found myself compelled to break from the prose and sprinkle in poetic stanzas. Those stanzas sparked the idea for a single song. That one song turned into three. And before I knew it, I had engineered a full 18-track album that established a perfect 1:1 parity with the book’s narrative structure.

What began as a creative impulse became a core part of the diagnostic system.

Nothing in the Traffic Engineer project is an accident.

The memoir and the album are not just “companion pieces”; they are two parts of a single diagnostic system. The memoir is the post-mortem report — the narrative, analytical account of a catastrophic system failure and the rebuild that followed.

The album is the emotional telemetry data.

It’s the raw, sonic schematic of the flawed logic, the chaotic variables, and the psychological states I was running. One is the “what happened”; the other is the “how it felt,” engineered to be a fully immersive, multi-sensory experience.

This is the architecture of that duality.

Act I: The Flawed Premise (The Fall)

Every system collapse begins with a single bug in the core code. For me, it was a flawed premise: that I could control my internal chaos with an external substance.

  • Book: The opening chapters describe a life of high-functioning addiction, a codependent relationship fueled by mutual self-destruction, and the first “bugs” that begin to slow the system down.
  • Album: “Chemical Love” is the sound of that bug. It’s the sonic representation of that codependence — the intoxicating, agonizing loop of that flawed logic. “Let’s Party” and “Casino Nites” are the sound of the chaos that a corrupted operating system generates, mirroring the memoir’s descent into a glitzy, hollow underworld where every variable is spinning out of control.

Act II: Architecting Chaos (The Engineer)

This is the hubris of the engineer. When the system becomes unstable, my response wasn’t to fix the core bug. It was to build a bigger, more complex, more “elegant” system on top of it, believing superior architecture could override a flawed foundation.

  • Book: This act details my shift from user to architect. I apply my engineering mind to an illicit enterprise, building apps, call centers, and chemical processes — a “perfect” system destined to fail.
  • Album: “The Formula” is the anthem of that hubris, the sound of my engineering mind being “redeemed” for a dark purpose. “Game Recognize Game” and “Life of a Dollar” are the new logic gates I built to justify the mission, the sound of a man trying to architect a moral framework inside a corrupt one.

Act III: The Catastrophic Failure (The Reckoning)

The crash is inevitable. When a system is built on a lie, it doesn’t just fail; it collapses violently.

  • Book: This is the story of the raid, the betrayal, the devastating personal loss, and the total loss of control as I am processed by the justice system.
  • Album: This act is a sonic confrontation. “The Raid” is the sound of the firewall being breached. “Why Did You Have to Go” is the stack trace of the emotional damage — the devastating personal cost of the crash. “How to Bid” is the new, primitive operating system one must learn to survive incarceration, and “Underwater Chameleons” captures the paranoia of a man who has lost all trust, mirroring the book’s exploration of betrayal and shifting alliances.

Act IV: The Reboot (Redemption)

You cannot debug a system until you are willing to admit you are its architect.

  • Book: The final chapters are the post-mortem. In the quiet of a cell, I finally diagnose myself. I take accountability and begin the long, methodical process of architecting a new system — a new life — built on a new premise.
  • Album: The title track, “Traffic Engineer”, is the sound of that final root cause analysis. It’s the moment of diagnosis. From there, “Rising Up” is the work of the rebuild. And “Dada’s Coming Back” is the new mission — the “why” that provides the core logic for the entire new system.

A case study for Puretome

This project isn’t just a story I’m telling; it’s a case study in the philosophy that built Puretome.

I had to live through a system collapse, perform a ruthless post-mortem on my own narrative, and find the causal links between my choices and my outcomes. The Traffic Engineer memoir is the data. The album is the emotion.

Puretome is the tool I am building so you can do the same: to analyze the schematic of your own life, to find the “why” behind your “what,” and to debug your own story.

Reading the book is an experience. Listening to the album is another. But experiencing them together is an act of systems analysis. It’s an invitation to deconstruct a life and find the blueprint for its redemption. This is that blueprint.