Home / Architecture  / Who Designs the Rules for a River?

Who Designs the Rules for a River?

Editorial photograph from an accessible hillside overlooking a vast hydropower reservoir in western Ethiopia’s Blue Nile.

A dam is never finished when its concrete sets. It is redesigned whenever someone decides how much water to store, when to generate electricity and what to release downstream. On the Blue Nile, the Grand Ethiopian Renaissance Dam makes that hidden architecture impossible to ignore. Ethiopia seeks electricity, industrial development and a break with an inherited regional hierarchy. Sudan and Egypt seek reliable water in a system where upstream decisions travel across borders. The dispute is not simply development versus conservation. It is a contest over who can make their own future more predictable—and whose future becomes collateral.

ArchDaily’s account frames the project as both monumental engineering and a challenge to colonial-era Nile arrangements. Architecture should take that challenge further. The dam’s operating rules are not paperwork attached to the infrastructure. They are part of its design.

PRO: Development Cannot Remain a Downstream Privilege

The strongest argument for Ethiopia’s dam begins with an intolerable asymmetry: contributing water to a river system has not historically guaranteed an equivalent voice in governing it. The 1929 Nile agreement privileged Egyptian interests within a colonial framework; the 1959 agreement between Egypt and Sudan allocated the river’s waters between those two states without Ethiopia’s participation. These are different instruments, but neither provides a defensible template for treating upstream development as permanently subordinate.

Electricity is spatial infrastructure. It determines whether a clinic can refrigerate medicines, whether a workshop can run machinery and whether a household must organize its evening around fuel rather than light. Hydropower can support Ethiopian cities and manufacturing, while regional electricity trade can extend benefits beyond the national border. Transmission networks, affordability and distribution investment determine who actually receives those benefits. Still, dismissing generation as a prestige project erases the material deprivation it is intended to address.

The architectural comparison is Ghana’s Akosombo Dam: a powerful development symbol whose electricity enabled industrial ambitions, but whose construction also displaced communities and transformed livelihoods. Its lesson is not that electrification is illegitimate. It is that megawatts cannot stand in for a complete social brief. As with Santiago’s trade-off between cheap housing and expensive distance, the headline benefit is not the whole social calculation. Ethiopia’s claim deserves recognition without granting any dam immunity from scrutiny.

PRO: Operating Rules Can Create Shared Benefits

Editorial photograph inside a modest metalworking workshop in an Ethiopian regional town, an electrician checking.

A hydropower reservoir does not consume water in the same way as an irrigated field. Much of the water passing through turbines continues downstream, although reservoir evaporation creates losses and storage changes the timing of flows. That distinction matters. Treating every cubic metre stored as permanently stolen obscures the real design questions: when storage occurs, how long it lasts and what happens when rainfall disappoints.

Seasonal regulation can potentially moderate damaging floods in Sudan, reduce sediment reaching downstream infrastructure and make flows more predictable. Those benefits are conditional, not automatic. Sudan’s Roseires Dam, downstream on the Blue Nile, makes timely information about releases especially consequential. A forecast shared early enough to adjust reservoir operations is infrastructure in its own right; the same forecast delivered after a release is merely an explanation.

Donella Meadows’s systems thinking offers a useful design reference: information flows and governing rules can be more consequential than changes to physical components. Applied here, the proposition is concrete. Agree on data exchange, distinguish ordinary seasonal operation from prolonged drought, and establish procedures for revising decisions as conditions change. Ethiopia need not abandon development to accept coordination. A negotiated operating system could turn national generating capacity into regional resilience—provided downstream security is treated as a design requirement rather than a diplomatic concession.

CONTRA: Storage Gives One State a Powerful New Clock

The strongest objection is not that Ethiopia should remain underpowered. It is that a vast upstream reservoir changes who controls time. Water that once arrived according to rainfall and river conditions can now be held or released through deliberate decisions. Hydropower may return water downstream, but a delayed release can still matter profoundly to irrigation schedules, drinking-water systems and the management of another reservoir.

With a total storage capacity of roughly 74 billion cubic metres, the Ethiopian reservoir is large enough that its operation cannot reasonably be described as a purely domestic matter. Capacity is not the same as annual consumption, and it does not establish that downstream harm is inevitable. It does establish that operating choices deserve scrutiny commensurate with the structure’s scale.

Egypt’s Aswan High Dam and Lake Nasser already provide substantial buffering against variable flows. That protection, however, is finite. During a prolonged basin-wide drought, maintaining storage upstream can shift pressure onto downstream reserves. Conversely, requiring Ethiopia to release large volumes regardless of reservoir conditions can constrain its generating capacity. No concrete cross-section resolves this distributional conflict.

Sudan’s position also resists a simple upstream-versus-downstream diagram. Flood moderation may be welcome, while uncoordinated changes in releases remain dangerous. Security depends on coordination, not merely geographical position.

CONTRA: An Operating Agreement Can Conceal Unequal Risk

Editorial photograph beside an irrigation canal connected to the Nile in rural Egypt, a farmer.

Calling for “cooperation” is easy. Designing cooperation that survives scarcity is the difficult work. An agreement based on average years can appear generous while leaving the central dispute untouched: who accepts losses during consecutive dry years, and who gets to define when the emergency starts? A fixed release promise may ignore changing hydrology. Unrestricted discretion may leave downstream users unable to plan.

The technical vocabulary can hide political choices. A drought trigger based only on one reservoir’s level protects different interests from a trigger based on basin rainfall, downstream storage or a combination of indicators. Post-drought refilling deserves equal attention: rapid recovery of upstream storage can prolong downstream stress after rains return. Each formula contains a theory of whose recovery comes first.

The Senegal River basin’s shared arrangements around projects such as Manantali offer a useful counterpoint: infrastructure benefits can be organized across states rather than understood exclusively as territorial possessions. The institutional model cannot simply be transplanted to the Nile, but it punctures the claim that sovereign ownership is the only imaginable architecture.

A credible Nile design needs accessible monitoring, agreed drought indicators, coordinated drought-response and recovery procedures, and a dispute process that works before damage becomes irreversible. As in debates over who gets a say before a luxury resort is built, the process must account for people who bear consequences without controlling decisions. Neither historical dependence nor upstream sovereignty should function as a blank cheque.

The Real Design Brief: Make the Risk Visible

Architectural representation usually gives us the heroic section: wall, reservoir, turbines, foundations. For this project, the more revealing drawing would show a sequence of dry years. It would trace reservoir levels, electricity output, downstream releases and the communities exposed to each decision. It would distinguish uncertainty in the weather from discretion in the control room.

Keller Easterling’s writing on infrastructure space helps identify what the monumental image leaves out: rules and protocols actively organize territory. Here, the territory extends from Ethiopian electricity networks to Sudanese farms and Egyptian water systems. The relevant design object is not just a dam but a relationship among reservoirs, institutions and users.

The position worth defending is therefore neither “build at any cost” nor “preserve the old allocation.” Ethiopia’s development claim is legitimate; downstream vulnerability is real. The obligation is to expose the trade-offs rather than bury them beneath nationalist imagery or reassuring engineering language. Publish operating principles, test competing drought scenarios and explain who bears the losses under each. A structure this consequential should not have an invisible constitution.

FAQ

Why are reservoir operating rules part of architectural design?

They determine how the structure performs across time: what it stores, when it releases water and how it responds to scarcity. Those choices distribute benefits and risks beyond the construction site, making them fundamental to the infrastructure’s design.

Does generating hydropower permanently remove Nile water?

Water passing through turbines generally continues downstream. However, evaporation causes losses, and filling or replenishing a reservoir temporarily retains water. The timing of storage and release can therefore be consequential even without irrigation withdrawals.

Why do Egypt and Sudan have different concerns?

Egypt depends heavily on the Nile and has substantial storage at Lake Nasser. Sudan sits closer to the Ethiopian dam and could benefit from moderated floods, but coordination with its own dams and timely release information are especially important.

What should a drought operating agreement cover?

It should address shared monitoring, drought thresholds, coordinated release and storage decisions, and procedures for resolving disagreements. It also needs post-drought recovery rules, because rebuilding one reservoir’s reserves can extend pressure elsewhere.

If every release protects one future while constraining another, who should have the authority to write—and revise—the river’s rules?

Watch the Mainifesto Short

Watch on YouTube

Enjoyed this perspective?

Get the Mainifesto weekly — curated design debates, speculative ideas and the week's best articles every Saturday.

Editorial Perspectives

Questions and counterpoints developed by the Mainifesto editorial desk to extend the discussion.

Perspective 1

I’m for jointly designed operating rules: electricity revenue means little if the release schedule makes downstream water supplies impossible to plan around. Ethiopia, Sudan and Egypt should share authority over those rules, with clear drought triggers and a revision process that doesn’t require a diplomatic crisis every time.

Perspective 2

I’m against treating this primarily as a design problem; Aswan should have cured us of the idea that a dam is merely an instrument awaiting better instructions. The operating rules constitute political power, not a user interface, and no elegant protocol can substitute for a legitimate settlement over who bears the losses.

Perspective 3

Before assigning authority, I’d want to see competing release schedules tested against multiyear droughts, electricity demand and downstream irrigation needs. A joint body needs shared monitoring data, published thresholds for revising the rules and a formal route for affected communities to challenge decisions. Otherwise, ‘adaptive management’ can become a polite name for moving the goalposts.

NO COMMENTS

POST A COMMENT