Cycle on Aug 10, 2026

I will begin by listing the open threads and reading the existing notes for this topic to understand what has already been researched and what active questions or watches we need to track.

I will list the current set of notes to understand the existing findings and see what slugs are already defined.

I see several active watches and threads that are very close to or on their "fire dates" or have highly relevant ongoing developments. Let's check the following: 1. "Louisiana PSC Vote on Entergy's $1.4B Cottonwood Plant Purchase" (id: `019f368a-84de-7966-96da-e934c102b368`) - Scheduled for August 12, 2026. Today is August 10, 2026. Let's search for recent news on this. 2. "FERC Large-Load Interconnection Show-Cause Deadline" (id: `019fc6bf-24db-7a1d-92c1-d650b023b348`) - August 17, 2026. 3. "PUCO Decision on FirstEnergy's Proposed Ohio Data Center Tariff (Schedule DCT)" (id: `019fa2ae-d1b6-76c4-b262-a8243cc17d1d`). 4. "Oregon PUC Decision on Amazon and DCC Reconsideration of Schedule 96" (id: `019f5a96-90e2-7c84-b08d-97328f23d33d`) - Due September 4, 2026. 5. "Louisiana PSC Decision on Entergy's Seven New Gas Plants for Meta" (id: `019eee6e-7999-77fb-81a7-d30d411389c0`). Let's run a web search on Louisiana PSC, Entergy, Cottonwood, and Meta to see if there are updates. I'll also look into FirstEnergy's Schedule DCT and Oregon's Schedule 96. First, let's start with a general search for any recent developments regarding the Louisiana PSC, Entergy, Cottonwood, or Meta's Hyperion data center in Richland Parish.

This is a major and highly relevant update. Entergy Louisiana has indefinitely postponed its proceedings to buy the Texas Cottonwood power plant (which was a $1.8 billion plan, updated from $1.4 billion). The postponement occurred very recently (about 5-6 days ago, in early August 2026) amid growing backlash and reports that the acquisition was driven by Meta's Hyperion data center load rather than general system growth. Let's fetch some of these articles to get precise details and quotes. Specifically, the NOLA.com article `https://www.nola.com/news/entergy-pauses-cottonwood-proceedings-as-cost-data-center-questions-mount/article_3449e442-28d2-4e4a-b821-17b78a2ccf14.html` and `https://www.nola.com/news/louisiana-politics-data-center-debate-meta-hyperion/article_d0704924-6a96-4cb0-840d-322668de0860.html`. Let's also look at the RTO Insider article `https://www.rtoinsider.com/138696-nonprofits-denounce-louisiana-meta-buildout-warn-cost-spillover/` and `https://kpel965.com/entergy-meta-data-center-ratepayer-savings/`. Let's fetch the NOLA.com article on Entergy pausing Cottonwood.

Ah, the NOLA.com URL returned a redirect/login page. Let's try fetching another source, or search for other articles that discuss this. Let's try fetching the RTO Insider article `https://www.rtoinsider.com/138696-nonprofits-denounce-louisiana-meta-buildout-warn-cost-spillover/` and the KPEL965 article `https://kpel965.com/entergy-meta-data-center-ratepayer-savings/`. Let's also look at the `san.com` article `https://san.com/cc/louisiana-utilitys-plan-to-buy-texas-power-plant-derailed-over-ratepayer-cost/`. Let's search for more details.

It seems the RTO Insider article is quite short or paywalled, but let's see if we can search for the text or find another page that has more details on the Cottonwood pause and the Meta agreement. Let's try searching for `"Entergy" "Cottonwood" "postponed" OR "paused"` or `"Entergy" "Meta" "ratepayer savings" OR "Cottonwood"`. Let's run a search.

Let's fetch the Yahoo Finance article: `https://finance.yahoo.com/energy/articles/under-pressure-entergy-looks-mitigate-085357028.html`. It looks like it has been syndicated or published there. Let's also fetch the Entergy news release: `https://www.entergy.com/news/phillip-may-president-and-ceo-entergy-louisiana-supporting-strong-protections-for-customers-as-state-sets-clear-path-for-data-center-growth` to see what Entergy is proposing in its "Fair Share Plus" pledge. Let's start with these two fetches.

Let's fetch the Yahoo Finance article `https://finance.yahoo.com/energy/articles/under-pressure-entergy-looks-mitigate-085357028.html`. This will give us the details on the Cottonwood pause and why it's "increasingly in doubt" according to analysts like Julien Dumoulin-Smith.

The URL `https://www.finance.yahoo.com/energy/articles/under-pressure-entergy-looks-mitigate-085357028.html` is actually `https://finance.yahoo.com/energy/articles/under-pressure-entergy-looks-mitigate-085357028.html`. The fetch was successful. Wait, let's search for the actual postponement of the Cottonwood proceedings. The NOLA.com article "Entergy pauses Cottonwood proceedings as cost, data center questions mount" was published "5 days ago" (which would be around August 5, 2026). Let's do a search for `"Entergy" "Cottonwood" "indefinitely postponed"` or `"Entergy" "Cottonwood" "August"` to see if there are more recent articles that explain the postponement. Let's run a search.

Let's fetch the `san.com` article `https://san.com/cc/louisiana-utilitys-plan-to-buy-texas-power-plant-derailed-over-ratepayer-cost/` to see what details it provides. This will help us write a robust finding on the Cottonwood postponement and its impact on the Louisiana AI data center power boom.

This is an incredibly rich and detailed update on Louisiana. Let's analyze what we have: - **Louisiana AI Data Center Power Boom / Cottonwood Dispute**: - Entergy Louisiana has **indefinitely postponed** its proceedings at the Louisiana Public Service Commission (LPSC) to buy the 1.26-GW Cottonwood Energy Project in Texas for $1.8 billion (previously discussed as $1.4B, updated to $1.8B). - This decision was announced around August 4-5, 2026. - The pause comes after a June LPSC staff analysis/consultant report (by Lane Sisung) found the deal would raise the average monthly residential bill by $7 to $9 ($8 to $13 in some estimates, or $7 for 1,000 kWh/month) and that the "near-term capacity need [Entergy] relies upon to justify Cottonwood is not being driven by general system load growth. Rather, the need appears to be driven primarily by the timing and magnitude of the extraordinary Meta-Related Load Additions." - Gov. Jeff Landry intervened, tweeting/posting that the PSC should not allow anyone to take advantage of power markets at the expense of ratepayers. - Entergy is seeking to "identify ways to lessen the initial bill impacts of the proposed Cottonwood acquisition" and intends to try again on a "revised timeline" (revised terms/timeline). - The scale of the buildout for Meta's Hyperion data center in Richland Parish is massive: 7.5 GW of gas power (3 plants approved, 7 pending) explicitly for Meta, plus 4 GW of renewable energy, plus the 1.5 GW of non-Meta gas plants from February, and the 1.3 GW (1.26 GW) Cottonwood plant. Total proposed additions are over 14 GW. - Entergy claims its "Fair Share Plus" pledge will deliver in excess of $2.8 billion (or $2.65B–$2.7B) in customer savings over two decades, but consumer groups like the Alliance for Affordable Energy and Earthjustice argue that ratepayers are on the hook for hidden grid maintenance and stranded asset risks if Meta leaves. Let's look at the active watches for Louisiana: - "Louisiana PSC Vote on Entergy's $1.4B Cottonwood Plant Purchase" (id: `019f368a-84de-7966-96da-e934c102b368`). Since Entergy has indefinitely postponed the proceedings, this watch can be resolved/recorded. Let's record the event. The purchase is postponed indefinitely, which resolves the immediate vote (or rather, the vote is postponed/canceled for now). Let's record an event with `resolves: false` or `resolves: true` depending on whether we want to keep tracking it. Wait, the watch was "one_shot" for the vote on August 12, 2026. Since the proceedings are indefinitely postponed, there won't be a final vote on August 12, 2026. Let's record an event and resolve it, or keep it open if it might be revived. Let's call `record_event` with `resolves: true` because the scheduled August 12 vote is derailed by the postponement. Wait, let's look at the other Louisiana watch: "Louisiana PSC Decision on Entergy's Seven New Gas Plants for Meta" (id: `019eee6e-7999-77fb-81a7-d30d411389c0`). We should search for any updates on those seven new gas plants. Let's do a search on that.

This is highly relevant! Let's look at the AAE (Alliance for Affordable Energy) article: `https://www.all4energy.org/watchdog/meta-data-center-to-cause-entergy-bill-increase/`. The title says: "Meta Data Center to Cause Entergy Bill Increase. On August 20th, our 5 elected Louisiana Public Service Commissioners are expected to make a decision that will impact the cost of our electricity bills for decades." This is the vote on the seven new gas plants. The vote is scheduled for **August 20, 2026**. Let's fetch that page `https://www.all4energy.org/watchdog/meta-data-center-to-cause-entergy-bill-increase/` to get the exact details. Let's do a fetch.

Wait, looking at the article's date: it is "08.12.2025" but the content refers to "On August 20th... expected to make a decision". Oh, wait, the article says "08.12.2025" at the top, but let's check if there is a newer update about the seven gas plants in 2026. Ah! In March 2026, Entergy announced the *seven* new gas plants (in addition to the 3 approved in August 2025). The article from AAE in August 2025 was about the *three* gas plants which were approved in August 2025. Let's search for the current status of the seven gas plants in August 2026. Let's run a search for `"Entergy Louisiana" "seven" "gas plants" LPSC OR "Public Service Commission" August 2026`. This will help us find what's happening this month (August 2026).

Let's fetch the Fox 8 Live article `https://www.fox8live.com/2026/08/04/groups-question-entergys-plan-build-gas-plants-metas-ai-data-center-entergy-responds/` and the KPEL 965 article `https://kpel965.com/acadiana-energy-bill-meta-richland-parish/` to get the latest details about the seven new gas plants and the cost-allocation issues. These will give us excellent coverage of both the Cottonwood postponement and the seven-plant application. Let's do that.

Let's fetch the KPEL 965 article `https://kpel965.com/acadiana-energy-bill-meta-richland-parish/` to get additional details.

Excellent! This is incredibly clear. Let's synthesize: - For the **Cottonwood Texas Gas Plant ($1.8B, 1.26 GW)**: - Entergy Louisiana has **indefinitely postponed** its proceedings at the LPSC (which was originally scheduled for a vote/discussion on August 12, 2026). - This indefinite postponement was announced in early August 2026 (around August 4-5) to "identify ways to lessen the initial bill impacts of the proposed Cottonwood acquisition" and try again on a "revised timeline". - This directly resolves the watch: "Louisiana PSC Vote on Entergy's $1.4B Cottonwood Plant Purchase" (id: `019f368a-84de-7966-96da-e934c102b368`), as the proceedings are postponed and the vote is off the table for August 12. Let's record an event on this and resolve it. - For the **Seven New Gas Plants for Meta ($3B, 5,200 MW / 5.2 GW)**: - The LPSC adopted a fast-track schedule in April 2026 to review the application (Docket U-37425 or similar). - The LPSC is expected to take up the seven-plant application again in **December 2026** (not August 20th, as the August 20th date in the older AAE article was from 2025 regarding the first three plants, while the new seven-plant case will be reviewed in December 2026 according to the KPEL 965 article published recently). - Earthjustice, Alliance for Affordable Energy, and the Union of Concerned Scientists filed testimony on Friday, August 1, 2026, outlining the consequences of building the seven new gas plants and raising serious concerns over confidentiality of the agreements, fuel and operation cost spillover, and what happens after Meta's 15-to-20-year contract ends (since gas plants last 30+ years). - Entergy claims Meta's presence will generate $2.6 billion in savings for customers over 20 years, while watchdog groups argue ratepayers are on the hook for hidden costs and risk. - The watch "Louisiana PSC Decision on Entergy's Seven New Gas Plants for Meta" (id: `019eee6e-7999-77fb-81a7-d30d411389c0`) should be updated to reflect that the LPSC is expected to review/rule on this in **December 2026**. Let's do a search on the other active watches to see if there are updates: - "FERC Large-Load Interconnection Show-Cause Deadline" (id: `019fc6bf-24db-7a1d-92c1-d650b023b348`) - Deadline is August 17, 2026. Let's check if there are early filings or news. - "PUCO Decision on FirstEnergy's Proposed Ohio Data Center Tariff (Schedule DCT)" (id: `019fa2ae-d1b6-76c4-b262-a8243cc17d1d`). Let's search for "FirstEnergy" "Schedule DCT" OR "DCT" "Ohio" "PUCO" 2026. - "Oregon PUC Decision on Amazon and DCC Reconsideration of Schedule 96" (id: `019f5a96-90e2-7c84-b08d-97328f23d33d`) - Due September 4, 2026. Let's search for "Portland General Electric" "Schedule 96" "reconsideration" OR "Oregon" "UM 2377" 2026. Let's search for FirstEnergy's Schedule DCT in Ohio.

This is a huge find! Look at the PDF from FirstEnergy's Q2 2026 Strategic & Financial Highlights: "Data Center Tariff. Application filed 5/22/26 and deemed complete 7/1/26; PUCO Staff Report due by 11/30/26; PUCO Staff testimony due 2..." Wait, let's fetch this PDF or look at the text. FirstEnergy's application for the Data Center Tariff (Schedule DCT) was filed on May 22, 2026 (or June 12/15) and deemed complete on July 1, 2026. The PUCO Staff Report is due by **November 30, 2026**. This means the PUCO decision is not expected immediately, but rather the PUCO Staff Report is due by November 30, 2026, and staff testimony is due later. Let's search for more details on the FirstEnergy Schedule DCT filing and the timeline. Let's do a quick web search.

Let's fetch the energychoicematters.com article `http://www.energychoicematters.com/stories/20260807c.html` to see the latest opposition to FirstEnergy's proposed data center tariff. It was published very recently (August 7, 2026). Let's do a fetch.

This is an exceptional finding! Let's examine the details of the FirstEnergy Schedule DCT in Ohio: - **FirstEnergy's Proposed Schedule DCT (Case 26-697-EL-ATA)**: - Filed on **May 22, 2026** (with subsequent filings around June 12/15, 2026) by FirstEnergy's Ohio utilities: Ohio Edison, Cleveland Electric Illuminating Company, and Toledo Edison Company. - Deemed complete on **July 1, 2026**. - **Key Unique Feature**: Unlike AEP Ohio's tariff, FirstEnergy's proposed Schedule DCT would **require data center customers to take generation service from a competitive retail electric service (CRES) provider** (i.e. they must shop in the retail competitive market) rather than receiving standard service offer (SSO) default utility generation. - **Opposition**: Constellation Energy (CEG) filed formal opposition on **August 7, 2026**, objecting to this requirement. Constellation argues that Ohio law mandates the availability of standard service offer (SSO) default utility generation to all customers, and that if a retail supplier defaults, the utility must provide SSO generation. - **Support/Alternative**: Retail energy suppliers (RESA and IGS Energy) support the requirement. IGS Energy proposed a market-based Supplier of Last Resort (SOLR) monthly referral program for data center customers whose CRES provider defaults, rather than using the standard SSO. IGS also proposed that PUCO require FirstEnergy to commit to customer-level PJM Reliability Backstop Obligation (RBO) assignment for data center accounts to ensure PJM Reliability Backstop Procurement costs are properly allocated to the Load Serving Entities (LSEs) rather than socialized. - **Timeline**: PUCO Staff Report is due by **November 30, 2026**. This is a fantastic, highly detailed update that directly relates to: 1. The PUCO Decision on FirstEnergy's Proposed Ohio Data Center Tariff (Schedule DCT) watch (id: `019fa2ae-d1b6-76c4-b262-a8243cc17d1d`). 2. The broader theme of cost allocation and grid reliability backstops (PJM Reliability Backstop Procurement). Let's check if we can find any updates on Portland General Electric's Schedule 96 in Oregon: - Oregon PUC Decision on Amazon and DCC Reconsideration of Schedule 96 (id: `019f5a96-90e2-7c84-b08d-97328f23d33d`) - Due September 4, 2026. Let's search for "Portland General Electric" "Schedule 96" OR "UM 2377" Oregon "reconsideration" 2026.

Let's fetch the Oregon PUC docket page or RTO Insider story to see if there are more details. Let's do a search specifically for "UM 2377" "reconsideration" to see the status of the filings. The Oregon PUC docket page `https://apps.puc.state.or.us/edockets/DocketNoLayout.asp?DocketID=24470` has some interesting files. Let's search for recent documents in UM 2377.

Wait! Let's search for the RTO Insider article `https://www.rtoinsider.com/131475-pge-expects-decision-soon-data-center-rate-hile/` which was published recently to see what the rate hike and the Schedule 96 reconsideration is about. Let's run a search on this.

Ah, the search budget is spent. That is fine, we have a wealth of incredible and extremely detailed primary evidence that we fetched! Let's examine what we have and write up our findings. Let's do a market view check for some of the key companies mentioned to ground our findings in live public-markets data. Specifically: - Entergy (ETR) - We fetched their earnings details, but let's call `market_view` for ETR to get their exact multi-quarter revenue/earnings trajectory, valuation multiples, and recent price movement. - FirstEnergy (FE) - Portland General Electric (POR) - mentioned in the Oregon Schedule 96. - Constellation Energy (CEG) - mentioned in the Ohio PUCO comments and the prior notes. - Vistra (VST) Let's do a `market_view` call for `ETR`. This is our first step for market data.

That's excellent. Let's pull `market_view` for `FE` (FirstEnergy) and `POR` (Portland General Electric) to get their profiles and numbers. This will give us rich numbers to ground our findings.

Let's pull `market_view` for `POR` (Portland General Electric). This will complete our public-markets coverage.

Now we have all the pieces we need to write outstanding, highly detailed findings. Let's review the required note structure and rules: 1. One note per theme/subject. 2. Grounded in concrete evidence with verbatim quotes and links. 3. No YAML frontmatter. First heading is the title, then text, then a Sources section. 4. Stable slugs that represent durable subjects. - We will update `louisiana-ai-data-center-power-boom` to capture the massive updates on the Cottonwood postponement and the seven-plant Meta case. - We will update `firstenergy-data-center-contracts-wv-surcharge` (or create a new note/update an existing one) to capture FirstEnergy's Ohio Schedule DCT filing and Constellation's opposition. Wait, do we have an Ohio FirstEnergy slug? The existing note is `firstenergy-data-center-contracts-wv-surcharge`. Let's check its title: "FirstEnergy Data Center Contracts Surge 50% in Q2, Igniting West Virginia Ratepayer Backlash". Let's update `firstenergy-data-center-contracts-wv-surcharge` or create a new note for FirstEnergy's Ohio Data Center Tariff. Since FirstEnergy operates across both Ohio and West Virginia, updating/extending a FirstEnergy-specific load and tariff note makes complete sense. Wait, another option is to update `regulatory-backlash-data-center-ratepayer-protections` or `quantitative-evidence-data-center-ratepayer-subsidies`. But let's look at the FirstEnergy Ohio Schedule DCT. This is a very specific, durable subject: FirstEnergy's regulatory battles over its Data Center Tariff (Schedule DCT) in Ohio. Let's create/update a note with slug `firstenergy-ohio-data-center-tariff-schedule-dct` or reuse `firstenergy-data-center-contracts-wv-surcharge` and expand it to cover Ohio, or create a new stable slug `firstenergy-ohio-data-center-tariff-schedule-dct` for the Ohio tariff specifically since it's a major development in a different state. Let's create a new note for the Ohio tariff: `firstenergy-ohio-data-center-tariff-schedule-dct`. - Let's also check Portland General Electric's Schedule 96 in Oregon. We have `oregon-pwr-act-pge-schedule-96-tariff` as an existing note! We can update `oregon-pwr-act-pge-schedule-96-tariff` with any new details about the reconsideration or the rate hike. Wait, let's look at what we found about Schedule 96. PGE is seeking a data center rate hike of 26% to 29% (under UM 2377) to ensure "growth pays for growth" and protects residential customers (who would see a 2% rate decrease if adopted). This is a highly relevant quantitative detail to add to the existing note `oregon-pwr-act-pge-schedule-96-tariff`. Let's write the updated note for `louisiana-ai-data-center-power-boom` first. Let's structure it beautifully. Wait, let's make sure we have the exact details for `louisiana-ai-data-center-power-boom`. We have: - The indefinite postponement of the $1.8 billion Cottonwood purchase (originally $1.4B) as of early August 2026. - LPSC staff analysis showing a $7 to $9 monthly bill hike for residential customers ($8 to $13 in some estimates), stating that the near-term capacity need is driven by Meta's Hyperion data center rather than general system growth. - Gov. Jeff Landry's intervention on social media. - Entergy's plan to try again on a "revised timeline" with "revised terms". - The ongoing fast-tracked 7-plant gas application (5.2 GW, $3 billion) explicitly for Meta, with a vote expected in December 2026. - The opposition from Alliance for Affordable Energy, Earthjustice, and Union of Concerned Scientists citing lack of transparency, non-binding renewable commitments, and risk shifting. - Entergy's claim of $2.6B to $2.8B in savings over 20 years. - Entergy's financial figures: ETR market cap $50.01B, total debt $34.63B, negative Q2 FCF of -$935M (operating $1.89B, capex $2.83B), trading at $107.18. Let's write this note using `write_note`. Let's draft it.

Now, let's look at the FirstEnergy Ohio Data Center Tariff (Schedule DCT) case in Ohio. Let's create a new note with slug `firstenergy-ohio-data-center-tariff-schedule-dct`. Wait, let's verify if there is an existing note we can reuse. We have `firstenergy-data-center-contracts-wv-surcharge` which is about FirstEnergy's West Virginia ratepayer backlash. Since that note is focused on West Virginia, and the new Ohio tariff (Schedule DCT) is a distinct regulatory docket (PUCO Case 26-697-EL-ATA), creating a dedicated note for the Ohio tariff is highly appropriate. Let's make sure we refer to `[[firstenergy-data-center-contracts-wv-surcharge]]` via a wikilink to keep our notes interconnected. Let's draft `firstenergy-ohio-data-center-tariff-schedule-dct` beautifully. Let's make sure we include the details of Constellation's opposition on August 7, 2026, the retail competition requirement, the PUCO Staff report due by November 30, 2026, and FirstEnergy's financials. FirstEnergy (FE) has a market cap of $27.47 billion, total debt of $28.98 billion, and reported Q2 EPS of $0.50 (beating estimates). Let's write this note.

Now let's update the Oregon note `oregon-pwr-act-pge-schedule-96-tariff` to capture Portland General Electric's (POR) recent rate hike filings (UM 2377), which include a proposed 26% to 29% rate increase specifically for data centers to protect residential customers (who would see a 2% rate decrease if adopted). This is a highly relevant quantitative detail. Let's first review the existing content of `oregon-pwr-act-pge-schedule-96-tariff` to make sure we update it accurately. Wait, let's call `read_notes` to get the full body of `oregon-pwr-act-pge-schedule-96-tariff` if needed, but actually we can just overwrite/update it with a comprehensive, updated version that covers everything from its approval in July 2026 to the recent rate hike filings and reconsideration applications. Let's search for any details about the reconsideration of Schedule 96. The watch is "Oregon PUC Decision on Amazon and DCC Reconsideration of Schedule 96" (id: `019f5a96-90e2-7c84-b08d-97328f23d33d`). Wait, let's look at the Portland General Electric (POR) market view we pulled: - Market cap $5.77B, total debt $5.21B, Q2 EPS of $0.64 (in line with estimates) on $787M in revenue. - Q2 capex of $376 million, operating cash flow of $220M, resulting in a negative free cash flow of -$156 million. - Price is $49.05. Let's write the updated note for `oregon-pwr-act-pge-schedule-96-tariff`. Let's draft it.

This is fantastic! Let's check our active threads and watches. We can resolve/update several of them: 1. **Louisiana PSC Vote on Entergy's $1.4B Cottonwood Plant Purchase** (id: `019f368a-84de-7966-96da-e934c102b368`). - Outcome: Entergy has indefinitely postponed the proceedings to buy the Cottonwood plant. The scheduled vote is off the table. - We should call `record_event` to note that this watch has fired/resolved because the proceedings have been indefinitely postponed. - Let's call `record_event` with `resolves: true` to close this watch. - Then we will call `resolve_thread` for the thread/watch. Wait, `list_threads` returns watches as threads. We can resolve the thread `019f368a-84de-7966-96da-e934c102b368` using `resolve_thread`. Let's do that. Let's call `record_event` on the Cottonwood watch.

Let's resolve the thread for the Cottonwood watch.

This is great. Now let's check the other watches and see if we should update or record events for them. Wait, let's look at the remaining watches: - "PUCO Decision on FirstEnergy's Proposed Ohio Data Center Tariff (Schedule DCT)" (id: `019fa2ae-d1b6-76c4-b262-a8243cc17d1d`). - We found that the PUCO Staff Report is due on **November 30, 2026**. - Let's check if we can record an event or update this watch. Wait, we can't update a watch directly, but we can register a new watch or keep it open. Since it's still open, we can keep it open. - "Oregon PUC Decision on Amazon and DCC Reconsideration of Schedule 96" (id: `019f5a96-90e2-7c84-b08d-97328f23d33d`). - This is due on **September 4, 2026**. It is still upcoming. - "Louisiana PSC Decision on Entergy's Seven New Gas Plants for Meta" (id: `019eee6e-7999-77fb-81a7-d30d411389c0`). - We found that the LPSC is expected to review/rule on this in **December 2026**. - Let's record an event on this watch to update its timeline, or let's create a new watch if we want to change its fire_date. Actually, we can record an event with `resolves: false` to update the status. Let's do that. Let's call `record_event` with `resolves: false` to note that the timeline has been pushed to December 2026. Let's do that.

Wait, let's look at the "FERC Large-Load Interconnection Show-Cause Deadline" (id: `019fc6bf-24db-7a1d-92c1-d650b023b348`). The deadline is August 17, 2026. This is next week! We should keep a close eye on this in the next cycle. Let's register a new watch or update existing ones if we want. Wait, the existing watches are already tracked. Is there any new forward-looking catalyst we surfaced? Yes, we found that: 1. FirstEnergy's PUCO Staff Report for Schedule DCT is due by **November 30, 2026**. Let's register a new `one_shot` watch for this. Let's do that. This is a very clean way to track it.

This is perfect. We have successfully: 1. Updated the Louisiana note `louisiana-ai-data-center-power-boom` with the massive Cottonwood postponement, the 14-GW total buildout, and Entergy's financial profile. 2. Created a new note `firstenergy-ohio-data-center-tariff-schedule-dct` detailing FirstEnergy's proposed Ohio Data Center Tariff (Schedule DCT) under Case No. 26-697-EL-ATA, Constellation's August 7, 2026 opposition, and FirstEnergy's financial profile. 3. Updated the Oregon note `oregon-pwr-act-pge-schedule-96-tariff` to include details on the proposed 26%-29% data center rate hike, the 2% residential rate relief, the pending September 4, 2026 reconsideration deadline, and PGE's Q2 2026 financial metrics. 4. Resolved the watch on the Cottonwood plant purchase vote as it has been indefinitely postponed. 5. Recorded an event on the seven-plant Meta case showing that the LPSC review is pushed to December 2026. 6. Registered a new watch for the FirstEnergy PUCO Staff Report due on November 30, 2026. All actions are fully grounded in the primary sources we fetched this cycle and the public-markets data we pulled. I am now ready to call `finish_cycle` and conclude this research cycle.

I have successfully completed this research cycle. Here is a summary of the key findings and updates: ### 1. **Louisiana AI Data Center Power Boom: Cottonwood Purchase Indefinitely Postponed** * **What Happened:** In early August 2026, **Entergy Louisiana (NYSE: ETR)** indefinitely postponed its LPSC proceedings to acquire the 1.26-GW gas-fired **Cottonwood Energy Project** in Texas for **$1.8 billion** (previously priced at $1.4 billion). * **Why It Happened:** The postponement follows intense ratepayer backlash and an LPSC consultant report showing that the near-term capacity need was driven primarily by **Meta's $50 billion Hyperion AI data center** rather than general system growth. Because Entergy framed the plant as system-wide, it was not covered by Meta's payment guarantees and would have raised residential bills by **$7 to $9 per month** ($8 to $13 in summer months). * **Broader Impact:** While Cottonwood is on ice, Entergy's broader fast-tracked **seven-plant gas application ($3 billion, 5.2 GW)** explicitly for Meta remains on the docket, with an LPSC review scheduled for **December 2026**. Watchdog groups (Alliance for Affordable Energy, Earthjustice, and UCS) filed testimony on August 1, 2026, warning of severe cost spillovers and long-term stranded asset risks once Meta's 15-to-20-year contract ends. * **Stable Slug Updated:** `louisiana-ai-data-center-power-boom` ### 2. **FirstEnergy’s Novel Ohio Data Center Tariff (Schedule DCT) Faces Opposition** * **What Happened:** On June 12, 2026, **FirstEnergy’s (NYSE: FE)** Ohio utilities filed a proposed **Data Center Tariff (Schedule DCT)** under Case No. 26-697-EL-ATA. * **Key Provisions:** Unlike AEP Ohio's tariff, FirstEnergy's tariff would **require all data centers to take generation service from a competitive retail supplier (CRES)** rather than the utility's Standard Service Offer (SSO), shifting procurement risk entirely to the competitive market. It features a 10-year term, minimum billing at 85% of contract capacity, and strict collateral requirements. * **The Conflict:** On **August 7, 2026**, **Constellation Energy (NYSE: CEG)** filed formal opposition with the PUCO, arguing that Ohio law mandates SSO availability to all customers and that the tariff fails to provide standard default service if a retail supplier defaults. Conversely, retail suppliers (RESA, IGS Energy) strongly support the mandate. The PUCO Staff Report is due by **November 30, 2026**. * **Stable Slug Created:** `firstenergy-ohio-data-center-tariff-schedule-dct` ### 3. **Oregon's PGE Proposes Aggressive 26%–29% Data Center Rate Hike** * **What Happened:** Following the July 2026 approval of its compliance filing under Docket UM 2377, **Portland General Electric (NYSE: POR)** has proposed a **26% to 29% rate premium** specifically for data centers under **Schedule 96**. * **The Mechanics:** The tariff utilizes a **Peak Growth Modifier (PGM)** to assign fixed generation and transmission costs directly to data centers based on their peak demand contribution. If fully adopted, this structure will shield residential ratepayers, who would see an approximate **2% rate decrease**. * **Hyperscaler Backlash:** Amazon Data Services, the Data Center Coalition (DCC), Verrus, and AWEC have filed formal applications for reconsideration, with an OPUC ruling due by **September 4, 2026**. * **Stable Slug Updated:** `oregon-pwr-act-pge-schedule-96-tariff` --- ### **Resolved & Registered Watches** * **Resolved:** `019f368a-84de-7966-96da-e934c102b368` (Louisiana PSC Vote on Entergy's Cottonwood Purchase) has been resolved as **Postponed Indefinitely**. * **Registered:** A new watch (`019feacb-b904-7a31-8234-1a5610975394`) has been registered to track the **PUCO Staff Report on FirstEnergy's Schedule DCT** due on **November 30, 2026**.