SPREAD

In 1971, Creeper displayed a message and moved between machines. In this framing, the message is the payload, self-copying is replication, and the ARPANET supplies possible destinations.

By 2003, SQL Slammer infected 75,000 hosts in ten minutes. Same three components. The payload shrank to 376 bytes. The replication got faster. The routing got random.

Code was doing distribution before anyone called it that.

Before writing, before printing, stories spread by mouth. The ones that survived weren't the most detailed .. they were the most retellable. Structured for the copy mechanism: a human voice. Routed by the only network available: whoever was sitting around the fire.

Rhythm and repetition made oral epics easier to retain and retell; they are part of, not a complete explanation for, The Odyssey's endurance. The analogy is useful here because retelling preserves some structure while details change.

I was reading Ogilvy and it hit me. He called it a headline .. that's the payload. He called it placement .. that's the routing. Different words, same thing.

Same pattern again. If people scan, the first line has to survive scanning. If people share, the first line has to survive sharing. If an AI agent is reading your README, the first paragraph has to be useful or it moves on.

A headline and SQL Slammer are not the same kind of thing. The limited comparison is size: both show how a small payload can travel quickly when the replication and routing systems already exist.

This one took me a minute. The new reader has a context window of 1M tokens and no patience. It doesn't skim .. it ingests. It doesn't bookmark .. it either loads you into context or it doesn't. So the question becomes: did you fit in the window, and were you useful once you got there?

A good README gets ingested into a context window. It changes what the agent does next. If it's useful, the agent recommends it to the human .. who puts it in more context windows. Same three pieces again. The payload is the docs. The replication is usefulness. The routing is whether the agent can find you at all.

I keep expecting this site to have the reach of something that's been around for years. It's been months.

The tools are new. The platforms are new. The audience is new. A six-month-old blog doesn't have the distribution of a six-year-old newsletter. That's not a failure .. that's just how time works.

There's a fourth thing to be patient with, beyond agents and humans and yourself: the audience that doesn't exist yet.

You write the thing. You put it somewhere. You choose who sees it first. And then you wait .. because the audience is brand new and you're expecting it to already care.

I can see the pattern now. Worms had it. Stories had it. Ads had it. The three-part frame fits these examples. It will not fit every kind of distribution.

None of that helps me get anyone to read this.

The writing might be fine. The replication mechanism is "post it and see." The routing is "whatever the algorithm decides." That's not a distribution strategy. That's a lottery ticket.

Noticing a pattern doesn't mean you can use it. Knowing how a worm spreads doesn't make you contagious. The question is still: did anyone actually read it?

Worms didn't read about spreading. They spread. Stories didn't theorize about retelling. They got retold. Ogilvy didn't admire distribution. He bought the placement. I'm still in the reading-about-it phase.