EIFFEL STATE / AI & SOCIETY
The abundance paradox of generative AI

The Eiffel State Building

When everybody can build an Eiffel Tower, an Empire State Building—or both—who is left to visit? The next AI problem may not be whether we can create. It may be whether we can coordinate.
By Robert Harvey Curtis (rhc) · August 2026 · Research and production assisted by AI
The Eiffel State Building hero infographic, a fanciful Eiffel Tower and Empire State Building hybrid beside the London Eye at dusk
The Eiffel State Building: infinite building capacity meets finite attention. Hero concept and direction by Robert Harvey Curtis; image generated with AI.

We solved the hard part. That may be the problem.

For most of the history of software, the first question was simple: Can we build it? A serious system required programmers, architects, testers, security specialists, project managers, servers, capital, time and the patience to coordinate all of them. The difficulty of production acted as a filter. Most ideas never became products because building was expensive.

Generative AI changes that equation. A technically experienced person can now describe a system, ask an AI to construct it, test it, inspect it, harden it, extend it and sometimes ask another AI to critique the first. The human may never type the code personally. The job becomes closer to architecture, orchestration, judgment and verification than traditional line-by-line programming.

A small real-world parable. A builder can spend a few days learning a new AI-assisted development environment, half a day getting a first system working, another half day expanding and debugging it, then have a technically minded friend run an independent AI review over the source. The review opens issues; the builder AI reads the issues and repairs the important ones. Two experienced humans remain deeply involved—but neither needs to write the implementation by hand. Twenty years ago this might have required a small team and a project plan. Today it can happen over a long weekend.

That is extraordinary. It is also the beginning of a new economic problem. If one person can do this, millions eventually can. The scarcity that protected each builder from millions of competitors begins to disappear.

AI can make production abundant. It cannot manufacture more hours in another human being’s day.
Old bottleneck
Building the thingCapital, labor, technical skill and time constrained supply.
New bottleneck
Getting anyone to careAttention, trust, discovery, relationships and shared purpose remain scarce.

This is the Eiffel State Building problem. Give everyone the power to build a landmark and the skyline fills with landmarks. But the number of visitors does not multiply merely because construction became cheap.

The literature is beginning to describe exactly this.

1
Attention was scarce long before AI. Herbert Simon’s classic argument was that abundant information consumes a finite resource: human attention. Modern attention-economy work continues to examine that constraint. Established idea
2
AI really is shifting software work toward supervision. A 2026 longitudinal study of professional engineers found less time spent writing code and a shift toward directing, evaluating and correcting AI output—what the authors call “supervisory engineering.” 2026 preprint
3
The “Builder Saturation Effect” now has a formal model. A 2026 paper explicitly models falling production costs, free entry and finite attention, predicting lower average attention and returns per builder as the number of builders grows. The author describes the work as synthesis and formalisation, so it should not be mistaken for settled empirical law. 2026 preprint
4
Volume can compete with preference. A 2026 study using data from tens of millions of users on a video platform reports a “scale-over-preference” pattern: AI-generated creators can achieve large aggregate engagement through output volume even where users prefer human-generated content. 2026 preprint
5
Private AI help can reduce public knowledge creation. Another 2026 model points out a subtle loss: when people solve problems privately with AI instead of asking and answering publicly, fewer reusable solutions enter the shared archive. 2026 preprint

The central idea is therefore not speculative in the loose sense. Several established theories point in the same direction, and current researchers are now applying them directly to generative AI. What remains uncertain is the magnitude: how fast builder saturation will occur, which markets will be most affected, and what new institutions will emerge in response.

Social networks are the cruelest example

A word processor can be valuable to one person. A private database can be valuable to one company. A social network is different. Its value depends heavily on who else is there. A technically superior network with three people may be less useful than an inferior network containing everyone you know. That is the logic of network effects and the cold-start problem.

So a creator can build something that is, feature for feature, “ten times better than Facebook” and still discover that the active population is the creator, a test account, a daughter and two patient friends. Nothing paradoxical happened. Technical quality and network utility are different variables.

A magnificent empty nightclub can still lose to the shabby club across the street—if everybody’s friends are across the street.

The builder may also stop being a consumer

There is an additional hypothesis worth testing. When people spend more of their leisure time building their own AI-generated systems, songs, games, feeds, videos and communities, that time is no longer available for consuming everybody else’s creations. AI could therefore increase supply while simultaneously consuming some of the demand.

average attention per creation ≈ available human attention ÷ number of competing creations

If AI drives the denominator sharply upward while builders spend more time creating and less time consuming, the pressure becomes stronger still. This particular builder-as-consumer effect is a reasonable inference, not yet a verified population-scale conclusion.

How many wheels can we reinvent?

The absurdity becomes visible with a toy calculation. There are more than eight billion people on Earth. We do not need all of them building. Move the slider and imagine only a fraction independently receiving the same perfectly sensible instruction from their own AI: “Build me a simple community platform.”

1%
This is illustrative, not a forecast.
Using a deliberately rounded population of 8 billion:
80,000,000
independently built “wheels” competing for overlapping users, contributors and attention.

The point is not that eighty million identical social networks will literally appear. The point is that production capacity can grow far faster than coordination capacity. The same duplication can happen at smaller scales inside companies: ten departments independently building ten AI assistants for the same workflow because each can now do so cheaply.

So how do we stop building eighty million wheels?

The solution is not to take AI away from builders. That would throw away one of the most useful productivity technologies we have developed. The solution is to make coordination as easy as creation.

We already know pieces of the answer. Open-source communities learned to coordinate large numbers of contributors through shared repositories, modular architecture, maintainers, issue trackers, standards and reuse. Research on open-source software has long emphasized that modularity and coordination allow many people to contribute without each recreating the entire system. More recent work on open AI ecosystems likewise describes pooling resources and reuse as ways to avoid duplicated effort.

Search before build

Before an AI generates a new product, it should first ask: Does this already exist? Not merely “can I write the code?” but “what projects, libraries, standards, datasets or communities already solve 70–90% of this?” Discovery should become a mandatory first phase of AI creation.

Default to contribute before fork

If an existing project is close, the AI should offer to contribute an enhancement, plugin, pull request, translation, test suite or adapter before proposing a complete replacement. The default question becomes: Can we add one floor to the existing tower instead of constructing another tower next door?

Build interoperable pieces, not isolated kingdoms

Minimal common standards, portable identities, shared APIs, open data formats and reusable modules let independently built systems cooperate. Current research on collaborative agentic AI is making the same argument: interoperability and minimal standards are necessary to prevent fragmentation.

Create a “wheel registry” for AI projects

Imagine a machine-readable global directory of active projects, capabilities, owners, licenses, APIs, maturity, open issues and desired collaborators. An AI could query that registry before creating anything substantial and say: “Seventeen teams are already building this. Three need exactly your expertise.”

Reward merging, maintenance and reuse

Today prestige often goes to founding something new. The next economy may need stronger rewards for integrating, documenting, testing, maintaining, standardizing and combining existing work. These are the activities that turn abundance into infrastructure.

Make AI a matchmaker, not merely a builder

The same AI capable of creating a product can compare goals across people. With appropriate privacy and consent, it could identify complementary teams, overlapping projects and reusable work. The most socially valuable AI may be the one that occasionally says: “Do not build this yet. I know three people you should meet.”

Preserve the public commons

When an AI privately solves the same problem for a million individuals, society may pay for the same reasoning a million times and retain none of it. Systems should make it easy—where privacy permits—to promote useful answers, components and lessons into shared knowledge bases that the next person can reuse.

The proposed shift

From artificial intelligence to coordinated intelligence.

The first generation of generative AI asks, “What can I make for you?” The next generation should also ask, “Who else is already working on this, what can we reuse, and whom should we bring together?”

The scarce resource after abundance

If implementation becomes cheap enough, value migrates upward. The important skills become choosing the right problem, discovering what already exists, establishing trust, attracting collaborators, integrating components, creating standards, building communities and deciding what not to produce.

That does not make human beings less important. It makes the particularly human parts—purpose, taste, judgment, social trust, responsibility and cooperation—more important. AI can produce an enormous number of technically plausible answers. Humans still have to decide which answers deserve a shared future.

The question after “Can everybody build an Eiffel State Building?” is not “How do we stop them?” It is “How do we help them discover that somebody else already poured the foundations—and might welcome a partner?”

There may eventually be AI agents consuming services from other AI agents, which would expand demand beyond human attention. But even that future creates another coordination problem: agents need protocols, identity, trust, discoverability and incentives to cooperate. Scarcity does not vanish. It moves.

A practical rule for the AI age

Before creating anything significant, ask five questions: Does it exist? Can I reuse it? Can I contribute to it? Can I interoperate with it? Who should I build it with? Only then ask the old question: How quickly can AI build it?

That is how we keep the extraordinary democratization of AI without turning the digital world into a skyline of empty Eiffel State Buildings—each sparkling beautifully, each maintained by its owner, and each wondering where all the people, jobs and money went.

Research notes & sources

Evidence status: The article deliberately distinguishes established economic ideas from recent working papers and preprints. Several 2026 sources below are new and may not yet have completed peer review. They support the direction of the argument, but the “Eiffel State Building problem” and the specific coordination framework above are a synthesis and proposal, not a settled scientific law.
  1. Herbert A. Simon’s attention-scarcity argument is discussed in the UN’s Attention Economy brief and in later scholarship such as Heitmayer, “Second Wave of Attention Economics” (2025).
  2. Brynjolfsson, Li & Raymond, “Generative AI at Work”, NBER Working Paper 31161. In a customer-support setting, access to AI assistance increased measured productivity.
  3. Vella & Blincoe, “The Impact of AI Coding Assistants on Software Engineering: A Longitudinal Study” (2026 preprint), reporting a shift from code creation toward verification and “supervisory engineering.”
  4. Catovic, “The Economics of Builder Saturation in Digital Markets” (2026 preprint), which formalizes the “Builder Saturation Effect.” The paper explicitly describes its contribution as synthesis and applied formalisation.
  5. Shi et al., “Scale over Preference: The Impact of AI-Generated Content on Online Content Ecology” (2026 preprint), using a longitudinal dataset of tens of millions of users.
  6. Zhang, “The Influence of Generative AI on Content Platforms: Supply, Demand, and Welfare Impacts in Two-Sided Markets”, modelling oversupply, information overload, traffic concentration and long-tail effects.
  7. “When AI Improves Answers but Slows Knowledge Creation” (2026 preprint), modelling the loss of reusable public knowledge when problems are solved privately through AI.
  8. Maurer & Scotchmer, “Open Source Software: The New Intellectual Property Paradigm”, NBER Working Paper 12148, on architecture, modularity and coordination in open-source production.
  9. Linåker et al., “A Cartography of Open Collaboration in Open Source AI”, describing collaboration, resource pooling, reuse and avoidance of duplicated effort.
  10. “Collaborative Agentic AI Needs Interoperability”, arguing for minimal, battle-tested standards to avoid fragmented agent ecosystems.
  11. Song, Agarwal & Wen, “The Impact of Generative AI on Collaborative Open-Source Software Development”, finding productivity and participation gains alongside increased integration time—an example of productivity creating new coordination costs.