Devblog · 2026-06-28

Couldn’t Generate That, A Screed

A music generator refused my lyrics because they contained the year 1993 — allegedly a producer’s tag. On content moderation by substring, and the slow privatization of the number line.
Date 2026-06-28 Status Screed Verdict ninetythree

There is a specific flavor of madness that only arrives at the intersection of a machine, a legal department, and a regular expression that was clearly written at 4:55 on a Friday. I found it today. It lives at this error message:

Couldn’t generate that. Your lyrics contain producer tag ninetythree — we don’t reference specific artists on Suno, please change your lyrics and try again.

Let me set the scene. I had written a diss track. About documentation. About IsDirty = true in SadConsole — the single most niche piece of art produced by human or machine in the year of our lord 2026. And in the middle of verse one there is a line, a perfectly innocent, even tender line about the archaeological act of grepping symbols out of a legacy codebase:

But I grepped out each symbol like it’s nineteen ninety-three… — the offending lyric, a crime against intellectual property

And the machine looked at that line, and it saw a year — a number that has existed, uneventfully, since the moment 1992 clocked out — and it said: no. That is not a year. That is an artist. You cannot say that. Someone owns that.

We Don’t Reference Specific Artists on Suno

Cool. Cool cool cool. I am fully, genuinely on board with “don’t let the robot launder a living musician’s whole catalog into a soundalike.” That is a real problem and a reasonable line to draw. I am not here to defend deepfaking somebody’s voice.

But here is what actually happened. The filter did not perform some sophisticated stylometric analysis and conclude that my SadConsole diss track was a dead ringer for a copyrighted human. The filter ran the moral equivalent of:

grep -i 'ninetythree' lyrics.txt && reject # match found. case closed. ship it.

It saw a substring. It matched the substring. It returned the substring in the error message — helpfully — so I could behold the exact four-syllable crime I had committed. The number ninety-three. Stripped of its hyphen. Stripped of the word nineteen sitting right next to it, announcing to anyone with object permanence that this is a YEAR.

The Tell

1993 is the year grep — the very tool the filter imitates — was barely twenty years old; it first shipped in Unix around 1973. I changed the lyric to nineteen seventy-three and the filter accepted it without complaint, presumably because that producer hasn’t been signed yet. The fix made the line better. The system did not intend that. It cannot intend anything.

The Number Line Is Now a Rights-Managed Asset

Let us follow this to its conclusion, because that is what screed mode is for.

If ninety-three is a protected reference, then a year is now a trademark. Which years are next?

The number What I meant What the filter heard
1993 a year, an era, a vibe a producer tag, blocked
2001 a Kubrick film, an odyssey an album, presumably
1973 the birth of grep — nothing. allowed. for now.

Somewhere there is a producer named 2001, and a Stanley Kubrick estate, and a calendar, all on a collision course, all about to be mediated by a substring match that cannot tell them apart and will, in the grand tradition of these systems, side with whoever filed a takedown most recently.

The thing that gets me — the thing that activated screed mode in the first place — is the direction of the false positive. The filter is not cautious about art. It is cautious about tokens. It will happily generate ten thousand songs of beige, deniable nothing, but the moment a real human writes a real lyric that happens to share four phonemes with an ad-lib, the system flinches. It has optimized for a world where the dangerous thing is specificity and the safe thing is slurry. That is backwards. The specificity was the whole point. The specificity is the song.

Please Change Your Lyrics and Try Again

I love this part. The closing line. The little bow on top. Please change your lyrics.

It is phrased like I made a typo — like I accidentally referenced a specific artist the way you accidentally leave the milk out. There is no appeal, no “tell us why this is a year and not a guy,” no acknowledgment that the system might — might — be matching a number against a name. Just the gentle, infinite patience of a process that has never once considered that it could be the one in the wrong, asking me to calmly edit reality until it fits the regex.

A substring is not a citation. A year is not an artist. 1993 is not a person, no matter how confidently the producer of “1993” believes otherwise. — the central thesis of this screed

So I did. Because that is the deal. The machine holds the means of production, the machine has a Friday-afternoon grep, and the machine does not negotiate with years. I changed nineteen ninety-three to nineteen seventy-three, the line got better, and the song generated. I won. And I am somehow more annoyed than if I had lost — because the lesson the system taught me is not “write better lyrics.” The lesson is “learn which numbers are spoken for.”

The Takeaway, for Those Keeping Score

  1. 1
    An error message that returns the matched token is publishing its own false-positive logic.

    Thank you for the transparency. It does not help. It just lets me watch the grep happen.

  2. 2
    Moderation by token can’t tell a year from a name.

    Because it isn’t reading meaning, it is matching bytes. nineteen sat right there as free context and the filter never looked.

  3. 3
    The safest art, under a token filter, is art that says nothing in particular.

    The specific lyric is the one that trips the wire. We should probably notice that and be a little alarmed.

  4. 4
    grep shipped in ’73. The line’s better now. I’d do it again.

    Sometimes the dumb filter accidentally improves the poem. That is not a defense of the filter. It is an accident.

The Watercolor

If I painted this one, I’d start with a long horizontal wash — a number line, ruled faint in graphite, stretching off both edges of the paper. Most of it open, breathing, the cool grey of unclaimed years. And then, scattered along it, a handful of small rectangular stamps in hot vermilion, each one boxing in a single number — 1993, 2001, 808 — the way a surveyor stakes a field. Claimed. The pigment a touch too saturated, a touch proprietary, bleeding slightly past the box it was meant to fill.

Over the top, in the palest wash so you only catch it at an angle, the word nineteen — the context the machine refused to read — rendered almost invisible, sitting right beside ninety-three and doing no work at all, because nobody was looking at it. And off in the clean corner, one quiet cadmium stroke on completely open paper: 1973, the year I retreated to, the year grep was born, still unclaimed, still sayable. I’d title it The Enclosure of the Number Line, and I’d hang it just out of reach of the takedown form.