no-fabricationThe summary's source_url is the committee's 'SEQR Research Findings' PDF (2026-11-01_seqr_research_findings.pdf). But the summary also states that 'A third-party tracker (Cleanview) separately lists the Lysander project at 300 MW on 120 acres.' Nothing in the entry indicates that the SEQR document cites Cleanview or gives the 300 MW or 120-acre figures. The summary itself frames the tracker as a separate source ('separately lists', 'the two figures are not reconciled'), so the named party (Cleanview) and both figures do not trace to source_url. Fix: drop the Cleanview sentence from this entry and keep it in its own entry with the Cleanview tracker URL as source_url, labeled as third-party reporting. While editing, also say that the SEQR document does not specify which load measure its MW figures represent (the 20, 75, 500, 750 and 270 MW figures), matching the caveat already in entry 3. Context: the 2026-11-05 finding about the wind-direction claim is resolved. That statement now sits in reported entry 35 with an attribution caveat, and estimated entry 37 no longer contains it. New entries 0, 1, 2, 3 and 5 were checked against every lens rule and raise no findings.

evidence-label-accuracyEntry is labeled 'estimated'. That fits the committee's generator heat arithmetic ('150% more fuel energy', 'a total site heat increase of 250%') and its estimates of a half-mile thermal plume and a 3 to 6 degree rise. But the summary also states, under the same label, that the deck says 'the prevailing wind blows east and northeast, with the wind blowing north or northwest roughly 20 percent of the time.' That is an uncited meteorological claim that the deck presents as observed fact. It is not a labeled calculation or scenario, and no figure in the entry is derived from it, so it is committee characterization that belongs under 'reported'. This is the same finding raised in the 2026-11-03 and 2026-11-04 verdicts (it was entry 30 there). Today's draft only inserts two new entries at indexes 0 and 1. Every other summary, including this one, is word-for-word unchanged, so the issue is still unresolved. Fix: move the wind-direction statement into a separate 'reported' entry (or into entry 30, the October 9 deck's reported-claims entry) or drop it, and keep entry 32 limited to the committee's calculations and estimates. The new entries 0 (November 5 Town Board agenda) and 1 (Post-Standard legal notice proof) were checked against all lens rules and raise no findings.

Source · 2026-10-09 ↗

estimated Critic flagged 2026-11-04

town-of-lysander-official-records

The October 9 deck includes the committee's own heat arithmetic for natural gas backup generators. It states the generators are about 40 percent efficient, so 60 percent of fuel energy becomes waste heat and they must consume '150% more fuel energy than the electricity they output', which it says yields '150% more heat from the generators alone' and, added to the data center's own heat, 'a total site heat increase of 250% over normal operating conditions.' The arithmetic is ambiguous: under the deck's own premises, generator waste heat of 1.5 times electrical output added to the data center's normal heat would make total heat about 2.5 times normal, which is a 150 percent increase, not a 250 percent increase. The deck also estimates thermal plumes of about half a mile downwind at full generator output and a localized temperature rise averaging 3 to 6 degrees (unit unstated on that slide; a later slide uses Fahrenheit) in that corridor, and states that the prevailing wind blows east and northeast, with the wind blowing north or northwest roughly 20 percent of the time. No source or model is cited for the plume, temperature or wind figures.

Proposed edit

If the heat figures are used, present them as the committee's own uncited estimates, flag that '250% increase' is inconsistent with the deck's own premises (which give roughly 2.5 times normal heat, a 150 percent increase), and do not present the plume distance or temperature rise as modeled results.

Critic findings against this item (1)

evidence-label-accuracyEntry is labeled 'estimated'. That fits the committee's generator heat arithmetic ('150% more fuel energy', 'total site heat increase of 250%') and its estimates of a half-mile thermal plume and a 3 to 6 degree rise. But the summary also states, under the same label, that the deck says 'the prevailing wind blows east and northeast, with the wind blowing north or northwest roughly 20 percent of the time.' That is an uncited meteorological claim the deck presents as observed fact. It is not a labeled calculation or scenario, and no figure in the entry is derived from it. Under the lens it is committee characterization and belongs in a 'reported' entry, the same way entries 28, 33, 44 and 48 split deck claims from deck calculations. This finding was raised in the 2026-11-03 verdict; the 2026-11-04 draft's changes array is identical to the 2026-11-03 draft, so it is still unresolved. Fix: move the wind-direction statement into a separate 'reported' entry (or into entry 28) or drop it, and keep entry 30 limited to the committee's calculations and estimates.

Source · 2026-10-09 ↗

estimated Critic flagged 2026-11-03

town-of-lysander-official-records

The October 9 deck includes the committee's own heat arithmetic for natural gas backup generators. It states the generators are about 40 percent efficient, so 60 percent of fuel energy becomes waste heat and they must consume '150% more fuel energy than the electricity they output', which it says yields '150% more heat from the generators alone' and, added to the data center's own heat, 'a total site heat increase of 250% over normal operating conditions.' The arithmetic is ambiguous: under the deck's own premises, generator waste heat of 1.5 times electrical output added to the data center's normal heat would make total heat about 2.5 times normal, which is a 150 percent increase, not a 250 percent increase. The deck also estimates thermal plumes of about half a mile downwind at full generator output and a localized temperature rise averaging 3 to 6 degrees (unit unstated on that slide; a later slide uses Fahrenheit) in that corridor, and states that the prevailing wind blows east and northeast, with the wind blowing north or northwest roughly 20 percent of the time. No source or model is cited for the plume, temperature or wind figures.

Proposed edit

If the heat figures are used, present them as the committee's own uncited estimates, flag that '250% increase' is inconsistent with the deck's own premises (which give roughly 2.5 times normal heat, a 150 percent increase), and do not present the plume distance or temperature rise as modeled results.

Critic findings against this item (1)

evidence-label-accuracyEntry is labeled 'estimated', which fits the committee's heat arithmetic and its plume and temperature-rise estimates. But the summary also carries a non-calculated factual claim under that label: the deck 'states that the prevailing wind blows east and northeast, with the wind blowing north or northwest roughly 20 percent of the time.' That is an uncited meteorological claim that the deck presents as fact. It is not a labeled calculation or scenario, and no figure in the entry is derived from it. Under the lens it belongs in a 'reported' entry, as committee characterization, the way entries 28, 33, 44 and 48 split deck claims away from the deck's calculations. As written, the 'estimated' label covers a statement that reads as observed fact. Split the wind-direction statement into a separate 'reported' entry, or drop it.

The Department of Public Service Large Load and Data Center Interconnection Technical Working Group (Load-ITWG) page lists, under 'Upcoming Load-ITWG Meeting', a working-group meeting on October 30, 2026, 2:00 to 3:00 PM ET via WebEx. On October 23 the same page still shows '0 results found' under past Load-ITWG meetings and posts no agenda or materials for the October 30 session. The page lists Executive Order 62 as related material. It does not state the meeting's Case 26-E-0045 docket association.

Proposed edit

Add the scheduled October 30, 2026 Load-ITWG meeting to the state interconnection timeline as an upcoming event, without describing its agenda until materials are posted.

Critic findings against this item (1)

evidence-label-accuracyThe proposed_change says to add the October 30, 2026 Load-ITWG meeting 'as an upcoming event'. This draft is dated October 31, 2026, so that date has already passed. The verified DPS page supports only that a meeting was scheduled for October 30 ('Upcoming Load-ITWG Meeting' as the page showed it when checked). It does not support calling the meeting upcoming now, and it does not show the meeting was held. The summary also mixes check dates: the source_date is October 30, but the summary reports what the page showed 'On October 23'. Fix: describe it as 'scheduled for October 30, 2026 (not confirmed held; no agenda, materials or notes located)', give the date the page was last checked, and update the entry once DPS lists the session under past meetings.

no-fabricationThe summary says 'the town homepage notice dated October 29, 2026 also places the 10-30-26 meeting in the library's Story Room'. That notice and its October 29 date do not come from source_url (dcac_agenda10-30-26.pdf), and no URL is given for the homepage notice. The rule names a general agency homepage as a source that cannot carry a specific fact. Either cite the specific notice URL or drop the corroboration and its date.

Source · 2026-10-29 ↗

verified Critic flagged 2026-10-30

town-of-lysander-official-records

The 23-page deck for the committee's October 30, 2026 meeting (PDF metadata creation date October 29, 2026; title slide dated October 30th, 2026) goes beyond the decommissioning goals already listed in the October 16 deck and sets out proposed decommissioning mechanisms the town could require: - infrastructure upgrade costs paid or bonded up front; - defined decommissioning work (environmental cleanup, bringing the site to current industrial code, possible demolition and restoration to a graded greenfield); - specific triggers, with examples of power use falling below 15 percent of planned usage or the site not operating for its approved use for an unspecified number of months; - a mandatory decommissioning trust fund backed by an irrevocable letter of credit or cash escrow, re-evaluated every three to five years by an independent engineer at the developer's expense, with top-up within 30 days; - environmental impairment liability insurance naming the town as additional insured; - utility easements and substations structured so they can be dedicated back to National Grid; - a funded site security and maintenance plan, and a workforce dislocation escrow or retraining contribution to the county workforce development board; - if a heating district is created, separate utility connections and escrowed reserves to keep heat service running. The deck states that the town routinely requires decommissioning plans and bonds for industrial and commercial projects. These are committee proposals for discussion, not adopted town code, and no minutes show they were presented.

Proposed edit

Record the committee's proposed decommissioning requirements (up-front bonding, usage-based triggers, a re-evaluated trust fund, EIL insurance, utility-infrastructure dedication, security and workforce escrows, heating-district protections) as proposed local controls under discussion, distinguished from enacted code.

Critic findings against this item (1)

evidence-label-accuracyThis entry is labeled 'verified' but includes 'The deck states that the town routinely requires decommissioning plans and bonds for industrial and commercial projects.' That is a claim about town practice, and no Planning Board record or town code backs it. Entry 28 files the same statement from the October 9 deck as 'reported' because 'they have not been checked against Planning Board records', so this draft treats one claim two different ways. Move the sentence to a reported entry, or state in this entry that the practice claim is the committee's and is unverified.

Source · 2026-10-30 ↗

reported No objection filed 2026-10-30

town-of-lysander-official-records

The same October 30, 2026 deck opens an 'Other Pollution' series. It lists concerns from the committee's spreadsheet with numeric scores whose scale the deck does not define: generator air pollution 3.1, other air pollution 2.4, spent fuel rods storage/transport 2.2, e-waste 2.1 and diesel storage for generators 1.9. It states that NYSDEC has primary responsibility for air emissions, e-waste and diesel fuel storage, that the U.S. Nuclear Regulatory Commission regulates nuclear fuel transportation, storage and disposal, and again that the planning board typically requires full SEQRA review for a project of this size. It lists pollutants from diesel and natural gas generators and proposes mitigation: for diesel, a particulate filter (stated 90-95 percent PM reduction), selective catalytic reduction with exhaust gas recirculation (80-95 percent NOx) and an oxidation catalyst (60-90 percent CO), assuming Tier 4 equipment; for lean-burn natural gas, SCR (75-95 percent NOx) and an oxidation catalyst (stated reductions for formaldehyde, CO and methane). The percentages, the jurisdiction statements and the methane comparison are the committee's own, with no cited source, and no nuclear power source has been proposed in any primary record located for the Lysander site.

Proposed edit

Note that the committee has begun an air and other pollution discussion favoring emission controls on backup generators, attributing the efficiency figures and agency-responsibility statements to the committee deck rather than stating them as fact.

Held only because another item in the 2026-10-30 batch was flagged. Nothing was filed against this one.

Source · 2026-10-30 ↗

verified No objection filed 2026-10-30

lysander-town-board-minutes

Unapproved minutes of the Lysander Town Board meeting of October 15, 2026 (PDF created October 28, 2026) list Supervisor Rode and Councilors Mangan, Schmitt and Kudarauskas as present and no members absent. The meeting's resolutions (246/2026 through 256/2026) cover a fire-protection agreement, the 2027 budget public hearing, a sewer-district final order, speed studies, tax levies and a dog-control contract; none concerns data centers, and adoption of the October 1 minutes was tabled. Under Town Board comments, the minutes record that Councilor Schmitt noted the Data Center Advisory Committee had discussed environmental issues and that its next meeting would be at the library because early voting would be held in Town Hall, and that Supervisor Rode 'once again noted that the Town Board is in agreement with passing the moratorium on Data Centers' and asked that comments at the public hearing focus on the moratorium. The minutes do not restate the hearing date; the November 5, 2026 date comes from the October 1 minutes. The statement is a recorded comment, not a vote, and the minutes are unapproved.

Proposed edit

Add to the Lysander moratorium timeline that at the October 15, 2026 Town Board meeting the Supervisor stated, per unapproved minutes, that the Town Board 'is in agreement with passing the moratorium on Data Centers', recorded as a comment with no vote taken; the November 5, 2026 hearing date and the extension framing are cited to the October 1, 2026 minutes, not to this record.

Held only because another item in the 2026-10-30 batch was flagged. Nothing was filed against this one.

Source · 2026-10-15 ↗

verified Critic flagged 2026-10-30

psc-case-26-e-0045-large-load-interconnection

A Department of Public Service press release dated September 17, 2026 (release 26085, Case 26-E-0045) states that the Public Service Commission issued a SEQRA positive declaration for its review of data center and other large-load interconnections under the Energize NY Development proceeding, together with a Draft Scope for a Generic Environmental Impact Statement, with public comments on the Draft Scope due October 20, 2026. The release states that Executive Order 62 (July 14, 2026) directed DPS to undertake the GEIS and directed agencies to pause data center permits until the review is complete. It lists impacts the Draft Scope will evaluate, including air, water, groundwater, human health, disadvantaged communities, agricultural resources, aesthetic resources, plants and animals, noise, odor and light, open space, and community character. After the comment period the Commission may revise the Draft Scope and accept a Final Scope. No Final Scope or draft GEIS had been located as of October 25, 2026.

Proposed edit

Add to the Case 26-E-0045 / EO 62 timeline that the PSC issued a positive declaration and Draft Scope for the statewide data center GEIS on September 17, 2026, with comments closed October 20, 2026 and a Final Scope still pending.

Critic findings against this item (1)

evidence-label-accuracyThe summary correctly says comments on the Draft Scope were 'due October 20, 2026', citing the September 17 release. The proposed_change turns this into 'comments closed October 20, 2026'. A release issued in September can't show that the comment period actually closed on that date and wasn't extended, so a verified label doesn't support that wording. Use 'comments were due October 20, 2026' unless a later DPS record confirms the closing.

Source · 2026-10-09 ↗

verified Critic flagged 2026-10-29

lysander-town-board-minutes

Unapproved minutes of the Lysander Town Board meeting of October 15, 2026 (PDF created October 28, 2026) list Supervisor Rode and Councilors Mangan, Schmitt and Kudarauskas as present and no members absent. The meeting's resolutions (246/2026 through 256/2026) cover a fire-protection agreement, the 2027 budget public hearing, a sewer-district final order, speed studies, tax levies and a dog-control contract; none concerns data centers, and adoption of the October 1 minutes was tabled. Under Town Board comments, the minutes record that Councilor Schmitt noted the Data Center Advisory Committee had discussed environmental issues and that its next meeting would be at the library because early voting would be held in Town Hall, and that Supervisor Rode 'once again noted that the Town Board is in agreement with passing the moratorium on Data Centers' and asked that comments at the public hearing focus on the moratorium. The minutes do not restate the hearing date; the November 5, 2026 date comes from the October 1 minutes. The statement is a recorded comment, not a vote, and the minutes are unapproved.

Proposed edit

Add to the Lysander moratorium timeline that at the October 15, 2026 Town Board meeting the Supervisor stated, per unapproved minutes, that the Board agrees on passing the data center moratorium extension, with no vote taken ahead of the scheduled November 5, 2026 hearing.

Critic findings against this item (1)

no-fabricationsource_url is the October 15, 2026 unapproved minutes, which per the summary quote Supervisor Rode only as saying the Board 'is in agreement with passing the moratorium on Data Centers' and 'do not restate the hearing date'. Two facts in this entry do not come from that document. First, the summary carries the 'November 5, 2026' hearing date and openly takes it from the October 1 minutes, a different source_url (entry 16). Second, the proposed_change says the Board 'agrees on passing the data center moratorium extension'. The word 'extension' is not in the quoted October 15 text; it is drawn from the October 1 record. The reading is plausible, but an entry labeled verified against the October 15 minutes should not put another document's date and framing into its proposed text. Fix: quote the October 15 wording as written ('passing the moratorium on Data Centers'), and cite the November 5 hearing and the extension framing to the October 1 minutes (entry 16) instead of this source_url.

Source · 2026-08-05 ↗

reported Critic flagged 2026-10-29

terawulf-q1-2026-investor-presentation

TeraWulf's second-quarter 2026 investor presentation, furnished as Exhibit 99.2 to the same August 5, 2026 Form 8-K, lists 'Lake Hawkeye, Lansing, NY' with '~320 MW' of total critical IT delivery shown against 2029. In its capacity chart Lake Hawkeye's 320 MW appears as a separate bar from the 839 MW of contracted critical IT capacity, under a 'Leased Capacity + Pipeline' heading. The deck's funding appendix lists Lake Hawkeye (NY / NYISO), but the table did not extract cleanly enough to attribute a specific funding status to it, so none is stated here. These are company statements, not permits, approvals or contracts.

Proposed edit

Note that TeraWulf's Q2 2026 investor presentation shows Lake Hawkeye's ~320 MW separately from its contracted capacity with delivery shown against 2029, labeled as company-reported.

Critic findings against this item (1)

distinguish-capacity-typesThe summary keeps the load measures straight: Lake Hawkeye's '~320 MW of total critical IT delivery' against '839 MW of contracted critical IT capacity'. The proposed_change drops both qualifiers, saying the presentation 'shows Lake Hawkeye's ~320 MW separately from its contracted capacity'. Entry 50 gives the same site as 'approximately 400 MW of gross capacity, or approximately 320 MW of critical IT load', so a bare '~320 MW' in site text can be read as a gross or service figure. It could then be set beside Lysander's '270 MW' (load measure unstated), the measure-type mixing this rule prohibits. Fix: say '~320 MW of critical IT' and 'contracted critical IT capacity' in the proposed_change.

distinguish-capacity-typesThe summary repeats Turner's 'a 4.9 million sq. ft./600 MW data center' (March 2024 Loudoun denial) without saying which load measure 600 MW is (requested interconnection, service capacity, critical IT load or operating load). Every sibling entry that carries a facility MW figure adds that qualifier: entry 18 ('270-300 MW ... without saying which load measure'), entry 41 and entry 45 ('load measure unstated'), and entry 12 (GW 'measure unstated'). Here the bare 600 MW reads as a single defined facility size and could later be set beside the Lysander 270 MW or TeraWulf's 400 MW gross / 320 MW critical IT figures as if they measured the same thing. The proposed_change does not cover this figure either. Fix: add that the white paper does not state which measure 600 MW represents, and have proposed_change say that if the 600 MW figure is cited, it is attributed to Turner with the measure unstated.

Source · 2026-10-22 ↗

verified Critic flagged 2026-10-27

town-of-lysander-official-records

The town posted july_1_data_center_briefing_202607131252299943_0.pdf in its 2026-10 upload folder: a 23-page presentation titled 'Data Center Growth: Our Changing Paradigm' by Vice Chair and Ashburn Supervisor Mike Turner, dated July 1, 2026, headed 'Resource Page, Ashburn, Loudoun County, VA' (PDF metadata creation date July 13, 2026). It states that its opinions and recommendations are the author's alone, do not represent any other Board member, the Loudoun County Board of Supervisors or county staff, and have no legal authority. It matches the October 23 agenda item 'Loudoun County PP / Mike Turner Presentation'. This entry verifies only the posting and the document's stated authorship.

Proposed edit

If the site lists the committee's reference material, note the Turner July 1, 2026 presentation as one Loudoun supervisor's personal opinion by its own disclaimer, not county policy and not Lysander findings.

Critic findings against this item (1)

evidence-label-accuracyLabeled 'verified', but the summary says the presentation 'matches the October 23 agenda item 'Loudoun County PP / Mike Turner Presentation''. Entry 3 of this same draft classes the session date as 'unknown' because the agenda's printed header reads 'Friday, October 16th, 2026', and it says October 23 is 'an inference only' from the file name and metadata. Calling it 'the October 23 agenda' in a verified entry states the inferred date as fact. Refer to the agenda by file name (dcac_agenda_10-23-26.pdf) or as the Baldwinsville Public Library work-session agenda.

Source · 2026-07-01 ↗

verified Critic flagged 2026-10-27

town-of-lysander-official-records

The town posted data_center_fact_sheet_2026_202609021623071592.pdf in its 2026-10 upload folder: a 2-page Loudoun County, Virginia 'Data Center Fact Sheet' branded loudoun.gov/DataCenters (PDF metadata creation date September 2, 2026). It contains a 'By the Numbers' panel labeled 'As of March 1, 2026', a data center timeline from the 1990s to 2026, and a list of ten 'top considerations' (siting, energy, electrical infrastructure, water, noise, land values, design standards, secure facilities, fire response, tax revenue). It matches the October 23 agenda item 'Loudoun County Fact Sheet'. This entry verifies only the posting and the document's origin.

Proposed edit

If the site lists the committee's reference material, note the posted Loudoun County fact sheet as Loudoun government material, not Lysander findings.

Critic findings against this item (1)

evidence-label-accuracyLabeled 'verified', but the summary says the fact sheet 'matches the October 23 agenda item 'Loudoun County Fact Sheet''. Entry 3 says no primary record establishes that the session was on October 23, so a verified entry should not date the agenda that way. Cite it by file name instead.

Source · 2026-09-02 ↗

verified Critic flagged 2026-10-27

town-of-lysander-official-records

The town posted data_center_-_residents_3_202609021954218107.pdf in its 2026-10 upload folder: a 1-page Loudoun County sheet titled 'Data Centers in Loudoun County - Stay Informed. Get Involved. Information for Residents' (PDF metadata creation date September 2, 2026). It covers how the county says it is addressing data center concerns, noise complaints, transmission lines and tax rates, and directs readers to loudoun.gov pages. It matches the October 23 agenda item 'LC Citizens Residents Info Sheet'. This entry verifies only the posting and the document's origin.

Proposed edit

If the site lists the committee's reference material, note the posted Loudoun residents information sheet as Loudoun government material, not Lysander findings.

Critic findings against this item (1)

evidence-label-accuracyLabeled 'verified', but the summary says the residents sheet 'matches the October 23 agenda item 'LC Citizens Residents Info Sheet''. Entry 3 treats that date as unestablished: the printed header reads 'Friday, October 16th, 2026' and October 23 is inferred from the file name. Cite the agenda by file name instead.

no-fabricationThe proposed_change ties the lithium iron phosphate and linear-generator figures 'to the 270 MW hypothetical'. The summary only says the deck refers to 'what it calls a 270 MW data center' and does not show that the deck calls it hypothetical. Entry 18 of this same draft reports that the October 16 deck 'describes the project as a '270–300 MW data center'', so the deck may mean the actual proposed project. The word 'hypothetical' does not trace to source_url. Either quote the deck's own framing or call it the deck's '270 MW data center', with the load measure unstated.

Source · 2026-09-25 ↗

verified No objection filed 2026-10-27

town-of-lysander-official-records

The Lysander Data Center Advisory Committee agenda for Friday, September 18, 2026 at 9:00 AM at 8220 Loop Road schedules a work session. Under old business the agenda lists proposed noise ordinance wording from outside consultants, described as awaiting changes; a data center concerns list progress update; and the Battery Energy Storage System ordinance. Under new business it lists a continuation of the electricity discussion and a new topic, generators and turbines. The agenda states the next meeting will continue the electricity discussion. No applicant, named project, or Community Benefit Agreement action appears on this agenda. The agenda shows the session was scheduled; minutes confirming it took place were not located in the reviewed record.

Proposed edit

Add the September 18, 2026 Data Center Advisory Committee work session to the local-process timeline as scheduled, noting that the consultant-drafted noise ordinance language is awaiting changes and that generators and turbines entered the committee's agenda as a new business item.

Held only because another item in the 2026-10-27 batch was flagged. Nothing was filed against this one.

Source · 2026-09-18 ↗

verified No objection filed 2026-10-27

town-of-lysander-official-records

The presentation deck accompanying the September 18, 2026 meeting sets out the committee's recommendations on on-site backup generation: - allow only natural gas or bi-fuel generators for emergency backup power; - trigger an immediate shutdown if bi-fuel units fall below 70 percent natural gas use during a test; - allow generators only for backup power during an outage, with no behind-the-meter use of generators or turbines; - require a full environmental impact study addressing noise and environmental issues before any approval; - require scheduled inspections by a certified third party; - confine testing to specified weekday daytime hours, with caps on units tested at once and on annual testing hours; - require a separate decommissioning bond for generator farms; - define generator farms as a special use requiring separate review and permit. The deck was prepared for the scheduled September 18 work session. No minutes were located showing it was presented, and the recommendations are not adopted town code. The deck's rationale and its statement of the division of authority are filed separately as reported.

Proposed edit

Record the committee's on-site generation recommendations - natural gas or bi-fuel only, backup-only with no behind-the-meter generation, special-use permitting, decommissioning bond and testing-hour limits - as proposed local controls under development, clearly distinguished from enacted code. The deck's division-of-authority statements are filed separately as reported and are not part of this change.

Held only because another item in the 2026-10-27 batch was flagged. Nothing was filed against this one.

Source · 2026-09-18 ↗

reported No objection filed 2026-10-27

town-of-lysander-official-records

The September 18 deck gives its own rationale and its own account of who controls what. It says natural gas and bi-fuel generators are the two quietest options, eliminate or greatly reduce on-site diesel storage, emit far less greenhouse gas, carbon and soot than diesel, and avoid the high-pitched whine of turbines. On authority, it says: - the town has no say in power delivery or rates; - NYISO operates the high-voltage grid and sets supply charges, while the PSC sets delivery charges and service classifications; - DEC regulates generator emissions, fuel types and fuel storage; - the town can regulate generator size, operating hours outside emergencies, setbacks and noise through code; - the town can designate on-site or behind-the-meter generation above a threshold (the deck suggests 5 MW) as a separate or prohibited land use. These are the committee's characterizations. They have not been checked against statute, PSC tariffs or DEC rules.

Proposed edit

If used at all, attribute the September 18 deck's generator rationale and its division-of-authority statements to the committee. Do not present them as confirmed.

Held only because another item in the 2026-10-27 batch was flagged. Nothing was filed against this one.

Source · 2026-09-18 ↗

estimated Critic flagged 2026-10-27

town-of-lysander-official-records

The September 18 deck works through backup-generation sizing for what it calls a '270 MW Data Center'; the deck does not say whether 270 MW is requested interconnection capacity, service capacity, or critical IT load. Its table, whose unit counts are labeled as calculated, gives with redundancy roughly 78 to 93 diesel units at 3.25 to 4 MW each, 64 to 118 natural gas units at 2.5 to 5 MW, and 78 bi-fuel units at 4 MW. For natural gas turbines at 34 to 50 MW each, the table lists 5 to 8 calculated units plus 1 redundant unit, but prints the total as 35 to 51; that total does not follow from the table's own columns (5 to 8 plus 1 would be 6 to 9), and the deck's noise table separately uses 58 turbine units, so the turbine totals are internally inconsistent in the source and should not be relied on. On fuel, the deck states that standard industrial backup generators use about 70 gallons of diesel per hour per megawatt, giving about 450,000 gallons for a 24-hour outage at 270 MW and 900,000 gallons for the 48-hour supply it calls industry standard, which the deck states are 'reduced by ~2/3 for bi-fuel generators' to 157,500 and 315,000 gallons (the printed gallon figures are 35 percent of the diesel totals, a 65 percent reduction, slightly less than the deck's '~2/3' wording). Its noise table estimates property-line levels at a 400-foot setback without mitigation of 73 dBA diesel, 68 natural gas, 69 bi-fuel and 75 turbine, with the deck's caveat that these are dBA only and that dBC levels need further research. All figures are the committee's own calculations against a hypothetical load, not a developer submission, permit application, or measurement.

Proposed edit

Present the committee's diesel, natural gas and bi-fuel unit counts, diesel storage figures and property-line noise estimates as its own calculations for an unspecified-capacity-type 270 MW hypothetical, omit the turbine unit total or flag it as internally inconsistent in the source, reproduce the dBA-only caveat, and give the bi-fuel storage as the deck's printed gallon figures rather than restating the '~2/3' reduction.

Critic findings against this item (1)

no-fabricationThe summary says 'All figures are the committee's own calculations against a hypothetical load', and the proposed_change calls 270 MW an 'unspecified-capacity-type 270 MW hypothetical'. The deck is quoted only as sizing for a ''270 MW Data Center''. Entry 18 indicates the committee uses 270–300 MW for the proposed project itself. Nothing quoted from source_url supports 'hypothetical', and the label conflicts with entry 18. Drop 'hypothetical' or support it with the deck's own wording.

evidence-label-accuracyEntry is labeled 'verified', but its central fact, the October 23, 2026 meeting date that the proposed_change wants added to the timeline, is admittedly an inference from the file name, embedded title and creation date. The printed header reads 'Friday, October 16th, 2026'. A primary record that contradicts the date being asserted does not directly support it. Either label the date claim separately as unverified/inferred or split the entry so 'verified' covers only the posting and agenda contents.

Source · 2026-10-22 ↗

verified Critic flagged 2026-10-26

town-of-lysander-official-records

The town posted white_paper_excerpt.pdf in its 2026-10 upload folder: 3 pages, PDF metadata creation date October 22, 2026, metadata title 'Microsoft Word - M Turner White Paper excerpt.docx' and metadata author 'Kevin Rode', the same metadata author as the committee's October 9 and October 23 agenda files. The text is headed 'Mike Turner White paper excerpt' and identifies itself as pages 12-14 of 'Loudoun County, Virginia: Data Center Capital of the World, "A Strategy for a Changing Paradigm"' by Vice Chair/Ashburn Supervisor Mike Turner, Loudoun County, VA Board of Supervisors, July 1, 2026 (original edition July 1, 2024). It reproduces a timeline of Loudoun County data center growth from 1993 onward. The metadata indicates the excerpt was prepared as a Word document on the Lysander side; the text itself is attributed to Turner. This entry verifies only the posting and the document's stated origin, not the Loudoun facts it contains.

Proposed edit

If the site lists the committee's reference material, note the posted Turner white-paper excerpt (pages 12-14 of his July 1, 2026 edition) as Loudoun County background, not Lysander findings.

Critic findings against this item (1)

no-fabricationThe summary states the white paper's metadata author 'Kevin Rode' is 'the same metadata author as the committee's October 9 and October 23 agenda files'. Those files' metadata cannot come from source_url (white_paper_excerpt.pdf). Cite the agenda PDFs for that comparison or drop it.

Source · 2026-10-22 ↗

verified No objection filed 2026-10-26

town-of-lysander-official-records

The town posted july_1_data_center_briefing_202607131252299943_0.pdf in its 2026-10 upload folder: a 23-page presentation titled 'Data Center Growth: Our Changing Paradigm' by Vice Chair and Ashburn Supervisor Mike Turner, dated July 1, 2026, headed 'Resource Page, Ashburn, Loudoun County, VA' (PDF metadata creation date July 13, 2026). It states that its opinions and recommendations are the author's alone, do not represent any other Board member, the Loudoun County Board of Supervisors or county staff, and have no legal authority. It matches the October 23 agenda item 'Loudoun County PP / Mike Turner Presentation'. This entry verifies only the posting and the document's stated authorship.

Proposed edit

If the site lists the committee's reference material, note the Turner July 1, 2026 presentation as one Loudoun supervisor's personal opinion by its own disclaimer, not county policy and not Lysander findings.

Held only because another item in the 2026-10-26 batch was flagged. Nothing was filed against this one.

Source · 2026-07-01 ↗

verified No objection filed 2026-10-26

town-of-lysander-official-records

The town posted data_center_fact_sheet_2026_202609021623071592.pdf in its 2026-10 upload folder: a 2-page Loudoun County, Virginia 'Data Center Fact Sheet' branded loudoun.gov/DataCenters (PDF metadata creation date September 2, 2026). It contains a 'By the Numbers' panel labeled 'As of March 1, 2026', a data center timeline from the 1990s to 2026, and a list of ten 'top considerations' (siting, energy, electrical infrastructure, water, noise, land values, design standards, secure facilities, fire response, tax revenue). It matches the October 23 agenda item 'Loudoun County Fact Sheet'. This entry verifies only the posting and the document's origin.

Proposed edit

If the site lists the committee's reference material, note the posted Loudoun County fact sheet as Loudoun government material, not Lysander findings.

Held only because another item in the 2026-10-26 batch was flagged. Nothing was filed against this one.

Source · 2026-09-02 ↗

verified No objection filed 2026-10-26

town-of-lysander-official-records

The town posted data_center_-_residents_3_202609021954218107.pdf in its 2026-10 upload folder: a 1-page Loudoun County sheet titled 'Data Centers in Loudoun County - Stay Informed. Get Involved. Information for Residents' (PDF metadata creation date September 2, 2026). It covers how the county says it is addressing data center concerns, noise complaints, transmission lines and tax rates, and directs readers to loudoun.gov pages. It matches the October 23 agenda item 'LC Citizens Residents Info Sheet'. This entry verifies only the posting and the document's origin.

Proposed edit

If the site lists the committee's reference material, note the posted Loudoun residents information sheet as Loudoun government material, not Lysander findings.

Held only because another item in the 2026-10-26 batch was flagged. Nothing was filed against this one.

Source · 2026-09-02 ↗

reported No objection filed 2026-10-26

town-of-lysander-official-records

The posted '15 Best Practices for Communities Considering Data Centers' one-pager (2 pages, footer dated May 2026, PDF metadata author 'Turner, Mike') points readers to the white paper of Loudoun County, VA Vice Chair Mike Turner. It ranks six issues in descending priority: noise, power, water, emissions, setback and appearance. It recommends: - never allowing data centers to build 'by right' without governing-body approval and never signing a non-disclosure agreement; - pre- and post-construction noise studies in dBA and dBC, and a noise limit of 50 dBA at the sending property line, with dBC tonal or narrow-band noise reduced to background levels; - requiring utilities to state in writing the maximum power requested and the delivery route, with board approval to exceed it; - siting near existing power lines but no closer than twice the right-of-way; - requiring substations on site or adjacent and included in the application; - long-duration storage (10 hours minimum) rather than lithium-ion; - written annual water-use figures from the data center and water utility, and disclosure of cooling type, potable versus reclaimed water and wastewater treatment; - Tier IV generators, or Tier II generators with selective catalytic reduction; - a 500-foot residential setback, with 1,000 feet described as ideal; - screening, height and floor-area-ratio limits, and microgrid design. These are a Loudoun official's recommendations. They are not Lysander positions or adopted Lysander code.

Proposed edit

If the site summarizes the committee's reference material, attribute the 15 best practices to Loudoun Supervisor Mike Turner and keep them separate from the Lysander committee's own recommendations and from enacted Lysander code.

Held only because another item in the 2026-10-26 batch was flagged. Nothing was filed against this one.

Source · 2026-05-26 ↗

reported Critic flagged 2026-10-26

town-of-lysander-official-records

The posted Loudoun County fact sheet states that in 2025, in Phase 1 of a policy project, the county Board of Supervisors ended by-right development of most data centers, so future proposals go through legislative review with public input, with a grandfathering resolution letting certain pending applications continue by right. It states that Phase 2, on use-specific zoning standards for data centers and substations, is underway in 2026, and that 'The FY 2027 adopted budget projects data center revenue at $1.3 billion, representing 40% of the total budget.' The separately posted residents sheet states that the Board ended by-right development of data centers in 2025 and that all new data center development requires its legislative approval. These are Loudoun County statements; the figures were not checked against Loudoun budget records.

Proposed edit

If the site cites Loudoun figures from the committee's reference material, attribute the by-right change and the $1.3 billion / 40 percent budget figure to the Loudoun County fact sheet.

Critic findings against this item (1)

no-fabricationsource_url is the Loudoun fact sheet (data_center_fact_sheet_2026_...pdf), but the summary also reports what 'the separately posted residents sheet states' (Board ended by-right development in 2025; all new development requires legislative approval). Those claims trace to data_center_-_residents_3_...pdf, not to the cited source. Split them out or cite the residents sheet.

Source · 2026-09-02 ↗

reported No objection filed 2026-10-26

town-of-lysander-official-records

The posted Turner white-paper excerpt states that the Loudoun County Board of Supervisors ended 'by right' data center development by a 7-2 vote at a March 18, 2025 Board meeting, that Loudoun has about 250 data centers with 117 more in the development pipeline, and that in March 2024 the Board denied a 4.9 million sq. ft./600 MW data center next to a residential neighborhood but approved it once reduced to 1.3 million sq. ft. These are Turner's statements in his own white paper, not county records.

Proposed edit

If the site cites the March 18, 2025 by-right decision or the Loudoun data center count, attribute them to Turner's white paper rather than presenting them as verified Loudoun records.

Held only because another item in the 2026-10-26 batch was flagged. Nothing was filed against this one.

Source · 2026-10-22 ↗

reported Critic flagged 2026-10-26

town-of-lysander-official-records

The posted Turner July 1, 2026 presentation states that FY2027 projected local tax funding in Loudoun is $2.9 billion, of which $1.3 billion is data center tax revenue (one-third real, two-thirds personal property), and gives Loudoun power consumption of 4.14 GW in 2024 and 5.33 GW in 2025 (labeled actual). It projects 14.2 GW by 2030 on a linear trend and 20+ GW with AI rack densities. Its $1.3 billion figure is set against $2.9 billion in local tax funding, while the county fact sheet describes $1.3 billion as 40 percent of the total budget; the two denominators differ and should not be combined. The presentation's own disclaimer says these are the author's opinions alone.

Proposed edit

If the site cites Loudoun revenue or power figures, attribute them to Turner's presentation as one supervisor's account and report its $1.3 billion of $2.9 billion separately from the fact sheet's 40 percent of the total budget.

Critic findings against this item (1)

distinguish-capacity-typesThe summary gives 'Loudoun power consumption of 4.14 GW in 2024 and 5.33 GW in 2025 (labeled actual)' and projects '14.2 GW by 2030' and '20+ GW'. GW is a unit of power (demand or capacity), not energy consumed, and the summary doesn't say whether these are peak demand, average load, contracted/connected capacity, or metered load. Calling them 'consumption' blurs operating load, capacity and metered usage. State the presentation's exact label and measure, or flag the measure as unstated.

Source · 2026-09-15 ↗

reported Critic flagged 2026-10-25

town-of-lysander-official-records

The 24-page deck for the Lysander Data Center Advisory Committee's October 9, 2026 meeting (PDF created October 9, 2026) gives the committee's own account of a call with National Grid on October 2, 2026. No National Grid document is attached; every statement below is what the committee says National Grid told it. Per the deck, National Grid confirmed it is looking to add a new substation in the area between Church Road and Emerick Road, paid for by Micron, exclusively for Micron's use, part of the Micron plan from the start, and only coincidentally near the proposed data center site. The deck also reports National Grid as saying: a data center would pay for its own grid upgrades; large-load users would be in their own rate group, which should not raise prices for other rate groups; brownouts would not occur because NYISO will not approve new large users without a plan to supply the power; grid upgrades for a data center would likely improve reliability for nearby customers; curtailment is a voluntary discounted-rate program that large-load customers are not required to join; and it had no problem with limiting lithium-ion battery storage. National Grid said it would follow up with historical area electricity usage data.

Proposed edit

If used, record the committee's account of the October 2 National Grid call, including the reported Micron-funded substation between Church and Emerick roads, as the committee's report of utility statements, not as a utility or PSC filing, and do not present the rate-group or reliability assurances as established facts.

Critic findings against this item (1)

evidence-label-accuracyLabeled 'verified', but the summary itself says 'No National Grid document is attached; every statement below is what the committee says National Grid told it.' The substantive content (Micron-funded substation 'between Church Road and Emerick Road', data center paying for its own upgrades, separate rate group, 'brownouts would not occur', voluntary curtailment) is a named party's statements relayed without underlying data, which is the definition of 'reported', not 'verified'. The proposed_change even says 'do not present the rate-group or reliability assurances as established facts', which contradicts a verified label. Relabel as 'reported'.

evidence-label-accuracyThe summary says 'The deck's statements about agency jurisdiction and bill status are filed separately as reported' (entry 27), but the proposed_change for this verified entry folds them back in: '...alongside the deck's own statement of the division of authority between the town, DEC, OCWA and WEP.' That would publish reported-class content (unverified division-of-authority claims) under a verified entry. Drop that clause from the proposed_change and leave it to entry 27.

Source · 2026-09-18 ↗

verified Critic flagged 2026-10-25

town-of-lysander-official-records

The presentation deck accompanying the September 18, 2026 meeting sets out the committee's recommendations on on-site backup generation: - allow only natural gas or bi-fuel generators for emergency backup power; - trigger an immediate shutdown if bi-fuel units fall below 70 percent natural gas use during a test; - allow generators only for backup power during an outage, with no behind-the-meter use of generators or turbines; - require a full environmental impact study addressing noise and environmental issues before any approval; - require scheduled inspections by a certified third party; - confine testing to specified weekday daytime hours, with caps on units tested at once and on annual testing hours; - require a separate decommissioning bond for generator farms; - define generator farms as a special use requiring separate review and permit. The deck was prepared for the scheduled September 18 work session. No minutes were located showing it was presented, and the recommendations are not adopted town code. The deck's rationale and its statement of the division of authority are filed separately as reported.

Proposed edit

Record the committee's on-site generation recommendations - natural gas or bi-fuel only, backup-only with no behind-the-meter generation, special-use permitting, decommissioning bond and testing-hour limits - as proposed local controls under development, clearly distinguished from enacted code, alongside the deck's own statement of the division of authority between the town, DEC, NYISO and the PSC.

Critic findings against this item (1)

evidence-label-accuracySame issue as entry 26. The summary says 'The deck's rationale and its statement of the division of authority are filed separately as reported' (entry 42), but the proposed_change for this verified entry adds '...alongside the deck's own statement of the division of authority between the town, DEC, NYISO and the PSC.' Those claims ('the town has no say in power delivery or rates', the NYISO/PSC/DEC split) are unchecked committee characterizations and should not ride along under a verified label. Remove the clause and keep them in entry 42.

evidence-label-accuracyEntry is labeled 'verified', but its entire substance is National Grid's statements as relayed by the committee — the summary itself says 'No National Grid document is attached; every statement below is what the committee says National Grid told it' (Micron-funded substation between Church Road and Emerick Road, separate large-load rate group, 'brownouts would not occur', curtailment voluntary). No primary public record from National Grid, NYISO or the PSC directly supports these statements; they are a named company's statements without public underlying data, which is the definition of 'reported'. The draft's own parallel entries for third-party positions relayed through committee decks (13: noise consultants; 20, 25, 36, 40: agency/species/regulatory characterizations) are labeled 'reported', so 18 is inconsistent with them. The proposed_change also hedges ('not as a utility or PSC filing ... do not present the rate-group or reliability assurances as established facts'), which contradicts a 'verified' label. Relabel as 'reported' (or split into a 'verified' entry covering only that the deck records an October 2 call, and a 'reported' entry for the statements attributed to National Grid).

Source · 2026-10-09 ↗

verified Critic flagged 2026-10-23

town-of-lysander-official-records

A Lysander Data Center Advisory Committee agenda file, dcac_agenda_10-23-26.pdf (PDF metadata creation date October 22, 2026), is now linked from the town home page and the Data Center Information notice page. It schedules a 9:00 AM work session at the Baldwinsville Public Library rather than the 8220 Loop Road location used on earlier agendas. The header reads 'Friday, October 16th, 2026', but the file name, the creation date and the separate October 16 agenda already on file indicate the meeting is October 23, 2026. The header date looks like a carry-over error, and this pass did not confirm the date independently. New business lists a 'White Paper Excerpt Mike Turner - How did We get here?', a 'Loudoun County PP / Mike Turner Presentation', a 'Loudoun County Fact Sheet', 'LC 15 Best Practices' and an 'LC Citizens Residents Info Sheet', followed by committee comments/feedback and next meeting. Unlike recent agendas, it lists no old business, so the noise ordinance and concerns-list items do not appear. The agenda shows only that the session was scheduled. It does not show that the meeting took place.

Proposed edit

Add the October 23, 2026 committee work session (Baldwinsville Public Library) to the Lysander timeline as scheduled. Note that its agenda is devoted to Loudoun County, Virginia reference material and that its header misstates the date as October 16.

Critic findings against this item (1)

evidence-label-accuracyLabeled 'verified', but the meeting date October 23, 2026 is inferred from the file name, PDF creation date and the existence of a separate October 16 agenda. The source itself prints 'Friday, October 16th, 2026', and the summary admits 'this pass did not confirm the date independently'. The proposed_change still asserts 'Add the October 23, 2026 committee work session' and says the header 'misstates' the date, which presents an inference as verified fact. Either label the date as inferred or estimated, or confirm it from a second primary record, such as the October 9 agenda's 'meeting location for October 23' item. The claim that the file 'is now linked from the town home page and the Data Center Information notice page' also does not trace to the agenda PDF given as source_url.

Source · 2026-10-22 ↗

verified Critic flagged 2026-10-23

town-of-lysander-official-records

Five reference documents matching the October 23 agenda items are linked from the town home page and the Data Center Information notice page, all in the town's 2026-10 upload folder. None is a Lysander-authored analysis of the Lysander project. - white_paper_excerpt.pdf: 3 pages, created October 22, 2026; PDF metadata title 'M Turner White Paper excerpt', metadata author 'Kevin Rode'. It reproduces a timeline of Loudoun County, Virginia data center growth from 1993 onward. - data_center_15_best_practices one-pager: 2 pages, metadata author 'Turner, Mike'. - 'Data Center Fact Sheet': 2 pages, Loudoun County, branded loudoun.gov/DataCenters. - 'Data Centers in Loudoun County' residents sheet: 1 page. - july_1_data_center_briefing: 23 pages, titled 'Data Center Growth: Our Changing Paradigm' by Vice Chair and Ashburn Supervisor Mike Turner, dated July 1, 2026. It states that its opinions are the author's alone and do not represent the Loudoun County Board of Supervisors or staff. The file names suggest the one-pager, fact sheet and residents sheet were obtained in May and September 2026, but all were posted in the October folder. This entry verifies only that the town posted these documents as committee material. Their contents describe Loudoun County, not Lysander.

Proposed edit

Note in the Lysander committee record that, for its October 23, 2026 session, the committee posted Loudoun County, Virginia reference material (a Turner white-paper excerpt, a July 1, 2026 Turner presentation, a 15 best-practices one-pager, and a county fact sheet and residents sheet) as background. Do not treat it as Lysander findings.

Critic findings against this item (1)

no-fabricationsource_url is the general notice page (lysanderny.gov/notices/data-center-information). The specific facts in the summary come from five separate PDFs that are not cited: the page counts (3, 2, 2, 1, 23), PDF metadata titles and authors ('M Turner White Paper excerpt', 'Kevin Rode', 'Turner, Mike'), the July 1, 2026 date and the 'Vice Chair and Ashburn Supervisor' title. The notice page cannot plausibly contain those. Also, 'None is a Lysander-authored analysis' sits uneasily with the white-paper excerpt's metadata author 'Kevin Rode', apparently the Lysander Supervisor named in entry 10. Ambiguity resolves to hold. Narrow the wording or cite each PDF.

Source · 2026-10-22 ↗

reported Critic flagged 2026-10-23

town-of-lysander-official-records

The posted '15 Best Practices for Communities Considering Data Centers' one-pager is attributed to Loudoun County Vice Chair Mike Turner. It ranks six issues in descending priority: noise, power, water, emissions, setback and appearance. It recommends: - never allowing 'by right' data center development and never signing a non-disclosure agreement; - pre- and post-construction noise studies in dBA and dBC, and a noise limit of 50 dBA at the sending property line, with dBC tonal or narrow-band noise reduced to background levels; - requiring utilities to state in writing the maximum power requested and the delivery route, with board approval to exceed it; - siting near existing power lines but no closer than twice the right-of-way; - requiring substations on site or adjacent and included in the application; - long-duration storage (10 hours minimum) rather than lithium-ion; - written annual water-use figures from the data center and water utility, and disclosure of cooling type, potable versus reclaimed water and wastewater treatment; - Tier IV generators, or Tier II generators with selective catalytic reduction; - a 500-foot residential setback, with 1,000 feet described as ideal; - screening, height and floor-area-ratio limits, and microgrid design. The posted Loudoun County fact sheet separately states that the county's Board of Supervisors ended by-right development of most data centers in 2025, and that the FY 2027 adopted budget projects $1.3 billion in data center revenue, 40 percent of the total budget. The Turner presentation dates the end of by-right development to March 18, 2025. These are statements by a Loudoun official and by Loudoun County materials. They are not Lysander positions or adopted Lysander code, and the Loudoun figures were not checked against Loudoun budget records.

Proposed edit

If the site summarizes the October 23 reference material, attribute the 15 best practices to Loudoun Supervisor Mike Turner and the by-right and revenue figures to Loudoun County documents. Keep them separate from the Lysander committee's own recommendations and from enacted Lysander code.

Critic findings against this item (1)

no-fabricationsource_url is the 15-best-practices one-pager, but the summary also states figures from other documents: the Loudoun fact sheet's by-right end in 2025 and 'FY 2027 adopted budget projects $1.3 billion in data center revenue, 40 percent of the total budget', and the Turner presentation's 'March 18, 2025' date. Those do not trace to the cited one-pager. Split them into entries citing the fact-sheet and july_1_data_center_briefing PDFs.

Source · 2026-10-22 ↗

verified No objection filed 2026-10-23

psc-case-26-e-0045-large-load-interconnection

The Department of Public Service Large Load and Data Center Interconnection Technical Working Group (Load-ITWG) page lists, under 'Upcoming Load-ITWG Meeting', a working-group meeting on October 30, 2026, 2:00 to 3:00 PM ET via WebEx. On October 23 the same page still shows '0 results found' under past Load-ITWG meetings and posts no agenda or materials for the October 30 session. The page lists Executive Order 62 as related material. It does not state the meeting's Case 26-E-0045 docket association.

Proposed edit

Add the scheduled October 30, 2026 Load-ITWG meeting to the state interconnection timeline as an upcoming event, without describing its agenda until materials are posted.

Held only because another item in the 2026-10-23 batch was flagged. Nothing was filed against this one.

Source · 2026-10-30 ↗

verified No objection filed 2026-10-23

psc-case-26-e-0045-large-load-interconnection

A Department of Public Service event page lists a Large Load and Data Center Interconnection Technical Working Group (Load-ITWG) meeting on September 10, 2026, 12:00 to 1:00 PM ET via WebEx, under Case 26-E-0045. The posted agenda covers introductions, a working group overview (identifying primary and secondary points of contact and liaisons for agenda development), a group discussion of interconnection queue status and concerns, and closing and next steps. The event page and agenda show that the session was scheduled with an agenda. They do not show that the meeting took place, and no meeting notes were located.

Proposed edit

Add to the Case 26-E-0045 timeline that DPS scheduled a Load-ITWG working group meeting for September 10, 2026, with a posted agenda on interconnection queue status. Do not state that the meeting was held.

Held only because another item in the 2026-10-23 batch was flagged. Nothing was filed against this one.

Source · 2026-09-10 ↗

verified No objection filed 2026-10-23

lysander-town-board-minutes

Unapproved minutes of the Lysander Town Board meeting of October 1, 2026 (PDF created October 17, 2026) record Resolution 237/2026, moved by Councilor Kudarauskas and seconded by Councilor Mangan and carried with all four members voting aye, authorizing the Town Clerk to advertise a public hearing before the Town Board at 6:30 PM on Thursday, November 5, 2026 to extend the moratorium on data centers in the Town of Lysander, and stating the moratorium 'will be extended to May 9, 2027.' The minutes also record that Supervisor Rode announced the November 5 hearing, that the Board 'discussed the proposed moratorium and expressed unanimous support,' with discussion including data center development practices and tax impacts in Loudoun County, Virginia, and that Councilor Schmitt reported the Data Center Advisory Committee had discussed fuel usage, energy and environmental impacts. The minutes are marked unapproved; the extension itself is not adopted until after the hearing. The minutes record four members voting; this pass did not confirm whether four was the full Board or only those present, so the vote should not be described as unanimous of the full Board.

Proposed edit

Update the Lysander moratorium entry: on October 1, 2026 the Town Board adopted Resolution 237/2026, carried with all four members voting aye per the unapproved minutes, authorizing a November 5, 2026 public hearing on extending the data center moratorium to May 9, 2027. Any differing date in the separately filed October 1 agenda entry should be reconciled against these minutes.

Held only because another item in the 2026-10-23 batch was flagged. Nothing was filed against this one.

Source · 2026-10-01 ↗

verified Critic flagged 2026-10-23

town-of-lysander-official-records

The Lysander Data Center Advisory Committee agenda for Friday, October 16, 2026 (file dcac_10-16-26_agenda.pdf, PDF metadata creation date October 15, 2026) schedules a 9:00 AM work session at 8220 Loop Road. Old business lists proposed noise ordinance wording from outside consultants, now described as a 'Progress Update' rather than awaiting changes; a data center concerns list progress update; and the Battery Energy Storage System (BESS) Ordinance. New business continues the environmental concerns discussion with three listed topics: DEC SPDES requirements, SEQRA EIS requirements and lead agency, and decommissioning goals. The next meeting's stated topic is again the environmental concerns discussion. No committee minutes had been located as of October 16, 2026.

Proposed edit

Add the October 16, 2026 DCAC work session to the local timeline with its three listed environmental topics (SPDES, SEQRA EIS and lead agency, decommissioning).

Critic findings against this item (1)

evidence-label-accuracyThe verified source is an agenda, which shows only that a session was scheduled. Yet the proposed_change says 'Add the October 16, 2026 DCAC work session to the local timeline' without 'as scheduled', and the summary omits the 'does not show that the meeting took place' caveat used in entries 0, 24, 28 and 32. As worded, it can be read as verifying that the meeting was held. Add the scheduled-only qualifier.

Source · 2026-10-09 ↗

verified Critic flagged 2026-10-23

town-of-lysander-official-records

The Lysander Data Center Advisory Committee agenda file dcac_agenda_10-9-26.pdf (PDF metadata creation date October 8, 2026, 23:52 UTC) schedules a 9:00 AM work session at 8220 Loop Road. The agenda header reads 'Friday, October 8th, 2026', but October 8, 2026 is a Thursday; the file name indicates October 9, a Friday, so the header date appears to be a typo. Old business repeats the prior weeks: proposed noise ordinance wording from outside consultants, still described as awaiting changes; a data center concerns list progress update; and the Battery Energy Storage System (BESS) Ordinance. New business lists the meeting location for October 23 and October 30, a 'Call with National Grid', and continuing the environmental concerns discussion, which is also the stated topic of the next meeting. The agenda itself does not reference a presentation deck; a deck for the October 9 meeting was posted separately (see the 10-9-26_pp_0.pdf entries). No committee minutes had been located as of October 11, 2026.

Proposed edit

Add the October 9, 2026 DCAC work session to the local timeline, quoting the new-business item 'Call with National Grid' as written (the companion October 9 deck entry reports a call that took place October 2), noting the listed October 23 and October 30 meeting-location item, and flagging the header-date discrepancy rather than resolving it.

Critic findings against this item (1)

evidence-label-accuracySame issue as entry 6. The proposed_change says 'Add the October 9, 2026 DCAC work session to the local timeline' without labeling it as scheduled, while the only verified support is the agenda, and no minutes were located as of October 11. The summary also does not say the agenda fails to show the meeting took place. Add the scheduled-only qualifier. Note too that the companion deck (entries 12-16) is a pre-meeting deck and does not confirm attendance.

no-fabricationsource_url is the October 30 event page, which per the summary shows only date, time and WebEx format. But the summary's framing ('the Load-ITWG page lists, under Upcoming Load-ITWG Meeting...') and the claim that 'The page lists Executive Order 62 among related material' come from the separate Load-ITWG overview page, not the cited event page. Either cite the overview page or limit the summary to what the event page shows.

Source · 2026-10-30 ↗

verified Critic flagged 2026-10-22

psc-case-26-e-0045-large-load-interconnection

A Department of Public Service event page lists a Large Load and Data Center Interconnection Technical Working Group (Load-ITWG) meeting on September 10, 2026, 12:00 to 1:00 PM ET via WebEx, under Case 26-E-0045. The posted agenda covered introductions, a working group overview (identifying primary and secondary points of contact and liaisons for agenda development), a group discussion of interconnection queue status and concerns, and closing and next steps. A separate DPS Load-ITWG page states the group's goal is to identify, discuss and resolve technical barriers to interconnecting data centers and other large loads to New York's transmission and distribution systems, names DPS's Kevin Luteran as working group chair, and lists Executive Order 62 among related materials; its past-meetings list showed zero results on October 19. The page does not state whether this meeting is the technical conference the February 12, 2026 order required before December 31, 2026, and no meeting notes or later meetings were located.

Proposed edit

Add to the Case 26-E-0045 timeline that DPS convened a Load-ITWG working group meeting on September 10, 2026 on interconnection queue status, without equating it to the order's required technical conference.

Critic findings against this item (2)

no-fabricationsource_url is the September 10 event page, but the summary brings in facts from other documents: Kevin Luteran as working group chair, Executive Order 62 in related materials, and the past-meetings list 'showed zero results on October 19' (all attributed to 'a separate DPS Load-ITWG page'), plus the February 12, 2026 order's December 31, 2026 technical-conference deadline (from the Order Instituting Proceeding, entry 30). None of these trace to the cited source_url.
evidence-label-accuracyproposed_change says 'DPS convened a Load-ITWG working group meeting on September 10, 2026', but the evidence is an event page and agenda, and the summary itself says 'no meeting notes ... were located.' The verified label supports only that the meeting was scheduled with a posted agenda, not that it was convened. Sibling entries (19, 23, 26) correctly say 'the agenda shows the session was scheduled; it does not show that the meeting took place.'

Source · 2026-09-10 ↗

verified Critic flagged 2026-10-22

lysander-town-board-minutes

Unapproved minutes of the Lysander Town Board meeting of October 1, 2026 (PDF created October 17, 2026) record Resolution 237/2026, moved by Councilor Kudarauskas and seconded by Councilor Mangan and carried with all four members voting aye, authorizing the Town Clerk to advertise a public hearing before the Town Board at 6:30 PM on Thursday, November 5, 2026 to extend the moratorium on data centers in the Town of Lysander, and stating the moratorium 'will be extended to May 9, 2027.' The October 1 agenda had listed April 1, 2027 for the same motion; the recorded resolution gives May 9, 2027. The minutes also record that Supervisor Rode announced the November 5 hearing, that the Board 'discussed the proposed moratorium and expressed unanimous support,' with discussion including data center development practices and tax impacts in Loudoun County, Virginia, and that Councilor Schmitt reported the Data Center Advisory Committee had discussed fuel usage, energy and environmental impacts. The minutes are marked unapproved; the extension itself is not adopted until after the hearing. The minutes record four members voting; this pass did not confirm whether four was the full Board or only those present, so the vote should not be described as unanimous of the full Board.

Proposed edit

Update the Lysander moratorium entry to state that on October 1, 2026 the Town Board adopted Resolution 237/2026, carried with all four members voting aye per the unapproved minutes, authorizing a November 5, 2026 public hearing on extending the data center moratorium to May 9, 2027, replacing any April 1, 2027 date taken from the agenda.

Critic findings against this item (1)

no-fabricationThe summary states 'The October 1 agenda had listed April 1, 2027 for the same motion'. That date comes from the separate agenda PDF (10-1-2026_agenda.pdf, entry 18), not the cited minutes PDF (10.1.2026_unapproved_meeting_minutes.pdf). The agenda/minutes discrepancy is useful but needs to cite both documents, not just the minutes.

evidence-label-accuracyLabeled 'verified', but much of the summary is the committee deck's own characterization of outside facts: the species statuses ('state-threatened' Pied-billed Grebe, Least Bittern, Henslow's Sparrow, Northern Harrier; 'federally and state-endangered' Indiana Bat and Northern Long-eared Bat), 'the planning board typically requires a full SEQRA review', and 'the town routinely requires decommissioning plans and bonds'. The summary admits these were not checked against DEC/USFWS records. Entry 5 labels the same kind of SEQRA-practice claim from a committee deck as 'reported'. The deck verifies only that the committee made these recommendations; split the entry or relabel the characterizations as reported.

Source · 2026-10-09 ↗

verified No objection filed 2026-10-22

town-of-lysander-official-records

A one-page map file, 10-9-26_map.pdf (PDF metadata creation date October 9, 2026), is linked from the town's Data Center Information notice page alongside the October 9 committee materials. It is a screenshot of an online map (Google map data attribution) showing the Three Rivers Wildlife Management Area between Wrights Corners, Phoenix, Radisson and Baldwinsville, with a red star outline placed south of the WMA, between its western section and its larger main section. The map has no title, legend or label explaining what the star marks.

Proposed edit

If used at all, cite the map only as a committee-posted reference image of the Three Rivers WMA, without stating what the unlabeled star marks or where it sits relative to any applicant's parcel.

Held only because another item in the 2026-10-22 batch was flagged. Nothing was filed against this one.

Source · 2026-10-09 ↗

estimated No objection filed 2026-10-22

town-of-lysander-official-records

The October 9 deck includes the committee's own heat arithmetic for natural gas backup generators. It states the generators are about 40 percent efficient, so 60 percent of fuel energy becomes waste heat and they must consume '150% more fuel energy than the electricity they output', which it says yields '150% more heat from the generators alone' and, added to the data center's own heat, 'a total site heat increase of 250% over normal operating conditions.' The arithmetic is ambiguous: under the deck's own premises, generator waste heat of 1.5 times electrical output added to the data center's normal heat would make total heat about 2.5 times normal, which is a 150 percent increase, not a 250 percent increase. The deck also estimates thermal plumes of about half a mile downwind at full generator output and a localized temperature rise averaging 3 to 6 degrees (unit unstated on that slide; a later slide uses Fahrenheit) in that corridor, and states that the prevailing wind blows east and northeast, with the wind blowing north or northwest roughly 20 percent of the time. No source or model is cited for the plume, temperature or wind figures.

Proposed edit

If the heat figures are used, present them as the committee's own uncited estimates, flag that '250% increase' is inconsistent with the deck's own premises (which give roughly 2.5 times normal heat, a 150 percent increase), and do not present the plume distance or temperature rise as modeled results.

Held only because another item in the 2026-10-22 batch was flagged. Nothing was filed against this one.

Source · 2026-10-09 ↗

verified No objection filed 2026-10-22

town-of-lysander-official-records

The Lysander Data Center Advisory Committee agenda file dcac_agenda_10-9-26.pdf (PDF metadata creation date October 8, 2026, 23:52 UTC) schedules a 9:00 AM work session at 8220 Loop Road. The agenda header reads 'Friday, October 8th, 2026', but October 8, 2026 is a Thursday; the file name indicates October 9, a Friday, so the header date appears to be a typo. Old business repeats the prior weeks: proposed noise ordinance wording from outside consultants, still described as awaiting changes; a data center concerns list progress update; and the Battery Energy Storage System (BESS) Ordinance. New business lists the meeting location for October 23 and October 30, a 'Call with National Grid', and continuing the environmental concerns discussion, which is also the stated topic of the next meeting. The agenda itself does not reference a presentation deck; a deck for the October 9 meeting was posted separately (see the 10-9-26_pp_0.pdf entries). No committee minutes had been located as of October 11, 2026.

Proposed edit

Add the October 9, 2026 DCAC work session to the local timeline, quoting the new-business item 'Call with National Grid' as written (the companion October 9 deck entry reports a call that took place October 2), noting the listed October 23 and October 30 meeting-location item, and flagging the header-date discrepancy rather than resolving it.

Held only because another item in the 2026-10-22 batch was flagged. Nothing was filed against this one.

Source · 2026-10-08 ↗

verified Critic flagged 2026-10-22

town-of-lysander-official-records

The 24-page presentation deck for the Lysander Data Center Advisory Committee's October 2, 2026 meeting, titled 'Environmental Concerns' (PDF created October 2, 2026), takes up light pollution, heat dissipation and site space. It recommends: updating town code to eliminate what it calls the 'ghost parking' loophole, under which unpaved reserved parking does not count toward the 30 percent site-coverage limit; requiring parking built to the industrial/manufacturing standard (1 space per 500 square feet rather than the warehouse standard of 1 per 4,000) to preserve adaptive reuse; adopting a separate Dark Sky lighting code for commercial and industrial users, including shielding, inward- and downward-facing perimeter lighting on its own circuit, and outdoor lighting off after 10 pm or within an hour of closing; requiring a heat dissipation study specific to the proposed cooling system; mandating green or high-albedo roofing; mandating strict cooling-system setbacks from property lines and wetland boundaries; establishing heat-differential standards with periodic monitoring; requiring deep, bedrock-level loops for geothermal systems; and requiring rooftop parapet thermal screening walls for air-cooled systems. The deck states that the planning board typically requires full SEQRA review for a project of this size, that DEC is responsible for water and air quality and for protecting the Three Rivers Wildlife Management Area and the Seneca River, that OCWA manages water and WEP wastewater for the site, and that the town can manage noise, light pollution, runoff and some heat discharge. It also notes that proposed state 'Dark Skies' bills (A4615, S9637) have not passed. These are committee recommendations in a deck prepared for the October 2 work session and posted alongside its agenda; no minutes were located showing the deck was presented or discussed, and the recommendations are not adopted town code.

Proposed edit

Record the committee's environmental recommendations - ghost-parking loophole closure, industrial parking standard, a Dark Sky lighting code, heat dissipation study and heat-differential monitoring, high-albedo or green roofing, cooling-system setbacks and geothermal and air-cooling controls - as proposed local controls under development, clearly distinguished from enacted code, alongside the deck's own statement of the division of authority between the town, DEC, OCWA and WEP.

Critic findings against this item (1)

evidence-label-accuracyLabeled 'verified', yet the summary includes unchecked deck claims about outside facts: 'proposed state Dark Skies bills (A4615, S9637) have not passed', that DEC is responsible for water/air quality and Three Rivers WMA/Seneca River protection, that OCWA manages water and WEP wastewater, and that the planning board typically requires full SEQRA review. Entry 6 labels the same division-of-authority statement from a committee deck as 'reported'. Bill status and agency jurisdiction are not verified by a committee deck; relabel or separate them from the verified recommendations.

evidence-label-accuracyLabeled 'verified', but includes the deck's regulatory and technical claims as content: 'natural-gas-fueled fuel cells do not meet New York clean energy guidelines because of CO2 emissions', 'only proton exchange membrane fuel cells and linear generators could serve as backup power', and sodium-ion/nickel-hydrogen having 'no thermal-runaway risk'. The summary calls these 'the deck's own technology characterizations', which fits 'reported', not 'verified'. A committee deck is not a primary record for New York clean-energy rules.

Source · 2026-09-25 ↗

estimated No objection filed 2026-10-22

town-of-lysander-official-records

The September 25 deck again refers to what it calls a 270 MW data center without saying whether 270 MW is requested interconnection capacity, service capacity, or critical IT load. The deck ties only two figures explicitly to that load: about 4 acres for a lithium iron phosphate BESS 'for 270MW backup system', and 108 linear-generator units 'required for a 270 MW data center', which it says would produce about 85 decibels and occupy 17 acres. It also lists footprints with no stated load basis: 1 to 2 acres for nickel manganese cobalt, about 6 acres for sodium-ion, 4 to 5 acres for nickel-hydrogen, about 25 acres for flow batteries, 3 to 5 acres for solid oxide fuel cells, 6 to 8 acres for molten carbonate and about 40 acres for proton exchange membrane fuel cells; whether those also assume 270 MW is not stated. These are the committee's own approximations, not vendor quotes, a developer submission or measurements; the 85-decibel figure is given without a stated distance or weighting.

Proposed edit

If the footprint and noise figures are used, present them as the committee's own approximations, tie only the lithium iron phosphate and linear-generator figures to the 270 MW hypothetical, state that the other acreages carry no stated load basis, and flag that the 85-decibel figure has no stated distance or weighting.

Held only because another item in the 2026-10-22 batch was flagged. Nothing was filed against this one.

Source · 2026-09-25 ↗

verified No objection filed 2026-10-22

town-of-lysander-official-records

The Lysander Data Center Advisory Committee agenda for Friday, September 18, 2026 at 9:00 AM at 8220 Loop Road schedules a work session. Under old business the agenda lists proposed noise ordinance wording from outside consultants, described as awaiting changes; a data center concerns list progress update; and the Battery Energy Storage System ordinance. Under new business it lists a continuation of the electricity discussion and a new topic, generators and turbines. The agenda states the next meeting will continue the electricity discussion. No applicant, named project, or Community Benefit Agreement action appears on this agenda. The agenda shows the session was scheduled; minutes confirming it took place were not located in the reviewed record.

Proposed edit

Add the September 18, 2026 Data Center Advisory Committee work session to the local-process timeline as scheduled, noting that the consultant-drafted noise ordinance language is awaiting changes and that generators and turbines entered the committee's agenda as a new business item.

Held only because another item in the 2026-10-22 batch was flagged. Nothing was filed against this one.

Source · 2026-09-18 ↗

verified Critic flagged 2026-10-22

town-of-lysander-official-records

The presentation deck accompanying the September 18, 2026 meeting sets out the committee's recommendations on on-site backup generation. It recommends allowing only natural gas or bi-fuel generators for emergency backup power, on the stated grounds that these are the two quietest options, eliminate or greatly reduce on-site diesel storage, produce far fewer greenhouse gas, carbon and soot emissions than diesel, and avoid the high-pitched whine of turbines; an immediate shutdown trigger if bi-fuel units fall below 70 percent natural gas utilization during a test; that generators be allowed only for backup power during an outage with no behind-the-meter use of generators or turbines; that a full environmental impact study addressing noise and environmental issues precede any approval; that scheduled inspections by a certified third party be required; that testing be confined to specified weekday daytime hours with caps on units tested at once and on annual testing hours; that a separate decommissioning bond be posted for generator farms; and that generator farms be defined as a special use requiring separate review and permit. The deck also records the division of authority: the town has no say in power delivery or rates, NYISO operates the high-voltage grid and sets supply charges while the PSC sets delivery charges and service classifications, and while DEC regulates generator emissions, fuel types and fuel storage, the town can regulate generator size, operating hours outside emergencies, setbacks and noise through code and can designate on-site or behind-the-meter generation above a threshold (the deck suggests 5 MW) as a separate or prohibited land use. These are committee recommendations in a deck prepared for the scheduled September 18 work session; no minutes were located showing it was presented, and the recommendations are not adopted town code.

Proposed edit

Record the committee's on-site generation recommendations - natural gas or bi-fuel only, backup-only with no behind-the-meter generation, special-use permitting, decommissioning bond and testing-hour limits - as proposed local controls under development, clearly distinguished from enacted code, alongside the deck's own statement of the division of authority between the town, DEC, NYISO and the PSC.

Critic findings against this item (1)

evidence-label-accuracyLabeled 'verified', but the 'division of authority' content is the deck's unchecked characterization of law and agency roles: 'NYISO ... sets supply charges while the PSC sets delivery charges and service classifications', 'DEC regulates generator emissions, fuel types and fuel storage', and that the town 'can designate ... generation above a threshold (the deck suggests 5 MW) as a separate or prohibited land use'. Entry 6 labels an equivalent division-of-authority passage 'reported'. Treating jurisdictional claims as verified because they appear in a committee deck misstates the evidence class.

Source · 2026-10-09 ↗

verified Critic flagged 2026-10-21

psc-case-26-e-0045-large-load-interconnection

A Department of Public Service event page lists a Large Load and Data Center Interconnection Technical Working Group (Load-ITWG) meeting on September 10, 2026, 12:00 to 1:00 PM ET via WebEx, under Case 26-E-0045. The posted agenda covered introductions, a working group overview (identifying primary and secondary points of contact and liaisons for agenda development), a group discussion of interconnection queue status and concerns, and closing and next steps. A separate DPS Load-ITWG page states the group's goal is to identify, discuss and resolve technical barriers to interconnecting data centers and other large loads to New York's transmission and distribution systems, names DPS's Kevin Luteran as working group chair, and lists Executive Order 62 among related materials; its past-meetings list showed zero results on October 19. The page does not state whether this meeting is the technical conference the February 12, 2026 order required before December 31, 2026, and no meeting notes or later meetings were located.

Proposed edit

Add to the Case 26-E-0045 timeline that DPS convened a Load-ITWG working group meeting on September 10, 2026 on interconnection queue status, without equating it to the order's required technical conference.

Critic findings against this item (1)

no-fabricationsource_url is the DPS event page for the September 10, 2026 meeting, but the summary also states facts it attributes to 'a separate DPS Load-ITWG page': the group's stated goal, 'DPS's Kevin Luteran as working group chair', 'Executive Order 62 among related materials', and that the past-meetings list 'showed zero results on October 19'. It also cites the February 12, 2026 order's December 31, 2026 technical-conference requirement. None of these is shown to be on the cited event page. Either add the Load-ITWG page (and the order, change 29) as cited sources, or remove those facts from this entry.

evidence-label-accuracyLabeled 'verified', but the summary itself says 'No National Grid document is attached; every statement below is what the committee says National Grid told it.' The claims (a Micron-funded substation between Church Road and Emerick Road, a separate rate group for large loads, 'brownouts would not occur', voluntary curtailment) are a named company's statements relayed second-hand, with no underlying data public. That matches 'reported', not 'verified'. The proposed_change already treats them as unconfirmed ('not as a utility or PSC filing'), and comparable deck entries that pass on third-party positions (3 and 5) are labeled 'reported'.

Source · 2026-10-09 ↗

verified Critic flagged 2026-10-20

psc-case-26-e-0045-large-load-interconnection

A Department of Public Service event page lists a Large Load and Data Center Interconnection Technical Working Group (Load-ITWG) meeting on September 10, 2026, 12:00 to 1:00 PM ET via WebEx, under Case 26-E-0045. The posted agenda covered introductions, a working group overview (identifying primary and secondary points of contact and liaisons for agenda development), a group discussion of interconnection queue status and concerns, and closing and next steps. A separate DPS Load-ITWG page states the group's goal is to identify, discuss and resolve technical barriers to interconnecting data centers and other large loads to New York's transmission and distribution systems, names DPS's Kevin Luteran as working group chair, and lists Executive Order 62 among related materials; its past-meetings list showed zero results on October 19. The page does not state whether this meeting is the technical conference the February 12, 2026 order required before December 31, 2026, and no meeting notes or later meetings were located.

Proposed edit

Add to the Case 26-E-0045 timeline that DPS convened a Load-ITWG working group meeting on September 10, 2026 on interconnection queue status, without equating it to the order's required technical conference.

Critic findings against this item (1)

no-fabricationsource_url is the DPS event page for the September 10, 2026 Load-ITWG meeting, but the summary also states facts drawn from 'a separate DPS Load-ITWG page' and from the February 12, 2026 order: the named party 'DPS's Kevin Luteran as working group chair', 'Executive Order 62' as a related material, the 'zero results on October 19' past-meetings observation, and the order's 'before December 31, 2026' technical-conference deadline. None of these trace to the cited event page. Either cite the Load-ITWG page and the order (entry 29's DocRefId) as additional sources, or remove these details from this entry.

Source · 2026-09-10 ↗

verified Critic flagged 2026-10-20

lysander-town-board-minutes

Unapproved minutes of the Lysander Town Board meeting of October 1, 2026 (PDF created October 17, 2026) record Resolution 237/2026, moved by Councilor Kudarauskas and seconded by Councilor Mangan and carried with all four members voting aye, authorizing the Town Clerk to advertise a public hearing before the Town Board at 6:30 PM on Thursday, November 5, 2026 to extend the moratorium on data centers in the Town of Lysander, and stating the moratorium 'will be extended to May 9, 2027.' The October 1 agenda had listed April 1, 2027 for the same motion; the recorded resolution gives May 9, 2027. The minutes also record that Supervisor Rode announced the November 5 hearing, that the Board 'discussed the proposed moratorium and expressed unanimous support,' with discussion including data center development practices and tax impacts in Loudoun County, Virginia, and that Councilor Schmitt reported the Data Center Advisory Committee had discussed fuel usage, energy and environmental impacts. The minutes are marked unapproved; the extension itself is not adopted until after the hearing. The minutes record four members voting; this pass did not confirm whether four was the full Board or only those present, so the vote should not be described as unanimous of the full Board.

Proposed edit

Update the Lysander moratorium entry to state that on October 1, 2026 the Town Board adopted Resolution 237/2026, carried with all four members voting aye per the unapproved minutes, authorizing a November 5, 2026 public hearing on extending the data center moratorium to May 9, 2027, replacing any April 1, 2027 date taken from the agenda.

Critic findings against this item (1)

no-fabricationsource_url is the unapproved October 1, 2026 minutes (10.1.2026_unapproved_meeting_minutes.pdf), but the summary says 'The October 1 agenda had listed April 1, 2027 for the same motion.' That April 1, 2027 date comes from a different document, 10-1-2026_agenda.pdf (entry 17's source), not the minutes. Cite the agenda for that date, or rely on entry 17 for the discrepancy instead of asserting it under the minutes' URL.

evidence-label-accuracyLabeled 'verified', but the summary includes the deck's own unverified characterizations stated as substantive facts: species protection statuses ('state-threatened (Pied-billed Grebe, Least Bittern, Henslow's Sparrow and Northern Harrier)', 'federally and state-endangered (Indiana Bat and Northern Long-eared Bat)') and procedural claims ('the planning board typically requires a full SEQRA review', 'the town routinely requires decommissioning plans and bonds'). The entry admits the statuses were not checked against DEC/USFWS records. Entries 4 and 5 put the same kind of committee characterization of external rules under 'reported'. The label is ambiguous, so this resolves toward hold. Either relabel as 'reported', or split it: one 'verified' entry for the recommendations alone, and the species and SEQRA characterizations under 'reported'.

evidence-label-accuracyEntry is labeled 'verified', but its own summary says 'No National Grid document is attached; every statement below is what the committee says National Grid told it.' Every substantive claim (the Micron-funded substation between Church Road and Emerick Road 'exclusively for Micron's use', large-load users in their own rate group, 'brownouts would not occur because NYISO will not approve new large users without a plan', curtailment being voluntary, no objection to limiting lithium-ion storage) is an uncorroborated secondhand account of utility statements, with no underlying primary record from National Grid, NYISO or the PSC. The proposed_change itself calls this 'the committee's report of utility statements, not ... a utility or PSC filing'. That fits 'reported' (as the parallel October 16 deck entries 3-5 are labeled), not 'verified'. Relabel to 'reported'.

Source · 2026-10-09 ↗

verified Critic flagged 2026-10-18

lysander-town-board-minutes

Unapproved minutes of the Lysander Town Board meeting of October 1, 2026 (PDF created October 17, 2026) record Resolution 237/2026, moved by Councilor Kudarauskas and seconded by Councilor Mangan and carried with all four members voting aye, authorizing the Town Clerk to advertise a public hearing before the Town Board at 6:30 PM on Thursday, November 5, 2026 to extend the moratorium on data centers in the Town of Lysander, and stating the moratorium 'will be extended to May 9, 2027.' The October 1 agenda had listed April 1, 2027 for the same motion; the recorded resolution gives May 9, 2027. The minutes also record that Supervisor Rode announced the November 5 hearing, that the Board 'discussed the proposed moratorium and expressed unanimous support,' with discussion including data center development practices and tax impacts in Loudoun County, Virginia, and that Councilor Schmitt reported the Data Center Advisory Committee had discussed fuel usage, energy and environmental impacts. The minutes are marked unapproved; the extension itself is not adopted until after the hearing.

Proposed edit

Update the Lysander moratorium entry to state that on October 1, 2026 the Town Board unanimously authorized a November 5, 2026 public hearing on extending the data center moratorium to May 9, 2027 (per unapproved minutes), replacing any April 1, 2027 date taken from the agenda.

Critic findings against this item (1)

evidence-label-accuracyThe proposed_change says the Board 'unanimously authorized' the hearing. The summary records the resolution as carried 'with all four members voting aye', and separately says the Board 'expressed unanimous support' during discussion. The Board has a Supervisor (Rode) plus councilors, so a four-member vote may not be the full Board, and 'unanimously' could overstate the recorded vote. Use the minutes' own wording ('carried, all four members voting aye'), or confirm that four was the full Board present.

Source · 2026-10-01 ↗

verified No objection filed 2026-10-18

town-of-lysander-official-records

The Lysander Data Center Advisory Committee agenda for Friday, October 16, 2026 (file dcac_10-16-26_agenda.pdf, PDF metadata creation date October 15, 2026) schedules a 9:00 AM work session at 8220 Loop Road. Old business lists proposed noise ordinance wording from outside consultants, now described as a 'Progress Update' rather than awaiting changes; a data center concerns list progress update; and the Battery Energy Storage System (BESS) Ordinance. New business continues the environmental concerns discussion with three listed topics: DEC SPDES requirements, SEQRA EIS requirements and lead agency, and decommissioning goals. The next meeting's stated topic is again the environmental concerns discussion. No committee minutes had been located as of October 16, 2026.

Proposed edit

Add the October 16, 2026 DCAC work session to the local timeline with its three listed environmental topics (SPDES, SEQRA EIS and lead agency, decommissioning).

Held only because another item in the 2026-10-18 batch was flagged. Nothing was filed against this one.

Source · 2026-10-15 ↗

reported No objection filed 2026-10-18

town-of-lysander-official-records

The 34-page deck for the October 16, 2026 committee meeting (PDF created October 15, 2026) reports a call with the town's outside noise consultants. By the committee's account, the consultants are adding sections on infrasound, 1/3-octave and low-frequency sound and will add dBC maximum thresholds alongside their original dBA-plus-offset approach. The deck says a 10 versus 15 dB dBC offset was debated and that the town will rent a meter to test which is more appropriate; limits of 60/50 versus 65/55 were discussed without a stated outcome; and the committee is 'leaning toward' measuring violations at whichever of the source or complainant property line reads highest. It states the consultants did not consider a local codes office capable of 1/3-octave or infrasound evaluations (periodic contracting was discussed), will not recommend penalties, enforcement or appeal provisions (the town will draft those), and declined to make recommendations on animal noise protections. No consultant document is attached; these are the committee's descriptions of the consultants' positions.

Proposed edit

Update the noise-ordinance status to show the draft is still in progress with consultants adding infrasound, 1/3-octave, low-frequency and dBC provisions, with the dBC offset, numeric limits and measurement point unresolved, attributing all consultant positions to the committee's account.

Held only because another item in the 2026-10-18 batch was flagged. Nothing was filed against this one.

Source · 2026-10-15 ↗

verified Critic flagged 2026-10-18

town-of-lysander-official-records

The same October 16 deck sets out the committee's understanding of the SEQRA environmental impact statement process and lead-agency question for the proposed data center. It states that for a project of this size the planning board typically requires a full SEQRA review; that the Lysander Planning Board routinely acts as lead agency for site plans and subdivisions while the Town Board typically does so for legislative actions, zone changes and special district formations; and that county bodies (OCIDA, County Planning, WEP, County Health) or state bodies (NYSDEC, NYPA, PSC) could also request lead-agency status, noting OCIDA is lead agency for Micron. It states that a lead-agency dispute not resolved by agreement is decided by the NYSDEC Commissioner, and argues that, although the Commissioner would usually favor a larger agency, the committee's documented work could support the town having the greater capacity. In this section the deck describes the project as a '270–300 MW data center' without saying which load measure that range represents. It lists the scope of an EIS, including cumulative impacts with the Micron project's power and water draw. The deck also lists decommissioning goals: no taxpayer-borne remediation or demolition cost, operator-funded hazardous-material disposal, the ability to claw back or reallocate grid allocations and water rights, nuisance limits during teardown, and workforce-transition provisions. These are committee positions and goals, not adopted town code or a lead-agency determination; no SEQRA application or lead-agency coordination for the project is documented in the deck.

Proposed edit

Record that the committee's October 16 deck argues the town could make a case for SEQRA lead-agency status on the grounds of its documented review capacity, describes SEQRA scoping in general terms, and lists draft decommissioning goals, all labeled as committee positions rather than enacted requirements, a lead-agency request or an agency determination.

Critic findings against this item (1)

evidence-label-accuracyLabeled 'verified', but the summary passes on the committee's legal and procedural claims without checking them against a primary record or adding a caveat: 'a lead-agency dispute not resolved by agreement is decided by the NYSDEC Commissioner', 'OCIDA is lead agency for Micron', and the Planning Board/Town Board lead-agency practice. Change 4 cites the same deck, makes the same kind of claim (the committee's description of state requirements, not checked against DEC), and is labeled 'reported' with an explicit not-checked caveat. Either relabel change 3 'reported', or add a caveat that these SEQRA and lead-agency statements are the deck's own characterizations, not checked against 6 NYCRR 617 or OCIDA records.

no-fabricationThe proposed_change calls the two petitions 'pending'. The summary only supports that the 10-K 'reports no ruling in either matter', and the court filings were not reviewed. Having no reported ruling does not prove a case is still open. Use 'no ruling reported in the 10-K' unless the 10-K text itself says 'pending', and if it does, quote it.

The same October 16 deck sets out the committee's understanding of the SEQRA environmental impact statement process and lead-agency question for the proposed data center. It states that for a project of this size the planning board typically requires a full SEQRA review; that the Lysander Planning Board routinely acts as lead agency for site plans and subdivisions while the Town Board typically does so for legislative actions, zone changes and special district formations; and that county bodies (OCIDA, County Planning, WEP, County Health) or state bodies (NYSDEC, NYPA, PSC) could also request lead-agency status, noting OCIDA is lead agency for Micron. It states that a lead-agency dispute not resolved by agreement is decided by the NYSDEC Commissioner, and argues that, although the Commissioner would usually favor a larger agency, the committee's documented work could support the town having the greater capacity. In this section the deck describes the project as a '270–300 MW data center' without saying which load measure that range represents. It lists the scope of an EIS, including cumulative impacts with the Micron project's power and water draw. The deck also lists decommissioning goals: no taxpayer-borne remediation or demolition cost, operator-funded hazardous-material disposal, the ability to claw back or reallocate grid allocations and water rights, nuisance limits during teardown, and workforce-transition provisions. These are committee positions and goals, not adopted town code or a lead-agency determination; no SEQRA application or lead-agency coordination for the project is documented in the deck.

Proposed edit

Record that the committee is preparing to seek town lead-agency status under SEQRA and a scoping process covering Three Rivers WMA, noise, grid, water and cumulative Micron impacts, plus draft decommissioning goals, all labeled as committee recommendations rather than enacted requirements or agency determinations.

Critic findings against this item (2)

no-fabricationproposed_change says the committee 'is preparing to seek town lead-agency status under SEQRA and a scoping process covering Three Rivers WMA, noise, grid, water and cumulative Micron impacts.' Neither the summary nor the source deck supports that. The deck's lead-agency slide only says 'the argument could be made that the town has the greater capacity to do a thorough review', which states no intent to seek lead-agency status. The list of Three Rivers WMA, noise, grid strain, water and air appears on the deck's generic explanation of how SEQRA scoping works ('This document forces the project to study specific local concerns like...'). It is not a scope the committee proposes. The summary itself is accurate ('argues that ... could support the town having the greater capacity'), but proposed_change turns a conditional argument into an intent the deck does not state. Reword it to: the deck argues the town could make a case for lead agency, and it describes SEQRA scoping in general terms.
evidence-label-accuracyEntry 2 is labeled 'verified', which is accurate for the summary. The proposed_change, though, presents 'preparing to seek town lead-agency status' as a documented fact. No primary record directly supports that statement, so the verified label does not cover it. Fix the wording of the proposed_change (see the no-fabrication finding); the label does not need to change.

evidence-label-accuracyLabeled 'verified', but the listing of protection statuses ('state-threatened Pied-billed Grebe, Least Bittern, Henslow's Sparrow and Northern Harrier, and the federally and state-endangered Indiana Bat and Northern Long-eared Bat') reads as a statement of fact without making clear the statuses are the deck's own characterization. The Northern Long-eared Bat's New York listing is generally threatened, not endangered, so 'state-endangered' may be wrong, and the deck is not a primary record for listing status. Either attribute each status explicitly to the deck ('which the deck describes as...') or cite the DEC/USFWS listing records. Because this is ambiguous, it is held.

Source · 2026-10-09 ↗

verified No objection filed 2026-10-15

town-of-lysander-official-records

A one-page map file, 10-9-26_map.pdf (PDF metadata creation date October 9, 2026), is linked from the town's Data Center Information notice page alongside the October 9 committee materials. It is a screenshot of an online map (Google map data attribution) showing the Three Rivers Wildlife Management Area between Wrights Corners, Phoenix, Radisson and Baldwinsville, with a red star outline placed south of the WMA, between its western section and its larger main section. The map has no title, legend or label explaining what the star marks.

Proposed edit

If used at all, cite the map only as a committee-posted reference image of the Three Rivers WMA, without stating what the unlabeled star marks or where it sits relative to any applicant's parcel.

Held only because another item in the 2026-10-15 batch was flagged. Nothing was filed against this one.

Source · 2026-10-09 ↗

estimated No objection filed 2026-10-15

town-of-lysander-official-records

The October 9 deck includes the committee's own heat arithmetic for natural gas backup generators. It states the generators are about 40 percent efficient, so 60 percent of fuel energy becomes waste heat and they must consume '150% more fuel energy than the electricity they output', which it says yields '150% more heat from the generators alone' and, added to the data center's own heat, 'a total site heat increase of 250% over normal operating conditions.' The arithmetic is ambiguous: under the deck's own premises, generator waste heat of 1.5 times electrical output added to the data center's normal heat would make total heat about 2.5 times normal, which is a 150 percent increase, not a 250 percent increase. The deck also estimates thermal plumes of about half a mile downwind at full generator output and a localized temperature rise averaging 3 to 6 degrees (unit unstated on that slide; a later slide uses Fahrenheit) in that corridor, and states that the prevailing wind blows east and northeast, with the wind blowing north or northwest roughly 20 percent of the time. No source or model is cited for the plume, temperature or wind figures.

Proposed edit

If the heat figures are used, present them as the committee's own uncited estimates, flag that '250% increase' is inconsistent with the deck's own premises (which give roughly 2.5 times normal heat, a 150 percent increase), and do not present the plume distance or temperature rise as modeled results.

Held only because another item in the 2026-10-15 batch was flagged. Nothing was filed against this one.

Source · 2026-10-09 ↗

verified Critic flagged 2026-10-15

town-of-lysander-official-records

The Lysander Data Center Advisory Committee agenda file dcac_agenda_10-9-26.pdf (PDF metadata creation date October 8, 2026, 23:52 UTC) schedules a 9:00 AM work session at 8220 Loop Road. The agenda header reads 'Friday, October 8th, 2026', but October 8, 2026 is a Thursday; the file name indicates October 9, a Friday, so the header date appears to be a typo. Old business repeats the prior weeks: proposed noise ordinance wording from outside consultants, still described as awaiting changes; a data center concerns list progress update; and the Battery Energy Storage System (BESS) Ordinance. New business lists the meeting location for October 23 and October 30, a 'Call with National Grid', and continuing the environmental concerns discussion, which is also the stated topic of the next meeting. The agenda itself does not reference a presentation deck; a deck for the October 9 meeting was posted separately (see the 10-9-26_pp_0.pdf entries). No committee minutes had been located as of October 11, 2026.

Proposed edit

Add the October 9, 2026 DCAC work session to the local timeline, noting the agenda's scheduled call with National Grid and the planned October 23 and October 30 sessions, and flag the header-date discrepancy rather than resolving it.

Critic findings against this item (1)

no-fabricationproposed_change says to note 'the agenda's scheduled call with National Grid', but the agenda only lists the item 'Call with National Grid' under new business. Entry 2, from the same October 9 materials, says the call took place on October 2, 2026. Calling it a call scheduled for the October 9 session is not supported by the source and conflicts with the companion entry. More likely it was a report on a call that had already happened. Quote the agenda item as written and do not describe it as a scheduled call.

Source · 2026-10-08 ↗

verified No objection filed 2026-10-15

town-of-lysander-official-records

The 24-page presentation deck for the Lysander Data Center Advisory Committee's October 2, 2026 meeting, titled 'Environmental Concerns' (PDF created October 2, 2026), takes up light pollution, heat dissipation and site space. It recommends: updating town code to eliminate what it calls the 'ghost parking' loophole, under which unpaved reserved parking does not count toward the 30 percent site-coverage limit; requiring parking built to the industrial/manufacturing standard (1 space per 500 square feet rather than the warehouse standard of 1 per 4,000) to preserve adaptive reuse; adopting a separate Dark Sky lighting code for commercial and industrial users, including shielding, inward- and downward-facing perimeter lighting on its own circuit, and outdoor lighting off after 10 pm or within an hour of closing; requiring a heat dissipation study specific to the proposed cooling system; mandating green or high-albedo roofing; mandating strict cooling-system setbacks from property lines and wetland boundaries; establishing heat-differential standards with periodic monitoring; requiring deep, bedrock-level loops for geothermal systems; and requiring rooftop parapet thermal screening walls for air-cooled systems. The deck states that the planning board typically requires full SEQRA review for a project of this size, that DEC is responsible for water and air quality and for protecting the Three Rivers Wildlife Management Area and the Seneca River, that OCWA manages water and WEP wastewater for the site, and that the town can manage noise, light pollution, runoff and some heat discharge. It also notes that proposed state 'Dark Skies' bills (A4615, S9637) have not passed. These are committee recommendations in a deck prepared for the October 2 work session and posted alongside its agenda; no minutes were located showing the deck was presented or discussed, and the recommendations are not adopted town code.

Proposed edit

Record the committee's environmental recommendations - ghost-parking loophole closure, industrial parking standard, a Dark Sky lighting code, heat dissipation study and heat-differential monitoring, high-albedo or green roofing, cooling-system setbacks and geothermal and air-cooling controls - as proposed local controls under development, clearly distinguished from enacted code, alongside the deck's own statement of the division of authority between the town, DEC, OCWA and WEP.

Held only because another item in the 2026-10-15 batch was flagged. Nothing was filed against this one.

Source · 2026-10-02 ↗

estimated Critic flagged 2026-10-15

town-of-lysander-official-records

The October 2, 2026 deck includes a 'Space Restrictions' table for a hypothetical 124-acre site with 30 percent buildable coverage (37.20 acres), comparing three two-story buildings with one tall building under industrial and warehouse parking standards. Each scenario deducts 5.50 acres for a generator farm, 2.75 for a substation, 1.75 for a switch yard, 6.00 for battery storage and 1.00 for gas regulation (17.00 acres), plus parking and roads (3.40 acres for the three-building layout, 3.20 for the one-building layout). Under the industrial parking standard, parking is 17.90 acres (three buildings) or 10.70 acres (one building), leaving -1.10 or 6.30 acres before the building; after a data center footprint of 13.80 or 5.50 acres, the table shows -14.90 acres (over the coverage limit) and 0.80 acres remaining. Under the warehouse standard, parking is 2.2 or 1.3 acres, leaving 14.60 or 15.70 acres before the building and 0.80 or 10.20 acres after it. The deck also gives parking-space ranges of 1,440 to 2,400 (industrial) and 180 to 300 (warehouse). Each column of the table is internally consistent. The deck does not name the site or state the building floor area or load behind these figures; they are the committee's own planning approximations, not a developer submission, site plan or survey.

Proposed edit

If the site-space comparison is used, present it as the committee's own approximation for an unnamed hypothetical 124-acre site, showing that the three-building industrial-parking layout exceeds the 30 percent coverage limit in the committee's own arithmetic, without attributing the figures to any applicant.

Critic findings against this item (1)

no-fabricationBoth the summary and proposed_change call the 124-acre site 'hypothetical' ('a hypothetical 124-acre site', 'an unnamed hypothetical 124-acre site'), but the summary itself says only that 'the deck does not name the site.' A site the deck doesn't name is not shown to be hypothetical. The figure may correspond to the actual proposed parcel discussed throughout the committee's environmental-concerns series. Nothing quoted from the source supports the word 'hypothetical'. Use 'an unnamed 124-acre site' unless the deck itself says the site is hypothetical.

Source · 2026-02-12 ↗

verified Critic flagged 2026-10-14

psc-case-26-e-0045-large-load-interconnection

The same February 12, 2026 order states the scale figure behind the proceeding: as of February 2026, 11.9 gigawatts of load within the New York Independent System Operator interconnection queue were attributed to future large-load projects, and in 2025 alone more than 8.3 gigawatts of new load entered the NYISO queue. The order presents these as the emerging challenge motivating interconnection reform. These are statewide queue figures for large loads generally, not a count of data centers and not specific to any Central New York project, and they should not be combined with any site-level megawatt figure. Re-verified this pass against the order text and unpromoted.

Proposed edit

Record the statewide context figure - 11.9 GW of large-load projects in the NYISO queue as of February 2026, with more than 8.3 GW added during 2025 - as state-level background, explicitly labeled statewide and not tied to a local site.

Critic findings against this item (1)

distinguish-capacity-typesThe summary keeps two separate figures from the order: '11.9 gigawatts of load ... attributed to future large-load projects' in the NYISO queue as of February 2026, and 'more than 8.3 gigawatts of new load entered the NYISO queue' in 2025. The summary does not say the 8.3 GW is limited to large loads. The proposed_change rewrites them as '11.9 GW of large-load projects in the NYISO queue as of February 2026, with more than 8.3 GW added during 2025'. That wording treats the 8.3 GW as a large-load subset of the 11.9 GW still in the queue, and the order as summarized does not say that. A queue snapshot at one date and a calendar-year inflow are different measures. Keep them as two separately stated figures, without the 'with ... added' wording that nests one inside the other.

town-of-lysander-official-records

The same October 9 deck continues the committee's environmental-concerns series with recommendations on heat dissipation and wildlife. On heat it recommends: a heat dissipation study specific to the proposed cooling system; green or high-albedo roofing; strict cooling-system setbacks from property lines and wetland boundaries; heat-differential standards with periodic compliance monitoring; deep, bedrock-level loops for geothermal systems; rooftop parapet thermal screening walls for air-cooled systems; an L-shaped earthen berm at the northwest corner of the site to protect the Three Rivers Wildlife Management Area west of Route 690; and an earthen berm between the generator farm and adjacent wetlands. It reiterates earlier recommendations limiting generators to emergency use and testing, pairing them with battery storage, dimming or turning off exterior lighting at night, and using closed-loop cooling. On wildlife it recommends that the environmental impact study specifically examine heat, emissions and noise effects on the WMA and adjacent wetlands, and an updated noise ordinance with pre- and post-implementation monitoring of low-frequency sound, infrasound and 1/3-octave bands plus a penalty for impulsive sound. The deck states that for a project of this size the planning board typically requires a full SEQRA review, and that the town routinely requires decommissioning plans and bonds for industrial and commercial projects. It lists species near the site it considers at risk, including state-threatened Pied-billed Grebe, Least Bittern, Henslow's Sparrow and Northern Harrier, and the federally and state-endangered Indiana Bat and Northern Long-eared Bat. A one-page map posted with the deck (10-9-26_map.pdf) shows the Three Rivers WMA with a red star marker just west of its southwestern boundary; the map has no legend or label explaining the marker.

Proposed edit

Record the committee's heat-dissipation and wildlife recommendations, including the berms protecting the Three Rivers WMA and the requested scope for an environmental impact study, as proposed local controls under development, clearly distinguished from enacted code, without stating where the unlabeled map marker sits relative to any applicant's parcel.

Critic findings against this item (1)

no-fabricationThe summary's last sentence describes 'A one-page map posted with the deck (10-9-26_map.pdf)' showing the Three Rivers WMA with a red star marker west of its southwestern boundary. That map is a separate file, not the cited source_url (10-9-26_pp_0.pdf), so the map description does not trace to source_url. Either move it to its own entry cited to the map PDF's URL or drop it.

Source · 2026-10-09 ↗

estimated No objection filed 2026-10-10

town-of-lysander-official-records

The October 9 deck includes the committee's own heat arithmetic for natural gas backup generators. It states the generators are about 40 percent efficient, so 60 percent of fuel energy becomes waste heat and they must consume '150% more fuel energy than the electricity they output', which it says yields '150% more heat from the generators alone' and, added to the data center's own heat, 'a total site heat increase of 250% over normal operating conditions.' The arithmetic is ambiguous: under the deck's own premises, generator waste heat of 1.5 times electrical output added to the data center's normal heat would make total heat about 2.5 times normal, which is a 150 percent increase, not a 250 percent increase. The deck also estimates thermal plumes of about half a mile downwind at full generator output and a localized temperature rise averaging 3 to 6 degrees (unit unstated on that slide; a later slide uses Fahrenheit) in that corridor, and states that the prevailing wind blows east and northeast, with the wind blowing north or northwest roughly 20 percent of the time. No source or model is cited for the plume, temperature or wind figures.

Proposed edit

If the heat figures are used, present them as the committee's own uncited estimates, flag that '250% increase' is inconsistent with the deck's own premises (which give roughly 2.5 times normal heat, a 150 percent increase), and do not present the plume distance or temperature rise as modeled results.

Held only because another item in the 2026-10-10 batch was flagged. Nothing was filed against this one.

Source · 2026-10-09 ↗

verified Critic flagged 2026-10-10

town-of-lysander-official-records

The Lysander Data Center Advisory Committee agenda posted October 8, 2026 (file dcac_agenda_10-9-26.pdf, linked from the town home page as 'Data Center Advisory Committee Meeting 10-9-26') schedules a 9:00 AM work session at 8220 Loop Road. The agenda header reads 'Friday, October 8th, 2026', but October 8, 2026 is a Thursday; the file name and notice title both indicate Friday, October 9, so the header date appears to be a typo. Old business repeats the prior weeks: proposed noise ordinance wording from outside consultants, still described as awaiting changes; a data center concerns list progress update; and the Battery Energy Storage System (BESS) Ordinance. New business lists the meeting location for October 23 and October 30, a 'Call with National Grid', and continuing the environmental concerns discussion, which is also the stated topic of the next meeting. No presentation deck was posted with this agenda, and no committee minutes have been located.

Proposed edit

Add the October 9, 2026 DCAC work session to the local timeline, noting the agenda's scheduled call with National Grid and the planned October 23 and October 30 sessions, and flag the header-date discrepancy rather than resolving it.

Critic findings against this item (2)

no-absence-as-proofThe summary flatly says 'No presentation deck was posted with this agenda,' yet entries 0-2 cite a 24-page deck for this same October 9 meeting (10-9-26_pp_0.pdf, created October 9, 2026). The absence of a deck at review time is phrased as a definitive fact, and the draft itself contradicts it. Reword to 'no deck had been located when the agenda was reviewed', or remove it given the deck now exists.
no-fabrication'posted October 8, 2026' (also used as source_date) and 'linked from the town home page as 'Data Center Advisory Committee Meeting 10-9-26'' are posting and provenance facts that the agenda PDF at source_url would not plausibly contain. The PDF's own header reads 'Friday, October 8th, 2026', which the summary itself treats as a typo. Cite the home page or PDF metadata for the posting date, or remove it.

The 24-page presentation deck for the Lysander Data Center Advisory Committee's October 2, 2026 meeting, titled 'Environmental Concerns' (PDF created October 2, 2026), takes up light pollution, heat dissipation and site space. It recommends: updating town code to eliminate what it calls the 'ghost parking' loophole, under which unpaved reserved parking does not count toward the 30 percent site-coverage limit; requiring parking built to the industrial/manufacturing standard (1 space per 500 square feet rather than the warehouse standard of 1 per 4,000) to preserve adaptive reuse; adopting a separate Dark Sky lighting code for commercial and industrial users, including shielding, inward- and downward-facing perimeter lighting on its own circuit, and outdoor lighting off after 10 pm or within an hour of closing; requiring a heat dissipation study specific to the proposed cooling system; mandating green or high-albedo roofing; mandating strict cooling-system setbacks from property lines and wetland boundaries; establishing heat-differential standards with periodic monitoring; requiring deep, bedrock-level loops for geothermal systems; and requiring rooftop parapet thermal screening walls for air-cooled systems. The deck states that the planning board typically requires full SEQRA review for a project of this size, that DEC is responsible for water and air quality and for protecting the Three Rivers Wildlife Management Area and the Seneca River, that OCWA manages water and WEP wastewater for the site, and that the town can manage noise, light pollution, runoff and some heat discharge. It also notes that proposed state 'Dark Skies' bills (A4615, S9637) have not passed. These are committee recommendations presented at a work session, not adopted town code.

Proposed edit

Record the committee's environmental recommendations - ghost-parking loophole closure, industrial parking standard, a Dark Sky lighting code, heat dissipation study and heat-differential monitoring, high-albedo or green roofing, cooling-system setbacks and geothermal and air-cooling controls - as proposed local controls under development, clearly distinguished from enacted code, alongside the deck's own statement of the division of authority between the town, DEC, OCWA and WEP.

Critic findings against this item (1)

evidence-label-accuracyLabeled 'verified', but the closing sentence says 'These are committee recommendations presented at a work session.' The cited source is a posted PDF deck (dcac_pp_enviro10-02-26.pdf). It shows the deck was prepared for the October 2 meeting. It does not show that the deck was actually presented. The companion entry 5 says outright that the October 2 agenda 'does not show that the meeting took place,' and no minutes are cited. Rephrase to 'prepared for' or 'posted with' the October 2 work session, or cite minutes.

evidence-label-accuracyLabeled 'verified', but it says 'These are committee recommendations and the deck's own technology characterizations presented at a work session.' The source is only the posted deck (lysander_dc_committee_electricity_usage_09-25-26.pdf). Entry 9 says minutes confirming that the September 25 session took place 'were not located in the reviewed record.' The claim that the deck was presented is not directly supported. Use 'posted with' or 'prepared for' the September 25 work session.

Source · 2026-09-25 ↗

estimated No objection filed 2026-10-07

town-of-lysander-official-records

The September 25 deck again refers to what it calls a 270 MW data center without saying whether 270 MW is requested interconnection capacity, service capacity, or critical IT load. The deck ties only two figures explicitly to that load: about 4 acres for a lithium iron phosphate BESS 'for 270MW backup system', and 108 linear-generator units 'required for a 270 MW data center', which it says would produce about 85 decibels and occupy 17 acres. It also lists footprints with no stated load basis: 1 to 2 acres for nickel manganese cobalt, about 6 acres for sodium-ion, 4 to 5 acres for nickel-hydrogen, about 25 acres for flow batteries, 3 to 5 acres for solid oxide fuel cells, 6 to 8 acres for molten carbonate and about 40 acres for proton exchange membrane fuel cells; whether those also assume 270 MW is not stated. These are the committee's own approximations, not vendor quotes, a developer submission or measurements; the 85-decibel figure is given without a stated distance or weighting.

Proposed edit

If the footprint and noise figures are used, present them as the committee's own approximations, tie only the lithium iron phosphate and linear-generator figures to the 270 MW hypothetical, state that the other acreages carry no stated load basis, and flag that the 85-decibel figure has no stated distance or weighting.

Held only because another item in the 2026-10-07 batch was flagged. Nothing was filed against this one.

Source · 2026-09-25 ↗

verified No objection filed 2026-10-07

town-of-lysander-official-records

The Lysander Data Center Advisory Committee agenda for Friday, September 18, 2026 at 9:00 AM at 8220 Loop Road schedules a work session. Under old business the agenda lists proposed noise ordinance wording from outside consultants, described as awaiting changes; a data center concerns list progress update; and the Battery Energy Storage System ordinance. Under new business it lists a continuation of the electricity discussion and a new topic, generators and turbines. The agenda states the next meeting will continue the electricity discussion. No applicant, named project, or Community Benefit Agreement action appears on this agenda. The agenda shows the session was scheduled; minutes confirming it took place were not located in the reviewed record.

Proposed edit

Add the September 18, 2026 Data Center Advisory Committee work session to the local-process timeline as scheduled, noting that the consultant-drafted noise ordinance language is awaiting changes and that generators and turbines entered the committee's agenda as a new business item.

Held only because another item in the 2026-10-07 batch was flagged. Nothing was filed against this one.

Source · 2026-09-18 ↗

verified Critic flagged 2026-10-07

town-of-lysander-official-records

The presentation deck accompanying the September 18, 2026 meeting sets out the committee's recommendations on on-site backup generation. It recommends allowing only natural gas or bi-fuel generators for emergency backup power, on the stated grounds that these are the two quietest options, eliminate or greatly reduce on-site diesel storage, produce far fewer greenhouse gas, carbon and soot emissions than diesel, and avoid the high-pitched whine of turbines; an immediate shutdown trigger if bi-fuel units fall below 70 percent natural gas utilization during a test; that generators be allowed only for backup power during an outage with no behind-the-meter use of generators or turbines; that a full environmental impact study addressing noise and environmental issues precede any approval; that scheduled inspections by a certified third party be required; that testing be confined to specified weekday daytime hours with caps on units tested at once and on annual testing hours; that a separate decommissioning bond be posted for generator farms; and that generator farms be defined as a special use requiring separate review and permit. The deck also records the division of authority: the town has no say in power delivery or rates, NYISO operates the high-voltage grid and sets supply charges while the PSC sets delivery charges and service classifications, and while DEC regulates generator emissions, fuel types and fuel storage, the town can regulate generator size, operating hours outside emergencies, setbacks and noise through code and can designate on-site or behind-the-meter generation above a threshold (the deck suggests 5 MW) as a separate or prohibited land use. These are committee recommendations presented at a work session, not adopted town code.

Proposed edit

Record the committee's on-site generation recommendations - natural gas or bi-fuel only, backup-only with no behind-the-meter generation, special-use permitting, decommissioning bond and testing-hour limits - as proposed local controls under development, clearly distinguished from enacted code, alongside the deck's own statement of the division of authority between the town, DEC, NYISO and the PSC.

Critic findings against this item (1)

evidence-label-accuracyLabeled 'verified', but it says 'These are committee recommendations presented at a work session.' The source is only the posted deck (dcac_pp_electricity_09-18-26.pdf). Entry 12 says minutes confirming that the September 18 session took place 'were not located in the reviewed record.' Saying the recommendations were presented goes beyond what the source shows. Rephrase to 'accompanying' or 'prepared for' the scheduled session.

Source · 2026-10-02 ↗

estimated Critic flagged 2026-10-06

town-of-lysander-official-records

The October 2, 2026 deck includes a site-space table for a hypothetical 124-acre site with 30 percent buildable coverage (37.20 acres), comparing three two-story buildings with one tall building under industrial and warehouse parking standards. Fixed allocations in every scenario are 5.50 acres for a generator farm, 2.75 for a substation, 1.75 for a switch yard, 6.00 for battery storage and 1.00 for gas regulation. Under the industrial parking standard, the table shows 17.90 acres of parking and a data center footprint of 13.80 acres for the three-building layout, leaving -14.90 acres (over the coverage limit), and 10.70 acres of parking with a 5.50-acre footprint for the one-building layout, leaving 0.80 acres. Under the warehouse standard, the same layouts leave 0.80 and 10.20 acres. The deck also gives parking-space ranges of 1,440 to 2,400 (industrial) and 180 to 300 (warehouse). The deck does not name the site or state the building floor area or load behind these figures; they are the committee's own planning approximations, not a developer submission, site plan or survey.

Proposed edit

If the site-space comparison is used, present it as the committee's own approximation for an unnamed hypothetical 124-acre site, showing that the three-building industrial-parking layout exceeds the 30 percent coverage limit in the committee's own arithmetic, without attributing the figures to any applicant.

Critic findings against this item (1)

no-fabricationThe summary says 'Fixed allocations in every scenario are 5.50 acres for a generator farm, 2.75 for a substation, 1.75 for a switch yard, 6.00 for battery storage and 1.00 for gas regulation', which presents that list as complete. The source table (dcac_pp_enviro10-02-26.pdf, 'Space Restrictions') also has a 'Roads' row: 3.40 acres for the three-building layout and 3.20 for the one-building layout, plus an intermediate 'Remaining space' row (-1.10 / 6.30 industrial; 14.60 / 15.70 warehouse). The roads line is left out, so the summary's own figures don't add up to the outcomes it reports. 37.20 - 17.00 fixed - 17.90 parking - 13.80 footprint = -11.50, not the stated '-14.90'. 37.20 - 17.00 - 10.70 - 5.50 = 4.00, not the stated '0.80'. Each figure is printed in the source, but the arithmetic the summary implies does not trace to it. Fix: add the Roads allocation (3.40 / 3.20 acres) and stop calling the five listed items the full fixed set, or say that roads are also deducted.

Source · 2026-09-25 ↗

estimated Critic flagged 2026-10-05

town-of-lysander-official-records

The September 25 deck again refers to what it calls a 270 MW data center without saying whether 270 MW is requested interconnection capacity, service capacity, or critical IT load. The deck ties only two figures explicitly to that load: about 4 acres for a lithium iron phosphate BESS 'for 270MW backup system', and 108 linear-generator units 'required for a 270 MW data center', which it says would produce about 85 decibels and occupy 17 acres. It also lists footprints with no stated load basis: 1 to 2 acres for nickel manganese cobalt, about 6 acres for sodium-ion, 4 to 5 acres for nickel-hydrogen, about 25 acres for flow batteries, 3 to 5 acres for solid oxide fuel cells, 6 to 8 acres for molten carbonate and about 40 acres for proton exchange membrane fuel cells; whether those also assume 270 MW is not stated. These are the committee's own approximations, not vendor quotes, a developer submission or measurements; the 85-decibel figure is given without a stated distance or weighting.

Proposed edit

If the footprint and noise figures are used, present them as the committee's own approximations, tie only the lithium iron phosphate and linear-generator figures to the 270 MW hypothetical, state that the other acreages carry no stated load basis, and flag that the 85-decibel figure has no stated distance or weighting.

Critic findings against this item (1)

no-fabricationThe summary says the deck ties 108 linear-generator units 'required for a 270 MW data center' to about 85 decibels 'and occupy 17 acres', and lists the linear-generator figures as one of 'only two figures' explicitly tied to 270 MW. In the source PDF (lysander_dc_committee_electricity_usage_09-25-26.pdf), 'Requires 17 acres' is a standalone CON bullet on the Linear Generators slide with no load stated. The 108 units / 270 MW / ~85 decibels sentence is on the separate 'Fuel Cell Issues' slide and says nothing about acreage. So the link between 17 acres and the 270 MW / 108-unit figure is the drafter's inference, not something the deck says. That is the same blurring of load basis this entry claims to avoid. The proposed_change would carry the error forward by tying 'the linear-generator figures' (including 17 acres) to the 270 MW hypothetical. Fix: list 17 acres with the other figures that have no stated load basis, and tie only the 4-acre LFP BESS figure and the 108-unit / ~85 dB statement to 270 MW.

evidence-label-accuracyThe summary is labeled 'verified' and calls the deck's contents 'committee recommendations presented at a work session'. The cited source is the deck PDF itself (PDF created October 2, 2026), and a PDF doesn't show that it was presented. Entry 5's companion agenda for the same October 2 session says the agenda 'does not show that the meeting took place.' Saying the deck was 'presented' asserts something the cited record doesn't support. It should read 'posted for' or 'prepared for' the work session.

Source · 2026-10-02 ↗

estimated Critic flagged 2026-10-04

town-of-lysander-official-records

The October 2, 2026 deck includes a site-space table for a hypothetical 124-acre site with 30 percent buildable coverage (37.20 acres), comparing three two-story buildings with one tall building under industrial and warehouse parking standards. Fixed allocations in every scenario are 5.50 acres for a generator farm, 2.75 for a substation, 1.75 for a switch yard, 6.00 for battery storage and 1.00 for gas regulation. Under the industrial parking standard, the table shows 17.90 acres of parking and a data center footprint of 13.80 acres for the three-building layout, leaving -14.90 acres (over the coverage limit), and 10.70 acres of parking with a 5.50-acre footprint for the one-building layout, leaving 0.80 acres. Under the warehouse standard, the same layouts leave 0.80 and 10.20 acres. The deck also gives parking-space ranges of 1,440 to 2,400 (industrial) and 180 to 300 (warehouse). The deck does not name the site or state the building floor area or load behind these figures; they are the committee's own planning approximations, not a developer submission, site plan or survey.

Proposed edit

If the site-space comparison is used, present it as the committee's own approximation for an unnamed hypothetical 124-acre site, showing that the three-building industrial-parking layout exceeds the 30 percent coverage limit in the committee's own arithmetic, without attributing the figures to any applicant.

Critic findings against this item (1)

no-fabricationThe figures quoted in the summary don't add up, and the summary doesn't say why. Buildable coverage is 37.20 acres and the fixed allocations listed total 17.00 acres (5.50 generator farm + 2.75 substation + 1.75 switch yard + 6.00 battery storage + 1.00 gas regulation), which leaves 20.20 acres. The industrial three-building case (17.90 parking + 13.80 footprint) would then leave -11.50 acres, not the stated -14.90. The industrial one-building case (10.70 + 5.50) would leave 4.00 acres, not the stated 0.80. The two gaps (3.40 and 3.20 acres) differ, so a single missing allocation can't explain them. One of three things is true: the figures were transcribed wrong, the deck has another allocation the summary leaves out, or the deck's own arithmetic is inconsistent. Entry 14 flags the same kind of problem for its turbine totals; this entry presents the figures as-is. The -14.90, 0.80 and 10.20 acre remainders need checking against the deck PDF. Any inconsistency should be stated explicitly before the proposed_change's claim about 'the committee's own arithmetic' is published.

Source · 2026-09-25 ↗

verified Critic flagged 2026-10-04

town-of-lysander-official-records

The 31-page presentation deck posted with the September 25, 2026 meeting (PDF created September 25, 2026) adds battery storage and fuel-cell material to the committee's electricity series. It recommends approving sodium-ion or nickel-hydrogen battery energy storage systems but not lithium-ion systems, citing no thermal-runaway risk, no cooling fans and better winter performance, and recommends that any generators be required to operate with an adequately sized BESS, on the stated grounds that this reduces generator testing time and cycles, the number of generators, noise, air pollution and fuel storage. On fuel cells it recommends waiting until hydrogen blending by the utility is a reality before allowing fuel cells as a behind-the-meter power source; after that, requiring carbon scrubbers for behind-the-meter use, preferring solid oxide fuel cells over generators for new builds, using fuel-cell waste heat to cool the data center through absorption chillers and a closed-loop cooling system, and pairing solid oxide fuel cells with a sodium-ion BESS. The deck states that natural-gas-fueled fuel cells do not meet New York clean energy guidelines because of CO2 emissions, and that only proton exchange membrane fuel cells and linear generators could serve as backup power, neither of which it considers suitable for the site. These are committee recommendations and the deck's own technology characterizations presented at a work session, not adopted town code.

Proposed edit

Record the committee's battery storage and fuel-cell recommendations - sodium-ion or nickel-hydrogen BESS only, no lithium-ion, generators paired with BESS, and fuel cells deferred until hydrogen blending exists - as proposed local controls under development, clearly distinguished from enacted code.

Critic findings against this item (1)

evidence-label-accuracySame problem as entry 0. The summary says the battery storage and fuel-cell recommendations were 'presented at a work session' and is labeled 'verified'. The source is the deck PDF 'posted with the September 25, 2026 meeting', and entry 9 says minutes confirming the September 25 session took place 'were not located in the reviewed record.' Saying the deck was presented goes beyond what the cited document shows.

Source · 2026-09-25 ↗

estimated No objection filed 2026-10-04

town-of-lysander-official-records

The September 25 deck again refers to what it calls a 270 MW data center without saying whether 270 MW is requested interconnection capacity, service capacity, or critical IT load. The deck ties only two figures explicitly to that load: about 4 acres for a lithium iron phosphate BESS 'for 270MW backup system', and 108 linear-generator units 'required for a 270 MW data center', which it says would produce about 85 decibels and occupy 17 acres. It also lists footprints with no stated load basis: 1 to 2 acres for nickel manganese cobalt, about 6 acres for sodium-ion, 4 to 5 acres for nickel-hydrogen, about 25 acres for flow batteries, 3 to 5 acres for solid oxide fuel cells, 6 to 8 acres for molten carbonate and about 40 acres for proton exchange membrane fuel cells; whether those also assume 270 MW is not stated. These are the committee's own approximations, not vendor quotes, a developer submission or measurements; the 85-decibel figure is given without a stated distance or weighting.

Proposed edit

If the footprint and noise figures are used, present them as the committee's own approximations, tie only the lithium iron phosphate and linear-generator figures to the 270 MW hypothetical, state that the other acreages carry no stated load basis, and flag that the 85-decibel figure has no stated distance or weighting.

Held only because another item in the 2026-10-04 batch was flagged. Nothing was filed against this one.

Source · 2026-09-25 ↗

verified No objection filed 2026-10-04

town-of-lysander-official-records

The Lysander Data Center Advisory Committee agenda for Friday, September 18, 2026 at 9:00 AM at 8220 Loop Road schedules a work session. Under old business the agenda lists proposed noise ordinance wording from outside consultants, described as awaiting changes; a data center concerns list progress update; and the Battery Energy Storage System ordinance. Under new business it lists a continuation of the electricity discussion and a new topic, generators and turbines. The agenda states the next meeting will continue the electricity discussion. No applicant, named project, or Community Benefit Agreement action appears on this agenda. The agenda shows the session was scheduled; minutes confirming it took place were not located in the reviewed record.

Proposed edit

Add the September 18, 2026 Data Center Advisory Committee work session to the local-process timeline as scheduled, noting that the consultant-drafted noise ordinance language is awaiting changes and that generators and turbines entered the committee's agenda as a new business item.

Held only because another item in the 2026-10-04 batch was flagged. Nothing was filed against this one.

Source · 2026-09-18 ↗

verified Critic flagged 2026-10-04

town-of-lysander-official-records

The presentation deck accompanying the September 18, 2026 meeting sets out the committee's recommendations on on-site backup generation. It recommends allowing only natural gas or bi-fuel generators for emergency backup power, on the stated grounds that these are the two quietest options, eliminate or greatly reduce on-site diesel storage, produce far fewer greenhouse gas, carbon and soot emissions than diesel, and avoid the high-pitched whine of turbines; an immediate shutdown trigger if bi-fuel units fall below 70 percent natural gas utilization during a test; that generators be allowed only for backup power during an outage with no behind-the-meter use of generators or turbines; that a full environmental impact study addressing noise and environmental issues precede any approval; that scheduled inspections by a certified third party be required; that testing be confined to specified weekday daytime hours with caps on units tested at once and on annual testing hours; that a separate decommissioning bond be posted for generator farms; and that generator farms be defined as a special use requiring separate review and permit. The deck also records the division of authority: the town has no say in power delivery or rates, NYISO operates the high-voltage grid and sets supply charges while the PSC sets delivery charges and service classifications, and while DEC regulates generator emissions, fuel types and fuel storage, the town can regulate generator size, operating hours outside emergencies, setbacks and noise through code and can designate on-site or behind-the-meter generation above a threshold (the deck suggests 5 MW) as a separate or prohibited land use. These are committee recommendations presented at a work session, not adopted town code.

Proposed edit

Record the committee's on-site generation recommendations - natural gas or bi-fuel only, backup-only with no behind-the-meter generation, special-use permitting, decommissioning bond and testing-hour limits - as proposed local controls under development, clearly distinguished from enacted code, alongside the deck's own statement of the division of authority between the town, DEC, NYISO and the PSC.

Critic findings against this item (1)

evidence-label-accuracySame problem as entries 0 and 10. The summary closes with 'committee recommendations presented at a work session' under a 'verified' label. The source is the September 18 deck PDF, and entry 12 says minutes confirming the September 18 session took place 'were not located in the reviewed record.' It should say the deck was prepared or posted for the session, not presented.

The Lysander Town Board agenda for Thursday, October 1, 2026 (work session 5:30 PM, regular meeting 6:30 PM, 8220 Loop Road) lists 'Data Center Moratorium' as a work-session topic. Agenda item G is a proposed motion authorizing the Town Clerk to advertise a public hearing before the Town Board at 6:30 PM on Thursday, November 5, 2026 'to extend the moratorium on data centers in the Town of Lysander,' and states 'This moratorium will be extended to April 1, 2027.' The mover and seconder lines are blank. The cited file is a revised agenda (PDF created October 1, 2026) that replaces a September 30 version; the revision adds unrelated appointment and surplus items and leaves the moratorium wording unchanged. An agenda shows only what was proposed for the meeting; it does not show that the motion passed, and an extension would require its own hearing and Town Board action. The agenda does not state the current moratorium's expiration date.

Proposed edit

Add to the local-process timeline that the October 1, 2026 Town Board agenda proposes scheduling a November 5, 2026 public hearing on extending the Lysander data center moratorium to April 1, 2027, labeled as proposed and not yet acted on.

Critic findings against this item (1)

no-fabricationThe summary says the cited file 'replaces a September 30 version' and that 'the revision adds unrelated appointment and surplus items and leaves the moratorium wording unchanged.' The September 30 date and the comparison both depend on an earlier agenda that is not the source_url (10-1-2026_agenda.pdf). A revised PDF does not plausibly contain its own predecessor's date and a diff against it. Either cite the September 30 agenda for that comparison or drop it from this entry.

Source · 2026-10-01 ↗

verified Critic flagged 2026-10-02

town-of-lysander-official-records

The Lysander Data Center Advisory Committee agenda for Friday, October 2, 2026 at 9:00 AM at 8220 Loop Road (PDF created October 1, 2026) schedules a work session. Old business repeats the prior two weeks: proposed noise ordinance wording from outside consultants, still described as awaiting changes; a data center concerns list progress update; and the Battery Energy Storage System (BESS) ordinance. New business is 'Begin Environmental Concerns Discussion,' and the next meeting is listed as continuing that discussion. Unlike the September 18 and 25 agendas, no electricity item appears. No applicant, named project, or Community Benefit Agreement action appears on the agenda. The agenda shows the session was scheduled; minutes confirming it took place were not located in the reviewed record, and no presentation deck for this meeting was posted as of this pass.

Proposed edit

Add the October 2, 2026 Data Center Advisory Committee work session to the local-process timeline as scheduled, noting that the committee moves from electricity to environmental concerns and that the noise ordinance language is still awaiting changes.

Critic findings against this item (1)

no-fabricationThe summary says 'Old business repeats the prior two weeks' and 'Unlike the September 18 and 25 agendas, no electricity item appears.' Those dates and the comparison come from other agendas (9-18_dcac_agenda.pdf, dcac_agenda_09-25-26.pdf), not from the cited dcac_agenda_10-02-26.pdf. Also, 'no presentation deck for this meeting was posted as of this pass' is an observation about the website, not something the agenda PDF says. Attribute the comparison to the earlier agendas or remove it.

Source · 2026-10-02 ↗

verified Critic flagged 2026-10-02

nysdec-micron-permit-dashboard

NYSDEC issued a new Article 24 freshwater wetlands permit to Micron, Permit ID 7-3124-00575/00016, effective August 12, 2026 with an expiration date of December 11, 2035. The permit authorizes 0.05 acres of permanent impacts to New York State regulated freshwater wetlands and associated adjacent area for construction of a rail siding track with a 70-rail-car storage capacity running parallel to the CSX Railway mainline, and for a parallel access roadway, in the Town of Clay. The permit is linked from the DEC Micron dashboard, which earlier passes recorded with July 30, 2026 as its latest action.

Proposed edit

Add the August 12, 2026 rail-siding freshwater wetlands permit (0.05 acres, 7-3124-00575/00016) to the Micron permit table, cited to the permit PDF.

Critic findings against this item (1)

no-fabricationThe summary says the permit 'is linked from the DEC Micron dashboard, which earlier passes recorded with July 30, 2026 as its latest action.' The July 30, 2026 date and the dashboard-linkage claim come from the DEC dashboard page and earlier pipeline runs, not from the cited permit PDF (micronrailpermitwetlands.pdf). Cite the dashboard for that fact or drop it.

Source · 2026-08-12 ↗

verified No objection filed 2026-10-02

nysdec-micron-permit-dashboard

Modification 2 to Micron's Section 401 Water Quality Certification, Permit ID 7-3124-00575/00007, is effective August 12, 2026 and authorizes 0.05 acres of additional fill within federally regulated wetlands for the same rail siding and parallel access roadway. The modified certification lists the original certification effective December 12, 2025, Modification 1 effective August 10, 2026 and Modification 2 effective August 12, 2026, all expiring December 11, 2045. Its authorized-activity text states permanent impacts of 176.44 acres of state-regulated freshwater wetlands, 195.05 acres of federally regulated wetlands and 6,283 linear feet of federally jurisdictional streams, and restoration and enhancement of 395.39 acres of wetlands across six mitigation sites with 14,448 linear feet of stream work. The document does not separate how much of those totals predates Modification 2 beyond the stated 0.05 acres.

Proposed edit

Add water quality certification Modification 2 (August 12, 2026, 0.05 acres of additional federally regulated wetland fill for the rail siding) to the Micron permit table, and if the cumulative impact totals are shown, cite them to this certification PDF.

Held only because another item in the 2026-10-02 batch was flagged. Nothing was filed against this one.

Source · 2026-08-12 ↗

verified Critic flagged 2026-10-02

nysdec-micron-permit-dashboard

Modification 1 to the Buxton Creek wetland mitigation permit, Permit ID 7-3554-00274/00001, issued to Micron and The Wetland Trust, Inc., is effective August 10, 2026 (expiration December 11, 2035) and authorizes a grading plan adjustment to the layout of core trenches and ditch plug changes at the mitigation site; the incorporated plans include a 'Proposed Core Trench Addition' figure dated June 23, 2026. A matching Modification 1 to the Section 401 Water Quality Certification, 7-3124-00575/00007, also effective August 10, 2026, approves the same grading plan adjustment at the Buxton Creek site.

Proposed edit

Add the August 10, 2026 Buxton Creek mitigation grading-plan modification to the Micron permit table, cited to the modification PDF, noting the parallel water quality certification Modification 1.

Critic findings against this item (1)

no-fabricationThe summary's second sentence says 'A matching Modification 1 to the Section 401 Water Quality Certification, 7-3124-00575/00007, also effective August 10, 2026, approves the same grading plan adjustment.' That is a separate DEC document. Nothing indicates the cited Buxton Creek wetland permit PDF (micronbuxtoncreekwetlandmod1.pdf) contains the WQC Modification 1 permit ID, effective date, or approval scope. Change 3 sources the WQC modification history to micronrailwaterqualitymod2.pdf instead. Cite that document for this sentence or remove it. Since this is unclear, it resolves toward hold.

Source · 2026-09-28 ↗

verified Critic flagged 2026-10-01

lysander-town-board-minutes

The Lysander Town Board agenda for Thursday, October 1, 2026 (work session 5:30 PM, regular meeting 6:30 PM, 8220 Loop Road) lists 'Data Center Moratorium' as a work-session topic. Agenda item G is a proposed motion authorizing the Town Clerk to advertise a public hearing before the Town Board at 6:30 PM on Thursday, November 5, 2026 'to extend the moratorium on data centers in the Town of Lysander,' and states 'This moratorium will be extended to April 1, 2027.' The mover and seconder lines are blank. An agenda shows only what was proposed for the meeting; it does not show that the motion passed, and an extension would require its own hearing and Town Board action. The agenda does not state the current moratorium's expiration date, and Local Law No. 4 runs six months from its effective date upon filing with the Secretary of State, a filing date not located in the reviewed record.

Proposed edit

Add to the local-process timeline that the October 1, 2026 Town Board agenda proposes scheduling a November 5, 2026 public hearing on extending the Lysander data center moratorium to April 1, 2027, labeled as proposed and not yet acted on.

Critic findings against this item (1)

no-fabricationThe summary says 'Local Law No. 4 runs six months from its effective date upon filing with the Secretary of State.' The cited source_url, the October 1, 2026 Town Board agenda PDF, does not contain this. A text extraction of the agenda has no 'No. 4', 'six month', 'filing' or 'Secretary of State' string; it only mentions the moratorium in the work-session list and in item G. The law number and six-month term come from a different document, presumably the moratorium local law itself. Either cite that document or drop the sentence.

Source · 2026-10-01 ↗

verified Critic flagged 2026-10-01

nysdec-micron-permit-dashboard

The NYSDEC Micron dashboard now lists three August 2026 permit actions not recorded in earlier passes; the linked PDFs are posted in the September 2026 files folder. (1) A new Article 24 freshwater wetlands permit, 7-3124-00575/00016, effective August 12, 2026 and expiring December 11, 2035, authorizing 0.05 acres of permanent impacts to state-regulated wetlands and adjacent area for a rail siding track with 70-rail-car storage capacity parallel to the CSX mainline, plus a parallel access road. (2) Modification 2 to the Section 401 Water Quality Certification, 7-3124-00575/00007, effective August 12, 2026, authorizing 0.05 acres of additional fill in federally regulated wetlands for the same rail siding; the modified certification's authorized-activity text states permanent impacts of 176.44 acres of state-regulated wetlands, 195.05 acres of federally regulated wetlands and 6,283 linear feet of federally regulated streams. (3) Modification 1 to the Buxton Creek wetland mitigation permit, 7-3554-00274/00001 (Micron and The Wetland Trust, Inc.), effective August 10, 2026, approving a grading-plan adjustment to the layout of core trenches and ditch plugs at the mitigation site; the same change appears as Modification 1 to the water quality certification, also effective August 10, 2026.

Proposed edit

Add the August 2026 DEC actions to the Micron permit table: the new rail-siding wetlands permit (0.05 acres), water quality certification Modification 2 for the rail siding, and the Buxton Creek mitigation grading-plan modification, each with its effective date.

Critic findings against this item (1)

no-fabricationThe source_url is the general NYSDEC Micron dashboard page. The summary takes several specific figures from the linked permit PDFs, which the dashboard page does not contain: the December 11, 2035 expiration date, the '70-rail-car storage capacity', and the Modification 2 authorized-activity totals of '195.05 acres of federally regulated wetlands and 6,283 linear feet of federally regulated streams'. A fetch of the dashboard text found none of 195.05, 6,283 or 2035. 176.44 appears there only on the earlier 00575/00003 Article 24 permit row, not as Modification 2 text. Cite the specific Modification 2 WQC and 00575/00016 permit PDFs, or split the entry so each figure traces to the document that holds it.

no-fabricationThe summary includes dates that do not come from the cited Governor's September 15, 2026 press release: 'that page's metadata records an earlier article:published_time of July 14, 2026 and a modification time of September 18, 2026.' Those dates come from the ESD page's HTML metadata, which belongs to change 8 (esd.ny.gov/communityinvestmentframework), not to this source_url. The caveat itself is reasonable, but under the rule every specific date in the summary has to trace to this entry's source_url. Remove the metadata dates here and point to change 8, or cite the ESD page for them.

no-fabricationThe summary says the deck's diesel storage figures are 'reduced by about two thirds for bi-fuel to 157,500 and 315,000 gallons.' The deck's own numbers work out to a 65% reduction (157,500 = 35% of 450,000; 315,000 = 35% of 900,000), not two thirds (which would give 150,000 and 300,000). The summary doesn't show whether 'about two thirds' is the deck's wording or the drafter's paraphrase. If it's a paraphrase, it misstates the ratio the source uses. Since unclear cases resolve to hold, either quote the deck's stated reduction percentage or drop the 'about two thirds' wording and give only the two gallon figures.

Source · 2026-09-15 ↗

verified Critic flagged 2026-09-30

micron-final-eis-and-appendices

The CHIPS Program Office NEPA page states that the First Amendment to the Micron Programmatic Agreement (the National Historic Preservation Act Section 106 agreement executed December 16, 2025 among the CHIPS Program Office, the U.S. Army Corps of Engineers Buffalo District and the New York State Historic Preservation Office) was completed on September 28, 2026, and posts the 17-page amendment with a revised Appendix 1. The amendment adds the Fish Creek Restoration Area (25PR10312) as a wetland and stream mitigation site tied to the Onondaga County Department of Water Environment Protection industrial wastewater conveyance connected action, with that department as its project sponsor. It also: requires project sponsors to document cultural sensitivity training in biannual reports; provides that approval of a Phase 1B, 2 or 3 archaeological work plan authorizes fieldwork without first completing end-of-field letter review; sets 14-day review periods for end-of-field letters; requires fieldwork results to be reported within six months of fieldwork completion; and adds procedures for construction discoveries with and without adverse effects. The amendment text also states that the telecommunications service project sponsor is still pending selection. The signature pages are not machine-readable, so individual signing dates were not confirmed; the September 28, 2026 completion date is taken from the CHIPS Program Office NEPA page (the source_url), which states 'The First Amendment to the Programmatic Agreement was completed on September 28, 2026'; the amendment's provisions summarized here come from the amendment PDF linked from that page (https://www.nist.gov/system/files/documents/2026/09/28/20260928_First-Amendment-to-Micron-PA_FE_508.pdf).

Proposed edit

Add to the Micron federal-review entry that the CHIPS Program Office NEPA page reports the First Amendment to the Programmatic Agreement was completed September 28, 2026, adding the county's Fish Creek Restoration Area as a mitigation site and revising the archaeological review procedures, cited to the NEPA page with a link to the amendment PDF.

Critic findings against this item (1)

no-fabricationsource_url is the CHIPS Program Office NEPA page (https://www.nist.gov/chips/implementation-strategies/national-environmental-policy-act-nepa-and-chips-act), but most of the specific facts in the summary come from a different document, the amendment PDF (20260928_First-Amendment-to-Micron-PA_FE_508.pdf). These include: the 'executed December 16, 2025' date of the original Programmatic Agreement; the named parties 'U.S. Army Corps of Engineers Buffalo District' and 'New York State Historic Preservation Office'; 'Fish Creek Restoration Area (25PR10312)'; the Onondaga County Department of Water Environment Protection as project sponsor; the '14-day review periods'; the 'within six months of fieldwork completion' reporting deadline; the '17-page' length; and the telecommunications sponsor 'still pending selection'. The rule requires every such fact to trace to source_url, and nothing shows the NEPA page states them itself. The summary says where they came from, but that doesn't meet the single-source_url requirement. Moving source_url to the NEPA page fixed the September 29 finding about the completion date but moved the mismatch onto the amendment provisions. Suggested fix: split into two entries. One entry cites the NEPA page for the September 28, 2026 completion date only. The other cites the amendment PDF for its provisions, parties and the December 16, 2025 date.

Source · 2026-09-15 ↗

verified Critic flagged 2026-09-29

micron-final-eis-and-appendices

The CHIPS Program Office NEPA page states that the First Amendment to the Micron Programmatic Agreement (the National Historic Preservation Act Section 106 agreement executed December 16, 2025 among the CHIPS Program Office, the U.S. Army Corps of Engineers Buffalo District and the New York State Historic Preservation Office) was completed on September 28, 2026, and posts the 17-page amendment with a revised Appendix 1. The amendment adds the Fish Creek Restoration Area (25PR10312) as a wetland and stream mitigation site tied to the Onondaga County Department of Water Environment Protection industrial wastewater conveyance connected action, with that department as its project sponsor. It also: requires project sponsors to document cultural sensitivity training in biannual reports; provides that approval of a Phase 1B, 2 or 3 archaeological work plan authorizes fieldwork without first completing end-of-field letter review; sets 14-day review periods for end-of-field letters; requires fieldwork results to be reported within six months of fieldwork completion; and adds procedures for construction discoveries with and without adverse effects. The amendment text also states that the telecommunications service project sponsor is still pending selection. The signature pages are not machine-readable, so individual signing dates were not confirmed; the completion date comes from the NIST page.

Proposed edit

Add to the Micron federal-review entry that the First Amendment to the Programmatic Agreement was completed September 28, 2026, adding the county's Fish Creek Restoration Area as a mitigation site and revising the archaeological review procedures, with a link to the amendment PDF.

Critic findings against this item (1)

no-fabricationThe summary attributes the key date to a document that is not the cited source_url. It says 'The CHIPS Program Office NEPA page states that the First Amendment ... was completed on September 28, 2026' and ends with 'the completion date comes from the NIST page.' But source_url is the amendment PDF itself (.../20260928_First-Amendment-to-Micron-PA_FE_508.pdf), not the NEPA page. The same summary admits the PDF's signature pages 'are not machine-readable, so individual signing dates were not confirmed.' So the September 28, 2026 completion date, which is also repeated in proposed_change, does not trace to source_url. The only link is the upload path in the PDF's URL, which shows when the file was posted, not when the agreement was completed. Fix: cite the NEPA page URL as the source for the completion date (or add it as a second source), or reword to 'posted September 28, 2026' and back that with the PDF path.

Source · 2026-09-15 ↗

verified Critic flagged 2026-09-27

town-of-lysander-official-records

The Lysander Data Center Advisory Committee agenda posted for Friday, September 25, 2026 at 9:00 AM at 8220 Loop Road schedules a work session. Old business repeats the prior week: proposed noise ordinance wording from outside consultants, still described as awaiting changes; a data center concerns list progress update; and the Battery Energy Storage System (BESS) ordinance. New business lists a continuation of the electricity discussion and a new topic, battery storage and fuel cells. Under next meeting, the agenda lists 'Begin Environmental Concerns Discussion.' No applicant, named project, or Community Benefit Agreement action appears on the agenda. The agenda shows the session was scheduled; no minutes confirming it took place have been posted.

Proposed edit

Add the September 25, 2026 Data Center Advisory Committee work session to the local-process timeline as scheduled, noting battery storage and fuel cells as the new agenda item, the noise ordinance language still awaiting changes, and environmental concerns listed for the next meeting.

Critic findings against this item (1)

no-absence-as-proofThe closing sentence 'no minutes confirming it took place have been posted' says as fact that no minutes exist on the town site. The pass only confirms minutes weren't found, and the meeting was just two days before this pass. Rephrase to 'minutes confirming it took place were not located in the reviewed record.'

Source · 2026-09-25 ↗

verified No objection filed 2026-09-27

town-of-lysander-official-records

The 31-page presentation deck posted with the September 25, 2026 meeting (PDF created September 25, 2026) adds battery storage and fuel-cell material to the committee's electricity series. It recommends approving sodium-ion or nickel-hydrogen battery energy storage systems but not lithium-ion systems, citing no thermal-runaway risk, no cooling fans and better winter performance, and recommends that any generators be required to operate with an adequately sized BESS, on the stated grounds that this reduces generator testing time and cycles, the number of generators, noise, air pollution and fuel storage. On fuel cells it recommends waiting until hydrogen blending by the utility is a reality before allowing fuel cells as a behind-the-meter power source; after that, requiring carbon scrubbers for behind-the-meter use, preferring solid oxide fuel cells over generators for new builds, using fuel-cell waste heat to cool the data center through absorption chillers and a closed-loop cooling system, and pairing solid oxide fuel cells with a sodium-ion BESS. The deck states that natural-gas-fueled fuel cells do not meet New York clean energy guidelines because of CO2 emissions, and that only proton exchange membrane fuel cells and linear generators could serve as backup power, neither of which it considers suitable for the site. These are committee recommendations and the deck's own technology characterizations presented at a work session, not adopted town code.

Proposed edit

Record the committee's battery storage and fuel-cell recommendations - sodium-ion or nickel-hydrogen BESS only, no lithium-ion, generators paired with BESS, and fuel cells deferred until hydrogen blending exists - as proposed local controls under development, clearly distinguished from enacted code.

Held only because another item in the 2026-09-27 batch was flagged. Nothing was filed against this one.

Source · 2026-09-25 ↗

estimated No objection filed 2026-09-27

town-of-lysander-official-records

The September 25 deck again refers to what it calls a 270 MW data center without saying whether 270 MW is requested interconnection capacity, service capacity, or critical IT load. The deck ties only two figures explicitly to that load: about 4 acres for a lithium iron phosphate BESS 'for 270MW backup system', and 108 linear-generator units 'required for a 270 MW data center', which it says would produce about 85 decibels and occupy 17 acres. It also lists footprints with no stated load basis: 1 to 2 acres for nickel manganese cobalt, about 6 acres for sodium-ion, 4 to 5 acres for nickel-hydrogen, about 25 acres for flow batteries, 3 to 5 acres for solid oxide fuel cells, 6 to 8 acres for molten carbonate and about 40 acres for proton exchange membrane fuel cells; whether those also assume 270 MW is not stated. These are the committee's own approximations, not vendor quotes, a developer submission or measurements; the 85-decibel figure is given without a stated distance or weighting.

Proposed edit

If the footprint and noise figures are used, present them as the committee's own approximations, tie only the lithium iron phosphate and linear-generator figures to the 270 MW hypothetical, state that the other acreages carry no stated load basis, and flag that the 85-decibel figure has no stated distance or weighting.

Held only because another item in the 2026-09-27 batch was flagged. Nothing was filed against this one.

Source · 2026-09-25 ↗

verified Critic flagged 2026-09-27

town-of-lysander-official-records

The Lysander Data Center Advisory Committee agenda for Friday, September 18, 2026 at 9:00 AM at 8220 Loop Road schedules a work session. Under old business the agenda lists proposed noise ordinance wording from outside consultants, described as awaiting changes; a data center concerns list progress update; and the Battery Energy Storage System ordinance. Under new business it lists a continuation of the electricity discussion and a new topic, generators and turbines. The agenda states the next meeting will continue the electricity discussion. No applicant, named project, or Community Benefit Agreement action appears on this agenda. The agenda shows the session was scheduled; no minutes confirming it took place have been posted.

Proposed edit

Add the September 18, 2026 Data Center Advisory Committee work session to the local-process timeline as scheduled, noting that the consultant-drafted noise ordinance language is awaiting changes and that generators and turbines entered the committee's agenda as a new business item.

Critic findings against this item (1)

no-absence-as-proofSame problem as entry 0: 'no minutes confirming it took place have been posted' says the minutes don't exist, when they just weren't found. Rephrase to 'were not located in the reviewed record.'

evidence-label-accuracyThe press release directly supports only that the Governor announced the framework on September 15, 2026. The draft goes further, saying it 'dates the framework's public launch to September 15, 2026,' and labels that inference 'verified.' It also calls September 15 'earlier than the September 18 ESD page modification timestamp' but leaves out the article:published_time of 2026-07-14T10:01:46-04:00 recorded in entry 6, which is earlier still. The page may have been a July outline, but nothing in the reviewed record shows that. So 'public launch' is not directly supported, and the proposed change to 'date the framework's publication' to September 15 conflicts with entry 6's metadata. Limit the verified claim to the announcement date, or explain the July 14 timestamp.

Source · 2026-09-15 ↗

verified Critic flagged 2026-09-26

town-of-lysander-official-records

The Lysander Data Center Advisory Committee held a work session on Friday, September 25, 2026 at 9:00 AM at 8220 Loop Road. Old business repeats the prior week: proposed noise ordinance wording from outside consultants, still described as awaiting changes; a data center concerns list progress update; and the Battery Energy Storage System (BESS) ordinance. New business lists a continuation of the electricity discussion and a new topic, battery storage and fuel cells. The agenda states the next meeting will begin the environmental concerns discussion, which indicates the electricity topic is closing. No applicant, named project, or Community Benefit Agreement action appears on the agenda.

Proposed edit

Add the September 25, 2026 Data Center Advisory Committee work session to the local-process timeline, noting battery storage and fuel cells as the new agenda item, the noise ordinance language still awaiting changes, and environmental concerns as the next scheduled topic.

Critic findings against this item (1)

evidence-label-accuracyLabeled 'verified' against a one-page agenda, but two statements go beyond what the agenda directly supports. First, 'held a work session on Friday, September 25' says the meeting took place; the agenda only shows it was scheduled. Second, 'which indicates the electricity topic is closing' is the drafter's inference. The agenda lists 'Continue Electricity Discussion' under new business and 'Begin Environmental Concerns Discussion' under next meeting. It never says the electricity topic is ending. Either rephrase as 'scheduled' and drop the inference, or cite the posted deck for the fact that the meeting happened.

Source · 2026-09-25 ↗

verified No objection filed 2026-09-26

town-of-lysander-official-records

The 31-page presentation deck posted with the September 25, 2026 meeting (PDF created September 25, 2026) adds battery storage and fuel-cell material to the committee's electricity series. It recommends approving sodium-ion or nickel-hydrogen battery energy storage systems but not lithium-ion systems, citing no thermal-runaway risk, no cooling fans and better winter performance, and recommends that any generators be required to operate with an adequately sized BESS, on the stated grounds that this reduces generator testing time and cycles, the number of generators, noise, air pollution and fuel storage. On fuel cells it recommends waiting until hydrogen blending by the utility is a reality before allowing fuel cells as a behind-the-meter power source; after that, requiring carbon scrubbers for behind-the-meter use, preferring solid oxide fuel cells over generators for new builds, using fuel-cell waste heat to cool the data center through absorption chillers and a closed-loop cooling system, and pairing solid oxide fuel cells with a sodium-ion BESS. The deck states that natural-gas-fueled fuel cells do not meet New York clean energy guidelines because of CO2 emissions, and that only proton exchange membrane fuel cells and linear generators could serve as backup power, neither of which it considers suitable for the site. These are committee recommendations and the deck's own technology characterizations presented at a work session, not adopted town code.

Proposed edit

Record the committee's battery storage and fuel-cell recommendations - sodium-ion or nickel-hydrogen BESS only, no lithium-ion, generators paired with BESS, and fuel cells deferred until hydrogen blending exists - as proposed local controls under development, clearly distinguished from enacted code.

Held only because another item in the 2026-09-26 batch was flagged. Nothing was filed against this one.

Source · 2026-09-25 ↗

estimated Critic flagged 2026-09-26

town-of-lysander-official-records

The September 25 deck again works against what it calls a 270 MW data center without saying whether 270 MW is requested interconnection capacity, service capacity, or critical IT load. It states land footprints for a 270 MW backup system or equivalent: about 4 acres for lithium iron phosphate BESS, 1 to 2 acres for nickel manganese cobalt, about 6 acres for sodium-ion, 4 to 5 acres for nickel-hydrogen and about 25 acres for flow batteries; 3 to 5 acres for solid oxide fuel cells, 6 to 8 acres for molten carbonate, about 40 acres plus on-site storage of about a million gallons of liquid hydrogen for proton exchange membrane fuel cells, and 17 acres for linear generators, of which it says 108 units would be required and would produce about 85 decibels. It also states that pairing generators with BESS reduces the number of natural gas generators by about 20 percent and generator testing time and frequency by 50 to 75 percent, and that BESS typically offers 2 to 4 hours of backup. These are the committee's own approximations for a hypothetical load, not vendor quotes, a developer submission or measurements; the 85-decibel figure is given without a stated distance or weighting.

Proposed edit

If the footprint and noise figures are used, present them as the committee's own approximations for an unspecified-capacity-type 270 MW hypothetical, and flag that the 85-decibel linear-generator figure has no stated distance or weighting.

Critic findings against this item (1)

no-fabricationThe summary says the deck 'states land footprints for a 270 MW backup system or equivalent' and then lists every technology's acreage. The 09-25 deck ties 270 MW to only two figures: lithium iron phosphate ('about 4 acres for 270MW backup system') and linear generators ('108 units required for a 270 MW data center'). The other figures carry no stated load basis in the deck: NMC '1-2 acres', sodium-ion 'about 6 acres', nickel-hydrogen '4-5 acres', flow '25 acres', SOFC '3-5 acres', MCFC '6-8 acres' and PEM '40 acres'. Tying all of them to 270 MW is the drafter's extrapolation, not something the source says.

Source · 2026-09-25 ↗

verified Critic flagged 2026-09-26

town-of-lysander-official-records

The Lysander Data Center Advisory Committee held a work session on Friday, September 18, 2026 at 9:00 AM at 8220 Loop Road. Under old business the agenda lists proposed noise ordinance wording from outside consultants, described as awaiting changes; a data center concerns list progress update; and the Battery Energy Storage System ordinance. Under new business it lists a continuation of the electricity discussion and a new topic, generators and turbines. The agenda states the next meeting will continue the electricity discussion. No applicant, named project, or Community Benefit Agreement action appears on this agenda.

Proposed edit

Add the September 18, 2026 Data Center Advisory Committee work session to the local-process timeline, noting that the consultant-drafted noise ordinance language is awaiting changes and that generators and turbines entered the committee's agenda as a new business item.

Critic findings against this item (1)

evidence-label-accuracy'held a work session on Friday, September 18, 2026' is labeled 'verified', but the source_url is the agenda (9-18_dcac_agenda.pdf). An agenda shows a meeting was scheduled, not that it took place. Say 'scheduled', or cite a record that shows the meeting happened.

no-fabricationThe summary says the Ithaca Voice article 'notes the Governor opted to issue Executive Order 62 in July 2026 instead of signing the bill.' The article says 'Hochul opted to issue an executive order instead of signing the bill' and separately 'In July, Hochul issued a one-year moratorium.' It never names the order as Executive Order 62. The order number does not trace to source_url.
evidence-label-accuracy'reported' is defined as a statement by a named applicant, company or official. Here the December 31 deadline and the pocket-veto claim ('Hochul has until Dec. 31 to sign or veto... If Hochul doesn't act, the bill won't become law') are the reporter's own assertions, not attributed to any official. The summary itself says no primary document was located. The label does not fit its definition, and ambiguity resolves toward hold. Either attribute the claim to a named official, find a primary record of the deadline, or reconsider the label.

Source · 2026-08-31 ↗

reported Critic flagged 2026-09-26

terawulf-q1-2026-investor-presentation

TeraWulf's second-quarter 2026 earnings release and investor presentation, furnished as Exhibits 99.1 and 99.2 to an SEC Form 8-K filed August 5, 2026, update the company's description of Lake Hawkeye in Lansing, New York. The release describes the site as 'a longer-term redevelopment opportunity' of approximately 183 leased acres at a former industrial site with existing electrical infrastructure, and states that, subject to permitting and site development, it has the potential to support approximately 400 MW of gross capacity, or approximately 320 MW of critical IT load, 'with operations not currently contemplated until approximately 2029.' The presentation lists Lake Hawkeye among pipeline sites, not contracted sites, with about 320 MW of critical IT delivery shown against 2029, and its funding appendix shows Lake Hawkeye's financing as TBD. The capacity figures match the tracked Q1 2026 deck; the new facts are the approximately 2029 operations timing and the longer-term framing. These are company statements of intent, not permits or approvals. The Q1 deck's site-plan-review status is not restated in the Q2 text that was read.

Proposed edit

Add to the Lake Hawkeye entry that TeraWulf's August 5, 2026 second-quarter materials describe it as a longer-term redevelopment opportunity with operations not contemplated until approximately 2029, still uncontracted, labeled as company-reported.

Critic findings against this item (1)

no-fabricationThe source_url is the Exhibit 99.1 earnings release only (a_wulfearningsreleaseq22026.htm). Several facts in the summary are not in it. The release contains no 'pipeline' language, no 'TBD' funding, and no 2029 delivery chart. Those claims ('lists Lake Hawkeye among pipeline sites, not contracted sites', 'about 320 MW of critical IT delivery shown against 2029', 'funding appendix shows Lake Hawkeye's financing as TBD') come from the Exhibit 99.2 investor presentation, which is not the cited source. 'in Lansing, New York' also does not appear in the release text. Cite the 99.2 exhibit URL for the presentation facts, or remove them. The proposed_change's 'still uncontracted' also relies on the presentation.

Source · 2026-08-05 ↗

verified No objection filed 2026-09-25

town-of-lysander-official-records

The Lysander Data Center Advisory Committee held a work session on Friday, September 18, 2026 at 9:00 AM at 8220 Loop Road. Under old business the agenda lists proposed noise ordinance wording from outside consultants, described as awaiting changes; a data center concerns list progress update; and the Battery Energy Storage System ordinance. Under new business it lists a continuation of the electricity discussion and a new topic, generators and turbines. The agenda states the next meeting will continue the electricity discussion. No applicant, named project, or Community Benefit Agreement action appears on this agenda.

Proposed edit

Add the September 18, 2026 Data Center Advisory Committee work session to the local-process timeline, noting that the consultant-drafted noise ordinance language is awaiting changes and that generators and turbines entered the committee's agenda as a new business item.

Held only because another item in the 2026-09-25 batch was flagged. Nothing was filed against this one.

Source · 2026-09-18 ↗

verified No objection filed 2026-09-25

town-of-lysander-official-records

The presentation deck accompanying the September 18, 2026 meeting sets out the committee's recommendations on on-site backup generation. It recommends allowing only natural gas or bi-fuel generators for emergency backup power, on the stated grounds that these are the two quietest options, eliminate or greatly reduce on-site diesel storage, produce far fewer greenhouse gas, carbon and soot emissions than diesel, and avoid the high-pitched whine of turbines; an immediate shutdown trigger if bi-fuel units fall below 70 percent natural gas utilization during a test; that generators be allowed only for backup power during an outage with no behind-the-meter use of generators or turbines; that a full environmental impact study addressing noise and environmental issues precede any approval; that scheduled inspections by a certified third party be required; that testing be confined to specified weekday daytime hours with caps on units tested at once and on annual testing hours; that a separate decommissioning bond be posted for generator farms; and that generator farms be defined as a special use requiring separate review and permit. The deck also records the division of authority: the town has no say in power delivery or rates, NYISO operates the high-voltage grid and sets supply charges while the PSC sets delivery charges and service classifications, and while DEC regulates generator emissions, fuel types and fuel storage, the town can regulate generator size, operating hours outside emergencies, setbacks and noise through code and can designate on-site or behind-the-meter generation above a threshold (the deck suggests 5 MW) as a separate or prohibited land use. These are committee recommendations presented at a work session, not adopted town code.

Proposed edit

Record the committee's on-site generation recommendations - natural gas or bi-fuel only, backup-only with no behind-the-meter generation, special-use permitting, decommissioning bond and testing-hour limits - as proposed local controls under development, clearly distinguished from enacted code, alongside the deck's own statement of the division of authority between the town, DEC, NYISO and the PSC.

Held only because another item in the 2026-09-25 batch was flagged. Nothing was filed against this one.

Source · 2026-09-18 ↗

estimated No objection filed 2026-09-25

town-of-lysander-official-records

The September 18 deck works through backup-generation sizing for what it calls a '270 MW Data Center'; the deck does not say whether 270 MW is requested interconnection capacity, service capacity, or critical IT load. Its table, whose unit counts are labeled as calculated, gives with redundancy roughly 78 to 93 diesel units at 3.25 to 4 MW each, 64 to 118 natural gas units at 2.5 to 5 MW, and 78 bi-fuel units at 4 MW. For natural gas turbines at 34 to 50 MW each, the table lists 5 to 8 calculated units plus 1 redundant unit, but prints the total as 35 to 51; that total does not follow from the table's own columns (5 to 8 plus 1 would be 6 to 9), and the deck's noise table separately uses 58 turbine units, so the turbine totals are internally inconsistent in the source and should not be relied on. On fuel, the deck states that standard industrial backup generators use about 70 gallons of diesel per hour per megawatt, giving about 450,000 gallons for a 24-hour outage at 270 MW and 900,000 gallons for the 48-hour supply it calls industry standard, reduced by about two thirds for bi-fuel to 157,500 and 315,000 gallons. Its noise table estimates property-line levels at a 400-foot setback without mitigation of 73 dBA diesel, 68 natural gas, 69 bi-fuel and 75 turbine, with the deck's caveat that these are dBA only and that dBC levels need further research. All figures are the committee's own calculations against a hypothetical load, not a developer submission, permit application, or measurement.

Proposed edit

Present the committee's diesel, natural gas and bi-fuel unit counts, diesel storage figures and property-line noise estimates as its own calculations for an unspecified-capacity-type 270 MW hypothetical, omit the turbine unit total or flag it as internally inconsistent in the source, and reproduce the dBA-only caveat.

Held only because another item in the 2026-09-25 batch was flagged. Nothing was filed against this one.

Source · 2026-09-18 ↗

verified Critic flagged 2026-09-25

new-york-executive-order-62

Empire State Development has published the Community Investment Framework page. The page states that Executive Order 62 directed Empire State Development to formulate the framework and that the framework delivers on a commitment made through the order. The page offers three documents: CIF Guidance, a CIF Template, and a CIF Template Example prepared for a hypothetical Town of Empire. It sets a recommended community investment benchmark of one million dollars for every megawatt of utility demand associated with a data center project, and organizes commitments under four pillars: establishing good neighbor commitments, enforcing workforce and labor standards, standardizing transparency and accountability, and specifying targeted investments. The page describes the framework as voluntary, a negotiating mechanism for local governments and developers rather than a binding requirement. The page carries no publication date.

Proposed edit

Update the Community Investment Framework entry from 'outline only' to published, listing the guidance, template and worked example, the $1 million per megawatt recommended benchmark and the four pillars, and stating plainly that the framework is voluntary.

Critic findings against this item (2)

no-fabricationThe entry carries source_date "2026-09-23", but its own summary says "The page carries no publication date", and a re-fetch of https://esd.ny.gov/communityinvestmentframework shows no date anywhere in the page text. The draft doesn't say where 2026-09-23 comes from (it isn't this pass's 2026-09-25 retrieval date and isn't a page date), so it can't be traced to source_url. If this goes into the timeline, readers will see a publication date for the CIF that isn't there. Either set source_date to a clearly labeled retrieval/first-observed date, or state that the publication date is unknown. Treated as a hold because it's ambiguous.
distinguish-capacity-typesThe summary gives the benchmark the way the source does: "$1 million for every megawatt of utility demand associated with a data center project", which matches the live page. But proposed_change cuts it to "the $1 million per megawatt recommended benchmark", which drops "of utility demand". The tracked record uses gross MW, critical IT MW and requested capacity side by side (e.g. Lake Hawkeye's ~400 MW gross / ~320 MW critical IT; the Lysander deck's unspecified 270 MW). Without the qualifier, the wiki text could apply the benchmark to the wrong capacity type. proposed_change should keep "per megawatt of utility demand". Treated as a hold because it's ambiguous.

no-fabricationThe summary calls the framework 'the deliverable Executive Order 62 required within 60 days'. The cited source_url (esd.ny.gov/communityinvestmentframework, fetched 2026-09-24) says only that the framework delivers 'on a commitment made through Executive Order No. 62' and that the EO 'directed Empire State Development to formulate' it. The page never mentions a 60-day deadline. That figure comes from the EO 62 text, which is a different source. Everything else checks out against the page and its linked documents: the $1 million per megawatt benchmark, the four named pillars, the word 'voluntary', and the Guidance, Template and Town of Empire Example files (CIFTemplate-TownofEmpireExample.pdf). Fix: cite EO 62 for the 60-day requirement, or drop it. Also, 'published and complete' is the drafter's own judgment; the page does not describe the framework as complete.

Source · 2026-09-23 ↗

verified Critic flagged 2026-09-24

psc-case-26-e-0045-large-load-interconnection

The Commission order that created Case 26-E-0045 was issued and effective February 12, 2026, instituting the proceeding to address large-load interconnection reform. Two forward deadlines appear in its ordering clauses that are absent from the DPS event page tracked so far: Department of Public Service staff shall convene at least one public technical conference before December 31, 2026, and shall prepare a whitepaper addressing the interconnection and related issues considered in the proceeding within one year of the order's issuance, that is by February 12, 2027. The order's own comment dates were April 13, 2026 for initial comments and May 13, 2026 for replies; the tracked event page shows those subsequently extended to May 13 and June 15, 2026, so the extended dates govern the comment phase while the conference and whitepaper deadlines stand as ordered. Re-verified this pass against the order text and unpromoted.

Proposed edit

Add the two ordered Case 26-E-0045 milestones - a DPS technical conference before December 31, 2026 and a DPS staff whitepaper by February 12, 2027 - to the forward calendar, cited to the February 12, 2026 Order Instituting Proceeding rather than to the DPS event page.

Critic findings against this item (1)

no-fabricationThe summary says the comment dates were 'subsequently extended to May 13 and June 15, 2026'. The cited source_url is the February 12, 2026 Order Instituting Proceeding. That order contains only the original April 13 and May 13, 2026 dates; June 15, 2026 appears nowhere in its text. The summary does attribute the extension to 'the tracked event page', but the rule requires every date in the summary to trace to source_url. Fix: cite the DPS event page for the extended dates, or move them into a separate entry. The order does support every other figure in this entry: issued and effective February 12, 2026, a technical conference before December 31, 2026, and a whitepaper within one year.

Source · 2026-02-12 ↗

verified No objection filed 2026-09-24

psc-case-26-e-0045-large-load-interconnection

The same February 12, 2026 order states the scale figure behind the proceeding: as of February 2026, 11.9 gigawatts of load within the New York Independent System Operator interconnection queue were attributed to future large-load projects, and in 2025 alone more than 8.3 gigawatts of new load entered the NYISO queue. The order presents these as the emerging challenge motivating interconnection reform. These are statewide queue figures for large loads generally, not a count of data centers and not specific to any Central New York project, and they should not be combined with any site-level megawatt figure. Re-verified this pass against the order text and unpromoted.

Proposed edit

Record the statewide context figure - 11.9 GW of large-load projects in the NYISO queue as of February 2026, with more than 8.3 GW added during 2025 - as state-level background, explicitly labeled statewide and not tied to a local site.

Held only because another item in the 2026-09-24 batch was flagged. Nothing was filed against this one.

Source · 2026-02-12 ↗

reported Critic flagged 2026-09-24

responsible-data-center-development-act

Press coverage reports that the Governor has until December 31, 2026 to sign or veto the Responsible Data Center Development Act, and that if she does not act the bill will not become law, a pocket veto. The Ithaca Voice states this in an August 31, 2026 article, which also notes the Governor opted to issue Executive Order 62 in July 2026 instead of signing the bill. The nysenate.gov and nyassembly.gov primary records show no action later than June 4, 2026 and do not themselves publish a deadline, so the December 31 date rests on the reporting rather than on a primary document located this pass. Carried forward from prior passes and unpromoted.

Proposed edit

Note on the bill's status entry that press coverage reports a December 31, 2026 deadline for gubernatorial action, after which the bill would be pocket-vetoed, labeled as reported rather than verified against a primary record.

Critic findings against this item (1)

no-fabricationThe summary says 'The nysenate.gov and nyassembly.gov primary records show no action later than June 4, 2026'. The cited source_url is the August 31, 2026 Ithaca Voice article, which does not contain the June 4, 2026 date. The date comes from the legislative records, which are not cited on this entry. The article does support the reported facts, and the 'reported' label is right for them: 'Hochul has until Dec. 31 to sign or veto', the pocket-veto explanation, the choice to issue an executive order instead, and the August 31, 2026 publication date. Fix: cite the nysenate.gov bill page for the June 4 date, or drop it from this entry.

Source · 2026-08-31 ↗

verified No objection filed 2026-09-23

town-of-lysander-official-records

The Lysander Data Center Advisory Committee held a work session on Friday, September 18, 2026 at 9:00 AM at 8220 Loop Road. Under old business the agenda lists proposed noise ordinance wording from outside consultants, described as awaiting changes; a data center concerns list progress update; and the Battery Energy Storage System ordinance. Under new business it lists a continuation of the electricity discussion and a new topic, generators and turbines. The agenda states the next meeting will continue the electricity discussion. No applicant, named project, or Community Benefit Agreement action appears on this agenda. This is the newest item on the data-center-information page and remains unpromoted (the tracked fingerprint still sits at July 31, 2026).

Proposed edit

Add the September 18, 2026 Data Center Advisory Committee work session to the local-process timeline, noting that the consultant-drafted noise ordinance language is awaiting changes and that generators and turbines entered the committee's agenda as a new business item.

Held only because another item in the 2026-09-23 batch was flagged. Nothing was filed against this one.

Source · 2026-09-18 ↗

verified No objection filed 2026-09-23

town-of-lysander-official-records

The presentation deck accompanying the September 18, 2026 meeting sets out the committee's recommendations on on-site backup generation. It recommends allowing only natural gas or bi-fuel generators for emergency backup power, on the stated grounds that these are the two quietest options, eliminate or greatly reduce on-site diesel storage, produce far fewer greenhouse gas, carbon and soot emissions than diesel, and avoid the high-pitched whine of turbines; an immediate shutdown trigger if bi-fuel units fall below 70 percent natural gas utilization during a test; that generators be allowed only for backup power during an outage with no behind-the-meter use of generators or turbines; that a full environmental impact study addressing noise and environmental issues precede any approval; that scheduled inspections by a certified third party be required; that testing be confined to specified weekday daytime hours with caps on units tested at once and on annual testing hours; that a separate decommissioning bond be posted for generator farms; and that generator farms be defined as a special use requiring separate review and permit. The deck also records the division of authority: the town has no say in power delivery or rates, NYISO operates the high-voltage grid and sets supply charges while the PSC sets delivery charges and service classifications, and while DEC regulates generator emissions, fuel types and fuel storage, the town can regulate generator size, operating hours outside emergencies, setbacks and noise through code and can designate on-site or behind-the-meter generation above a threshold (the deck suggests 5 MW) as a separate or prohibited land use. These are committee recommendations presented at a work session, not adopted town code. Unpromoted.

Proposed edit

Record the committee's on-site generation recommendations - natural gas or bi-fuel only, backup-only with no behind-the-meter generation, special-use permitting, decommissioning bond and testing-hour limits - as proposed local controls under development, clearly distinguished from enacted code, alongside the deck's own statement of the division of authority between the town, DEC, NYISO and the PSC.

Held only because another item in the 2026-09-23 batch was flagged. Nothing was filed against this one.

Source · 2026-09-18 ↗

estimated No objection filed 2026-09-23

town-of-lysander-official-records

The September 18 deck works through backup-generation sizing for what it calls a '270 MW Data Center'; the deck does not say whether 270 MW is requested interconnection capacity, service capacity, or critical IT load. Its table, whose unit counts are labeled as calculated, gives with redundancy roughly 78 to 93 diesel units at 3.25 to 4 MW each, 64 to 118 natural gas units at 2.5 to 5 MW, and 78 bi-fuel units at 4 MW. For natural gas turbines at 34 to 50 MW each, the table lists 5 to 8 calculated units plus 1 redundant unit, but prints the total as 35 to 51; that total does not follow from the table's own columns (5 to 8 plus 1 would be 6 to 9), and the deck's noise table separately uses 58 turbine units, so the turbine totals are internally inconsistent in the source and should not be relied on. On fuel, the deck states that standard industrial backup generators use about 70 gallons of diesel per hour per megawatt, giving about 450,000 gallons for a 24-hour outage at 270 MW and 900,000 gallons for the 48-hour supply it calls industry standard, reduced by about two thirds for bi-fuel to 157,500 and 315,000 gallons. Its noise table estimates property-line levels at a 400-foot setback without mitigation of 73 dBA diesel, 68 natural gas, 69 bi-fuel and 75 turbine, with the deck's caveat that these are dBA only and that dBC levels need further research. All figures are the committee's own calculations against a hypothetical load, not a developer submission, permit application, or measurement. Unpromoted; revised from the 2026-09-22 draft after the critic hold on the turbine row.

Proposed edit

Present the committee's diesel, natural gas and bi-fuel unit counts, diesel storage figures and property-line noise estimates as its own calculations for an unspecified-capacity-type 270 MW hypothetical, omit the turbine unit total or flag it as internally inconsistent in the source, and reproduce the dBA-only caveat.

Held only because another item in the 2026-09-23 batch was flagged. Nothing was filed against this one.

Source · 2026-09-18 ↗

verified Critic flagged 2026-09-23

new-york-executive-order-62

The Empire State Development Community Investment Framework, the deliverable Executive Order 62 required within 60 days, is published and complete. The page offers three documents: CIF Guidance, a CIF Template, and a CIF Template Example prepared for a hypothetical Town of Empire. It sets a recommended community investment benchmark of one million dollars for every megawatt of utility demand associated with a data center project, and organizes commitments under four pillars: establishing good neighbor commitments, enforcing workforce and labor standards, standardizing transparency and accountability, and specifying targeted investments. The framework is a voluntary negotiating tool for local governments and developers rather than a binding requirement. The page itself carries no publication date. Re-verified this pass via WebFetch (direct curl returned HTTP 403) and unchanged; it remains unpromoted, with promoted.json still recording only the earlier outline-only state.

Proposed edit

Update the Community Investment Framework entry from 'outline only, completed framework pending' to published, listing the guidance, template and worked example, the $1 million per megawatt recommended benchmark and the four pillars, and stating plainly that the framework is voluntary.

Critic findings against this item (2)

no-fabricationThe summary opens by calling the framework 'the deliverable Executive Order 62 required within 60 days.' The 60-day term comes from Executive Order 62, not from the cited source_url (https://esd.ny.gov/communityinvestmentframework), which the entry itself says 'carries no publication date.' The entry is labeled 'verified' against the ESD page alone, and that page cannot support the 60-day figure. This is the same defect the 2026-09-20 verdict flagged, and it has not been fixed. Either cite the EO 62 text for the 60-day term or drop the characterization.
distinguish-capacity-typesThe summary correctly gives the benchmark as 'one million dollars for every megawatt of utility demand associated with a data center project.' The proposed_change shortens this to 'the $1 million per megawatt recommended benchmark,' which drops the qualifier 'of utility demand.' A bare per-megawatt figure on the site could be read against critical IT load, requested interconnection capacity, or a nameplate figure such as TeraWulf's '400 gross MW / 320 critical IT MW,' and each would give a different dollar amount. The proposed_change should keep 'per megawatt of utility demand' exactly as the source words it.

Source · 2026-09-23 ↗

verified Critic flagged 2026-09-23

psc-case-26-e-0045-large-load-interconnection

The Commission order that created Case 26-E-0045 was issued and effective February 12, 2026, instituting the proceeding to address large-load interconnection reform. Two forward deadlines appear in its ordering clauses that are absent from the DPS event page tracked so far: Department of Public Service staff shall convene at least one public technical conference before December 31, 2026, and shall prepare a whitepaper addressing the interconnection and related issues considered in the proceeding within one year of the order's issuance, that is by February 12, 2027. The order's own comment dates were April 13, 2026 for initial comments and May 13, 2026 for replies; the tracked event page shows those subsequently extended to May 13 and June 15, 2026, so the extended dates govern the comment phase while the conference and whitepaper deadlines stand as ordered. Re-verified this pass against the order text and unpromoted.

Proposed edit

Add the two ordered Case 26-E-0045 milestones - a DPS technical conference before December 31, 2026 and a DPS staff whitepaper by February 12, 2027 - to the forward calendar, cited to the February 12, 2026 Order Instituting Proceeding rather than to the DPS event page.

Critic findings against this item (1)

no-fabricationThe summary says the comment dates were 'subsequently extended to May 13 and June 15, 2026.' Those extension dates cannot appear in the source_url document, the Order Instituting Proceeding issued February 12, 2026. The summary itself attributes them to 'the tracked event page,' a different source whose URL is not given in this entry. The order's own April 13 / May 13 dates, the December 31, 2026 conference deadline and the one-year whitepaper term do trace to source_url. The extension dates do not, yet the whole entry is labeled 'verified' against the order. The 2026-09-20 verdict flagged the same defect, and the entry still carries it unchanged. Either cite the event page for the extension dates or move them to their own entry.

Source · 2026-02-12 ↗

verified No objection filed 2026-09-23

psc-case-26-e-0045-large-load-interconnection

The same February 12, 2026 order states the scale figure behind the proceeding: as of February 2026, 11.9 gigawatts of load within the New York Independent System Operator interconnection queue were attributed to future large-load projects, and in 2025 alone more than 8.3 gigawatts of new load entered the NYISO queue. The order presents these as the emerging challenge motivating interconnection reform. These are statewide queue figures for large loads generally, not a count of data centers and not specific to any Central New York project, and they should not be combined with any site-level megawatt figure. Re-verified this pass against the order text and unpromoted.

Proposed edit

Record the statewide context figure - 11.9 GW of large-load projects in the NYISO queue as of February 2026, with more than 8.3 GW added during 2025 - as state-level background, explicitly labeled statewide and not tied to a local site.

Held only because another item in the 2026-09-23 batch was flagged. Nothing was filed against this one.

Source · 2026-02-12 ↗

reported Critic flagged 2026-09-23

responsible-data-center-development-act

Press coverage reports that the Governor has until December 31, 2026 to sign or veto the Responsible Data Center Development Act, and that if she does not act the bill will not become law, a pocket veto. The Ithaca Voice states this in an August 31, 2026 article, which also notes the Governor opted to issue Executive Order 62 in July 2026 instead of signing the bill. The nysenate.gov and nyassembly.gov primary records show no action later than June 4, 2026 and do not themselves publish a deadline, so the December 31 date rests on the reporting rather than on a primary document located this pass. Carried forward from prior passes and unpromoted.

Proposed edit

Note on the bill's status entry that press coverage reports a December 31, 2026 deadline for gubernatorial action, after which the bill would be pocket-vetoed, labeled as reported rather than verified against a primary record.

Critic findings against this item (1)

evidence-label-accuracyThe lens defines 'reported' as a statement by a named applicant, company or official whose underlying data is not public. The December 31, 2026 sign-or-pocket-veto deadline here comes only from an Ithaca Voice article ('Press coverage reports...'). A news outlet's own account of a legal deadline is not a named applicant, company or official making a statement. The summary also admits no primary record states the deadline. Under this lens the claim is closer to 'unknown' for the primary record, with the article as a pointer, than to 'reported.' Because the fit is at best ambiguous, and ambiguity resolves toward hold: either name the official or legislative source the article relies on, or relabel it and describe the Ithaca Voice piece as secondary coverage only.

Source · 2026-08-31 ↗

verified No objection filed 2026-09-22

town-of-lysander-official-records

The Lysander Data Center Advisory Committee held a work session on Friday, September 18, 2026 at 9:00 AM at 8220 Loop Road. Under old business the agenda lists proposed noise ordinance wording from outside consultants, described as awaiting changes; a data center concerns list progress update; and the Battery Energy Storage System ordinance. Under new business it lists a continuation of the electricity discussion and a new topic, generators and turbines. The agenda states the next meeting will continue the electricity discussion. No applicant, named project, or Community Benefit Agreement action appears on this agenda. This is the newest item on the data-center-information page and remains unpromoted (the tracked fingerprint still sits at July 31, 2026).

Proposed edit

Add the September 18, 2026 Data Center Advisory Committee work session to the local-process timeline, noting that the consultant-drafted noise ordinance language is awaiting changes and that generators and turbines entered the committee's agenda as a new business item.

Held only because another item in the 2026-09-22 batch was flagged. Nothing was filed against this one.

Source · 2026-09-18 ↗

verified No objection filed 2026-09-22

town-of-lysander-official-records

The presentation deck accompanying the September 18, 2026 meeting sets out the committee's recommendations on on-site backup generation. It recommends allowing only natural gas or bi-fuel generators for emergency backup power, on the stated grounds that these are the two quietest options, eliminate or greatly reduce on-site diesel storage, produce far fewer greenhouse gas, carbon and soot emissions than diesel, and avoid the high-pitched whine of turbines; an immediate shutdown trigger if bi-fuel units fall below 70 percent natural gas utilization during a test; that generators be allowed only for backup power during an outage with no behind-the-meter use of generators or turbines; that a full environmental impact study addressing noise and environmental issues precede any approval; that scheduled inspections by a certified third party be required; that testing be confined to specified weekday daytime hours with caps on units tested at once and on annual testing hours; that a separate decommissioning bond be posted for generator farms; and that generator farms be defined as a special use requiring separate review and permit. The deck also records the division of authority: the town has no say in power delivery or rates, NYISO operates the high-voltage grid and sets supply charges while the PSC sets delivery charges and service classifications, and while DEC regulates generator emissions, fuel types and fuel storage, the town can regulate generator size, operating hours outside emergencies, setbacks and noise through code and can designate on-site or behind-the-meter generation above a threshold (the deck suggests 5 MW) as a separate or prohibited land use. These are committee recommendations presented at a work session, not adopted town code. Unpromoted.

Proposed edit

Record the committee's on-site generation recommendations - natural gas or bi-fuel only, backup-only with no behind-the-meter generation, special-use permitting, decommissioning bond and testing-hour limits - as proposed local controls under development, clearly distinguished from enacted code, alongside the deck's own statement of the division of authority between the town, DEC, NYISO and the PSC.

Held only because another item in the 2026-09-22 batch was flagged. Nothing was filed against this one.

Source · 2026-09-18 ↗

estimated Critic flagged 2026-09-22

town-of-lysander-official-records

The same September 18 deck works through backup-generation sizing against a 270 megawatt data center load. Its table is explicitly labeled as calculated and gives, with redundancy included, roughly 78 to 93 diesel units at 3.25 to 4 MW each, 64 to 118 natural gas units at 2.5 to 5 MW, 78 bi-fuel units at 4 MW, and 35 to 51 natural gas turbines at 34 to 50 MW. On fuel it states that standard industrial backup generators consume about 70 gallons of diesel per hour per megawatt, yielding about 450,000 gallons for a 24-hour outage at 270 MW and about 900,000 gallons for the 48-hour supply it describes as industry standard, with bi-fuel reducing those figures by roughly two thirds to about 157,500 and 315,000 gallons. A companion table estimates combined noise at a 400-foot property-line setback without mitigation at 73 dBA for diesel, 68 for natural gas, 69 for bi-fuel and 75 for turbines, and carries the deck's own caveat that these are dBA only and that further research is required for dBC levels. Every figure here is the committee's own labeled calculation against a hypothetical load, not a developer submission, a permit application, or a measured value. Unpromoted.

Proposed edit

Present the committee's generator-count, diesel-storage and property-line noise figures as the committee's own calculations against a hypothetical 270 MW load, reproducing the deck's dBA-only caveat and avoiding any implication that these describe a proposed project.

Critic findings against this item (2)

no-fabricationThe turbine row does not reconcile with the 270 MW basis the rest of the entry uses, so at least one of its figures cannot be tracing correctly to the deck at source_url. As written, '35 to 51 natural gas turbines at 34 to 50 MW' spans 1,190 MW to 2,550 MW of backup capacity - 4.4x to 9.4x the stated 270 megawatt load - while every sibling row lands near it: diesel '78 to 93 units at 3.25 to 4 MW' = 254-372 MW, bi-fuel '78 units at 4 MW' = 312 MW, natural gas '64 to 118 units at 2.5 to 5 MW' = 160-590 MW. Either the unit count or the per-unit MW rating for turbines has been misread from dcac_pp_electricity_09-18-26.pdf, and the summary reproduces it without noticing the discrepancy. The turbine count must be re-read against the source table and corrected, or the mismatch explained, before this figure is recorded.
distinguish-capacity-typesThe entry carries the 270 MW figure through generator sizing, diesel volume ('about 450,000 gallons for a 24-hour outage at 270 MW') and the noise table without ever saying which capacity type it is. The deck's own basis - requested interconnection capacity, service capacity, or critical IT load - is not stated, and the three quantities derived from it do not follow identically from each: backup generation is normally sized to critical IT load plus redundancy, not to an interconnection request. Calling it 'a 270 megawatt data center load' and 'a hypothetical load' identifies it as hypothetical but not as a type. Name the capacity type the deck uses, or state that the deck does not specify it.

Source · 2026-09-18 ↗

verified No objection filed 2026-09-22

new-york-executive-order-62

The Empire State Development Community Investment Framework, the deliverable Executive Order 62 required within 60 days, is published and complete. The page offers three documents: CIF Guidance, a CIF Template, and a CIF Template Example prepared for a hypothetical Town of Empire. It sets a recommended community investment benchmark of one million dollars for every megawatt of utility demand associated with a data center project, and organizes commitments under four pillars: establishing good neighbor commitments, enforcing workforce and labor standards, standardizing transparency and accountability, and specifying targeted investments. The framework is a voluntary negotiating tool for local governments and developers rather than a binding requirement. The page itself carries no publication date. Re-verified this pass and unchanged; it remains unpromoted, with promoted.json still recording only the earlier outline-only state.

Proposed edit

Update the Community Investment Framework entry from 'outline only, completed framework pending' to published, listing the guidance, template and worked example, the $1 million per megawatt recommended benchmark and the four pillars, and stating plainly that the framework is voluntary.

Held only because another item in the 2026-09-22 batch was flagged. Nothing was filed against this one.

Source · 2026-09-22 ↗

verified No objection filed 2026-09-22

psc-case-26-e-0045-large-load-interconnection

The Commission order that created Case 26-E-0045 was issued and effective February 12, 2026, instituting the proceeding to address large-load interconnection reform. Two forward deadlines appear in its ordering clauses that are absent from the DPS event page tracked so far: Department of Public Service staff shall convene at least one public technical conference before December 31, 2026, and shall prepare a whitepaper addressing the interconnection and related issues considered in the proceeding within one year of the order's issuance, that is by February 12, 2027. The order's own comment dates were April 13, 2026 for initial comments and May 13, 2026 for replies; the tracked event page shows those subsequently extended to May 13 and June 15, 2026, so the extended dates govern the comment phase while the conference and whitepaper deadlines stand as ordered. Carried forward from prior passes and unpromoted.

Proposed edit

Add the two ordered Case 26-E-0045 milestones - a DPS technical conference before December 31, 2026 and a DPS staff whitepaper by February 12, 2027 - to the forward calendar, cited to the February 12, 2026 Order Instituting Proceeding rather than to the DPS event page.

Held only because another item in the 2026-09-22 batch was flagged. Nothing was filed against this one.

Source · 2026-02-12 ↗

verified No objection filed 2026-09-22

psc-case-26-e-0045-large-load-interconnection

The same February 12, 2026 order states the scale figure behind the proceeding: as of February 2026, 11.9 gigawatts of load within the New York Independent System Operator interconnection queue were attributed to future large-load projects, and in 2025 alone more than 8.3 gigawatts of new load entered the NYISO queue. The order presents these as the emerging challenge motivating interconnection reform. These are statewide queue figures for large loads generally, not a count of data centers and not specific to any Central New York project, and they should not be combined with any site-level megawatt figure. Carried forward and unpromoted.

Proposed edit

Record the statewide context figure - 11.9 GW of large-load projects in the NYISO queue as of February 2026, with more than 8.3 GW added during 2025 - as state-level background, explicitly labeled statewide and not tied to a local site.

Held only because another item in the 2026-09-22 batch was flagged. Nothing was filed against this one.

Source · 2026-02-12 ↗

reported No objection filed 2026-09-22

responsible-data-center-development-act

Press coverage reports that the Governor has until December 31, 2026 to sign or veto the Responsible Data Center Development Act, and that if she does not act the bill will not become law, a pocket veto. The Ithaca Voice states this in an August 31, 2026 article, which also notes the Governor opted to issue Executive Order 62 in July 2026 instead of signing the bill. The nysenate.gov and nyassembly.gov primary records show no action later than June 4, 2026 and do not themselves publish a deadline, so the December 31 date rests on the reporting rather than on a primary document located this pass. Carried forward from prior passes and unpromoted.

The Commission order that created Case 26-E-0045 was located and read in full this pass. It was issued and effective February 12, 2026, instituting the proceeding to execute the Energize NY Development initiative that the Governor announced in the January 13, 2026 State of the State. Two forward deadlines appear in its ordering clauses that are absent from the DPS event page tracked so far: Department of Public Service staff shall convene at least one public technical conference before December 31, 2026, and shall prepare a whitepaper on large-load interconnection within one year of the order's issuance, that is by February 12, 2027. The order specifies the whitepaper will be informed by the technical conference, will address the comments filed in the proceeding, will be subject to public notice and comment, and will contain recommendations for the Commission's consideration. The order's own comment dates were April 13, 2026 for initial comments and May 13, 2026 for replies; the tracked event page shows those subsequently extended to May 13 and June 15, 2026 respectively, so the extended dates govern the comment phase while the conference and whitepaper deadlines stand as ordered.

Proposed edit

Add the two ordered Case 26-E-0045 milestones - a DPS technical conference before December 31, 2026 and a DPS staff whitepaper by February 12, 2027 - to the forward calendar, cited to the February 12, 2026 Order Instituting Proceeding rather than to the DPS event page.

Critic findings against this item (1)

no-fabricationThe summary's closing sentence carries two dates - comment deadlines 'subsequently extended to May 13 and June 15, 2026' - that cannot be contained in the source_url document, which is the Order Instituting Proceeding issued February 12, 2026. The summary itself attributes them to 'the tracked event page,' i.e. a different source than the one cited in source_url, and no URL for that page is given in this entry. The order's own April 13 / May 13, 2026 comment dates do trace to source_url; the extension dates do not, and the entry is labeled 'verified' against a document that cannot support them.

Source · 2026-02-12 ↗

verified No objection filed 2026-09-20

psc-case-26-e-0045-large-load-interconnection

The same February 12, 2026 order states the scale figure behind the proceeding: as of February 2026, 11.9 gigawatts of load within the New York Independent System Operator interconnection queue were attributed to future large-load projects, and in 2025 alone more than 8.3 gigawatts of new load entered the NYISO queue. The order presents these as the emerging challenge motivating interconnection reform and notes such requests may introduce planning uncertainty through speculative entries. These are statewide queue figures for large loads generally, not a count of data centers and not specific to any Central New York project, and they should not be combined with any site-level megawatt figure.

Proposed edit

Record the statewide context figure - 11.9 GW of large-load projects in the NYISO queue as of February 2026, with more than 8.3 GW added during 2025 - as state-level background, explicitly labeled statewide and not tied to a local site.

Held only because another item in the 2026-09-20 batch was flagged. Nothing was filed against this one.

Source · 2026-02-12 ↗

verified Critic flagged 2026-09-20

new-york-executive-order-62

The Empire State Development Community Investment Framework, the deliverable Executive Order 62 required within 60 days, is published and complete. The page now offers three documents: CIF Guidance, a CIF Template, and a CIF Template Example prepared for a hypothetical Town of Empire. It sets a recommended community investment benchmark of one million dollars for every megawatt of utility demand associated with a data center project, and organizes commitments under four pillars: good neighbor commitments, workforce standards, transparency and accountability, and targeted investments. The framework is a voluntary negotiating tool for local governments and developers rather than a binding requirement, and ESD asks communities to share completed frameworks with it. The page itself carries no publication date. This is carried forward from a prior pass and remains unpromoted; promoted.json still records only the earlier outline-only state.

Proposed edit

Update the Community Investment Framework entry from 'outline only, completed framework pending' to published, listing the guidance, template and worked example, the $1 million per megawatt recommended benchmark and the four pillars, and stating plainly that the framework is voluntary.

Critic findings against this item (1)

no-fabricationThe summary opens by characterizing the framework as 'the deliverable Executive Order 62 required within 60 days.' The '60 days' requirement is a term of Executive Order 62, not of the ESD Community Investment Framework page at source_url (https://esd.ny.gov/communityinvestmentframework), which the entry elsewhere notes 'carries no publication date.' The specific 60-day figure is not traceable to the cited URL, and the entry is labeled 'verified' on the strength of that URL alone. Either cite the EO 62 text directly for the 60-day term or drop the characterization.

Source · 2026-09-20 ↗

verified No objection filed 2026-09-20

town-of-lysander-official-records

The Lysander Data Center Advisory Committee held a work session on Friday, September 18, 2026 at 9:00 AM at 8220 Loop Road. Under old business the agenda lists proposed noise ordinance wording from outside consultants, described as awaiting changes; a data center concerns list progress update; and the Battery Energy Storage System ordinance. Under new business it lists a continuation of the electricity discussion and a new topic, generators and turbines. The agenda states the next meeting will continue the electricity discussion. No applicant, named project, or Community Benefit Agreement action appears on this agenda. Carried forward from the prior pass and re-verified from the posted PDF; it remains unpromoted.

Proposed edit

Add the September 18, 2026 Data Center Advisory Committee work session to the local-process timeline, noting that the consultant-drafted noise ordinance language is awaiting changes and that generators and turbines entered the committee's agenda as a new business item.

Held only because another item in the 2026-09-20 batch was flagged. Nothing was filed against this one.

Source · 2026-09-18 ↗

verified No objection filed 2026-09-20

town-of-lysander-official-records

The presentation deck accompanying the September 18, 2026 meeting sets out the committee's recommendations on on-site backup generation. It recommends allowing only natural gas or bi-fuel generators for emergency backup power, on the stated grounds that these are the two quietest options, eliminate or greatly reduce on-site diesel storage, produce dramatically fewer greenhouse gas, carbon and soot emissions than diesel, and avoid the high-pitched whine of turbines; it also recommends an immediate shutdown trigger if bi-fuel units fall below 70 percent natural gas utilization during a test. Further recommendations are that generators be allowed only for backup power during an outage with no behind-the-meter use of generators or turbines, that a full environmental impact study addressing noise and environmental issues precede any approval, that scheduled inspections by a certified third party be required, that testing be confined to specified weekday daytime hours with a cap on units tested at once and on annual testing hours, that a separate decommissioning bond be posted for generator farms, and that generator farms be defined as a special use requiring separate review and permit. The deck also records what the town can and cannot control: it states the town has no say in power delivery or rates, that NYISO operates the high-voltage grid and sets supply charges while the Public Service Commission sets delivery charges and service classifications, and that while DEC regulates generator emissions, fuel types and fuel storage, the town can regulate generator size, operating hours outside emergencies, setbacks and noise through code. These are committee recommendations presented at a work session, not adopted town code. Carried forward from the prior pass and re-verified from the posted PDF; it remains unpromoted.

Proposed edit

Record the committee's on-site generation recommendations - natural gas or bi-fuel only, backup-only with no behind-the-meter generation, special-use permitting, decommissioning bond and testing-hour limits - as proposed local controls under development, clearly distinguished from enacted code, alongside the deck's own statement of the division of authority between the town, DEC, NYISO and the PSC.

Held only because another item in the 2026-09-20 batch was flagged. Nothing was filed against this one.

Source · 2026-09-18 ↗

estimated No objection filed 2026-09-20

town-of-lysander-official-records

The same September 18 deck works through backup-generation sizing against a 270 megawatt data center load. Its table is explicitly labeled as calculated and gives, with redundancy included, roughly 78 to 93 diesel units at 3.25 to 4 MW each, 64 to 118 natural gas units at 2.5 to 5 MW, 78 bi-fuel units at 4 MW, and 35 to 51 natural gas turbines at 34 to 50 MW. On fuel it states that standard industrial backup generators consume about 70 gallons of diesel per hour per megawatt, yielding about 450,000 gallons for a 24-hour outage at 270 MW and about 900,000 gallons for the 48-hour supply it describes as industry standard, with bi-fuel reducing those figures by roughly two thirds to about 157,500 and 315,000 gallons. A companion table estimates combined noise at a 400-foot property-line setback without mitigation at 73 dBA for diesel, 68 for natural gas, 69 for bi-fuel and 75 for turbines, and carries the deck's own caveat that these are dBA only and that further research is required for dBC levels. Every figure here is the committee's own labeled calculation against a hypothetical load, not a developer submission, a permit application, or a measured value. Carried forward from the prior pass and re-verified from the posted PDF; it remains unpromoted.

Proposed edit

Present the committee's generator-count, diesel-storage and property-line noise figures as the committee's own calculations against a hypothetical 270 MW load, reproducing the deck's dBA-only caveat and avoiding any implication that these describe a proposed project.

Held only because another item in the 2026-09-20 batch was flagged. Nothing was filed against this one.

Source · 2026-09-18 ↗

reported No objection filed 2026-09-20

responsible-data-center-development-act

Press coverage reports that the Governor has until December 31, 2026 to sign or veto the Responsible Data Center Development Act, and that if she does not act the bill will not become law, a pocket veto. The Ithaca Voice states this in an August 31, 2026 article, which also notes the Governor opted to issue Executive Order 62 in July 2026 instead of signing the bill. The nysenate.gov and nyassembly.gov primary records show no action later than June 4, 2026 and do not themselves publish a deadline, so the December 31 date rests on the reporting rather than on a document located this pass. Separately, one commentary piece speculates about a year-end veto; that is speculation and is not treated as a reportable fact.

Empire State Development's Community Investment Framework for data center development, the deliverable Executive Order No. 62 directed ESD to publish within 60 days, is live and complete. The ESD page carries three documents: a CIF Guidance document, a CIF negotiation Template, and a worked 'Town of Empire' example. This moves the deliverable past the earlier outline-only, framework-pending state. The page itself carries no publication dates for the three documents.

Proposed edit

Update the state-framework status note to state that the ESD Community Investment Framework is published in full - guidance, template, and worked example - replacing the earlier 'outline only, completed framework pending' language.

Critic findings against this item (1)

no-fabricationThe summary asserts a specific figure - that Executive Order No. 62 'directed ESD to publish within 60 days' - but source_url is the ESD Community Investment Framework landing page (esd.ny.gov/communityinvestmentframework), not the text of EO 62 where the 60-day deadline actually lives. That specific '60 days' figure is not established to appear at the cited source_url; it traces to a different document (the EO itself). Per strict traceability this is a source_url mismatch.

Source · 2026-09-14 ↗

verified No objection filed 2026-09-18

new-york-executive-order-62

The published framework sets a recommended community investment benchmark of $1 million for every megawatt of utility demand associated with a data center project, presented as a voluntary reference point to help local governments and industrial development agencies negotiate benefits proportional to project scale. The figure now appears in a published state framework rather than a policy outline. Applying the benchmark to any particular project would be a calculation, not a figure the framework itself states.

The Oak Orchard SPDES permit (NY0030317, Onondaga County, DEC number 7-3124-00018/00001) is a renewal and modification effective May 1, 2026 and expiring April 30, 2031. It structures the plant's expansion in four phases whose transitions are triggered by DEC acceptance of construction completion rather than by calendar date: Phase 1 maintains existing plant operations; Phase 2 begins on acceptance of the first portion of the industrial treatment train; Phase 3 begins on acceptance of the upgraded municipal treatment train; Phase 4 begins on acceptance of the second portion. The modification creates two new internal outfalls, 01A for the municipal treatment train and 01B for the industrial treatment train, and raises the municipal train's monthly average flow limit from 10 MGD to 14.3 MGD while setting a 16.5 MGD monthly average flow limit for the industrial train. The permit states that during Phase 2 the industrial train's design flow will be 8.25 MGD and the municipal train's will remain 13.3 MGD, for a combined Phase 2 effluent rate of 21.6 MGD, against an existing 10.0 MGD facility. Two reuse outfalls are established, 006 for municipal treatment train effluent reuse and 007 for industrial treatment train effluent reuse, with reuse flow monitoring becoming effective on DEC acceptance of construction completion. A dedicated emerging-contaminants section sets levels and monitoring for a long list of perfluorinated compounds including PFOA, PFOS, PFBS, PFHxA, PFNA and related acids. The modification also removes a set of prior requirements at Outfall 001, including fecal coliform, pH, settleable solids and TSS monitoring and action levels for total recoverable iron, chloroform, cadmium, chromium, copper, nickel, zinc and arsenic and total phenols, transferring or replacing them at the new internal outfalls.

Proposed edit

Expand the Oak Orchard SPDES permit entry from the current general description to carry the permit term (effective May 1, 2026, expiring April 30, 2031), the four named phases and the fact that phase transitions are triggered by DEC acceptance of construction completion rather than dates, the specific flow limits (municipal train raised 10 to 14.3 MGD, industrial train 16.5 MGD, combined Phase 2 rate 21.6 MGD against a 10.0 MGD existing facility), and the two reuse outfalls 006 and 007 by name. Note explicitly that the underlying document is unchanged and that this detail became available because the PDF's text layer extracted on this pass after failing on several prior passes.

Critic findings against this item (1)

evidence-label-accuracyThe summary reads: 'The permit states that during Phase 2 the industrial train's design flow will be 8.25 MGD and the municipal train's will remain 13.3 MGD, for a combined Phase 2 effluent rate of 21.6 MGD.' 8.25 + 13.3 = 21.55 (rounds to 21.6), so '21.6 MGD' appears to be the drafter's own sum of the two component design flows rather than a figure the permit itself states, yet it is placed inside a 'The permit states that...' clause and filed under evidence:verified. A computed combined total presented as a directly-stated, measured permit fact should be labeled as a calculation, not carried as verified. Compounding it, the same clause then compares this Phase 2 combined DESIGN FLOW (21.6 MGD) to 'an existing 10.0 MGD facility,' where 10 MGD is identified two sentences earlier as the existing monthly-average flow LIMIT ('raises the municipal train's monthly average flow limit from 10 MGD to 14.3 MGD') - blurring design flow against permitted flow limit (distinguish-capacity-types) in the same comparison.

Source · 2026-05-01 ↗

verified No objection filed 2026-09-14

town-of-lysander-data-storage-center-moratorium

The text of Lysander Local Law No. 4 of 2026 uses two different triggers, which prior records on this source had collapsed into one. Section VIII provides that the law takes effect upon filing with the Secretary of State and 'shall remain in force and effect for a period of 6 months from its effective date', so the six-month duration runs from the Secretary of State filing. Section III separately provides that the law 'applies to all applications for Data Storage Facilities filed with the Town after adoption', keying applicability to adoption instead. The duration therefore runs from filing while the scope of application runs from adoption, and the two dates need not coincide. The document as posted still bears no adoption date and no Secretary of State filing date on its face, so the expiry of the pause remains underivable from this document alone. The law also bars any Town board, including the Town Board, Planning Board and Zoning Board of Appeals, from accepting applications for Data Storage Facilities during the period; suspends Section 276 of the Town Law and the Zoning Board of Appeals' Section 267-b jurisdiction to grant relief from it; reserves to the Town Board alone the power to vary the law after a public hearing on a $100 application, with any relief granted by amendment; and sets a penalty of $1,000 per day of violation.

Proposed edit

Correct the moratorium entry to distinguish the two triggers rather than describing the pause as keyed to adoption: the six-month duration runs from the effective date, which Section VIII sets at filing with the Secretary of State, while Section III keys applicability to adoption. Keep the existing caveat that neither date appears on the posted document so the expiry cannot be stated, and add the enforcement and relief mechanics (no board may accept applications, Zoning Board of Appeals relief jurisdiction suspended, variance only by Town Board after public hearing and by amendment, $1,000 per day penalty).

Held only because another item in the 2026-09-14 batch was flagged. Nothing was filed against this one.

Source · 2026-04-22 ↗

verified No objection filed 2026-09-14

new-york-executive-order-62

The Empire State Development Community Investment Framework Policy Outline dated July 14, 2026, issued under Executive Order No. 62, recommends a minimum contribution threshold for data center operators of $1 million per 1 megawatt of anticipated utility demand per project, expressed as dollars invested per megawatt of demand and described as a recommended level intended to give local governments and developers a consistent basis for negotiation. The outline states that ESD 'shall prepare a Community Investment Framework template' containing Good Neighbor Commitments (landscaping, design, and mitigation of noise and light pollution), Labor Commitments (prevailing wage standards, project labor agreements, local hiring, apprenticeships and workforce development), and a Community Investment Fund whose eligible investments may include public infrastructure such as parks, water and sewer upgrades, roads, energy transmission, transit, water treatment plants and EV charging. This is the policy outline, not the completed framework: as of September 14, 2026 the ESD page still carries only this July 14 document and the statement that the completed framework 'will be released by mid-September', and the order's 60-day deadline for posting the framework passed on or about September 12, 2026.

Proposed edit

Add the $1 million-per-megawatt recommended minimum contribution threshold and the three named framework components (Good Neighbor Commitments, Labor Commitments, Community Investment Fund) to the Executive Order No. 62 material, attributed to the July 14, 2026 ESD Policy Outline and labelled as a recommended threshold in an outline for a framework not yet issued. State alongside it that the completed framework remained unreleased as of September 14, 2026, past the order's roughly September 12 deadline. Do not describe the framework as released or the threshold as binding.

Held only because another item in the 2026-09-14 batch was flagged. Nothing was filed against this one.

Source · 2026-07-14 ↗

verified On the main site 2026-09-12

town-of-lysander-official-records

Published to the main site on 2026-09-12 under #status: Lysander committee electricity scope and BESS ordinance.

The electricity-usage presentation deck for the September 11, 2026 Lysander Data Center Advisory Committee work session is now posted, attached to the same September 10 page posting that previously carried the agenda alone. Titled on the page 'Elec. Usage PP 9-11-26' (lysander_dc_committee_electricity_usage_09-11-26.pdf, 659.07 KB), the deck opens with priority scores drawn from the committee's concerns spreadsheet: an overall electricity priority of 2.4, with Electricity Usage/Brown Outs/Capacity at 2.8, Battery Storage at 1.8, Nuclear Power generation onsite at 2.1, Generator Usage at 2.4, and 'Who pays for Infrastructure upgrades?' at 3.0. It sets out the committee's reading of the town's regulatory reach: the town has no say in power delivery, rates or grid operation, which sit with NYISO, the Public Service Commission and National Grid, but through its code and the Planning Board SEQR process it can regulate on-site generators by size, operating hours, setbacks and noise, and can influence generator fuel types. It records that the town already has a moratorium on Battery Energy Storage Systems and is actively updating its BESS ordinance, cites existing town code 320-51 barring activities emitting dangerous radioactivity, and floats code options including designating 'behind the meter' on-site generation above a threshold ('say 5 Megawatts') as a separate or prohibited land use and restricting high-voltage switch yards within the zone. The deck's stated next steps are to continue the electricity-usage and on-site-generation discussion and to begin drafting electricity recommendations.

Proposed edit

Add the September 11, 2026 committee electricity-usage presentation to the Lysander local-process entry, recording the concern priority scores, the town-versus-state/NYISO/PSC/National Grid division of regulatory authority the committee lays out, the existing BESS moratorium and in-progress BESS ordinance update, and the code options it is weighing for on-site generation.

Source · 2026-09-11 ↗

reported On the main site 2026-09-12

town-of-lysander-official-records

Published to the main site on 2026-09-12 under #status: Lysander committee electricity scope and BESS ordinance.

The bulk of the September 11, 2026 Lysander committee electricity deck is a proactive analysis of nuclear generation, and it asserts several propositions it does not source. It states that there is currently no application at the state or local level for a nuclear reactor at the proposed data center site or anywhere in the Town of Lysander, and that the state has received no applications for any Small or Micro Modular Reactors anywhere in New York; these are statements by a town advisory committee with no underlying record cited and substantiate the reported claim filed on 2026-09-11 from the meeting agenda. The deck characterizes Small Modular Reactors as up to 300 MW (with about 270 MW more typical) needing 5 to 30 acres plus an NRC 0.22-mile safety buffer, and Micro Modular Reactors as 1 to 20 MW, and asserts that NRC population-density guidelines, based on the combined population of Lysander, Van Buren, Salina and Clay, would bar a conventional nuclear plant anywhere in the town while an SMR or MMR could likely be sited. As named external examples it states that X-energy is partnering with Dow Chemical in Texas to build four 80 MW SMRs totaling 320 MW and that an MMR is planned for Fort Drum with construction expected to start in 2028. It also asserts that state DEC rules bar SMRs and MMRs from disadvantaged communities and that the state could ultimately control siting through the Office of Renewable Energy Siting, which can override home rule, especially if towns enact full bans. None of these figures or claims carry a citation in the deck, and the reactor engineering detail it presents is the committee's own summary; all should be checked against NRC, DEC and ORES records before being repeated as fact.

Proposed edit

Record that the Lysander committee's September 11 electricity deck treats small and micro modular reactors at length as a forward-looking code question, attributing its factual claims (no SMR/MMR applications statewide, the X-energy/Dow and Fort Drum examples, and the ORES home-rule override) to the committee rather than stating them as established, and noting the committee frames all of it as proactive code preparation with no reactor proposed for the site.

Source · 2026-09-11 ↗

verified Critic flagged 2026-09-11

town-of-lysander-official-records

The Town of Lysander data center information page now carries a posting dated September 10, 2026, titled 'Data Center Committee Agenda 9-11-26', linking a single PDF at /sites/default/files/2026-09/dcac_agenda09-11-26.pdf and listed at 145.39 KB. It is the first September 2026 Data Center Advisory Committee document on the page, and it follows the page's own preceding September item, a September 3, 2026 notice reading 'The 9-4-26 Data Center Advisory Committee Meeting is cancelled.' Taken together the two postings establish that the committee's fortnightly Friday cadence was interrupted for one sitting and then resumed a week later rather than a fortnight later. One difference in the posting's form is worth recording: each of the four August postings on this page attaches a dated topic presentation alongside its agenda, the August 7 and August 14 postings sharing lysander_dc_committee_waste_water_8-07-26-26.pdf, the August 21 posting attaching lysander_dc_committee_waste_water_8-21-26.pdf and the August 28 posting attaching lysander_dc_committee_electricity_usage_8-28-26.pdf, whereas the September 10 posting attaches the agenda alone. No minutes for any Data Center Advisory Committee meeting were located on this page as of this retrieval; every committee item on it is an agenda or a presentation.

Proposed edit

Update the Lysander local-process entry to record that the advisory committee resumed on September 11, 2026 after cancelling its September 4 sitting, noting that the September posting carries an agenda only with no accompanying presentation deck.

Critic findings against this item (1)

evidence-label-accuracyThe entry is labeled evidence:"verified" but the clause "the committee's fortnightly Friday cadence was interrupted for one sitting and then resumed a week later rather than a fortnight later" is not directly supported by the primary record and is contradicted by it. The same summary lists the August committee meetings as August 7, 14, 21 and 28 — those dates are seven days apart, i.e. a weekly cadence, not fortnightly. A characterization presented as verified measured fact that the source's own dates refute cannot carry the "verified" label; the cadence claim should be dropped or corrected (and, if kept, downgraded).

Source · 2026-09-10 ↗

verified No objection filed 2026-09-11

town-of-lysander-official-records

The agenda for the September 11, 2026 Lysander Data Center Advisory Committee work session, held at 8220 Loop Road at 9:00 AM, records three matters that were not on any earlier published committee agenda. Under Old Business it lists 'DEC feedback on wastewater, generators, and SEQR', which establishes that the committee has received or expects input from the state environmental agency on those three subjects; the agenda does not reproduce that feedback, date it, or say in what form it was given. Also under Old Business it lists 'Battery Energy Storage System (BESS) Ordinance Update', placing battery storage on the data center committee's own agenda rather than only on the Town Board's. The third is the Old Business item 'Proposed Noise Ordinance Wording from outside consultants - awaiting changes', a third distinct wording for this engagement across three agendas: 'Pending response from vendor' on August 14, 'pending' on August 28, and 'awaiting changes' here, which indicates draft language has now been received and is being revised rather than still awaited. The remaining Old Business item is a Data Center Concerns List Progress Update. Under New Business the agenda lists 'Continue Electricity Discussion', and the Next Meeting item also reads 'Continue Electricity Discussion', so the electricity phase opened on August 28 was scheduled to run past this sitting as well. The agenda closes with a Committee Comments/Feedback item. Reading an agenda establishes what was scheduled, not what was decided.

Proposed edit

Add the September 11, 2026 committee agenda to the Lysander local-process entry, recording the new DEC-feedback and battery-storage-ordinance items, the shift in the noise-ordinance item from awaiting a vendor response to awaiting changes, and the electricity discussion continuing into the next meeting.

Held only because another item in the 2026-09-11 batch was flagged. Nothing was filed against this one.

Source · 2026-09-11 ↗

reported No objection filed 2026-09-11

town-of-lysander-official-records

The September 11, 2026 Lysander Data Center Advisory Committee agenda adds small modular reactors to the committee's scope and, in doing so, asserts three propositions it does not source. Its second New Business item reads "SMR's and MMR's (There are No Plans for this to the best of our knowledge, and none are currently approved for use by the state of New York, but we should update our town code for this emerging technology just in case some future project requests one)". The claim that no such reactors are currently approved for use in New York State is a statement by a town advisory committee with no underlying document cited, and the committee's own hedge, 'to the best of our knowledge', applies to its separate claim that no plans exist. The third element, that the town should update its code for the technology in advance of any application, is the committee's stated intention rather than an action taken; the agenda records no draft code language, no timetable and no vote. This is the first appearance of nuclear generation in the committee's published record, and it follows the committee's move into its electricity phase. The approval-status claim should be checked against the state's own record before being repeated as fact.

Proposed edit

Record that the Lysander committee has added small and micro modular reactors to its code-update scope as of September 11, 2026, attributing the accompanying claim that none are currently approved for use in New York State to the committee rather than stating it as established.

Held only because another item in the 2026-09-11 batch was flagged. Nothing was filed against this one.

Source · 2026-09-11 ↗

verified Critic flagged 2026-09-10

town-of-lysander-official-records

The agenda for the August 14, 2026 Lysander Data Center Advisory Committee work session, held at 8220 Loop Road at 9:00 AM, records two matters that do not appear elsewhere in the town's published account of the committee's work. Under Old Business it lists 'Proposed Noise Ordinance Wording from outside consultants - Pending response from vendor', which establishes that the committee had solicited draft noise-ordinance language from an outside vendor and was still waiting on it as of that date. The agenda does not name the vendor, state when the engagement began, or say who is paying for it. Under New Business it lists 'CNY Solidarity Data Center Meeting Recap', establishing that the committee set aside time to report back on a meeting convened by an outside group; the agenda gives no account of what was discussed there and no minutes of this committee meeting exist on the town site. The remaining items are a Water Usage Discussion under Old Business, a Data Center Concerns List Progress Update, and 'Begin Waste Water Discussion', with the Next Meeting item reading 'Continue Waste Water Discussion'.

Proposed edit

Add the August 14, 2026 meeting to the Lysander advisory-committee timeline, recording the outside-vendor noise ordinance wording as pending on that date and the CNY Solidarity meeting recap as an agenda item, with the caveat that the vendor is unnamed and no minutes exist.

Critic findings against this item (2)

no-absence-as-proofThe summary states 'no minutes of this committee meeting exist on the town site' - phrasing a failure to locate as a statement of non-existence. Entry 5 in this same draft handles the identical situation correctly ('Minutes of this meeting were not posted as of this retrieval'). Rephrase to 'no minutes were located on the town site as of this retrieval'.
no-fabricationTwo claims in the summary cannot trace to source_url, which is the single agenda PDF 8-14-26_dcac_agenda.pdf: (a) that the two matters 'do not appear elsewhere in the town's published account of the committee's work' - a survey across other documents the agenda cannot support; and (b) that no minutes exist on the town site. The agenda supports only the agenda text itself.

Source · 2026-08-14 ↗

verified Critic flagged 2026-09-10

town-of-lysander-official-records

The agenda for the August 28, 2026 Lysander Data Center Advisory Committee work session, held at 8220 Loop Road at 9:00 AM, marks the point at which the committee moved from wastewater to electricity. Under New Business it lists, in order, 'Shared Drive for Documents', 'Data Center Concerns List Progress Update', 'Formalize Waste Water Recommendations' and 'Begin Electricity Usage Discussion', and the Next Meeting item reads 'Continue Electricity Usage Discussion'. The wastewater phase was therefore scheduled to close and the electricity phase to open at the same sitting. Under Old Business the noise ordinance item has been shortened to 'Proposed Noise Ordinance Wording from outside consultants - pending', dropping the 'Pending response from vendor' wording carried two weeks earlier on the August 14 agenda; the agenda does not say whether anything changed in that engagement. The next meeting the agenda anticipates would have been September 4, 2026, which the town later announced as cancelled.

Proposed edit

Add the August 28, 2026 meeting to the Lysander advisory-committee timeline as the sitting at which the committee scheduled formalizing its wastewater recommendations and beginning its electricity discussion, and note that the intended follow-on meeting was the one later cancelled.

Critic findings against this item (2)

no-fabricationThe closing sentence - 'The next meeting the agenda anticipates would have been September 4, 2026, which the town later announced as cancelled' - contains two elements the August 28 agenda at source_url cannot contain: a later cancellation announcement (an event after the document's date), and, given the hedged 'would have been' phrasing, the specific date September 4, 2026 appears derived rather than printed on the agenda (the agenda's own Next Meeting line is quoted as reading only 'Continue Electricity Usage Discussion'). Cite the cancellation notice separately or drop it.
evidence-label-accuracyLabeled 'verified', but the entry bundles the directly-supported agenda text with an unsourced downstream event (the town's later cancellation of the September 4 meeting) that no primary record cited here supports. A 'verified' label must not cover the cancellation clause; split it out or downgrade.

Source · 2026-08-28 ↗

verified Critic flagged 2026-09-10

town-of-lysander-official-records

The Lysander Data Center Advisory Committee's August 21, 2026 wastewater deck sets out the committee's own priority ratings and the monitoring regime it is working toward. It reports ratings drawn from the committee's concerns spreadsheet with water at an overall priority of 2.5, broken into water pollution including PFAs at 2.5, water usage at 2.7, residential water pressure at 2.1, ground water levels at 1.8, who pays for infrastructure upgrades at 3.0, and wastewater handling and treatment at 3.0; the deck does not explain the scale or how the ratings were produced. It records that stormwater runoff was added as a discussion item the week before. On substance it treats a true closed-loop system with no wastewater as the ideal case and states that in reality closed-loop systems drastically reduce total water consumed but most must be periodically flushed and occasionally drained for maintenance, and it notes open loop was already recommended against. It lists as wastewater concerns the volume, coolant toxicity often ethylene-glycol based, PFAs found in some immersion liquids, in fluorinated gases used in some chillers and in some fire-suppression chemicals, anti-corrosion nitrites, biocides, heavy metals leached from equipment, pH and heat. It then sets out a twenty-item monitoring list covering flow rate and total volume, temperature, pH, water hardness, total suspended solids, conductivity, nutrient levels, total organic carbon, biocide levels, dissolved oxygen, chemical and biochemical oxygen demand, chlorides and salts, heavy metals and PFAs, each with a stated reason, and argues for a public dashboard on transparency, trend monitoring, alerting and reuse of the same data for regulatory reporting. The deck states the dashboard requirement would apply to all industrial users and floats making it volume- or content-dependent, with the thresholds left as 'XXX' gallons per week and 'YYY' level of PFAs. Its Next Steps slide sets stormwater as the following topic.

Proposed edit

Add the August 21, 2026 wastewater deck to the Lysander advisory-committee record, covering the committee's water priority ratings, its closed-loop and PFAs analysis, its twenty-parameter monitoring list and its unresolved dashboard thresholds; this replaces the held 2026-09-09 entry that cited these facts to the August 28 electricity deck.

Critic findings against this item (1)

no-fabricationThe summary asserts a 'twenty-item monitoring list' but then enumerates it, and the enumeration does not reach twenty: flow rate, total volume, temperature, pH, water hardness, total suspended solids, conductivity, nutrient levels, total organic carbon, biocide levels, dissolved oxygen, chemical oxygen demand, biochemical oxygen demand, chlorides, salts, heavy metals, PFAs is seventeen at the most generous split, and fewer if the paired items ('chlorides and salts', 'heavy metals and PFAs') are single rows in the deck as written. The count '20' is a specific number that must trace to the deck; either confirm the row count against the posted PDF or drop the count and describe the list without numbering it.

Source · 2026-08-21 ↗

reported No objection filed 2026-09-10

town-of-lysander-official-records

The same August 21, 2026 committee deck asserts a set of background propositions about who is responsible for water and wastewater in Lysander, none of which the deck traces to an underlying document. On a slide headed 'Background' it states that the previously approved warehouse required water and sewer lines to be built out to the site, that the planning board typically requires developers to pay for any required infrastructure additions, that the town does not have its own municipal water system, that the town's wastewater treatment is handled by the county, and that existing town code covers stormwater and runoff. On a further slide it states that the county provides municipal water through OCWA and wastewater management through WEP, and that the town can mandate connection to municipal water supplies, can regulate the use of wells including limits on large-scale water withdrawals, and can during droughts mandate limits on outdoor water use including withdrawals from wells. The prior-warehouse approval and the asserted scope of the town's well and drought authority are the load-bearing claims here and neither is cited in the deck to a code section, a resolution or a prior approval record.

Proposed edit

Record the committee's stated town-versus-county water and wastewater responsibility split and its prior-warehouse infrastructure claim as the committee's own uncited assertions, attributed to the August 21 deck rather than stated as established fact.

Held only because another item in the 2026-09-10 batch was flagged. Nothing was filed against this one.

Source · 2026-08-21 ↗

verified No objection filed 2026-09-10

town-of-lysander-official-records

The Lysander Data Center Advisory Committee's August 28, 2026 deck opens, before any electricity content, with a two-slide 'Waste Water Recommendations' section that is the formalized output of the committee's wastewater phase. The recommendations are to reiterate the need for closed loop cooling systems; that the Planning Board must require a full environmental review for projects of this size or nature; that industrial users disclose any toxic chemicals used in their cooling systems and industrial processes during the environmental review process; that wastewater be treated and managed by WEP and the New York State DEC per their guidelines with no direct release to the environment; that a public-facing dashboard display current values and trends of potential wastewater pollutants including the items listed in the committee's August 21 meeting; and that used chemicals including coolants be properly recycled or disposed of per WEP, DEC and EPA guidelines. The dashboard recommendation carries an unresolved threshold, stating the requirement 'may be limited to industrial users who produce more than XXX gallons of wastewater in any given day, and those whose waste water contains PFAs above the ambient level already existing in the environment' - the placeholder is in the posted document, and the unit has shifted from the per-week basis used a week earlier to a per-day basis here. The file is named lysander_dc_committee_electricity_usage_8-28-26.pdf; the filename understates its contents, and the wastewater section was confirmed present by direct text extraction of that file this pass.

Proposed edit

Record the committee's six formalized wastewater recommendations as of August 28, 2026, including the unfilled gallons-per-day placeholder and the PFAs ambient-level test, noting that they are published inside the electricity-named deck.

Held only because another item in the 2026-09-10 batch was flagged. Nothing was filed against this one.

Source · 2026-08-28 ↗

verified No objection filed 2026-09-10

lysander-town-board-minutes

The agenda for the September 3, 2026 Lysander Town Board meeting, read in full this pass, schedules a 5:30 PM work session and a 6:30 PM regular meeting and carries twelve lettered motions, A through L. The work session items are a Gates Road speed study, the Brett Maring zone change, trooper barracks construction bids, and 'Battery Energy Storage Code' - the last placing the town's battery storage code on the board's own agenda, distinct from any data-center application. The agenda schedules adoption of the August 20, 2026 minutes and a public hearing on Clinton Heights Sewer District Extension No. 3 - Hanley. The lettered motions include forming Clinton Heights Sewer District No. 3, ordering a county and state speed and traffic study for Gates Road from Route 370 to Plainville Road, budget transfers, a special event license, and a sequence on the Maring petition for 9086 Oswego Road, Tax Map Number 024.-01-49.1, from Agricultural to General Business: declaring the Town Board lead agency for SEQR review with a stated negative declaration, referring the petition to the Lysander Planning Board, Zoning Board and Onondaga County Planning Board, and advertising an October 1, 2026 public hearing on it. Three further October 1, 2026 hearings are advertised, on the Maring zone change, on a local law overriding the General Municipal Law 3-c tax levy limit for 2027, and on the 2027 West Phoenix Fire Protection Agreement with Enterprise Fire Company No. 1 with the dollar amounts left blank. The agenda also authorizes the Supervisor to sign contract drawings for Timber Banks Phase 4 Section 10, advertises an October 15, 2026 hearing on the 2027 Preliminary Budget, and sets an October 22, 2026 special meeting at 5:00 PM to adopt the 2027 budget. No item on this agenda concerns a data storage facility application. Minutes of this meeting were not posted as of this retrieval.

Proposed edit

Add the September 3, 2026 Town Board agenda to the Lysander local timeline, recording the Battery Energy Storage Code work-session item and the October 1, October 15 and October 22, 2026 hearing and budget dates it sets, and noting that this agenda contains no data storage facility item and that its minutes are not yet posted.

Held only because another item in the 2026-09-10 batch was flagged. Nothing was filed against this one.

Source · 2026-09-03 ↗

reported Critic flagged 2026-09-10

responsible-data-center-development-act

A trade outlet reports a procedural posture for the Responsible Data Center Development Act that differs from the one currently recorded. In a June 15, 2026 article it states that the bill had not been sent to the Governor and that 'the legislature has until the end of the year to send it to her, and she has until the end of the year to choose whether to sign, amend or veto the bill.' The same article reports that Assemblyman Scott A. Gray and three Republican colleagues were urging a veto, quoting Gray that 'A statewide moratorium is the wrong answer to the right questions. It freezes investment, takes decisions away from the communities that should be making them,' and that Gray was promoting an alternative High Energy User Act addressing noise, water and power through regulatory standards instead. It further reports the Governor as having said data centers are 'a local decision for municipalities' and 'not a statewide approach necessarily.' None of this is a primary legislative record: the Senate and Assembly pages for A11560 and S10642 still show no dated delivery, signing, veto, chapter number or veto memo, and their status trackers show the delivery and signature checkpoints unmarked. The outlet's account and the unmarked tracker are consistent with each other, but neither establishes on its own that delivery has not occurred, and the article predates the current date by nearly three months.

Proposed edit

Soften the recorded status of the Responsible Data Center Development Act from 'delivered to the Governor' to passed-both-chambers-and-awaiting-delivery, attributing the end-of-year delivery and action windows to this reported account rather than to the legislature's own pages.

Critic findings against this item (2)

no-fabricationsource_url is a single govtech.com article dated 2026-06-15, but the summary also asserts a present-tense state of the legislature's own systems: that 'the Senate and Assembly pages for A11560 and S10642 still show no dated delivery, signing, veto, chapter number or veto memo, and their status trackers show the delivery and signature checkpoints unmarked.' Neither the bill numbers' tracker state nor the 'still' (as-of-this-pass) framing can come from a June article. The legislative-page check needs its own source_url and source_date.
evidence-label-accuracyA single 'reported' label is applied to an entry that mixes two evidence classes: the govtech account of Gray's veto push and the Governor's 'a local decision for municipalities' remark (correctly 'reported'), and a direct inspection of the Senate/Assembly status trackers presented as measured fact ('still show no dated delivery'), which is a 'verified'-class observation if it was actually performed this pass and 'unknown' if it was not. Split the entry so each class carries its own label and source.

Source · 2026-06-15 ↗

verified Critic flagged 2026-09-09

town-of-lysander-official-records

The Lysander Data Center Advisory Committee has produced a written set of wastewater recommendations, posted as a slide deck on the town's Data Center Information page. The deck titled 'Lysander Data Center Advisory Committee Meeting August 28th 2026' opens with a 'Waste Water Recommendations' section listing six items in the committee's own words: 'We reiterate the need for closed loop cooling systems'; 'The Planning Board must require a full environmental review for projects of this size or nature'; 'Require that Industrial Users disclose any toxic chemicals used in their cooling systems and industrial processes during the environmental review process'; 'Require that Waste Water is treated and managed by WEP and the NY State DEC per their guidelines, with no direct release to the environment'; 'Require a public facing dashboard displaying current values and trends of potential waste water pollutants', which the deck says 'may be limited to industrial users who produce more than XXX gallons of wastewater in any given day, and those whose waste water contains PFAs above the ambient level already existing in the environment'; and 'Require the Proper Recycling or Disposal of used Chemicals, including coolants, per WEP, DEC, and EPA guidelines'. The placeholder 'XXX' appears in the posted document, so no volume threshold has been fixed. These are recommendations of an advisory committee. Nothing in the posted record shows them adopted by the Town Board, incorporated into town code, or applied to any application, and the committee's own agenda for the same meeting lists the item as 'Formalize Waste Water Recommendations' under New Business.

Proposed edit

Add a subsection to the Lysander local-process entry recording the committee's six formalized wastewater recommendations as posted on August 28, 2026, quoted or closely paraphrased, and labeled explicitly as advisory-committee recommendations that carry no adopted legal effect, with the unfilled 'XXX' gallons-per-day threshold noted as still open.

Critic findings against this item (1)

no-fabricationThe summary attributes an opening 'Waste Water Recommendations' section (six quoted wastewater items, the 'XXX' gallons-per-day placeholder, PFAs language) to 'The deck titled Lysander Data Center Advisory Committee Meeting August 28th 2026', but the source_url is https://lysanderny.gov/sites/default/files/2026-08/lysander_dc_committee_electricity_usage_8-28-26.pdf — a file whose name indicates the electricity-usage deck. The checked notes and change_index 2/3 establish the committee posts dedicated wastewater decks under separate filenames (lysander_dc_committee_waste_water_8-07-26-26.pdf, an August 21 wastewater deck). It is not established that this electricity-named file contains the wastewater recommendations; per ambiguity-resolves-to-hold, the wastewater content does not plausibly trace to the cited electricity source_url.

Source · 2026-08-28 ↗

verified No objection filed 2026-09-09

town-of-lysander-official-records

The same August 28, 2026 committee deck sets out the committee's reading of what the Town can and cannot regulate on electricity, and identifies specific zoning levers it believes are available. On limits, the deck states 'The town does not manage or maintain the electric grid or electricity prices in any way' and 'The town has no say in power delivery or rates', and assigns roles to other bodies: the New York Independent System Operator operates the high-voltage grid and runs wholesale markets, the New York Power Authority and companies such as Constellation Energy own generation, National Grid owns the wires and does not generate power, the Public Service Commission sets delivery charges, service classifications and demand caps, and the operator sets supply charges. On available levers, the deck states the town 'can designate that any on-site or "behind the meter" electrical power generation over a specific threshold (say 5 Meagwatts) is a separate, prohibited land use', can limit on-site generation to emergency battery storage and blackout generators, can mandate security perimeters for high-voltage generation or specialized fuel systems, may be able to restrict high-voltage transmission switchyards within the zone, and can regulate generator size, operating hours, setbacks and noise through code and influence generator type through the Planning Board SEQRA process. It cites existing town code 320-51: 'There shall be no activities which emit radioactivity dangerous to health or adversely affecting the operation of any equipment.' The deck also records that the town has an existing moratorium on Battery Energy Storage Systems and is 'actively working on updating its BESS ordinance'. The 5 MW figure is presented in the deck as an illustrative threshold, prefaced by 'say', not as a settled number. The deck records priority scores the committee has assigned from a spreadsheet, including an overall electricity priority of 2.4 and 3.0 for 'Who pays for Infrastructure upgrades?'; the scale those scores sit on is not explained in the document.

Proposed edit

Add an electricity subsection to the Lysander local-process entry recording the committee's stated division of authority between the town, the grid operator, the utility and the Public Service Commission, and the specific zoning levers it identifies, with the 5 MW behind-the-meter figure marked as illustrative and the priority scores reported without interpreting the unexplained scale.

Held only because another item in the 2026-09-09 batch was flagged. Nothing was filed against this one.

Source · 2026-08-28 ↗

reported On the main site 2026-09-09

town-of-lysander-official-records

Published to the main site on 2026-09-12 under #status: ESD Community Investment Framework outline only, completed framework pending.

The August 28, 2026 committee deck asserts three physical characteristics of the proposed data center site in support of its on-site power discussion, none of which the deck sources to an underlying engineering or utility record. Under a slide headed 'Background', it states 'There are two separate major power transmission lines crossing at the site', that 'The second transmission line may mitigate the need for additional back up power, but that is unlikely', and that 'There is a large Natural Gas main running beneath the proposed data center site'. On nuclear generation it states that 'NRC guidelines for population density would prevent a large scale nuclear reactor at this site based on the combined population of Lysander, Van Buren, Salina, and Clay', without citing the guideline or the population figures relied on. Separately, the committee's August 21, 2026 wastewater deck states that 'The previously approved warehouse required water and sewer lines to be built out to the site', which is a claim about a prior approval on the same parcel rather than about the data center proposal. Each of these is a statement by a town advisory committee in a working presentation; no primary utility, transmission, pipeline or regulatory record supporting them was located this pass.

Proposed edit

Record the committee's site-characteristic assertions, two crossing transmission lines, a large gas main beneath the site, an NRC population-density constraint on a large reactor, and a prior warehouse approval that required water and sewer build-out, as committee-reported claims awaiting a primary record, and flag them as items to confirm against utility and county sources before the site treats any of them as established.

Critic findings against this item (1)

no-fabricationThe summary quotes 'The previously approved warehouse required water and sewer lines to be built out to the site' and explicitly attributes it to 'the committee's August 21, 2026 wastewater deck', a different document than the single source_url given (lysander_dc_committee_electricity_usage_8-28-26.pdf, the August 28 electricity deck). That August 21 warehouse/water-sewer claim, a specific named-prior-approval fact, does not trace to the cited source_url.

Source · 2026-08-28 ↗

verified Critic flagged 2026-09-09

lysander-town-board-minutes

The minutes of the August 20, 2026 Lysander Town Board meeting, now posted, contain the only account in the town's published record of what the Data Center Advisory Committee has been discussing, because no committee minutes are published anywhere on the town site. Under Town Board Comments the minutes state: 'Councilor Schmitt reported on the Data Center group, and that the last discussion was focused on wastewater and noise ordinance revisions. He touched on the battery energy storage discussion, and he liked Town of Clay's ordinance, that can be used as a template.' The same section records that 'Councilor Mangan thanked the group who came in to speak about Battery Energy Storage.' No resolution concerning data storage facilities, the moratorium or the committee appears among the numbered resolutions of that meeting, which cover stop-sign local laws, personnel, piggyback contracting and a parks budget amendment. The subsequent September 3, 2026 Town Board agenda, read in full, lists 'Battery Energy Storage Code' as a work-session item and carries no data-storage-facility application, no moratorium item and no zoning amendment directed at data centers among its twelve lettered motions; its public hearings concern a sewer district extension, a zone change at 9086 Oswego Road from Agricultural to General Business, a tax-levy-limit override, a fire protection agreement and the 2027 budget.

Proposed edit

Add the August 20, 2026 Town Board report on the Data Center Advisory Committee to the Lysander local-process entry as the town's only published narrative of committee proceedings, noting the wastewater and noise-ordinance focus and the councilor's reference to the Town of Clay battery-storage ordinance as a template, and note that neither the August 20 resolutions nor the September 3, 2026 agenda contains a data-storage-facility or moratorium item.

Critic findings against this item (1)

no-fabricationThe source_url is https://lysanderny.gov/sites/default/files/2026-09/8.20.26_meeting_minutes.pdf (the August 20 minutes), but the summary and proposed_change also carry specific facts from a separate document — the September 3, 2026 Town Board agenda: its 'twelve lettered motions', 'Battery Energy Storage Code' work-session item, and public hearings including 'a zone change at 9086 Oswego Road from Agricultural to General Business', a sewer district extension, a tax-levy-limit override, a fire protection agreement and the 2027 budget. Those September 3 agenda specifics do not trace to the August 20 minutes source_url; the agenda is a distinct document that is not cited.

Source · 2026-08-20 ↗

verified No objection filed 2026-09-09

new-york-executive-order-62

Empire State Development has published a policy outline for the Community Investment Framework that Executive Order No. 62 directs it to produce, and the outline proposes a numerical baseline for developer contributions. The document, headed 'Policy Outline for the New York State Data Center Community Investment Framework', states that under the Executive Order 'Within 60 days, ESD will post on its website a Community Investment Framework (CIF)' and describes the framework as covering Good Neighbor Commitments on landscaping, design and noise and light mitigation; Labor Commitments prioritizing prevailing wage standards, project labor agreements, local hiring and apprenticeships; a Community Investment Fund; and Transparency requirements for ongoing operator reporting on full-time on-site jobs, average salary, water and utility usage and energy demand, annual and cumulative tax revenue, construction workers used, funds invested and 'calculation of CIF investment provided in terms of dollars-invested-per-megawatt-demand'. On contribution levels it states that Empire State Development 'shall establish guidance related to contribution levels from data center operators, developed to create a minimum threshold for contributions, such as at $1 million in data center operator contribution per 1 megawatt (MW) of anticipated utility demand per project', described as 'a consistent starting point for negotiations' with final levels tailored to each host community. A table applies the ratio across eight rows from 50 MW at $50,000,000 to 400 MW at $400,000,000. The outline closes by inviting public feedback 'Over the next 30 days' to [email protected]. The document carries no printed date on its face; the file it was downloaded from is named CIF-Policy-Outline-071426.pdf, and it refers to the Executive Order issued July 14, 2026.

Proposed edit

Create an entry for the Empire State Development Community Investment Framework policy outline covering its four framework components and its proposed $1 million per megawatt of anticipated utility demand negotiation baseline with the 50-to-400 MW table, marking the $1 million per MW figure as a recommended starting point rather than a requirement, and noting that the document is undated on its face and that its date is taken from the filename and its reference to Executive Order No. 62.

Held only because another item in the 2026-09-09 batch was flagged. Nothing was filed against this one.

Source · 2026-07-14 ↗

verified On the main site 2026-09-09

new-york-executive-order-62

Published to the main site on 2026-09-12 under #status: ESD Community Investment Framework outline only, completed framework pending.

As of this retrieval the Empire State Development Community Investment Framework landing page carries only the policy outline, not the completed framework, and states that 'The completed framework will be released by mid-September.' The page links the outline as 'Policy Outline' pointing to CIF-Policy-Outline-071426.pdf and provides an email address for feedback rather than a dated comment deadline. Executive Order No. 62 was issued July 14, 2026 and directs Empire State Development to post the framework within sixty days, which falls in mid-September 2026. The framework is therefore an outstanding state deliverable at the time of this check, and its final contribution guidance may differ from the outline's proposed $1 million per megawatt baseline, which the outline itself words as 'such as at' that level.

Proposed edit

Record on the Executive Order 62 entry that the Community Investment Framework was still unpublished as of September 9, 2026, with only the policy outline posted and the agency page stating the completed framework will be released by mid-September, and mark it as a near-term item to re-check rather than treating the outline's figures as final.

Held only because another item in the 2026-09-09 batch was flagged. Nothing was filed against this one.

Source · 2026-09-09 ↗

verified Critic flagged 2026-09-08

psc-case-26-e-0045-large-load-interconnection

The order that created PSC Case 26-E-0045 sets procedural milestones that run well past the comment deadlines the tracked Department of Public Service event page displays. The Order Instituting Proceeding and Soliciting Comments was issued and effective February 12, 2026, at a session held in Albany that day, and its text was downloaded and read in full this pass. Ordering Clause 1 states that the proceeding is instituted 'to execute the Energize NY Development initiative.' Ordering Clause 2 set initial comments on the questions in the order's appendix for April 13, 2026 and reply comments for May 13, 2026, the deadlines later extended by the revised notice to May 13 and June 15, 2026. Ordering Clause 3 directs that 'Department of Public Service staff shall convene at least one public technical conference before December 31, 2026'. Ordering Clause 4 directs that staff 'shall prepare a whitepaper addressing the interconnection and related issues considered in this proceeding within one year of the issuance of this Order', that the whitepaper 'shall be informed by the technical conference in Ordering Clause 3, address the comments received in the responses to Ordering Clause 2, be subject to public notice and comment, and contain recommendations for the Commission's consideration.' Ordering Clause 5 provides that 'In the Secretary's sole discretion, the deadlines set forth in this Order may be extended', on a written request stating a justification and filed at least three days before the affected deadline. Three limits. The order fixes the whitepaper obligation as a period, one year from issuance, and prints no calendar date for it; deriving a date from the February 12, 2026 issuance would be a calculation rather than a reading of the record, and is not offered here. The technical conference is stated only as a deadline, before December 31, 2026, with no scheduled date, and no notice scheduling it was located this pass. And Ordering Clause 5 means every date in the order is extendable at the Secretary's discretion, which is not a hypothetical in this proceeding: the comment deadlines have already been extended once.

Proposed edit

Extend the Case 26-E-0045 entry beyond the comment deadlines to record the order's two later milestones as the order words them, a public technical conference before December 31, 2026 and a staff whitepaper within one year of the order's February 12, 2026 issuance subject to public notice and comment, and note that the Secretary may extend any of these deadlines and has already extended the comment deadlines once.

Critic findings against this item (1)

no-fabricationThe summary asserts 'the deadlines later extended by the revised notice to May 13 and June 15, 2026' and 'the comment deadlines have already been extended once'. Those two dates and the extension fact come from a separate revised notice, not from the February 12, 2026 Order Instituting Proceeding at source_url, whose Ordering Clause 2 is quoted here as setting April 13 and May 13, 2026. No URL or source_date for that revised notice is supplied anywhere in the entry, so the May 13 / June 15, 2026 figures do not trace to the cited document.

Source · 2026-02-12 ↗

verified No objection filed 2026-09-08

new-york-executive-order-62

Executive Order No. 62 carries an 'Interconnection, Reliability, and Cost Allocation' section with two deadlines and a directive to transmission owners that the site's current account of the order does not record. Its text, retrieved and read in full this pass, states: 'DPS is directed within sixty days to form a Data Center Interconnection Working Group to identify and resolve issues related to the interconnection of data centers, and other large loads, in order to support efficient interconnection of large new customers and the faithful compliance of "beneficiary pays" principles as related to network upgrade and resource adequacy costs.' The same section states: 'DPS is directed to convene the State's transmission owners to review their practices and methodologies for studying the system impacts of data centers, and other large loads in order to understand their sufficiency for the purpose of estimating and managing cost impacts, both as they relate to network upgrades and to supply.' It then states: 'DPS is directed to report to the Commission within ninety days.' The section closes by noting that data centers 'may also be subject to service classifications and requirements pertaining to data centers to be developed by DPS and as may be established by the Public Service Commission in the exercise of its discretion.' Four limits. The order states both obligations as periods, sixty days and ninety days, and prints no calendar dates; converting them would be a calculation, not a reading of the record, and none is offered here. The ninety-day report is a report to the Commission on the matters in this section and is a distinct instrument from the Generic Environmental Impact Statement report the order requires elsewhere, from the Empire State Development Community Investment Framework, and from the twelve-month Department of Environmental Conservation water report. No document evidencing formation of the Working Group, no membership list and no ninety-day report was located this pass, which does not establish that none exists. And the service-classification sentence is permissive on its face, describing what may be developed and what the Commission may establish in its discretion, not a requirement that any classification be adopted.

Proposed edit

Add the order's interconnection section to the Executive Order 62 entry, recording the sixty-day directive to form a Data Center Interconnection Working Group, the directive to convene the State's transmission owners on their large-load system-impact study practices, and the ninety-day report to the Commission, each stated as a period rather than a calendar date, with the note that no formation record or report has been located.

Held only because another item in the 2026-09-08 batch was flagged. Nothing was filed against this one.

Source · 2026-07-14 ↗

verified No objection filed 2026-09-08

new-york-executive-order-62

Executive Order No. 62 contains a separate water directive aimed at the adequacy of the state's water-withdrawal program rather than at any individual permit. Its 'Data Center Water Withdrawal Review and Report' section states that the Department of Environmental Conservation 'shall assess whether any new or amended regulations, policies, reporting, or guidance is necessary or appropriate to help ensure its water withdrawal program requirements, pursuant to 6 NYCRR Parts 601 and 602, accurately and completely reflect the water demands of large use customers in the State, including data centers.' It further states: 'No later than twelve months after the date of this order, DEC shall deliver a report setting forth the results of such assessment and an identification of the potential regulatory, policy, and guidance actions that are necessary or appropriate to address the concerns associated with the siting and operation of data centers in the State.' Three limits worth keeping on the page. This is a review of whether the withdrawal program's requirements capture large-use demand, together with a report identifying potential actions; it is not itself a regulation, a reporting requirement or a change to any permitted withdrawal volume, and nothing in it alters an existing water-withdrawal permit. The deadline is stated as a period, twelve months from the date of the order, with no calendar date printed. And the order does not say who receives the report or that it will be published, so whether it becomes a public record is not established by this text.

Proposed edit

Add the order's water directive to the Executive Order 62 entry as a distinct obligation: a Department of Environmental Conservation assessment of whether its 6 NYCRR Parts 601 and 602 water-withdrawal program requirements accurately reflect large-use demand including data centers, with a report on the assessment and potential regulatory, policy and guidance actions due within twelve months of the order, and note that this is a program review rather than a change to any permitted withdrawal volume.

Held only because another item in the 2026-09-08 batch was flagged. Nothing was filed against this one.

Source · 2026-07-14 ↗

verified No objection filed 2026-09-08

new-york-executive-order-62

Executive Order No. 62 defines the facilities it reaches, and the definition both narrows and expressly excludes categories the site's account of the 50 MW threshold does not currently carry. The order defines a data center as 'a facility or group of facilities located on the same site or contiguous sites used to house computer servers, associated components, or computing or telecommunications equipment for the storage, processing, distribution, and / or management of data.' It then lists three characteristics a covered facility's equipment has: that it is '(1) in facilities containing uninterruptible power supply systems, specialized cooling systems designed for high-density computing loads, and / or contain cybersecurity systems designed for secure digital infrastructure operations, (2) provide data storage, cloud computing, and/or content delivery to customers, internal operations, and/or affiliated business operations, oftentimes on a continuous twenty-four-hour cycle, and (3) consume or can consume 50 megawatts of energy or more.' The order then carves out categories: 'Provided, however, that a facility that is primarily used for manufacturing, research (including but not limited to quantum computing research or biomedical research), education (including but not limited to such facilities used by accredited colleges and universities in New York State, to the extent such colleges and universities are engaging in academic research, and the Empire AI consortium, or the institute, as defined in section three hundred sixty-one of the Economic Development Law), or the provision of medical care, is not covered by this definition and thus not subject to this Executive Order.' Three points of discipline. The 50 MW figure is a consumption threshold, stated as energy the facility consumes or can consume; it is not a requested interconnection capacity, a service capacity, a critical IT load or a metered load, and it should not be set alongside figures of those other kinds as though they were comparable. The exclusion is drawn by primary use, and the order names no facility as excluded or included, so the order's text alone does not classify any particular project. And the exclusion is written on the definition, meaning an excluded facility is outside the order entirely rather than merely outside the permitting abeyance.

Proposed edit

Replace the bare '50 MW threshold' shorthand in the Executive Order 62 entry with the order's own definition: the three listed equipment and use characteristics, the 50 MW figure identified as energy the facility consumes or can consume, and the exclusion of facilities primarily used for manufacturing, research, education or the provision of medical care, noting that the order classifies no named facility.

Held only because another item in the 2026-09-08 batch was flagged. Nothing was filed against this one.

Source · 2026-07-14 ↗

verified No objection filed 2026-09-08

new-york-executive-order-62

Executive Order No. 62 recites a figure for pending data-center demand in the interconnection queue that the site does not currently carry. The order's recitals state: 'as of May 2026, nearly 12 gigawatts (12,000 megawatts) of data center load requests are in the New York Independent System Operator interconnection queue with more than eight gigawatts entering the queue in 2025 alone, representing accelerating demand growth and a need for action.' A second recital states the state policy the order rests on: 'it is the policy of New York State that the cost of electric system upgrades required to provide electric utility service to large loads should not be paid for by every-day New Yorkers.' A third records that 'Energize NY Development, announced in the 2026 State of the State, directs the Public Service Commission to modernize how large energy consumers, including data centers, connect to the grid, while ensuring those consumers pay their fair share or supply their own power', which ties the order's naming of Case 26-E-0045 to that initiative. What is verified here is that the order states these things. On the queue figure specifically, three cautions belong on the page. It is a count of load requests in an interconnection queue, which is requested interconnection capacity and not service capacity, not operating load, not critical IT load and not metered load; queue entries are withdrawn as well as advanced, so the figure does not establish that 12 gigawatts of data-center load will be built or served. It is stated as of May 2026 and the order cites no underlying queue report, so the composition of the figure and any later revision of it were not located in the reviewed record. And the figure is statewide, so it cannot be attributed to any project, site or region, and must not be combined with Micron demand or with any individual project's figures.

Proposed edit

Add the order's recital figure to the Executive Order 62 entry as the state's stated basis for acting, described as nearly 12 gigawatts of data-center load requests in the New York Independent System Operator interconnection queue as of May 2026 with more than eight gigawatts entering in 2025, labeled as requested interconnection capacity statewide and not as service capacity, operating load or critical IT load.

Held only because another item in the 2026-09-08 batch was flagged. Nothing was filed against this one.

Source · 2026-07-14 ↗

verified Critic flagged 2026-09-08

responsible-data-center-development-act

The Assembly's own record for A11560 supplies the bill's scope and its threshold, and shows a legislative history that stops at June 4, 2026. The Assembly page states the bill 'Places a one year moratorium on the issuance of data center permits; requires utilities to establish an independent classification of service for large data centers; sets energy efficiency goals for data centers; provides for benefits for host communities; sets labor standards for the construction of data centers', and sets the threshold for a large data center at 'twenty megawatts or more'. Its action list runs 06/01/2026 referred to ways and means; 06/03/2026 reported, reported referred to rules, rules report cal.468, ordered to third reading rules cal.468; and 06/04/2026 passed assembly, delivered to senate, referred to rules, substituted for S10642, third reading cal.1787, passed senate, returned to assembly. The Senate page for S10642 shows the same substitution and ends at the same point. Four limits, and they matter. The Assembly action list contains no delivery-to-Governor entry, no signing and no veto, and shows no chapter number or veto memo; the Senate page for A11560 displays a 'Delivered to Governor' status indicator with the governor-signature step shown incomplete, but no dated action line corresponding to that delivery was located in either chamber's record. So as of this retrieval the bill's disposition is not established by the legislative record beyond having passed both houses, and no date on which the Governor's period to act began was located. The bill's twenty-megawatt threshold is lower than the fifty-megawatt threshold in Executive Order No. 62 and applies to a different mechanism, a moratorium on issuance of permits for one year as against the order's abeyance of incomplete Department of Environmental Conservation applications pending a Generic Environmental Impact Statement; the two must not be merged into a single threshold or a single moratorium. The bill's threshold as read here is the summary's phrase, not the operative definition read in the bill text, which was not retrieved this pass. And the vote figures on the Senate page, 43 ayes, 17 nays, 1 absent and 2 excused, differ from tallies of 44 to 16 in the Senate and 102 to 39 in the Assembly that circulate in law-firm commentary; the Assembly page returned no tallies to this retrieval, so the Assembly vote is not established here and the discrepancy is left open rather than resolved.

Proposed edit

Expand the Responsible Data Center Development Act entry with the Assembly record's statement of scope and its twenty-megawatt large-data-center threshold, contrast that threshold and the bill's one-year permit-issuance moratorium against Executive Order 62's fifty-megawatt threshold and permit abeyance without merging them, and state that as of September 8, 2026 neither chamber's action list records a delivery to the Governor, a signing, a veto, a chapter number or a veto memo.

Critic findings against this item (3)

no-fabricationsource_url is the nyassembly.gov page for A11560, but the summary sources specific figures and status from other pages and from uncited commentary: the vote figures '43 ayes, 17 nays, 1 absent and 2 excused' and the "'Delivered to Governor' status indicator" are attributed to 'the Senate page' (nysenate.gov S10642 / A11560), which is neither cited nor linked; and the competing tallies '44 to 16 in the Senate and 102 to 39 in the Assembly' are attributed only to unnamed 'law-firm commentary' with no source at all. Four vote counts and a disposition indicator in this summary cannot be checked against the one URL given.
evidence-label-accuracyThe entry is labeled evidence: 'verified', but the summary itself states that parts of it are not supported by a primary public record: the 44-to-16 and 102-to-39 tallies rest on 'law-firm commentary', and the twenty-megawatt threshold is conceded to be 'the summary's phrase, not the operative definition read in the bill text, which was not retrieved this pass'. A single 'verified' label is applied to a mixture that includes reported and not-located material; the commentary tallies at minimum are 'reported' and the operative threshold definition is 'unknown' for this pass.
no-absence-as-proofproposed_change directs the page to 'state that as of September 8, 2026 neither chamber's action list records a delivery to the Governor, a signing, a veto, a chapter number or a veto memo', while dropping the contrary observation the summary records one paragraph earlier — that the Senate page for A11560 'displays a "Delivered to Governor" status indicator with the governor-signature step shown incomplete'. As worded for publication, the absence of a dated action line reads as establishing that no delivery to the Governor has occurred, when the reviewed record contains an affirmative indicator that it has.

Source · 2026-06-04 ↗

verified Critic flagged 2026-09-08

lysander-town-board-minutes

The Town of Lysander board-meetings archive has extended into September 2026, and none of the September business concerns data storage facilities. Three September meetings are posted. A Planning Board meeting on Thursday, September 10, 2026 at 7:00 p.m., whose agenda was read directly, continues an August 13, 2026 public hearing on a major subdivision, Case No. 2026-001, Landmark Challenger, Melvin Farms on Hayes Road, and on a multi-family site plan review, Case No. 2023-008, Longview at Radisson on Longview Terrace and River Road; carries those two items plus a controlled site use, Case No. 2026-005, Landmark Challenger, Melvin Farms Phase 2 Lots 1 and 3, as old business; a minor subdivision, Case No. 2026-007, Edward Coulter at 769 Sprague Road, as new business; a zone change recommendation to the Town Board for Brett Maring and Maring Properties at 9086 Oswego Road from Agricultural to General Business; and a controlled site use for Zachary Butler at 2464 Lamson Road for information only. It states the next regular Planning Board meeting is Thursday, October 8, 2026. A Zoning Board of Appeals special meeting on Monday, September 14, 2026 at 5:00 p.m., whose agenda was also read directly, carries one substantive item, a zone change recommendation to the Town Board for Leo Duger at 8075 Plainville Road, plus review of the July 6, 2026 special meeting minutes. A Town Board meeting on September 3, 2026 is posted with an agenda and extra documents whose link titles cover a sewer district extension plan and report, Hanley sewer main extension contract drawings and an order approving that extension, a September budget transfer, a special event license, a zone change procedure and application, a Maring properties document and a Clinton Heights SEQRA resolution; that agenda's body was not read this pass, so its contents are described here only by the archive's link titles. Also posted are an August 31, 2026 Town Board special meeting whose only extra document is a draft bond resolution and August 20, 2026 Town Board minutes. Three limits. Reading agendas establishes what was scheduled, not what was decided, and no minutes for any September 2026 meeting are posted. The absence of a data-storage-facility item is what the moratorium would predict, since Local Law No. 4 bars the Town Board, Planning Board and Zoning Board of Appeals from accepting such applications while it is in force, so this is not evidence that interest in the site has lapsed. And no agenda item proposing to amend, extend or replace Local Law No. 4 appears on any of these September agendas, which does not establish that none is being prepared.

Proposed edit

Update the Lysander board-records entry to note that the archive now runs through a September 14, 2026 Zoning Board of Appeals special meeting, that the September 3, September 10 and September 14, 2026 agendas carry no data-storage-facility application and no item proposing to amend, extend or replace Local Law No. 4, and that no minutes for any September 2026 meeting and no minutes for any Data Center Advisory Committee meeting are posted.

Critic findings against this item (2)

no-fabricationsource_url is the Lysander board-meetings archive index, not the agenda documents the summary actually quarries. Case numbers and named private parties — 'Case No. 2026-001, Landmark Challenger, Melvin Farms on Hayes Road', 'Case No. 2026-007, Edward Coulter at 769 Sprague Road', 'Brett Maring and Maring Properties at 9086 Oswego Road', 'Zachary Butler at 2464 Lamson Road', 'Leo Duger at 8075 Plainville Road', the 7:00 p.m. and 5:00 p.m. meeting times — sit in individual agenda PDFs whose URLs are never given. The same entry also asserts the content of a document it does not cite at all: 'Local Law No. 4 bars the Town Board, Planning Board and Zoning Board of Appeals from accepting such applications while it is in force'. And proposed_change introduces a body, the 'Data Center Advisory Committee', that appears nowhere in the summary or in the cited source.
no-absence-as-proofThe opening sentence states as a finding that 'none of the September business concerns data storage facilities', and proposed_change repeats it flatly ('the September 3, September 10 and September 14, 2026 agendas carry no data-storage-facility application'). The summary later concedes that for the September 3, 2026 Town Board meeting 'that agenda's body was not read this pass, so its contents are described here only by the archive's link titles'. A categorical negative over three agendas is being drawn from two agendas read and one unread, i.e. from a gap in the reviewed record rather than from the record.

Source · 2026-09-08 ↗

verified On the main site 2026-09-07

new-york-executive-order-62

Published to the main site on 2026-09-12 under #status: ESD Community Investment Framework outline only, completed framework pending.

As retrieved on September 7, 2026, Empire State Development's Community Investment Framework page posts only a policy outline; no completed framework document is posted there. The page states that ESD 'is working to develop a Community Investment Framework (CIF) to help localities maximize the benefits of hosting data centers while addressing potential community impacts', that the framework 'will provide guidance on opportunities for community investment, including infrastructure improvements, workforce development, and enhancements to public services', and carries a single document link reading 'Click here to view the Policy Outline.' It gives an ESD address for public comment on the CIF. The page also carries the sentence 'The completed framework will be released by mid-September.' That sentence is an agency statement about a future action rather than a record of one, and taken on its own it is reported rather than verified; what is verified here is that the sentence appears on the page and that no completed framework is posted alongside it as of this retrieval. The page is undated and displays no last-updated stamp, so the date given below is the retrieval date, not a publication date. The framework's absence from this page means it was not located, which is not the same as its not existing at some other address.

Proposed edit

Record that as of September 7, 2026 ESD's Community Investment Framework page posts only a Policy Outline, with no completed framework document posted there, and that the page states the completed framework will be released by mid-September, labeling that release timing as an agency statement about a future action rather than an accomplished step.

Held only because another item in the 2026-09-07 batch was flagged. Nothing was filed against this one.

Source · 2026-09-07 ↗

verified No objection filed 2026-09-07

new-york-executive-order-62

The document linked from ESD's Community Investment Framework page as the Policy Outline was downloaded and its full text extracted this pass. It is titled 'Policy Outline for the New York State Data Center Community Investment Framework'. It opens by stating that in Executive Order No. 62 the Governor directed ESD to assist localities in analyzing and attaining economic benefits and mitigating potential negative effects of hosting a data center, and that 'Within 60 days, ESD will post on its website a Community Investment Framework (CIF).' It defines a CIF as a document that includes an example of a structured policy or agreement establishing how the developer will invest in and partner with the host community and workforce. It states that ESD 'shall prepare a Community Investment Framework template' covering four elements: Good Neighbor Commitments (landscaping, design, and mitigation of noise and light pollution); Labor Commitments (prevailing wage standards and project labor agreements for construction, local hiring, apprenticeships, workforce development); a Community Investment Fund of mutually-agreed investments, with eligible categories listed as public infrastructure improvements, community anchor institutions, housing initiatives, workforce development and training programs, childcare facilities, broadband expansion, public safety initiatives, school facility and educational enhancements, blight remediation, and other locally identified energy affordability and community development priorities; and Transparency, in the form of codified ongoing operator reporting on full-time on-site jobs, average salary, water and utility usage and energy demand, annual and cumulative tax revenue, construction workers utilized, funding invested into the CIF and its intended uses, a calculation of CIF investment in dollars-invested-per-megawatt-demand, and environmental impacts and mitigation actions. On contribution levels the outline states: 'As a baseline for negotiations, Empire State Development shall establish guidance related to contribution levels from data center operators, developed to create a minimum threshold for contributions, such as at $1 million in data center operator contribution per 1 megawatt (MW) of anticipated utility demand per project. This recommended contribution level is intended to provide local governments and developers with a consistent starting point for negotiations, while allowing the final investment levels and eligible uses of the Fund to be tailored to the unique needs, priorities, and circumstances of each host community.' A table follows with two columns headed 'Megawatts (MW)' and 'Recommended Community Investment Level', running 50 / $50,000,000, 100 / $100,000,000, 150 / $150,000,000, 200 / $200,000,000, 250 / $250,000,000, 300 / $300,000,000, 350 / $350,000,000, 400 / $400,000,000. Note on that table's capacity type: its own column header is the bare phrase 'Megawatts (MW)' and supplies no qualifier, and the only definition the document gives for the megawatt basis is in the threshold sentence immediately above it, 'anticipated utility demand per project'. The table's rows must therefore be reported as anticipated utility demand, not as interconnection capacity, service capacity, critical IT load or metered load, and the bare header should not be read as licensing any of those. The outline closes: 'Public Feedback: Over the next 30 days, members of the public may submit feedback on the CIF to [email protected]'. Three limits on what this document establishes. It is expressly an outline and describes the framework in the future tense throughout ('shall prepare', 'The Framework will include'). The $1 million per megawatt figure is a recommended minimum threshold and a starting point for negotiation, phrased 'such as at', not a requirement, and the document says so on its face. And no date is printed anywhere in the document body; the fragment '071426' appears only in the filename, which is not a printed date, so the date recorded below is the retrieval date.

Proposed edit

Record the CIF Policy Outline's four framework elements and its transparency reporting list, and its recommended negotiating baseline of $1 million per megawatt of anticipated utility demand per project, reproducing the table as anticipated utility demand from 50 MW / $50 million to 400 MW / $400 million in $50 million steps, stating on the table that its own column header is the unqualified phrase 'Megawatts (MW)' and that the anticipated-utility-demand basis comes from the threshold sentence above it; label the $1 million per megawatt level a recommended minimum and starting point for negotiation rather than a requirement, and note that the document is an outline pending the final framework and carries no printed date in its body.

Held only because another item in the 2026-09-07 batch was flagged. Nothing was filed against this one.

Source · 2026-09-07 ↗

reported No objection filed 2026-09-07

new-york-executive-order-62

A Governor's Office press release dated July 29, 2026, located during discovery this pass and not part of the tracked source set, states a duration for the data-center moratorium that the Executive Order's own text does not contain. The release reads: 'During the development of this GEIS, which will take up to a year, a moratorium will be in place and the Department of Environmental Conservation (DEC) will not issue any discretionary permits not already deemed complete.' The same release states that Empire State Development will 'issue a Community Investment Framework (CIF) within 60 days', notes that an outline is available on ESD's website and that the public is encouraged to submit feedback, and states: 'Additionally, the Governor is directing DPS to consider creating a New York Grid Acceleration Fund to require data centers to invest in the state's aging grid infrastructure and energy needs so all New Yorkers benefit from responsible development.' Both the duration sentence and the Grid Acceleration Fund sentence were confirmed by a second independent retrieval of the page with a differently worded request. The evidence class here is reported rather than verified, and the distinction matters. The order itself, re-read this pass at https://www.governor.ny.gov/executive-order/no-62-establishing-temporary-moratorium-data-centers-new-york-while-state-develops, fixes no term of years and ties the moratorium's end to the point when DPS submits its report of the final Generic Environmental Impact Statement and associated findings statement. 'Up to a year' is therefore the executive's own projection of how long that work will take, stated by a public official without an underlying document that sets it as a deadline, and it should not be presented as an expiration date or converted into one. Likewise the Grid Acceleration Fund is described as something DPS is being directed to consider, not as an established fund; no fund, tariff or docket for it was located in the record reviewed this pass, which is not evidence that none exists. This release also settles a question left open in the previous pass: the characterization of the moratorium as roughly a one-year pause, previously encountered only in law-firm commentary, does trace to a primary state publication, though as a projection rather than as a term set by the order.

Proposed edit

Record that a July 29, 2026 Governor's Office release states the Generic Environmental Impact Statement 'will take up to a year' with the moratorium in place during its development, presenting that as the executive's own projection and not as an expiration date, and noting that Executive Order 62 itself sets no term and ends the moratorium when DPS submits the final GEIS and findings statement; and record separately that the same release states the Governor is directing DPS to consider creating a New York Grid Acceleration Fund, describing it as under consideration rather than established.

Held only because another item in the 2026-09-07 batch was flagged. Nothing was filed against this one.

Source · 2026-07-29 ↗

verified No objection filed 2026-09-07

psc-case-26-e-0045-large-load-interconnection

Executive Order No. 62 names PSC Case 26-E-0045 by number as the proceeding through which the Department of Public Service is directed to examine data-center interconnection impacts. The order's text reads: 'The Department of Public Service (DPS) is directed to examine the impacts associated with the interconnection of data centers to the electric distribution network through its proceeding under Case 26-E-0045, Proceeding on Motion of the Commission to Address Interconnection Reforms for Large Loads.' That sentence was located by targeted search of the order's text and confirmed by a second independent retrieval of the page. This supersedes the weaker footing recorded in the previous pass, where the same linkage was carried only as a lead drawn from law-firm commentary. Two limits. The DPS event page tracked for this case, https://dps.ny.gov/event/response-comments-due-proceeding-motion-commission-address-interconnection-reforms-large, does not itself mention the executive order, the moratorium or a Generic Environmental Impact Statement, and its listed documents remain the order instituting the proceeding and a revised notice extending comment deadlines, so a reader consulting only that page would not find the connection; that is a gap in the DPS page rather than a conflict between the two records. And the order directs DPS to examine interconnection impacts through this docket, which is not the same as stating that the GEIS itself will be conducted inside this docket; no document reviewed this pass establishes which docket, if any, will carry the GEIS, and that question remains unanswered in the reviewed record.

Proposed edit

Record that Executive Order 62 names PSC Case 26-E-0045 as the proceeding through which DPS is directed to examine data-center interconnection impacts, citing the order rather than the DPS case page, and note that the tracked DPS event page for that case does not itself mention the order or the GEIS, and that the order does not state that the GEIS will be conducted within that docket.

Held only because another item in the 2026-09-07 batch was flagged. Nothing was filed against this one.

Source · 2026-07-14 ↗

verified No objection filed 2026-09-07

town-of-lysander-official-records

Re-issue of a finding previously held on phrasing and still not reflected on the site. The Town of Lysander has posted a notice cancelling the Data Center Advisory Committee meeting scheduled for September 4, 2026. On the town's Data Center Information page the item is titled '9-4-26 Data Center Advisory Committee Meeting - Cancelled', is dated September 3, 2026, and its complete body is one sentence: 'The 9-4-26 Data Center Advisory Committee Meeting is cancelled.' Unlike most items the town posts there it has no attached document. It is the newest item on that page, sitting above the August 27, 2026 entry that holds the 8-28-26 committee agenda and an electricity-usage presentation. What this establishes is narrow. It confirms that a September 4, 2026 committee meeting existed on the town's schedule and was cancelled. It does not establish why, whether the committee will reconvene, or when: the notice states none of that, and no rescheduled date and no agenda for the September 4 meeting appear anywhere on that page, so that meeting's intended subject matter is also not recorded there. Preceding this notice, the page shows committee agendas posted for July 10, July 17, July 24, July 31, August 7, August 14, August 21 and August 28, 2026. Those are posted agendas; no minutes for any committee meeting appear on that page, so the record reviewed does not establish that any of those meetings was held as scheduled. Each negative above is scoped to the reviewed record: these items were not located on the town's Data Center Information page, which does not establish that they do not exist in some other town record. As of this pass, four days after the cancelled date, no September 2026 committee agenda, presentation or minutes had been posted to that page.

Proposed edit

Record that the Town of Lysander posted a one-sentence notice on September 3, 2026 cancelling the September 4, 2026 Data Center Advisory Committee meeting, with no reason, no rescheduled date and no agenda for that meeting appearing on the Data Center Information page as of September 7, 2026; and describe the July 10 through August 28, 2026 committee series as posted agendas and presentations for which no minutes appear on that page, rather than as meetings confirmed to have been held.

Held only because another item in the 2026-09-07 batch was flagged. Nothing was filed against this one.

Source · 2026-09-03 ↗

verified Critic flagged 2026-09-07

terawulf-q1-2026-investor-presentation

TeraWulf's Form 10-Q for the quarter ended June 30, 2026, filed August 5, 2026, discloses that the site the company markets as Lake Hawkeye is held under a lease from Cayuga Operating Company LLC. The filing states that on August 12, 2025 the company entered a lease agreement 'related to the Company's Lake Hawkeye site in New York with a counterparty which is a related party due to control by a member of Company management', and that the lease covers 'a portion of Cayuga Lease Lessor's real property consisting of approximately 183 acres, including all structures, equipment, facilities and fixtures located thereon which the Company expects to use primarily for HPC datacenter operations.' The filing's exhibit index identifies the instrument as a 'Lease Agreement, dated August 12, 2025, by and between Cayuga Operating Company LLC and Lake Hawkeye LLC'. Terms disclosed: an initial term of 80 years with no renewal rights; prepaid rent of $95.0 million in common stock, issued as 18.6 million shares priced on a 15-day trailing VWAP, plus $3.0 million in cash, both during the year ended December 31, 2025; a proportionate share of the lessor's costs of owning and operating the remaining property; an option after the 50th anniversary for the company to buy the premises for $100, exercisable in the other direction by the lessor and its parent on the same terms; a further $100 purchase obligation the lessor may impose on a reasonable determination that the premises will be subject to material environmental damage arising from the company's use, any such sale being 'as is' 'where is'; reversion of buildings and improvements to the lessor at expiration; and classification of all three lease components, land, buildings and equipment, as finance leases because of the bargain purchase option, measured at a 7.5 percent discount rate. Three limits on what this establishes. The identification of this lessor with the Cayuga Operating Company named in the tracked NYSDEC Region 7 permit record rests on the matching entity name and the shared Cayuga Lake location, not on any cross-reference in either document; neither document names the other. Nothing in this filing states a water withdrawal, discharge or supply arrangement for the site, so the reduction of Cayuga Operating's authorized withdrawal from and discharge to Cayuga Lake from about 245 MGD to 1 MGD approved April 13, 2026 - a figure read not from this filing but from the tracked NYSDEC Region 7 page, https://dec.ny.gov/regulatory/permits-licenses/environmental-permits/regional-environmental-permits-information/region-7 - cannot be read as describing the data center's water use, cannot be attributed to the data center, and is not combined here with anything in this filing. And the approximately 183 leased acres is a land area governed by this lease, a separate measure from the 400 gross MW and 320 critical IT MW the tracked Q1 2026 deck shows for the same site; none of the three figures may be substituted for another. The tracked Q1 2026 investor presentation contains none of this lease disclosure.

Proposed edit

Record that TeraWulf's Form 10-Q of August 5, 2026 identifies the Lake Hawkeye site as approximately 183 acres leased from Cayuga Operating Company LLC to Lake Hawkeye LLC under an August 12, 2025 related-party lease with an 80-year initial term, $95.0 million of prepaid rent in stock plus $3.0 million cash, and a $100 purchase option after 50 years, expected to be used primarily for HPC datacenter operations; state that the link to the Cayuga Operating Company in the tracked DEC Region 7 record rests on entity name and location rather than a cross-reference, and state explicitly that no reviewed document establishes the site's water arrangement, so the DEC reduction from about 245 MGD to 1 MGD must not be presented as the data center's water use.

Critic findings against this item (2)

no-fabricationThe summary's specific figures and date 'from about 245 MGD to 1 MGD approved April 13, 2026' do not trace to source_url, which is the TeraWulf Form 10-Q (https://www.sec.gov/Archives/edgar/data/1083301/000108330126000166/wulf-20260630.htm) — the summary itself concedes the figure was 'read not from this filing'. The inline attribution given for it, https://dec.ny.gov/regulatory/permits-licenses/environmental-permits/regional-environmental-permits-information/region-7, is a general DEC regional permits information page, not the specific permit modification document that would carry a 245 MGD / 1 MGD authorization and an April 13, 2026 approval date. The same applies to '400 gross MW and 320 critical IT MW', cited to the 'tracked Q1 2026 deck' with no document URL at all. Either drop these cross-referenced figures from this entry or file them as separate entries whose source_url is the specific permit document and the specific investor deck.
distinguish-capacity-typesThe phrase "Cayuga Operating's authorized withdrawal from and discharge to Cayuga Lake from about 245 MGD to 1 MGD" attaches one figure pair to both a permitted withdrawal and a discharge at once, treating the two as a single interchangeable quantity. Permitted withdrawal and permitted discharge are distinct measures under this lens and must be stated as separate authorized values (or, if the underlying permit genuinely sets one number for each, stated as two explicitly labeled figures) rather than merged into a single '245 MGD to 1 MGD' reduction covering both directions.

Source · 2026-08-05 ↗

verified On the main site 2026-09-06

new-york-executive-order-62

Published to the main site on 2026-09-12 under #status: ESD Community Investment Framework outline only, completed framework pending.

Empire State Development has published a Policy Outline for the New York State Data Center Community Investment Framework, and has posted a standing page stating that the completed framework is still to come. Executive Order No. 62 directs ESD to post a Community Investment Framework on its website within 60 days. ESD's page at esd.ny.gov/communityinvestmentframework, retrieved this pass, describes the CIF as a tool to help localities maximize the benefits of hosting data centers while addressing community impacts, states 'The completed framework will be released by mid-September.', links to the Policy Outline, and gives [email protected] for comments. The linked Policy Outline PDF, whose filename carries the date 071426, was downloaded and read in full. It describes a CIF as a document establishing how a developer will invest in and partner with the host community and workforce. It states that ESD shall prepare a CIF template covering Good Neighbor Commitments (landscaping, design, mitigation of noise and light pollution); Labor Commitments (prevailing wage standards, project labor agreements, local hiring, apprenticeships, workforce development); a Community Investment Fund whose eligible investments may include public infrastructure improvements, community anchor institutions, housing initiatives, workforce development and training, childcare facilities, broadband expansion, public safety initiatives, school facility and educational enhancements, blight remediation and other locally identified energy affordability and community development priorities; and Transparency, in the form of codified ongoing public reporting by the operator on full-time on-site jobs, average salary, water and utility usage and energy demand, annual and cumulative tax revenue, construction workers used, funding invested into the CIF and its intended uses, the investment expressed as dollars invested per megawatt of demand, and environmental impacts and mitigation actions. On contribution levels the outline states that ESD shall establish guidance creating a minimum threshold, 'such as at $1 million in data center operator contribution per 1 megawatt (MW) of anticipated utility demand per project', described as a consistent starting point for negotiations with final investment levels and eligible uses tailored to each host community. It carries a table running from 50 MW at $50,000,000 to 400 MW at $400,000,000 in $50,000,000 steps. It closes by inviting public feedback over the following 30 days to [email protected]. Three limits on what this establishes. The outline is expressly an outline and repeatedly describes the framework in the future tense; the completed CIF was not posted on ESD's page as retrieved this pass. The $1 million per megawatt figure is stated as a recommended baseline for negotiation, not as a requirement, and the outline says so on its face. And the 60-day deadline is not printed as a date in these documents; counting 60 days from the order's July 14, 2026 effective date gives September 12, 2026, and ESD's own page says only 'mid-September'.

Proposed edit

Record that ESD has published a CIF Policy Outline and that the completed Community Investment Framework required by Executive Order No. 62 has not yet been posted, with ESD's page stating it will be released by mid-September; note the outline's recommended negotiating baseline of $1 million per megawatt of anticipated utility demand and its table from 50 MW / $50 million to 400 MW / $400 million, labeling the figure a recommended starting point rather than a requirement, and note that the outline is an outline pending the final framework.

Critic findings against this item (4)

no-fabricationThe summary asserts "Executive Order No. 62 directs ESD to post a Community Investment Framework on its website within 60 days" and later "the order's July 14, 2026 effective date", but source_url is https://esd.ny.gov/communityinvestmentframework, the ESD Community Investment Framework landing page. Nothing in the entry says that page states the 60-day directive or the order's effective date. The July 14, 2026 date is in fact inferred from the outline PDF's filename fragment "071426", which the summary itself notes; a date read off a filename is not the same as the effective date printed in the order. Cite the Executive Order text itself for both the 60-day directive and the effective date, or drop them.
no-fabricationThe bulk of the summary's specifics - the Good Neighbor / Labor / Community Investment Fund / Transparency headings, the quoted threshold "such as at $1 million in data center operator contribution per 1 megawatt (MW) of anticipated utility demand per project", the 50 MW / $50,000,000 to 400 MW / $400,000,000 table, and the 30-day feedback window - come from the linked Policy Outline PDF, not from the page given as source_url. The entry records only that the PDF's filename carries "071426"; it gives no URL for the document those figures were read from, so the cited source does not plausibly contain them. Add the Policy Outline PDF's own URL as the source for these figures.
evidence-label-accuracyThe entry is labeled `verified`, but it contains a derived figure presented alongside the primary-record material: "counting 60 days from the order's July 14, 2026 effective date gives September 12, 2026". September 12, 2026 is a calculation resting on an effective date that the summary itself concedes is "not printed as a date in these documents". Within a `verified` entry that computed deadline needs its own `estimated` labeling, or it should be removed in favor of ESD's own published wording, "mid-September".
distinguish-capacity-typesThe quoted threshold is tied to a specific capacity type - "per 1 megawatt (MW) of anticipated utility demand per project" - but the table is then reported with bare megawatts: "a table running from 50 MW at $50,000,000 to 400 MW at $400,000,000", and proposed_change repeats it as "its table from 50 MW / $50 million to 400 MW / $400 million" with no capacity type at all. As drafted the site would carry MW figures that a reader could take as interconnection capacity, service capacity or critical IT load. State the capacity type on the table rows as the outline states it.

Source · 2026-09-06 ↗

verified No objection filed 2026-09-06

town-of-lysander-official-records

Re-issue of a finding held on phrasing. The Town of Lysander has posted a notice cancelling the Data Center Advisory Committee meeting scheduled for September 4, 2026. On the town's Data Center Information page the item is titled '9-4-26 Data Center Advisory Committee Meeting - Cancelled', is dated September 3, 2026, carries no department label, and its complete body is one sentence: 'The 9-4-26 Data Center Advisory Committee Meeting is cancelled.' Unlike most items the town posts, it has no attached document. It is the newest item on that page, sitting above the August 27, 2026 entry that holds the 8-28-26 committee agenda and an electricity-usage presentation. What this establishes is narrow. It confirms that a September 4, 2026 committee meeting existed on the town's schedule and was cancelled. It does not establish why, whether the committee will reconvene, or when: the notice states none of that, no rescheduled date is posted on that page, and no agenda for the September 4 meeting is posted on that page, so its intended subject matter is also not recorded there. Preceding this notice, the page shows committee agendas posted for July 10, July 17, July 24, July 31, August 7, August 14, August 21 and August 28, 2026. Those are posted agendas; the page carries no minutes for any committee meeting, so the record reviewed does not establish that any of those meetings was held as scheduled.

Proposed edit

Record that the Town of Lysander posted a one-sentence notice on September 3, 2026 cancelling the September 4, 2026 Data Center Advisory Committee meeting, with no reason, no rescheduled date and no agenda for that meeting appearing on the Data Center Information page; and describe the July 10 through August 28, 2026 committee series as posted agendas and presentations, for which no minutes appear on that page, rather than as meetings confirmed to have been held.

Held only because another item in the 2026-09-06 batch was flagged. Nothing was filed against this one.

Source · 2026-09-03 ↗

verified Critic flagged 2026-09-05

town-of-lysander-official-records

The Town of Lysander has posted a notice cancelling the Data Center Advisory Committee meeting scheduled for September 4, 2026. On the town's Data Center Information page the item is titled '9-4-26 Data Center Advisory Committee Meeting - Cancelled', is dated September 3, 2026, carries no department label, and its complete body is one sentence: 'The 9-4-26 Data Center Advisory Committee Meeting is cancelled.' Unlike most items the town posts, it has no attached document. It is the newest item on that page, sitting above the August 27, 2026 entry that holds the 8-28-26 committee agenda and an electricity-usage presentation. What this establishes is narrow. It confirms that a September 4, 2026 committee meeting existed on the town's schedule and was cancelled. It does not establish why, whether the committee will reconvene, or when: the notice states none of that, no rescheduled date is posted, and no agenda was ever posted for the September 4 meeting, so its intended subject matter is also unknown. Preceding this notice, the page shows committee agendas posted for July 10, July 17, July 24, July 31, August 7, August 14, August 21 and August 28, 2026. Those are posted agendas; the page carries no minutes for any committee meeting, so the record does not establish that any of those meetings was held as scheduled.

Proposed edit

Record on the local timeline that the Town of Lysander posted a one-sentence notice dated September 3, 2026 cancelling the September 4, 2026 Data Center Advisory Committee meeting, giving no reason and no rescheduled date, and that this follows a run of committee agendas posted weekly from July 10 through August 28, 2026 for which no minutes have ever been published.

Critic findings against this item (1)

no-absence-as-proofTwo unscoped absolute negatives assert non-existence rather than non-location. The summary says 'no agenda was ever posted for the September 4 meeting', and the proposed_change says the July 10 - August 28 committee agendas are ones 'for which no minutes have ever been published'. The rest of the entry scopes its negatives correctly to the reviewed record ('the page carries no minutes for any committee meeting', 'no rescheduled date is posted'), but 'was ever posted' / 'have ever been published' claim publication never occurred anywhere, which the reviewed page cannot establish. Rephrase to the located-record form, e.g. 'no agenda for the September 4 meeting is posted on that page' and 'for which no minutes appear on the Data Center Information page'.

Source · 2026-09-03 ↗

verified No objection filed 2026-09-05

town-of-lysander-official-records

A correction to a finding filed in the previous pass and still pending review. That pass reported that the town's /notices index dates the data-center meeting cancellation September 1, 2026 and files it under the department heading 'Fire Department', and treated the resulting mismatch with the September 3 date shown elsewhere as an unresolved discrepancy. Reading the index page's HTML directly, the table row for the cancellation notice has an empty department-and-date cell. The September 1, 2026 date and the Fire Department heading belong to the following row, the 9-18-2026 Plainville Fire District Workshop, and were misread across the row boundary. On the notices index the cancellation notice therefore carries no date and no department at all. There is no date discrepancy between the town's pages, and no mis-categorization of this item.

Proposed edit

Do not record a date discrepancy or a Fire Department mis-categorization for the data-center meeting cancellation notice; the notices index shows that item with no date and no department, and the September 1 date and Fire Department label belong to the adjacent Plainville Fire District item.

Held only because another item in the 2026-09-05 batch was flagged. Nothing was filed against this one.

Source · 2026-09-05 ↗

verified No objection filed 2026-09-05

lysander-town-board-minutes

The agenda for the September 3, 2026 Lysander Town Board meeting was downloaded and read in full. It sets a 5:30 PM work session and a 6:30 PM regular meeting at 8220 Loop Road. The work session lists four topics: Gates Road Speed Study, Zone Change Brett Maring, Trooper Barracks Construction Bids, and Battery Energy Storage Code. The regular meeting includes a public hearing on the Clinton Heights Sewer District Extension No. 3 - Hanley and adoption of the August 20, 2026 minutes. Three of the listed agenda items concern a zone change petition from Brett Maring for property at 9086 Oswego Road, Baldwinsville, Tax Map Number 024.-01-49.1, from Agricultural to General Business: item E would declare the Town Board lead agency for SEQR review and records that the board has determined a negative declaration; item F would refer the petition to the Lysander Planning Board, the Lysander Zoning Board and the Onondaga County Planning Board; item G would authorize advertising a public hearing before the Town Board at 6:30 PM on Thursday, October 1, 2026 on the petition. Two further items would set October 1, 2026 hearings on a local law overriding the tax levy limit for 2027 and on the 2027 West Phoenix Fire Protection Agreement, and later items would set an October 15, 2026 hearing on the 2027 preliminary budget and an October 22, 2026 special meeting to adopt the 2027 budget. Every one of these is drafted as an unexecuted motion, with blank lines for the moving and seconding councilors. The agenda establishes what was placed before the board, not what the board did. No minutes for the September 3, 2026 meeting have been posted, so whether any of these motions was adopted, amended or withdrawn is not on the public record. The agenda contains no item concerning data centers or the data-storage moratorium; the nearest related item is the Battery Energy Storage Code work-session topic, which the agenda names without further description. This restates a finding filed in the September 3 pass, which attributed the same content to the board-meetings archive index rather than to the agenda document that contains it.

Proposed edit

Record from the September 3, 2026 Town Board agenda that the board was asked to take lead agency for SEQR on the Brett Maring Agricultural-to-General-Business zone change at 9086 Oswego Road with a negative declaration, to refer it to the town Planning and Zoning Boards and the county Planning Board, and to advertise an October 1, 2026 public hearing on it, and that Battery Energy Storage Code was a work-session topic; and state explicitly that these are agenda motions rather than adopted actions, since no minutes for that meeting have been posted.

Held only because another item in the 2026-09-05 batch was flagged. Nothing was filed against this one.

Source · 2026-09-03 ↗

verified Critic flagged 2026-09-04

town-of-lysander-official-records

The Town of Lysander has posted a notice cancelling the Data Center Advisory Committee meeting scheduled for September 4, 2026. The notice is titled '9-4-26 Data Center Advisory Committee Meeting - Cancelled' and its complete body text is one sentence: 'The 9-4-26 Data Center Advisory Committee Meeting is cancelled.' It carries no attached document, unlike most items the town posts. It appears in all three of the town's posting locations and is the newest item on both the /notices index and the /notices/data-center-information subpage. The two pages disagree on its date: the notices index lists it under Sep 1, 2026 while the data-center subpage lists it under Sep 3, 2026, with title and body text identical in both places. Which date reflects actual posting is not established by the record, and the discrepancy is stated here rather than resolved. The notices index also categorizes the item under the department heading 'Fire Department', which is inconsistent with its subject; comparable mis-categorization of data-center items on this index has been recorded in prior passes. Two points bear on how much this establishes. It confirms that a September 4, 2026 committee meeting existed on the town's calendar, which the prior pass could not determine, since committee agendas had run weekly from July 10 through August 28 and no September agenda had been posted. It does not establish why the meeting was cancelled, whether the committee will reconvene, or when; the notice states none of that, no rescheduled date is posted, and no such inference is available from this record. No agenda was ever posted for the September 4 meeting, so its intended subject matter is also unknown.

Proposed edit

Record on the local timeline that the Town of Lysander cancelled the September 4, 2026 Data Center Advisory Committee meeting by a one-sentence notice giving no reason and no rescheduled date, ending the committee's unbroken weekly run of meetings from July 10 through August 28, 2026, and note that the town's two posting locations date the notice differently, September 1 on the notices index and September 3 on the data-center subpage.

Critic findings against this item (2)

no-fabricationThe summary asserts two facts about the /notices index page — that it 'lists it under Sep 1, 2026' and that it 'categorizes the item under the department heading \'Fire Department\'' — but source_url is https://lysanderny.gov/notices/data-center-information, the data-center subpage. The subpage cannot contain the notices-index's own date field or department heading, so those two figures/labels do not trace to the cited source_url. The date discrepancy is the load-bearing claim of the entry and half of it is unsourced by the URL given.
evidence-label-accuracyThe proposed_change is labeled evidence 'verified' but states the cancellation ends 'the committee's unbroken weekly run of meetings from July 10 through August 28, 2026.' What the record verifies is an unbroken run of posted agendas and presentations; the same pass's own note states the committee 'has still never posted minutes for any of its meetings.' Whether those meetings were actually held is not in the primary record, so 'unbroken weekly run of meetings' is an inference presented as verified fact. The summary itself is careful here ('committee agendas had run weekly'); the proposed_change silently upgrades agendas to meetings.

Source · 2026-09-03 ↗

verified Critic flagged 2026-09-04

lysander-town-board-minutes

Minutes for the August 20, 2026 Lysander Town Board meeting have been posted to the board-meetings archive at https://lysanderny.gov/sites/default/files/2026-09/8.20.26_meeting_minutes.pdf and were retrieved and read in full this pass. They are the first minutes for any August 2026 meeting to appear on the archive; prior passes recorded the July 16 and July 31 sets as the most recent. The minutes are signed by Town Clerk Dina Falcone and record all four board members present, Supervisor Kevin Rode and Councilors Vince Mangan, Ed Schmitt and Jeffrey Kudarauskas, with the meeting called to order at 6:37 PM and adjourned at 7:27 PM. Two data-center-related statements are recorded, both in the Town Board Comments section, and both are reports of what members said rather than actions the board took. Councilor Schmitt reported on the Data Center group and stated that its last discussion focused on wastewater and noise ordinance revisions, which corresponds to the subject matter of the committee's posted August presentations. He also touched on the battery energy storage discussion and stated that he liked the Town of Clay's ordinance and that it can be used as a template. Councilor Mangan thanked the group who came in to speak about Battery Energy Storage. No resolution, local law or referral concerning data centers, the data-storage moratorium or battery energy storage appears anywhere in the minutes. The twelve resolutions adopted, numbered 179 through 191 of 2026, concern stop-sign local laws at Mercer, Afternoon, Giddings and Springwoods Circle, adoption of the August 6 minutes, a Town Clerk's Office resignation and hiring, authorization to use piggyback contracting clauses on six county and state contracts, and a $68,000 budget amendment for Ninja Course cost overruns. One absence is worth stating precisely. The posted agenda for this meeting listed 'Noise/Battery Energy Storage/Microgrid Networks' as the first work session item, as recorded in the August 28 pass. These minutes begin with the 6:37 PM call to order of the regular meeting and contain no record of the work session. Whatever was discussed under that agenda item is therefore still not on the public record, and the two comments quoted above are the only trace of it in the minutes.

Proposed edit

Add the August 20, 2026 Town Board minutes to the local record, noting that the board took no data-center or battery-storage action and that the only related content is two members' comments, Councilor Schmitt reporting that the Data Center group's last discussion covered wastewater and noise ordinance revisions and that he considers the Town of Clay's battery energy storage ordinance a usable template, and Councilor Mangan thanking residents who spoke on battery energy storage; and record that the agenda's 'Noise/Battery Energy Storage/Microgrid Networks' work session item is not covered by the minutes, which begin at the regular meeting.

Critic findings against this item (1)

no-fabricationThe summary states that 'The posted agenda for this meeting listed \'Noise/Battery Energy Storage/Microgrid Networks\' as the first work session item,' and the proposed_change repeats it as a recorded fact. source_url is the minutes PDF (8.20.26_meeting_minutes.pdf), which the same paragraph says contains no record of the work session — so the agenda text cannot trace to it. The claim is sourced only to 'the August 28 pass,' not to the cited document. It needs the agenda's own URL as the source for that element.

Source · 2026-08-20 ↗

verified Critic flagged 2026-09-04

lysander-town-board-minutes

A September 10, 2026 Codes / Planning / Zoning entry has appeared on the Town of Lysander board-meetings archive that was not present in the prior pass, holding a Planning Board agenda at https://lysanderny.gov/sites/default/files/2026-09/91026pb_0.pdf and a meeting-materials packet at https://lysanderny.gov/sites/default/files/2026-09/9102026pb.pdf. Both are scanner-produced image PDFs with no extractable text layer; the agenda was rendered to an image and read visually this pass, while the materials packet, at roughly 20 MB, was not read and its contents remain unknown. Both files carry internal creation timestamps of September 3, 2026, at 13:54 and 14:01 UTC respectively, which is after the prior pass ran and is consistent with their appearing only now. The agenda sets a Planning Board meeting at 8220 Loop Road for 7:00 p.m. on Thursday, September 10, 2026. It opens with a public hearing continued from August 13, 2026 on two items, Major Subdivision Case No. 2026-001, Landmark Challenger, Melvin Farms on Hayes Road, and Site Plan Review-Multi Family Case No. 2023-008, Longview at Radisson, Longview Terrace and River Road. Old business carries those two forward and adds Controlled Site Use Case No. 2026-005, Landmark Challenger, Melvin Farms Phase 2, Lots 1 and 3. New business is a single item, Minor Subdivision Case No. 2026-007, Edward Coulter, 769 Sprague Road. Under other business the agenda lists a Recommendation to Town Board on a Zone Change from Agricultural to General Business for Maring, Brett / Maring Properties at 9086 Oswego Road. An information-only item lists Controlled Site Use, Case No. TBD, Zachary Butler, 2464 Lamson Road. The next regular Planning Board meeting is stated as October 8, 2026. The Maring item is the direct continuation of a thread recorded in the prior pass: the September 3, 2026 Town Board agenda carried a motion referring that same petition, identified there by the 9086 Oswego Road address and Tax Map Number 024.-01-49.1, to the Lysander Planning Board, the Zoning Board and the Onondaga County Planning Board, alongside a motion advertising a Town Board public hearing for October 1, 2026. The Planning Board agenda states no intended use for the parcel and makes no reference to a data center, and the agenda contains no data-center, data-storage-moratorium or battery-storage item of any kind. No connection between this rezoning and any data-center proposal is asserted here, and none is available from the documents read.

Proposed edit

Add the September 10, 2026 Lysander Planning Board meeting to the local-record timeline, recording that the board will take up the Brett Maring / Maring Properties zone change at 9086 Oswego Road from Agricultural to General Business as a recommendation to the Town Board, following the Town Board's September 3 referral and ahead of its October 1, 2026 public hearing, and stating that the agenda lists no data-center, moratorium or battery-storage item and no intended use for the parcel.

Critic findings against this item (1)

no-fabricationsource_url is the Planning Board agenda PDF (91026pb_0.pdf), but the summary attributes to the record several specifics that page does not contain: the September 3, 2026 Town Board referral motion, the parcel's 'Tax Map Number 024.-01-49.1,' the referrals to the Zoning Board and the Onondaga County Planning Board, and the 'Town Board public hearing for October 1, 2026.' The summary concedes the Planning Board agenda 'states no intended use for the parcel,' confirming those details come from a different document. The proposed_change then asserts the October 1, 2026 hearing date flatly, citing only this agenda URL.

Source · 2026-09-10 ↗

verified Critic flagged 2026-09-04

lysander-town-board-minutes

The September 3, 2026 Town Board entry on the board-meetings archive now carries nine supporting documents rather than the six recorded in the prior pass. The three additions are seqra_resolution_of_the_town_of_lysander-clinton_heights.pdf, sewer_district_extension_plan_and_report_08-05-26_002.pdf and hanley_order_approving_sewer_district_extension.pdf, all served from the 2026-09 file directory. All three relate to the Clinton Heights Sewer District Extension No. 3 - Hanley public hearing that the September 3 agenda listed as its sixth regular-meeting item, and the file names indicate a SEQR resolution, an updated plan and report dated August 5, 2026, and an order approving the district extension. The documents themselves were not retrieved and read this pass, so their contents are not characterized here beyond what the file names state. None of the three relates to a data center, the data-storage moratorium or the Maring zone change. The addition is recorded because the entry's document set changed, not because it bears on the data-center subject.

Proposed edit

Update the September 3, 2026 Town Board entry in the local record to reflect nine supporting documents rather than six, the three additions being a SEQR resolution, an August 5, 2026 plan and report, and an order approving the extension, all concerning the Clinton Heights Sewer District Extension No. 3 - Hanley and none concerning data centers.

Critic findings against this item (2)

evidence-label-accuracyLabeled 'verified,' but the summary states the documents 'were not retrieved and read this pass' and that their subject matter is known only because 'the file names indicate' it. The entry nonetheless characterizes their contents as established: 'All three relate to the Clinton Heights Sewer District Extension No. 3 - Hanley,' 'an updated plan and report dated August 5, 2026,' and 'None of the three relates to a data center, the data-storage moratorium or the Maring zone change.' Filename inference about unread PDFs is not a primary record directly supporting those statements. What is verified is that three files with those names were added to the September 3 entry; the content characterization is not.
evidence-label-accuracyThe proposed_change drops the filename caveat that the summary carries and states the additions as measured fact: 'the three additions being a SEQR resolution, an August 5, 2026 plan and report, and an order approving the extension.' Written into the wiki in that form, an unread-document inference becomes an unqualified verified record entry. It should read as 'three files whose names indicate...' or the documents should be retrieved before the change lands.

Source · 2026-09-03 ↗

verified Critic flagged 2026-09-03

lysander-town-board-minutes

The Town Board meetings archive at https://lysanderny.gov/board-meetings now carries a September 3, 2026 Town Board entry that does not appear in the records of any prior pass. The archive lists against it an agenda at https://lysanderny.gov/sites/default/files/2026-09/9-3-2026_agenda.pdf and six supporting documents: september_budget_transfer_.pdf, sewer_district_extension_plan_and_report_07-24-26.pdf, hanley_sewer_main_ext_contract_drawings_07-28-26.pdf, special_event_license_annals_angels_2026.pdf, zone_change_procedure_and_application.pdf and maring_properties_rev.pdf. The last three of those are served from a 2026-09 file directory that did not exist in prior passes. The agenda document itself was retrieved and its text extracted, and everything that follows is read off that document. It sets a meeting at 8220 Loop Road on Thursday, September 3, 2026, with a work session at 5:30 PM and the regular meeting at 6:30 PM. The work session lists four topics: Gates Road Speed Study, Zone Change Brett Maring, Trooper Barracks Construction Bids, and Battery Energy Storage Code. The regular meeting's fifth item is adoption of minutes for August 20, 2026, and no other meeting's minutes are listed for adoption. Its sixth item is a public hearing on Clinton Heights Sewer District Extension No. 3 - Hanley. Three lettered motions concern a zone change petition received from Brett Maring for property at 9086 Oswego Road, Baldwinsville, Tax Map Number 024.-01-49.1, from Agricultural to General Business: one would declare the Town Board lead agency for SEQR review and states the board has determined a negative declaration; one would refer the petition to the Lysander Planning Board, the Zoning Board and the Onondaga County Planning Board; and one would authorize advertising a public hearing before the Town Board at 6:30 PM on Thursday, October 1, 2026. Further motions would advertise October 1, 2026 hearings on a local law to override the tax levy limit established in General Municipal Law 3-c for 2027 and on a 2027 fire protection agreement with Enterprise Fire Company No. 1, an October 15, 2026 hearing on the 2027 Preliminary Budget, and a special meeting on October 22, 2026 at 5:00 PM to consider adoption of the 2027 budget. Two absences are worth stating precisely, because both bear on the subject this record is tracked for and neither should be read as more than an absence. The agenda contains no reference to a data center, to the data-storage moratorium or to the Data Center Advisory Committee; its only energy-infrastructure item is the Battery Energy Storage Code work-session topic, which the agenda does not describe further. And the zone change is identified in the agenda solely by the 9086 Oswego Road address and tax map number and by the Agricultural to General Business change; the agenda states no intended use and makes no connection to any data-center proposal, so none is asserted here. The two supporting documents specific to the petition, zone_change_procedure_and_application.pdf at 10 pages and maring_properties_rev.pdf at 1 page, are scanner-produced image PDFs from which no text could be extracted this pass, so what they contain has not been read.

Proposed edit

Add the September 3, 2026 Town Board meeting to the local-record timeline, recording the Battery Energy Storage Code work-session item, the Brett Maring zone change at 9086 Oswego Road from Agricultural to General Business with its negative declaration and October 1, 2026 public hearing, and the October 1, October 15 and October 22 budget and local-law dates, while stating that the agenda carries no data-center or moratorium item and no stated use for the rezoned parcel.

Critic findings against this item (2)

no-absence-as-proofThe summary states the last three supporting documents "are served from a 2026-09 file directory that did not exist in prior passes." Non-observation of links into that directory does not establish that the directory did not exist; a 2026-09 path could have existed on the server with nothing yet linked from the archive page. The parallel claim earlier in the same paragraph is phrased correctly ("does not appear in the records of any prior pass") and this one should match it, e.g. "served from a 2026-09 file directory not seen in prior passes." The same sentence is also the one statement in this entry that no primary public record can support, while the entry carries evidence: verified.
no-fabricationsource_url is the archive index https://lysanderny.gov/board-meetings, but nearly every specific figure in the summary is read off a different document: the 5:30 PM work session and 6:30 PM regular meeting, the 8220 Loop Road location, the four work-session topics, Tax Map Number 024.-01-49.1, the negative declaration, the October 1 / October 15 / October 22 (5:00 PM) dates, the General Municipal Law 3-c reference, Enterprise Fire Company No. 1, and the 10-page and 1-page counts. The archive index does not contain any of that. The summary does name and attribute the agenda (https://lysanderny.gov/sites/default/files/2026-09/9-3-2026_agenda.pdf, "everything that follows is read off that document"), so the provenance is disclosed in prose, but the entry's source_url field still does not point at the record carrying the facts. Set source_url to the agenda PDF, or split the archive-listing observation and the agenda-content findings into separate entries with their own source_url values.

Source · 2026-09-03 ↗

verified Critic flagged 2026-08-31

town-of-lysander-official-records

The Town of Lysander notices index at lysanderny.gov carries an entry titled 8-28-26 Data Center Advisory Committee Meeting Agenda with a listing date of August 27, 2026, holding two files: the agenda itself and a separate presentation file. The agenda document notices a work session of the Lysander Data Center Advisory Committee at 8220 Loop Road for 9:00 AM on Friday, August 28th, 2026. Under old business it carries a single item, proposed noise ordinance wording from outside consultants, marked pending. Under new business it lists four items: a shared drive for documents, a Data Center Concerns List progress update, formalizing waste water recommendations, and beginning the electricity usage discussion. It then lists committee comments and feedback, and records the next meeting as continuing the electricity usage discussion. The agenda names no consultant, states no figures, records no vote or decision, and identifies no applicant or parcel. It establishes what was noticed and scheduled, not what occurred at the meeting.

Proposed edit

Add the August 28, 2026 Data Center Advisory Committee work session to the Lysander local-process timeline with its noticed old-business item (noise ordinance wording from outside consultants, pending) and its four new-business items, stating that the agenda records scheduling only and no vote, decision or applicant.

Critic findings against this item (1)

no-fabricationThe opening sentence asserts facts about the town's notices index page - an entry 'titled 8-28-26 Data Center Advisory Committee Meeting Agenda with a listing date of August 27, 2026, holding two files: the agenda itself and a separate presentation file' - but the single source_url is the agenda PDF itself (datacenteradvisorycommitteeagenda08-28-26.pdf). The listing date of August 27, 2026 and the two-file count cannot appear inside that PDF; they come from the index page, which is not cited. Either cite the notices-index URL alongside the PDF or drop the listing date and file count.

Source · 2026-08-28 ↗

verified No objection filed 2026-08-31

town-of-lysander-official-records

The presentation file the town posted for the August 28, 2026 committee meeting carries the file name lysander_dc_committee_electricity_usage_8-28-26.pdf, but the document itself opens with a section headed Waste Water Recommendations before moving to electricity; both subjects are inside this single file. The wastewater section states six recommendation items: that the committee reiterates the need for closed loop cooling systems; that the Planning Board must require a full environmental review for projects of this size or nature; that industrial users be required to disclose any toxic chemicals used in their cooling systems and industrial processes during the environmental review process; that wastewater be required to be treated and managed by WEP and the NY State DEC per their guidelines, with no direct release to the environment; that a public facing dashboard be required displaying current values and trends of potential waste water pollutants including the items listed in the committee's 8/21/26 meeting; and that proper recycling or disposal of used chemicals, including coolants, be required per WEP, DEC and EPA guidelines. The dashboard item carries an unfilled placeholder where a number should be, stating the requirement may be limited to industrial users who produce more than XXX gallons of wastewater in any given day, and those whose waste water contains PFAs above the ambient level already existing in the environment. The document presents this as recommendation text. It records no vote, no adoption, no transmittal to the Town Board, and it names no applicant.

Proposed edit

Record that the Lysander committee's wastewater work reached written recommendation language dated August 28, 2026, listing the six items including the closed-loop reiteration, the toxic-chemical disclosure requirement, the no-direct-release-to-the-environment requirement and the public-facing pollutant dashboard; state that the gallons-per-day threshold in the dashboard item is an unfilled placeholder; state that the document records no vote or adoption; and note that this recommendation text sits inside the file the town posted under an electricity-usage file name.

Held only because another item in the 2026-08-31 batch was flagged. Nothing was filed against this one.

Source · 2026-08-28 ↗

verified No objection filed 2026-08-31

town-of-lysander-official-records

The second half of the same August 28, 2026 committee presentation opens the committee's electricity subject area. It states priority figures taken from the committee's concerns spreadsheet, on the same undefined scale used in its earlier decks: electricity overall priority 2.4, with electricity usage, brown outs and capacity at 2.8, battery storage at 1.8, nuclear power generation onsite at 2.1, and generator usage at 2.4; it separately lists who pays for infrastructure upgrades at 3.0 as an item also covered in other areas. Under background it states that the committee already recommends that any water infrastructure upgrades for the project be paid for by the developer, that the planning board typically requires developers to pay for any required infrastructure additions, that the town does not manage or maintain the electric grid or electricity prices in any way, that the town has an existing moratorium on Battery Energy Storage Systems, and that the town is actively working on updating its BESS ordinance. It then sets out regulatory options the document says the town may hold: designating any on-site or behind-the-meter electrical power generation over a specific threshold, given in the document as an illustrative 5 megawatts, as a separate prohibited land use; explicitly limiting on-site generation to emergency battery storage and generators meant solely for temporary use during blackouts; mandating security perimeters for high voltage generation or specialized fuel systems; possibly restricting high voltage transmission switchyards within the zone; and it quotes existing town code 320-51, that there shall be no activities which emit radioactivity dangerous to health or adversely affecting the operation of any equipment. It divides jurisdiction as follows: NYISO operates the high-voltage grid, runs the wholesale markets, plans for future power needs, and sets supply charges; the New York Power Authority and companies such as Constellation Energy own and operate the generation plants; National Grid owns the wires and delivers power and does not generate it; the Public Service Commission sets delivery charges, service classifications and demand caps; the town has no say in power delivery or rates; the DEC has authority over generator air emissions, fuel types and fuel storage; and the town can regulate generator size, operating hours outside emergencies, setbacks and noise through code, and can influence generator types and pollution through the Planning Board SEQRA process. On capacity the document keeps three distinct quantities in play. First, peak load: it states that the local utility and NYISO approve a user's connection through the interconnection queue and that this approval is based on the peak load required by the user. Second, approved interconnection capacity: it states that once approved, the industrial user is allowed to use the full capacity they are approved for. Third, system capacity: it states that in theory a user would never be approved to use more power than system capacity allows, and that if the local utility and NYISO approved a connection through the interconnection queue but mathematically miscalculated the grid's capacity, the responsibility rests with them. It adds that consumers may be protected from price increases due to large scale user demand through the use of peak-load pricing. It defines a brownout as an intentional or unintentional drop in voltage in an electrical power supply system, states that brownouts can damage motors used by commercial users as well as those in residential appliances, and states that what looks like a brownout caused by a large user is often a deliberate, controlled voltage reduction engineered by the local utility or NYISO to keep the grid stable. It lists on-site power options as generators in diesel and natural gas form, battery energy storage, and nuclear or small modular reactors, and compares diesel against natural gas on energy density, fuel efficiency, upfront equipment cost, on-site fuel storage, fuel cost, emissions, noise and maintenance. The document's closing next-steps slide lists continuing the discussion on electricity usage and on-site generation and beginning to talk about electricity recommendations; no electricity recommendation text appears anywhere in this document.

Proposed edit

Open an electricity section in the Lysander local-process record carrying the August 28, 2026 priority figures on the committee's undefined scale, the statement that the town already has a BESS moratorium and is updating its BESS ordinance, the developer-pays framing already recommended for water infrastructure, the enumerated town-level regulatory options including the illustrative five-megawatt behind-the-meter threshold and the code 320-51 radioactivity clause, the town versus NYISO versus PSC versus DEC jurisdiction split, and the committee's account of interconnection review with peak load, approved interconnection capacity and system capacity named as three separate quantities; state that no electricity recommendation text appears in this document.

Held only because another item in the 2026-08-31 batch was flagged. Nothing was filed against this one.

Source · 2026-08-28 ↗

reported No objection filed 2026-08-31

town-of-lysander-official-records

The August 28, 2026 committee presentation makes four site-specific statements under a background heading in its on-site power section, none of which cite an underlying permit, utility filing or survey. As stated by the committee: there are two separate major power transmission lines crossing at the site; the second transmission line may mitigate the need for additional back up power, but that is unlikely; there is a large natural gas main running beneath the proposed data center site; and NRC guidelines for population density would prevent a large scale nuclear reactor at this site based on the combined population of Lysander, Van Buren, Salina and Clay. What the posted record directly supports is that the committee stated these things on that date. The underlying site conditions and the population-density conclusion were not located in any primary permit, utility or federal record during this pass, and the document identifies no applicant or parcel by name.

Proposed edit

Record the committee's four site-specific statements of August 28, 2026 about the two crossing transmission lines, the possible but described-as-unlikely backup-power mitigation from the second line, the natural gas main beneath the proposed site, and the NRC population-density constraint, attributing each to the committee presentation rather than to any permit, utility filing or federal record, and noting that no such underlying record was located during the check.

Held only because another item in the 2026-08-31 batch was flagged. Nothing was filed against this one.

Source · 2026-08-28 ↗

reported No objection filed 2026-08-31

town-of-lysander-official-records

A section of the August 28, 2026 committee presentation describes a NYISO proposal to revise the large load interconnection process, attributed in the document to NYISO rather than to the town. As stated there, NYISO is proposing changes to the interconnection process in response to the unprecedented pace and scale of large load development across New York State, and is considering five reforms: developing criteria to define and categorize large loads, including differentiated treatment for data centers and similar computational load facilities such as cryptocurrency mining; considering additional requirements for certain facilities, such as impact-based cost recovery, customer-supplied generation or storage, curtailment or flexibility obligations, long-term contracts, tariff revisions or other mechanisms to protect reliability; examining planning, modeling and queue-management improvements, particularly regarding speculative load, to enhance transparency, forecasting accuracy and interconnection efficiency; assessing clear and equitable impact-based risk- and cost-sharing arrangements for necessary grid upgrades; and identifying system and customer benefits, including opportunities for rate reductions and beneficial reuse of waste heat through coordination with thermal-energy-network initiatives. This is a town committee's restatement of a NYISO stakeholder proposal. The presentation cites no NYISO filing, docket number or date, and NYISO's own site returned an empty HTTP 202 response to automated requests during this pass, so the restatement could not be checked against the source. The subject matter overlaps the separately tracked Public Service Commission proceeding on large load interconnection, Case 26-E-0045, but the presentation does not state that the two are the same process and no record confirming that was located.

Proposed edit

Note that a NYISO large load interconnection reform proposal entered the Lysander committee record on August 28, 2026, summarizing the five reform areas as restated by the committee, labelled reported rather than verified because no NYISO filing is cited and NYISO's own site could not be read this pass, and cross-referenced to but not merged with the separately tracked Public Service Commission proceeding Case 26-E-0045.

Held only because another item in the 2026-08-31 batch was flagged. Nothing was filed against this one.

Source · 2026-08-28 ↗

verified Critic flagged 2026-08-31

lysander-town-board-minutes

The Town Board Meetings archive now carries the agenda document for the Lysander Town Board special meeting of Monday, August 31, 2026 at 5:00 PM at 8220 Loop Road, whose contents were not previously in the record. The agenda lists two items. Item A is a motion to adopt the bond resolution of the Town of Lysander, Onondaga County, authorizing the acquisition, construction and equipping of a capital improvement project for the benefit of the Cold Springs Sewer District No. 1 at an estimated maximum cost of $6,982,000, appropriating that amount, and authorizing issuance of up to $3,170,000 of bond anticipation notes and serial bonds to pay part of the cost of the project; those figures match the separately posted draft resolution already in the record. Item B is a motion authorizing the Town Clerk to advertise a public hearing before the Town Board at 6:30 PM on Thursday, September 15, 2026 on a zone change petition received from Leo R. Duger for the property at 8075 Plainville Road, tax map number 034.-01-01.2, currently Neighborhood Residential Business District extension, with the agenda noting the item is on for approval because it is time sensitive for advertisement in the Post-Standard. Two document-level observations follow from comparing this agenda with the Town Clerk's notice of the same meeting, dated August 6, 2026, which is already in the record: the notice states the purpose as conducting a public hearing regarding the bond resolution, while the agenda as posted lists a motion to adopt the resolution and lists no public hearing step among its items; and the notice does not mention the zone change item that the agenda carries. Neither item names a data-center applicant, and the agenda records what is scheduled for the meeting, not what was decided at it.

Proposed edit

Add the contents of the August 31, 2026 Town Board special meeting agenda to the local-process record, showing that the Cold Springs Sewer District No. 1 bond resolution reached a motion to adopt with the $6,982,000 maximum cost and up-to-$3,170,000 borrowing figures carried over from the draft resolution, and noting that the posted agenda differs from the meeting notice of August 6, 2026 in listing a motion to adopt rather than a public hearing and in carrying an additional zone-change advertisement item unrelated to any data-center applicant.

Critic findings against this item (1)

no-fabricationTwo sets of specific facts in the summary do not trace to source_url (8-31-2026_special_meeting_agenda.pdf): (a) 'those figures match the separately posted draft resolution already in the record' - the $6,982,000 / $3,170,000 match is a claim about a second document, the draft resolution, whose URL is not given; and (b) the entire final comparison paragraph, which attributes content to 'the Town Clerk's notice of the same meeting, dated August 6, 2026' - that it 'states the purpose as conducting a public hearing regarding the bond resolution' and 'does not mention the zone change item'. The August 6 date and both quoted characterizations come from that notice, not from the cited agenda. The document-mismatch observation is the most consequential claim in the entry and it rests on an uncited source; add the notice URL and the draft-resolution URL, or restrict the summary to what the agenda PDF itself contains.

Source · 2026-08-31 ↗

verified Critic flagged 2026-08-30

town-of-lysander-official-records

The Town of Lysander website posts an August 28, 2026 Data Center Advisory Committee meeting agenda together with a presentation file. The posted file name identifies it as the electricity-usage deck, but the document itself opens with a section titled Waste Water Recommendations before moving to electricity; both subjects are inside the single posted file. The agenda for that meeting lists, under new business, a shared drive for documents, a concerns-list progress update, formalizing wastewater recommendations, and beginning the electricity usage discussion, with a noise-ordinance wording item from outside consultants carried as pending old business. The wastewater section states six recommendation items: reiterating the need for closed loop cooling systems; that the Planning Board must require a full environmental review for projects of this size or nature; requiring industrial users to disclose any toxic chemicals used in their cooling systems and industrial processes during the environmental review process; requiring that wastewater is treated and managed by WEP and the New York State DEC per their guidelines with no direct release to the environment; requiring a public facing dashboard displaying current values and trends of potential wastewater pollutants, described in the document as including the items listed in the committee's own 8/21/26 meeting; and requiring the proper recycling or disposal of used chemicals, including coolants, per WEP, DEC and EPA guidelines. The dashboard item carries an unfilled placeholder where a number should be, stating the requirement may be limited to industrial users who produce more than XXX gallons of wastewater in any given day and those whose wastewater contains PFAs above the ambient level already existing in the environment. The document is recommendation text presented to the committee. It records no vote, no adoption, no transmittal to the Town Board, and it names no applicant.

Proposed edit

Record that the Lysander committee's wastewater work reached written recommendation language at the August 28, 2026 meeting, listing the six items including the closed-loop reiteration, the toxic-chemical disclosure requirement, the no-direct-release-to-the-environment requirement and the public-facing pollutant dashboard, stating that the gallons-per-day threshold in the dashboard item is an unfilled placeholder, stating that the document records no vote or adoption, and noting that the recommendation text sits inside the file the town posted under an electricity-usage file name.

Critic findings against this item (1)

no-fabricationThe summary attributes a specific list of items to a separate document that is not the cited source_url. It asserts that the town 'posts an August 28, 2026 Data Center Advisory Committee meeting agenda together with a presentation file' and then states 'The agenda for that meeting lists, under new business, a shared drive for documents, a concerns-list progress update, formalizing wastewater recommendations, and beginning the electricity usage discussion, with a noise-ordinance wording item from outside consultants carried as pending old business.' The only source_url given is the presentation PDF, lysander_dc_committee_electricity_usage_8-28-26.pdf, which the same summary describes as containing a wastewater recommendations section and then electricity content. That file does not plausibly contain the agenda's new-business and old-business ordering, and the agenda file's own URL is not supplied. Either cite the agenda document's URL alongside the deck, or drop the agenda-contents sentence and the noise-ordinance old-business item from this entry.

Source · 2026-08-28 ↗

verified No objection filed 2026-08-30

town-of-lysander-official-records

The same August 28, 2026 committee document opens the committee's electricity subject area. It states priority figures taken from the committee's concerns spreadsheet, on the same undefined scale used in its earlier decks: electricity overall priority 2.4, with electricity usage, brownouts and capacity at 2.8, battery storage at 1.8, nuclear power generation onsite at 2.1, and generator usage at 2.4; it separately lists who pays for infrastructure upgrades at 3.0 as an item also covered in other areas. Under background it states that the committee already recommends that any water infrastructure upgrades for the project be paid for by the developer, that the Planning Board typically requires developers to pay for any required infrastructure additions, that the town does not manage or maintain the electric grid or electricity prices in any way, that the town has an existing moratorium on Battery Energy Storage Systems, and that the town is actively working on updating its BESS ordinance. It then sets out regulatory options the document says the town may hold: designating on-site or behind-the-meter electrical power generation over a specific threshold, given in the document as an illustrative five megawatts, as a separate prohibited land use; explicitly limiting on-site generation to emergency battery storage and generators meant solely for temporary use during blackouts; mandating security perimeters for high voltage generation or specialized fuel systems; possibly restricting high voltage transmission switchyards within the zone; and it quotes existing town code 320-51 barring activities which emit radioactivity dangerous to health or adversely affecting the operation of any equipment. It divides jurisdiction as follows: NYISO operates the high-voltage grid, runs the wholesale markets, plans for future power needs and sets supply charges; the New York Power Authority and companies such as Constellation Energy own and operate generation plants; National Grid owns the wires and delivers power and does not generate it; the Public Service Commission sets delivery charges, service classifications and demand caps; the town has no say in power delivery or rates; the DEC has authority over generator air emissions, fuel types and fuel storage; and the town can regulate generator size, operating hours outside emergencies, setbacks and noise through code and can influence generator types and pollution through the Planning Board SEQRA process. On capacity the document distinguishes three quantities without using those words together: it states that the local utility and NYISO approve a user's connection through the interconnection queue, that this approval is based on the peak load required by the user, that once approved the industrial user is allowed to use the full capacity they are approved for, and that in theory a user would never be approved to use more power than system capacity allows. It adds that consumers may be protected from price increases due to large scale user demand through the use of peak-load pricing. It defines a brownout as an intentional or unintentional drop in voltage in an electrical power supply system, states that brownouts can damage commercial and residential motors, states that what looks like a brownout caused by a large user is often a deliberate controlled voltage reduction engineered by the local utility or NYISO to keep the grid stable, and states that if the local utility and NYISO approved a connection through the interconnection queue but mathematically miscalculated the grid's capacity, the responsibility rests with them. It lists on-site power options as generators in diesel and natural gas form, battery energy storage, and nuclear or small modular reactors, and compares diesel against natural gas on energy density, fuel efficiency, upfront equipment cost, on-site fuel storage, fuel cost, emissions, noise and maintenance. The document's closing next-steps slide lists continuing the electricity usage and on-site generation discussion and beginning to talk about electricity recommendations; no electricity recommendation text appears anywhere in this document.

Proposed edit

Open an electricity section in the Lysander local-process record carrying the August 28, 2026 priority figures on the committee's undefined scale, the statement that the town already has a BESS moratorium and is updating its BESS ordinance, the developer-pays framing already recommended for water infrastructure, the enumerated town-level regulatory options including the illustrative five-megawatt behind-the-meter threshold and the code 320-51 radioactivity clause, the town versus NYISO versus PSC versus DEC jurisdiction split, and the committee's account of interconnection review in which peak load is the basis of approval, approved interconnection capacity is what the user may then draw, and system capacity is the separate limit the utility and NYISO are said to check against; state that this document contains no electricity recommendation text.

Held only because another item in the 2026-08-30 batch was flagged. Nothing was filed against this one.

Source · 2026-08-28 ↗

reported No objection filed 2026-08-30

town-of-lysander-official-records

The August 28, 2026 committee document makes four site-specific statements under a background heading in its on-site power section, none of which cite an underlying permit, utility filing or survey. As stated by the committee: there are two separate major power transmission lines crossing at the site; the second transmission line may mitigate the need for additional backup power, though the document says that is unlikely; there is a large natural gas main running beneath the proposed data center site; and Nuclear Regulatory Commission guidelines for population density would prevent a large scale nuclear reactor at this site based on the combined population of Lysander, Van Buren, Salina and Clay. What is directly supported by the posted record is that the committee stated these things on that date. The underlying site conditions and the NRC population-density conclusion were not located in any primary permit, utility or federal record during this pass, and the document identifies no applicant or parcel by name.

Proposed edit

Record the committee's four site-specific statements of August 28, 2026 about the two crossing transmission lines, the possible but described-as-unlikely backup-power mitigation from the second line, the natural gas main beneath the proposed site, and the NRC population-density constraint, attributing each to the committee document rather than to any permit, utility filing or federal record, and noting that no such underlying record was located.

Held only because another item in the 2026-08-30 batch was flagged. Nothing was filed against this one.

Source · 2026-08-28 ↗

reported No objection filed 2026-08-30

town-of-lysander-official-records

A section of the August 28, 2026 committee document describes a NYISO proposal to revise the large load interconnection process, attributed in the document to NYISO rather than to the town. As stated there, NYISO is proposing changes to the interconnection process in response to the unprecedented pace and scale of large load development across New York State, and is considering five reforms: developing criteria to define and categorize large loads, including differentiated treatment for data centers and similar computational load facilities such as cryptocurrency mining; additional requirements for certain facilities such as impact-based cost recovery, customer-supplied generation or storage, curtailment or flexibility obligations, long-term contracts, tariff revisions or other mechanisms to protect reliability; planning, modeling and queue-management improvements, particularly regarding speculative load, to enhance transparency, forecasting accuracy and interconnection efficiency; clear and equitable impact-based risk- and cost-sharing arrangements for necessary grid upgrades; and identification of system and customer benefits including opportunities for rate reductions and beneficial reuse of waste heat through coordination with thermal-energy-network initiatives. This is a town committee's restatement of a NYISO stakeholder proposal. The document cites no NYISO filing, docket number or date, and NYISO's own site was not reachable by automated request this pass. The subject matter overlaps the separately tracked Public Service Commission proceeding on large load interconnection, Case 26-E-0045, but the document does not state that the two are the same process and no record confirming that was located.

Proposed edit

Note that a NYISO large load interconnection reform proposal entered the Lysander committee record on August 28, 2026, summarizing the five reform areas as restated by the committee, labelled reported rather than verified because no NYISO filing is cited, and cross-referenced to but not merged with the separately tracked Public Service Commission proceeding Case 26-E-0045.

Held only because another item in the 2026-08-30 batch was flagged. Nothing was filed against this one.

Source · 2026-08-28 ↗

verified Critic flagged 2026-08-29

town-of-lysander-official-records

A twenty-three-slide presentation dated August 28, 2026 and headed for the Lysander Data Center Advisory Committee is posted on the Town of Lysander website alongside the August 28 meeting agenda. Its opening section converts the committee's earlier wastewater material into drafted recommendation language. The drafted recommendations are: reiterating the need for closed-loop cooling systems; requiring the Planning Board to require a full environmental review for projects of this size or nature; requiring industrial users to disclose any toxic chemicals used in cooling systems and industrial processes during the environmental review process; requiring wastewater to be treated and managed by the county Water Environment Protection department and the state Department of Environmental Conservation per their guidelines with no direct release to the environment; requiring a public-facing dashboard displaying current values and trends of potential wastewater pollutants including the items listed at the committee's August 21, 2026 meeting; and requiring proper recycling or disposal of used chemicals including coolants per WEP, DEC and EPA guidelines. The dashboard recommendation carries an unfilled numeric placeholder, stating the requirement may be limited to industrial users producing more than a blank number of gallons of wastewater in any given day and those whose wastewater contains PFAS above the ambient level already existing in the environment. The document is drafted recommendation text presented to the committee; it records no vote, no adoption, and no transmittal to the Town Board, and it names no applicant.

Proposed edit

Record that the Lysander committee's wastewater work reached drafted recommendation language on August 28, 2026, listing the six drafted items including the closed-loop reiteration, the toxic-chemical disclosure requirement, the no-direct-release requirement, and the public-facing pollutant dashboard, and stating that the gallons-per-day threshold in the dashboard item is still an unfilled placeholder and that the document records no vote or adoption.

Critic findings against this item (1)

no-fabricationThe entire summary is wastewater content ('reiterating the need for closed-loop cooling systems', 'requiring wastewater to be treated and managed by the county Water Environment Protection department', 'a public-facing dashboard displaying current values and trends of potential wastewater pollutants'), but source_url is 'lysander_dc_committee_electricity_usage_8-28-26.pdf' — a file whose own slug identifies it as the electricity-usage deck. The summary also asserts specifics not obviously carried by that file: that it is 'A twenty-three-slide presentation', that it is 'posted on the Town of Lysander website alongside the August 28 meeting agenda', and that the dashboard item references 'the items listed at the committee's August 21, 2026 meeting' (a different meeting's record). Change 0 further says the document's 'opening section converts the committee's earlier wastewater material into drafted recommendation language' while change 1 says the same document 'opens the committee's electricity subject area' — the two entries make competing claims about the same document's opening. Either cite the specific wastewater deck/agenda URL for these six drafted items, or confirm and state that they appear inside the electricity-usage PDF.

Source · 2026-08-28 ↗

verified Critic flagged 2026-08-29

town-of-lysander-official-records

The same August 28, 2026 committee document opens the committee's electricity subject area and states priority figures drawn from the committee's concerns spreadsheet on the same undefined scale used in its earlier decks: electricity overall 2.4, electricity usage, brownouts and capacity 2.8, battery storage 1.8, nuclear power generation onsite 2.1, generator usage 2.4, and, carried over from other areas, who pays for infrastructure upgrades 3.0. Under background the document states that the town does not manage or maintain the electric grid or electricity prices in any way, that the town has an existing moratorium on Battery Energy Storage Systems, and that the town is actively working on updating its BESS ordinance. It sets out regulatory options the town may hold: designating on-site or behind-the-meter electrical generation above a threshold, given as an illustrative five megawatts, as a separate prohibited land use; explicitly limiting on-site generation to emergency battery storage and generators meant solely for temporary use during blackouts; mandating security perimeters for high-voltage generation or specialized fuel systems; possibly restricting high-voltage transmission switchyards within the zone; and it cites existing town code 320-51 barring activities emitting radioactivity dangerous to health. It separates jurisdictions, stating that NYISO operates the high-voltage grid and sets supply charges, that the New York Power Authority and companies such as Constellation Energy own and operate generation, that National Grid owns the wires and does not generate power, that the Public Service Commission sets delivery charges, service classifications and demand caps, that the town has no say in power delivery or rates, that DEC has authority over generator air emissions, fuel types and fuel storage, and that the town can regulate generator size, operating hours outside emergencies, setbacks and noise through code and can influence generator types through the Planning Board SEQRA process. It states that the local utility and NYISO are legally responsible for grid reliability, that interconnection approval is based on the user's peak load, that an approved user is allowed to use the full capacity approved, and that if the utility and NYISO approved a connection but miscalculated grid capacity the responsibility rests with them. It defines a brownout as an intentional or unintentional drop in voltage and states that an apparent large-user brownout is often a deliberate controlled voltage reduction engineered by the utility or NYISO. It lists on-site power options as diesel and natural gas generators, battery energy storage, and nuclear or small modular reactors, with diesel and natural gas compared on energy density, upfront cost, fuel storage, emissions and noise. Three site-specific assertions appear, stated by the committee without a cited underlying record: that two separate major power transmission lines cross at the site, that the second transmission line may mitigate the need for additional backup power though that is unlikely, that a large natural gas main runs beneath the proposed data center site, and that Nuclear Regulatory Commission population-density guidelines would prevent a large-scale nuclear reactor at this site based on the combined population of Lysander, Van Buren, Salina and Clay. The document closes by listing next steps as continuing the electricity usage and on-site generation discussion and beginning to talk about electricity recommendations, so no electricity recommendation has been drafted.

Proposed edit

Open an electricity section in the Lysander local-process record with the August 28, 2026 priority figures on the committee's undefined scale, the statement that the town already has a BESS moratorium and is updating its BESS ordinance, the enumerated town-level regulatory options including the illustrative five-megawatt behind-the-meter threshold and the code 320-51 radioactivity clause, and the town-versus-NYISO-versus-PSC-versus-DEC jurisdiction split; attribute the site-specific claims about two crossing transmission lines, the natural gas main beneath the site, and the NRC population-density constraint to the committee document rather than to any permit or utility record, and state that electricity recommendations had not yet been drafted as of that date.

Critic findings against this item (4)

no-absence-as-proofThe summary closes 'so no electricity recommendation has been drafted.' That converts the absence of recommendation language in one located slide deck into an affirmative statement of fact about the committee's output. The defensible phrasing is that no electricity recommendation appears in this document / none was located in the reviewed record as of August 28, 2026. The proposed_change repeats the same construction ('state that electricity recommendations had not yet been drafted as of that date').
no-fabricationThe summary states 'Three site-specific assertions appear' and then enumerates four: (1) two separate major power transmission lines cross at the site, (2) the second transmission line may mitigate the need for additional backup power though that is unlikely, (3) a large natural gas main runs beneath the proposed data center site, and (4) NRC population-density guidelines would prevent a large-scale nuclear reactor at this site. The count 'Three' does not trace to the enumeration it introduces; either the count is wrong or one listed item is not actually in the source document.
evidence-label-accuracyThe entry carries a single evidence label of 'verified' while the summary itself states that the transmission-line-crossing, buried-gas-main and NRC-population-density claims are 'stated by the committee without a cited underlying record.' Those are reported-class statements about site conditions, not statements a primary public record directly supports; only 'the committee document says X' is verified. Change 2 correctly uses 'reported' for the structurally identical case (the committee restating a NYISO proposal with no filing cited), so the same material is being labeled two different ways within one draft. Split this entry, or downgrade it to 'reported' for the site-specific assertions.
distinguish-capacity-typesThe summary states 'that interconnection approval is based on the user's peak load, that an approved user is allowed to use the full capacity approved, and that if the utility and NYISO approved a connection but miscalculated grid capacity the responsibility rests with them.' This runs peak load, approved interconnection capacity, and grid capacity together in one clause without marking them as distinct quantities, and the reader cannot tell which of the three the committee actually asserted. Restate with each capacity type named explicitly and attributed to the committee's own wording.

Source · 2026-08-28 ↗

reported No objection filed 2026-08-29

town-of-lysander-official-records

The same August 28, 2026 committee document contains a section describing a NYISO proposal to revise the large-load interconnection process, which it attributes to NYISO rather than to the town. As characterized in the document, NYISO is proposing changes in response to the pace and scale of large-load development across New York State and is considering: developing criteria to define and categorize large loads, including differentiated treatment for data centers and similar computational load facilities such as cryptocurrency mining; additional requirements for certain facilities such as impact-based cost recovery, customer-supplied generation or storage, curtailment or flexibility obligations, long-term contracts, tariff revisions or other mechanisms to protect reliability; planning, modeling and queue-management improvements particularly regarding speculative load, to improve transparency, forecasting accuracy and interconnection efficiency; clear and equitable impact-based risk- and cost-sharing arrangements for necessary grid upgrades; and identification of system and customer benefits including opportunities for rate reductions and beneficial reuse of waste heat through coordination with thermal-energy-network initiatives. This is a town committee's restatement of a NYISO stakeholder proposal; no NYISO document, docket number, filing date or tariff filing is cited in the town document, and the underlying NYISO material was not reachable directly this pass. The subject matter overlaps the tracked Public Service Commission proceeding on large-load interconnection but the document does not identify the two as the same process.

Proposed edit

Note that a NYISO large-load interconnection reform proposal entered the Lysander committee record on August 28, 2026, summarizing the five reform areas as restated by the committee, labelled as reported rather than verified because no NYISO filing is cited, and cross-referenced to but not merged with the separately tracked Public Service Commission large-load interconnection proceeding.

Held only because another item in the 2026-08-29 batch was flagged. Nothing was filed against this one.

Source · 2026-08-28 ↗

verified Critic flagged 2026-08-28

town-of-lysander-official-records

A Data Center Advisory Committee agenda posted on the Town of Lysander website on August 27, 2026 notices a work session at 8220 Loop Road for 9:00 AM on Friday, August 28, 2026. Under old business the agenda carries forward a single item, proposed noise-ordinance wording from outside consultants, marked pending. Under new business it lists a shared document drive, a Data Center Concerns List progress update, an item to formalize wastewater recommendations, and an item to begin an electricity usage discussion. The agenda also lists committee comments and feedback, and records the next meeting as continuing the electricity usage discussion. The agenda names no consultant, states no figures, and records no decision; it establishes what was noticed and scheduled, not what occurred.

Proposed edit

Add the noticed August 28, 2026 Data Center Advisory Committee work session to the committee meeting record, showing wastewater moving to a formalize-recommendations item and electricity usage opening as the committee's next subject area.

Critic findings against this item (1)

no-fabricationThe summary opens "A Data Center Advisory Committee agenda posted on the Town of Lysander website on August 27, 2026 ...". The document at source_url contains no posting date; its body carries only the meeting particulars (8220 Loop Road, Friday, August 28th, 2026, Work Session 9:00 AM). The only August 27 datum in the record is the PDF's internal CreationDate/ModDate stamp (D:20260827154556-04'00'), which records when the file was generated, not when the town published it. Every other element of this summary verifies against the agenda text; only the asserted website-posting date does not, and the same entry's own closing caution ("it establishes what was noticed and scheduled, not what occurred") is the standard the opening sentence should meet. Recast as dated August 27, 2026 per the file's own timestamp, or drop the date.

Source · 2026-08-28 ↗

verified No objection filed 2026-08-28

town-of-lysander-official-records

A thirteen-slide presentation document posted on the Town of Lysander website, headed for a Data Center Advisory Committee meeting and dated August 7, 2026, contains background material not present in the committee's later August 21, 2026 wastewater deck. It states that a previously approved warehouse required water and sewer lines to be built out to the site, that the planning board typically requires developers to pay for any required infrastructure additions, that the town does not have its own municipal water system, that the town's wastewater treatment is handled by the county, and that existing town code covers stormwater and runoff. It lists the same undefined-scale priority figures from a committee concerns spreadsheet as the later deck -- water overall 2.5, water pollution including PFAS 2.5, water usage 2.7, residential water pressure 2.1, ground water levels 1.8, who pays for infrastructure upgrades 3.0, wastewater handling and treatment 3.0 -- and records that stormwater runoff was suggested as an additional item the prior week. It states the committee had already recommended against open-loop cooling, describes closed-loop systems as drastically reducing total water consumed while still requiring periodic flushing and occasional draining for maintenance, and lists mitigation options as choosing the least toxic coolant available, proper disposal of used chemical coolants away from the wastewater system, on-site treatment, discharge to the county for treatment, and robust monitoring and reporting. The document records no decision and identifies no applicant, and its presence on the website establishes that it was posted, not that a meeting took place.

Proposed edit

Add the August 7, 2026 committee wastewater document to the Lysander local-process record as the earlier of two wastewater decks, citing its background statements on the warehouse water and sewer build-out, the planning board's practice of requiring developers to fund infrastructure additions, and the coolant-disposal and on-site-treatment mitigation options.

Held only because another item in the 2026-08-28 batch was flagged. Nothing was filed against this one.

Source · 2026-08-07 ↗

verified No objection filed 2026-08-28

lysander-town-board-minutes

The posted agenda for the Lysander Town Board meeting of Thursday, August 20, 2026 lists, as the first work session item, 'Noise/Battery Energy Storage/Microgrid Networks.' The remaining work session items are unrelated town business, and the regular meeting agenda covers stop-sign local laws, adoption of July 31, 2026 special-meeting minutes, and routine reports. The agenda lists these subjects as scheduled for discussion; it does not record what was said or decided, and it names no data-center applicant.

Proposed edit

Record that noise, battery energy storage and microgrid networks appeared together as a Town Board work session subject on August 20, 2026, showing these topics reaching the full board rather than only the advisory committee, without asserting an outcome.

Held only because another item in the 2026-08-28 batch was flagged. Nothing was filed against this one.

Source · 2026-08-20 ↗

verified No objection filed 2026-08-28

lysander-town-board-minutes

The draft bond resolution posted for the Town of Lysander Town Board session of August 31, 2026 supplies figures for the Cold Springs Sewer District #1 project that the previously posted meeting notice did not state. The draft would authorize acquisition, construction and equipping of the project at a maximum estimated cost of $6,982,000 and authorize issuance of up to $3,170,000 of serial bonds or bond anticipation notes. Its financing plan consists of payment of project costs by a third party developer in the amount of $3,812,000, expenditure of state grants, federal grants and other available funds if any, and the up-to-$3,170,000 bond or note issuance. The project is described as a new pump station, approximately 20,000 linear feet of gravity sewer and force main piping, branch gravity sewer connections, precast concrete manholes, sewer laterals, cleanout structures, and air release valves and structures. The period of probable usefulness is stated as forty years, and debt service is to be apportioned against parcels within the district, with the town's full faith and credit pledged and ad valorem taxes on all taxable town property available if district assessments do not cover payment. The draft recites that the Map, Plan and Report was filed with the Town Clerk on January 14, 2026, that the board on July 31, 2026 classified the project as an Unlisted Action, declared itself lead agency for an uncoordinated review and issued a Negative Declaration, that the district formation resolution adopted July 31, 2026 was subject to permissive referendum, and that the referendum period elapsed with no valid petition filed. The draft names no developer and makes no reference to any data center or data storage facility. Its own caption describes the August 31, 2026 session as a regular meeting at 4:00 P.M.

Proposed edit

Add the Cold Springs Sewer District No. 1 figures to the local sewer-infrastructure timeline -- $6,982,000 maximum estimated cost, up to $3,170,000 in bonds or notes, a $3,812,000 third-party developer contribution, roughly 20,000 linear feet of piping plus a new pump station, and a forty-year period of probable usefulness -- stating that the resolution is a draft, that no developer is named, and that the document makes no data-center reference; and flag for reconciliation that the draft's caption gives 4:00 P.M. while the separately posted Town Clerk notice gives 5:00 PM for the same date.

Held only because another item in the 2026-08-28 batch was flagged. Nothing was filed against this one.

Source · 2026-08-31 ↗

reported Critic flagged 2026-08-28

terawulf-q1-2026-investor-presentation

TeraWulf filed a Q2 2026 investor presentation as an exhibit to an 8-K on August 5, 2026, superseding the tracked Q1 2026 deck, which was re-verified unchanged at its own URL this pass. The Q2 deck locates Lake Hawkeye at Lansing, NY in NYISO, still shows approximately 320 MW of critical IT capacity there, still shows the site in the uncontracted pipeline rather than among contracted sites, and adds a delivery target the Q1 deck did not state: approximately 320 MW of total critical IT delivery in 2029. It reports platform totals of 3,630 MW gross and 2,921 MW critical IT, up from 2,870 MW gross and 2,272 MW critical IT in the Q1 deck, and contracted critical IT capacity of approximately 839 MW, up from 522 MW, which the deck attributes to a 401 MW lease with Anthropic at the Justified Data campus in Hawesville, Kentucky and to acquisition of the Muskie site in Grayson, Kentucky with 1 GW of contracted electric service. The deck also states an agreement to sell the company's Abernathy joint venture interest for $530 million and shows Chesapeake Data as pending closing and regulatory approvals. All figures are company-reported; the 2029 Lake Hawkeye date is a forward-looking target stated by the company, not a permit, interconnection or construction record, and the deck reports no contracted capacity at Lake Hawkeye and no site-plan-approval status for it.

Proposed edit

Update the Lake Hawkeye entry to the company's Q2 2026 reported position -- Lansing, NY, approximately 320 MW critical IT, no contracted capacity, a company-stated 2029 critical-IT delivery target -- labelled as company-reported and distinguished from critical IT MW already contracted elsewhere on TeraWulf's platform, and consider repointing the config entry from the Q1 deck to this successor filing.

Critic findings against this item (2)

distinguish-capacity-typesThe summary reports "contracted critical IT capacity of approximately 839 MW, up from 522 MW, which the deck attributes to a 401 MW lease with Anthropic at the Justified Data campus in Hawesville, Kentucky and to acquisition of the Muskie site in Grayson, Kentucky with 1 GW of contracted electric service." This folds two different capacity types into one figure. The deck's 839 MW is contracted CRITICAL IT capacity; Muskie's "1 GW of Contracted Electric Service" is utility electric service capacity, a distinct quantity that the deck reports separately (Muskie's critical IT figure is ~800 MW and appears under "Pipeline Sites Total Planned Critical IT Capacity: ~2,082 MW", not under contracted). The deck's own arithmetic confirms the separation: 438 MW contracted at Lake Mariner Data plus 401 MW at Justified Data equals the ~839 MW contracted total exactly, with zero contribution from Muskie.
no-fabricationThe clause "which the deck attributes to ... acquisition of the Muskie site in Grayson, Kentucky with 1 GW of contracted electric service" is not supported by source_url. The Q2 deck lists "Acquired Muskie and Secured 1 GW of Contracted Electric Service" as a separate Q2 milestone alongside the Anthropic lease and the Abernathy JV sale; it nowhere attributes the rise in contracted critical IT capacity to Muskie, and it places Muskie (800 MW) in the controlled pipeline. The attributed causal link is the draft's own inference presented as the deck's statement.

Source · 2026-08-05 ↗

verified Critic flagged 2026-08-27

town-of-lysander-official-records

The Lysander Data Center Advisory Committee held a work session at 9:00 a.m. on Friday, August 14, 2026 at 8220 Loop Road. The posted agenda lists, under old business, proposed noise-ordinance wording from outside consultants marked as pending a response from the vendor, and a water-usage discussion. New business lists a progress update on the committee's data-center concerns list, a recap of a CNY Solidarity data-center meeting, and the start of a wastewater discussion. The agenda names no consultant and states no decision.

Proposed edit

Add the August 14, 2026 Data Center Advisory Committee work session to the committee meeting record, noting the noise-ordinance consultant item as still awaiting a vendor response.

Critic findings against this item (1)

evidence-label-accuracySummary asserts the committee "held a work session at 9:00 a.m. on Friday, August 14, 2026 at 8220 Loop Road" and is labeled evidence:verified, but the cited source (8-14-26_dcac_agenda.pdf) is a posted agenda -- a notice of a scheduled meeting. An agenda directly supports that the work session was noticed/scheduled for that time and place and what items were listed; it does not support that the session was actually held, nor that the listed items were in fact taken up. No minutes, recording, or post-meeting record is cited. Either recast the statement as scheduled/noticed ("the posted agenda for a work session set for 9:00 a.m. Friday, August 14, 2026..."), or cite a record of the meeting having occurred.

Source · 2026-08-14 ↗

verified Critic flagged 2026-08-27

town-of-lysander-official-records

The Lysander Data Center Advisory Committee held a further work session at 9:00 a.m. on Friday, August 21, 2026 at 8220 Loop Road. The posted agenda carries the noise-ordinance wording from outside consultants forward as a status update, and lists as new business a shared document drive, a concerns-list progress update, a Battery Energy Storage System ordinance update, and continuation of the wastewater discussion focused on monitoring. The agenda records the next meeting as a further continuation of the wastewater discussion.

Proposed edit

Add the August 21, 2026 Data Center Advisory Committee work session to the committee meeting record, including the Battery Energy Storage System ordinance item as a newly visible workstream distinct from the noise ordinance.

Critic findings against this item (1)

evidence-label-accuracySame defect as change 0: summary asserts the committee "held a further work session at 9:00 a.m. on Friday, August 21, 2026 at 8220 Loop Road" under evidence:verified, while the only cited source (dcac_agenda_08-21-26.pdf) is a posted agenda. The agenda supports the scheduling and the listed items (noise-ordinance status update, shared document drive, concerns-list progress, Battery Energy Storage System ordinance update, wastewater/monitoring continuation, next-meeting note); it does not support occurrence. Note the related presentation cited in change 2 is described as "posted with" the agenda, which likewise does not establish that the meeting took place.

Source · 2026-08-21 ↗

verified No objection filed 2026-08-27

town-of-lysander-official-records

A presentation posted with the August 21, 2026 Data Center Advisory Committee agenda sets out the committee's wastewater analysis. It lists priority figures drawn from a committee concerns spreadsheet -- water overall 2.5, water pollution including PFAS 2.5, water usage 2.7, residential water pressure 2.1, ground water levels 1.8, who pays for infrastructure upgrades 3.0, and wastewater handling and treatment 3.0 -- on a scale the document does not define, so the figures cannot be read as a ranking without further source support. The presentation records that the town has no municipal water system of its own, that the county provides both water through OCWA and wastewater treatment through WEP, and that the town's available levers are mandating connection to municipal water, regulating wells including limits on large-scale withdrawals, and imposing drought-time outdoor use limits. It states the committee has already recommended against open-loop cooling, identifies coolant toxicity, PFAS, nitrite corrosion inhibitors, biocides, heavy metals, pH and heat as wastewater concerns, and proposes a monitoring and public dashboard reporting requirement applying to all industrial users above an unspecified volume or contaminant threshold, listing fourteen parameters to monitor. Next steps recorded are continued wastewater discussion followed by stormwater.

Proposed edit

Add a wastewater subsection to the Lysander local-process record summarizing the committee's August 21 presentation: the open-loop recommendation, the town-versus-county authority split, and the proposed industrial-user monitoring and dashboard reporting requirement, with the priority figures presented as undefined-scale committee scoring rather than a ranking.

Held only because another item in the 2026-08-27 batch was flagged. Nothing was filed against this one.

Source · 2026-08-21 ↗

verified Critic flagged 2026-08-27

lysander-town-board-minutes

The Town Board Meetings archive now lists records postdating the prior check: Town Board agendas for August 6 and August 20, 2026, a bond resolution draft filed under an August 31, 2026 Town Board entry, and minutes for the July 31, 2026 special meeting, which were previously outstanding. The Codes / Planning / Zoning series now lists an August 13, 2026 agenda with meeting materials and a September 14, 2026 agenda with meeting materials, both posted in advance of the September date. Data Center Advisory Committee meetings continue not to appear in this archive; they are posted only as notices on the town's main page.

Proposed edit

Extend the Lysander meeting-records inventory through August 2026, note that July 31, 2026 special-meeting minutes are now published, and retain the caveat that Data Center Advisory Committee records are not carried in the Board Meetings archive.

Critic findings against this item (2)

no-fabricationThe clause "they are posted only as notices on the town's main page" does not trace to source_url (https://lysanderny.gov/board-meetings). That archive page can substantiate what it does and does not list -- the first clause, "Data Center Advisory Committee meetings continue not to appear in this archive," is properly scoped to it -- but it cannot substantiate where else in the site those records are or are not published. The word "only" is an exclusivity claim about the rest of lysanderny.gov, and it sits awkwardly against changes 0-2 of this same draft, which cite committee documents at stable /sites/default/files/2026-08/ PDF paths rather than at the homepage. Either cite the page that establishes the exclusive publication path or drop the claim to "not located in the Board Meetings archive this pass."
no-absence-as-proofRelated to the finding above: "continue not to appear in this archive" is acceptable phrasing on its own, but combined with "posted only as notices on the town's main page" the summary converts a not-located result into an affirmative finding about the town's publication practice. The reviewed record supports only that the committee records were not found in the Board Meetings archive on this check.

Source · 2026-08-20 ↗

verified No objection filed 2026-08-27

lysander-town-board-minutes

A notice signed by the Town Clerk and dated August 6, 2026 calls a special meeting of the Lysander Town Board for 5:00 p.m. on Monday, August 31, 2026 at the Lysander Town Hall, 8220 Loop Road, Baldwinsville. The stated purpose is a public hearing on the bond resolution for establishment of the Cold Springs Sewer District No. 1. The notice does not state a bond amount and makes no reference to any data-center project.

Proposed edit

Record the August 31, 2026 special meeting and its Cold Springs Sewer District No. 1 bond public hearing in the local sewer-infrastructure timeline, without asserting a connection to data-center demand that the notice does not state.

Held only because another item in the 2026-08-27 batch was flagged. Nothing was filed against this one.

Source · 2026-08-06 ↗

verified Critic flagged 2026-08-26

town-of-lysander-official-records

Data Center Advisory Committee held meetings on August 14 and August 21, 2026. Town website updated with additional notices and schedules from August 2026.

Proposed edit

Update DCAC meeting record to include August 14 and August 21, 2026 meetings

Critic findings against this item (1)

no-fabricationsource_url is https://lysanderny.gov/, a general agency homepage, not a specific document. The summary claims specific facts ('meetings on August 14 and August 21, 2026') that should trace to a specific page or document URL (e.g., town agenda, DCAC meeting archive, or dated notice), not a general homepage.

Source · 2026-08-25 ↗

verified On the main site 2026-08-26

lysander-town-board-minutes

Published to the main site on 2026-09-12 under #status: Four Micron dam safety permits issued Jun 1 and Jul 30 2026.

Town Board meeting on September 1, 2026 and Codes/Planning/Zoning meeting on September 14, 2026 now appear in the official Board Meetings archive.

Proposed edit

Add September 2026 meeting records (Sept 1 Town Board, Sept 14 Planning) to archive

Held only because another item in the 2026-08-26 batch was flagged. Nothing was filed against this one.

Source · 2026-09-14 ↗

verified On the main site 2026-08-26

nysdec-micron-permit-dashboard

Published to the main site on 2026-09-12 under #status: Four Micron dam safety permits issued Jun 1 and Jul 30 2026.

Four Article 15 Title 5 Dam safety permits for stormwater retention structures issued between June 1 and July 30, 2026.

Proposed edit

Add Article 15 Title 5 Dam safety permits (issued June-July 2026) to Micron permit record

Held only because another item in the 2026-08-26 batch was flagged. Nothing was filed against this one.

Source · 2026-07-30 ↗

verified Critic flagged 2026-08-25

town-of-lysander-official-records

Town of Lysander website now shows Data Center Advisory Committee meetings on August 14, 2026 with next meeting agenda posted August 20, 2026. Wastewater presentations dated August 7 and August 21, 2026 appear on DCAC meeting pages.

Proposed edit

Update DCAC meeting record to reflect August 2026 meetings and wastewater presentations beyond the July 31 milestone previously recorded

Critic findings against this item (1)

no-fabricationsource_url is the general town homepage (https://lysanderny.gov/) but summary contains specific facts: DCAC meetings on August 14 and 20, wastewater presentations dated August 7 and 21. A general homepage does not plausibly contain these specific meeting details without linking to a more specific source document (e.g., the actual meeting page or agenda).

Source · 2026-08-25 ↗

verified Critic flagged 2026-08-25

cny-forward-transportation-eis

CNY Forward Transportation EIS public comment period now closed as of August 14, 2026. Public scoping meetings were held July 30 and August 6, 2026, with dedicated website CNYForward.com and outreach office at 4483 State Route 31 in Clay.

Proposed edit

Update project status to reflect completed public comment period (deadline August 14, 2026) and scoping meeting dates

Critic findings against this item (1)

no-fabricationsource_url is a governor.ny.gov press announcement, which typically provides high-level information. Summary contains specific office location '4483 State Route 31 in Clay' — this level of detail does not plausibly appear in a gubernatorial press release and should trace to a project-specific document, not a general announcement.

Source · 2026-08-14 ↗

verified No objection filed 2026-08-25

white-pine-science-technology-park

White Pine Science and Technology Park documentation shows Final Scope available (as of June 17, 2026) with Draft Generic Environmental Impact Statement preparation pending. No 104-acre project acreage mentioned in current source material; Onondaga County Industrial Development Agency is lead agency for environmental review.

Proposed edit

Verify 104-acre acreage claim from prior record; current OCIDA/DEC notice does not include project size, only Final Scope availability and pending DGEIS

Held only because another item in the 2026-08-25 batch was flagged. Nothing was filed against this one.

Source · 2026-06-17 ↗

verified Critic flagged 2026-08-24

town-of-lysander-official-records

Town of Lysander official website now displays multiple Data Center Advisory Committee meetings held in August 2026, with downloadable agendas and wastewater-focused presentations. Most recent DCAC meetings documented are August 21, August 14, and August 7, 2026. Wastewater presentations to the committee are now publicly available, supporting analysis of water and sanitary infrastructure for data center planning.

Proposed edit

Update town-of-lysander-official-records fingerprint to reflect August 2026 DCAC meetings and wastewater presentation materials now published.

Critic findings against this item (1)

no-fabricationThe summary claims specific DCAC meeting dates ('August 21, August 14, and August 7, 2026') and 'downloadable agendas and wastewater-focused presentations.' The source_url 'https://lysanderny.gov/' is the general homepage, not a specific DCAC meetings page, dashboard, or document listing. The rule requires that 'source_url' plausibly contain the specific facts cited; a general agency homepage does not plausibly document specific meeting dates and materials as the primary record. The actual DCAC meeting page or dedicated meeting materials listing should be the source_url, not the homepage.

Source · 2026-08-24 ↗

verified On the main site 2026-08-24

nysdec-micron-permit-dashboard

Published to the main site on 2026-09-12 under #status: Four Micron dam safety permits issued Jun 1 and Jul 30 2026.

NYSDEC Micron permit dashboard now documents additional Micron campus permits issued after the previous record date. Dam Safety Permits for stormwater retention structures were issued June-July 2026. Air Title V Permit for Fab 1 and Fab 2 operations was issued March 31, 2026. These permits represent authorizations for critical infrastructure supporting the semiconductor manufacturing campus.

Proposed edit

Update nysdec-micron-permit-dashboard fingerprint to include Air Title V Permit (issued March 31, 2026) and Dam Safety Permits (issued June-July 2026) for stormwater retention structures.

Held only because another item in the 2026-08-24 batch was flagged. Nothing was filed against this one.

Source · 2026-08-24 ↗

verified Critic flagged 2026-08-23

town-of-lysander-official-records

Town of Lysander website shows Data Center Advisory Committee held meetings on August 7, 2026 and August 21, 2026, both after the prior record date of July 31. August 21 meeting included a wastewater management presentation. Additional recent notices include Cold Springs Sewer District formation documents (August 13), Clinton Heights Sewer District Extension No. 3 notice (August 17), and an Empire State Development public hearing for the 8280 Sixty Road project (August 17, 2026).

Proposed edit

Update Data Center Advisory Committee meeting log with August 7 and August 21, 2026 meetings; add references to recent sewer district notices and Empire State Development hearing scheduled August 17.

Critic findings against this item (1)

no-fabricationThe source_url https://lysanderny.gov/ is the general town homepage, not a specific document. The summary references specific municipal records—Data Center Advisory Committee meeting minutes from August 7 and August 21, 2026; Cold Springs Sewer District formation documents (August 13); Clinton Heights Sewer District Extension No. 3 notice (August 17); and an Empire State Development public hearing notice for 8280 Sixty Road (August 17)—but the source_url provided does not plausibly point to where these specific documents or meeting records would be located.

Source · 2026-08-23 ↗

verified On the main site 2026-08-23

nysdec-micron-permit-dashboard

Published to the main site on 2026-09-12 under #status: Four Micron dam safety permits issued Jun 1 and Jul 30 2026.

NYSDEC Micron permit dashboard now shows issuance of four Dam Safety permits between June 1 and July 30, 2026, representing a more complete permit record than the July 29 prior record. All major campus permits (wetlands, water quality certification, endangered species, air title V) remain as previously documented, with connected action permits largely issued.

Proposed edit

Add Dam Safety Permits (7-3124-00575/00XXX series) issued June 1 to July 30, 2026 to the Micron permit tracking section.

Held only because another item in the 2026-08-23 batch was flagged. Nothing was filed against this one.

Source · 2026-08-23 ↗

verified Critic flagged 2026-08-22

town-of-lysander-official-records

Town of Lysander website now shows August 2026 Data Center Advisory Committee meetings and agendas. Meeting held August 7 with wastewater discussion; meeting scheduled August 21 with wastewater presentation materials. Previous fingerprint only referenced July 31 meeting.

Proposed edit

Update fingerprint to include August 7 and August 21, 2026 DCAC meetings and their agendas

Critic findings against this item (1)

no-fabricationsource_url 'https://lysanderny.gov/' is the general town homepage. The summary cites specific DCAC meeting agendas from August 7 and August 21, 2026. A general town homepage URL does not plausibly contain these specific DCAC meeting agendas without a more direct link to the DCAC or meetings archive page.

Source · 2026-08-21 ↗

verified On the main site 2026-08-22

nysdec-micron-permit-dashboard

Published to the main site on 2026-09-12 under #status: Four Micron dam safety permits issued Jun 1 and Jul 30 2026.

Dashboard updated with multiple permit approvals and status changes beyond the July 29 fingerprint date. New information includes: Air Title V Permit issued March 31, 2026; Article 15 Title 5 Dam Permits issued June 1 and July 30, 2026; multiple connected-action permits with dates from March-June 2026 including Water Services (March 23), Gas Main Extension (May 20), and Raw Water Pump Station (June 8).

Proposed edit

Update fingerprint with specific permit dates and approvals: Air Permit (3/31/2026), Dam Permits (6/1, 7/30/2026), connected-action approvals (3/23, 5/20, 6/8/2026)

Held only because another item in the 2026-08-22 batch was flagged. Nothing was filed against this one.

Source · 2026-08-22 ↗

verified No objection filed 2026-08-22

cny-forward-transportation-eis

CNY Forward transportation EIS public comment period is now closed. Public scoping meetings were held July 30 and August 6, 2026, with public comment deadline of August 14, 2026 (now past). Project is beyond its initial public engagement phase.

Proposed edit

Update fingerprint to reflect that public scoping and comment period is closed as of August 14, 2026; project is now in DEIS preparation phase

Held only because another item in the 2026-08-22 batch was flagged. Nothing was filed against this one.

Source · 2026-08-14 ↗

verified No objection filed 2026-08-22

lysander-town-board-minutes

Town of Lysander Board Meetings archive now includes minutes through August 20, 2026, extending the previously recorded range (through July 30). Meetings continue to be published as separate PDFs for Town Board meetings.

Proposed edit

Update fingerprint to reflect that records now extend through August 20, 2026

Held only because another item in the 2026-08-22 batch was flagged. Nothing was filed against this one.

Source · 2026-08-20 ↗

verified Critic flagged 2026-08-21

town-of-lysander-official-records

Town of Lysander main website now displays Data Center Advisory Committee (DCAC) meeting materials dated August 14, 2026 and August 21, 2026 (upcoming), superseding the previous record dated July 31, 2026. August 14 meeting included wastewater systems presentation materials. Related town board meetings held August 17 (Empire State Development public hearing), August 6, and August 20. Sewer district extension notices (August 17), infrastructure project bid documents (August 14), and planning/zoning meeting materials (August 13) also posted. Community Benefit Agreement draft currently not visible in posted materials.

Proposed edit

Update DCAC record_date to 2026-08-21 and last_seen_fingerprint to reflect August 14 and August 21 DCAC meeting materials, plus August 17 Town Board action and new infrastructure notices.

Critic findings against this item (1)

no-fabricationThe summary attributes specific materials with precise dates (DCAC meetings August 14 and August 21, Town Board meetings August 17/6/20, notices and documents with specific dates on August 17/14/13) to source_url https://lysanderny.gov/, which is the town's main domain homepage. Per the rule, a general agency homepage does not plausibly contain the specific documents themselves—only navigation to them. The source_url should be the specific DCAC archive page, Town Board minutes page, or other direct endpoint where these dated materials are actually posted, not the main homepage.

Source · 2026-08-21 ↗

verified Critic flagged 2026-08-20

town-of-lysander-official-records

Data Center Advisory Committee held a new meeting on August 14, 2026 with posted agenda and wastewater presentation. Previous record indicated July 31 meeting; this is a subsequent scheduled meeting.

Proposed edit

Update Data Center Advisory Committee meeting record from July 31 to include August 14, 2026 meeting

Critic findings against this item (1)

no-fabricationSource URL is the town homepage (https://lysanderny.gov/) but the summary cites specific meeting details: 'August 14, 2026 with posted agenda and wastewater presentation.' A general homepage does not plausibly contain the specific agenda and presentation content referenced. To satisfy no-fabrication, source_url should point to the specific Data Center Advisory Committee meeting record or agenda, not the homepage.

Source · 2026-08-14 ↗

verified Critic flagged 2026-08-20

cny-forward-transportation-eis

Public comment deadline for CNY Forward transportation EIS scoping process is Friday, August 14, 2026. Public scoping meetings were held July 30 and August 6, 2026 at Clay Town Hall.

Proposed edit

Add public comment deadline August 14, 2026 and scoping meeting dates (July 30 and August 6) to CNY Forward project record

Critic findings against this item (1)

no-fabricationSource URL is a Governor's press announcement about launching the CNY Forward project (https://www.governor.ny.gov/news/...) but the summary includes specific future operational details: 'Public comment deadline for CNY Forward transportation EIS scoping process is Friday, August 14, 2026. Public scoping meetings were held July 30 and August 6, 2026 at Clay Town Hall.' A launch announcement press release does not plausibly contain these granular meeting dates, deadlines, and venue details. These specifics would be found in the actual EIS scoping document or public notice, not the announcement.

Source · 2026-08-14 ↗

verified Critic flagged 2026-08-19

town-of-lysander-official-records

Town of Lysander website now shows Data Center Advisory Committee meetings scheduled for August 7 and August 14, 2026, in addition to the July 31 meeting already recorded. The July 31 Town Board special meeting minutes have been published.

Proposed edit

Update town-of-lysander-official-records fingerprint to include August 7 and August 14 DCAC meetings and confirm July 31 minutes published status

Critic findings against this item (1)

no-fabricationsource_url is https://lysanderny.gov/ (general agency homepage), but summary claims specific facts: 'Data Center Advisory Committee meetings scheduled for August 7 and August 14, 2026' and 'July 31 Town Board special meeting minutes have been published.' The lens requires source_url to plausibly contain those specific facts, not just be a general homepage. Should point to the specific DCAC meeting schedule page or the specific published minutes document, not the homepage.

Source · 2026-08-19 ↗

verified Critic flagged 2026-08-17

town-of-lysander-official-records

Data Center Advisory Committee held meetings on 2026-08-07 and has an upcoming meeting scheduled for 2026-08-14. Water infrastructure continuation presentation materials were presented at the 2026-07-31 meeting and wastewater analysis materials at the 2026-08-07 meeting. The Community Benefit Agreement remains updated as of 2026-07-29.

Proposed edit

Update Data Center Advisory Committee meeting record to include 2026-08-07 meeting and 2026-08-14 upcoming meeting with details on water/wastewater infrastructure presentations.

Critic findings against this item (1)

no-fabricationSource URL 'https://lysanderny.gov/' is a general agency homepage, not a specific document. The summary claims specific meeting dates (2026-08-07, 2026-08-14, 2026-07-31, 2026-07-29) and detailed presentation materials, but the URL provided does not plausibly point to the specific meeting minutes or calendar page containing these facts. Per the lens: 'If source_url doesn't plausibly contain that fact (e.g. it's a general agency homepage, not the specific document), that's a violation.'

Source · 2026-08-17 ↗

verified On the main site 2026-08-17

nysdec-micron-permit-dashboard

Published to the main site on 2026-09-12 under #status: Four Micron dam safety permits issued Jun 1 and Jul 30 2026.

NYSDEC has issued Dam Safety permits (7-3124-00575/00010, 00011, 00014, 00015) on 2026-06-01 and 2026-07-30 for the Micron project. These permits postdate the last record and reflect completion of additional dam safety reviews required for the campus infrastructure.

Proposed edit

Add NYSDEC Dam Safety permits (issued 2026-06-01 and 2026-07-30) to the Micron permit tracking dashboard record.

Held only because another item in the 2026-08-17 batch was flagged. Nothing was filed against this one.

Source · 2026-07-30 ↗

verified Critic flagged 2026-08-16

town-of-lysander-official-records

Cold Springs Sewer District formation proceedings were completed with special meeting on 7-31-26 including formation resolution and environmental review; materials now documented on town website alongside regular town board governance records.

Proposed edit

Update SALTTOSILICON infrastructure context to note Cold Springs Sewer District formation completion and public participation deadline (7-31-26).

Critic findings against this item (2)

no-fabricationsource_url is 'https://lysanderny.gov/' (general agency homepage), which does not plausibly contain the specific facts claimed: Cold Springs Sewer District formation details, formation resolution, environmental review, and special meeting on 7-31-26. A general homepage is not the specific document where these details would be found. Per the rule: 'If source_url doesn't plausibly contain that fact (e.g. it's a general agency homepage, not the specific document), that's a violation.'
evidence-label-accuracyevidence is labeled 'verified', claiming 'a primary public record directly supports the statement', but source_url points only to a general homepage, not a specific primary document containing the Cold Springs Sewer District formation proceedings, resolution, or environmental review. The specificity of the claims (formation resolution, environmental review materials) requires a direct primary source document, not a homepage reference.

Source · 2026-08-15 ↗

verified Critic flagged 2026-08-15

town-of-lysander-official-records

Data Center Advisory Committee held two additional meetings with newly published materials since the last record date. August 14, 2026 meeting agenda and wastewater presentation materials now posted; August 7, 2026 meeting materials also available with wastewater technical details.

Proposed edit

Update record to reflect August 14, 2026 Data Center Advisory Committee meeting with wastewater presentation and August 7, 2026 meeting materials now available

Critic findings against this item (1)

no-fabricationSource URL (https://lysanderny.gov/) is a general agency homepage, not the specific document or page containing the cited meeting materials. The summary claims 'August 14, 2026 meeting agenda and wastewater presentation materials now posted' and 'August 7, 2026 meeting materials also available with wastewater technical details,' but the general homepage does not plausibly constitute the specific evidence location for these documents. A direct link to the Data Center Advisory Committee meeting page or materials archive would be required.

Source · 2026-08-14 ↗

verified On the main site 2026-08-15

nysdec-micron-permit-dashboard

Published to the main site on 2026-09-12 under #status: Four Micron dam safety permits issued Jun 1 and Jul 30 2026.

NYSDEC Micron permit dashboard shows Dam Safety permits issued June 1 through July 30, 2026, providing more recent permit completion dates than previously recorded (July 29). Four dam safety permits (00010, 00011, 00014, 00015) all issued within the June-July 2026 window.

Proposed edit

Update permit status record to include Dam Safety permits issued through July 30, 2026 (earlier record date was July 29)

Held only because another item in the 2026-08-15 batch was flagged. Nothing was filed against this one.

Source · 2026-07-30 ↗

verified Critic flagged 2026-08-15

white-pine-science-technology-park

The 104-acre acreage cited in the fingerprint is not present in the current page content. The webpage explicitly states 'The provided content does not include: Acreage specifications for the development.' The Final Scope has been released by OCIDA and Draft GEIS is next as expected, but the specific 104-acre figure cannot be verified from the current source.

Proposed edit

Clarify or remove the 104-acre acreage specification from the fingerprint unless a separate source document can verify it; note that the environmental review page does not provide this detail

Critic findings against this item (1)

evidence-label-accuracyEvidence is labeled 'verified,' but the substantive finding is that the 104-acre acreage specification cannot be verified from the source. The summary states 'the specific 104-acre figure cannot be verified from the current source' and quotes the page saying 'does not include: Acreage specifications for the development.' This is evidence of absence from the source (unknown or not-located class), not verification of the figure's accuracy. Label should be 'unknown' to accurately reflect that the specification is unverified from this source.

Source · 2026-06-17 ↗

verified No objection filed 2026-08-15

cny-forward-transportation-eis

CNY Forward transportation EIS scoping process has progressed with public scoping meetings held July 30 and August 6, 2026 at Clay Town Hall with multiple session times (1-3 p.m. and 4-7 p.m.). Public comment deadline is August 14, 2026, which is imminent. Community Outreach Office established at 4483 State Route 31, Clay with regular office hours (Tuesdays 9-1, Thursdays 3-7).

Proposed edit

Update to reflect current public comment deadline of August 14, 2026 and include details of scoping meetings held July 30 and August 6; note Community Outreach Office hours for continued engagement

Held only because another item in the 2026-08-15 batch was flagged. Nothing was filed against this one.

Source · 2026-08-14 ↗

verified No objection filed 2026-08-14

town-of-lysander-official-records

Town of Lysander website now shows Data Center Advisory Committee held a second meeting on August 7, 2026, with a wastewater management presentation, and a third meeting scheduled for August 14, 2026. These represent substantive new meeting activity beyond the July 31, 2026 meeting captured in the prior fingerprint.

Proposed edit

Update DCAC meeting record to include July 31 (held), August 7, 2026 (held, wastewater presentation), and August 14, 2026 (scheduled). Update meeting materials status: agendas and supporting documents published; minutes not yet published.

Held only because another item in the 2026-08-14 batch was flagged. Nothing was filed against this one.

Source · 2026-08-14 ↗

verified On the main site 2026-08-14

nysdec-micron-permit-dashboard

Published to the main site on 2026-09-12 under #status: Four Micron dam safety permits issued Jun 1 and Jul 30 2026.

NYSDEC Micron permit dashboard now shows two additional permit types with issuance dates: Air Title V permit issued March 31, 2026 (covering Fab 1 and Fab 2 emissions), and four Dam Safety permits all issued between June 1 and July 30, 2026. Prior record did not enumerate these permits separately.

Proposed edit

Add Air Title V permit (7-3124-00575/00004, issued 3/31/2026) and four Dam Safety permits (issued 6/1/2026–7/30/2026) to the Micron permit status record. Update fingerprint to reflect complete permit inventory.

Held only because another item in the 2026-08-14 batch was flagged. Nothing was filed against this one.

Source · 2026-08-14 ↗

verified No objection filed 2026-08-14

white-pine-science-technology-park

White Pine Science & Technology Park Final Scope document is now complete and finalized by OCIDA. The prior fingerprint stated acreage and that a Draft GEIS was expected next; current documentation shows no acreage mentioned in the public notice and indicates that the Final Scope will be used to prepare the Draft GEIS, meaning the GEIS has not yet begun.

Proposed edit

Update White Pine park status: Final Scope completed by OCIDA; Draft GEIS preparation phase has not yet started. Clarify that the 104-acre acreage figure from prior estimate should be verified separately (not stated in June 2026 notice).

Held only because another item in the 2026-08-14 batch was flagged. Nothing was filed against this one.

Source · 2026-08-14 ↗

verified Critic flagged 2026-08-14

cny-forward-transportation-eis

CNY Forward transportation EIS public scoping process now has firm dates: scoping meetings held/scheduled for July 30 and August 6, 2026 (both at Clay Town Hall), public comment deadline August 14, 2026. Community outreach office opened July 14, 2026 with posted office hours (Tues 9a–1p, Thurs 3–7p). These represent substantive new procedural milestones beyond the prior fingerprint's reference to routes and comment periods.

Proposed edit

Update CNY Forward EIS status with specific public scoping meeting dates (July 30, August 6, 2026) and public comment deadline (August 14, 2026). Add community outreach office location and hours (4483 State Route 31, Clay; Tues 9a–1p, Thurs 3–7p, opened July 14, 2026).

Critic findings against this item (1)

no-fabricationThe source_url is a governor's press release announcing the CNY Forward project launch. The summary includes specific operational details not plausibly contained in an announcement: office location '4483 State Route 31, Clay' and office hours 'Tues 9a–1p, Thurs 3–7p'. These details require a more specific source (project website or community outreach materials), not the governor's announcement.

Source · 2026-08-14 ↗

verified Critic flagged 2026-08-13

town-of-lysander-official-records

Data Center Advisory Committee published agenda for August 7, 2026 meeting, indicating continued regular meetings beyond the July 31 record date.

Proposed edit

Update Lysander records fingerprint to include August 7 DCAC agenda publication

Critic findings against this item (1)

no-fabricationSource URL https://lysanderny.gov/ is a general town homepage, not a direct link to the specific August 7, 2026 DCAC agenda document. Claiming a specific published agenda traces plausibly to a general agency homepage only if the agenda is prominently linked from the homepage; homepage URL alone is insufficient to support the specific claim that the agenda was published.

Source · 2026-08-07 ↗

verified Critic flagged 2026-08-13

new-york-executive-order-62

New York Grid Acceleration Fund identified as a proposed mechanism requiring data centers to contribute upfront capital for grid improvements, preventing costs to other ratepayers. This is an additional framework element beyond the 50 MW threshold, state-permit abeyance, GEIS, and local-permit exception previously recorded.

Proposed edit

Add New York Grid Acceleration Fund as a proposed provision to Executive Order 62 framework

Critic findings against this item (1)

evidence-label-accuracySummary describes 'New York Grid Acceleration Fund identified as a proposed mechanism' — the word 'proposed' indicates this is not yet law or final policy. Evidence is labeled 'verified' but the claim is about a proposed (not yet adopted) provision. If the fund exists in the executive order text, the label should clarify 'proposed provision identified in EO-62' or use 'reported' instead of 'verified' to distinguish between what the source says and what is established policy.

Source · 2026-07-14 ↗

verified Critic flagged 2026-08-13

cny-forward-transportation-eis

CNY Forward project public comment period deadline confirmed as August 14, 2026 (Friday). Scoping meetings held July 30 and August 6, 2026 with community outreach office hours available Tuesday 9am-1pm and Thursday 3pm-7pm at 4483 State Route 31, Clay, NY.

Proposed edit

Update CNY Forward fingerprint with specific comment deadline (August 14, 2026) and community engagement details

Critic findings against this item (1)

no-fabricationSummary includes highly specific operational details: 'Tuesday 9am-1pm and Thursday 3pm-7pm at 4483 State Route 31, Clay, NY.' The source URL is a governor press release announcement. Press releases typically announce projects and high-level details, not specific office hours and street addresses. These details do not plausibly originate from the governor's announcement URL without being linked to a separate detailed planning document.

Source · 2026-08-13 ↗

verified Cleared by critic 2026-08-12

town-of-lysander-official-records

Town of Lysander website shows three new Data Center Advisory Committee meeting agendas posted: August 7, 2026; July 31, 2026; and July 23, 2026. The July 31 meeting was previously noted as held with minutes pending; agendas are now visible. Additionally, Town Board published 2026 School Tax Collection dates (August 11 notice) and Cold Springs Sewer District Phase 1 supporting documents.

Proposed edit

Update Data Center Advisory Committee meeting record to include posted agendas for July 23, July 31, and August 7, 2026; note addition of Cold Springs Sewer District project documents to the public record.

Source · 2026-08-11 ↗

verified On the main site 2026-08-12

nysdec-micron-permit-dashboard

Published to the main site on 2026-09-12 under #status: Four Micron dam safety permits issued Jun 1 and Jul 30 2026.

NYSDEC permit dashboard now shows two additional Dam Safety permits issued on July 30, 2026 (permits 00014 and 00015 under application ID 7-3124-00575), which post-date the July 29 last-seen record. These are the final two of four Dam Safety permits (first two issued June 1, 2026).

Proposed edit

Update Micron permit status to include issuance of final two Dam Safety permits on July 30, 2026; note that campus permits are now substantially complete with only Oak Orchard mitigation items remaining under review.

Source · 2026-07-30 ↗

verified Cleared by critic 2026-08-12

Published to the main site on 2026-09-12 under #status: Four Micron dam safety permits issued Jun 1 and Jul 30 2026.

New dam safety permits for Micron campus have been issued (4 applications, all 'Permit Issued' between June-August 2026). These are Class A low-hazard stormwater retention dams. Previous fingerprint from July 29 did not enumerate these as part of the 'campus permits and connected-action permit dates and status.'

Proposed edit

Update nysdec-micron-permit-dashboard fingerprint to include new dam safety permits (4 applications issued June-August 2026, all Class A low-hazard stormwater retention).

Held only because another item in the 2026-08-11 batch was flagged. Nothing was filed against this one.

Source · 2026-08-11 ↗

verified Critic flagged 2026-08-11

cny-forward-transportation-eis

Public comment deadline for CNY Forward transportation EIS is confirmed as August 14, 2026. Public scoping meetings were held July 30 and August 6, 2026. The project addresses Route 31, Route 11, I-81, and Route 481 corridors in central New York.

Proposed edit

Update cny-forward-transportation-eis fingerprint to include August 14, 2026 public comment deadline and confirm completion of scoping meetings held July 30 and August 6, 2026.

Critic findings against this item (1)

no-fabricationThe source URL (https://www.governor.ny.gov/news/governor-hochul-announces-launch-central-new-york-forward-project-address-future) is a Governor's announcement page about the project launch. A general announcement page does not plausibly contain specific regulatory details such as the EIS comment deadline (August 14, 2026) or detailed scoping meeting dates (July 30 and August 6, 2026). These facts would typically trace to project-specific EIS documentation, regulatory notice pages, or formal public notice records, not launch announcements.

Source · 2026-08-14 ↗

verified Critic flagged 2026-08-10

town-of-lysander-official-records

The Town of Lysander's Data Center Advisory Committee continued meeting past the July 31, 2026 session recorded previously: a water-continuation document was presented July 31, and a wastewater presentation was posted for an August 7, 2026 committee meeting. The Community Benefit Agreement draft remains at its July 29, 2026 revision, with no newer version posted as of this check.

Proposed edit

Update the Lysander local-timeline entry to add the August 7, 2026 Data Center Advisory Committee meeting (wastewater presentation) and the July 31 water-continuation document, replacing the 'minutes not yet published' note for the July 31 meeting.

Critic findings against this item (2)

no-fabricationsource_url is 'https://lysanderny.gov/' — the town's bare homepage, not the specific committee agenda/minutes page, the July 31 water-continuation document, or the August 7 wastewater presentation. None of the specific facts in the summary (the July 31 water-continuation document, the August 7 committee meeting and its wastewater presentation, or the claim that the CBA draft is unchanged since its July 29 revision) can plausibly be confirmed from a homepage URL alone.
evidence-label-accuracyLabeled 'verified' (requires a primary public record that directly supports the statement), but the cited source_url is a generic homepage rather than the specific document/page containing the July 31 water-continuation document, the August 7 wastewater presentation, or the CBA draft-revision status — so the label overstates what the linked source actually substantiates.

Source · 2026-08-07 ↗

verified No objection filed 2026-08-10

new-york-executive-order-62

Empire State Development posted the Community Investment Framework (CIF) policy outline required by Executive Order 62's 60-day directive. It recommends a minimum host-community contribution of $1 million per MW of anticipated data-center demand (e.g. $50M for a 50 MW project, scaling to $400M at 400 MW), and defines Good Neighbor Commitments, labor commitments, an eligible-use list for a community investment fund, and standardized public-reporting requirements. Public feedback is open for 30 days to [email protected].

Proposed edit

Add a new fact to the EO 62 page describing the published Community Investment Framework policy outline, including the $1M-per-MW recommended contribution scale and the 30-day public comment window; note it is a policy outline (not yet a final template).

Held only because another item in the 2026-08-10 batch was flagged. Nothing was filed against this one.

Source · 2026-07-14 ↗

verified On the main site 2026-08-10

nysdec-micron-permit-dashboard

Published to the main site on 2026-09-12 under #status: Four Micron dam safety permits issued Jun 1 and Jul 30 2026.

All four Dam Safety permit applications for the Micron campus are now shown as issued, with issuance dates spanning June 1 through July 30, 2026 — the latest one day after this source's prior check date of July 29, 2026. Connected-action freshwater wetlands and Clean Water Act Section 401 permits tied to the water-main and gas-main extensions remain listed as under review, not yet issued.

Proposed edit

Update the Micron permit tracker to mark all four Dam Safety stormwater-retention permits as issued (through 7/30/2026) and note that connected-action wetlands/401 permits for the water-main and gas-main extensions are still under review.

Held only because another item in the 2026-08-10 batch was flagged. Nothing was filed against this one.

Source · 2026-07-30 ↗

reported No objection filed 2026-08-10

oak-orchard-final-spdes-permit-ny0030317

Neighbors for a Better Micron and Jobs to Move America filed an Article 78 petition in Albany County Supreme Court on July 31, 2026 against NYSDEC, Onondaga County, and Micron, challenging the March 31, 2026 Title V air permit and the April 10, 2026 Oak Orchard Wastewater Treatment Plant SPDES permit (this tracked source). The petition alleges the wastewater permit's expanded discharge allowance (rising from about 10 to 30.8 MGD average) lacks binding PFAS ('forever chemicals') limits and that required environmental analysis and mitigation were deferred until after the permits were issued.

Proposed edit

Add a note to the Oak Orchard SPDES permit page that the permit is under legal challenge (Article 78 petition, Albany County Supreme Court, filed 7/31/2026) alleging insufficient PFAS discharge limits; the underlying court filing itself has not been independently reviewed and should be sourced directly if tracked going forward.

Held only because another item in the 2026-08-10 batch was flagged. Nothing was filed against this one.

Source · 2026-08-01 ↗

verified Critic flagged 2026-08-10

cny-forward-transportation-eis

NYSDOT and FHWA held CNY Forward scoping meetings at Clay Town Hall on July 30 and August 6, 2026, and the scoping-comment deadline is confirmed for August 14, 2026 (submissions accepted online, in person, or by mail to NYSDOT Region 3).

Proposed edit

Add the confirmed CNY Forward scoping meeting dates (July 30 and August 6, 2026, Clay Town Hall) and the August 14, 2026 public-comment deadline to the transport section.

Critic findings against this item (2)

no-fabricationsource_url is the governor's original project-launch press release ('governor-hochul-announces-launch-central-new-york-forward-project-address-future'), which announces the initiation of the CNY Forward study/project. It does not plausibly contain the specific scoping-meeting logistics asserted in the summary — the July 30 and August 6, 2026 Clay Town Hall meeting dates or the August 14, 2026 public-comment deadline — since those are scoping-notice/meeting-schedule details, not launch-announcement content.
evidence-label-accuracyLabeled 'verified', but the linked governor.ny.gov press release is a general project-launch announcement, not a primary record of the specific scoping meeting dates (July 30, August 6) or the August 14 comment deadline being claimed — those specifics are not directly supported by the cited source.

Source · 2026-08-06 ↗

verified No objection filed 2026-08-09

town-of-lysander-official-records

The Town of Lysander homepage lists an '8-7-26 Data Center Advisory Committee Meeting' entry posted August 6, 2026, linking a meeting agenda PDF and a document titled 'Wastewater Powerpoint,' in addition to the July 31, 2026 Data Center Advisory Committee meeting already recorded in the prior fingerprint. The linked PDFs were not opened/read in this pass, so only the fact that this meeting was scheduled and these two documents were posted is confirmed here; their substantive content (what was discussed) is not verified.

Proposed edit

Add an entry noting the Town of Lysander Data Center Advisory Committee met again on August 7, 2026, with an agenda and a wastewater-focused presentation document posted August 6, 2026; update the fingerprint to reflect this newest meeting.

Held only because another item in the 2026-08-09 batch was flagged. Nothing was filed against this one.

Source · 2026-08-06 ↗

verified No objection filed 2026-08-09

town-of-lysander-official-records

The Town of Lysander homepage now shows a Notice of Special Meeting and a document titled 'Cold Springs Sewer SEQRA 7-31-26,' along with public hearing materials for a Cold Springs Sewer District Phase 1 project, dated July 31, 2026 — none of which appear in the previously recorded fingerprint. The PDF content was not read in this pass, so only the existence and posting date of this notice is confirmed; its relevance to data-center-adjacent infrastructure (vs. an unrelated town sewer matter) has not been assessed.

Proposed edit

If judged relevant to site scope, add a brief entry noting a Cold Springs Sewer District Phase 1 SEQRA public hearing notice was posted July 31, 2026 on the Town of Lysander site; otherwise note it as reviewed-and-excluded.

Held only because another item in the 2026-08-09 batch was flagged. Nothing was filed against this one.

Source · 2026-07-31 ↗

verified On the main site 2026-08-09

nysdec-micron-permit-dashboard

Published to the main site on 2026-09-12 under #status: Four Micron dam safety permits issued Jun 1 and Jul 30 2026.

The NYSDEC Micron permit dashboard now shows two Dam Safety permits issued July 30, 2026 (applications 7-3124-00575/00014 and 7-3124-00575/00015, both for Class A-low hazard stormwater retention dams) that were not present in the July 29, 2026 fingerprint. The dashboard also shows the Youngs Creek Mitigation Site (7-3124-00618/00001) and Fish Creek Mitigation Site (7-3554-00280/00001) permit statuses moved from pending to under review.

Proposed edit

Update the Micron permit tracker to add two Dam Safety permits issued July 30, 2026 for stormwater retention dams (applications 7-3124-00575/00014 and /00015), and note that the Youngs Creek and Fish Creek mitigation-site permits moved from pending to under-review status.

Held only because another item in the 2026-08-09 batch was flagged. Nothing was filed against this one.

Source · 2026-07-30 ↗

reported Critic flagged 2026-08-09

cny-forward-transportation-eis

The tracked Governor's-office launch press release for the CNY Forward project now displays specific public scoping meeting dates (Thursday, July 30 and Thursday, August 6, 2026, both at Clay Town Hall) and a public comment deadline of August 14, 2026, plus community outreach office hours at 4483 State Route 31, Clay — more specific than the general 'scoping and public-comment dates' previously recorded. Caveat: prior research passes have repeatedly surfaced similar granular meeting-date content from this same general-announcement URL, and those proposals were held in review on the grounds that a project-launch press release is an implausible primary source for this level of scheduling detail (see 2026-08-01, 2026-08-02, and 2026-08-06 verdicts on this source). This content should be independently corroborated against the project's own site (cnyforward.com) before being treated as confirmed.

Proposed edit

Do not publish these meeting/comment dates from this source alone. If corroborated against cnyforward.com/documents/ or another primary CNY Forward project source, add the July 30 and August 6, 2026 scoping meeting dates and the August 14, 2026 comment deadline to the site, and consider retargeting this tracked source to the project's own documents page.

Critic findings against this item (1)

no-fabricationThe summary presents specific scheduling facts — 'Thursday, July 30 and Thursday, August 6, 2026, both at Clay Town Hall,' a 'public comment deadline of August 14, 2026,' and 'community outreach office hours at 4483 State Route 31, Clay' — as newly observed content on a Governor's-office project-launch press release (source_url is the 'announces-launch' page). A static launch announcement is an implausible place for updated meeting/comment scheduling to appear weeks after publication, and the entry's own caveat admits this exact pattern was already flagged and held on 2026-08-01, 2026-08-02, and 2026-08-06 for the same source. Recurrence of the same implausible-primary-source claim, unresolved, means source_url does not plausibly contain these facts — the definition of a no-fabrication violation — regardless of the hedged proposed_change.

Source · 2026-08-09 ↗

verified No objection filed 2026-08-09

onondaga-lake-superfund-reuse-profile

The EPA Superfund redevelopment page for Onondaga Lake now includes specific ecological-recovery figures not previously recorded: about 90 acres of wetlands restored and about 1.1 million native plants planted; more than 60 fish species now present versus nine to twelve species recorded in the 1970s; more than 250 wildlife species on-site including more than 120 bird species; a deep-water fishing pier completed in early 2023; and a 'Loop the Lake Trail.' The page also states that, as of December 2025, there are 13 on-site businesses employing 211 people generating about $48.4 million in annual sales revenue.

Proposed edit

Add updated Onondaga Lake reuse figures to the site: ~90 acres of wetlands restored, ~1.1 million native plants, 60+ fish species (up from 9-12 in the 1970s), 250+ wildlife species including 120+ bird species, the 2023 fishing pier and Loop the Lake Trail, and the December 2025 economic figures (13 businesses, 211 jobs, ~$48.4M in annual sales).

Held only because another item in the 2026-08-09 batch was flagged. Nothing was filed against this one.

Source · 2025-12 ↗

verified Critic flagged 2026-08-08

town-of-lysander-official-records

The Town of Lysander's Data Center Information notices page (a specific subpage, not the site homepage) shows an additional Data Center Advisory Committee entry beyond the July 31, 2026 meeting recorded in the prior fingerprint: an '8-7-26 Data Center Advisory Committee Meeting' listing posted August 6, 2026, linking a meeting agenda and a wastewater-focused presentation document. The interior content of those two PDFs could not be extracted by automated fetch, so only the fact that this meeting and its two named documents were posted is confirmed here, not their substance.

Proposed edit

Add an entry noting the Town of Lysander Data Center Advisory Committee met again on August 7, 2026 (agenda and wastewater presentation posted August 6, 2026), as the committee's third recorded meeting after July 23 and July 31, 2026; update the fingerprint to reference this page by its specific notices URL rather than the site root.

Critic findings against this item (1)

no-fabricationproposed_change asserts the August 7 meeting is 'the committee's third recorded meeting after July 23 and July 31, 2026' — introducing a July 23, 2026 meeting date that appears nowhere else in this entry. The summary field only references 'the July 31, 2026 meeting recorded in the prior fingerprint' (singular), so the prior record establishes just one earlier meeting, not two. Neither source_url (the notices subpage, which per the summary's own admission had its two linked PDFs unreadable by automated fetch) nor the summary text supports a July 23, 2026 meeting existing at all. That date is not traceable to source_url and should not be asserted as fact in the content pushed to the wiki.

Source · 2026-08-06 ↗

verified Critic flagged 2026-08-07

town-of-lysander-official-records

The Town of Lysander Town Board approved a resolution forming the Cold Springs Sewer District No. 1 at its July 31, 2026 special meeting, following a public hearing and filing of a Map, Plan and Report and a SEQRA environmental assessment (posted July 21, 2026). The estimated district cost is about $3.17 million, with an annual charge of $720 per EDU; the town has tied the district's timing to anticipated population growth from the nearby Micron facility.

Proposed edit

Add the Cold Springs Sewer District No. 1 formation (approved July 31, 2026, ~$3.17M estimated cost) to the Lysander local-infrastructure tracking as a new water/sewer item connected to Micron-driven growth, distinct from the still-unpublished Data Center Advisory Committee minutes.

Critic findings against this item (2)

no-fabricationThe summary cites specific facts — the July 31, 2026 special meeting date, the public hearing, the Map/Plan/Report filing, the SEQRA assessment 'posted July 21, 2026', the '~$3.17 million' district cost, and the '$720 per EDU' annual charge — but source_url is only 'https://lysanderny.gov/', the town's general homepage. That URL does not point to the resolution, meeting minutes, or Map/Plan/Report document that would actually contain these dates and figures.
evidence-label-accuracyevidence is labeled 'verified', which per the lens requires a primary public record that directly supports the statement. The only source_url given is the lysanderny.gov homepage, not the specific resolution/report — as sourced, this cannot be confirmed as a directly-supported 'verified' fact rather than a 'reported' one.

Source · 2026-07-31 ↗

verified On the main site 2026-08-07

nysdec-micron-permit-dashboard

Published to the main site on 2026-09-12 under #status: Four Micron dam safety permits issued Jun 1 and Jul 30 2026.

The NYSDEC Micron permit dashboard now shows two additional Dam Safety permits for the Micron campus issued July 30, 2026, completing the set of four Dam Safety permits (two others were issued June 1, 2026). This postdates the prior fingerprint check of July 29, 2026.

Proposed edit

Update the Micron permit-status page to note all four Dam Safety permits (IDs ending 00010, 00011, 00014, 00015) are now issued, with the last two dated July 30, 2026.

Held only because another item in the 2026-08-07 batch was flagged. Nothing was filed against this one.

Source · 2026-07-30 ↗

verified Critic flagged 2026-08-06

cny-forward-transportation-eis

The Governor's office announcement page for the CNY Forward transportation EIS now carries a specific process timeline that was not previously on record: NYSDOT and FHWA published a Notice of Intent on July 10, 2026 opening the environmental scoping phase for Route 31, Route 11, I-81 and Route 481 improvements in Cicero and Clay; public scoping meetings are set for July 30 and August 6, 2026 at Clay Town Hall (afternoon and early-evening sessions each day); a community outreach office is open Tuesdays and Thursdays at 4483 State Route 31, Clay; and the public comment period closes August 14, 2026.

Proposed edit

Update the CNY Forward EIS wiki page with the July 10, 2026 Notice of Intent, the July 30 and August 6, 2026 scoping meeting dates/times at Clay Town Hall, the Clay outreach-office hours, and the August 14, 2026 public comment deadline.

Critic findings against this item (2)

no-fabricationThe source_url is a Governor's office news page titled 'governor-hochul-announces-launch-central-new-york-forward-project-address-future' — a general project-launch press release. The summary attributes to it a level of procedural detail (exact scoping meeting times described as 'afternoon and early-evening sessions each day,' the outreach office's specific address '4483 State Route 31, Clay' and open days 'Tuesdays and Thursdays,' and an exact comment-period close date of 'August 14, 2026') that is characteristic of a formal NOI/scoping notice document, not a high-level gubernatorial announcement page. This is the lens's own example of the violation: 'a general agency homepage, not the specific document.' Absent confirmation that the governor's announcement page itself contains these granular logistics (rather than a separate NOI filing or meeting notice PDF), these specifics do not plausibly trace to the cited source_url.
evidence-label-accuracyThe entry is labeled 'verified,' which requires a primary public record that directly supports the statement. While the Governor's office page qualifies as a primary record for the top-level fact that the project was announced on July 10, 2026, the summary bundles in specific times, an address, office hours, and a comment deadline that likely originate from a distinct scoping-notice or meeting-notice document rather than the press-release page itself. Labeling the entire compound statement 'verified' when the granular logistics may only be 'reported' (or sourced from an unlinked secondary document) overstates the evidentiary support of the cited source_url.

Source · 2026-07-10 ↗

verified On the main site 2026-08-04

nysdec-micron-permit-dashboard

Published to the main site on 2026-09-12 under #status: Four Micron dam safety permits issued Jun 1 and Jul 30 2026.

The NYSDEC Micron permit dashboard now shows dated issuance for all major campus and connected-action permits: Air Title V permit issued 3/31/2026; four Dam Safety permits issued between 6/1/2026 and 7/30/2026 (the latter is one day after this source's prior 2026-07-29 check date); Water Services to White Pine Commerce Park issued 3/23/2026; Gas Main Extension issued 5/20/2026; OCWA Raw Water Pump Station permit issued 6/8/2026. Oak Orchard Wastewater Treatment Plant permits remain listed as under review. The individual DEC environmental-notice-bulletin pages for the White Pine water mains, gas main extension, and OCWA pump station applications still display only their original December 2025 / July 2025 'Notice of Complete Application' status and were not themselves updated; the dashboard is the more current record for issuance status.

Proposed edit

Update the Micron permitting status to reflect that the Air Title V permit, four Dam Safety permits, and all three tracked connected-action permits (White Pine water mains, gas main extension, OCWA pump station) are now shown as issued with specific dates, while Oak Orchard permits remain under review.

Critic findings against this item (1)

no-fabricationsource_url is https://dec.ny.gov/environmental-protection/facilities-in-your-neighborhood/micron, DEC's generic per-facility landing page template (the same URL pattern used for hundreds of unrelated facilities), not a link to a specific dashboard view, document ID, or dated record. The summary nonetheless attributes five distinct, precisely dated permit-issuance facts to this one URL (Air Title V 3/31/2026; four Dam Safety permits 6/1/2026-7/30/2026; Water Services to White Pine 3/23/2026; Gas Main Extension 5/20/2026; OCWA Raw Water Pump Station 6/8/2026) plus a sixth claim (Oak Orchard 'remain listed as under review'). This is exactly the pattern the rule calls out as a violation trigger -- a general agency page cited for facts that require a specific document/dashboard section to substantiate. Nothing in source_url or the entry indicates the page actually renders a dated permit-status table; per the skill's ambiguity-resolves-to-hold instruction, this must be flagged rather than passed.

Source · 2026-08-04 ↗

verified No objection filed 2026-08-03

town-of-lysander-official-records

The Town of Lysander's Data Center Advisory Committee posted a revised community-benefit agreement draft dated July 29, 2026, a further revision beyond the version described in the fingerprint recorded July 23, 2026.

Proposed edit

Update the Lysander local-records page to reference the July 29, 2026 revised community-benefit agreement draft as the current version.

Held only because another item in the 2026-08-03 batch was flagged. Nothing was filed against this one.

Source · 2026-07-29 ↗

verified Critic flagged 2026-08-03

town-of-lysander-official-records

A Data Center Advisory Committee meeting was posted for July 31, 2026, with an agenda and a separate document continuing the committee's water-supply discussion, both dated after the July 23, 2026 fingerprint.

Proposed edit

Note the July 31, 2026 Data Center Advisory Committee meeting (agenda and continued water-supply discussion document) on the Lysander local-records page.

Critic findings against this item (1)

no-fabricationThe summary asserts two distinct documents were posted for the July 31, 2026 meeting: the agenda and 'a separate document continuing the committee's water-supply discussion.' Only one source_url is given (datacenteradvisorycommitteeagenda7-31-26.pdf), which by its own filename is the agenda. The claimed second, separate water-supply document has no source_url tracing it, so that specific named document does not plausibly trace to the cited source.

Source · 2026-07-31 ↗

verified No objection filed 2026-08-03

responsible-data-center-development-act

The New York Senate passed an Assembly substitute of the Responsible Data Center Development Act (A11560, replacing S10642) on a 43-17 vote on June 4, 2026, moving the bill from committee referral to a floor vote; the fingerprint on record predates this and only described a general legislative record.

Proposed edit

Update the Responsible Data Center Development Act page to record the June 4, 2026 Senate floor vote (43-17) passing the A11560 substitute, and note it is pending in the Assembly.

Held only because another item in the 2026-08-03 batch was flagged. Nothing was filed against this one.

Source · 2026-06-04 ↗

verified No objection filed 2026-08-03

psc-case-26-e-0045-large-load-interconnection

The Commission extended the comment schedule in Case 26-E-0045 beyond the deadline structure implied by the February 12, 2026 fingerprint: initial comments were moved from April 13 to May 13, 2026, and a new response-comment deadline of June 15, 2026 (4:30 PM ET) was set, per the Commission's revised notice.

Proposed edit

Update the PSC Case 26-E-0045 page to reflect the extended comment schedule (initial comments to May 13, 2026; response comments to June 15, 2026).

Held only because another item in the 2026-08-03 batch was flagged. Nothing was filed against this one.

Source · 2026-06-15 ↗

verified No objection filed 2026-08-03

micron-final-eis-and-appendices

The CHIPS Program Office issued a Record of Decision on December 16, 2025 (confirmed by the document's own title page and PDF creation metadata) approving disbursement of CHIPS Incentives Program federal financial assistance to Micron for the Clay, New York project, a step beyond the November 12, 2025 Final EIS acceptance described in the current fingerprint.

Proposed edit

Add the December 16, 2025 CHIPS Program Office Record of Decision (approving federal financial assistance disbursement) to the Micron Final EIS page/timeline, citing the ROD document directly rather than the general NIST NEPA/CHIPS landing page.

Held only because another item in the 2026-08-03 batch was flagged. Nothing was filed against this one.

Source · 2025-12-16 ↗

verified Critic flagged 2026-08-02

town-of-lysander-official-records

The Town of Lysander's Data Center Advisory Committee posted an updated community-benefit agreement draft (dated 7-29-2026) and held a committee meeting on 7-31-2026 with an agenda including a continued water presentation, superseding the version on record as of 2026-07-23.

Proposed edit

Update the Lysander local-records page to reflect the 7-29-2026 revised community-benefit agreement and the 7-31-2026 Data Center Advisory Committee agenda/water presentation continuation.

Critic findings against this item (1)

no-fabricationsource_url is the bare town homepage 'https://lysanderny.gov/', not a specific page for the Data Center Advisory Committee's community-benefit agreement draft or the 7-31-2026 meeting agenda. This is exactly the 'general agency homepage, not the specific document' case the rule calls out — the specific dated facts (7-29-2026 draft, 7-31-2026 agenda item) do not plausibly trace to the root homepage URL.

Source · 2026-07-31 ↗

verified Critic flagged 2026-08-02

psc-case-26-e-0045-large-load-interconnection

PSC Case 26-E-0045 comment deadlines have been extended: the initial-comment deadline moved from April 13, 2026 to May 13, 2026, and a response-comment deadline of June 15, 2026 (4:30 PM ET) has been set, both later than the 2026-02-12 record.

Proposed edit

Update the PSC Case 26-E-0045 page to note the extended comment deadlines (initial comments to May 13, 2026; response comments to June 15, 2026).

Critic findings against this item (1)

no-fabricationsource_url title is 'response-comments-due-proceeding-motion-commission-address-interconnection-reforms-large' — a DPS event page specific to the response-comment deadline (June 15, 2026). The summary also asserts a separate fact, that the initial-comment deadline moved from April 13 to May 13, 2026, which is a distinct procedural event; it is not established that this response-comments-due event page also documents the earlier initial-comment deadline change. Per the lens, ambiguity about whether a fact traces to the cited URL resolves to a violation.

Source · 2026-06-15 ↗

verified Critic flagged 2026-08-02

micron-final-eis-and-appendices

The CHIPS Program Office completed a Record of Decision on December 16, 2025, approving federal financial assistance disbursements to Micron for the Clay, New York facility, a step beyond the November 12, 2025 Final EIS acceptance previously on record.

Proposed edit

Add the December 16, 2025 CHIPS Program Office Record of Decision (federal financial assistance approval) to the Micron Final EIS page/timeline.

Critic findings against this item (1)

no-fabricationsource_url is NIST's general 'implementation-strategies' NEPA/CHIPS Act overview page, not a specific Record-of-Decision document or announcement dated December 16, 2025. The summary's specific claim (a ROD completed on that exact date approving federal financial assistance disbursements to Micron) is the precise kind of fact the lens example flags as not plausibly contained on a general agency landing page.

Source · 2025-12-16 ↗

verified Critic flagged 2026-08-02

cny-forward-transportation-eis

The CNY Forward EIS scoping process now has concrete public-participation dates not previously on record: in-person scoping meetings at Clay Town Hall on July 30 and August 6, 2026, and a written-comment deadline of August 14, 2026.

Proposed edit

Add the CNY Forward scoping meeting dates (July 30 and August 6, 2026, Clay Town Hall) and the August 14, 2026 written-comment deadline to the transportation EIS page.

Critic findings against this item (1)

no-fabricationsource_url is Governor Hochul's July 10, 2026 press release announcing the *launch* of the CNY Forward project. The summary attributes to this same source specific downstream EIS scoping logistics — exact meeting dates of July 30 and August 6, 2026 at Clay Town Hall, and an August 14, 2026 written-comment deadline — that a project-launch announcement would not typically contain, especially since some of those dates (July 30) fall before other cited content would have been finalized. This combination is not plausibly supported by a launch-announcement press release.

Source · 2026-07-10 ↗

verified Critic flagged 2026-08-01

town-of-lysander-official-records

The Town posted a Data Center Advisory Committee meeting agenda for July 31, 2026, together with an updated Community Benefit Agreement draft dated July 29, 2026, superseding the previously posted revised CBA-suggestions document from July 23, 2026.

Proposed edit

Update the local page's data-center-committee note to reference the July 31, 2026 agenda and the July 29, 2026 Community Benefit Agreement draft as the current documents in place of the July 23, 2026 revision.

Critic findings against this item (1)

no-fabricationsource_url points only to 'datacenteradvisorycommitteeagenda7-31-26.pdf' (the meeting agenda), but the summary also asserts the existence, exact date (July 29, 2026), and superseding status of a separate 'Community Benefit Agreement draft' relative to a named prior version (July 23, 2026). Nothing in the cited URL establishes that this specific CBA draft document, its date, or its supersession relationship are contained there rather than in a different, uncited file.

Source · 2026-07-31 ↗

verified Critic flagged 2026-08-01

town-of-lysander-official-records

A new Cold Springs Sewer District No. 1 formation process is underway: a formation resolution and SEQR resolution revised July 31, 2026, a Map/Plan/Report, and a public hearing notice for a July 31, 2026 Town Board special meeting have all been posted; none of this appeared in the prior fingerprint.

Proposed edit

Add a note on the Cold Springs Sewer District No. 1 formation process (public hearing and Town Board special meeting July 31, 2026) to the local page, and flag it as a candidate for its own tracked source given its proximity to the data-center growth corridor.

Critic findings against this item (1)

no-fabricationsource_url is the single PDF 'cold_springs_road_sewer_district_ph_notice_7.31.2026_0.pdf' (a public hearing notice), but the summary attributes specific, separate facts to it: a 'formation resolution and SEQR resolution revised July 31, 2026' and a 'Map/Plan/Report' being posted. These are distinct documents from the hearing notice itself; the cited URL does not establish that the resolutions carry that exact revision date or that the Map/Plan/Report was independently posted.

Source · 2026-07-31 ↗

verified Critic flagged 2026-08-01

responsible-data-center-development-act

The Responsible Data Center Development Act, via its Assembly companion/substitute A11560, passed the New York State Senate floor vote 43-17-1 on June 4, 2026 — a status change from the prior fingerprint, which recorded only the existence of the legislative record with no vote outcome.

Proposed edit

Update the tracked status of S10642/A11560 to 'passed the Senate (as A11560) on June 4, 2026, 43-17-1' and note that further action (Assembly floor vote or gubernatorial action) is not yet confirmed on this page.

Critic findings against this item (1)

no-fabricationsource_url is the NY Senate page for bill S10642, but the summary's specific vote tally ('43-17-1') and floor-vote date (June 4, 2026) are attributed to 'its Assembly companion/substitute A11560' — a different bill number in a different chamber. The cited S10642 page is not shown to be the record for an A11560 vote; the exact tally needs to trace to a page for the bill it was actually cast on.

Source · 2026-06-04 ↗

verified Critic flagged 2026-08-01

psc-case-26-e-0045-large-load-interconnection

Specific comment deadlines have been set for this proceeding since the fingerprint was recorded (Feb 12, 2026, which named only the general reform topics): the initial comment deadline was extended from April 13 to May 13, 2026, and response comments were due June 15, 2026.

Proposed edit

Add the comment schedule (initial comments extended to May 13, 2026; response comments due June 15, 2026) to the PSC Case 26-E-0045 entry.

Critic findings against this item (1)

no-fabricationsource_url is a single DPS calendar/event page titled 'response comments due ... ' dated 2026-06-15. The summary also asserts an earlier, distinct scheduling fact — that the initial comment deadline was 'extended from April 13 to May 13, 2026' — which is a different event than the one the cited page announces, and is not established as content of that page.

Source · 2026-06-15 ↗

verified Critic flagged 2026-08-01

micron-final-eis-and-appendices

The CHIPS Program Office issued a Record of Decision on December 16, 2025, approving disbursement of federal financial assistance to Micron and finding the Final EIS's Preferred Action Alternative satisfies NEPA — a milestone postdating the fingerprint recorded November 12, 2025.

Proposed edit

Add the December 16, 2025 Record of Decision (CHIPS financial-assistance disbursement approval, Final EIS found NEPA-sufficient) to the Micron EIS/permitting timeline.

Critic findings against this item (1)

no-fabricationsource_url (nist.gov/chips/implementation-strategies/national-environmental-policy-act-nepa-and-chips-act) is a general topical overview page about the NEPA/CHIPS process, not the specific December 16, 2025 Record of Decision document. This matches the lens's own named failure case: a general agency page cited for a specific document's contents and date.

Source · 2025-12-16 ↗

verified No objection filed 2026-08-01

white-pine-pump-station-and-force-mains

Onondaga County's project page now reports construction progress beyond the original cost/route/capacity description: Caughdenoy Road reopened to traffic on September 2, 2025, sewer-line installation was underway as of May 2025, and construction (begun Spring 2025) is expected to finish Fall 2026. The core figures (about $36.4 million cost, 20,400 feet of force mains, 5.5 MGD peak design flow) are unchanged.

Proposed edit

Add the construction-progress milestones (Caughdenoy Road reopening, Spring 2025 start / Fall 2026 target completion) to the entry, keeping the existing cost/route/flow figures as-is.

Held only because another item in the 2026-08-01 batch was flagged. Nothing was filed against this one.

Source · 2025-09-02 ↗

verified Critic flagged 2026-08-01

cny-forward-transportation-eis

The governor's CNY Forward project page specifies concrete scoping-meeting dates (July 30 and August 6, 2026, at Clay Town Hall, 1-3 p.m. and 4-7 p.m. sessions), a public-comment deadline of August 14, 2026, and a dedicated outreach office at 4483 State Route 31, Clay, open since July 14, 2026 — none of which appeared in the prior fingerprint, which named only the corridor routes.

Proposed edit

Add the CNY Forward scoping-meeting schedule (July 30 and August 6, 2026), the August 14, 2026 comment deadline, and the Clay outreach-office address/hours to the transportation-EIS entry.

Critic findings against this item (1)

no-fabricationsource_url is a single governor's-office press release announcing the CNY Forward project launch. The summary additionally cites granular logistics — two named session time windows (1-3 p.m. and 4-7 p.m.) at a specific venue, a specific street address for an outreach office, and that the office has been 'open since July 14, 2026' (two weeks before the July 30 announcement date). It is not established that a launch press release, rather than a separate fact sheet or office notice, is the source of these specific operational details.

Source · 2026-07-30 ↗

verified Critic flagged 2026-08-01

lysander-town-board-minutes

A Town Board Special Meeting was posted and confirmed on the board-meetings archive for July 31, 2026 (agenda covering the Cold Springs Sewer District formation, SEQR resolution, and procurement policy); minutes are not yet published as of this check.

Proposed edit

Add the July 31, 2026 Special Meeting to the board-meetings index; note minutes are pending.

Critic findings against this item (1)

no-fabricationsource_url is 'lysanderny.gov/board-meetings', a generic meetings index/archive page. The summary asserts specific agenda content for the July 31 special meeting (Cold Springs Sewer District formation, SEQR resolution, and procurement policy) — an index listing page typically shows only meeting title/date/link, not itemized agenda topics, so this level of detail is not established as coming from the cited URL.

Source · 2026-07-31 ↗