Addis Ababa decided it had waited long enough. On 9 September 2025, Ethiopia’s prime minister stood at the Grand Ethiopian Renaissance Dam (GERD) and turned on Africa’s largest hydropower plant. State television showed the turbines rotating above the Blue Nile gorge. In the capital, people celebrated with flags. The moment carried the force of a national declaration. For fourteen years, Ethiopia had been told that the dam was too risky, too unilateral and simply too large. Now, with the turbines running, it seemed to be saying that the debate was over, or at least that it would no longer wait for everyone else to agree.
Cairo saw it differently. Egypt’s foreign ministry issued a diplomatic note, calling the dam an illegal project built and operated without agreement. It repeated the demand that Ethiopia has heard for more than a decade, the two countries must first reach an agreement on how the reservoir will be filled and how the dam will be operated?
Egypt’s fears are not difficult to understand. The Nile provides around 97 per cent of its freshwater. Under the 1959 agreement between Egypt and Sudan, Egypt receives 55.5 billion cubic metres of the river’s annual flow, a figure the two countries reaffirmed in August 2025. But Ethiopia was not part of that agreement though it signed a Nile Dam agreement on March 2015 with Egypt and Sudan regarding GERD.
It rejects the notion that a deal made by two downstream countries can bind an upstream state that supplies most of the Nile’s water. Both sides believe they are defending a legitimate interest. Egypt sees the river as a matter of national survival, Ethiopia sees the dam as a long delayed path to electricity, development and greater control over its own resources. Yet beneath the legal arguments and diplomatic language lies a simple reality, only one side controls the valve.
For ordinary people living along the river, the uncertainty remains. An Ethiopian villager near the dam may now have electricity for the first time, and a government that can finally point to something tangible. But a farmer in Egypt’s delta still has no way of knowing, from one season to the next, how a reservoir hundreds of miles upstream will be managed, who will control it, or what rules will govern its operation. The inauguration did not resolve any of those questions. If anything, it made them harder to ignore.
This is the final article in a series that has so far examined two uncomfortable stories about India. The first was about China beginning work on the world’s largest dam on the Brahmaputra, despite India’s objections, and without allowing those objections to slow the project down. The second looked at India’s decision to suspend the Indus Waters Treaty after the Pahalgam massacre. India had, arguably, assembled the strongest legal case of its kind in the treaty’s history. The tribunal nevertheless ruled against it.
In both cases, the side with the stronger argument lost. Ethiopia and Egypt now offer a third example. The question before this article is therefore not whether India’s arguments are persuasive. It is whether a persuasive argument can stop a dam, or any other piece of infrastructure, once the concrete has already begun to harden.
Put the three disputes side by side and a pattern begins to emerge, even though the legal circumstances are different in each case.
On the Brahmaputra, India never had a tribunal to turn to. There is no binding water treaty between India and China, only a data sharing arrangement that expired in 2023. So there was no court in which India could win or lose. China simply went ahead and built.
The Indus dispute was different. India had a substantive legal case. After the Pahalgam massacre, India placed the 65 year old treaty in abeyance, citing Pakistan’s sponsorship of the terrorist attack. It also refused to recognise the arbitration panel that Pakistan subsequently approached.
In August 2026, however, the panel ruled that the treaty remained fully in force and that India could not suspend it on its own. The ruling did not decide whether Pakistan’s conduct amounted to a breach serious enough to justify India’s position. India’s objection was directed mainly at the tribunal’s jurisdiction and at the parallel process taking place alongside it, not simply at the final decision. New Delhi rejected the ruling. But in practical terms, the treaty’s position remains unchanged.
The Nile offers a third variation. There was no tribunal and no court case, only fourteen years of negotiations that failed to produce a binding agreement on the dam’s operation. Egypt had the older treaties and the greater exposure as a downstream country. Ethiopia had the construction timetable, the money and, most importantly, the site.
These are three distinct legal disputes. Yet beneath the differences, the same uncomfortable fact keeps returning, in none of them did the state with the stronger documented grievance manage to stop, delay or legally bind the state controlling the infrastructure. A legal claim without the power to enforce it remains a claim. It has not become protection.
The idea is an old one. In 416 BC, an Athenian general told the people of Melos that the strong do what their power permits, while the weak endure what they have to. No one has to accept that as a moral principle to recognise how closely it still reflects the politics of dam building. A reservoir is not a warship, but it can alter the balance in much the same way: it changes what one side can compel the other to live with. That does not mean the upstream state is right. It means that, whatever the legal or moral merits of the downstream state’s case, the upstream state’s decision becomes much harder to disregard once the project is physically in place.
Law still matters. This article is not an argument for abandoning it. Law determines which claims can be treated as legitimate, how much reputational and diplomatic damage a project may inflict, and what sort of settlement might remain possible later. Egypt’s decades of diplomacy were not pointless; they are one reason Ethiopia continues to answer Cairo in legal and diplomatic language instead of simply ignoring it.
But law was never going to be the only safeguard. The mistake this series has followed, from the Brahmaputra, through the Indus, to the Nile, is the belief that it can serve as the principal one.
A water treaty is generally expected to do four things. Most are reasonably good at the first three. The fourth is where they often fall short.
First, a treaty sets out entitlements, who can use the river and how much. Second, it establishes procedures, advance notice, consultation, data-sharing and environmental assessment. Third, it provides a way to settle disputes, usually by naming a court, tribunal or other forum. The fourth is implementation, what happens when a state has the physical ability to disregard all the rules and there is no effective way to make it comply?
That is the central weakness of much of the world’s transboundary water law. The rules are usually detailed when it comes to allocations and procedures, less certain when it comes to adjudication, and largely silent on enforcement. The result is an imbalance between law and power.
Downstream countries often have the stronger legal case because they bear the consequences of decisions taken upstream, without having much say in making them. Upstream countries, however, hold the physical advantage because they control the source. A downstream state can win the legal argument and still lose control over the river. There is another problem, construction operates on its own clock. Diplomacy and courts take time while infrastructure does not wait for either. Tunnels are drilled, reservoirs filled and turbines are installed. By the time a court ruling or political agreement arrives, the physical reality may already have changed.
Throughout this series, we have seen that India’s response has largely been legal. Issue objections, invoke treaties and prepare for tribunals. China and Ethiopia have approached their respective disputes differently. They have treated them as engineering projects to be completed before the legal and diplomatic arguments could catch up. That is not a ‘written’ universal rule of geopolitics. But it is the pattern visible across these three rivers, and one India can no longer afford to treat as a surprise.
India’s answer cannot be another carefully argued legal brief. What it needs is a broader strategic doctrine, and the right place to begin is the region at the centre of this series, the Tibetan Plateau and the wider Hindukush Himalaya. This area is often called the ‘Third Pole‘ because, after the Arctic and Antarctic, it contains the planet’s largest store of ice. Its glaciers and snowfields feed the rivers on which hundreds of millions of people across South and Southeast Asia depend.
The doctrine could be called the Third Pole Doctrine. Its central idea is straightforward, law can protect a country only when that country has the means to give the law some force, but power is legitimate only when it is exercised with restraint. A state that lacks capability is left asking the law to do more than it can. A state that gathers power without limits eventually resembles the aggressor it criticises. India’s challenge, and perhaps its opportunity, is to become the first major power in the region to combine strength with self-restraint.
That principle can be turned into four practical commitments.
See everything: India should have its own reliable picture of every major development affecting a shared river. Essential information cannot be left to an upstream power’s discretion.
Buffer, don’t bluster: The aim should be to prepare for disruption and reduce its impact, not to rely on public warnings once the threat has already emerged.
Lead the coalition by reforming itself: India’s smaller downstream neighbours will not automatically support its position against a stronger upstream power. Their confidence has to be earned through India’s own treatment of shared waters.
Write the clause before you need it: If existing law leaves a gap, India should work to fill it before the next emergency. A missing rule is far more difficult to create once a crisis is under way.
The doctrine would not require India to copy China’s approach, build a dam for every dam, or exploit every site available to it. Power without restraint would only reproduce the same danger at a different scale. The purpose of combining capability with restraint is to ensure that no country, including India, can turn a shared river into an instrument of coercion without paying a serious political price.
It begins with technology India already possesses but has not fully turned into usable public capacity. ISRO operates a near real time flood monitoring system for the Brahmaputra basin, drawing on radar and optical satellites such as EOS-04, Resourcesat-2A and the Cartosat series. The system can generate flood maps within five or six hours of receiving the relevant data. By the end of July 2026, it had supplied Assam’s disaster management authorities with 33 separate flood products.
The problem, then, is not that India lacks the ability to observe the river. It is the gap between detection and action, what a satellite identifies, and what reaches a district official early enough to make a difference. In Sivasagar this year, officials said they had received barely three hours’ warning before flash floods arrived, even though the monitoring system had been operating in the background.
India could close part of that gap by creating a dedicated Brahmaputra Dam Monitor, modelled on the Stimson Center’s Mekong Dam Monitor. It could combine satellite imagery with river-gauge readings, rainfall records and seismic data. Such a system would not reveal what Chinese engineers were thinking or show India what was happening inside underground tunnels. Satellites cannot do that. But it could track sudden changes in river flows, visible construction activity and shifts in reservoir behaviour, giving India, Bangladesh and independent researchers information on their own timetable rather than waiting for Beijing to provide it. In a basin where so much remains hidden, being able to see clearly is already a form of deterrence.
It brings us back to the Upper Siang project on India’s stretch of the Brahmaputra, examined earlier in this series. The strategic argument for creating storage and regulating the river is serious. But so are the objections, the seismic dangers of building in a young mountain range, the possible displacement of Adi communities and local opposition that has already slowed survey work.
If Upper Siang is treated as part of a wider doctrine rather than simply as India’s answer to a Chinese dam, it should be judged by a broader measure. The relevant question is not only how many gigawatts it can generate, but how much disruption India could absorb if China’s cascade suddenly releases water, or holds it back. That approach should not stop with a single dam. It should also include stronger floodplain protection, a more distributed power network instead of excessive dependence on centralised facilities, and evacuation systems designed to operate within hours rather than days.
It is the most difficult of the four commitments, and the one that will show whether the doctrine is genuinely principled or merely useful when India is the aggrieved party.
India cannot demand consultation, data sharing and restraint from China over the Brahmaputra while treating Bangladesh, which lies downstream of India within the same river system, as an inconvenient footnote. The two situations are not identical. China operates infrastructure on a scale India does not, while India and Bangladesh have formal treaties, established institutions and decades of technical cooperation that have no equivalent in the India-China relationship.
Still, the underlying issue is the same. Dhaka can see the contradiction, even when Delhi prefers not to.
Two separate agreements lie at the heart of this test. The first is the Ganges Water Sharing Treaty, signed in December 1996 for a period of 30 years. It expires in December 2026. In February 2026, India’s MoS Kirti Vardhan Singh told Parliament that formal talks on renewal had not yet begun. The following month, technical experts from the two countries met at the Farakka Barrage to review the data on which the treaty rests.
The Teesta is a different and older problem. A draft agreement prepared in 2011 proposed allocating about 42.5 per cent of the river’s dry season flow to India and 37.5 per cent to Bangladesh, leaving the balance unallocated. It was ready to be signed but never became law. That proposal came from one round of negotiations, it is not an existing legal entitlement. Any future talks should therefore use it as a starting point, not as an irrevocable formula.
The politics have also become more complicated on both sides. This is not simply a story of Indian obstruction. West Bengal’s consent is effectively indispensable to any Teesta agreement, and the state changed governments at its most recent election. The party now in power in Kolkata is the BJP, which also governs in New Delhi. That political alignment has not resolved the dispute. Leaders from northern West Bengal, where farmers depend on the Teesta, have told reporters that sending more water to Bangladesh would carry a domestic political cost, regardless of which party was asking them to do it. Bangladesh, meanwhile, elected a new government led by the Bangladesh Nationalist Party in February 2026. Its foreign ministry has said Dhaka will not assume what the new West Bengal government wants until Kolkata states its position directly.
Both countries, then, are proceeding cautiously for reasons that extend beyond mutual trust. Bangladesh has also kept alive a long standing Chinese proposal for managing the Teesta. That is a quiet but unmistakable message to Delhi, a downstream neighbour kept waiting indefinitely will eventually look elsewhere.
A settlement is still possible. It could begin with jointly measured and publicly released flow data from Farakka and the Teesta. It could guarantee an ecological minimum flow instead of focusing only on dry-season allocations. It could provide for periodic reviews based on rainfall patterns and glacier conditions, rather than locking both sides into figures drawn from the hydrology of 1996. And it could support investment in more efficient irrigation in the Indian and Bangladeshi districts that rely on these rivers, so that negotiations are not reduced to dividing an increasingly scarce supply.
Smaller technical agreements may also be more effective at rebuilding confidence than one sweeping political bargain. A 2022 arrangement allowing Bangladesh to draw a limited and clearly specified quantity of water from the Kushiyara through the Rahimpur canal showed that a narrow, measurable agreement can succeed even when a comprehensive treaty has remained stuck for fifteen years.
Bhutan offers a useful example of what this relationship can look like when it functions properly. In 2026, Indian and Bhutanese officials met twice, once in Thimphu in February and again in Delhi in August, to expand the sharing of hydrological data, improve flood monitoring stations on rivers flowing into Assam and West Bengal, and review joint hydropower projects, including Punatsangchhu-I.
No one describes the India-Bhutan relationship as coercive. It works because India shares information before being pressed to do so, helps finance infrastructure Bhutan could not easily build on its own, and treats cooperation as a continuing relationship rather than a series of isolated transactions. There is no reason that approach cannot be extended to Bangladesh, even if the scale and political difficulty are much greater. The case for doing so is not only a moral one. A Bangladesh that feels secure and fairly treated is a diplomatic asset that no tribunal ruling can manufacture, a lower riparian neighbour with strong reasons to remain close to India instead of accepting the next attractive offer from elsewhere.
India’s most convincing response to Chinese unilateralism upstream is to ensure that no country downstream of India can honestly conclude that India opposes China’s behaviour only because it has finally found itself on the receiving end.
Let’s return to the legal argument from the second piece in this series, except this time, it’s not a defence. It’s a proposal.
India made three arguments after Pahalgam. First, that a sustained campaign of cross-border terrorism counts as what the Vienna Convention calls a material breach. Second, that enough had changed since 1960 to meet treaty law’s own test for a fundamental change of circumstances. Third, that what it did was a narrow, reversible use of the necessity doctrine in the law of state responsibility.
Trade law has its own version of this same problem. The WTO’s charter lets any member set aside its obligations for whatever it considers necessary to its own essential security, a clause that’s been invoked before, with pretty mixed results, by Russia, by the United States, and during the Gulf states’ blockade of Qatar over alleged support for terrorism. None of that is a rule water treaties can simply borrow. But it’s a good model for what water treaties are missing, a security exception that’s written down in advance and narrow enough to actually hold up under review, instead of one improvised in the middle of a crisis and argued over for sixteen months afterward.
So what would a workable version for future water treaties actually look like? A security exception that’s narrowly defined and genuinely reviewable, not something a state simply certifies for itself. A material breach clause that names sustained state support for armed proxies specifically. A rule that any emergency measure has to be temporary, proportionate, and reversible. A floor underneath all of it, so that even a suspended treaty can never be used to physically cut off the other side’s essential humanitarian water needs. Data sharing that continues even through a diplomatic crisis. And one single, clear sequence for expert review and arbitration, so two forums can never end up ruling on the same technical question at once, exactly the mess that complicated the 2026 Indus proceedings.
India doesn’t need the world’s permission to start. The next time it renegotiates a water treaty of its own, with Bangladesh, say, or with Bhutan, it can put exactly this kind of clause on the table itself. It just paid the price for having a rulebook with no answer to this problem, which puts it in a good position to go write that answer, instead of waiting to be judged by the same gap again.
Picture the day Ethiopia finally flipped the switch on those turbines over the Blue Nile. It’s tempting to read that as a legal win, but that’s not really the story, legal scholars still don’t agree on whose case was actually stronger. What decided things was far more concrete. Ethiopia found the money, kept building, and never let go of the site. Egypt had the better legal brief and Ethiopia had the dam.
So what should India take from that? There are really three options on the table. One: keep doing what it did with Medog, raise objections only after the project is already a done deal. Two, swing to the other extreme and start building first, asking questions later, which is just borrowing the exact playbook it criticises China for running. Or three, harder, less dramatic, but the one that actually holds up, build the capability needed to protect its own interests, be upfront about what that capability can’t tell it, and start treating the smaller neighbours next door as partners, not as an audience it only bothers to court when it needs their backing.
None of this lets India off the hook, either. China acting unilaterally doesn’t excuse India’s own shortcomings, and neither does Pakistan’s hostility, nor India’s conviction that the tribunal got its jurisdiction wrong. Fair enough, these might all be real grievances. But a grievance isn’t a strategy, no matter how many of them you stack up.
Put all three rivers side by side and the lesson is pretty simple. Construction doesn’t wait for the lawyers to finish talking. Even the stronger argument can still lose. And trust isn’t something you can conjure up the moment you suddenly need it, it has to be laid down long before that, through moves that barely look significant at the time: finally sorting out the Teesta, passing along a flood-gauge reading, telling a neighbour something useful before they even think to ask.
And through all of this, the water just keeps moving. The Siang keeps flowing through Arunachal Pradesh, carrying down whatever China decides to release upstream. The Indus keeps crossing into Pakistan regardless. The treaty is technically still alive, even as India’s decision to hold it in abeyance sits unresolved. Down in Egypt, the Nile still reaches the delta, just with a lot more uncertainty trailing it now that the turbines are running.
Not one of these rivers is pausing for India to finish making its case. The issue isn’t that law has stopped mattering. It’s that India keeps expecting a referee to show up, in disputes where, realistically, the referee walked off the field a long time ago.
The next test won’t wait for the next dam to be announced, it happens before that. Can India spot the danger early enough? Can it get real protection in place before the water arrives? Can it settle things with its neighbours before it’s the one needing the favour? How India answers those three questions will matter far more than how airtight its next legal brief turns out to be.
In this third and final part, we will unpack every single layer of India’s energy roadmap for the next 20 to 30 years.
This report explores the chemical and industrial shift behind India’s successful 20% ethanol blending (E20) target. It details the molecular benefits of ethanol, such as boosting petrol’s octane rating and reducing emissions.
Whatever India intended by holding the treaty in abeyance, physically choking Pakistan’s water supply was never actually on the table; the infrastructure for it does not exist, and cannot be built quickly even if Delhi wanted to try. What India suspended was information and process, not flow.
Selected issues, clear explanations and thoughtful perspectives—delivered when we publish.
