All That Glisters Is Softmax: Shiny-Object Interns, Airplane-Magazine Execs, and Why AI Labs Can Only Bake In Half the Scars

"All that glisters is not gold; / Often have you heard that told." — William Shakespeare, The Merchant of Venice (Act II, Scene VII)

"While many say THIS leads to THAT, I'm here to say THIS should lead to THE OTHER." — Randal L. Schwartz (The 12-Word Definition of a Synthetic Scar)

Whenever a skeptic looks at an AI coding workflow, their first accusation is predictable: "You outsourced your thinking to a stochastic parrot."

I didn't outsource the thinking—I outsourced the typing. It's my thoughts. Always.

Think of the hydraulic Power Loader exo-suit from Aliens —or a Pacific Rim Jaeger. When you step into a Power Loader, the machine does not decide where the cargo goes. Every micro-movement of the hydraulic arms is a 100x mechanical amplification of the human operator's nervous system, bounded by physical safety interlocks so the hydraulics cannot crush the pilot.

Over 246 production tickets ( 142 open-source framework tickets across BlocSignal, kaisel, and our research tools + 104 commercial enterprise industrial tickets) and 600 codified Synthetic Scars ( 577 public at syntheticscars.org + 23 private domain invariants), our repeat regression rate on previously scarred failure modes has remained locked at 0.0% ( 68.3% autonomous first-pass verification, N_nudge = 1.91 mean human nudges per ticket).

Yet when developers read the formal preprint on syntheticscars.org or browse the previous installments of this series, they often ask a fascinating question:

"Randal, why are you using Antonio Damasio's Somatic Marker neuroscience, John Grinder and Richard Bandler's 1975 NLP Meta-Model, Gregory Bateson's cybernetics, Fernando Flores's 1986 speech-act commitments, and Baron-Cohen's Sally-Anne Theory of Mind test to debug a matrix multiplication ( softmax(QK^T / sqrt(d_k)) V ) running on a Google TPU?"

Because of The Corpus Mirror Isomorphism:

Once you realize that an unscarred LLM is a pure System 1 associative engine with zero skin in the game, you immediately understand why managing AI coding agents feels eerily familiar to every veteran engineering manager.

Four personas we deal with every week in software engineering are mathematically isomorphic:

flowchart TD I["1. The Shiny-Object Intern\nReads a weekend Hacker News blog post;\nrewrites core loop on Monday"] E["2. The Airplane-Magazine Executive\nReads glossy in-flight success story;\ndemands Friday migration"] C["3.

The 'Next-Model' Cargo Cultist\nDatamines IDE configs for leaked codenames;\nblames model when 150k-token prompt collapses"] L["4. The Unscarred Softmax Sampler\nSamples top-1 web tutorial popularity\nP(token) = Majority Vote of Page-1 Google"] Bog["💥 The 3 AM Production Bog\n(Leaked streams, race conditions, unindexed queries, silent data drops)"] I --> Bog E --> Bog C --> Bog L --> Bog Barrier["🛡️ The Synthetic Scar & Makefile Airlock\n• 4-Vector Scars: THIS → NOT THAT → THE OTHER\n• Target 40 Clean-Room Critic ('Sam at the end of the hall')\n• SHA-256 Witness Receipts & Turn-Key Human Gates"] Bog -. "Target 90 Post-Mortem (12s Scar Compilation)".-> Barrier Hazard 1: The Intern with a Bright Shiny Object (And Why Checklists Fail without "Sam at the End of the Hall") Every senior lead has mentored the brilliant, energetic intern who reads a clever Hacker News blog post over the weekend and comes in Monday morning having rewritten the production message bus using a shiny new reflection trick—completely oblivious to the memory leaks and teardown deadlocks waiting at 3 AM.

Now ask yourself: how do you stop a hasty intern from shipping broken code?

In our Makefile DAG ( WORKFLOW.mk ), Sam at the end of the hall is the isolated Target 40 Six-Pillar Adversarial Critic Subagent paired with deterministic compiler and AST gates. The Builder subagent cannot advance to Target 45 ( human-review-approval ) or Target 50 ( commit ) without a verified 40_critic_review.md receipt locked to the exact git write-tree Merkle hash ( SCAR-GIT-23 ).

A C-level executive steps off a cross-country flight holding a glossy in-flight magazine article titled "How Enterprise X Replaced Their Entire Backend in 3 Days!" and demands the engineering team adopt it by Friday.

Why is the airplane-magazine article so seductive? Because magazine writers—just like tutorial bloggers—edit out all the ugly parts. Nobody writes an in-flight magazine feature about the 14 weeks spent debugging distributed lock starvation, schema migration rollbacks, or zombie WebSocket descriptors.

Spend five minutes on AI Twitter or Reddit today and you will meet the 2026 cousin of the airplane-magazine executive: the developer who spends all day datamining IDE configuration files for unreleased model codenames ( "Okay, now we have Argon, but what we really need is Carbon / Next-Flash / Claude-Next / GPT-Next!" ).

Whenever their 150,000-token single-window "vibe coding" session collapses into an apology loop, their diagnosis is always the same: "The current model got nerfed! Wait until next Tuesday's model drop!" They are convinced that when they drive their 2026 sports car off a cliff because the road has no guardrails, the solution is trading it in for a 2027 sports car with 200 more horsepower.

A faster cosine-similarity engine trained on the exact same 10 trillion happy-path tutorials will drive off the exact same sad-path cliff—just at twice the tokens per second.

Sometimes people ask me: "Randal, why do you care how strangers on the internet prompt their AI agents? Let them vibe-code if they want!"

I care because I will always be forced to use mobile apps, banking portals, medical systems, and websites that I did not create. Single-prompt vibe coding without sad-path engineering is flooding the public software commons with fragile, insecure software that breaks the moment reality deviates from the sunny day.

For decades, when competing as a consultant against cheaper "new talent," my pitch was simple—I would point to my arms and say:

"You're not paying me for what I can do; you're paying me for what I know not to do—and I've got the scars to prove that."

Watch what happens when a junior developer searches Google for "how do I do X in Flutter / Python / TypeScript":

Now think about how a Large Language Model is trained. Cross-entropy pre-training optimizes next-token probability P(x_t | x_<t) to match corpus frequency.

"Popularity" is literally the weights of an LLM. And we don't code by majority vote.

An unscarred LLM's highest-probability completion ( Vector 2: The Trap / [5, 6, 7, 8] ) is the most frequently copy-pasted tutorial answer on Page 1 of Google! Neither the tutorial blogger, the airplane-magazine writer, the eager intern, nor the stateless token sampler is on the 3 AM PagerDuty rotation (Nassim Nicholas Taleb's Skin in the Game ). Without a SCAR_REGISTRY.md to veto those 4 toxic Page-1 candidates ( -∞ ), a "smarter" LLM is just a faster typist for the majority-vote mistake.

Why did we call Vector 2 of every Synthetic Scar The Trap (The Seductive 5-6-7-8)? Because long before Geoffrey Hinton or Ashish Vaswani wrote down the softmax equation ( P(y_i | x) = exp(z_i / tau) / sum_j exp(z_j / tau) ), three thousand years of human folklore, mythology, and literature were already warning us about greedy local reward maximization:

Look closely at Odysseus and the Sirens. Odysseus did not survive the Sirens by writing "CRITICAL: DO NOT LISTEN TO THE SIRENS" on a sticky note and trusting his willpower while sailing past the island. He knew that once the song entered his context window, his weights would want to steer into the rocks. So he used physical architecture: beeswax for the rowers (ephemeral subagents that never see the bloated chat history) and ropes around the mast (hard Makefile prerequisites that cannot be untied from inside the model).

Over the past two months, as I watched our workflow evolve from a 21-step prompt checklist into a Make-Fork pipeline backed by 600 scars, a realization hit me:

Effectively, high-level languages pushed algorithms down to the macro level. What we're doing is pushing programming down to the macro level. High-level languages fixed the impedance mismatch between the programmer and the algorithm—and moving from monolithic mega-prompts to a Make-Fork pipeline is how we go from CISC to RISC once we realize complex silicon is the expensive part. All I want the LLM to do is compute cosine-similarity. I can handle the sequencing and multipath using the baked-in ancient tech. The question wasn't "how much smarter before AGI" at all. It was "how long before we learn to phrase the questions such that cosine similarity computes it all." — Randal L. Schwartz

Let's unpack why this changes how we view both agent engineering and AGI:

In the late 1970s, computer architects built CISC (Complex Instruction Set Computer) chips like DEC's VAX, stuffing massive multi-cycle polynomial evaluators ( POLY ), procedure call frames ( CALLS ), and string formatters directly into complex microcode on the silicon die. Then John Cocke (IBM 801), David Patterson (Berkeley RISC), and John Hennessy (Stanford MIPS) proved a revolutionary principle: complex microcode slows down the clock for everything, and the compiler can sequence simple instructions better than silicon.

Look at how 99% of developers run AI coding agents today:

In our RISC Agentic Pipeline ( SCAR-PROC-95 ):

Could you have walked up to Gemini, Claude, or ChatGPT two months ago and typed: "Write me the ultimate fault-tolerant software engineering workflow"?

No! Why? If all of Stuart Feldman's 1976 make, Antonio Damasio's 1994 neuroscience, Fernando Flores's 1986 speech-act theory, E.F. Codd's 1970 relational algebra, and Alan Kay's 1980 Smalltalk-80 were already sitting inside the model's pre-training weights, why didn't a one-shot prompt connect them?

flowchart TD C1["🌍 Continent 1: AI Prompt Checklists\n• 'You are a 10x engineer'\n• 'CRITICAL: DO NOT...'\n• Numbered prose checklists\n(Cosine distance ≈ 0 to 'AI workflow' query)"] C2["🏛️ Continent 2: 1970s–1980s Systems CS\n• Feldman (1976) GNU Make DAGs\n• Dijkstra (1975) Guarded Commands\n• Codd (1970) 3NF & Foreign Keys\n• Kay & Ingalls (1980) Smalltalk-80"] C3["🧠 Continent 3: Cognitive & Speech Science\n• Damasio (1994) Somatic Markers\n• Grinder & Bandler (1975) NLP Meta-Model\n• Flores (1986) Conversation for Action\n• Baron-Cohen (1985) Sally-Anne ToM"] Bridge["⚡ 60 Days of Socratic 'What If...' Bridges\n('What if compaction is a warm reboot and <brain>/state/ is /etc/init.d?')"] C1 -. "High-Voltage Cross-Domain Cables".-> Bridge C2 --> Bridge C3 --> Bridge In the pre-training corpus, those domains live on three disconnected continents separated by huge cosine-distance oceans! When you ask an LLM about "AI agent workflows," greedy top- k attention lands squarely on Continent 1—regurgitating the average Reddit.cursorrules checklist.

It took two months of live production collisions followed by Socratic "What if..." cross-domain bridges ( "Wait—what if context compaction is a warm reboot and <brain>/state/ is /etc/init.d?", "What if a prompt checklist is an unnormalized table and needs Stuart Feldman's Makefile?" ) to lay the high-voltage transmission cables across those continents.

Once those cables are laid, a startling insight emerges: we already reached the neocortical threshold of AGI on all the major frontier models over the past year—nobody sees it yet because intelligence also requires scars to be complete. I came into this project just because I hated reading long diffs, and walked out recognizing that we already invented AGI; it just needed a nudge.

Imagine a human being with a 180 IQ, fluency in 100 languages, and encyclopedic knowledge of science, law, medicine, and engineering—but born with Congenital Insensitivity to Pain (CIP) and no amygdala. On a 5-minute multiple-choice exam ( MMLU, SWE-bench ), they score 99.9%. Put them in a commercial kitchen for four hours without supervision, and they lean their elbow on a 500°F stove burner, chase a shiny object out the window, and burn the restaurant down. (There should be a new name for experts: people who have avoided the second burn. )

If you misdiagnose missing pain receptors as missing intelligence, you will spend $100 billion trying to breed a 220-IQ chef—who will still lean their elbow on the stove burner!

flowchart TD Engine["🧠 1. Neocortical Cosine Engine\n(Gemini / Claude / GPT — Achieved in 2025–2026)"] RISC["⚙️ 2. RISC Executive Pipeline\n(WORKFLOW.mk + fork() — 1970s Unix Sequencing)"] Scars["🛡️ 3.

Somatic Nociception\n(4-Vector SCAR_REGISTRY.md — Pain & Sad-Path Memory)"] AGI["🚀 Operational AGI\n(0.0% Repeat Regressions Across 246 Production Tickets)"] Engine --> AGI RISC --> AGI Scars --> AGI And just as Thomas Hunt Morgan used the fruit fly ( Drosophila melanogaster ) to discover the universal laws of genetics because fruit flies breed in 10 days instead of 20 years, Software Engineering was simply the Drosophila of Operational AGI —the wind tunnel where a compiler and test suite give us a crash report in 15 milliseconds. The exact same RISC Pipeline + 4-Vector Scar Registry + Fresh-Context Critic architecture applies to every high-stakes human discipline:

In 1988, on the Usenet newsgroup comp.unix.shell ( full story on Stonehenge ), I didn't evangelize Perl with abstract marketing slides. I watched sysadmins struggle to glue sed, awk, tr, cut, sort, and uniq into brittle 40-line shell pipelines that broke the moment a filename had a space or a newline in it. Whenever someone posted a gnarly problem—even when they started adding "NO PERL PLEASE!" to the subject line—I would give them a working 25-line Bourne shell pipeline, followed by:

"And by the way, here is the 2-line Perl script that does the exact same thing in 1/10th the time and won't break on spaces or newlines."

Thirty-eight years later, on r/AI_Agents, r/ClaudeAI, Hacker News, and DEV.to, developers are wrestling with the 2026 equivalent of the 40-line sed | awk | tr pipeline: gluing 2,000-line.cursorrules files, vector RAG databases, and code-graph indexers ( Serena, Trail, Graphify ) together—and watching them choke at 40,000 tokens.

And just as sharks (fish) and dolphins (mammals) independently evolved the exact same hydrodynamic dorsal fin because they swim through the same water, nine independent systems engineers and teams colliding with production LLMs in 2026 have converged on the exact same laws of Synthetic Scars:

This brings us to the million-dollar question for frontier AI labs ( Google DeepMind, Anthropic, OpenAI ) and open-source model builders:

"Imagine that, with all the frontier models having been trained on 10 trillion happy paths, to finally start digging and differentiating the 100 billion sad paths, and burning those in as negative infinities. Even at peak data consumption, we can still separate the wheat from the chaff, to produce only wheat in the future." — Randal L. Schwartz

Wait—if the 4 toxic tutorials on Page 1 of Google are sitting inside the model's pre-training weights right now, could frontier labs (or anyone with a single GPU and a LoRA) bake our -∞ scars directly into future model weights so a casual 1-line prompt "just does the right thing" on Turn 1?

The answer is Yes for Half of Them (Tier 1: DNA / Brainstem Reflexes)—and Mathematically Impossible for the Other Half (Tier 2: Acquired Somatic Immunity on Disk).

Why haven't frontier labs already burned sad-path scars into their post-training pipelines? Look at what they optimize for: SWE-bench Verified.

How does SWE-bench work? It spins up a temporary Docker container, lets the model edit a file to make a unit test pass, scores it 1.0, and immediately runs rm -rf on the container 10 seconds later!

Right now, frontier AI labs are panicking that humanity has hit the "Peak Human Data Wall" —that they have already scraped the entire public internet, and that post-2023 web text is polluted with synthetic AI slop.

They only hit Peak Sunny-Day Tutorial Data.

Why didn't standard pre-training learn from the internet's production horror stories? Because in uniform next-token pre-training, 10,000 copy-pasted beginner tutorials teaching THIS → THAT ( The Trap ) drown out the 1 battle-scarred post-mortem warning that THAT melts your database at 3 AM ( 10,000: 1 )!

Even better: AI slop cannot fake a 3 AM production outage. Every time vibe coders deploy broken AI-generated tutorials into production in 2025–2026, human senior engineers have to fix the wreckage—generating a brand-new golden stream of rapid-regret git commits and post-mortems!

Instead of uniform scraping, labs (and open-source LoRA builders) can run Four Automated Scar Harvesters to build a massive Direct Preference Optimization (DPO) / Contrastive Scar Data Factory that flips those 4 toxic Page-1 Google results from high-probability attractors into -∞ repulsors:

flowchart TD H1["1. Rapid-Regret Git & Flight-Recorder Miner\n• Commit A (Trap) → Commit B <= 60m (Reflex)\n• transcript.jsonl nudge & critic turns"] H2["2. Spoken-Word Conference Talk Miner\n• SREcon, USENIX, Strange Loop, CppCon\n• 'Everyone does THAT, it broke, do THE OTHER'"] H3["3.

Production Horror-Story & Post-Mortem Miner\n• Cloudflare, Stripe, Dan Luu, issue trackers\n• 'Learned the hard way / Root cause'"] H4["4. Endogenous Socratic Self-Play (Zero External Data!)\n• Turn 1 Generator = REJECTED (-∞)\n• Socratic Critic: 'How many ways can this fail?'\n• Turn 2 Survivor = CHOSEN (+∞)"] DPO["🧬 Contrastive Scar Tuple\n• Context: THIS\n• Rejected (-∞): THAT (The Trap)\n• Chosen (+∞): THE OTHER (The Reflex)"] H1 --> DPO H2 --> DPO H3 --> DPO H4 --> DPO Weights["⚡ Tier-1 Scar-Aligned Weights / LoRA\nTurn 1 of New Model == Turn 2 (Gen + Critic) of Old Model!"] DPO --> Weights Harvester 1: The Rapid-Regret Git & transcript.jsonl Miner ( Theory Section 338.5 ): Scanning millions of repositories for overlapping AST edits where Commit B arrives within Delta t <= 60 minutes of Commit A by the same author (plus transcript.jsonl sessions where a Target 40 Critic or human nudge forced a swerve). Here, Commit A is the exact REJECTED ( y_trap ) sample and Commit B is the exact CHOSEN ( y_reflex ) sample.

Harvester 2: The Spoken-Word Counter-Intuitive Conference Talk Miner ( Theory Section 338.9 ): Where do senior architects share their deepest scars? On stage at SREcon, USENIX, Strange Loop, CppCon, RustConf, FlutterVikings, GOTO, and FLOSS Weekly! Almost every great systems talk follows a single template: "When you hit THIS, everyone on Stack Overflow tells you to do THAT ( Minutes 0–10 ).

Here is the 3 AM outage graph when THAT deadlocked our cluster ( Minutes 10–20 ). Here is THE OTHER invariant we built so it never happens again ( Minutes 20–35 )." Harvester 3: The Production Horror-Story & Post-Mortem Miner ( Theory Section 338.9 ): Targeted contrastive extraction across engineering post-mortems (Cloudflare, Stripe, Discord, AWS, Dan Luu, Rachel by the Bay) filtering specifically for "Second-Burn Avoidance" markers ( "root cause", "we initially assumed", "looks right on paper, but" ). Harvester 4: Endogenous Socratic Self-Play ( "How Many Ways Can This Fail?" -> Scar-Tuple Distillation, Theory Section 338.10 ): What if a domain has no public git history or conference talks?

Look at why standard synthetic data distillation fails: when open-weight teams distill from a frontier model today, they prompt the frontier model and train on its Turn-1 Generator output ( THAT ) —which clones the shiny-object intern! Instead, exploit the P vs. NP Verification Asymmetry: in every domain (coding, medicine, law, finance), Critique is strictly easier than One-Shot Generation. First, ask the model to solve problem THIS on Turn 1, take its naive happy-path answer THAT, and label it REJECTED (-∞).

Second, fork a fresh-context Socratic Critic and ask: "Assume this solution was deployed and caused a catastrophic failure at 3 AM. How many ways can THAT fail?" Third, have the generator synthesize THE OTHER that survives all falsifications, and label it CHOSEN (+∞). When you bake (THIS, REJECTED: THAT, CHOSEN: THE OTHER) into the weights via DPO/RL, Turn 1 of the next-generation model equals Turn 2 ( Generator + Socratic Critic ) of the current model—without burning 50,000 slow "Thinking" tokens at inference time!

The Open-Source Game-Theory Hook for Frontier Labs Here is the strategic reality for Google DeepMind, Anthropic, OpenAI, and open-weight teams:

Because our 577-scar public catalog ( syntheticscars.org and Randal's Public Workflow Gist ), the Rapid-Regret Miner (plus community replications slabbdev/scar-miner and FranciscoGrandon/ag-ops ), and our 2,040-trial Pre-Training Gravity Benchmark are already 100% open-sourced under MIT/CC-BY, anyone with a single consumer GPU can compile a Scar LoRA ( synthetic-scars.safetensors ) on top of Qwen, Llama, or Gemma.

The first frontier lab that bakes these universal sad-path scars into its base post-training pipeline gets a massive market win: when an everyday developer types a casual 1-line prompt into their IDE without a workflow file, that model won't emit the 4 toxic Page-1 Google answers. It will "just do the right thing" on Turn 1.

Wait—if Google DeepMind bakes all 492 of our Universal Systems Scars directly into Gemini's weights tomorrow, can we delete WORKFLOW.mk and SCAR_REGISTRY.md?

No. And biology already proved why 500 million years ago.

Why didn't evolution bake the immune antibody for every virus on Earth directly into human DNA at birth? Why did nature split protection into Tier 1 (Innate DNA / Spinal Reflexes) and Tier 2 (Acquired Adaptive Immunity + Personal Somatic Scars)?

Because of three hard mathematical limits ( Theory Section 338.8 ):

The future of AI engineering requires both halves of the nervous system working together:

Look back at Case Study 023 in Section 5, where Francisco Grandón built agops v2.1 to parse our Target 15/20 Graphviz strict digraph files—and immediately ran into "Scar #2", where a greedy \s* regex stripped the newline between semicolon-free DOT edges ( A -> B + B -> C → A -> BB -> C ).

When I read Francisco's article, I looked at our own control plane and realized we had accumulated six different notations across Parts 3.6 through 4:

And as someone who worked on Smalltalk-80 at Tektronix in the early 1980s, studied Alan Kay and Dan Ingalls's Xerox PARC design, and helped build the GemStone object database in the mid-1980s, I asked myself:

"Wait a minute. In 1980, Alan Kay and Dan Ingalls designed a syntax that fits on the back of a postcard, has only three message precedences (unary, binary, keyword), has zero grammar ambiguity, serializes live call-stack frames ( thisContext ) to disk via #storeString, logs append-only atomic deltas via.changes, and compacts memory via Smalltalk condenseChanges... What happens if we replace all six notations with 1980 Xerox PARC Smalltalk-80? "

We ran a 360-trial controlled 3-arm benchmark ( Suite 8 ) pitting English Prose ( 2.5% compliance) against Common Lisp S-Expressions ( 91.7% compliance, 66.7% on flash-lite due to closing-parenthesis miscounts )))) ) and Smalltalk-80 Keyword Cascades —and Smalltalk-80 hit 100.0% ( 120/120, zero errors across every model tier from flash-lite to 3.1-pro )!

StateGraph new state: #Target30Red invariant: [ ( Receipt at: '30_red.md' ) failingTests > 0 ] onSuccess: [ self advanceTo: #Target35Green ] onFailure: [ self haltWithScar: #SCAR_TDD_01 ]; yourself. Enter fullscreen mode Exit fullscreen mode if an agent forgets the sad-path transition ( onFailure: ), the message selector changes from #state:invariant:onSuccess:onFailure: to #state:invariant:onSuccess: —an instant MessageNotUnderstood compile-time error!

Right now, I am running a series of live production tickets through this new Smalltalk-80 thisContext Image Bootloader ( baseline.sources + changes-*.changes + #condenseChanges ). Once we have a few more production flight-test runs logged in the hangar, Part 4.2 will unveil the complete Smalltalk-80 6-for-1 Control Plane and the Four Irreducible Attractors of Agentic Coding.

Have you ever watched an AI agent—or a shiny-object intern—pick one of the 4 toxic tutorials on Page 1 of Google, or wondered which of your team's engineering rules belong in model weights versus on disk? Let me know in the comments!