<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:googleplay="http://www.google.com/schemas/play-podcasts/1.0"><channel><title><![CDATA[Klamath Basin Lawfare]]></title><description><![CDATA[Documenting the Legal Exploitation of the Klamath Basin]]></description><link>https://www.klamathbasinlawfare.org</link><image><url>https://substackcdn.com/image/fetch/$s_!lZbK!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fbce6671f-d95c-4d15-9c2c-f87d7868f047_512x512.png</url><title>Klamath Basin Lawfare</title><link>https://www.klamathbasinlawfare.org</link></image><generator>Substack</generator><lastBuildDate>Sat, 11 Jul 2026 22:02:48 GMT</lastBuildDate><atom:link href="https://www.klamathbasinlawfare.org/feed" rel="self" type="application/rss+xml"/><copyright><![CDATA[Transparency]]></copyright><language><![CDATA[en]]></language><webMaster><![CDATA[transparencyinlawfare@substack.com]]></webMaster><itunes:owner><itunes:email><![CDATA[transparencyinlawfare@substack.com]]></itunes:email><itunes:name><![CDATA[Transparency]]></itunes:name></itunes:owner><itunes:author><![CDATA[Transparency]]></itunes:author><googleplay:owner><![CDATA[transparencyinlawfare@substack.com]]></googleplay:owner><googleplay:email><![CDATA[transparencyinlawfare@substack.com]]></googleplay:email><googleplay:author><![CDATA[Transparency]]></googleplay:author><itunes:block><![CDATA[Yes]]></itunes:block><item><title><![CDATA[The Anatomy of Procedural Inversion — How Federal Agencies Pre-Negotiate the Record]]></title><description><![CDATA[Foundational Post No. 3]]></description><link>https://www.klamathbasinlawfare.org/p/the-anatomy-of-procedural-inversion</link><guid isPermaLink="false">https://www.klamathbasinlawfare.org/p/the-anatomy-of-procedural-inversion</guid><dc:creator><![CDATA[Transparency]]></dc:creator><pubDate>Mon, 08 Jun 2026 21:35:10 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!lZbK!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fbce6671f-d95c-4d15-9c2c-f87d7868f047_512x512.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p><em>Post No. 1 established what lawfare is: the use of legal process as a strategic weapon &#8212; not to find truth, but to drain, constrain, and foreclose. </em></p><p><em>Post No. 2 established the specific litigation architecture that governs this basin &#8212; the forums, the instruments, and why the administrative record is the only battlefield that matters by the time any of this reaches a judge. </em></p><p><em>This post shows how the weapon operates inside a specific federal regulatory process, the Endangered Species Act. It is a step-by-step account of a legal procedure that has a correct sequence, what that sequence is designed to protect, and exactly how it is being subverted in the Klamath Basin. No legal training is required to follow this post. The mechanism is not complicated. It is just hidden.</em></p><div><hr></div><h2>I. What the Law Actually Requires: Section 7 Has Two Duties, Not One</h2><p>Most people who have heard of the Endangered Species Act in the context of Klamath water know about one requirement: federal agencies cannot jeopardize listed species. That requirement is real. It is also only half of the statute.</p><p>Section 7 of the ESA imposes two separate and legally distinct obligations on federal agencies like the Bureau of Reclamation. They are written in consecutive subsections of the same statute. They have different verbs. They require different things. And in the Klamath Basin, only one of them has been enforced.</p><div><hr></div><h3>Section 7(a)(1) &#8212; The Duty to Actively Conserve</h3><p>The first obligation is found at 16 U.S.C. &#167; 1536(a)(1).&#185; The statute states:</p><blockquote><p><em>&#8220;All Federal agencies shall, in consultation with and with the assistance of the Secretary, utilize their authorities in furtherance of the purposes of this chapter by carrying out programs for the conservation of endangered species and threatened species listed pursuant to section 1533 of this title.&#8221;</em></p></blockquote><p>Read that precisely. It does not say &#8220;avoid harming species.&#8221; It says <strong>utilize their authorities</strong> to <strong>carry out programs</strong> for conservation. The verb is <em>shall</em>. Congress chose that word deliberately, after rejecting every qualifying phrase &#8212; &#8220;to the extent practicable,&#8221; &#8220;consistent with their primary mission&#8221; &#8212; that earlier drafts had included. When Congress passed the ESA in 1973, it deliberately stripped out all the escape clauses. The duty is absolute.</p><p>The U.S. Supreme Court confirmed this in <em>TVA v. Hill</em>, describing Section 7(a)(1)&#8217;s language as &#8220;stringent&#8221; and &#8220;mandatory&#8221; and characterizing it as &#8220;an explicit Congressional decision to require agencies to afford first priority to the declared national policy of saving endangered species.&#8221;&#8309;</p><p><strong>Section 7(a)(1) is not a consultation trigger. It has no trigger at all.</strong> It begins the moment a species is listed and does not stop until that species is delisted. It requires action continuously, at all times, independent of any proposed project or pending BiOp cycle. The Secretary of the Interior &#8212; who holds supervisory authority over both Reclamation and USFWS &#8212; carries a parallel obligation to assist agencies in developing and implementing those conservation programs.&#178;</p><div><hr></div><h3>Section 7(a)(2) &#8212; The Duty Not to Jeopardize</h3><p>The second obligation, at 16 U.S.C. &#167; 1536(a)(2),&#179; is the one most people know: federal agencies must ensure their actions are not likely to jeopardize the continued existence of any listed species or result in the destruction or adverse modification of designated critical habitat. This is the requirement that triggers formal consultation, Biological Opinions, and the rest of the procedural machinery described in Sections II through IV of this post.</p><p>Section 7(a)(2) is a floor &#8212; a minimum standard. It says: whatever you do, do not push listed species closer to extinction. Section 7(a)(1) is the mandate above that floor: beyond not causing harm, actively pursue recovery.</p><p>The two duties are not alternatives. Both are mandatory. Both use <em>shall</em>. The Department of Interior&#8217;s own Office of the Solicitor confirmed in its February 2024 legal memorandum to the Director of USFWS that compliance with Section 7(a)(2) is explicitly <strong>not</strong> equivalent to compliance with Section 7(a)(1).&#8308; An agency that passes its BiOp review has met the floor. It has not met the ceiling.</p><div><hr></div><h3>The Boundary That Cannot Be Crossed: What &#8220;Utilize Their Authorities&#8221; Means &#8212; and What It Does Not</h3><p>Section 7(a)(1) directs each agency to utilize <strong>its own</strong> authorities. It does not grant new powers. It does not authorize agencies to act beyond their enabling legislation. The D.C. Circuit established this in <em>Platte River Whooping Crane Critical Habitat Maintenance Trust v. FERC</em>:&#8310; an agency&#8217;s 7(a)(1) obligation is to use the authority it already has &#8212; no more, no less.</p><p>This boundary is critical for understanding what Reclamation can and cannot do in the Klamath Basin.</p><p><strong>The Klamath Project was authorized under the Reclamation Act of 1902&#8311; and formally established by the Secretary of the Interior in 1905. Its sole authorized purpose is the delivery of irrigation water to agricultural lands in the Klamath and Lost River Basins of Oregon and California.</strong></p><p>That project authorization defines the outer boundary of Reclamation&#8217;s legal authority. Reclamation is an irrigation delivery agency in the Klamath Basin. It is not a habitat restoration agency. It is not a water quality regulator. It is not a forest watershed manager. It is not a hatchery operator. It is not a wildlife refuge manager. It cannot spend appropriated funds on programs that fall under the jurisdiction of other federal agencies. It cannot implement fish passage measures that belong to the Army Corps or USFWS. It cannot direct the Forest Service to manage upland watersheds. It cannot acquire water rights for in-stream flows absent specific congressional authorization.</p><p>When a Section 7(a)(2) BiOp&#8217;s Reasonable and Prudent Alternative requires Reclamation to implement conservation measures that fall outside its project authorization &#8212; measures that belong to USFWS, the Forest Service, or EPA &#8212; that RPA is legally defective. The Services can only require Reclamation to exercise its existing discretionary authorities differently. They cannot use a BiOp to assign Reclamation obligations it has no statutory power to perform.&#8312;</p><p><strong>The practical implication is direct: Reclamation&#8217;s contribution to any Section 7(a)(1) conservation program is necessarily narrow, because its project authorization is narrow.</strong> The heavy lifting of species conservation in the Klamath Basin &#8212; habitat restoration, water quality improvement, watershed management, refuge operations &#8212; belongs to the agencies with authority over those resources. Those agencies have been required by law to do that work since the day each species was listed.</p><div><hr></div><h3>The Federal Agency Landscape: Who Holds What Authority, and What 7(a)(1) Requires of Each</h3><p>Six federal agencies hold substantial operational authorities in the Klamath Basin. Each carries an independent, non-discretionary, species-specific Section 7(a)(1) obligation. Lost River and shortnose suckers were listed in July 1988. SONCC coho salmon were listed in 1997. Those listing dates are the triggering dates. Every agency below has been under a continuous 7(a)(1) obligation for between 29 and 38 years.</p><div><hr></div><p><strong>U.S. Fish and Wildlife Service</strong></p><p>USFWS manages approximately 200,000 acres across six National Wildlife Refuges in the Klamath Basin: Lower Klamath, Tule Lake, Upper Klamath, Clear Lake, Bear Valley, and Klamath Marsh NWRs. These refuges encompass critical wetland and shallow lake habitat directly relevant to Lost River and shortnose sucker recovery &#8212; the same species for which USFWS is the lead biological review agency in the Section 7(a)(2) consultation process.</p><p>USFWS holds independent water rights associated with refuge operations. It has authority to manage water delivery to refuge wetlands, restore emergent vegetation, and improve spawning and rearing habitat for suckers using its own operational budget and land management authorities. It has had recovery plans for these species since the 1990s.</p><p>The Solicitor&#8217;s Memo is unambiguous that incidental benefits from programs designed for other purposes do not satisfy 7(a)(1). The programs must be <strong>species-specific</strong> and **meaningful.**&#8313; A refuge management program that happens to benefit suckers as a byproduct of general wetland management does not meet the standard. A documented, funded, implemented program specifically designed to advance sucker recovery using refuge authorities does.</p><p>The administrative record of what USFWS has done under 7(a)(1) using its refuge operational authorities &#8212; specifically, for Lost River and shortnose suckers &#8212; as a documented programmatic instrument is not publicly established.</p><div><hr></div><p><strong>U.S. Forest Service</strong></p><p>The Klamath and Fremont-Winema National Forests encompass the majority of the upper watershed &#8212; the headwater systems that feed Scott, Shasta, Salmon, and other tributaries critical to SONCC coho spawning and rearing. Forest management decisions on those lands &#8212; road construction and maintenance practices, riparian buffer standards, timber harvest prescriptions, livestock grazing terms &#8212; directly determine sediment loads, water temperature, and low-flow conditions in coho habitat.</p><p>The Forest Service has authority under the National Forest Management Act and the Organic Administration Act to manage these lands in ways that materially benefit listed species. An implemented, species-specific upper-watershed management program &#8212; reducing road-related sedimentation, enforcing riparian buffers, restoring stream channel conditions &#8212; would produce measurable coho habitat improvements that no Reclamation operational change could replicate, because Reclamation&#8217;s operations do not reach those tributaries.</p><p>A formal, documented Section 7(a)(1) conservation program for SONCC coho, implemented through Forest Service land management authorities in the Klamath and Fremont-Winema National Forests, coordinated with NMFS recovery objectives, has not been publicly established as an instrument in the administrative record.</p><div><hr></div><p><strong>Environmental Protection Agency</strong></p><p>The Klamath River has carried Clean Water Act Section 303(d) impaired waters designation for temperature, dissolved oxygen, and nutrient loading. Toxic algal blooms &#8212; the microcystin events that previously exceeded public health limits in 58 percent of lower-river samples below Iron Gate &#8212; were driven in part by nutrient loading from multiple sources throughout the watershed. EPA holds authority under the Clean Water Act to establish Total Maximum Daily Loads (TMDLs) &#8212; binding, enforceable numerical limits on pollutant loads &#8212; and to require state water quality programs to implement them.</p><p>Temperature and nutrient TMDLs for the Klamath, if established and enforced, would directly benefit coho and sucker recovery independent of any change in Reclamation&#8217;s water delivery operations. EPA&#8217;s 7(a)(1) obligation requires it to use its Clean Water Act authorities affirmatively for listed species benefit. A final, enforceable Klamath temperature TMDL has not been implemented as an instrument of species recovery.</p><div><hr></div><p><strong>Bureau of Indian Affairs</strong></p><p>BIA holds trust responsibilities to the Klamath Tribes (Klamath, Modoc, Yahooskin Band of Snake), the Yurok Tribe, the Karuk Tribe, and the Hoopa Valley Tribe. Tribal water rights, tribal hatchery programs, and tribal natural resources management directly affect basin hydrology and salmon populations. BIA&#8217;s 7(a)(1) obligation includes supporting tribal conservation programs through its trust management and technical assistance authorities.</p><div><hr></div><p><strong>U.S. Army Corps of Engineers</strong></p><p>The Corps holds Clean Water Act Section 404 jurisdiction over dredge-and-fill activities in waters of the United States throughout the Klamath Basin. Wetland restoration, riparian buffer establishment, side-channel reconnection, and habitat enhancement projects that involve earthwork in jurisdictional waters require Corps authorization. The terms and conditions the Corps attaches to Section 404 permits &#8212; and the mitigation requirements it imposes &#8212; directly shape the pace and scope of habitat restoration in the basin. Under its own Section 7(a)(1) obligation, the Corps must orient its permitting and project-authorization authorities toward listed species recovery. A coordinated programmatic approach to Section 404 permitting in the Klamath Basin &#8212; one that actively facilitates restoration projects with recovery value &#8212; has not been established as a documented instrument.</p><div><hr></div><p><strong>Bureau of Reclamation</strong></p><p>Reclamation&#8217;s 7(a)(1) obligations are the most constrained of any federal agency operating in the Klamath Basin, for the reason stated above: its project authorization is limited to irrigation water delivery. Within its operational discretion &#8212; timing of releases, storage management choices within permitted ranges, coordination with downstream operators, data collection and reporting &#8212; Reclamation can make choices that benefit or harm listed species. Those choices are real. They are also bounded by the project authorization. Reclamation&#8217;s 7(a)(1) contribution to basin-wide species recovery is structurally limited to what an irrigation delivery agency can do within its irrigation delivery authority.</p><div><hr></div><h3>The February 2024 Solicitor&#8217;s Memorandum: Interior&#8217;s Own Lawyers Confirm What Has Been Missing</h3><p>On February 6, 2024, the Department of the Interior&#8217;s Office of the Solicitor issued a formal legal memorandum to Martha Williams, then-Director of USFWS, examining the scope of federal agencies&#8217; obligations under Section 7(a)(1).&#8308; The memo was prepared by Deputy Solicitor Sarah Krakoff and Attorney-Advisor Shawn Finley. It is formal legal guidance &#8212; the Department&#8217;s own authoritative legal interpretation of what the statute requires.</p><p>The memo&#8217;s conclusions, applied to the Klamath Basin, are unsparing.</p><p><strong>The duty is non-discretionary.</strong> Agencies have discretion about how to design their conservation programs. They have no discretion about whether to have them. The Solicitor&#8217;s Memo states directly: &#8220;agencies&#8217; core obligation to comply with ESA Section 7(a)(1) is not discretionary.&#8221;</p><p><strong>The duty is species-specific.</strong> General conservation postures do not satisfy it. Incidental benefits from programs designed for other purposes do not satisfy it. <em>Sierra Club v. Glickman</em> &#8212; cited in the memo &#8212; rejected exactly that argument when USDA tried to claim that national farm programs incidentally benefited aquifer-dependent species. The court held that Section 7(a)(1) &#8220;requires species-specific measures developed in consultation with FWS.&#8221;&#185;&#185; Each agency in the Klamath Basin must have a documented program for each listed species for which it holds relevant operational authority.</p><p><strong>Programs must be meaningful.</strong> The Eleventh Circuit&#8217;s holding in <em>Florida Key Deer v. Paulison</em> &#8212; also cited &#8212; established that a program so insignificant as to have only incidental effects on species conservation amounts to inaction and violates 7(a)(1).&#8313;</p><p><strong>The authority ceiling is fixed.</strong> The memo reiterates <em>Platte River Whooping Crane</em>: 7(a)(1) does not expand any agency&#8217;s statutory powers. Each agency works within its enabling act. For Reclamation in the Klamath Basin, that means the Reclamation Act of 1902 and the 1905 Project authorization. Irrigation delivery. Nothing beyond it.</p><p><strong>The memo&#8217;s closing conclusion is the most consequential sentence in the document for Klamath Basin water users:</strong></p><blockquote><p>*&#8221;Robust Section 7(a)(1) programs therefore have the potential to streamline or, in highly successful cases, eliminate the need for consultation under Section 7(a)(2).&#8221;*&#185;&#8304;</p></blockquote><p>Read that again. The Department of Interior&#8217;s own lawyers stated in writing, in February 2024, that if the agencies with actual conservation authority had built and implemented robust 7(a)(1) programs, the species recovery trajectory could have advanced to the point where Reclamation&#8217;s Section 7(a)(2) consultation burden is reduced or eliminated entirely.</p><p>Lost River and shortnose suckers have been listed since 1988. Coho since 1997. The agencies with the actual conservation tools &#8212; refuge management, forest watershed authority, water quality enforcement &#8212; have had non-discretionary obligations to build those programs for 29 to 38 years. They have not built them in documented, programmatic form. The Solicitor&#8217;s Memo, issued to USFWS Director Williams in February 2024, acknowledges the gap directly: it describes Section 7(a)(1) as having &#8220;the greatest unrealized potential to achieve the ESA&#8217;s conservation goals&#8221; and the provision as a &#8220;sleeping giant.&#8221;&#185;&#8304;</p><p>More than two years after that memo was issued, no formal inter-agency Section 7(a)(1) conservation framework for the Klamath Basin appears in the public administrative record.</p><div><hr></div><h3>The Cost-Shifting Structure: How 7(a)(1) Failures Load the 7(a)(2) Burden onto Irrigators</h3><p>The consequence of 37 years of unmet 7(a)(1) obligations by the agencies with actual conservation authority is not abstract. It is structural.</p><p>Because USFWS has not implemented meaningful sucker recovery programs through its refuge authorities, because the Forest Service has not implemented species-specific coho watershed programs through its land management authorities, and because EPA has not implemented enforceable water quality standards through its Clean Water Act authorities &#8212; the species recovery that those programs would have advanced has not occurred. The listed species remain listed. The 7(a)(2) consultation cycle continues. And the entire visible regulatory burden of that continuing cycle falls on the one federal actor whose project authorization is most limited: Reclamation, and through Reclamation, onto the water users it serves.</p><p>The agencies with the broadest conservation tools face no parallel public accountability for their 7(a)(1) obligations. The agency with the narrowest conservation authority and the most concrete private-party obligations bears the entire weight of the regulatory structure.</p><p><strong>That asymmetry is not an accident of administration. It is the operational structure of the lawfare documented in this archive.</strong> By concentrating all ESA compliance accountability in the Section 7(a)(2) consultation cycle &#8212; where the record can be pre-negotiated, as Section IV of this post will show &#8212; and by leaving the 7(a)(1) obligations of other agencies entirely unaccounted for, the system achieves a precise result: the appearance of ESA compliance, the imposition of real economic cost on irrigators, and the insulation of the agencies with the most powerful recovery tools from any accountability for using them.</p><p>An irrigator whose water is cut under a BiOp RPA cannot point to decades of unmet Forest Service 7(a)(1) obligations and demand accountability before Reclamation&#8217;s operations are further constrained. That argument belongs in a proceeding that has never been opened. The current regulatory structure ensures it never is.</p><div><hr></div><h3>The Documented Financial Record: What Reclamation Has Actually Spent &#8212; and What It Has No Authority to Spend</h3><p>The cost-shifting described above is not theoretical. It is documented in Reclamation&#8217;s own accounts, and the documentation reveals a compounding legal problem that has gone unresolved for more than three decades.</p><p><strong>The scope of the spending.</strong> According to a memorandum prepared by Klamath Water Users Association Director of Water Policy Moss Driscoll on August 30, 2024, Reclamation&#8217;s unresolved ESA expenditures charged against the Klamath Project accounts exceed $100 million &#8212; more than five times the original cost to build the Project.&#178;&#8310; The spending encompasses not just compliance infrastructure like the A Canal fish screen headworks ($17.7 million, completed 2003) and the Link River Dam fish ladder (completed 2004, with the Driscoll Memorandum documenting a combined cost for both structures of over $21 million), but tens of millions in biological studies and investigations, private land acquisitions, grants to tribal governments, interagency agreements funding staff and offices at USFWS, NMFS, and USGS, and &#8212; in at least one documented instance &#8212; consulting fees channeled through the Bureau of Indian Affairs to the Department of Justice for tribal water rights litigation adversarial to the Project.&#178;&#8310; The annual ESA compliance budget for the Project grew every year for four consecutive years, from $13.3 million in fiscal year 2021 to $28.6 million in fiscal year 2024.</p><p><strong>The absence of legal authority.</strong> The Reclamation Act of 1902 establishes the default rule: all costs in connection with a federal reclamation project are reimbursable unless Congress expressly provides otherwise.&#8311; Congress has not enacted any law expressly authorizing the categories of ESA activities Reclamation has funded through Klamath Project appropriations, nor authorizing those expenditures to be nonreimbursable. The Driscoll Memorandum concludes directly: &#8220;No federal law expressly authorizes the kinds of activities that Reclamation has undertaken in connection with the Project, let alone for them to be nonreimbursable.&#8221;&#178;&#8310;</p><p><strong>The 1998 regional committee decision.</strong> The designation of these costs as nonreimbursable was made not by Congress but by an internal Reclamation regional committee in 1998, which reclassified over $10 million in past-incurred ESA costs as &#8220;non-project&#8221; costs on the basis that they benefited the entire Klamath Basin. The committee&#8217;s decision altered two project accounts &#8212; one for suckers, one for salmon &#8212; striking out the word &#8220;reimbursable&#8221; and replacing it with &#8220;nonreimbursable.&#8221; That decision has never been reviewed, challenged, or legislatively ratified. Hundreds of millions of dollars have been charged to those two accounts in the 26 years since.&#178;&#8310;</p><p><strong>The collapsed accounting record.</strong> Reclamation is required by its own manual to prepare an annual Statement of Project Construction Costs and Repayment (SPCCR) for every major federal reclamation project. The last complete, accurate SPCCR for the Klamath Project was issued in 1988 &#8212; the same year the first species listing triggered ESA obligations. The 1994 SPCCR was marked &#8220;INCORRECT&#8221; in writing across the front by Reclamation staff. A draft was prepared in 2001 but never signed. Attempts in 2010 and 2014 to produce a corrected document were abandoned. No SPCCR for the Klamath Project has been finalized or publicly released in this century.&#178;&#8310;</p><p><strong>The significance for Section 7(a)(1).</strong> The Driscoll Memorandum identifies the Agency Lake Ranch purchase &#8212; a $5.3 million acquisition of 7,300 acres adjacent to Upper Klamath Lake in 1998 &#8212; as the only documented instance in the entire history of Klamath Project operations where Section 7(a)(1) of the ESA was formally cited as the authority for Reclamation&#8217;s actions on behalf of listed species.&#178;&#8310; Every other expenditure described above &#8212; the studies, the monitoring programs, the tribal grants, the interagency agreements, the restoration projects &#8212; proceeded without a governing Section 7(a)(1) framework. They were funded through the 7(a)(2) consultation cycle&#8217;s BiOp requirements, or through informal agency practice, with costs charged to Project accounts and no congressional authorization on record.</p><p><strong>What this means in plain terms.</strong> Reclamation has spent well over $100 million of Klamath Project irrigation appropriations on activities that its own project authorization does not permit, under a cost classification made by a regional committee without congressional authority, against an accounting record that has not been completed in over 30 years, with no documented Section 7(a)(1) programmatic framework governing how any of it advances species recovery. The money has been spent. The mandatory legal structure that would give it accountability, transparency, and measurable conservation objectives has never been built.</p><p>The January 2026 memorandum from KWUA Counsel Paul Simmons to Executive Director Elizabeth Nielsen confirms that Reclamation has recently raised the possibility that some of these ESA expenditures may be reimbursable by Project water users &#8212; a position for which, as the Driscoll Memorandum establishes, there is no legal foundation.&#178;&#8311; Meanwhile, KWUA has separately compiled a basin-wide accounting of federal, farmer, and ratepayer expenditures on Klamath ESA programs. The Klamath Irrigation District&#8217;s October 2024 letter to Congressman Bentz, with its attached table of Klamath projects since 1988, identifies more than 98 discrete line items with documented taxpayer costs totaling in excess of $614 million across a period the document acknowledges is substantially incomplete &#8212; with dozens of additional line items, including all ongoing USGS, USFWS, NMFS, and NOAA species monitoring programs, USDA programs, and multiple dam removal projects, listed as costs unknown. The cover letter&#8217;s own stated summary is $560 million in American taxpayer expenditures, with the difference from the independently tallied $614 million attributable to the document&#8217;s notation that $162 million in BIL funds is duplicative of individually listed projects. Additional losses to Klamath farmers are characterized as exceeding $1.06 billion.&#178;&#8312;</p><p>Taken together, these documents establish a financial record that is inseparable from the procedural inversion described in Section IV of this post. An agency that has spent more than five times its original project construction budget on ESA activities without congressional authorization, whose accounting records are 30 years out of date, and that has never implemented the Section 7(a)(1) programmatic framework the law requires, is an agency that has every institutional incentive to pre-negotiate its 7(a)(2) Proposed Action rather than submit an honest one. A clean administrative record &#8212; of the kind Section VI of this post describes &#8212; would require a complete accounting of both.</p><div><hr></div><h2>II. The Section 7(a)(2) Consultation Process in Plain Terms</h2><p>When a federal agency plans to do something &#8212; deliver water, build a dam, manage a federal project &#8212; and that action might affect a listed species, the ESA requires a formal review process called <strong>Section 7 Consultation</strong>.</p><p>The consultation process has one fundamental design principle: <strong>the agency that runs the project decides what it is going to do first, independently, and then a separate biological agency evaluates whether that plan will harm listed species.</strong></p><p>That order matters. The project agency is not supposed to ask the biological agency what they want it to do. The project agency is not supposed to negotiate with environmental groups about what to propose. The project agency is supposed to look at its legal obligations &#8212; what it is required to do by contract, by statute, by water rights law &#8212; write that down honestly and completely, and hand that document to the biological reviewers so they can evaluate it.</p><p>The document that describes what the project agency is going to do is called the <strong>Proposed Action</strong> (PA). The evaluation the biological agency produces in response is called a <strong>Biological Opinion</strong> (BiOp).&#185;&#178;</p><p>In the Klamath Basin, the project agency is the Bureau of Reclamation. Its legal obligations are straightforward: deliver irrigation water to farmers under long-term federal water contracts, and manage Project infrastructure for flood control. Those are not optional activities. They are legal commitments the federal government made decades ago, and they are what Reclamation is required to describe in its Proposed Action before consultation begins.</p><p>The two biological review agencies are NMFS (National Marine Fisheries Service) and USFWS. They review what Reclamation proposes and decide whether it jeopardizes listed species.</p><p><strong>That is the legal design. Action agency goes first. Biological agencies go second. They do not collaborate on the script before the play begins.</strong></p><div><hr></div><h2>III. The Correct Sequence, Step by Step</h2><p>The ESA Section 7 Consultation Handbook&#185;&#179; and the governing regulation at 50 CFR &#167; 402.14&#185;&#178; establish four mandatory steps.</p><div><hr></div><h3>Step 1 &#8212; Reclamation Writes an Honest Proposed Action</h3><p>Before Reclamation can write the Proposed Action, it must do something the public rarely hears about: it must formally sort its own operations into two legally distinct categories. This sorting step is not optional. It is required by 50 CFR &#167; 402.03 and the ESA Section 7 Consultation Handbook, and it determines the entire scope of what gets evaluated.</p><p><strong>The two categories are discretionary actions and non-discretionary actions.</strong> The distinction controls everything that follows.</p><div><hr></div><p><strong>Non-Discretionary Actions &#8212; The Environmental Baseline</strong></p><p>A non-discretionary action is something Reclamation is legally required to do regardless of any ESA consultation outcome. The agency has no authority to modify, reduce, or withhold a non-discretionary action to avoid harming a listed species. The law requires it. Full stop.</p><p>For the Klamath Project, the delivery of contracted irrigation water is non-discretionary. Reclamation holds long-term water-service and repayment contracts with Project irrigation districts. Those contracts are legal obligations. Reclamation does not have the authority to unilaterally reduce contracted deliveries because a biological agency finds it inconvenient. The obligation exists independent of the ESA.</p><p>Flood control operations mandated by Reclamation&#8217;s statutory authority over Project infrastructure are similarly non-discretionary.</p><p>Under the regulations and the Consultation Handbook, non-discretionary actions are not part of the Proposed Action. They are part of the <strong>environmental baseline</strong> &#8212; the existing condition of the world against which the Proposed Action is evaluated.&#185;&#8308; They are described in the Biological Assessment so the Services understand the operating context, but they cannot be modified by a Biological Opinion&#8217;s Reasonable and Prudent Alternative. An RPA cannot instruct Reclamation to stop doing something it has no legal authority to stop doing.</p><p><strong>This is a critical legal protection for water users.</strong> If contracted water delivery is correctly classified as non-discretionary and placed in the environmental baseline, the Services cannot use an RPA to cut it. Their authority to impose mitigation through the RPA process is limited to the agency&#8217;s discretionary actions &#8212; the things Reclamation actually has the legal freedom to change.</p><div><hr></div><p><strong>Discretionary Actions &#8212; The Proposed Action</strong></p><p>A discretionary action is something Reclamation has genuine operational flexibility over &#8212; a choice within a range of legally permissible options. How it times certain releases. How it manages lake elevations within a permitted band. Operational decisions where the law leaves room for judgment.</p><p>Only discretionary actions belong in the Proposed Action. Only discretionary actions can be evaluated for jeopardy. Only discretionary actions can be modified by an RPA.</p><p>The Proposed Action is, therefore, a description of how Reclamation intends to exercise its discretionary operational authority &#8212; not a description of everything Reclamation does. The non-discretionary core &#8212; water delivery under contract &#8212; is the baseline. The discretionary operational choices &#8212; how Reclamation manages the system around that core &#8212; are what get evaluated.</p><p><strong>Why this must be done without input from the biological agencies or outside groups:</strong> Because the classification of actions as discretionary or non-discretionary is itself a legal determination that belongs to Reclamation, based on its own statutory authority and contractual obligations. If outside parties are allowed to influence how Reclamation sorts its actions before the formal process begins, they can reclassify non-discretionary water delivery as a discretionary operational choice &#8212; and suddenly the contracted water supply becomes negotiable through the RPA process. The baseline gets converted into a bargaining chip.</p><p>That conversion is the foundation of the procedural inversion described in Section IV. It begins not with a bad BiOp, but with a corrupted Step 1 sorting exercise &#8212; one in which Reclamation&#8217;s non-discretionary obligation to deliver contracted water is quietly folded into the Proposed Action as though it were an operational choice subject to modification. Once that reclassification occurs, everything downstream is compromised.</p><p><strong>The correct Proposed Action for the Klamath Project</strong> describes Reclamation&#8217;s discretionary operational choices &#8212; how it will manage the system &#8212; against a baseline that includes full contracted water delivery as a given. The biological analysis then evaluates whether those discretionary choices jeopardize listed species. The non-discretionary delivery obligation is not on the table. It never was.</p><div><hr></div><h3>Step 2 &#8212; Reclamation Officially Submits the Consultation Package</h3><p>Once the Proposed Action is written, Reclamation formally initiates consultation by submitting a complete package to NMFS and USFWS under 50 CFR &#167; 402.14(c).&#185;&#8309; The package includes the PA, supporting technical data, a description of the affected area, and a description of which listed species may be affected.</p><p>When NMFS and USFWS receive the complete package, a 135-day clock starts running.&#185;&#8310; During those 135 days, the biological agencies do their analysis. Reclamation waits.</p><p><strong>The agencies are now in separate lanes. Reclamation has submitted its plan. The biological agencies evaluate it independently.</strong></p><div><hr></div><h3>Step 3 &#8212; The Biological Agencies Evaluate the Plan and Issue a Finding</h3><p>NMFS and USFWS study the Proposed Action. They look at the science: what water flows are proposed, what species are present, what the habitat looks like, what the best available biological data shows about harm thresholds.</p><p>Then they issue the Biological Opinion.&#185;&#8311;</p><p>The BiOp has one of two possible conclusions:</p><p><strong>No Jeopardy</strong> &#8212; The proposed action, as submitted, will not push listed species toward extinction. Reclamation can proceed. For irrigation districts, a No-Jeopardy finding on a <em>full-delivery</em> Proposed Action is extremely valuable: it establishes on the official record that delivering full contracted water under current river conditions does not harm listed species. That finding is durable and defensible in court.</p><p><strong>Jeopardy</strong> &#8212; The proposed action, as submitted, will push listed species toward extinction. Reclamation cannot proceed with that plan as written. But the process does not stop there. A Jeopardy finding automatically triggers the next step.</p><p><strong>Both findings are useful. Both findings are honest. The process is designed to produce truth, not to produce a predetermined answer.</strong></p><div><hr></div><h3>Step 4 &#8212; If Jeopardy Is Found, the Solution Phase Opens</h3><p>A Jeopardy finding is not a dead end. It is an opening.</p><p>Under Section 7 of the ESA and 50 CFR &#167; 402.14(i), once a Jeopardy BiOp is issued, the law requires the biological agencies to propose a <strong>Reasonable and Prudent Alternative</strong> (RPA) &#8212; a modified plan that (a) still accomplishes the core purpose of the project, (b) stays within the legal authority of the agencies involved, (c) is technically and economically feasible, and (d) avoids the jeopardy problem.</p><p>This is where <strong>irrigation districts enter the process with legal standing as formal applicants</strong> &#8212; not as commenters, not as stakeholders sitting in the back of the room, but as parties with a recognized seat at the table and the right to propose solutions.&#185;&#8312;</p><p>In the Klamath context, Step 4 is where a district could formally propose a <strong>&#8220;Flow-Through&#8221; operational model</strong> &#8212; a structured framework specifying exactly how much water passes through to the river to protect biological conditions at each point in the irrigation season, with the remainder delivered to farmers under their contracts. If accepted as an RPA, that agreement is enforceable, durable, and protects all parties from future ESA liability.</p><p>It is also where districts could elect a longer-term instrument: a <strong>Section 10 Habitat Conservation Plan (HCP)</strong>.&#185;&#8313; An HCP is a negotiated, legally binding agreement between the districts and the federal government, specifying mitigation measures in exchange for an Incidental Take Permit for the life of the plan &#8212; potentially 20, 30, or 50 years. Under the &#8220;No Surprises&#8221; rule, once an HCP is approved, the government cannot come back and impose additional restrictions beyond what the plan specifies.</p><p><strong>Step 4 is the district&#8217;s statutory moment.</strong> But it only opens if Step 3 produces an honest finding. And Step 3 can only produce an honest finding if Step 1 submitted an honest Proposed Action. The entire sequence depends on Step 1 being done correctly and independently.</p><div><hr></div><h2>IV. What Is Actually Happening &#8212; Procedural Inversion, Explained</h2><p>Now that the correct sequence is clear, here is what procedural inversion means in plain language.</p><p><strong>Reclamation is writing the Proposed Action together with the agencies and stakeholders who are supposed to evaluate it &#8212; before the formal process begins. The fix is in before the clock starts.</strong></p><p>Before Reclamation ever formally initiates consultation, agency officials and their counterparts at NMFS, USFWS, state water agencies, tribal governments, and allied environmental organizations are in contact &#8212; through meetings, working groups, informal correspondence, and coordination calls. The subject of those conversations is not administrative housekeeping. The subject is: <em>what will the Proposed Action say?</em></p><p>Specifically: What flow levels will it commit to? What curtailment triggers will it include? What Upper Klamath Lake elevation thresholds will it build in? What drought-tier restrictions will be written into the operating rules?</p><p>These are not incidental details. They are the operational constraints that determine how much water reaches farms, and when, and under what conditions deliveries can be cut off.</p><p><strong>By the time Reclamation formally sits down to write the Biological Assessment, those questions have already been answered &#8212; informally, off the record, in rooms and calls that do not appear in the consultation file.</strong></p><p>The document Reclamation then submits &#8212; presented as its independent determination of what it is legally obligated to do &#8212; is not that. It is a pre-agreed product dressed up as an independent agency determination.</p><p><strong>The 2024 Biological Assessment and the resulting 2024 BiOp are the documentary evidence of this pattern.</strong></p><p>The Proposed Action that Reclamation submitted in its June 2024 Biological Assessment&#178;&#8304; already included Keno Dam compliance flows, drought-tier curtailment rules, Upper Klamath Lake elevation requirements, and associated delivery restrictions &#8212; all of which reduce the water available to Klamath Project contractors below their contracted entitlements. These constraints were already baked into the document when it was submitted.</p><p>NMFS then received that pre-constrained PA, evaluated it, and issued its October 28, 2024 No-Jeopardy Biological Opinion.&#178;&#185;</p><p>The No-Jeopardy finding is cited &#8212; publicly, frequently &#8212; as proof that Klamath Project operations are consistent with ESA obligations. <strong>It proves no such thing.</strong> It proves that a specific, pre-constrained, pre-negotiated operating regime &#8212; one that already cuts farmers&#8217; water &#8212; does not jeopardize listed species. It says nothing about whether <em>full contractual deliveries</em> under <em>current post-dam-removal river conditions</em> would jeopardize listed species. That question has never been honestly posed. The answer is not in the record because the question was never put to the test.</p><p><strong>The sequence was inverted. The conclusion shaped the premise. The administrative record reflects the endpoint of a negotiation, not the output of an independent scientific evaluation.</strong></p><p>Note also what this means in relation to Section 7(a)(1). If Reclamation had fulfilled its affirmative conservation obligations under 7(a)(1) &#8212; by developing and implementing genuine conservation programs using its operational authorities &#8212; the Section 7(a)(2) consultation baseline would look materially different. An agency that has actively invested in conservation programs enters consultation with a record of good-faith performance. An agency that has done nothing under 7(a)(1) and then pre-negotiates its 7(a)(2) Proposed Action has compounded a statutory omission with a procedural inversion. Both failures run in the same direction: away from the honest, independent record that the law requires.</p><div><hr></div><h2>V. Why This Is Lawfare &#8212; Three Concrete Consequences</h2><p>Procedural inversion is not an administrative technicality. It produces three specific, concrete harms to Klamath Project water users, each of which functions as a component of lawfare as defined in Post No. 1.</p><div><hr></div><h3>Consequence 1: The Administrative Record Is Corrupted &#8212; and It Cannot Be Challenged From the Outside</h3><p>Federal courts reviewing agency action under the APA are limited to the administrative record.&#178;&#178; A judge evaluating whether a Biological Opinion was arbitrary or capricious looks at the documents in the record and asks whether the agency&#8217;s conclusion follows logically from what is in front of it.</p><p><strong>The decisions that actually determined the outcome of the 2024 consultation are not in the record.</strong> The conversations in which Reclamation and the biological agencies agreed on what the PA would say &#8212; not in the record. The working-group meetings where curtailment thresholds were negotiated &#8212; not in the record. The informal coordination that produced the specific flow numbers and lake-level triggers &#8212; not in the record.</p><p>What is in the record is the finished product of those conversations, presented as an independent agency determination.</p><p>A reviewing court sees an agency that wrote a Biological Assessment, submitted it, received a BiOp, and followed the process. The court has no visibility into the pre-negotiation. The corruption is invisible because it happened before the reviewable record began.</p><p><strong>For irrigation districts and their attorneys, this is a trap.</strong> The record they would need to challenge is the record that was already constructed against them, before they had any formal standing to object.</p><div><hr></div><h3>Consequence 2: The Notice-and-Comment Process Is Bypassed Entirely</h3><p>The APA requires federal agencies to publish proposed rules, accept public comments, respond to those comments, and justify their final decisions in the record.&#178;&#179; This notice-and-comment process is the primary mechanism through which affected parties &#8212; including farmers and irrigation districts &#8212; can challenge the factual premises of agency action before it becomes binding.</p><p>When Reclamation pre-negotiates the operational constraints that go into a Proposed Action, it achieves the same substantive result as a formal rulemaking &#8212; new, binding operational restrictions on water delivery &#8212; <strong>without publishing anything, without accepting public comments, and without creating a reviewable record of the decisional process.</strong></p><p>Irrigation districts are not in the room where the constraints are agreed upon. By the time formal consultation begins and the public-facing documents appear, the substantive decisions are already made.</p><p><strong>Pre-negotiation accomplishes, off the record and without accountability, exactly what formal rulemaking would require the agency to defend in public.</strong></p><div><hr></div><h3>Consequence 3: The Districts&#8217; Statutory Role in the Solution Phase Is Eliminated</h3><p>The law gives irrigation districts a specific role at Step 4. It is a statutory right: to enter the process as formal applicants, propose RPAs, and pursue a long-term HCP that provides durable legal certainty.</p><p><strong>That role only exists if a Jeopardy finding is issued at Step 3.</strong></p><p>If the Proposed Action is pre-engineered to produce a No-Jeopardy finding, Step 4 never opens. The Solution Phase never begins. The districts are never recognized as applicants. The Flow-Through model is never formally evaluated. The HCP pathway is never pursued on the record.</p><p>The districts cannot propose solutions to a problem the record says does not exist.</p><p>They operate under a BiOp that evaluated a constrained plan they did not design, on behalf of a river that has fundamentally changed, with no formal record establishing what their full legal entitlements look like under current conditions. Their compliance is mandatory. Their remedies are foreclosed. Their strategic options are extinguished before the formal process begins.</p><p><strong>That is the lawfare. Not the BiOp. Not the consultation. The pre-negotiation that made the BiOp&#8217;s outcome inevitable before the clock started.</strong></p><p>Add to that the unmet Section 7(a)(1) obligation. Districts are being regulated under an escalating series of 7(a)(2) BiOps, each one built on a pre-negotiated baseline, while the affirmative conservation mandate that would require the agencies to actively invest in recovery &#8212; using their own authorities, at their own initiative &#8212; has gone unimplemented since the day the first sucker was listed. The regulated party bears the compliance burden. The regulating agency bears none of the affirmative conservation burden. That asymmetry is not an accident of administration. It is the structure of the lawfare.</p><div><hr></div><h2>VI. The Case for a Clean Record</h2><p>What a clean record requires is straightforward: Reclamation submits a Proposed Action reflecting its actual, full non-discretionary legal obligations under current, post-dam-removal river conditions, and the biological agencies evaluate it independently. Simultaneously, Reclamation and USFWS develop and publish a formal Section 7(a)(1) programmatic conservation plan &#8212; finally accounting for the affirmative statutory duty that has gone unmet for decades.</p><p>The post-dam-removal Klamath River is a materially different system from the one on which every prior consultation was based. In 2025, 51,277 adult fall-run Chinook returned to the basin at 205 percent of the pre-season forecast &#8212; while Project operations continued without modification.&#178;&#8308; More than 400 miles of anadromous habitat has been reopened. Microcystin blooms that previously exceeded public health limits in 58 percent of lower-river samples are now non-detectable in 82 percent.&#178;&#8309; Chinook have been documented spawning more than 360 river miles from the ocean for the first time in over a century.</p><p>Not one of these changed conditions has been evaluated against a full-delivery Proposed Action. The operating restrictions on Klamath Project water users were calibrated against a river that no longer exists. The Section 7(a)(1) conservation programs that should have been running for thirty years have not been written.</p><p>A clean record forces both evaluations. The outcome &#8212; whatever it is &#8212; becomes the honest, legally defensible basis for operational decisions going forward.</p><p>If No Jeopardy: the districts have a durable record establishing that full deliveries are consistent with species recovery under current conditions. If Jeopardy: Step 4 opens, districts enter as applicants, and the Flow-Through model and HCP are formally evaluated with all parties&#8217; rights on the record.</p><p>Either outcome is better than what exists today: a consultation record built on a pre-negotiated baseline, governing a river it was not designed for, producing legal cover for delivery restrictions that were never independently evaluated &#8212; and a Section 7(a)(1) conservation mandate that has been ignored by the very agencies charged with enforcing it.</p><p>This archive will continue to document the gap between the process as it is required to function and the process as it is currently functioning. The administrative record is the battlefield. Building a clean one is the objective.</p><div><hr></div><h2>Footnotes</h2><p>&#185; 16 U.S.C. &#167; 1536(a)(1), affirmative conservation mandate. Full text: <a href="https://www.law.cornell.edu/uscode/text/16/1536">https://www.law.cornell.edu/uscode/text/16/1536</a></p><p>&#178; The Secretary of the Interior&#8217;s obligation under 16 U.S.C. &#167; 1536(a)(1) to &#8220;assist&#8221; federal agencies in carrying out conservation programs is a co-obligation, not merely advisory. USFWS, as a bureau within the Department of the Interior, operates under direct Secretarial authority on this point.</p><p>&#179; 16 U.S.C. &#167; 1536(a)(2), jeopardy consultation mandate. Full text: <a href="https://www.law.cornell.edu/uscode/text/16/1536">https://www.law.cornell.edu/uscode/text/16/1536</a></p><p>&#8308; Office of the Solicitor, U.S. Department of the Interior. <em>Memorandum: Federal Agency Obligations under Section 7(a)(1) of the Endangered Species Act.</em> February 6, 2024. From: Sarah Krakoff, Deputy Solicitor for Parks and Wildlife; Shawn Finley, Attorney-Advisor, Division of Parks and Wildlife. To: Martha Williams, Director, U.S. Fish and Wildlife Service. Available at: <a href="https://www.fws.gov/sites/default/files/documents/federal-agency-obligations-under-section-7-a-1-memo-2024-02-06.pdf">https://www.fws.gov/sites/default/files/documents/federal-agency-obligations-under-section-7-a-1-memo-2024-02-06.pdf</a>. The memo expressly states that compliance with Section 7(a)(2) is not equivalent to compliance with Section 7(a)(1), citing <em>CBD v. Vilsack</em>, 276 F. Supp. 3d 1015, 1032 (D. Nev. 2017).</p><p>&#8309; <em>TVA v. Hill</em>, 437 U.S. 153, 185 (1978). The Supreme Court described Section 7(a)(1)&#8217;s language as &#8220;stringent, mandatory language&#8221; and held that the legislative history reveals &#8220;an explicit Congressional decision to require agencies to afford first priority to the declared national policy of saving endangered species.&#8221;</p><p>&#8310; <em>Platte River Whooping Crane Critical Habitat Maintenance Trust v. FERC</em>, 962 F.2d 27, 34 (D.C. Cir. 1992). The court rejected the argument that ESA Sections 7(a)(1) and 7(a)(2) obligate agencies to do &#8220;whatever it takes&#8221; to protect listed species when doing so would exceed the limitations contained in the agency&#8217;s relevant enabling authority.</p><p>&#8311; Reclamation Act of 1902, 32 Stat. 388, 43 U.S.C. &#167; 371 et seq. The Klamath Project was formally established under this authority in 1905. The Project&#8217;s enabling authorization describes a single authorized function: delivery of water to irrigable lands in the Klamath and Lost River Basins of Oregon and California. Full text: <a href="https://www.usbr.gov/lc/region/g1000/reclamationact.pdf">https://www.usbr.gov/lc/region/g1000/reclamationact.pdf</a></p><p>&#8312; The limitation on RPA scope is established by 50 CFR &#167; 402.14(i)(3), which requires that a Reasonable and Prudent Alternative &#8220;can be implemented in a manner consistent with the scope of the Federal agency&#8217;s legal authority and jurisdiction.&#8221; An RPA requiring Reclamation to implement conservation measures outside its project authorization would fail this test. <em>See also Platte River Whooping Crane</em>, 962 F.2d at 34.</p><p>&#8313; <em>Florida Key Deer v. Paulison</em>, 522 F.3d 1133, 1147 (11th Cir. 2008). The court held that an agency&#8217;s conservation program producing only insignificant effects on listed species amounts to inaction and violates Section 7(a)(1). Cited in the Solicitor&#8217;s Memorandum, supra note 4.</p><p>&#185;&#8304; Solicitor&#8217;s Memorandum, supra note 4, at conclusion. The full quoted sentence: &#8220;Robust Section 7(a)(1) programs therefore have the potential to streamline or, in highly successful cases, eliminate the need for consultation under Section 7(a)(2).&#8221; The memo also references J.B. Ruhl, <em>Section 7(a)(1) of the &#8220;New&#8221; Endangered Species Act: Rediscovering and Redefining the Untapped Power of Federal Agencies&#8217; Duty to Conserve Species</em>, 25 Envt&#8217;l L. 1107, 1109 (1995), describing the provision as &#8220;the sleeping giant of the ESA programs.&#8221;</p><p>&#185;&#185; <em>Sierra Club v. Glickman</em>, 156 F.3d 606, 618 (5th Cir. 1998). The court rejected USDA&#8217;s argument that national farm programs providing incidental benefits to aquifer-dependent listed species satisfied Section 7(a)(1), holding that the statute requires &#8220;species-specific measures developed in consultation with FWS.&#8221;</p><p>&#185;&#178; 50 CFR &#167; 402.14, <em>Formal Consultation.</em> Full text: <a href="https://www.ecfr.gov/current/title-50/chapter-IV/subchapter-A/part-402/subpart-B/section-402.14">https://www.ecfr.gov/current/title-50/chapter-IV/subchapter-A/part-402/subpart-B/section-402.14</a></p><p>&#185;&#179; U.S. Fish and Wildlife Service and National Marine Fisheries Service. <em>Endangered Species Consultation Handbook: Procedures for Conducting Section 7 Consultations and Conferences.</em> March 1998. Available at: <a href="https://www.fws.gov/sites/default/files/documents/endangered-species-consultation-handbook.pdf">https://www.fws.gov/sites/default/files/documents/endangered-species-consultation-handbook.pdf</a></p><p>&#185;&#8308; The discretionary/non-discretionary distinction and the environmental baseline concept are codified at 50 CFR &#167; 402.03 (&#8221;Section 7 and the requirements of this part apply to all actions in which there is discretionary Federal involvement or control&#8221;), 50 CFR &#167; 402.02 (definition of &#8220;action&#8221;), and elaborated in the ESA Section 7 Consultation Handbook at pp. 4-21 to 4-23. The environmental baseline is defined in the Handbook as &#8220;the condition of the listed species or its designated critical habitat in the action area, without the consequences caused by the proposed action.&#8221; Non-discretionary agency obligations are part of the baseline condition, not the proposed action, and are not subject to modification through a Reasonable and Prudent Alternative. <em>See also</em> 50 CFR &#167; 402.14(g)(2).</p><p>&#185;&#8309; 50 CFR &#167; 402.14(c), initiation requirements for formal consultation &#8212; specifying the content of the written request and supporting documentation required to begin the formal 135-day period.</p><p>&#185;&#8310; 50 CFR &#167; 402.14(e). The 135-day consultation period runs from the date the Services receive the completed initiation package. A 60-day extension is available under 50 CFR &#167; 402.14(e)(2).</p><p>&#185;&#8311; 16 U.S.C. &#167; 1536(b)(3), Biological Opinion requirements. See also 50 CFR &#167; 402.14(h) for the full regulatory specification of required BiOp contents including the incidental take statement.</p><p>&#185;&#8312; 50 CFR &#167; 402.14(i), Reasonable and Prudent Alternatives. RPAs must be consistent with the scope of the action agency&#8217;s legal authority, economically and technologically feasible, and capable of avoiding the likelihood of jeopardy.</p><p>&#185;&#8313; 16 U.S.C. &#167; 1539(a)(2), HCP requirements for incidental take permits. &#8220;No Surprises&#8221; assurance: 50 CFR &#167; 17.22(b)(5).</p><p>&#178;&#8304; Bureau of Reclamation, <em>Biological Assessment for Klamath Project Operations, October 2024 &#8211; September 2029,</em> submitted to NMFS and USFWS, June 2024. The operational constraints incorporated into the BA &#8212; Keno Dam compliance flows, drought-tier curtailment rules, Upper Klamath Lake elevation requirements &#8212; are the pre-negotiated elements described in Section IV.</p><p>&#178;&#185; National Marine Fisheries Service, <em>Biological Opinion on Bureau of Reclamation Klamath Project Operations (FY2025&#8211;FY2029),</em> October 28, 2024. Available at: <a href="https://www.fisheries.noaa.gov/s3//2024-11/biological-opinion-klamath-project-operations-2024.pdf">https://www.fisheries.noaa.gov/s3//2024-11/biological-opinion-klamath-project-operations-2024.pdf</a> | Document page: <a href="https://www.fisheries.noaa.gov/resource/document/2024-klamath-project-biological-opinion">https://www.fisheries.noaa.gov/resource/document/2024-klamath-project-biological-opinion</a></p><p>&#178;&#178; Administrative Procedure Act, 5 U.S.C. &#167; 706. Review is confined to the administrative record compiled by the agency. Full text: <a href="https://www.law.cornell.edu/uscode/text/5/706">https://www.law.cornell.edu/uscode/text/5/706</a></p><p>&#178;&#179; 5 U.S.C. &#167; 553, <em>Rule Making.</em> Notice-and-comment requirements apply to substantive rulemaking. Pre-decisional informal negotiations that functionally determine the binding operational content of a Proposed Action are not insulated from APA scrutiny by the label of &#8220;consultation planning.&#8221;</p><p>&#178;&#8308; California Department of Fish and Wildlife, <em>&#8220;Salmon Everywhere&#8221;: One Year After Klamath Dam Removal,</em> November 2025. Available at: <a href="https://wildlife.ca.gov/News/Archive/salmon-everywhere-one-year-after-klamath-dam-removal">https://wildlife.ca.gov/News/Archive/salmon-everywhere-one-year-after-klamath-dam-removal</a>. Return data also reported in: Fishing the North Coast, <em>Klamath Fall Chinook Return Tops Expectations in 2025,</em> February 19, 2026. Available at: <a href="https://fishingthenorthcoast.com/2026/02/19/klamath-fall-chinook-return-tops-expectations-in-2025/">https://fishingthenorthcoast.com/2026/02/19/klamath-fall-chinook-return-tops-expectations-in-2025/</a></p><p>&#178;&#8309; NOAA Fisheries, <em>Final Step in Klamath River Dam Removal Opens Path for Returning Salmon.</em> Available at: <a href="https://www.fisheries.noaa.gov/feature-story/final-step-klamath-river-dam-removal-opens-path-returning-salmon">https://www.fisheries.noaa.gov/feature-story/final-step-klamath-river-dam-removal-opens-path-returning-salmon</a>. Every prior Klamath Project Biological Opinion &#8212; 2002, 2008, 2010, 2013, 2019 &#8212; was developed under pre-dam-removal river conditions. The four lower-mainstem dams were removed between summer 2023 and October 2024.</p><p>&#178;&#8310; Driscoll, Moss (Director of Water Policy, Klamath Water Users Association). <em>Memorandum: Endangered Species Act Costs Incurred in Connection with the Klamath Project.</em> To: Paul Simmons, Executive Director and Counsel, KWUA. August 30, 2024. On file with KWUA, Klamath Falls, Oregon. The memorandum provides a detailed analysis of Reclamation&#8217;s project authorities under the Reclamation Act of 1902, the 1998 regional committee decision to reclassify ESA costs as nonreimbursable, the collapsed SPCCR accounting record, and the absence of any federal law authorizing the ESA activities funded through Project appropriations. The memorandum further identifies the Agency Lake Ranch purchase as the only documented instance in Klamath Project history where Section 7(a)(1) was cited as the formal authority for Reclamation action benefiting listed species. The specific ESA compliance budget figures &#8212; $13.3 million (FY2021) through $28.6 million (FY2024) &#8212; are drawn from this memorandum.</p><p>&#178;&#8311; Simmons, Paul (Executive Director and Counsel, KWUA). <em>Memorandum: Project Debt.</em> To: Elizabeth Nielsen, Executive Director, KWUA. January 12, 2026. Transmitting the Driscoll Memorandum and providing supplemental analysis of outstanding cost issues including the A Canal fish screen and headworks (subject of a 2016 OIG report finding the costs reimbursable by KID), the Clear Lake Dam replacement, and the C Siphon repayment contract. The memorandum notes that Reclamation has raised the reimbursability of ESA costs in recent meetings and correspondence with KID, and that no complete or accurate SPCCR has been produced for the Project in any year in the current century. Copies to Wyatt Kane, Mark Limbaugh, Chris Kearney, and Brittany Johnson.</p><p>&#178;&#8312; Souza, Gene (Executive Director, Klamath Irrigation District). <em>Letter to Congressman Cliff Bentz re: Klamath Watershed Restoration Activity Summary,</em> with attached Table of Klamath Projects since 1988 (13 pages). October 18, 2024. On file with Klamath Irrigation District, Klamath Falls, Oregon. The cover letter states it provides &#8220;estimates of the economic burden on the American People, the Klamath Farmers, and the communities in the Klamath watershed between 2001 and 2027&#8221;; the attached table is titled &#8220;Table of Klamath Projects since 1988&#8221; and includes line items dating to 1988. The document identifies 98 discrete line items with documented American taxpayer costs. The cover letter&#8217;s own summary states: American taxpayer expenditures in excess of $560 million; additional losses to Klamath farmers exceeding $1.06 billion. The dam removal line item in the table lists $250 million (California) plus $45 million Oregon/California contingency in the American Taxpayer column, and separately records $200 million in the &#8220;Levied Costs on rate payers without a vote&#8221; column, with that figure labeled in the source document as &#8220;Tribal &amp; Ecological groups PR &amp; litigation, ???.&#8221; The sum of all documented line items in the table&#8217;s American Taxpayer column, independently tallied from the table, exceeds $614 million; the difference from the letter&#8217;s stated $560 million reflects the document&#8217;s own notation that the $162 million BIL figure is duplicative of several individually listed projects, as well as rounding methodology.</p><div><hr></div><p><em>Next in the Foundational Archive &#8212; Post No. 4: The Biological Opinion as a Legal Instrument: How Jeopardy Findings, RPAs, and Incidental Take Statements Distribute Legal Risk Across the Consultation Record.</em></p><div><hr></div><p><em>Klamath Basin Lawfare is an independent public archive. All source material is derived from public records, statutes, regulations, and agency guidance documents. This archive applies the procedural inversion framework only where the administrative record demonstrates a documented departure from the mandatory consultation sequence &#8212; not from the fact of regulatory constraint alone. Editorial correspondence and records submissions may be directed to the archive.</em></p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://www.klamathbasinlawfare.org/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading Klamath Basin Lawfare! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div>]]></content:encoded></item><item><title><![CDATA[What Is Lawfare?]]></title><description><![CDATA[Foundational Post No. 1]]></description><link>https://www.klamathbasinlawfare.org/p/what-is-lawfare</link><guid isPermaLink="false">https://www.klamathbasinlawfare.org/p/what-is-lawfare</guid><dc:creator><![CDATA[Transparency]]></dc:creator><pubDate>Sat, 23 May 2026 19:24:12 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!lZbK!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fbce6671f-d95c-4d15-9c2c-f87d7868f047_512x512.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<h1>What Is Lawfare?</h1><p><em>Klamath Basin Lawfare &#8212; Foundational Post No. 1</em></p><div><hr></div><p>The term &#8220;lawfare&#8221; circulates widely in political commentary, frequently stripped of its analytical precision and reduced to a rhetorical charge. This archive uses it in a specific, documented, and academically grounded sense. Before this publication tracks a single case, files a single records request, or publishes a single exhibit, it is necessary to establish exactly what lawfare means, where the definition comes from, how it has been challenged, and why&#8212;properly bounded&#8212;it remains a legitimate and necessary analytical instrument.</p><div><hr></div><h2>I. The Origin: Law as a Substitute for Traditional Means</h2><p>The term was introduced into formal strategic discourse in 2001 by <strong>Major General Charles J. Dunlap Jr.</strong>, then-Deputy Judge Advocate General of the United States Air Force, in a paper delivered at the Humanitarian Challenges in Military Intervention Conference, hosted by the Carr Center for Human Rights Policy at Harvard University&#8217;s Kennedy School of Government.&#185;</p><p>Dunlap defined lawfare as:</p><blockquote><p><em>&#8220;The strategy of using&#8212;or misusing&#8212;law as a substitute for traditional military means to achieve an operational objective.&#8221;</em></p></blockquote><p>The definition is deliberately value-neutral. Dunlap was not describing something categorically illegitimate. He was identifying a strategic category: the use of legal process as an instrument of operational power, capable of achieving outcomes that would otherwise require conventional force, negotiation, or political capital. He subsequently elaborated this framework in a 2008 article in the <em>Yale Journal of International Affairs</em>, acknowledging that legal mechanisms can serve either constructive or destructive ends depending on their deployment.&#178;</p><p>The key phrase is <strong>&#8220;substitute for traditional means.&#8221;</strong> The legal system, in this framework, is not primarily a venue for establishing truth or resolving disputes on their merits. It is a tool&#8212;deployable, scalable, and effective against a target who cannot afford to ignore it.</p><div><hr></div><h2>II. The Mechanism: Compliance-Leverage Disparity</h2><p>In his 2016 work <em>Lawfare: Law as a Weapon of War</em>, published by Oxford University Press, legal scholar <strong>Orde Kittrie</strong> systematized Dunlap&#8217;s framework into operational subcategories with documented historical case studies.&#179; The subcategory most directly applicable to domestic regulatory and land-use contexts is <strong>Compliance-Leverage Disparity Lawfare</strong>.</p><p>The mechanism operates as follows:</p><p><strong>Party A</strong> is a regulated entity&#8212;a farm, a water user, a rural business&#8212;that holds permits, operates under agency oversight, and has a documented legal and financial commitment to regulatory compliance. Departure from that compliance carries severe consequences: permit revocation, fines, injunctions, loss of operating authority.</p><p><strong>Party B</strong> initiates or supports legal and administrative challenges against Party A. Party B&#8217;s objective is not necessarily to prevail on the merits of any given argument. The objective is to impose costs.</p><p>The disparity is structural:</p><ul><li><p>Party A cannot walk away from the legal process without forfeiting the permits and authorizations their operations depend upon.</p></li><li><p>Party A must retain legal counsel, respond to discovery, appear at hearings, and manage agency relationships&#8212;indefinitely, and at full cost.</p></li><li><p>Party B faces no equivalent constraint. A challenge can be filed, withdrawn, amended, or re-filed at minimal expense relative to the cost it imposes on the target.</p></li></ul><p>The result is <strong>asymmetric attrition</strong>. The legal system&#8217;s procedural architecture&#8212;designed to ensure due process&#8212;is inverted into a cost-imposition engine. Time, capital, and organizational capacity are drained from the target, regardless of the underlying legal merit of the challenge.</p><p>In domestic administrative practice, this pattern has an established parallel: the <strong>Strategic Lawsuit Against Public Participation (SLAPP)</strong>, a term coined by legal scholars George Pring and Penelope Canan following their systematic study of retaliatory civil litigation.&#8308; While SLAPP doctrine was originally developed to protect public participation rights against powerful institutional plaintiffs, the same structural asymmetry operates in reverse when administrative challenges are used against individual regulated parties who lack the resources of the challenging organization.</p><div><hr></div><h2>III. The Counterargument: The Term Has Been Weaponized</h2><p>This is the objection that must be addressed before this archive proceeds.</p><p>A significant body of legal scholarship argues that &#8220;lawfare&#8221; is itself a politically loaded term&#8212;one that has been selectively deployed by state and military actors to delegitimize legitimate human rights litigation, war crimes accountability mechanisms, and judicial oversight of executive power. The critique deserves a precise statement.</p><p>Legal scholar David Kennedy, in his influential work <em>Of War and Law</em> (Princeton University Press, 2006), documented how legal framing has become inseparable from the conduct of modern war&#8212;used by all parties, including powerful states, to authorize violence, manage accountability, and shape public narrative.&#8309; The implication is that &#8220;lawfare&#8221; accusations can function as a shield against legitimate legal scrutiny, not merely a description of abusive legal tactics.</p><p>Scott Horton, writing in the <em>Case Western Reserve Journal of International Law</em>, made this critique most directly: that the lawfare label has been applied opportunistically by actors who find legal accountability inconvenient, effectively stigmatizing human rights advocates and plaintiff-side litigants as bad-faith combatants rather than legitimate legal participants.&#8310;</p><p>Lisa Hajjar&#8217;s comparative analysis of Israeli and American military legal doctrines further demonstrated that the accusation of lawfare is frequently asymmetric&#8212;invoked against challengers of state power while the legally aggressive conduct of state institutions escapes the same characterization.&#8311;</p><p><strong>This archive takes these objections seriously.</strong> They establish something important: the lawfare label, used imprecisely, is a rhetorical cudgel. Applied without evidentiary discipline, it can be used to pre-emptively delegitimize any legal challenge brought by any party the labeler dislikes. That is not analysis. That is advocacy dressed as terminology.</p><div><hr></div><h2>IV. Why the Framework Remains Valid&#8212;With Discipline</h2><p>The scholarly critique of lawfare does not invalidate the concept. It defines the conditions under which the concept is analytically legitimate.</p><p>The Dunlap-Kittrie framework is valid when the following conditions are demonstrable from the record:</p><ol><li><p><strong>The procedural pattern is documentable.</strong> Filing frequency, withdrawal timing, and cost-imposition effects must be traceable through court records, agency dockets, and disclosed financial data&#8212;not inferred from political alignment.</p></li><li><p><strong>The merit-to-cost ratio is assessable.</strong> Lawfare, properly defined, is distinguished from aggressive but good-faith litigation by the relationship between the legal arguments advanced and the procedural costs imposed. Cases that produce substantial legal costs while advancing novel, weak, or repeatedly rejected legal theories warrant scrutiny that cases litigated to clear, contested legal questions do not.</p></li><li><p><strong>The compliance asymmetry is structural, not merely tactical.</strong> The defining feature of compliance-leverage disparity is that one party&#8217;s regulatory exposure prevents exit from the legal process while the other faces no equivalent constraint. This must be demonstrated, not assumed.</p></li><li><p><strong>The pattern is longitudinal.</strong> A single aggressive legal challenge is not lawfare. A documented pattern&#8212;of challenges filed, withdrawn, refiled, or transferred across forums as prior venues close&#8212;is a different analytical object.</p></li></ol><p>This archive commits to applying the framework under these conditions only. Where the record does not support a lawfare characterization, that will be stated. Where it does, it will be documented.</p><div><hr></div><h2>V. The Local Application: What This Archive Is</h2><p>The Klamath Basin presents a documented environment for compliance-leverage disparity analysis. Water adjudications, federal regulatory proceedings, agency rulemaking, and multi-party litigation have run concurrently and sequentially in this region for decades. The cumulative burden on individual water users, agricultural operators, and local governments is measurable&#8212;in legal fees, foregone investment, administrative staff time, and operational uncertainty.</p><p><strong>Klamath Basin Lawfare</strong> exists to track and document these patterns at the local level, under the evidentiary discipline described above.</p><p>This publication operates on a specific standard: <strong>direct public records and government receipts</strong>. Court filings, agency correspondence, permit records, administrative decisions, and official transcripts. No anonymous sourcing. No inference where documentation is available. No allegation unsupported by an exhibit.</p><p>The archive&#8217;s function is taxonomic and longitudinal. Individual legal actions are rarely self-explanatory in isolation. Patterns become visible over time, across cases, and across institutions. This publication intends to build that record&#8212;and to hold itself to the same evidentiary standard it applies to the conduct it documents.</p><div><hr></div><h2>Footnotes</h2><p>&#185; Dunlap, Charles J., Jr. &#8220;Law and Military Interventions: Preserving Humanitarian Values in 21st Century Conflicts.&#8221; Paper presented at the Humanitarian Challenges in Military Intervention Conference, Carr Center for Human Rights Policy, Kennedy School of Government, Harvard University, November 29, 2001.</p><p>&#178; Dunlap, Charles J., Jr. &#8220;Lawfare Today: A Perspective.&#8221; <em>Yale Journal of International Affairs</em>, Winter/Spring 2008, pp. 146&#8211;154.</p><p>&#179; Kittrie, Orde F. <em>Lawfare: Law as a Weapon of War</em>. Oxford University Press, 2016.</p><p>&#8308; Pring, George W., and Penelope Canan. <em>SLAPPs: Getting Sued for Speaking Out</em>. Temple University Press, 1996. Pring and Canan&#8217;s original study analyzed over 300 civil actions filed against citizens engaging in public participation and identified the structural pattern of cost-imposition as the operative mechanism regardless of legal merit.</p><p>&#8309; Kennedy, David. <em>Of War and Law</em>. Princeton University Press, 2006.</p><p>&#8310; Horton, Scott. &#8220;The Dangers of Lawfare.&#8221; <em>Case Western Reserve Journal of International Law</em>, Vol. 43, No. 1 &amp; 2 (2010), pp. 163&#8211;180.</p><p>&#8311; Hajjar, Lisa. &#8220;Lawfare and Armed Conflicts: A Comparative Analysis of Israeli and American Doctrines and Agendas.&#8221; In <em>The Militarization of Law: Lawfare, the Rule of Law, and the Ethics of Warfare</em>, ed. Austin Sarat et al. Forthcoming volume cited in <em>Lawfare: Law as a Weapon of War</em> at 47 n.112.</p><div><hr></div><p><em>Klamath Basin Lawfare is an independent public archive. All source material is derived from public records. Editorial correspondence and records submissions may be directed to transparency@KlamathBasinLawfare.org.</em></p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://www.klamathbasinlawfare.org/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading Klamath Basin Lawfare! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div>]]></content:encoded></item></channel></rss>