Plutonic Rainbows

Montana's Silver Year

April 19, 2026 · uneasy.in/ef8f3ed

On 30 January 1991, Claude Montana showed his haute couture collection for Lanvin in Paris, and somewhere in the middle of it Yasmeen Ghauri walked out in a silver mesh hood and a white bubble skirt. The look now reads like the exact midpoint of a career: still built around the glamazon silhouette that had made him the King of Shoulders, but lighter, younger, flirting with the sixties Space Age revival that the earliest nineties briefly tried to make happen.

This was as good as it was ever going to get for him.

The Lanvin job had arrived in 1990 on the back of a decade nobody else had owned quite as completely. Broad shoulders, sculpted leather, the body treated like architecture. Dynasty borrowed it. Wall Street borrowed it. Working Girl borrowed it. By the end of the eighties, Montana's silhouette wasn't just a look, it was the look: the default shape a woman took when a film or a TV show wanted to signal that she was about to walk into a boardroom and win. Alexander McQueen would later credit him openly. So would Riccardo Tisci, Olivier Theyskens, Anthony Vaccarello at Saint Laurent, and Willy Chavarria. The DNA was load-bearing.

His Lanvin work earned him two consecutive Golden Thimbles (the Dé d'Or, the closest thing French couture has to an Oscar). Critics who'd doubted whether a ready-to-wear designer could handle the discipline of a 19th-century atelier were reportedly astonished. Pale green iridescent trench coats. Patterned dresses with ribbon hats. Embroidered leather panels and, controversially at the time, beaded T-shirts on a couture runway, which was roughly the couture equivalent of serving crisps at a state banquet. He'd smuggled his own vocabulary into the house and made it work.

Then the decade happened around him.

By 1993, Helmut Lang had shown the anti-shoulder collection that basically ended the era. Margiela was deconstructing linings and wearing them as outerwear. Calvin Klein was doing the thing where nothing happens and everyone calls it genius, which my post on his 1980s advertising tried to take seriously on its own terms. Nirvana had put a cardigan on MTV. Kate Moss was on the cover of British Vogue in a slip. The culture's tolerance for theatrical power dressing had collapsed almost overnight, and Montana's response was essentially not to have one. He kept working in his own register. Retailers started dropping him. The House of Montana was in receivership by 1997.

The retrospective question is whether anything from that Spring 1991 collection crossed into the wider decade it opened. The honest answer is: not directly. The nineties that followed belonged to Prada nylon, Miuccia's ugly sandals, Jil Sander trousers, and the kind of Calvin Klein minimalism that Azzedine Alaïa had already quietly predicted three autumns earlier in a roomful of black. Even Mugler, Montana's closest rival in theatrical silhouette, was being pushed toward the costume-piece end of his archive. Valentino had his own reckoning the same year, managing it more gracefully because he never really needed the shoulder to be doing the talking.

What survived, survived filtered. The militarised tailoring and exaggerated shoulder came back through McQueen in 1996, through Balenciaga under Ghesquière, through Tisci at Givenchy in the 2010s, through Saint Laurent under Vaccarello now. The debt is real. It just took twenty-five years to be paid in a currency anyone still recognised as spendable.

By 1994, the same silhouettes that had made him a god in 1988 looked like costume in a room that had decided it wanted clothes. It wasn't that Montana had stopped being good. It was that the weather had turned, and he was still dressed for the last one.

Sources:

Cromptons of Ramsgate

April 19, 2026 · uneasy.in/62f3cf1

The cabinet on the end of the row at Skegness was built before I was born. A two-penny coin slot, a sloped tray of copper, a hydraulic shelf shoving a tide of coins toward an edge that never quite spilled. The wood-effect side panel was patched with masking tape where someone had bashed it, probably more than once, and the back of the machine still ran on what looked like the original transformer. A boy in front of me dropped his last coin in. The shelf swept forward. Three coins fell. He cheered.

The Cromptons Penny Falls was first manufactured in 1964 in Ramsgate, with a refined version released by 1966. Decimalisation in 1971 retooled the slot. The euro changed nothing because it never came. The shift from one penny to two pence to whatever fractional unit will replace cash entirely has been, for this object, a series of cosmetic tweaks to a mechanism that was finished sixty years ago. Alan Meades, who wrote a social history of the British amusement arcade, calls them pivotal — the machines that, alongside the fruit machine, kept arcades solvent through the collapse of the seaside holiday and everything that came after it.

What's strange about the coin pusher is not the survival itself but the absence of any pressure to replace it. The software industry I work in cannot tolerate a system that hasn't been rewritten in three years. The financial system cannot tolerate physical currency at all if it can be helped. Yet a sweeping shelf in a Blackpool arcade, manufactured the year of Goldfinger, is still earning its keep. Nobody has built a better coin pusher because nobody needs to. The mechanism is correct. It performs the function exactly. The only thing it had to adapt to was the denomination of the coin.

The wider arcade is more layered than this. Penny pushers share floor space with light-gun shooters from the eighties, crane grabbers whose grip strength is famously calibrated to fail, and pre-decimal "old penny arcades" that have repositioned themselves as heritage attractions, charging entry to mechanical fortune-tellers and execution dioramas built between the wars. The original pioneer of all this was a Leeds mechanic named John Dennison, who started making working models in 1875 and supplied Blackpool Tower with around fifty machines that ran on its upper floors until the late sixties. Three of his daughters — Evelyn, Florence, and Alice — kept the business going. Alice did the mechanics. Most of what they built has been lost.

The point is not that the arcades are sad now. They are not. A wet Tuesday in October at Coral Island, Blackpool, is still a functioning piece of infrastructure for a child with a paper cup of two-pence pieces. The point is that almost nothing else in British public life has been allowed to persist on its own terms this long. Libraries get rebranded. Pools get demolished. Post offices close. The arcade survives because it was never institutionally important enough to be rationalised. Nobody was ever going to commission a five-year strategic review of what coin pushers are for.

Cromptons is still based in Kent, the same county the original prototype came out of. Coin pushers, in slightly varied cabinets, are still being sold. The mechanism is older than most of the people who built the rest of the seaside, and it does not appear to be going anywhere.

Sources:

Counting R's in Strawberry

April 18, 2026 · uneasy.in/1669a90

Ask a frontier model to count the letter 'r' in "strawberry." Often you'll get two. Sometimes three. Rarely with consistent accuracy across a hundred trials. This isn't a bug somebody hasn't fixed. It's a direct consequence of how text enters the model in the first place, and it explains a dozen other strange behaviours that cluster around counting, spelling, and arithmetic.

Language models don't read text. They read tokens, which are integers that index a lookup table. The algorithm most of them use to build that table is called Byte-Pair Encoding, or BPE. It was originally designed as a data compression scheme. Philip Gage wrote it in 1994 for compressing files. Sennrich, Haddow, and Birch adapted it for machine translation in 2016, and it's been the default across most major model families since.

The idea is simple. Start with individual characters. Find the most frequent adjacent pair in your training corpus. Merge them into a new token. Find the next most frequent pair. Merge. Repeat for tens of thousands of iterations. The result is a vocabulary full of common words and common subword pieces. "The" is one token. "ing" is one token. "Strawberry" might split into ["straw", "berry"]. Rare words fragment into more pieces.

Once the model is trained, it sees "strawberry" as two integers, not ten characters. No mechanism inside the transformer can reach inside a token to ask how many r's it contains. The letters are sealed inside the token the way pages are sealed inside a book you can only see the cover of. The model has, statistically, learned that strawberry contains three r's. It just hasn't learned it from the token sequence. It's learned it from surrounding text that happened to mention the fact. That knowledge is fragile, and it decays on uncommon words.

The arithmetic failures come from the same place. Numbers don't tokenize uniformly. "480" might be one token. "481" might be two. A four-digit number can split one way and the same digits rearranged can split another. Researchers using arithmetic as a diagnostic have found that when an answer has more digits than either input, accuracy on certain tasks collapses to under 10%. The model isn't bad at maths. It's being handed digit sequences in a shape it wasn't trained to work with.

The fix, in principle, is byte-level tokenization. Every byte becomes a token. No merging, no hidden letters. The tradeoff is sequence length. The same passage takes more tokens, sometimes many more. That means more compute, longer context windows, slower inference. GPT-2 went byte-level and paid the cost. Recent models use hybrid approaches: BPE for efficiency, special handling for digits, sometimes per-character processing inside the chain-of-thought. None of it is free.

What strikes me is how much of the model's apparent cognitive style is downstream of this one preprocessing choice. The blind spot for letters isn't a reasoning failure. It's the data format not including letters, most of the time. Change the tokenizer and you change what the model can notice.

The cost-per-task shift playing out across the industry is partly a reasoning-modes story, but it's also a tokenization story. The reasoning variants often break digits into individual character tokens during arithmetic steps, which inflates token counts for the same sum. The reason your cheap tier struggles with long division is the same reason your expensive tier's bill keeps climbing when you ask it to do the job properly. Both are paying, differently, for the fact that the default encoding hides the thing you want the model to count.

Sources:

Palette Icon, Canva Engine

April 18, 2026 · uneasy.in/315d589

On Friday, Anthropic launched Claude Design, the AI design tool I wrote about on Wednesday when it was still a single-source scoop in The Information. The product is now live as a research preview for Pro, Max, Team, and Enterprise subscribers, reachable via a palette icon on Claude.ai's left-hand navigation. It is powered by Opus 4.7. Figma dropped about 7% on the news. The market made the same mistake twice.

What actually shipped is neither of the two shapes I expected.

The question I raised on Wednesday was whether Claude Design would be hosted-only or API-accessible. A hosted product is a controlled experiment. An API-accessible one would reset the wrapper economy — the cohort of Lovable, Bolt, v0, Cursor builders who pipe prompts into frontier models and ship a UI on top of the response.

Anthropic shipped neither version cleanly. The product is hosted only, no API. But it isn't running on design infrastructure Anthropic owns. It runs on Canva's Design Engine. Output is exportable as PDFs, URLs, or PowerPoints, or handed off directly to Canva for drag-and-drop editing. Canva's own Create event was in Los Angeles the same day, where they announced Canva AI 2.0 and called it the biggest product launch in company history. Both launches were timed together, which is not how opportunistic partnerships work.

This is a third shape I didn't account for: a hosted-only product that gets reach through somebody else's installed base. Canva has distribution inside enterprise marketing teams. Anthropic does not. The partnership gives Anthropic that distribution without building it, and gives Canva a direct pipe into the frontier-model side Adobe has been slow to acquire. It's joint, not cannibalistic.

Which partially inverts the thesis. I argued Figma and Adobe were the wrong targets. That's still true; they trade in coordination and indemnified enterprise contracts Claude Design doesn't touch. I argued Lovable, Bolt, and v0 should be the ones panicking. The Register named Lovable explicitly as the shot-across-the-bow target. That half lands as predicted.

What I didn't see coming: Canva is the structural winner. The consumer-grade design generators (Microsoft Designer, Adobe Express's free tier) lose more than Figma ever was going to, because they don't have Opus sitting underneath their prompt box and they don't get the dual announcement billing. Opus 4.7 itself shipped a day earlier, framed in Anthropic's own launch materials as "less broadly capable" than the restricted Mythos. That framing makes sense now. Opus 4.7 is the commercial frontier with Claude Design parked inside it. Mythos is the internal model kept in reserve. The two launches rhyme in a single week because they are solving different problems in the same portfolio.

The interesting question is when the API arrives. A hosted-only Claude Design is a controlled experiment. A Canva-backed Claude Design is a distribution play. A Claude Design with an API, and maybe a Canva-rendered API, would be the real wrapper-layer displacement. None of the coverage I've read this morning says anything about API access. Anthropic's research-preview framing keeps all of that future-tense.

The signal I was waiting for on Wednesday has shifted. It's no longer "what does Anthropic do about the wrapper economy." It's "what does Anthropic do with Canva six months from now."

Sources:

Cut Along the Dotted Line

April 18, 2026 · uneasy.in/fd6e237

The coupon was usually in the bottom corner of the right-hand page, bordered with a dashed line and the instruction to cut here. You cut. You filled in your name and address in capital letters. You walked to the post office with a parent or on your own if you were old enough, stood in the queue, and asked for a postal order for one pound ninety-nine. The woman behind the grille filled in the amount, stamped it, and handed it across with a receipt. You folded the order into an envelope with the coupon, stuck on a second-class stamp, and dropped it into the pillar box on the way home.

Then you waited.

The waiting is the part that has become unrecoverable. Most small ads specified "please allow 28 days for delivery," and that figure was realistic rather than padded. The ad you'd torn out lived in Exchange & Mart, or the back pages of Roy of the Rovers, or somewhere inside Smash Hits. The company processing your order might be one man operating out of a garage. Your postal order had to clear. The catalogue had to be printed. Stock had to be located. The padded envelope came back eventually, franked by a post office hundreds of miles away, the address scrawled in a handwriting you'd never seen.

In the month between sending and arriving, the object lived entirely in your head. X-ray specs that saw through skin. Sea monkeys that performed synchronised dances. A magic set whose tricks the advert had strongly implied would fool everyone. The mental image grew more specific and more extraordinary the longer the padded envelope took. You could not check on its progress. There was no tracking number, no notification of dispatch, no photograph of the warehouse worker who'd packed it. The order entered a system and disappeared from view, and your imagination filled the silence.

When the padded envelope arrived, the object inside could not win. The X-ray specs were pieces of plastic with cardboard lenses that made everything look striped and red. The sea monkeys were brine shrimp that hatched to roughly the size of a comma. The magic set came with trick cards you could see through in good light. You held the thing in your hand and felt the distance between the copy in the advert and the object the padding had protected. Then you played with it for an afternoon and mostly forgot.

Nostalgia is not the right register for any of this. The objects were nearly always a let-down. What has disappeared is not the stuff but the structure of expectation the stuff was suspended inside. A whole month of specific, named waiting, knowing exactly what you'd ordered and unable to retrieve or cancel or check. The desire had time to become baroque before meeting reality.

The small ads themselves have mostly vanished from regional press. Their mail-order equivalents migrated to online storefronts that list, illustrate, price, and review everything in one page without requiring you to tear anything out of anywhere. The padded envelope has been replaced by the brown Amazon box, which arrives on a schedule you can track hour by hour. That the product inside is often the same plastic tat imported from the same factories is beside the point. Next-day delivery cannot sustain the same quality of imagining. The real object arrives before the imagined one has started to grow.

Plastic tricks and broken toys still turn up in charity shops and at car boot sales, slipped from their time but intact. The X-ray specs outlast the magazine that advertised them. Someone ordered them in 1983 and kept them in a drawer. The padded envelope is long gone, but the object still carries the shape of something that was waited for. An artefact that came through the post moves on differently from one that came over a counter. It always contained an interval.

A postal order can still be bought at any British post office. I don't know anyone under forty who has ever held one.

Sources:

Cheaper Per Token, More Per Task

April 17, 2026 · uneasy.in/b4693c3

The sticker price of a frontier model has been falling for eighteen months. The bill I run up using one has not. Both are true, and they are both true for a reason.

Per million input tokens, GPT-5.4 Standard is $2.50 and $10 on the output side. Claude 4.6 Sonnet sits at $3 and $15. Gemini 3.1 Pro is $1.25 on input, with the output price landing somewhere between $5 and $12 depending on the table you trust. Eighteen months ago the comparable tier was meaningfully higher. At the budget end the collapse has been more dramatic. GPT-5 Nano is $0.05 in, $0.40 out. Gemini 3.1 Flash-Lite hovers around $0.10 and $0.40. DeepSeek halved its prices in late 2025 and the copycat pressure has not let up. If all you are doing is matching 2024 workloads to 2026 models, you are paying less.

That is the sticker answer. The receipt answer is worse.

The first thing that moved is the premium tier. GPT-5.4 has a High Reasoning mode that runs $10 in, $40 out — roughly 16× the standard tier for the same provider, same parent model, just with the thinking dial turned up. A Claude Opus Fast Mode clears $30 per million input tokens. Long-context windows, the big selling feature of 2025, became a billing surface: GPT-5.4 doubles input pricing beyond 272K tokens and adds 1.5× on output, and Gemini 3.1 Pro doubles input beyond 200K. Anthropic, to its credit, removed its long-context premium on March 13; the full 1M window bills at standard rates now.

The second thing is the token count itself. Gemini 3.1 Pro's chain-of-thought reasoning generates internal tokens billed at output rates, and a simple prompt can consume three to five times more tokens than expected. This is the quiet version of a price hike. You did not pay more per token. You paid for more tokens. Any workflow that shipped in 2024 with a predictable output length is now spending meaningfully more on the same question if the model is thinking before answering. Which it will be, because every provider is pushing you toward the reasoning variants as the default for serious work.

Third is where most of the enterprise analysis actually lands: context caching. Both platforms discount cached reads heavily, up to 90% off base rates on repeated context. If your workload has a stable system prompt and repeated document context — customer support, code assistance, document processing — the effective per-million blended rate can compress substantially. If your workload does not — agentic tools that spin up fresh contexts, one-shot research queries — the cache discount saves you nothing. The bill diverges based on access pattern, not sticker price.

Against all of that, the budget tier deserves its own column. A Gemini 3.1 fast variant at $0.075 in, $0.30 out is not a frontier model. It is a utility-grade language model that happens to be smarter than GPT-4 was two years ago. That tier has collapsed so far below the frontier that calling any of this a "price rise" misses the entire rearrangement. For high-volume, low-stakes work, the cost per task has fallen by an order of magnitude. For frontier-quality work on harder tasks, the cost per task has held steady or climbed.

I suspect this is what the providers want. The price floor drops aggressively enough that casual users move on sticker alone. The premium ceiling goes up just as aggressively, and the people who have actual hard problems — research, production coding agents, long-horizon reasoning work — end up on the tier where the margin actually lives. Between the two, the flagship standard tier holds a middling price that lets the pricing page look competitive without giving anything away.

The honest answer, then: per token, no. Per unit of intelligence applied to a specific task, probably yes for anything hard, and flatly yes if you are using the reasoning modes the providers are quietly making default. The budget I set in 2024 for a particular agentic task has to stretch much further on 2026 Opus at $5 and $25, because the agent thinks three times as hard before producing the same output and the output itself is longer. That is not a price rise. It is also not a price cut. It is the industry offering a cheaper ruler and then giving you longer things to measure.

A ruler I keep thinking about: the automated alignment researchers Anthropic ran cost $18,000 in compute for nine Claude instances running for five days. A year ago that per-token figure would have been higher. I doubt the total would have been lower.

Sources:

Eight Years, No Walkout

April 17, 2026 · uneasy.in/ff52552

Google is negotiating with the Department of Defense to let the Pentagon run Gemini on classified networks, The Information reported on Thursday. Reuters, Engadget, and a handful of others picked it up the same day. The proposed contract reportedly carves out two exclusions: no mass domestic surveillance, no autonomous lethal weapons. It is, in shape, the OpenAI deal.

That framing is the story.

What Google already runs inside DoD is larger than I realised. Since December, the GenAI.mil portal has given Gemini to around 1.2 million Defense Department staff across a user base of more than three million. Roughly forty million prompts and four million documents have gone through it. Eight pre-built agents handle work the Pentagon apparently considers administrative: meeting notes, budgets, sanity-checks against the national defense strategy. There's a feature called Agent Designer that lets personnel build their own agents in plain English. None of that is classified. It is also not nothing.

The new deal is the next step. Same infrastructure, cleared for secret and top-secret environments. The Under Secretary of Defense for Research and Engineering was quoted saying expansion talks are "underway."

Eight years ago this would not have happened. In 2018 Google pulled out of Project Maven, the drone-footage computer-vision contract, after employee protests. The company declined to renew it.

The two new exclusions, mass domestic surveillance and autonomous lethal weapons, are the same two items Anthropic refused to drop in February, when the Pentagon blacklisted them for keeping those commitments. Hegseth gave Amodei a Friday deadline; Amodei refused; the company was designated a supply chain risk. OpenAI accepted the terms Anthropic wouldn't and kept its contract. Google, eight years after walking away, is now pitching itself on roughly that middle ground.

It is a narrower position than 2018 Google held. It is a wider position than February Anthropic held. In the current window, it is where the business lives.

The part I keep circling is the silence. In 2018 the Maven protest was a company-wide story with a visible fracture line and a public exit. This week's news is a Reuters summary citing an Information scoop, picked up through the wire services, noted by industry press. There's no internal petition making the rounds. No engineers are speaking anonymously to the Times. The deal and its terms are being negotiated in the normal way, which is to say without anyone getting in the way of it.

That might be because the workforce has changed. It might be because what looked plainly wrong in 2018, helping the military see, has been reclassified as ordinary productivity software that happens to have some optional national security use cases attached. The agents summarising budgets look very much like the ones Anthropic was meant to be, before the February argument.

I don't think this is the same company that walked away from Maven. The contract terms say something Google once said it wouldn't sign. The absence of a visible fight says the company isn't planning to argue about it.

Sources:

Rosalind Without the Promises

April 17, 2026 · uneasy.in/447e0f1

OpenAI released GPT-Rosalind yesterday — the first entry in a new "Life Sciences" model series, gated to a trusted-access programme for a handful of enterprise partners. Amgen, Moderna, Thermo Fisher, the Allen Institute, and Los Alamos National Laboratory are on the preview list. Named after the crystallographer who made DNA legible, the model ships in ChatGPT Enterprise, Codex, and the API, behind enterprise-grade security controls and the standard "no training on your data" clause.

The benchmark numbers are good. On BixBench, GPT-Rosalind scores 0.751 Pass@1. On LABBench2, it wins six of eleven subtasks. Against human experts on two representative tasks, it sits in the 95th and 84th percentiles. Reasonable results for a domain model built on top of the frontier reasoning stack.

But the interesting thing isn't the benchmarks. It's the language around them.

Read the announcement carefully. OpenAI doesn't say GPT-Rosalind will design drugs. The model is described as a tool to accelerate the early stages of discovery — evidence synthesis, hypothesis generation, experimental planning. That's the research-assistant frame, not the autonomous-designer frame. The Codex Life Sciences plugin talks to more than fifty scientific databases. The model reads papers, cross-checks datasets, drafts experiments. That is useful. It is not a cure.

Contrast that with the last five years of pure-play AI drug discovery. Exscientia, Recursion, BenevolentAI — the three companies that raised the most money on the premise that AI could find drugs faster — have all had their first clinical readouts. All three were negative. Recursion absorbed Exscientia. BenevolentAI has been in retrenchment. The sector is sitting on roughly a billion and a half in market cap and has approved zero drugs. UCL's Peter Coveney, cited in a recent Nature piece, has made the structural case: discovery isn't the bottleneck. Validation is. You can generate ten thousand candidate molecules. Testing them is the part that takes a decade.

GPT-Rosalind isn't promising to solve validation. It's promising to make the scientists who do validation a little faster at reading papers. That's a smaller claim. It might also be a correct one.

There's something honest about the framing. Opus 4.7 shipped yesterday with Mythos held back, carefully gated — the same instinct in a different domain. OpenAI's move here rhymes: trusted-access only, enterprise-only, a short partner list, no individual researchers, dual-use safety language that reads as if somebody who has read the risk literature wrote the announcement.

Whether this is restraint or marketing discipline is open. It's possible GPT-Rosalind is simply a harder model to sell on hype because pharma buyers have been burned too many times and know better. It's possible the trusted-access structure is there to keep the model from generating plausible-but-wrong bioinformatics claims at industrial scale.

Either way, it's the first new model family in a while whose launch language reads like it was written by people who watched the AI-for-biology narrative play out in public. Rosalind Franklin did careful work and died before seeing it credited. Putting her name on a frontier model is either a very nice gesture or a warning about what happens when you overstate.

Sources:

Left to Weather

April 17, 2026 · uneasy.in/4892ef6

The roof of a pagoda at Orford Ness is a pillow of shingle sat on top of concrete piers. That isn't decoration. If one of the WE177 initiators had gone wrong during a vibration test, the pillars were supposed to give way and drop the shingle-laden roof down onto the blast, smothering it from above. No fissile material was ever on site, only the conventional explosives that start the chain reaction. The buildings were designed on the assumption that they might, occasionally, explode.

The Atomic Weapons Research Establishment ran this Suffolk spit from 1953 until 1971. Britain's bombs were shaken, frozen, baked, and spun here before they were shipped to the deterrent. The specific pagodas — Laboratories E2 and E3 — went up in 1960 to test the WE177 and ET317. When the Ministry of Defence eventually cleared out, they took the equipment and not much else. In 1993 the National Trust bought the spit for conservation, inherited the concrete, and eventually adopted a policy they call curated decay.

It means: we will not restore these buildings, and we will not demolish them. We keep roofs from collapsing. We fence off the worst of it. The sea and the gulls do the rest. In 2023 the Trust sent a robot dog in to survey the interiors because the floors are no longer trustworthy.

Sebald walked through here in 1992 for The Rings of Saturn and wrote of feeling he was "amidst the remains of our own civilisation after its extinction." That line is quoted in every essay about Orford Ness because if you stand in front of a pagoda on a low cloud day, with the shingle crunching under your feet, you will probably think it yourself. The future the pagodas were built for, the one where we actually used them, did not arrive. The future that replaced it does not need them. They stand in a kind of double-negative tense, unused and unusable.

The pull toward the hauntological register is strong, but a stubborn counter-reading deserves weight too. Orford Ness is one of the largest vegetated shingle spits in Europe. For the avocets and the spoonbills, the pagodas are just another headland feature, colder than the rest. The Trust knows this. Half the reason the curated-decay policy works is that ripping the concrete out would wreck the ground underneath, which is older and more fragile than anything the MoD ever poured.

There's also the question of whether ruin aesthetics hide the politics of the places they prettify. Nothing went wrong here, which is the point. The bombs worked. Calling the pagodas beautiful in decay elides the fact that their decay is the eventual downstream of a successful deterrent, which is predicated on the possibility of cities burning somewhere else. A curated ruin is a ruin given a meaning it didn't have when it was working. You don't know whether to respect that or not.

The robot dog made it in and out. The floors held.

Sources:

Pierce's Verdict

April 16, 2026 · uneasy.in/3189f0b

In November 1966, seven scientists delivered a thirty-four-page report to three federal agencies that had been paying for machine translation research for a decade. The committee was called ALPAC, chaired by John R. Pierce of Bell Labs, and it had been asked to decide whether continued funding was justified. Ninety pages of appendices backed up the body of the report. The committee's conclusion was direct: machine translation was slower than human translation, less accurate, and more expensive. It recommended a pivot toward basic research in computational linguistics.

Funding collapsed within months. The Department of Defense, the National Science Foundation, and the CIA (the three agencies that had been sponsoring the work through the Joint Automatic Language Processing Group) effectively stopped paying for MT research. Graduate pipelines dried up. American MT labs closed or reoriented. The field survived mostly in Europe and Japan, where institutions drew different conclusions from the same evidence, and it did not meaningfully recover in the United States until IBM's 1990 statistical MT paper.

What makes ALPAC worth revisiting is not that it was wrong. On the facts in front of Pierce's committee in 1966, the report was largely correct. The rule-based systems being built with government money really were producing stilted output that needed heavy human post-editing to be useful. And the committee had found something sharper than performance numbers. The whole target was Russian-English translation, because the motivation was military intelligence, and the United States already had more human translators of Russian than it needed. The Joint Publications Research Service had four thousand contract translators on the books and was using an average of three hundred a month. A reasonable committee looking at a reasonable set of numbers concluded that the field was not delivering against a need that did not fully exist.

What makes ALPAC worth revisiting is that the committee's framing — compare what we have now against a human translator, ask whether it is cheaper — foreclosed a direction that, thirty years later, would turn out to be exactly the right one.

The statistical approach that rescued MT in the 1990s did not look like the systems Pierce was evaluating. It was not written by linguists. It was a probabilistic model trained on parallel corpora, which is to say, it won by being dumber and using more data. Rich Sutton's Bitter Lesson names the pattern: over seventy years of AI research, clever knowledge-intensive systems lose to methods that scale with compute. ALPAC sits in the pre-history of that pattern. The committee evaluated the clever systems honestly and killed their funding, which is, in the Sutton frame, exactly what should have happened. What Sutton does not say, and what the ALPAC story does say, is that the method which eventually wins can take decades to arrive.

John Hutchins's (in)famous report analysis argues the impact of ALPAC is often overstated: MT work continued quietly at Wayne State and the University of Texas through the 1970s, and European groups grew into the American gap. This is fair, and a useful correction to the tidy winter narrative. But the American pipeline did die. The Transformer paper, which finally cracked machine translation as a problem, arrived fifty-one years after ALPAC was filed.

A report is a compressed judgment. It takes a field as it finds it and asks whether the trajectory justifies the cost. ALPAC answered no, defensibly, and was right about the trajectory of the systems it evaluated. It just was not evaluating the systems that would win.

Sources: