What an Executive Order Can (and Can't) Actually Rename: The Lake Ontario Case

This isn't Ruby's usual commercial-contract territory, but the legal mechanism underneath it is worth walking through.

Key takeaways: An executive order signed August 27, 2026 renamed Lake Ontario “Lake America,” but only for US federal purposes. The authority behind it is a narrow, decades-old statute that binds US federal agencies and nothing outside US jurisdiction, so Canada isn't bound by it and hasn't adopted it. The underlying doctrine, that legal authority only reaches as far as the jurisdiction granting it, shows up constantly in cross-border commercial contracts too.

On August 27, 2026, an executive order renamed Lake Ontario “Lake America” for US federal purposes. Canada's response arrived within the day. Industry Minister Melanie Joly: “We'll always call it Lake Ontario, period.” Prime Minister Mark Carney pointed to the name's actual history, a Wendat-origin name more than 400 years old, and said naming reality means calling it Lake Ontario “then, now and always.”

Neither side is bluffing. Underneath the headline sits a genuinely useful question: how far does a piece of domestic legal authority actually reach, and what happens once the thing it's acting on crosses a border. It's the same question that shows up, in miniature, in ordinary cross-border commercial contracts.

The order is narrower than the headline

The order cites 43 U.S.C. sections 364 through 364f, the Geographic Names Act, and directs the Secretary of the Interior, working with the U.S. Board on Geographic Names, to complete the change within 30 days. That statute created the Board as the federal government's internal standardizing body for names, historically housed within the U.S. Geological Survey. Section 364b gives the Secretary a narrow fallback: act directly if the Board doesn't act within a reasonable time.

It isn't a new or invented power. Interior Secretary Sally Jewell used the identical mechanism in 2015 to make “Denali” the federal name over “Mount McKinley,” from the opposite political direction. An executive order in this space isn't a freestanding presidential naming authority; it's a directive to use a specific, pre-existing statutory tool Congress already built, one that's already been used before, by someone else, for the opposite result.

What the order can't touch

This order follows the same template as the January 2025 order that renamed the Gulf of Mexico “Gulf of America” and reverted Denali to “Mount McKinley,” and that earlier order previews what happens next. Mexico, Cuba, the UK, and most non-US news outlets kept using “Gulf of Mexico.” Google Maps showed “Gulf of America” to US-located users, “Gulf of Mexico” to Mexico-located users, and both names to everyone else. Mexico's government threatened litigation against Google specifically over the map label, not against the US government over the renaming power itself, and a Mexican court dismissed the resulting suit on jurisdictional grounds. The one piece of US litigation that went anywhere, Associated Press v. Budowich, was a First Amendment press-access case about White House credentials, not a challenge to the Secretary's authority to rename anything in the first place.

Put together, that's the actual boundary. The Board on Geographic Names' authority is domestic: it binds US federal agencies, US federal databases, US government documents. It doesn't bind Canada, the Geographical Names Board of Canada, or any entity outside US jurisdiction, and no international body enforces a single uniform name for a feature two countries share. Lake Ontario adds a wrinkle the Gulf never had. The international border runs through the lake itself rather than along its edge, so mapping platforms may end up showing two different names for the same water with a boundary line running across it, a situation that hasn't come up before.

One claim circulating alongside this story doesn't survive a closer look: that a “1989 agreement” between the two countries' naming boards requires Canadian consent before either side renames a shared feature. Natural Resources Canada's own description of how the two boards coordinate mentions only a shared committee under a UN naming body, nothing binding. The Boundary Waters Treaty's actual jurisdiction covers water levels, water quality, and use, not names. A citation that sounds specific isn't automatically a verified one.

The part that isn't really about geography

Strip out the lake and the politics, and the remaining doctrine is one every founder doing business across the border should already have internalized: legal authority is only as strong as the jurisdiction that granted it. It doesn't extend automatically just because the thing it's acting on happens to cross a line.

Commercial contracts run into the same limit. A governing law and forum selection clause drafted under Ontario law doesn't bind a counterparty who never agreed to be sued there, and a judgment won at home isn't automatically enforceable against assets or a party sitting somewhere else. Founders selling into the US, or signing with a US vendor, hit a version of this question constantly: which country's law actually governs, and where can you actually enforce what you signed. Get an answer before you sign, not after the clause you were counting on turns out not to reach as far as you assumed. Ruby's flat-fee Contract Review, starting at $499 CAD with a licensed Canadian lawyer, is a fast way to check what a cross-border agreement actually says before that becomes a problem.

Sources: NBC News, CNBC, Al Jazeera, “Can Trump really rename Lake Ontario, Lake America?”, Wikipedia, Executive Order 14172, Natural Resources Canada, Geographical Names Board of Canada international activities. Congress.gov CRS product IF12881. Facts verified in an independent second research pass as of Aug 28, 2026; a circulating “1989 agreement” claim was checked and found unsupported.