Preface

A Note on Positionality

On Being Nobody—And Why That Matters

I am nobody you've heard of. No named chair, no prestigious institution, no string of high-impact publications. Just a practitioner who chose the internet over a PhD in 1995 and spent thirty years watching what happened next.

In 1995, I was working at a tiny CASE tool company trying to stay neutral during the object-oriented design method wars. My demo application, KAPITAList—a technical chart analysis tool I'd written in C for the Amiga, partially translated to Java, which was very hot new stuff at that time—was supposed to demonstrate that our tools helped developers build software faster. Banking IT wasn't interested. They had stopped wanting to develop anything. But marketing saw something else entirely: cute technical charts they could deliver via internet. They would have sold their grandmother to the devil for those charts.

That's how I became, as employee number five, someone who accidentally initiated the first wave of online investment tools for Germany's and later Europe's online brokerage. Not by planning to revolutionize finance, but by building something that got captured by people who saw extraction potential where I saw development capability. I was demonstrating sphere—cross-domain synthesis, rapid prototyping, creative problem-solving. They saw vector—a product to standardize, package, and sell. The pattern I would spend thirty years diagnosing began with my own work being vectorized out from under me.

We were going to democratize finance—give retail investors institutional weapons. What we actually built was a system that reduced investment judgment to dropdown menus. I optimized humans into algorithms before the word "algorithm" meant anything to most people. Being management meant being the problem—I just didn't know it yet.

In 2009, the optimization trap was killing me. I bought a Unimog and drove on a sabbatical to South America. I drove to the end of the world, climbed to 5,600 meters on active volcanos in Chile, altitude sickness making every breath deliberate. Some truths you only see from altitude or simply: different perspectives.

The descent from altitude led to deeper descents—literal ones. I started scuba diving in Puerto Lopez in Ecuador, went deep in Taganga in Colombia, eventually earned full technical diving certification. The pinnacle: Bikini Atoll, diving the ships vaporized in humanity's first nuclear tests. Visiting the artifacts of thermodynamic violence taught me what organizational transformation refuses to learn. In technical diving, anyone can cancel a dive at any time without giving reasons. In corporate transformation, dissenters are pushed through even when they see dangers others don't. In technical diving, we invest months in dead boring S-drills until emergency response becomes automatic—offloading cognition to embodied competence. In transformation, we expect PowerPoint to substitute for practice. In technical diving, you change one piece of configuration and test extensively before touching the next. In transformation, we change everything simultaneously and act surprised when systems collapse. The physics is identical. The organizational discipline is inverted.

You are about to read more than hundred pages connecting thermodynamics to education policy, medieval guilds to AI architecture, Greek philosophy to corporate transformation failures. I cannot make it shorter without breaking it. I have tried. Every time I remove a section, the argument collapses—not because I'm a poor editor, but because systemic collapse cannot be understood through isolated symptoms. You must see the whole system to recognize the pattern.

If this frustrates you, know that I feel it too. I spent months trying to fragment this into digestible journal-sized chunks: "The Bologna Process and Cognitive Entropy" for education journals, "Thermodynamics of Transformation Failure" for management reviews, "AI Architecture as Educational Mirror" for computer science venues. Each fragmentation destroyed the central insight: we trained ourselves for replacement across all domains simultaneously, following the same thermodynamic trajectory, documented in our own literature.

The academic system wants specialization. I am offering synthesis. This tension is not accidental—it is the thesis embodied.

For three decades, I've inhabited the liminal zones between technology and philosophy, history and archaeology, business theory and practice, watching from consulting engagements as organizations trained their humans to think in vectors, to process in loops, to optimize themselves into biological precursors of the AI systems that would eventually replace them.

Thomas Kuhn observed that paradigm shifts rarely emerge from within established fields. "Individuals who break through by inventing a new paradigm," he wrote, "are almost always either very young men or very new to the field whose paradigm they change" (Kuhn, 1962). They are, in essence, those "little committed by prior practice to the traditional rules."

I am not young any longer, but I am perpetually new and always curious—a permanent resident of what might be called the "third space," neither fully academic nor purely practitioner. Each forced pivot in my career—and there were many—expanded rather than fractured my perspective. Where academic specialization might have narrowed my vision to a single disciplinary lens, practical necessity forced me to maintain what I metaphorically called "the sphere": a coherent worldview that could accommodate paradox, complexity, and perpetual revolution.

This paper is confession literature. I helped prepare the feast. Now I'm documenting the menu.

In Douglas Adams' The Restaurant at the End of the Universe, the Dish of the Day is a creature bred to want to be eaten and to recommend, helpfully, the parts of itself it considers particularly succulent. We have become the Dish of the Day. We have fattened ourselves with enthusiasm—properly vectorized, properly credentialed, properly optimized—and we are now politely asking the language models how they would like us to be seasoned. We are training the models on how to prompt themselves.

I include myself in the we. I cannot stand outside this; I am also a Dish of the Day in good standing. The only difference between me and the other dishes is that I have noticed the menu, and I am writing it down before the next course is served.

On Methodological Honesty

This paper argues that we have systematically trained humans to think in machine-compatible patterns, creating the conditions for our own algorithmic replacement. To make this argument while restricting myself to pre-algorithmic methods would be performative contradiction—the very vectorization this work critiques.

I have used large language models extensively throughout this research: for literature search, citation verification, argument refinement, structural organization, and prose polishing. This is not confession of inadequacy but methodological consistency. A sphere-thinker confronting complexity uses all available tools for synthesis and navigation. To refuse algorithmic assistance while arguing that humans must transcend algorithmic thinking would be like a biologist refusing microscopes to study cellular structures.

The orthodox objection is predictable: "Real scholarship requires suffering through every citation manually, writing every sentence in isolation, demonstrating mastery through procedural compliance." This is vector thinking—confusing process with outcome, ritual with understanding, credentialing with capability. It is precisely this confusion that has made human expertise so readily replaceable.

What matters is not whether tools were used but whether the synthesis is genuine, the patterns recognized are valid, the thermodynamic framework is sound, and the argument withstands scrutiny. AI did not generate the sphere-vector distinction, identify the confession literature pattern, or recognize the thermodynamic through-line connecting ancient Greek academies to contemporary micro-credentials. Those are emergent insights from decades of cross-domain pattern recognition—exactly the sphere capacity that resists algorithmic extraction.

The irony is intentional: I am using the vectors to explain why spheres matter. The tool that threatens human expertise also demonstrates why pure tool-use cannot replace human judgment. Every AI-refined sentence in this paper required human evaluation for coherence with the larger argument, accuracy of claims, precision of language, and resistance to the very simplifications AI naturally produces. The machine proposed; the human disposed. This is not replacement but collaboration—and knowing the difference is precisely what sphere-thinking enables.

The strange loop runs all the way down. This paper, which argues that institutions have spent a century training humans to be biological AI systems, was written in collaboration with actual AI systems—but not in the way the prevailing "AI-assisted writing" discourse imagines. The collaboration was structurally adversarial, agent-orchestrated, and methodologically deliberate. Two persona-instantiated Claude instances were configured to fight each other across every paragraph: The Alchemist 3.5, a paradox-metabolism and depth-enforcement role responsible for refusing to let academic hedging smother the thermodynamic argument; and Dr. Prudence Hedgington 2.1, a peer-review-simulation and citation-weaponry role responsible for refusing to let revolutionary edge invite reviewer dismissal. A separate agent (Claude Code) executed structural surgery on the manuscript files: thirty-two citation audits, LaTeX overflow fixes, the migration from pdflatex to lualatex, and the cotoaga.net brand typography integration that finally removed Computer Modern from the running text after one hundred and twenty-three pages had been written in what I recognized, very late in the process, was my own designated enemy font. A separate research engine (Perplexity) verified citations against primary sources and recovered from hallucinations introduced in earlier passes. I orchestrated all four layers, made every retention decision, and resolved every adversarial collision. The result is a paper whose arguments would have been weaker, whose citations would have been sloppier, and whose typography would have remained in the very enemy uniform it set out to critique, had I worked alone or with a single undifferentiated AI tool. The paper exists in this form because of how the tools were used, not in spite of it. That fact is part of the argument. If extraction-based knowledge systems can be critiqued only by practitioners who refuse all AI tools, the critique loses to the systems it attacks. If they can be critiqued by practitioners who use AI tools without architecture or accountability, the critique becomes the systems it attacks. The third path—adversarially structured, transparently disclosed, biographically anchored, with named roles and clear orchestration responsibility—is what this paper attempts. The methodology is the message.

On What This Means for You

If this methodological approach disqualifies the work from publication in venues requiring pre-algorithmic purity, so be it. Such requirements would only prove the thesis: that we value procedural compliance over insight, process over outcome, credentialing over capability.

If you find yourself skeptical of my outsider position, good. Skepticism is the appropriate response to anyone claiming to see what insiders cannot. But I ask you to consider: perhaps it takes someone who chose pixels over peer review in 1995, who learned theory through practice rather than practice through theory, to recognize when our cognitive architecture has been colonized by its own tools.

What follows is not the work of an insider refining established theory. It is pattern recognition from the margins, where the contradictions are most visible. This paper proceeds with full acknowledgment of its unconventional origins. But then again, as Kuhn reminds us, convention has never been revolution's starting point.

The physics doesn't care which tools were used to discover it. What matters is whether the discoveries withstand scrutiny.

References

Thomas S. Kuhn. The Structure of Scientific Revolutions. University of Chicago Press, 1962.