Plutonic Rainbows

On Monday Anthropic announced that it had bought Stainless, a developer-tools company most readers will never have heard of even though they have almost certainly used its output. Stainless writes the SDKs. The Python and TypeScript and Go client libraries that wrap the major model APIs were, for a quietly large fraction of the industry, generated by the same small team sitting between every lab and every customer who wanted a tidy language binding.

That is the part of the deal worth pausing on. TechCrunch reports the customer list as OpenAI, Google, Cloudflare, Replicate, and Runway. Alex Rattray, the ex-Stripe engineer who founded Stainless, had built the closest thing the agentic era has to a shared neutral utility: take an OpenAPI spec, get back a generated SDK that feels handwritten, plus the CLI and the new MCP server scaffolding that turns an API into something an agent can actually use. The Information puts the deal north of $300 million. Anthropic does not confirm a number.

Anthropic's framing is the technical one. Agents are only as useful as what they can connect to, MCP is the protocol that does the connecting, and owning the team that has been generating the servers gives Claude a faster path to every backend it might want to reach. That is a real argument. The plumbing layer for the agentic web has been underspecified and over-promised for two years, and consolidating expertise inside the lab that introduced MCP at least produces one coherent place where the standard can be hardened, even now that governance has moved to the Linux Foundation.

The other reading is harder to ignore. Forbes called it cutting off OpenAI and Google from a shared SDK pipeline, and that framing is ungenerous but not wrong. Stainless customers will keep the SDKs they have already generated. The hosted product, the bit where a competitor could press a button and get fresh client libraries for tomorrow's API surface, is being wound down. The shared neutral utility is no longer either shared or neutral. It belongs to one of the labs.

I keep returning to a line I wrote about Google last week: OpenAI sells the interface, Anthropic sells the model and the caution, Google sells the operating environment. Stainless does not fit that taxonomy, which is exactly why buying it is interesting. It is a quiet category, the plumbing under the plumbing, the layer that decides how easy it is to wire a model into a product. Owning it doesn't show up in benchmarks or keynote slides. It shows up two years from now, when half the agent frameworks in production were trained against tooling that Anthropic shaped first.

Whether that constitutes strategic foresight or just a competitive nudge dressed in MCP enthusiasm depends on how much you trust labs to behave as good stewards of a standard once they own the toolchain that implements it. The track record is short and the incentives are not subtle. What looks like infrastructure investment from inside the acquiring company tends to look like enclosure from outside it.

Marc Jacobs sent his Spring 1993 collection for Perry Ellis down a runway at the brand's Seventh Avenue showroom on the evening of 3 November 1992. Bill Clinton was being elected president the same night. The two facts are not connected except by coincidence, but the coincidence is useful for orientation: the country was about to change governments, and a twenty-nine-year-old designer was about to lose his job by mistaking what the brand executives in the room actually wanted.

The collection took grunge, then a Seattle music scene that had not yet learned to take itself seriously, and translated it into sportswear made of materials that grunge specifically refused. Two-dollar second-hand flannel shirts became printed silks. Lumberjack thermals became cashmere. Kurt Cobain's floral granny dresses became chiffon. Doc Martens stayed Doc Martens, though Converse appeared too, rendered in duchesse satin. Christy Turlington opened the show to L7's "Pretend We're Dead." Kate Moss and Kristen McMenamy closed it in matching beanies and layered pastel knits. Naomi Campbell wore combat boots and a silk flannel shirt, possibly for the first and last time in her career.

What Jacobs had done, technically, was the brief. Perry Ellis sportswear was supposed to read American youth. He had read American youth correctly, more correctly than the company executives at any of the meetings, and translated it into luxury fabrics at a price point the brand sat at. The mistake was that Perry Ellis did not want to be told what its customers were already wearing. It wanted to dress the customer the buyers thought it had. Suzy Menkes wrote "Grunge Is Ghastly" in the International Herald Tribune, then had pins made saying the same thing. Bernadine Morris in the New York Times described the looks as "put together with the eyes closed in a very dark room." The Council of Fashion Designers of America named Jacobs Designer of the Year in January 1993. Perry Ellis terminated his contract shortly afterward and killed production on the collection. The clothes were never shipped to stores. The samples sent to Cobain and Courtney Love were reportedly burned, which is the kind of detail that would not survive fact-checking if the people involved had been less famous.

The reason the show matters, beyond the brand drama, is the gap between what the room heard and what the December 1992 issue of Vogue published a few weeks later. Steven Meisel had photographed a Grace Coddington–styled editorial called "Grunge & Glory," running Kristen McMenamy, Naomi Campbell, and Nadja Auermann in warmly-shot Perry Ellis plaid and Nirvana T-shirts. The editorial worked. The clothes, photographed by Meisel and styled by Coddington, looked like the future of how women might actually want to dress. The same garments, walked under showroom lights by a young Kate Moss, had looked like the end of the world to half the front row. It is the same disjunction that played out at the other end of the same season, on a different runway, where a different designer was being read incorrectly by people in the room and correctly by the magazine that would canonise him later.

Jacobs went to Louis Vuitton in 1997 with Robert Duffy and spent the next sixteen years there. The grunge collection became one of the most reproduced editorial images of the 1990s, reissued by Jacobs himself in 2018, taught in fashion schools as the example of a show that was right at the wrong moment for the company that paid for it. The lesson everyone draws is that the executives were wrong and Jacobs was right. What nobody draws is the harder one, which is that the executives were doing their job. A brand whose customer is a forty-five-year-old in a midwestern department store does not benefit from being told its customer's daughter is going to wear ripped flannel instead. The show did exactly what the buyers feared. It also did exactly what fashion needed. Both sentences can be true on the same night.

The Rolodex is one of those objects that became a verb without quite becoming invisible. You can still hear it in business talk: a digital Rolodex, a modern investor's Rolodex, a list of business contacts treated as portable value. The object has mostly left the desk. The moral arrangement it implied has not.

Cooper Hewitt's short history is useful because it returns the word to the thing. Rolodex was a portmanteau of "rolling" and "index", a rotating file of cards arranged around a spindle, designed for the office where information arrived on paper and stayed close to the hand. Another Cooper Hewitt note places its office-supply arrival in the early 1950s, with Zephyr American Corporation's patent following in 1956. The patent record names Hildaur L. Neilsen's rotary card-filing device. That is the part I like: not the networking myth, but the physical choreography. Turn the wheel. Find the letter. Lift the card. Make the call.

Every contact in that system had edges. A card could be amended, crossed out, taped over, or thrown away. The file sat on one desk, under one person's authority, and this mattered. A Rolodex did not pretend a relationship was a shared organisational resource. It made a quieter claim: this person is in my reach because I wrote them down and kept them there. The modern phrase "my contacts" still carries that possessive little hook.

CRM software was supposed to dissolve that hook into process. A modern contact system can store interaction history, reminders, tags, email threads, pipelines, team ownership, automation, and the sort of executive dashboards that turn friendship into coloured rectangles. Folk's own explainer on the digital Rolodex makes the distinction neatly enough: the address book stores who someone is; the CRM decides what to do with them. Yet the old word keeps returning because it says the embarrassing part more plainly. A network is not only a network. It is leverage with names attached.

You can see the same residue in investor tools. Contacts+ still sells the idea of a "modern investor's Rolodex", meaning a refreshed system of profiles, reminders, context, and competitive access to people who might matter before they obviously matter. The phrase persists because it is blunter than relationship management. It admits that the contact is not only a person but a future option, tagged and waiting.

I keep thinking about this alongside the floppy save icon, another dead office object that survived by becoming interface grammar. The Rolodex is less visible than the floppy, but maybe more revealing. The save icon preserves a gesture. The Rolodex preserves an attitude toward people: sorted, retrievable, privately maintained, and valuable because they can be activated later.

There is a small ugliness in that, though not only ugliness. A handwritten card also preserved context that software often flattens: the assistant's name, the office extension, the note that someone hated calls before ten, the old company crossed out and replaced by the new one. The period before everything was archived was full of these half-private systems, practical and intimate in the same breath. A Rolodex was a machine for remembering people, but also for deciding which people were worth remembering.

The plastic wheel is now mostly a design object, a thing in museum collections and office-memory essays. The phrase survived because it still names a social fantasy we haven't retired: that a life can be indexed, that access can be owned, that the right name at the right moment can still be found by turning something inside reach.

Google I/O used to have a recognisable shape. Android first, a few developer APIs, a hardware tease, then the bit where Search got a little stranger. This year the structure collapsed into Gemini. Not because Google forgot the rest of the company exists, but because the rest of the company now seems to exist as places where Gemini can be put to work.

The cleanest announcement is Gemini 3.5, Google's new model family, which starts with 3.5 Flash. Google says Flash is available now in the Gemini app, AI Mode in Search, Google Antigravity, AI Studio, Android Studio, Vertex-adjacent enterprise products, and the Gemini Enterprise Agent Platform. It is also the default model for the Gemini app and AI Mode globally. That is not a laboratory release. It is Google pushing a new base layer under its consumer and developer surfaces on day one.

The numbers are pitched with the usual violence. Google says 3.5 Flash is its strongest agentic and coding model yet, beats Gemini 3.1 Pro on several agent and coding benchmarks, and runs four times faster than other frontier models when measured by output tokens per second. I don't much like writing benchmark paragraphs because they age badly, sometimes by lunchtime, but the direction matters. In February I wrote about Gemini Deep Think as Google spending inference-time compute on hard reasoning. This release pulls the other way: make the everyday model fast enough and good enough that agentic work stops feeling like a special mode.

Then there is Gemini Omni, which is the showier thing and maybe the more revealing one. Omni takes text, images, audio, and video as input and starts by producing video as output. Google says the first model, Gemini Omni Flash, is rolling out to the Gemini app, Google Flow, and YouTube Shorts, with image and audio output planned later. The claim is not only better video. The claim is continuity: edit through conversation, keep characters stable, make the physics hold together, let one instruction build on the last.

That is where Google's advantage looks least abstract. A video model inside a chatbot is one product. A video model inside YouTube, Flow, Android, Search, and whatever Google decides Chrome should become next is something else. AP reported that the Gemini app has passed 900 million monthly active users, more than double the previous year. Even allowing for the fuzziness of app metrics, that is distribution almost no AI-native company can touch.

The less glamorous Android and Chrome announcements say the same thing in a more domestic register. Google says Gemini Intelligence on Android will automate multi-step tasks, fill forms with opt-in personal context, turn spoken mess into cleaner messages, and build custom widgets from natural language. Chrome on Android is getting Gemini summaries, app actions, and auto browse for chores like booking parking or updating an order, with confirmations before sensitive actions. I can feel the pitch hardening as I type it: Google doesn't want one agent. It wants every surface to contain an agent small enough to disappear into the verb you were already using.

I still don't know whether people want that much help. Some of this will be useful in the dullest possible way, which is usually the way software wins. Some of it will be exhausting, another layer of anticipatory cleverness between a person and a task they could have finished with three taps. But the strategic point is clear enough. OpenAI sells the interface. Anthropic sells the model and the caution. Google sells the operating environment in which the model is already waiting.

OpenAI has put Codex inside the ChatGPT mobile app, in preview, on iOS and Android, on every plan including Free and Go. The announcement landed this week and the rollout was already underway by the weekend. Windows users still have to wait, but for everyone else the coding agent now lives a tap away on the phone you already carry.

The framing in OpenAI's own messaging is interesting. It is not "write code on your phone." Nobody wants that, and the screen is the wrong shape for it anyway. What you actually get is a remote viewport into a Codex session running somewhere else: a desktop, a devbox, a server. The phone shows screenshots, terminal output, the agent's progress on a task it was already chewing through. You can answer a clarifying question, approve the next step, nudge it in a direction, or tell it to back off. The heavy lifting stays on the machine where your credentials and your local setup already live.

There is a secure relay layer in the middle, which is the boring detail that makes the rest of it work. Your laptop is not suddenly exposed to the public internet because you wanted to check on a bug from the supermarket queue. The relay is the kind of plumbing that gets invented once and then disappears into the background of everything else.

I keep thinking about what this changes about the rhythm of the work. The older model was: open the laptop, sit down, type for an hour, close the laptop. The intermediate model, where agents took on long-running tasks, already pushed against that rhythm. You'd kick off a refactor before lunch and come back to a pile of proposed diffs. Now that pile can find you on the bus. You can glance at a screenshot of a failing test and tell the agent to try the obvious fix while you keep walking. The latency between "agent needs a decision" and "decision arrives" collapses from hours to whatever it takes you to read a notification.

The free tier matters here in a way that I don't think OpenAI is quite shouting about. There are around four million weekly Codex users by the company's count, and the gating to date has been both subscription and surface area. Putting the surface on the phone, with no paywall for at least basic use, is the kind of move that grows habits more than it grows revenue. Habit is the thing every AI lab is actually competing for at this point. Paid plans follow habit; habit does not follow paid plans.

There is a counter-reading. Putting an autonomous coding agent within easy reach of every distracted moment is also a way of extending work into the gaps that used to be rest. The agent does not care that you are at the grocery store. It only cares that you have a phone and a connection. The same convenience that collapses the latency on a real decision also invites you to make half-formed ones while your attention is elsewhere. We will see what that does to the shape of code review and to the people doing it.

For now, the immediate effect is small and concrete: an update to the ChatGPT mobile app and the macOS Codex app, and a tab on your phone that wasn't there last week. Everything that follows from that is downstream.

Helmut Lang showed his Spring/Summer 1992 ready-to-wear in Paris in October 1992, and on the evidence of the runway images preserved by Vogue, the collection looked nothing like the brand most people now remember him for. Bolos. Chaps. Earth tones. Body paint. Quill-like breastplates that read as half armour, half costume. Beaded snakes wound around briefs. A Wild West reference no one would later attach to the word "Lang." It is the sort of show you would expect from a designer still finding his idiom, which by 1992 Lang nearly was. The flat-fronted tailoring and the sheer, layered cotton came shortly after, and they came with someone else in the room.

Melanie Ward, by 1992, was already a problem for the industry's hierarchies. She had spent the previous two years producing a body of work in The Face and i-D with the photographers Corinne Day and David Sims, a visual language stripped of styling tricks and built from secondhand clothes, sneakers paired with everything, and models who looked like they had just got off the bus. In June 1992 The Face put Ward and Day on its cover under the banner "Young Style Rebels, London's New Model Army," and the underground phase of what would soon be called grunge ended on that issue. By the autumn Vogue and Harper's Bazaar had begun adopting a softer version. Calvin Klein had hired her for the Kate Moss jeans and underwear campaigns shot by Sims. And Lang, watching from Vienna, had begun the conversation that would last thirteen years.

The partnership ran from 1992 to 2005, the year Lang retired. Across that period Ward is credited, by people who were in the rooms, with shaping the casting, the styling logic, and a great deal of the brand's public image. StyleZeitgeist's obituary specifies that her hand first showed clearly on the Spring/Summer 1994 catwalk, where she shook up Lang's casting with a London cool the Paris ready-to-wear circuit was not yet used to. By the mid-90s the language we now think of as Helmut Lang, sharp tailoring, sensual layered T-shirts, transparent organza and nylon over bare skin, was fully present. By the late 90s the language had spread outward into everything Ward also touched: the Klein campaigns, the Jil Sander adjacencies, Harper's Bazaar under Liz Tilberis.

What I find worth recording is the gap. October 1992 shows you a designer doing one thing. By 1994 he is doing another, and the second thing is the one that becomes the decade's default register for serious clothes. The brand that everyone copies is the brand after the meeting, not before. And the meeting, which lives in old interviews and a small number of magazine archives, is essentially undocumented in the way a hire would be documented now. There is no LinkedIn post. There is no announcement. There is a stylist who started doing the casting, and a designer who let her, and a partnership that read across the work for years before anyone outside the industry knew her name.

The other thing worth recording is how much of this period exists only in print. Ward herself told System Magazine that the first ten years of her work were not extensively digitised, that they survive in a small number of bound back issues and the imagination of people who happened to be paying attention to magazines at the time. Lang's pre-New York shows are partly online now, because Vogue Runway has been backfilling them, but the backfill is recent and patchy. A reader under thirty mostly cannot see what made the 1990s look the way they did. The cleanest visual evidence of the most influential stylist of the decade is locked inside paper that nobody scans.

There is a temptation in writing about this period to make the partnership sound inevitable. It was not. Lang could have stayed in the Wild West register. Ward could have taken a different magazine job, or signed exclusively with Klein. The thing that distinguishes 1992 is that neither happened. Two specific people, both already distinctive, found a shared idiom in time to define a decade. The October show was the last one before the shared idiom arrived. It is worth looking at in that light.

Most British towns had at least one. A wooden case with a sloped glass front, screwed to the brick outside the library or the post office or, in the small towns, the launderette. Inside, a square of cork or hessian half a centimetre too small for the frame, so the edges showed where the fabric had faded a different shade. Drawing pins. Index cards. Felt-tipped writing on the back of cereal boxes. Polaroid snapshots of missing cats curled at the corners from the damp.

The thing held the bounded life of a few streets, and it held it for as long as the pins kept their grip.

A noticeboard was not a classified column. The classifieds were typeset and counted by the line and paid for at a front desk; they aggregated upward into a paper that circulated across a county. The board outside the launderette aggregated nowhere. It was visible to perhaps two hundred people a week, all of whom lived within walking distance, and it carried things the paper would not have bothered to print. A piano teacher. A spare room, women only, references essential. A plea, in shaky capitals, for the return of a tortoise named Stanley. Knitting circle, Tuesdays, church hall, bring your own needles.

The content varied by the host. The library board ran to evening classes and political meetings, with the occasional yellowing leaflet about a footpath inquiry no one remembered initiating. The post office favoured laminated official notices about pension adjustments, surrounded by handwritten cards offering ironing services. The launderette tended toward the desperate: lost dogs, room shares, secondhand pushchairs. A board could acquire a tone the way a pub does, and locals knew which one to read for what.

Nothing on these boards was archived. Not by the library, not by the council, not by anyone. The cards came down when they got wet, or when the next pin needed the space, or when the cleaner decided the board was getting cluttered. Some cards stayed up for years because nobody wanted to be the one to remove the tortoise. Some came down within days. The board maintained itself through a slow informal consensus that left no record of what it had looked like the week before.

This is the part that interests me. A village in 1986 had a working memory that existed only in the present tense. You could not consult the noticeboard of last March. You could only consult the noticeboard of now, and the noticeboard of now contained whatever had survived since you last looked. The full texture of who in your street needed what, who was teaching what, who had lost what, was readable only by being there, and was unreadable forever the moment you weren't.

Replacements exist. The local Facebook group does roughly the same work, with infinitely more reach and an indelible archive of every cruel comment ever made about somebody's missing cat. Nextdoor performs a caricature of it. Both are searchable, both persist, both make the original noticeboard look quaint by comparison. Neither produces the same object, because the object's defining property was that it would not last. The noticeboard told you what your neighbours needed this week, and accepted that next week would need its own.

The wooden cases mostly survive. I see them still on village halls and outside the older library branches, their cork half empty, holding a single bus timetable and a poster for a flower show that happened in 2019. The pins are still there. The hands that used to put things up have moved indoors, onto screens, into feeds that never quite forget anything. The board waits anyway. A piece of public furniture for a kind of public attention that no longer collects in that shape.

There was a moment, roughly between 1983 and 1987, when a serious AI researcher worked at a Symbolics. Not on one. At one. The machine was the workstation, the operating system, the editor, the debugger, the version control, the inspector, and the language all at once, and the language was Lisp from the microcode up. The LM-2 in 1981 was the first commercial repackaging of MIT's CADR design, and by the time the 3600 line shipped you could buy a desk-sized Lisp environment with over five hundred thousand lines of system code written in the same language you were writing your own code in. Down to the kernel. That is still an extraordinary thing to think about.

Symbolics was a spinoff from the MIT AI Lab, one of two companies that came out of a hacker schism around the turn of the decade, the other being Lisp Machines Inc. Symbolics got most of the hackers and most of the money. For a few years the bet looked obviously right. The Defense Advanced Research Projects Agency had decided that expert systems were a route to military advantage, and the Strategic Defense Initiative meant DARPA was buying. Symbolics machines went into labs and skunkworks and Star Wars feasibility studies. Revenues climbed. The company signed long real estate leases in California on the assumption the run would continue.

It did not. The mechanism is worth being specific about, because the standard summary, "AI winter killed it", obscures more than it explains. Two things happened in parallel. The first was that expert systems, the thing Symbolics had been sold as the platform for, turned out to scale badly. Rules accumulated, interactions between rules produced surprises, knowledge engineers were expensive, and the systems could not learn. The second was that Sun Microsystems and the rest of the RISC workstation industry caught up on raw compute and then surpassed Symbolics on price-performance, while compiler people figured out how to make Lisp run respectably on general-purpose silicon. A purpose-built Lisp machine had been the only way to run Lisp fast; once it wasn't, the entire commercial premise dissolved.

DARPA noticed before the company did. Funding cuts started biting in 1987. Russell Noftsker, the co-founder running operations, ended up in a power struggle with Brian Sear, the CEO the board had hired in 1986, over whether to pivot to selling Lisp software that ran on Sun boxes or double down on Symbolics' superior hardware. The board fired both of them. Sales fell off a cliff, the California leases turned into millstones, and Symbolics filed for bankruptcy in early 1993. A small remnant company kept maintaining Open Genera, a virtual machine version of the OS, for the customers who could not afford to migrate off it. By 1995 the Lisp machine era was over.

The instructive bit is that no single decision killed Symbolics. The technology was genuinely impressive. The customers were real. The leadership had founder energy and MIT pedigree. What killed it was the assumption that a specialised hardware platform could remain the cheapest way to run a particular kind of software, in a decade when general-purpose silicon was doubling in capability roughly every eighteen months. The platform was a moat that was also a clock. Every Moore's Law tick narrowed it.

You can see the same shape now in the argument over whether GPU accelerators stay a category, or whether the workload that currently justifies them gets absorbed by whatever comes next. Specialised hardware is enormously valuable while the gap is wide, and a liability when it narrows. The companies that bet on the gap staying wide are the ones who sign the California leases. There is no indication this lesson generalises, and every indication it does.

The laminated A4 sheet appears on the lamp-post outside the corner shop sometime in the night, and within a week the rain has buckled the plastic pouch and turned the photocopy blue at the edges. The notice is addressed to nobody in particular and to every adult in the postcode at the same time. A six-line description of the proposal in the flat register of development-control prose, the address of the site, the place where the full application can be inspected, and a date by which any written representation must be received. Twenty-one days from the date of first display, which is the statutory minimum councils must allow before they can determine an application.

The strange part is that the notice is the building's own ghost made visible before the building has gone anywhere. The shopfront is still trading. The Victorian terrace still has its tenants. The car park still has cars in it. And yet the sheet on the pole, in its unread and weatherproofed way, is already describing the place in the past tense, in the dry syntax councils use for things that have not happened yet and might not. Erection of a three-storey block of nine self-contained flats with associated parking, cycle storage, refuse store and amenity space. The proposal has not been approved. It may never be approved. But the sheet has introduced the future as a piece of municipal furniture, and the present has become the version of the street that the proposal will replace.

You can stand and read one of these for as long as you like and nothing will be clearer at the end than at the beginning. The description is technically complete. It is not legible in the sense of giving you any image of what will happen. The language is engineered to be neutral enough to survive an appeal. Active verbs are converted into nouns. Heights are given in metres above ordnance datum. Materials are described as proposed elevations finished in stock brick and standing seam zinc. The thing the prose refuses to do, by training, is to picture itself. You have to take the drawings down from the council's portal and find a planner who likes you to learn what the notice actually means, and even then it is provisional until the committee meets.

Telegraph poles get a different layer of paper. The Electronic Communications Code gives a broadband operator the right to put up a wooden pole of up to fifteen metres with only twenty-eight days' prior notice to the local planning authority, and no statutory requirement to consult the residents whose front gardens the pole will face. Some councils ask operators to laminate a courtesy A4 to the pole that is being installed, naming the next pole, the company, and a date. There is nowhere on the sheet for the householder to register dissent that would stop the installation. The notice is not asking. It is announcing. The grammar of the planning notice has been carried, intact, into a regime where the consultation period is decorative.

What this leaves on the British street is a continuous low layer of paper futures pasted onto its furniture. Most of the notices belong to applications that will be granted, often with conditions, and turned into the buildings they describe. Some belong to applications that will be refused, withdrawn, or appealed to inspectors and won on the third attempt two years later. Some belong to operators who will put the pole up regardless of what the council says. A few belong to proposals nobody at the council can later remember receiving. The sheet is taken down when the application is determined, or stays up until the rain unmakes the plastic and the staple lets go, or both at once. The street has by then long since stopped reading the lamp-post and resumed its own business, and the next sheet appears two doors down, addressed to the same nobody.

I think the unease they produce is not about the proposals themselves, most of which are unobjectionable infill that any honest assessment of the housing shortage would welcome. It is about the address. The sheet is written to a public that does not assemble to read it. The twenty-one-day clock starts on a day no one notices, runs through a window of attention no one has been given, and closes before most of the people the proposal will affect have understood that a clock was running. The notice is a working piece of democratic infrastructure that has been engineered to look exactly like litter. That is the trick the pole has learned, and it learned it long before any of us were paying attention.