Wisconsin research coverage.

Source references: WI-S0002, WI-S0003, WI-S0004

• WEDC certification letters, application files and any award amounts were not located.
• WEDC's wider press archive was not swept for other data center announcements because the session WebSearch budget was exhausted.

Source references: WI-S0005, WI-S0006, WI-S0007, WI-S0008, WI-S0009

• Every apps.psc.wi.gov docket page returned HTTP 403 to curl and to WebFetch, so no filings, electric service agreements, load forecasts or MW figures were read.
• Docket 6680-TE-115 and the ATC Ozaukee County interconnection docket were not read.
• Alliant and other utility large-load tariff filings could not be searched (WebSearch budget exhausted).

Source references: WI-S0010, WI-S0011

• No statewide DNR air permit search was run for other data center generator permits (Microsoft Mount Pleasant, Meta Beaver Dam, colocation sites); the permit search portal was not queried because the WebSearch budget was exhausted and no direct query URL was known.
• Individual permit PDFs, the environmental analysis summary and the WEPA compliance determination were not downloaded.
• No generator megawatt total appears in the DNR pages read, so no generation capacity is recorded.

Source references: WI-S0012, WI-S0014, WI-S0015, WI-S0016, WI-S0042, WI-S0043, WI-S0044, WI-S0045

• Port Washington and Kenosha municipal sites returned HTTP 403 and Beaver Dam's document centre refused connections, so no minutes, ordinances or staff reports were read for those cities.
• No assessor or GIS parcel records were queried for any Wisconsin site; no parcel IDs were captured.
• Caledonia's homepage contained no data center material and no case file was located.

Source references: WI-S0013, WI-S0017, WI-S0018, WI-S0019

• No TID project plan, development agreement or PILOT document was read for Beaver Dam, Port Washington, Mount Pleasant, Kenosha or the Town of Beloit.
• Wisconsin Watch articles on community nondisclosure agreements and the Port Washington TIF referendum returned HTTP 429, so the four communities that signed secrecy deals were not identified.
• Searches for the Port Washington TID and development agreement could not be run (WebSearch budget exhausted).

Source references: WI-S0020, WI-S0021, WI-S0022, WI-S0023, WI-S0024, WI-S0025, WI-S0026, WI-S0027, WI-S0028, WI-S0029, WI-S0030, WI-S0031

• The EdgeConneX Madison page returned HTTP 403.
• Amazon Web Services, Google, Oracle and Apple location pages were not checked for Wisconsin sites.
• Colocation operators absent from Compute Atlas were not enumerated.

Source references: WI-S0001

• Directory listings cited by Compute Atlas (Baxtel, datacenterHawk, datacentermap) were not opened.
• No other licensed dataset was consulted for Wisconsin.

Source references: WI-S0032, WI-S0033, WI-S0034, WI-S0035, WI-S0036, WI-S0037, WI-S0040, WI-S0047, WI-S0048

• No municipal withdrawal letter, denial or rescission record was read for any of these projects.
• WTMJ's year-end review (HTTP 403) and three DataCenterDynamics articles (HTTP 403) were not read.
• Wisconsin Watch follow-ups on Cassville and Cloverleaf Carlton were rate-limited (HTTP 429) or not attempted to avoid hammering the host.

Source references: WI-S0038, WI-S0039, WI-S0041, WI-S0046

• No general news sweep was possible after the session WebSearch budget was exhausted; discovery after that point followed Compute Atlas source URLs and links inside fetched pages only.