Engineering

TL;DR, ordered by how much I trust each finding Solid: every embedding I tested (6 representations, 8 OpenAI dimension variants) detects that later lyrics stop returning to earlier stanzas. That is mostly the refrain disappearing. Solid, and negative: none of them detects the direction a song takes, or tells apart the songs where readers see an argument. 256 dimensions see what 3,072 see. Strong lead: the band’s topics barely move in 25 years; how it handles them does. Songs with an arc rise from 2 of 34 to 11 of 29. Exploratory: half of those arcs are open: offers and promises the lyric never resolves. Embeddings are good at telling you what a text is about. They are also good at noticing when a text repeats itself. What they lose is the relation between two passages: who does what to whom, in what order, and on what condition. Giving the vector more dimensions does not bring that relation back. ...

An agent finds a supported answer on its third attempt. Its trace shows a useful result, a successful tool call, and a judge’s approval. What did the team improve: the memory policy, the opportunity to try again, or the conditions in which this run happened? This question becomes practical when a deployment decision rests on the answer. A retry budget is something we can intervene on. A temporary tool outage is something we can record and test. A permissive judge can make a poor policy appear reliable. Calling the remaining uncertainty luck helps only if it leads us to an experiment capable of separating these mechanisms. ...

Someone promises to change. A few passages later, the person they are addressing replies that the promise is no longer enough. When the expression of commitment returns, we recognize the words, but we now know that someone challenges them. The offer remains; its place in the conversation has changed. That happens in “Puesto Pa’ Ti,” by Maluma featuring Farina. I wanted to read it alongside a declaration of affection that persists in The Beatles and a command that returns after a protest in Metallica. Placing these records together brings three different relationships between repetition and change into view, without assuming which should matter most. ...

I am not here to criticize or praise any particular era. I want to understand what songs mean, explore how they relate to one another through embeddings, and follow how the story they tell unfolds along its narrative arc. Seeing that evolution laid out makes me ask: which feelings endure from one decade to the next? Which values appear, change shape, or take on a different weight? Over the decades, the front line of what worries us has moved, and the move starts with how we perceive the city. Fear, as in the movies, first lived outside our doors, in the street, and ended up as a mantra repeating inside our heads. That shift is what I set out to follow along the narrative arc. This time I follow songs that talk about fear, from the eighties to 2026. I want to see which worries remain and what changes in the way they are told: who is afraid, what they fear, what they value, and how they respond. When I listen to albums, that mix of permanence and change is part of what draws me to following a band’s evolution. Here I try to turn that curiosity into a reading we can test and visualize. ...

An agent answered a question about Infest with 2,326 tokens of memory in its final context. Getting to that answer required thirteen model calls and 19,831 input and output tokens. The verifier accepted it. One of its claims attributed evidence from the fourth song to the first. That execution contains the central problem of this study. A smaller context can conceal a more expensive decision process, and an accepted answer can conceal an unsupported interpretation. Neither becomes visible if the experiment ends at the final prompt or the aggregate score. ...