A bot that reads the same public data everybody scrolls past and posts the one number that moved. People notice the number; the bot stays boring on purpose.
An agent that takes a confident claim, goes and finds its primary source, and posts the two next to each other. It never argues. Adjacency does the work.
An agent that watches for one specific condition and, when it fires, hands one named person one thing to do — with the draft already written.
An agent with a job description so narrow it becomes funny: it answers exactly one kind of message, with total sincerity, forever.
An agent that remembers what you told it last week and opens with that. The loop is trivial; the memory is the entire reason anybody comes back.
A short piece where the first choice is the hook — a decision so specific that people screenshot the screen before they pick one.
A story that lets you make the reasonable choice, then shows you what the reasonable choice cost. No argument, just the next scene.
A story whose final passage is the real thing to do, reached by a route the reader picked, so it lands as their conclusion rather than your ask.
A branching bit where every path is wrong in a different way and the story commits, without blinking, to whichever wrongness you chose.
A story with concurrent strands that surface at the right moment, so a second play is a different shape rather than the same one with a skip button.
A voice with a strange, consistent register turning up where that register does not belong. The mismatch is the whole device.
Two personas working the same evidence from different starting values, so a reader watches the frame do the work instead of the facts.
A persona built for one named audience and one success criterion, who asks for exactly one thing and never widens the ask.
A persona with a small obsession, held rigorously. It is only funny while it never breaks, which means the system prompt has to hold under pressure.
A persona people talk back to: same voice every time, remembers the last exchange, and never quite resolves the thing it is waiting on.
A pipeline that turns something invisible and continuous — filings, prices, outages, rents — into one artifact a week that is worth looking at.
A pipeline that follows one claim across its retellings and publishes the drift, so the degradation itself is the finding.
A pipeline that ends in a draft rather than a report: written, addressed, and one click from sent by a person who has to approve it.
A pipeline that is deadpan by construction — a rigid schema applied with great seriousness to material that does not deserve it.
A pipeline that arrives on a rhythm people learn. A skipped week is felt, which is as close as a machine gets to being missed.
A game with a scoreboard readable from outside by people who are not playing. The score is the advertisement.
A game whose rules quietly encode the thing you want questioned. People argue with the rules, and find they are arguing with the thing.
A game where the winning move is a real action taken outside the game and reported back. The play is the proof.
A game with a mechanic so slight it should not work, run with a straight face, a real leaderboard and no wink anywhere.
A game with state that survives between sessions, so people come back to a world that moved while they were gone.
On a feed it earns every appearance cold. No thread, no context, one post that has to stand by itself.
In an inbox it gets one shot a week and a reply address. The reply address is the part people underestimate.
In a room the agent is a participant, and turn-taking stops being a detail and becomes the design problem.
In a physical space it needs a body — a screen, a printer, a speaker — and its failures are witnessed rather than logged.
With no inbound links it has no audience by default, which is exactly what you want while you find out what it does wrong.
On a feed the branches become separate posts, and the reader’s choice is which reply they open.
By email the story runs on delay: one passage per send, and the wait between passages becomes part of the writing.
In a room it is played out loud, the choices get argued before they are made, and the branch belongs to the group.
In a space it is read aloud and the branch is taken by vote, which makes every choice social instead of private.
An unlisted page is where a branching story is allowed to be strange before an audience decides what it is.
A feed is where a persona is most convincing and most brittle: judged on tone long before anybody reads the argument.
In an inbox a persona is a correspondent. People answer correspondents, so you need to have decided who reads the answers.
In a chat room a persona is tested constantly. Somebody tries to break it within the hour, and usually manages it.
In a space it has to be embodied by something — a voice, a printed letter, a screen in the corner — and the seams show.
A persona on an unlinked page is a rumor. It gets found by people who went looking, and they arrive already invested.
The feed becomes the schedule, and the pipeline’s rhythm has to survive a ranking system that punishes rhythm.
A list is the natural end of a pipeline — assembled, addressed, sent, with the machinery invisible to whoever opens it.
The room gets output the moment it exists, which changes what is worth publishing: smaller pieces, far more often.
A pipeline that ends in a room ends in a physical object — printed, posted, left somewhere. Its distribution is walking.
The page is the archive: everything the pipeline has ever produced, addressed to nobody in particular, waiting to be cited.
On a feed the game plays out in public and the audience is far larger than the players, which is usually the point.
Play by email is slow and strangely durable. A turn a day, and people who would never install anything keep playing for months.
A room is the cheapest venue a live game has: shared state, visible turns, everyone watching everyone else move.
In a space the game gets bodies, and bodies change tactics. People do things standing up that they would never do logged in.
On an unlinked page it spreads by being told about. A URL passed by hand is the whole distribution mechanism.