CROFT.ing
A CROFT TERM

ENS

THE SIGNPOST

A polite acronym for how platforms rot.

THE SURFACE

ENS, sometimes pronounced "ins," is Croft's shorthand for enshittification, Cory Doctorow's name for the arc by which platforms decay from serving their users to consuming them. Deliberately, ENS has no single expansion: in the old free-software tradition of self-referential acronyms, it reads differently depending on where you stand, and every reading describes the same decline.

THE SOIL

The word problem. Doctorow named the pattern in 2023, and the word stuck because everyone recognized the thing it named: a platform is generous to its users until they are locked in, then squeezes them for its business customers, then squeezes the business customers too, keeping the extracted value for itself. The concept is indispensable. The word, though, is a room-clearer in exactly the rooms where the pattern gets decided: board meetings, procurement reviews, syllabi, budget lines. ENS is a passport. It carries the full concept across that border with its analytical content intact and its shock value checked at the door.

The tradition. ENS takes its shape from free software's habit of acronyms that refuse to sit still: GNU's Not Unix, WINE Is Not an Emulator, YAML Ain't Markup Language. The habit looks like a joke and functions as a philosophy: the name defines itself by what it refuses to be. So the root definition of ENS is recursive.

ENS is Not Service. Software as a Service makes a claim in its own name: that what you are buying is service. A platform that has crossed into ENS has quietly forfeited that claim. The subscription still bills, the uptime page is still green, but the system's real product is no longer the service rendered to you; it is the value extracted from you. ENS is Not Service is the recursive root, and the three expansions below are the same forfeiture seen from three chairs.

From the boardroom: Extractive Neglect Syndrome. This is the cause. At some point a platform's operators shift strategy from value creation, making the product better so people choose it, to value extraction, monetizing the people who can no longer easily leave. Extraction gets the engineers, the roadmap, and the OKRs; the core product gets neglect, and the neglect is not an accident but a reallocation. If you sit where budgets are set, ENS is the name for that reallocation.

From the machine room: Eventual Non-utility State. This is the mechanic, and it is a deliberate play on eventual consistency, the distributed-systems promise that replicas, left to themselves, converge on agreement. Offered in the same spirit as the industry's other satirical laws: a centralized, investor-fed platform, left to itself, converges too, on a state of zero utility for the person using it, as each quarter's re-engineering serves the payer a little more and the user a little less. Engineers watch this convergence from the inside, one migration at a time. If you sit at the architecture diagram, ENS is the name for the attractor.

From the interface: Erosive Nudge Syndrome. This is the symptom. Design research gave us the nudge, a gentle default that helps a person do what they already meant to do. ENS inverts it: the erosive nudge wears the user down instead. Consent walls rebuilt weekly, sponsored rows dressed as results, the cancel flow that takes six screens while the upgrade takes one, the setting that resets itself. No single cut is worth complaining about, which is the design. If you sit in front of the product, or in front of users, ENS is the name for death by a thousand nudges.

One arc, three chairs. The three expansions are not competing definitions; they are the same failure observed from the boardroom, the machine room, and the chair in front of the screen. That is the diagnostic use of the term: notice which chair the person across from you is sitting in, and offer the expansion that describes their view. The executive hears a strategy critique, the engineer hears a systems law, the designer hears a pattern audit, and all three are now discussing the same disease, in a word that can be said in any of their meetings.

Why a vocabulary at all. The point of the polite acronym is not politeness; it is admissibility. A pattern that cannot be named in the rooms where it is decided cannot be refused in those rooms either. And naming is only half of Croft's interest. The other half is construction: the pattern has structural preconditions, and software can be built without them. arecipe is the working experiment, and its treatise is that one app's account of its own ENS-resistance, walked precondition by precondition.

THE BEDROCK