{
  "schemaVersion": 2,
  "edition": "2026-10-28-batch-9",
  "scope": "27 source-verified instrument records and 4 needs-review records, 38 linked provisions, plus official proposal/source leads across 15 states; bounded sample, not comprehensive national survey.",
  "jurisdictions": [
    {
      "id": "us",
      "name": "United States",
      "authorityType": "Federal",
      "parentIds": [],
      "geographicScope": "United States",
      "boundarySource": "site/app/data-center/states.json",
      "boundaryVersion": "illustrative state navigation geometry"
    },
    {
      "id": "virginia",
      "name": "Virginia",
      "authorityType": "State",
      "parentIds": [
        "us"
      ],
      "geographicScope": "Commonwealth of Virginia",
      "boundarySource": "site/app/data-center/states.json",
      "boundaryVersion": "illustrative state navigation geometry"
    },
    {
      "id": "fairfax-county",
      "name": "Fairfax County",
      "authorityType": "Local",
      "parentIds": [
        "virginia"
      ],
      "geographicScope": "Fairfax County zoning jurisdiction",
      "boundarySource": null,
      "boundaryVersion": null
    },
    {
      "id": "ohio-power",
      "name": "Ohio Power Company service territory",
      "authorityType": "Utility",
      "parentIds": [
        "us"
      ],
      "geographicScope": "Ohio Power Company service territory; not statewide",
      "boundarySource": null,
      "boundaryVersion": null
    },
    {
      "id": "loudoun-county",
      "name": "Loudoun County",
      "authorityType": "Local",
      "parentIds": [
        "virginia"
      ],
      "geographicScope": "Loudoun County zoning jurisdiction",
      "boundarySource": null,
      "boundaryVersion": null
    },
    {
      "id": "minnesota",
      "name": "Minnesota",
      "authorityType": "State",
      "parentIds": [
        "us"
      ],
      "geographicScope": "Minnesota; project-specific permits may be narrower",
      "boundarySource": "site/app/data-center/states.json",
      "boundaryVersion": "illustrative state navigation geometry"
    },
    {
      "id": "pennsylvania",
      "name": "Pennsylvania",
      "authorityType": "State",
      "parentIds": [
        "us"
      ],
      "geographicScope": "Commonwealth of Pennsylvania",
      "boundarySource": "site/app/data-center/states.json",
      "boundaryVersion": "illustrative state navigation geometry"
    },
    {
      "id": "utah",
      "name": "Utah",
      "authorityType": "State",
      "parentIds": [
        "us"
      ],
      "geographicScope": "State of Utah",
      "boundarySource": "site/app/data-center/states.json",
      "boundaryVersion": "illustrative state navigation geometry"
    },
    {
      "id": "oregon",
      "name": "Oregon",
      "authorityType": "State",
      "parentIds": [
        "us"
      ],
      "geographicScope": "State of Oregon; utility implementation may be narrower",
      "boundarySource": "site/app/data-center/states.json",
      "boundaryVersion": "illustrative state navigation geometry"
    },
    {
      "id": "california",
      "name": "California",
      "authorityType": "State",
      "parentIds": [
        "us"
      ],
      "geographicScope": "California",
      "boundarySource": "site/app/data-center/states.json",
      "boundaryVersion": "illustrative state navigation geometry"
    },
    {
      "id": "florida",
      "name": "Florida",
      "authorityType": "State",
      "parentIds": [
        "us"
      ],
      "geographicScope": "Florida",
      "boundarySource": "site/app/data-center/states.json",
      "boundaryVersion": "illustrative state navigation geometry"
    },
    {
      "id": "south-dakota",
      "name": "South Dakota",
      "authorityType": "State",
      "parentIds": [
        "us"
      ],
      "geographicScope": "South Dakota",
      "boundarySource": "site/app/data-center/states.json",
      "boundaryVersion": "illustrative state navigation geometry"
    },
    {
      "id": "nebraska",
      "name": "Nebraska",
      "authorityType": "State",
      "parentIds": [
        "us"
      ],
      "geographicScope": "Nebraska",
      "boundarySource": "site/app/data-center/states.json",
      "boundaryVersion": "illustrative state navigation geometry"
    },
    {
      "id": "nevada",
      "name": "Nevada",
      "authorityType": "State",
      "parentIds": [
        "us"
      ],
      "geographicScope": "Nevada",
      "boundarySource": "site/app/data-center/states.json",
      "boundaryVersion": "illustrative state navigation geometry"
    },
    {
      "id": "oklahoma",
      "name": "Oklahoma",
      "authorityType": "State",
      "parentIds": [
        "us"
      ],
      "geographicScope": "State of Oklahoma",
      "boundarySource": "site/app/data-center/states.json",
      "boundaryVersion": "illustrative state navigation geometry"
    },
    {
      "id": "new-jersey",
      "name": "New Jersey",
      "authorityType": "State",
      "parentIds": [
        "us"
      ],
      "geographicScope": "State of New Jersey",
      "boundarySource": "site/app/data-center/states.json",
      "boundaryVersion": "illustrative state navigation geometry"
    },
    {
      "id": "illinois",
      "name": "Illinois",
      "authorityType": "State",
      "parentIds": [
        "us"
      ],
      "geographicScope": "State of Illinois",
      "boundarySource": "site/app/data-center/states.json",
      "boundaryVersion": "illustrative state navigation geometry"
    },
    {
      "id": "arizona",
      "name": "Arizona",
      "authorityType": "State",
      "parentIds": [
        "us"
      ],
      "geographicScope": "State of Arizona",
      "boundarySource": "site/app/data-center/states.json",
      "boundaryVersion": "illustrative state navigation geometry"
    }
  ],
  "legalInstruments": [
    {
      "id": "fairfax-data-center-zoning-2024",
      "title": "Fairfax County Data Center Zoning Ordinance Amendment",
      "officialIdentifier": "ZO 112.1-2024-9 and ZO 112.2-2024-8",
      "jurisdictionIds": [
        "fairfax-county"
      ],
      "state": "Virginia",
      "authority": "Local",
      "instrumentType": "Ordinance",
      "bindingForce": "Binding",
      "legalStatus": "Effective",
      "litigationStatus": "Unknown",
      "adoptionDate": "2024-09-10",
      "effectiveDate": "2024-09-11",
      "sunsetDate": null,
      "officialUrl": "https://www.fairfaxcounty.gov/planning-development/sites/planning-development/files/Assets/Documents/zoning%20ordinance/adopted%20amendments/ZO_112_1-2024-9.pdf",
      "relatedInstrumentIds": [],
      "reviewStatus": "Source-verified",
      "checked": "2026-10-28",
      "residentSummary": "For covered data centers in Fairfax County, the adopted zoning standards require noise studies before site-plan approval and before a Nonresidential Use Permit, equipment screening, and minimum distances from residential lots, subject to specified special-exception routes and transition rules.",
      "applicabilityNote": "Use-specific zoning standards apply according to the county's use tables and approval route. This amendment is a local zoning rule, not a Virginia-wide rule.",
      "limitations": "Noise-study provisions require a showing of compliance with the separate County Noise Ordinance; this record does not independently normalize Chapter 108.1's measurement limits. The official amendment history page was checked for the listed adoption/effective dates and recent amendments.",
      "sourceIds": [
        "fairfax-text",
        "fairfax-history"
      ]
    },
    {
      "id": "virginia-heuf-site-assessment-2026",
      "title": "Siting of data centers; site assessment",
      "officialIdentifier": "Va. Code § 15.2-2209.5",
      "jurisdictionIds": [
        "virginia"
      ],
      "state": "Virginia",
      "authority": "State",
      "instrumentType": "Statute",
      "bindingForce": "Binding",
      "legalStatus": "Effective",
      "litigationStatus": "Unknown",
      "adoptionDate": null,
      "effectiveDate": null,
      "sunsetDate": null,
      "officialUrl": "https://law.lis.virginia.gov/vacode/title15.2/chapter22/section15.2-2209.5/",
      "relatedInstrumentIds": [],
      "reviewStatus": "Source-verified",
      "checked": "2026-10-28",
      "residentSummary": "Before approving specified land-use applications for a new high-energy-use facility reasonably expected to draw at least 100 MW from a retail electric utility, a locality must require an assessment of sound impacts on homes and schools within 500 feet and a utility form describing serving substations and anticipated voltage, to the extent known and practicable.",
      "applicabilityNote": "A locality may also require assessments of water, agricultural, park, historic-site, and forestland effects. The statute preserves local zoning authority and does not transfer State Corporation Commission jurisdiction. A limited expansion/modification exception applies when added power does not reach 100 MW.",
      "limitations": "The current Virginia Code text cites 2026 Acts chapters 567 and 568 but the source page does not display an effective date; date left unknown. Facility must meet the statutory HEUF threshold and a covered rezoning, special exception, or special use permit must be at issue.",
      "sourceIds": [
        "virginia-code"
      ]
    },
    {
      "id": "federal-stationary-rice-zzzz",
      "title": "Stationary reciprocating engines: selected emergency-operation and compliance provisions",
      "officialIdentifier": "40 C.F.R. pt. 63, subpt. ZZZZ, § 63.6640(f)",
      "jurisdictionIds": [
        "us"
      ],
      "state": "Federal",
      "authority": "Federal",
      "instrumentType": "Regulation",
      "bindingForce": "Binding",
      "legalStatus": "Effective",
      "litigationStatus": "Unknown",
      "adoptionDate": null,
      "effectiveDate": null,
      "sunsetDate": null,
      "officialUrl": "https://www.ecfr.gov/current/title-40/chapter-I/subchapter-C/part-63/subpart-ZZZZ/section-63.6640",
      "relatedInstrumentIds": [],
      "reviewStatus": "Source-verified",
      "checked": "2026-10-28",
      "residentSummary": "The federal hazardous-air-pollutant rule limits when an engine may qualify as an emergency stationary engine. For covered emergency engines, the rule allows emergency operation without a time limit, while separately limiting maintenance/testing and certain non-emergency operation; the 50-hour provisions have significant conditions and are not a universal data-center operating allowance.",
      "applicabilityNote": "Applicability depends on engine type, size, construction/reconstruction date, HAP source classification, and other subpart requirements. This entry summarizes selected provisions only; it is not a facility air-permit determination.",
      "limitations": "eCFR text was current through 2026-10-26 when checked. EPA separately states that operation under certain 202(c) emergency orders is treated as an emergency situation for cited rules; later orders and equipment-specific rules must be checked.",
      "sourceIds": [
        "ecfr-63-6640",
        "epa"
      ]
    },
    {
      "id": "mn-water-preapp-2025",
      "title": "Preapplication evaluation of certain water appropriation projects",
      "officialIdentifier": "Minn. Stat. § 103G.265, subd. 5; 2025 Minn. Laws, 1st Spec. Sess., ch. 12, § 3",
      "jurisdictionIds": [
        "minnesota"
      ],
      "state": "Minnesota",
      "authority": "State",
      "instrumentType": "Statute",
      "bindingForce": "Binding",
      "legalStatus": "Effective",
      "litigationStatus": "Unknown",
      "adoptionDate": "2025-06-14",
      "effectiveDate": "2025-06-15",
      "sunsetDate": null,
      "officialUrl": "https://www.revisor.mn.gov/statutes/2025/cite/103G.265",
      "relatedInstrumentIds": [],
      "reviewStatus": "Source-verified",
      "checked": "2026-10-28",
      "residentSummary": "For a data center proposing more than 100 million gallons/year of consumptive use that needs a new individual permit or permit amendment, DNR may request specified project and water-use information and must respond in writing about potential water availability constraints. Communications and exchanged information under this subdivision are classified as nonpublic.",
      "applicabilityNote": "Data centers as defined by Minn. Stat. § 216B.02, subd. 11; proposed consumptive use must exceed 100,000,000 gallons per year and require a new individual permit or permit amendment.",
      "limitations": "The agency may request preapplication information; the law classifies those communications and records as nonpublic. The process does not replace environmental review, well approval, or appropriation-permit review.",
      "sourceIds": [
        "mn-water-preapp",
        "mn-laws-2025-c12"
      ]
    },
    {
      "id": "mn-water-permit-2025",
      "title": "Large water appropriation projects; permit conditions",
      "officialIdentifier": "Minn. Stat. § 103G.271, subd. 5b; 2025 Minn. Laws, 1st Spec. Sess., ch. 12, § 4",
      "jurisdictionIds": [
        "minnesota"
      ],
      "state": "Minnesota",
      "authority": "State",
      "instrumentType": "Statute",
      "bindingForce": "Binding",
      "legalStatus": "Effective",
      "litigationStatus": "Unknown",
      "adoptionDate": "2025-06-14",
      "effectiveDate": "2025-06-15",
      "sunsetDate": null,
      "officialUrl": "https://www.revisor.mn.gov/statutes/2025/cite/103G.271",
      "relatedInstrumentIds": [],
      "reviewStatus": "Source-verified",
      "checked": "2026-10-28",
      "residentSummary": "For covered data-center permits exceeding 100 million gallons/year of new or additional consumptive use, DNR must ensure public health, safety, and welfare; reasonably consider conservation and watershed-health measures; and address water-use conflicts. DNR must require an aquifer test when it finds one necessary for public-health protection.",
      "applicabilityNote": "New or modified permits for a data center with proposed new/additional consumptive use over 100,000,000 gallons/year, or an existing permit where more than that amount will be supplied to a data center.",
      "limitations": "The text addresses consumptive use, not a general cap on all withdrawals; permit-specific terms and the referenced Minnesota Rules water-conflict process require separate review.",
      "sourceIds": [
        "mn-water-permit",
        "mn-laws-2025-c12"
      ]
    },
    {
      "id": "mn-large-customer-2025",
      "title": "Service to very large customers",
      "officialIdentifier": "Minn. Stat. § 216B.1622; 2025 Minn. Laws, 1st Spec. Sess., ch. 12, § 9",
      "jurisdictionIds": [
        "minnesota"
      ],
      "state": "Minnesota",
      "authority": "State",
      "instrumentType": "Statute",
      "bindingForce": "Binding",
      "legalStatus": "Effective",
      "litigationStatus": "Unknown",
      "adoptionDate": "2025-06-14",
      "effectiveDate": "2025-06-15",
      "sunsetDate": null,
      "officialUrl": "https://www.revisor.mn.gov/statutes/2025/cite/216B.1622",
      "relatedInstrumentIds": [],
      "reviewStatus": "Source-verified",
      "checked": "2026-10-28",
      "residentSummary": "Minnesota requires the PUC to define a very-large-customer class or subclass for each electric public utility by December 15, 2026. In reviewing a utility tariff or service agreement, the Commission must consider cost assignment, clean-energy benchmarks, protection against stranded costs for other customers, and other public-interest outcomes.",
      "applicabilityNote": "Public utilities and customers that meet the Commission-defined very-large-customer class. The statute does not itself specify a MW threshold for the class.",
      "limitations": "The statutory deadline is December 15, 2026; as checked October 28, 2026, the implementation deadline had not yet passed. This statute does not itself establish a finished tariff or identify each utility customer covered. Existing/renewed/extended agreements and customers served before 2020 are excluded under subd. 3.",
      "sourceIds": [
        "mn-large-customer",
        "mn-laws-2025-c12"
      ]
    },
    {
      "id": "mn-large-fee-2025",
      "title": "Qualified large-scale data center fee",
      "officialIdentifier": "Minn. Stat. § 216B.72; 2025 Minn. Laws, 1st Spec. Sess., ch. 12, § 16",
      "jurisdictionIds": [
        "minnesota"
      ],
      "state": "Minnesota",
      "authority": "State",
      "instrumentType": "Statute",
      "bindingForce": "Binding",
      "legalStatus": "Effective",
      "litigationStatus": "Unknown",
      "adoptionDate": "2025-06-14",
      "effectiveDate": "2025-06-15",
      "sunsetDate": null,
      "officialUrl": "https://www.revisor.mn.gov/statutes/2025/cite/216B.72",
      "relatedInstrumentIds": [],
      "reviewStatus": "Source-verified",
      "checked": "2026-10-28",
      "residentSummary": "Commerce must collect an annual fee based on the utility-arranged peak-demand forecast: $2 million for 100–250 MW; $3 million above 250 and below 500 MW; $4 million for 500 and below 750 MW; and $5 million at 750 MW or greater. Fee data are classified as nonpublic.",
      "applicabilityNote": "Qualified large-scale data centers under the statutory definition, with fee tier based on MW of peak demand the utility arranges to serve.",
      "limitations": "The fee is not based on actual energy consumption (MWh). The statute delegates schedule details to the commissioner; do not infer incidence or local/community allocation from the fee alone.",
      "sourceIds": [
        "mn-fee",
        "mn-laws-2025-c12"
      ]
    },
    {
      "id": "mn-tax-exemption-2025",
      "title": "Qualified data-center sales and use tax exemption",
      "officialIdentifier": "Minn. Stat. § 297A.68, subd. 42; 2025 Minn. Laws, 1st Spec. Sess., ch. 12, § 17 and ch. 13, art. 3, § 4",
      "jurisdictionIds": [
        "minnesota"
      ],
      "state": "Minnesota",
      "authority": "State",
      "instrumentType": "Statute",
      "bindingForce": "Binding",
      "legalStatus": "Effective",
      "litigationStatus": "Unknown",
      "adoptionDate": "2025-06-14",
      "effectiveDate": "2025-07-01",
      "sunsetDate": null,
      "officialUrl": "https://www.revisor.mn.gov/statutes/2025/cite/297A.68",
      "relatedInstrumentIds": [],
      "reviewStatus": "Source-verified",
      "checked": "2026-10-28",
      "residentSummary": "Minnesota exempts qualifying enterprise IT equipment and software purchases for certified data centers; qualifying large-scale centers need at least 25,000 square feet and $250 million in aggregate qualifying investment over 60 months. Large-scale centers must meet prevailing-wage and recognized sustainability/green-building requirements or may face tax recapture.",
      "applicabilityNote": "Facilities meeting the separate statutory qualification tiers and certified by DEED; large-scale tier includes the square-footage and investment threshold.",
      "limitations": "The large-scale exemption is available for certification before July 1, 2042 and qualifying purchases within 35 years of the first qualifying purchase. Electricity is not included for purchases after June 30, 2025; legacy and refurbished eligibility criteria differ.",
      "sourceIds": [
        "mn-tax-exemption",
        "mn-laws-2025-c12"
      ]
    },
    {
      "id": "pa-tax-exemption-2021",
      "title": "Computer Data Center Equipment Incentive Program: sales and use tax exemption",
      "officialIdentifier": "61 P.S. § 2931-D; 2024 Act 56, § 30(12)",
      "jurisdictionIds": [
        "pennsylvania"
      ],
      "state": "Pennsylvania",
      "authority": "State",
      "instrumentType": "Statute",
      "bindingForce": "Binding",
      "legalStatus": "Effective",
      "litigationStatus": "Unknown",
      "adoptionDate": "2021-06-30",
      "effectiveDate": "2022-01-01",
      "sunsetDate": null,
      "officialUrl": "https://www.legis.state.pa.us/WU01/LI/LI/US/HTM/1971/0/0002.029D000.031.000..HTM",
      "relatedInstrumentIds": [],
      "reviewStatus": "Source-verified",
      "checked": "2026-10-28",
      "residentSummary": "The Commonwealth exempts covered equipment for installation in a certified computer data center, subject to statutory exclusions. The owner’s qualification period can last through the 25th full calendar year after the application year; a qualified tenant’s period ends at the earlier of its agreement term or the 10th full calendar year after agreement.",
      "applicabilityNote": "Owner/operator or qualified tenant of a computer data center certified under the statutory program. Certification standards are in related sections and must be checked for an applicant-specific determination.",
      "limitations": "Excludes specified internal-use telecom centers, equipment for electricity generation/resale or supplying more than 5% of facility electricity outside the center, proof-of-work crypto mining, and laptops/handheld devices/vehicles. 2024 Act 56 applies the crypto-mining exclusion to taxable years beginning after Dec. 31, 2025.",
      "sourceIds": [
        "pa-data-center-tax"
      ]
    },
    {
      "id": "federal-stationary-ci-2026",
      "title": "Stationary compression-ignition engine compliance requirements",
      "officialIdentifier": "40 C.F.R. § 60.4211",
      "jurisdictionIds": [
        "us"
      ],
      "state": "Federal",
      "authority": "Federal",
      "instrumentType": "Regulation",
      "bindingForce": "Binding",
      "legalStatus": "Effective",
      "litigationStatus": "Unknown",
      "adoptionDate": null,
      "effectiveDate": null,
      "sunsetDate": null,
      "officialUrl": "https://www.ecfr.gov/current/title-40/chapter-I/subchapter-C/part-60/subpart-IIII/section-60.4211",
      "relatedInstrumentIds": [],
      "reviewStatus": "Source-verified",
      "checked": "2026-10-28",
      "residentSummary": "For covered stationary compression-ignition engines, owners/operators must follow applicable engine standards, installation/maintenance instructions, testing and monitoring rules. Emergency engines have a separate operating category with conditional maintenance/testing and non-emergency hours; the 50-hour allowance is restricted and does not generally authorize peak shaving or demand response.",
      "applicabilityNote": "Stationary compression-ignition engines within 40 C.F.R. part 60, subpart IIII; applicability varies with engine model year, power, construction and source category.",
      "limitations": "Selected § 60.4211 requirements only; a facility-specific determination also requires other subpart provisions, permit terms, and equipment facts. Current eCFR is authoritative but unofficial; it displayed text through 2026-10-26.",
      "sourceIds": [
        "ecfr-ci-4211"
      ]
    },
    {
      "id": "utah-data-center-water-transparency-2026",
      "title": "Data Center Water Transparency Amendments",
      "officialIdentifier": "Utah HB 76 (2026), Utah Code § 73-5-8.3",
      "jurisdictionIds": [
        "utah"
      ],
      "state": "Utah",
      "authority": "State",
      "instrumentType": "Statute",
      "bindingForce": "Binding",
      "legalStatus": "Effective",
      "litigationStatus": "Unknown",
      "adoptionDate": null,
      "effectiveDate": "2026-05-06",
      "sunsetDate": null,
      "officialUrl": "https://le.utah.gov/~2026/bills/hbillenr/HB0076.pdf",
      "relatedInstrumentIds": [],
      "reviewStatus": "Source-verified",
      "checked": "2026-10-28",
      "residentSummary": "For covered new large data centers, Utah requires water-agency notice and projected-use reporting before construction, followed by annual withdrawal and conservation reporting. Most reported withdrawal data are made public, with statutory protections for specified proprietary information.",
      "applicabilityNote": "A covered large data center must meet statutory ownership/facility criteria, have at least 10,000 square feet, and withdraw at least 75 acre-feet annually. New large data centers begin operations on or after July 1, 2026; preconstruction and annual reporting duties use that applicability definition.",
      "limitations": "This is a reporting, notice, and disclosure law, not a general water-use cap or substitute for water-right, discharge, or wastewater permits. Certain submitted information may be protected and aggregated by county.",
      "sourceIds": [
        "utah-hb76-enrolled"
      ]
    },
    {
      "id": "virginia-data-center-gen-set-air-2026",
      "title": "Permits for data centers; emission limits for certain engine-generator sets",
      "officialIdentifier": "Va. Code § 10.1-1322.6; 2026 Acts ch. 397 (HB 507)",
      "jurisdictionIds": [
        "virginia"
      ],
      "state": "Virginia",
      "authority": "State",
      "instrumentType": "Statute",
      "bindingForce": "Binding",
      "legalStatus": "Effective",
      "litigationStatus": "Unknown",
      "adoptionDate": "2026-04-08",
      "effectiveDate": "2026-07-01",
      "sunsetDate": null,
      "officialUrl": "https://law.lis.virginia.gov/vacode/title10.1/chapter13/section10.1-1322.6/",
      "relatedInstrumentIds": [],
      "reviewStatus": "Source-verified",
      "checked": "2026-10-28",
      "residentSummary": "For covered data-center air-permit applications filed on or after July 1, 2026, DEQ cannot issue the permit unless the limit for each engine-generator is no higher than emissions from a Tier 4-equivalent set.",
      "applicabilityNote": "Applies to an air permit under the chapter, including general-permit coverage, for a data-center application submitted on or after July 1, 2026. Tier 4 equivalent includes equivalent NOx, carbon-monoxide, and particulate controls.",
      "limitations": "This permit gate does not automatically require replacement of existing equipment and preserves stricter permit controls and other federal/state standards. Verify facility and application facts for any site-specific conclusion.",
      "sourceIds": [
        "virginia-gen-set-air-code",
        "virginia-hb507-history"
      ]
    },
    {
      "id": "ohio-power-schedule-dct-2026",
      "title": "Ohio Power Company Schedule DCT (Data Center Tariff)",
      "officialIdentifier": "Ohio Power P.U.C.O. No. 22, Schedule DCT, sheets 223-2 to 223-5",
      "jurisdictionIds": [
        "ohio-power"
      ],
      "state": "Ohio",
      "authority": "Utility",
      "instrumentType": "Tariff",
      "bindingForce": "Binding",
      "legalStatus": "Effective",
      "litigationStatus": "Challenged",
      "adoptionDate": null,
      "effectiveDate": "2026-08-28",
      "sunsetDate": null,
      "officialUrl": "https://www.aepohio.com/lib/docs/ratesandtariffs/Ohio/November_2026_Ohio_Power_Tariff_Book.pdf",
      "relatedInstrumentIds": [],
      "reviewStatus": "Source-verified",
      "checked": "2026-10-28",
      "residentSummary": "Ohio Power’s data-center tariff applies to qualifying loads above 25 MW and sets minimum monthly billing-demand floors. New loads face an 85% ramp-capacity floor and a later tiered minimum, which can require payment for substantial contracted capacity even when actual use is lower.",
      "applicabilityNote": "Applies only to Ohio Power Company service. Eligibility is generally monthly maximum demand over 25,000 kW at a single location or aggregated customer contract capacity over 25,000 kW in the service territory, subject to detailed definitions and load categories.",
      "limitations": "Tariff sheets 223-2–223-5 were issued/effective Aug. 28, 2026 and filed under PUCO cases 25-392-EL-AIR and 26-113-EL-ATA. Existing and new loads have distinct formulas and transition terms. The underlying tariff is challenged in Ohio Supreme Court No. 2025-1458; this batch did not identify a final disposition or verify a stay. Do not generalize to other Ohio utilities.",
      "sourceIds": [
        "ohio-power-schedule-dct-current",
        "ohio-puco-2026-sso"
      ]
    },
    {
      "id": "oregon-large-energy-use-facilities-hb3546-2025",
      "title": "Large Energy Use Facilities",
      "officialIdentifier": "Oregon 2025 HB 3546, 2025 Or. Laws ch. 323",
      "jurisdictionIds": [
        "oregon"
      ],
      "state": "Oregon",
      "authority": "State",
      "instrumentType": "Statute",
      "bindingForce": "Binding",
      "legalStatus": "Effective",
      "litigationStatus": "Unknown",
      "adoptionDate": "2025-06-16",
      "effectiveDate": "2025-06-16",
      "sunsetDate": null,
      "officialUrl": "https://olis.oregonlegislature.gov/liz/2025R1/Downloads/MeasureDocument/HB3546",
      "relatedInstrumentIds": [],
      "reviewStatus": "Source-verified",
      "checked": "2026-10-28",
      "residentSummary": "Oregon requires a separate electric-service class and tariff for qualifying very large computing facilities. Utilities must use long-term service contracts, at least ten years, with a commission-set minimum payment tied to projected electricity use.",
      "applicabilityNote": "A covered facility uses or can use at least 20 MW and primarily provides NAICS 518210 services, under statutory definitions aggregating facilities at single/contiguous/adjacent sites under common control.",
      "limitations": "The statute directs commission tariff design and contract terms but does not provide every utility's actual approved tariff terms. PGE implementation Order 26-154 and associated tariff action are under further procedural review; current Schedule 96 terms remain a separate research task.",
      "sourceIds": [
        "oregon-hb3546-enrolled",
        "oregon-puc-um2377-docket"
      ]
    },
    {
      "id": "loudoun-zoning-noise-2023",
      "title": "Loudoun County Zoning Ordinance — data-center noise study and sound standards",
      "officialIdentifier": "Loudoun County Zoning Ordinance §§ 4.06.02, 7.05.03",
      "jurisdictionIds": [
        "loudoun-county"
      ],
      "state": "Virginia",
      "authority": "Local",
      "instrumentType": "Ordinance",
      "bindingForce": "Binding",
      "legalStatus": "Effective",
      "litigationStatus": "Unknown",
      "adoptionDate": "2023-12-13",
      "effectiveDate": "2023-12-13",
      "sunsetDate": null,
      "officialUrl": "https://sheriff.loudoun.gov/DocumentCenter/View/178347/Ch-7-Dev-Standards-Compare",
      "relatedInstrumentIds": [],
      "reviewStatus": "Source-verified; current clean codification needs review",
      "checked": "2026-10-28",
      "residentSummary": "The available County-hosted ordinance text sets A-weighted sound standards and measurement procedures and requires noise studies for covered data-center uses. Certain generator sounds are exempt from the table limits, while separate data-center rules require acoustic barriers for some mechanical equipment near residential areas.",
      "applicabilityNote": "County zoning jurisdiction only; the seven incorporated towns use their own ordinances. Certain Route 28 Tax District properties remain under the 1972 ordinance and grandfathered applications may use prior rules. The ordinance has subsequent amendments; the cited available text is a County-hosted comparison copy.",
      "limitations": "Chapter 7 County-hosted comparison PDF is accessible; current clean Chapter 4 and Chapter 7 PDF endpoints returned 404. Confirm live code and amendment history before relying on exact application. § 7.05.03 table limits have exceptions, including emergency/utility generator operation and testing. Mitigation text references 55 dBA even where table thresholds differ; interpretation needs review. This record requires independent legal review before public reliance. County-hosted comparison text is not a clean, current codification; treat specific claims as provisional pending independent review.",
      "sourceIds": [
        "loudoun-chapter7-official-comparison",
        "loudoun-chapter4-current-url",
        "loudoun-zoning-scope"
      ]
    },
    {
      "id": "ca-ab1577-2026",
      "title": "AB 1577, Data centers: energy and local-permit information",
      "officialIdentifier": "Cal. AB 1577, ch. 434 (2026)",
      "jurisdictionIds": [
        "california"
      ],
      "state": "California",
      "authority": "State",
      "instrumentType": "Statute",
      "bindingForce": "Binding",
      "legalStatus": "Enacted; operative reporting dates follow commission process",
      "litigationStatus": "Unknown",
      "adoptionDate": "2026-09-21",
      "effectiveDate": "2027-01-01",
      "sunsetDate": null,
      "officialUrl": "https://leginfo.legislature.ca.gov/faces/billNavClient.xhtml?bill_id=202520260AB1577",
      "relatedInstrumentIds": [],
      "reviewStatus": "Source-verified",
      "checked": "2026-10-28",
      "residentSummary": "Owners/operators of data centers with at least 10 MW electrical capacity must report facility, energy, onsite generation/fuel, and efficiency data to the Energy Commission after energization and annually; local applicants for discretionary permits must disclose expected energy, onsite generation, and boundary sound levels.",
      "applicabilityNote": "The measure creates specified reporting and permit-disclosure duties; covered facilities and disclosure details are governed by the act.",
      "limitations": "Exempts specified publicly funded research, public safety, publicly funded national-security, publicly owned, and utility facilities. Commission publishes anonymized aggregated information; no customer-level energy-use disclosure. Local disclosure duty is triggered by application for discretionary permit, entitlement, or land-use authorization. Confirm Energy Commission reporting process and its dates before assessing facility compliance.",
      "sourceIds": [
        "ab1577-ca"
      ]
    },
    {
      "id": "ca-ab2383-2026",
      "title": "AB 2383, Data centers: electric service tariffs",
      "officialIdentifier": "Cal. AB 2383, ch. 435 (2026)",
      "jurisdictionIds": [
        "california"
      ],
      "state": "California",
      "authority": "State",
      "instrumentType": "Statute",
      "bindingForce": "Binding",
      "legalStatus": "Enacted; CPUC tariffs and CCA/ESP tariffs remain implementation dependent",
      "litigationStatus": "Unknown",
      "adoptionDate": "2026-09-21",
      "effectiveDate": "2027-01-01",
      "sunsetDate": null,
      "officialUrl": "https://leginfo.legislature.ca.gov/faces/billNavClient.xhtml?bill_id=202520260AB2383",
      "relatedInstrumentIds": [],
      "reviewStatus": "Source-verified",
      "checked": "2026-10-28",
      "residentSummary": "Requires CPUC-approved T&D and generation tariffs for covered data-center customers, allocates class costs, and requires minimum 10-year generation payment commitments with collateral, early-exit/non-interconnection fees, and projected-load minimums for covered customers.",
      "applicabilityNote": "Applicable electric corporations, and specified CCAs and ESPs under the act.",
      "limitations": "Statutory duties are verified; exact filed and approved tariff sheets and customer-specific application remain implementation questions. Public text excludes certain facilities; electrical cooperatives are excluded from electrical-corporation definition.",
      "sourceIds": [
        "ab2383-ca"
      ]
    },
    {
      "id": "ca-ab2469-2026",
      "title": "AB 2469, Data centers: water-supply assessment",
      "officialIdentifier": "Cal. AB 2469, ch. 436 (2026)",
      "jurisdictionIds": [
        "california"
      ],
      "state": "California",
      "authority": "State",
      "instrumentType": "Statute",
      "bindingForce": "Binding",
      "legalStatus": "Enacted; water-scarcity plan applies beginning 2028",
      "litigationStatus": "Unknown",
      "adoptionDate": "2026-09-21",
      "effectiveDate": "2027-01-01",
      "sunsetDate": null,
      "officialUrl": "https://leginfo.legislature.ca.gov/faces/billNavClient.xhtml?bill_id=202520260AB2469",
      "relatedInstrumentIds": [],
      "reviewStatus": "Source-verified",
      "checked": "2026-10-28",
      "residentSummary": "Cities and counties cannot approve a discretionary or ministerial permit or entitlement for covered construction or an expansion increasing peak water use unless required water-supply/use, efficiency, and workforce information is supplied; from 2028, a drought-stage water-scarcity plan is required, and the applicant pays required water infrastructure costs.",
      "applicabilityNote": "City and county permit/entitlement applications for a new data center or expansion that increases peak water use.",
      "limitations": "Applies to all cities including charter cities. A compliant applicant is not automatically entitled to approval. Plan requirement begins January 1, 2028; infrastructure cost paragraph is severable.",
      "sourceIds": [
        "ab2469-ca"
      ]
    },
    {
      "id": "ca-ab2619-2026",
      "title": "AB 2619, Data centers: water-use disclosure",
      "officialIdentifier": "Cal. AB 2619, ch. 437 (2026)",
      "jurisdictionIds": [
        "california"
      ],
      "state": "California",
      "authority": "State",
      "instrumentType": "Statute",
      "bindingForce": "Binding",
      "legalStatus": "Enacted; detailed thresholds and code sections need final pinpoint check",
      "litigationStatus": "Unknown",
      "adoptionDate": "2026-09-21",
      "effectiveDate": "2027-01-01",
      "sunsetDate": null,
      "officialUrl": "https://leginfo.legislature.ca.gov/faces/billNavClient.xhtml?bill_id=202520260AB2619",
      "relatedInstrumentIds": [],
      "reviewStatus": "Needs clause-level review",
      "checked": "2026-10-28",
      "residentSummary": "California data centers must provide water suppliers and local licensing authorities projected water use and source before initial business license/permit applications and report actual annual total, direct, and indirect water use at renewal; water suppliers must include data-center demand in shortage planning.",
      "applicabilityNote": "Data centers covered by the act’s statutory definitions and licensing framework.",
      "limitations": "Statutory facility definitions use three power tiers: Type I >25 MW; Type II 2–25 MW; Type III <2 MW. Exact reporting thresholds and implementation details vary by code section. This is disclosure and planning, not a universal water cap. Full chaptered text has now been reviewed; remaining work is to map Type I/II/III definitions to each reporting and water-planning obligation and confirm effective-date clauses.",
      "sourceIds": [
        "ab2619-ca"
      ]
    },
    {
      "id": "ca-sb886-2026",
      "title": "SB 886, Data centers: electrical service and cost allocation",
      "officialIdentifier": "Cal. SB 886, ch. 438 (2026)",
      "jurisdictionIds": [
        "california"
      ],
      "state": "California",
      "authority": "State",
      "instrumentType": "Statute",
      "bindingForce": "Binding",
      "legalStatus": "Enacted; CPUC implementation due by 2028; covered agreement rule begins 2027",
      "litigationStatus": "Unknown",
      "adoptionDate": "2026-09-21",
      "effectiveDate": "2027-01-01",
      "sunsetDate": null,
      "officialUrl": "https://leginfo.legislature.ca.gov/faces/billNavClient.xhtml?bill_id=202520260SB886",
      "relatedInstrumentIds": [],
      "reviewStatus": "Source-verified",
      "checked": "2026-10-28",
      "residentSummary": "The CPUC must establish or update rules by January 1, 2028 for covered data-center transmission interconnections and retail service, including customer responsibility for transmission upgrades, a 10-year early termination/ramp-up fee, and safeguards against shifting costs to other ratepayers.",
      "applicabilityNote": "Specified large data-center customers seeking covered transmission-level service and other applications within the statute.",
      "limitations": "Statutory terms verified. Customer-specific tariff and implementation details remain for CPUC action; scope is transmission-level interconnection and participating-customer service as specified.",
      "sourceIds": [
        "sb886-ca"
      ]
    },
    {
      "id": "ca-sb887-2026",
      "title": "SB 887, Data centers: environmental review",
      "officialIdentifier": "Cal. SB 887, ch. 439 (2026)",
      "jurisdictionIds": [
        "california"
      ],
      "state": "California",
      "authority": "State",
      "instrumentType": "Statute",
      "bindingForce": "Binding",
      "legalStatus": "Enacted; CEQA applicability rule plus conditional streamlining pathway",
      "litigationStatus": "Unknown",
      "adoptionDate": "2026-09-21",
      "effectiveDate": "2027-01-01",
      "sunsetDate": null,
      "officialUrl": "https://leginfo.legislature.ca.gov/faces/billNavClient.xhtml?bill_id=202520260SB887",
      "relatedInstrumentIds": [],
      "reviewStatus": "Source-verified",
      "checked": "2026-10-28",
      "residentSummary": "CEQA applies to entitlements for covered data-center development and operation, and categorical exemptions are unavailable for covered projects (subject to statutory facility exclusions). The Governor may certify a qualifying project for the environmental-leadership pathway only after lead-agency certification of demanding conditions for grid cost responsibility, zero-carbon energy/storage, water-efficient cooling, community benefits, and related requirements. That pathway is conditional; the act does not automatically require an EIR for every project.",
      "applicabilityNote": "CEQA entitlement rule for a data center as defined in Pub. Resources Code § 21061.6; the categorical-exemption restriction applies to a project proposed to be carried out or approved by a public agency in furtherance of data-center development/operation, subject to § 21084(f)(2) exclusions. Separate leadership-project provisions require lead-agency certification and gubernatorial certification.",
      "limitations": "The law removes categorical exemptions for covered data-center projects; it does not direct an EIR in every case or eliminate negative declarations/other CEQA determinations based on the record. Environmental-leadership certification is a conditional option with project-specific statutory criteria and is not an exemption from CEQA. Existing leadership-program statutory sunset is January 1, 2032. Official California Legislature site confirmed chapter status but returned 403 for full text in this research environment; chaptered text was reviewed on an accessible mirror and must be rechecked against the official chaptered act when obtainable.",
      "sourceIds": [
        "sb887-ca"
      ]
    },
    {
      "id": "ca-sb1168-2026",
      "title": "SB 1168, Data centers: electrical service rate assessment",
      "officialIdentifier": "Cal. SB 1168, ch. 440 (2026)",
      "jurisdictionIds": [
        "california"
      ],
      "state": "California",
      "authority": "State",
      "instrumentType": "Statute",
      "bindingForce": "Binding",
      "legalStatus": "Enacted; directs CPUC assessment",
      "litigationStatus": "Unknown",
      "adoptionDate": "2026-09-21",
      "effectiveDate": "2027-01-01",
      "sunsetDate": null,
      "officialUrl": "https://leginfo.legislature.ca.gov/faces/billNavClient.xhtml?bill_id=202520260SB1168",
      "relatedInstrumentIds": [],
      "reviewStatus": "Source-verified",
      "checked": "2026-10-28",
      "residentSummary": "Directs the CPUC to assess rate opportunities intended to ensure large data-center customers bear a reasonable share of transmission/distribution and procurement costs and to alleviate residential cost pressure.",
      "applicabilityNote": "The commission’s assessment of specified data-center electricity cost allocation.",
      "limitations": "Directs an assessment of possible cost-allocation approaches; it does not itself adopt a tariff, set a large-customer rate, or guarantee reduced residential bills.",
      "sourceIds": [
        "sb1168-ca"
      ]
    },
    {
      "id": "fl-large-data-center-water-2026",
      "title": "Large-scale data centers: water allocation safeguards and conservation plans",
      "officialIdentifier": "Fla. Stat. § 373.262; 2026 ch. 2026-65, § 5",
      "jurisdictionIds": [
        "florida"
      ],
      "state": "Florida",
      "authority": "State",
      "instrumentType": "Statute",
      "bindingForce": "Binding",
      "legalStatus": "Effective",
      "litigationStatus": "Unknown",
      "adoptionDate": "2026-05-22",
      "effectiveDate": "2026-07-01",
      "sunsetDate": null,
      "officialUrl": "https://www.flsenate.gov/Laws/Statutes/2026/373.262",
      "relatedInstrumentIds": [],
      "reviewStatus": "Source-verified",
      "checked": "2026-10-28",
      "residentSummary": "Water districts or DEP may not grant covered allocations when the statutory harm or land-use condition applies; reclaimed water and conservation planning are required under specified conditions.",
      "applicabilityNote": "Applications for water allocations to large-scale data centers under Florida Stat. § 373.262.",
      "limitations": "The reclaimed-water condition has feasibility, availability, capacity, quality, access, and permit-consistency prerequisites. The hearing and conservation-plan requirements apply at the statutory average-allocation threshold.",
      "sourceIds": [
        "fl-statute-373-262-2026"
      ]
    },
    {
      "id": "pa-data-center-executive-order-2026-05",
      "title": "Executive Order 2026-05: responsible data-center development",
      "officialIdentifier": "Executive Order 2026-05; 4 Pa. Code ch. 7, subch. RRR",
      "jurisdictionIds": [
        "pennsylvania"
      ],
      "state": "Pennsylvania",
      "authority": "State",
      "instrumentType": "Executive order",
      "bindingForce": "Binding",
      "legalStatus": "Effective",
      "litigationStatus": "Unknown",
      "adoptionDate": "2026-08-18",
      "effectiveDate": "2026-08-18",
      "sunsetDate": null,
      "officialUrl": "https://www.pacodeandbulletin.gov/secure/pabulletin/data/vol56/56-36/1274.html",
      "relatedInstrumentIds": [],
      "reviewStatus": "Source-verified",
      "checked": "2026-10-28",
      "residentSummary": "Pennsylvania directs covered agencies to apply public permitting, transparency, and consumer-protection procedures. Projects over 25 MW that commit to GRID requirements can use a consent-agreement review path; projects without that agreement must clear specified local and water approvals before DEP starts reviewing permits. The order also requires no NDAs for Governor-controlled agencies, a public DEP project map, and annual energy/water reporting.",
      "applicabilityNote": "Applies to Governor-controlled agencies and specified applications. The GRID consent-agreement/review pathway applies to projects with peak demand over 25 MW that commit to GRID requirements. Local governments and independent agencies are not directly controlled by this order.",
      "limitations": "The order controls agencies under the Governor, not local governments or independent agencies. Some provisions direct advocacy for future PUC rules or DEP recommendations rather than establish final utility tariffs or new environmental standards. It creates no private right and is limited by existing law.",
      "sourceIds": [
        "pa-eo-2026-05-bulletin"
      ]
    },
    {
      "id": "sd-large-load-and-water-reporting-sb135-2026",
      "title": "SB 135: large-load customer terms and data-center water reporting",
      "officialIdentifier": "2026 S.D. SB 135",
      "jurisdictionIds": [
        "south-dakota"
      ],
      "state": "South Dakota",
      "authority": "State",
      "instrumentType": "Statute",
      "bindingForce": "Binding",
      "legalStatus": "Enacted; effective in 2026",
      "litigationStatus": "Unknown",
      "adoptionDate": "2026-03-24",
      "effectiveDate": "2026-07-01",
      "sunsetDate": null,
      "officialUrl": "https://mylrc.sdlegislature.gov/api/Documents/306610.html",
      "relatedInstrumentIds": [],
      "reviewStatus": "Source-verified",
      "checked": "2026-10-28",
      "residentSummary": "For data centers with peak demand of at least 10 MW, providers must use separate service terms and recover fairly attributable costs including departure or material load reduction. Operators notify local water providers before operation, obtain written compatibility determinations, comply with Board allocation limits prioritizing residential and essential services, and submit public semiannual water reports.",
      "applicabilityNote": "Large-load customer and data-center water provisions under SB 135; specific requirements apply to covered providers, customers, and water authorities.",
      "limitations": "The enrolled act text sets the core duties. Implementation details are prescribed by the Board of Water Management and electricity providers; the water allocation limit is separately set by Board order after residential and essential public-service allocation.",
      "sourceIds": [
        "sd-sb135-enrolled-2026"
      ]
    },
    {
      "id": "ne-large-load-customer-act-lb1010-2026",
      "title": "LB 1010: Large Load Customer Regulation Act and data-center provisions",
      "officialIdentifier": "2026 Neb. LB 1010; Large Load Customer Regulation Act",
      "jurisdictionIds": [
        "nebraska"
      ],
      "state": "Nebraska",
      "authority": "State",
      "instrumentType": "Statute",
      "bindingForce": "Binding",
      "legalStatus": "Enacted; clause-level review pending",
      "litigationStatus": "Unknown",
      "adoptionDate": "2026-04-14",
      "effectiveDate": null,
      "sunsetDate": null,
      "officialUrl": "https://www.nebraskalegislature.gov/FloorDocs/109/PDF/Slip/LB1010.pdf",
      "relatedInstrumentIds": [],
      "reviewStatus": "Needs clause-level review",
      "checked": "2026-10-28",
      "residentSummary": "Establishes additional requirements for public-power suppliers serving large load customers, including data-center definitions, interconnection disclosures, study fees, and financial commitments.",
      "applicabilityNote": "Large load customers, including defined data centers, and Nebraska public-power suppliers within the statute.",
      "limitations": "A single-site customer load above 20 MW triggers Large Load Customer Regulation Act provisions; separate data-center reporting provisions use their own definitions and thresholds. Section-specific effective dates and supplier type govern. The controlling chaptered text was not fully checked for every threshold and transition clause in this batch; treat this as a research record pending focused verification.",
      "sourceIds": [
        "ne-lb1010-slip-law"
      ]
    },
    {
      "id": "nv-data-center-tax-abatement-eo-2026-005",
      "title": "Executive Order 2026-005: data-center tax abatements and community commitments",
      "officialIdentifier": "Nevada Executive Order 2026-005",
      "jurisdictionIds": [
        "nevada"
      ],
      "state": "Nevada",
      "authority": "State",
      "instrumentType": "Executive order",
      "bindingForce": "Binding",
      "legalStatus": "Effective",
      "litigationStatus": "Unknown",
      "adoptionDate": "2026-09-17",
      "effectiveDate": "2026-09-17",
      "sunsetDate": null,
      "officialUrl": "https://www.gov.nv.gov/executive-actions/executive-orders/2026-executive-orders/eo-2026-005",
      "relatedInstrumentIds": [],
      "reviewStatus": "Source-verified",
      "checked": "2026-10-28",
      "residentSummary": "Requires specified state tax-abatement applicants to make a community-support commitment as part of the application process.",
      "applicabilityNote": "Only pending applications for state sales/use-tax partial abatements not yet acted upon by the Economic Development Board, as specified in the order.",
      "limitations": "Does not change approved abatements, utility tariffs, PUC authority, or local land-use law; conditions are limited to the tax-abatement program and statutory recapture limits.",
      "sourceIds": [
        "nv-eo-2026-005"
      ]
    },
    {
      "id": "ok-hb2992-2026",
      "title": "Oklahoma Data Center Customer Ratepayer Protection Act of 2026",
      "officialIdentifier": "2026 Okla. H.B. 2992; new 17 O.S. §§ 900–906",
      "jurisdictionIds": [
        "oklahoma"
      ],
      "state": "Oklahoma",
      "authority": "State / electric supplier regulators",
      "instrumentType": "Statute",
      "bindingForce": "Binding",
      "legalStatus": "Effective; enrolled act states July 1, 2026 and separately contains an emergency clause; confirm codified effective treatment",
      "litigationStatus": "Unknown",
      "adoptionDate": "2026-05-11",
      "effectiveDate": "2026-07-01 (express date in § 8; § 9 emergency clause creates a timing issue to confirm)",
      "sunsetDate": null,
      "officialUrl": "https://www.oklegislature.gov/cf_pdf/2025-26%20ENR/hB/HB2992%20ENR.PDF",
      "relatedInstrumentIds": [],
      "reviewStatus": "Source-verified",
      "checked": "2026-10-28",
      "residentSummary": "For qualifying new data-center and other computing loads of at least 75 MW, Oklahoma requires supplier-specific service terms and cost protections intended to keep directly caused costs and stranded investment from shifting to other customers. Some land purchases outside industrial parks or municipalities also trigger notice to regulators, county commissioners, and abutting owners.",
      "applicabilityNote": "The large-load definition includes new data centers, cryptocurrency mining, and facilities primarily providing AI computing, at 75 MW or more per facility or in aggregate behind one interconnection after July 1, 2026. Rules apply across investor-owned, cooperative, municipal, and public-power suppliers. The adjacent-land notice applies to covered purchasers acquiring land outside an industrial development park or municipality.",
      "limitations": "No actual tariff or OCC implementing rule was reviewed. Enrolled § 8 says July 1, 2026, while § 9 declares an emergency and says the act takes effect after passage and approval; exact effective-date treatment should be reconciled to codification. A 10-year service term has a stated exception for certain tax-exempt-financed public-power agreements.",
      "sourceIds": [
        "ok-hb2992-enrolled-2026",
        "ok-hb2992-history-2026"
      ]
    },
    {
      "id": "ok-sb259-2026",
      "title": "Oklahoma groundwater-use amendments (SB 259)",
      "officialIdentifier": "2026 Okla. S.B. 259; 82 O.S. §§ 1020.12, 1020.15, 1020.19B",
      "jurisdictionIds": [
        "oklahoma"
      ],
      "state": "Oklahoma",
      "authority": "State",
      "instrumentType": "Statute",
      "bindingForce": "Binding",
      "legalStatus": "Enacted; effective November 1, 2026",
      "litigationStatus": "Unknown",
      "adoptionDate": "2026-05-20",
      "effectiveDate": "2026-11-01",
      "sunsetDate": null,
      "officialUrl": "https://www.oklegislature.gov/cf_pdf/2025-26%20ENR/SB/SB259%20ENR.PDF",
      "relatedInstrumentIds": [],
      "reviewStatus": "Source-verified",
      "checked": "2026-10-28",
      "residentSummary": "Starting November 1, 2026, a data center seeking groundwater permits may not use groundwater-consuming evaporative or discharge cooling without recirculation; the permit applicant must show a closed-loop, dielectric-immersion, or comparably low-consumptive design as determined by the state water board.",
      "applicabilityNote": "This is a groundwater-use restriction tied to groundwater permits and applies to data-center cooling systems within the statutory text. It is not a ban on all data-center cooling or all water use.",
      "limitations": "Rules and board implementation were not reviewed. The act also changes generally applicable permitted-groundwater reporting, waste investigation, and enforcement; this dataset captures only the explicit data-center cooling rule.",
      "sourceIds": [
        "ok-sb259-enrolled-2026"
      ]
    },
    {
      "id": "nj-data-center-reporting-2026",
      "title": "New Jersey Data Center Water and Energy Reporting Act",
      "officialIdentifier": "P.L. 2026, c.75 (S3379/A4096)",
      "jurisdictionIds": [
        "new-jersey"
      ],
      "state": "New Jersey",
      "authority": "State",
      "instrumentType": "Statute",
      "bindingForce": "Binding",
      "legalStatus": "Effective; signed August 27, 2026",
      "litigationStatus": "Unknown",
      "adoptionDate": "2026-08-27",
      "effectiveDate": "2026-08-27",
      "sunsetDate": null,
      "officialUrl": "https://pub.njleg.state.nj.us/Bills/2026/S3500/3379_R2.HTM",
      "relatedInstrumentIds": [],
      "reviewStatus": "Enacted; chapter-text reconciliation needed",
      "checked": "2026-10-28",
      "residentSummary": "New Jersey data-center owners and operators must report energy and water use to the BPU every six months. The state must publish core operating, energy, water-source, and backup-power information; extra performance and sustainability metrics are required for centers receiving state incentives and have special confidentiality treatment.",
      "applicabilityNote": "Applies to data centers in New Jersey as defined in the act, excluding facilities primarily used for internal operations by licensed health-care providers if they do not provide commercial processing or colocation to unaffiliated entities. First reporting deadline is three months after effectiveness for facilities already operating at least one year, and six months for others.",
      "limitations": "Enactment as P.L. 2026, c.75 is confirmed by the Governor’s official signing announcement, but only the Senate second-reprint text—not the final chapter-law pamphlet—was available for clause-level review in this batch. Treat provision detail as provisional until the chapter text is compared. The statutory reporting program lasts three years from each facility’s first report; the BPU then decides whether to continue permanently. This is reporting and disclosure, not a water-use cap or energy limit.",
      "sourceIds": [
        "nj-s3379-enacted-status",
        "nj-s3379-2r-text"
      ]
    },
    {
      "id": "nj-data-center-fair-share-2026",
      "title": "Data Center Fair Share Act: BPU electric-service standards and tariffs",
      "officialIdentifier": "P.L. 2026, c.32; N.J.S.A. 48:7-6.2 (A796/S731)",
      "jurisdictionIds": [
        "new-jersey"
      ],
      "state": "New Jersey",
      "authority": "State",
      "instrumentType": "Statute",
      "bindingForce": "Binding",
      "legalStatus": "Enacted and effective; BPU standards and utility tariffs pending implementation",
      "litigationStatus": "Not researched in this batch",
      "adoptionDate": "2026-07-07",
      "effectiveDate": "2026-07-07",
      "sunsetDate": null,
      "officialUrl": "https://pub.njleg.state.nj.us/Bills/2026/PL26/32_.HTM",
      "relatedInstrumentIds": [],
      "reviewStatus": "Source-verified",
      "checked": "2026-10-28",
      "residentSummary": "New Jersey law directs the BPU to set large-data-center electric-service standards and requires utilities to create approved tariffs. The framework assigns attributable grid costs to covered customers, includes long-term financial protections, and requires demand-flexibility commitments. The exact threshold and tariffs depend on BPU and utility proceedings.",
      "applicabilityNote": "Applies to large data center customers served by electric public utilities in New Jersey. BPU must define qualifying characteristics and a minimum MW threshold for each utility; that threshold cannot exceed 50 MW and must aggregate peak monthly energy demand for facilities under common ownership/control, on the same or contiguous sites, or sharing substantial infrastructure. Utilities file tariffs within 180 days after BPU standards orders; tariffs apply after BPU approval. Pending service applications and already approved pre-effective-date service have specified transition/grandfathering treatment.",
      "limitations": "The statute is operative, but BPU standards and utility tariffs determine the specific thresholds and customer terms. Do not describe all statutory design criteria as immediately operative tariff conditions before implementation. The RFI docket is at an early stakeholder-input stage as of the research cutoff. Pre-effective-date approved service is exempt from selected requirements for approved MW only; expansions above the eventual threshold remain subject to tariff. Federal wholesale and transmission jurisdiction is expressly preserved.",
      "sourceIds": [
        "nj-c32-chapter-law",
        "nj-bpu-c32-rfi-2026"
      ]
    }
  ],
  "provisions": [
    {
      "id": "fairfax-noise-studies",
      "instrumentId": "fairfax-data-center-zoning-2024",
      "pillarTags": [
        "noise",
        "transparency"
      ],
      "mechanismTags": [
        "study/assessment",
        "monitoring/disclosure",
        "enforcement/remedy"
      ],
      "plainLanguageRule": "Submit a pre-site-plan noise study demonstrating compliance with County Code Chapter 108.1, and submit a post-construction noise study before issuance of a Nonresidential Use Permit; the Zoning Administrator must be satisfied.",
      "coveredEntities": "Data center applications subject to the county's zoning standards and applicable review route",
      "thresholdText": null,
      "exemptions": "Applicability is governed by use tables, approval route, and transition provisions.",
      "existingFacilityTreatment": "Certain applications accepted or approved by July 16, 2024 may proceed under prior provisions if listed conditions are met.",
      "enforcementAuthority": "Fairfax County Zoning Administrator; related noise ordinance enforcement authority not independently reviewed here",
      "enforcementTools": "Zoning review and permit sequencing; separate noise-code remedies not analyzed",
      "sourceIds": [
        "fairfax-text"
      ],
      "pinpoint": "ZO 112.1-2024-9 / 112.2-2024-8, § 4102.6.A(6), pp. 2–3; submission requirements, §§ 8101.2.E(12), 8101.3.D(8), pp. 3–4",
      "residentSummary": "Noise compliance must be studied before key approvals and checked again after construction.",
      "researcherNote": "The amendment cross-references Chapter 108.1 but does not itself state the decibel limits, measurement point, time period, or tonal adjustment."
    },
    {
      "id": "fairfax-siting-and-screening",
      "instrumentId": "fairfax-data-center-zoning-2024",
      "pillarTags": [
        "land",
        "noise"
      ],
      "mechanismTags": [
        "siting restriction",
        "discretionary approval"
      ],
      "plainLanguageRule": "Covered buildings generally must be at least 200 feet from residential-zoning lot lines or property developed for residential use; ground equipment generally must be at least 300 feet away or shielded by the main building. Cooling and operating equipment must generally be enclosed, with a mechanical-feasibility exception and screening alternative. A special exception may authorize lesser residential distances.",
      "coveredEntities": "Data centers governed by Fairfax County Zoning Ordinance § 4102.6.A",
      "thresholdText": null,
      "exemptions": "Mechanical-feasibility determination for enclosure; special exception for lesser distances; solar panels excluded from screening standard.",
      "existingFacilityTreatment": "Transition rules in Appendix 1, § 2.B preserve certain earlier applications and approvals.",
      "enforcementAuthority": "Fairfax County zoning officials",
      "enforcementTools": "Site-plan, special-exception, and permit review",
      "sourceIds": [
        "fairfax-text"
      ],
      "pinpoint": "§ 4102.6.A(1), (4), pp. 2–3; Appendix 1, § 2.B, p. 4",
      "residentSummary": "The ordinance uses distance, building placement, enclosure, and screening to reduce proximity and noise impacts.",
      "researcherNote": "Distance is measured from specified residential lot lines or developed residential properties. The Metro station distance rule is a distinct additional requirement."
    },
    {
      "id": "virginia-heuf-sound-assessment",
      "instrumentId": "virginia-heuf-site-assessment-2026",
      "pillarTags": [
        "noise",
        "transparency"
      ],
      "mechanismTags": [
        "study/assessment",
        "participation"
      ],
      "plainLanguageRule": "Before approval of a covered application for a new HEUF, the locality must require an applicant site assessment of the facility sound profile on residential units and schools within 500 feet of the facility boundary, to the extent practicable and within the referenced application timeline.",
      "coveredEntities": "Applicant for a new high-energy-use facility in a rezoning, special-exception, or special-use-permit process",
      "thresholdText": "At least 100 MW reasonably anticipated from a retail electric utility at filing",
      "exemptions": "Specified existing or approved facility expansions/modifications are excluded when added power does not reach at least 100 MW.",
      "existingFacilityTreatment": "Existing approval exception in subsection F; existing local zoning authority preserved.",
      "enforcementAuthority": "Locality reviewing the covered application",
      "enforcementTools": "Assessment required before approval; locality considers assessment for plan and legal consistency",
      "sourceIds": [
        "virginia-code"
      ],
      "pinpoint": "Va. Code § 15.2-2209.5(A)–(D), (F)–(G)",
      "residentSummary": "Large projects seeking specified land-use approvals must assess nearby sound impacts before a locality decides.",
      "researcherNote": "The statute mandates only sound assessment; the separate water/agriculture/park/historic/forest assessments are discretionary under subsection B."
    },
    {
      "id": "federal-emergency-rice",
      "instrumentId": "federal-stationary-rice-zzzz",
      "pillarTags": [
        "air",
        "power"
      ],
      "mechanismTags": [
        "operating/performance limit",
        "monitoring/disclosure",
        "enforcement/remedy"
      ],
      "plainLanguageRule": "Covered emergency stationary RICE may operate without a time limit during an emergency situation. A separate 100-hour annual cap generally applies to specified maintenance/readiness testing, with up to 50 non-emergency hours counted within that 100-hour allowance and subject to restrictions that vary by source category.",
      "coveredEntities": "Owners/operators of stationary RICE subject to Subpart ZZZZ emergency-engine provisions",
      "thresholdText": "Equipment and source-category applicability is determined under Subpart ZZZZ; not a data-center MW threshold.",
      "exemptions": "Paragraph-specific exceptions and conditions apply, including limited dispatch conditions; the 50-hour allowance generally cannot be used for peak shaving or non-emergency demand response.",
      "existingFacilityTreatment": "Different standards can apply by engine age, construction/reconstruction date, site rating, and major/area source status.",
      "enforcementAuthority": "U.S. EPA and delegated air agencies",
      "enforcementTools": "Compliance demonstrations, reporting, emission/operating limits, and Clean Air Act enforcement",
      "sourceIds": [
        "ecfr-63-6640",
        "epa"
      ],
      "pinpoint": "40 C.F.R. § 63.6640(f)(1)–(4), as of 2026-10-26",
      "residentSummary": "The federal rule’s emergency-engine categories have distinct limits; the often-mentioned 50 hours are conditional and do not authorize routine grid sales or demand response in most cases.",
      "researcherNote": "Do not transfer this provision to compression-ignition engines under § 60.4211 or spark-ignition engines under § 60.4243 without checking those subparts separately."
    },
    {
      "id": "mn-water-preapp-info",
      "instrumentId": "mn-water-preapp-2025",
      "pillarTags": [
        "water",
        "transparency"
      ],
      "mechanismTags": [
        "study/assessment",
        "monitoring/disclosure"
      ],
      "plainLanguageRule": "DNR may request a project description, maximum-day/month and annual water estimates, water source, and water-quality/temperature needs, then must respond in writing about potential water-availability constraints. Communications and records under the process are nonpublic.",
      "coveredEntities": "Minnesota data center project meeting the statutory water-use and permit trigger.",
      "thresholdText": "Proposed consumptive use greater than 100,000,000 gallons/year and new individual permit or permit amendment.",
      "exemptions": "No exemption stated for a project meeting the trigger; DNR has discretion about the preapplication information it requests.",
      "existingFacilityTreatment": "The procedure does not replace environmental review, well-construction approval, or permit review.",
      "enforcementAuthority": "Minnesota Department of Natural Resources",
      "enforcementTools": "Written availability-constraint response; other water permits/reviews remain applicable.",
      "sourceIds": [
        "mn-water-preapp"
      ],
      "pinpoint": "Minn. Stat. § 103G.265, subd. 5(a)–(g); 2025 Minn. Laws, 1st Spec. Sess., ch. 12, § 3",
      "residentSummary": "Very large water projects must provide enough information for the state to assess whether a source can meet demand, but this preapplication exchange is classified nonpublic.",
      "researcherNote": "Track water availability transparency separately from permit conditions; disclosure rules materially affect residents’ ability to review demand forecasts."
    },
    {
      "id": "mn-water-permit-conditions",
      "instrumentId": "mn-water-permit-2025",
      "pillarTags": [
        "water"
      ],
      "mechanismTags": [
        "operating/performance limit",
        "study/assessment"
      ],
      "plainLanguageRule": "For covered new/modified permits, DNR must protect public health, safety, and welfare; reasonably consider conservation, efficient-use, and watershed-health measures; address water conflicts; and require an aquifer test when necessary for the health/safety/welfare finding.",
      "coveredEntities": "Minnesota DNR permit applicants for covered data-center water use, including permittees supplying the stated volume.",
      "thresholdText": "New/additional consumptive use greater than 100,000,000 gallons/year; or existing permit supplying more than that annual volume to a data center.",
      "exemptions": "Not a one-size numeric maximum; conservation measures must be reasonably considered, and aquifer testing is required if DNR determines it necessary.",
      "existingFacilityTreatment": "Applies to new/modified permits and existing permits under the stated supply/use condition.",
      "enforcementAuthority": "Minnesota Department of Natural Resources",
      "enforcementTools": "Permit conditions, conflict review, and aquifer testing where required.",
      "sourceIds": [
        "mn-water-permit"
      ],
      "pinpoint": "Minn. Stat. § 103G.271, subd. 5b(a)–(b); 2025 Minn. Laws, 1st Spec. Sess., ch. 12, § 4",
      "residentSummary": "Above the threshold, water permits must consider conservation and watershed health and protect public health; the statute does not set a single fixed statewide consumption cap.",
      "researcherNote": "Threshold refers to consumptive use. Distinguish withdrawal from consumption and calculate on the statute’s annual basis."
    },
    {
      "id": "mn-large-load-ratepayer",
      "instrumentId": "mn-large-customer-2025",
      "pillarTags": [
        "power",
        "transparency"
      ],
      "mechanismTags": [
        "cost allocation",
        "discretionary approval"
      ],
      "plainLanguageRule": "By December 15, 2026, the PUC must establish a very-large-customer class/subclass for each public electric utility. In reviewing tariffs or service agreements, the PUC must consider assignment of attributable costs, compliance with state electricity benchmarks, protections against stranded costs for other utility customers, and other public-interest outcomes.",
      "coveredEntities": "Minnesota public utilities and customers meeting the class definition that the Commission establishes.",
      "thresholdText": "Threshold and customer characteristics to be set by PUC order; statute itself has no MW number.",
      "exemptions": "Excludes existing, renewed, or extended service agreements and customers actively served before 2020.",
      "existingFacilityTreatment": "Agreements existing/renewed/extended and pre-2020 active-service customers are excluded under subd. 3.",
      "enforcementAuthority": "Minnesota Public Utilities Commission",
      "enforcementTools": "Commission order/rate case and review of utility tariffs or service agreements.",
      "sourceIds": [
        "mn-large-customer"
      ],
      "pinpoint": "Minn. Stat. § 216B.1622, subds. 1–3; 2025 Minn. Laws, 1st Spec. Sess., ch. 12, § 9",
      "residentSummary": "The statute sets a forthcoming process for large-load classes and tariff review; it does not yet state a final threshold or tariff price.",
      "researcherNote": "As checked Oct. 28, 2026, the statutory Dec. 15, 2026 classification deadline remained in the future. Check PUC docket/orders after that date."
    },
    {
      "id": "mn-large-data-fee",
      "instrumentId": "mn-large-fee-2025",
      "pillarTags": [
        "power",
        "finance"
      ],
      "mechanismTags": [
        "cost allocation",
        "incentive/eligibility"
      ],
      "plainLanguageRule": "Commerce must collect an annual fee using the forecast peak demand that the utility arranges to serve: $2 million for 100–250 MW; $3 million above 250 and below 500 MW; $4 million for 500 and below 750 MW; $5 million at 750 MW or above. The fee supports an energy/conservation account and the fee data are nonpublic.",
      "coveredEntities": "Qualified large-scale data centers meeting the linked statutory definition.",
      "thresholdText": "Utility-arranged forecast peak demand: 100 MW or more.",
      "exemptions": "No discretionary waiver stated in § 216B.72; detail of collection schedule delegated to commissioner.",
      "existingFacilityTreatment": "Applies annually to qualified large-scale data centers.",
      "enforcementAuthority": "Minnesota Department of Commerce",
      "enforcementTools": "Annual fee collection; fee data classified nonpublic.",
      "sourceIds": [
        "mn-fee"
      ],
      "pinpoint": "Minn. Stat. § 216B.72(a)–(c); 2025 Minn. Laws, 1st Spec. Sess., ch. 12, § 16",
      "residentSummary": "Minnesota charges an annual fee tied to the power capacity a utility arranges to serve, not the center’s measured energy use.",
      "researcherNote": "Keep MW peak demand separate from MWh energy consumption. Confidential fee data may limit public visibility of assessments."
    },
    {
      "id": "mn-data-tax-eligibility",
      "instrumentId": "mn-tax-exemption-2025",
      "pillarTags": [
        "finance",
        "power",
        "land"
      ],
      "mechanismTags": [
        "incentive/eligibility",
        "enforcement/remedy"
      ],
      "plainLanguageRule": "Certified data centers may receive sales/use tax refunds for eligible enterprise IT equipment and software. A qualified large-scale facility has a 25,000-square-foot minimum and $250 million collective investment threshold over 60 months; it must meet prevailing-wage conditions and obtain an accepted sustainability/green-building certification within three years after service, or the exemption amount is repayable.",
      "coveredEntities": "DEED-certified qualified, refurbished, or qualified large-scale data centers and eligible owners/tenants/purchases.",
      "thresholdText": "Large-scale tier: at least 25,000 square feet and $250,000,000 aggregate facility/tenant qualifying investment in 60 months beginning after June 30, 2025.",
      "exemptions": "Certification and category-specific thresholds; electricity purchases after June 30, 2025 are not exempt; large-scale sustainability certification and prevailing wage apply.",
      "existingFacilityTreatment": "Qualification windows differ by facility type; purchases may qualify within 35 years of first qualifying purchase; certification must occur before July 1, 2042.",
      "enforcementAuthority": "Minnesota DEED, Revenue, and Commerce according to the requirement",
      "enforcementTools": "Certification, tax refund/exemption, labor enforcement, and recapture if green-building requirement is not met.",
      "sourceIds": [
        "mn-tax-exemption"
      ],
      "pinpoint": "Minn. Stat. § 297A.68, subd. 42(a), (e)–(n); 2025 Minn. Laws, 1st Spec. Sess., ch. 12, § 17; ch. 13, art. 3, § 4",
      "residentSummary": "Minnesota offers a long tax exemption for eligible equipment and software, conditioned on certification; the largest tier has labor and sustainability requirements and possible repayment.",
      "researcherNote": "The 2025 amendments removed electricity treatment for purchases after June 30, 2025. Do not describe this as a blanket tax exemption for all data-center costs."
    },
    {
      "id": "pa-data-center-exclusion",
      "instrumentId": "pa-tax-exemption-2021",
      "pillarTags": [
        "finance",
        "power"
      ],
      "mechanismTags": [
        "incentive/eligibility",
        "enforcement/remedy"
      ],
      "plainLanguageRule": "Certified computer data centers and qualified tenants may claim an exemption for covered equipment purchased for installation during the applicable qualification period.",
      "coveredEntities": "Owners/operators and qualified tenants of certified Pennsylvania computer data centers.",
      "thresholdText": "Certification under related Subarticle C provisions; this section defines owner and tenant qualification periods.",
      "exemptions": "Excludes certain internal-use telecom centers, equipment for specified electricity generation/export, proof-of-work crypto-asset mining, and laptops/handheld devices/vehicles.",
      "existingFacilityTreatment": "Owner period runs through the 25th full calendar year after application year; tenant period ends at agreement expiry or the 10th full calendar year after contract year, whichever comes first.",
      "enforcementAuthority": "Pennsylvania Department of Revenue under the certification program",
      "enforcementTools": "Tax exemption; related statutory provisions govern certification and disqualification.",
      "sourceIds": [
        "pa-data-center-tax"
      ],
      "pinpoint": "61 P.S. § 2931-D(a)–(d); 2024 Act 56, § 30(12)",
      "residentSummary": "Pennsylvania offers a certified-project equipment tax break, with exclusions for certain power exports and crypto mining and different time limits for owners and tenants.",
      "researcherNote": "Eligibility standards, application steps, and recapture should be verified against the linked related sections before advising a specific applicant."
    },
    {
      "id": "federal-ci-emergency-hours",
      "instrumentId": "federal-stationary-ci-2026",
      "pillarTags": [
        "air",
        "power"
      ],
      "mechanismTags": [
        "operating/performance limit",
        "monitoring/disclosure",
        "enforcement/remedy"
      ],
      "plainLanguageRule": "Covered stationary compression-ignition engine owners/operators must follow applicable emissions and operating standards. Emergency engines have unlimited hours during qualifying emergencies, generally up to 100 annual hours for specified maintenance/readiness testing, and up to 50 non-emergency hours only under conditions; most cannot use those hours for peak shaving or demand response.",
      "coveredEntities": "Owners/operators of stationary CI engines subject to 40 C.F.R. part 60, subpart IIII.",
      "thresholdText": "Engine type, model year, maximum engine power, construction/installation and applicable source category determine coverage.",
      "exemptions": "Exceptions and testing rules vary by age, size, and use; paragraph (f)(3) has narrow dispatch circumstances.",
      "existingFacilityTreatment": "Different standards apply to pre-2007 and later engines, fire pumps, and non-emergency engines.",
      "enforcementAuthority": "U.S. EPA or delegated air agency",
      "enforcementTools": "Certified engines, maintenance/operating conditions, testing/monitoring, and Clean Air Act enforcement.",
      "sourceIds": [
        "ecfr-ci-4211"
      ],
      "pinpoint": "40 C.F.R. § 60.4211(a), (f)–(g), current eCFR as of 2026-10-26",
      "residentSummary": "Federal emergency backup generator rules are equipment-specific; conditional 50-hour provisions do not create a general grid-sales allowance.",
      "researcherNote": "Do not infer emergency status from labels alone. Analyze the relevant engine subpart, permit, emergency-order policy, source status, and dispatch arrangement."
    },
    {
      "id": "utah-data-center-water-reporting",
      "instrumentId": "utah-data-center-water-transparency-2026",
      "pillarTags": [
        "water",
        "transparency",
        "land"
      ],
      "mechanismTags": [
        "monitoring/disclosure",
        "participation",
        "enforcement/remedy"
      ],
      "plainLanguageRule": "Before approval of a land-use application for a covered new large data center, local authorities must notify the Division of Water Rights, Division of Water Quality, and any relevant water provider. Operators must report projected water needs, annual withdrawals, discharge treatment/temperature, and reuse/replacement plans 90–360 days before construction; after operations begin, annual actual withdrawal and conservation reporting is required. The Division publishes individual withdrawal data and county aggregates for qualifying protected information.",
      "coveredEntities": "Operators of statutory large data centers and municipal/county land-use authorities considering a new large data center application.",
      "thresholdText": "At least 75 acre-feet annual withdrawal and at least 10,000 square feet, plus detailed facility, infrastructure, ownership, and parcel criteria; new large data center means begins operations on/after July 1, 2026.",
      "exemptions": "Statutory protected-record treatment applies to designated projected discharge/reuse and conservation/environmental fields if the operator follows Utah GRAMA procedure; withdrawal reporting/publication remains specifically addressed.",
      "existingFacilityTreatment": "Annual reporting applies to covered new large data centers beginning operations on/after July 1, 2026; existing facilities outside that definition are not brought in by this provision.",
      "enforcementAuthority": "Utah Division of Water Rights / State Engineer",
      "enforcementTools": "Notice of incomplete/non-filed report; fine up to $100 per day for continued failure after notice.",
      "sourceIds": [
        "utah-hb76-enrolled"
      ],
      "pinpoint": "Utah Code § 73-5-8.3(1)(d),(f), (2)–(6), enrolled HB 76 pp. 3–7; effective-date clause p. 7",
      "residentSummary": "Covered new facilities must notify agencies and providers and report expected and actual water withdrawals; the state publishes withdrawal data, with limited statutory confidentiality treatment.",
      "researcherNote": "Do not characterize the measure as a withdrawal cap. The definition contains multiple facility/ownership criteria; statutory annual withdrawals are not synonymous with consumptive use."
    },
    {
      "id": "virginia-gen-set-tier4-permit-gate",
      "instrumentId": "virginia-data-center-gen-set-air-2026",
      "pillarTags": [
        "air",
        "climate",
        "transparency"
      ],
      "mechanismTags": [
        "operating/performance limit",
        "discretionary approval",
        "enforcement/remedy"
      ],
      "plainLanguageRule": "DEQ may not issue an air permit, including general-permit coverage, for a data-center application filed on/after July 1, 2026 unless each engine-generator's permitted emission limit is equal to or below Tier 4-equivalent emissions for the listed pollutants.",
      "coveredEntities": "Applicants for data-center permits under Virginia's air pollution control chapter; each engine-generator covered by the permit.",
      "thresholdText": "Application submission date on/after July 1, 2026. Tier 4 equivalent means selective catalytic reduction or equivalent for NOx, diesel oxidation catalyst or equivalent for CO, and diesel particulate filter or equivalent for particulate matter.",
      "exemptions": "No blanket exception is stated in § 10.1-1322.6; other applicable permit standards may impose stricter requirements.",
      "existingFacilityTreatment": "Application-date trigger; existing permits are not expressly converted by this section alone.",
      "enforcementAuthority": "Virginia Department of Environmental Quality / Air Pollution Control Board under the air-permitting chapter",
      "enforcementTools": "Permit issuance gate and applicable permit enforcement mechanisms.",
      "sourceIds": [
        "virginia-gen-set-air-code",
        "virginia-hb507-history"
      ],
      "pinpoint": "Va. Code § 10.1-1322.6(A)–(C); 2026 Acts ch. 397",
      "residentSummary": "New covered air-permit applications must meet an emissions benchmark for every engine-generator before DEQ can issue the permit.",
      "researcherNote": "The benchmark is defined in terms of emissions achieved by a Tier 4-equivalent set, not a requirement that every gen-set be a particular model. The statute preserves BACT, LAER, RACT, NSPS, NESHAP and stricter permit limits."
    },
    {
      "id": "ohio-dct-minimum-demand",
      "instrumentId": "ohio-power-schedule-dct-2026",
      "pillarTags": [
        "power",
        "transparency"
      ],
      "mechanismTags": [
        "cost allocation",
        "financial security"
      ],
      "plainLanguageRule": "Schedule DCT imposes minimum monthly billing demand floors. Existing load is billed at no less than 60% of contract capacity or the highest billing demand in the preceding 11 months, as written in the sheet. New load billing demand is at least 85% of ramp contract capacity during the ramp; afterward it is at least the greater of 85% of the highest recent billing demand or a tiered Minimum Demand formula, capped at 85% of contract capacity at the top tier.",
      "coveredEntities": "Ohio Power customers with qualifying data-center load under Schedule DCT; associated affiliates/new loads are aggregated according to tariff definitions.",
      "thresholdText": "Generally >25,000 kW (25 MW) monthly maximum demand at a single location or aggregated total customer contract capacity in the service territory; see tariff for separate existing/new load rules.",
      "exemptions": "Specific existing-load treatment and expansion rules apply; separately metered non-data-center load may use a separate account when technically feasible and customer pays associated costs.",
      "existingFacilityTreatment": "Existing Load and New Load have separate minimum-demand formulas and transition definitions.",
      "enforcementAuthority": "Ohio Power Company under PUCO-approved tariff; PUCO oversees regulated service.",
      "enforcementTools": "Minimum monthly tariff billing; tariff allows suspension with Commission approval if use exceeds contract capacity by more than 1,000 kW.",
      "sourceIds": [
        "ohio-power-schedule-dct-current"
      ],
      "pinpoint": "Ohio Power P.U.C.O. No. 22, Schedule DCT, sheets 223-2–223-4; issued/effective Aug. 28, 2026",
      "residentSummary": "Large customers can owe minimum demand charges even when actual use is below the contracted level, helping allocate some load and capacity risk to the customer.",
      "researcherNote": "Tariff text is controlling. The existing-load sentence is disjunctive; reproduce the precise tariff formula in any calculation. Do not treat billing demand as energy consumption (kWh/MWh). Applies to Ohio Power service territory only."
    },
    {
      "id": "ohio-dct-standard-service-notice",
      "instrumentId": "ohio-power-schedule-dct-2026",
      "pillarTags": [
        "power",
        "transparency"
      ],
      "mechanismTags": [
        "cost allocation",
        "participation"
      ],
      "plainLanguageRule": "Schedule DCT requires a customer to give at least 180 days' written notice before returning to or beginning Standard Service Offer service. The utility procures energy separately, with the full cost assigned to the data-center customer; if notice is not given, PJM spot-market costs are assigned to that customer under the tariff/order text.",
      "coveredEntities": "Ohio Power Schedule DCT customers electing Standard Service Offer supply.",
      "thresholdText": "Eligible Schedule DCT customer; the schedule's >25 MW applicability and related definitions govern.",
      "exemptions": "The current tariff text controls; exact exceptions were not extracted in this batch.",
      "existingFacilityTreatment": "Current sheets filed/effective Aug. 28, 2026 incorporate the August 5, 2026 PUCO order for the identified SSO procedure.",
      "enforcementAuthority": "Public Utilities Commission of Ohio and Ohio Power Company",
      "enforcementTools": "Tariff procurement and customer-specific cost assignment; detailed remedy governed by order and tariff.",
      "sourceIds": [
        "ohio-power-schedule-dct-current",
        "ohio-puco-2026-sso"
      ],
      "pinpoint": "Ohio Power P.U.C.O. No. 22, Schedule DCT, sheets 223-4–223-5; PUCO Aug. 5, 2026 release and Case 26-113-EL-ATA",
      "residentSummary": "A large customer that wants default supply must give six months' notice, and energy procurement costs are assigned to that customer under the tariff process.",
      "researcherNote": "The related order is challenged/reconsideration status may matter; no stay conclusion is made. Verify precise current terms and litigation status before future refresh."
    },
    {
      "id": "oregon-large-load-class-and-contract",
      "instrumentId": "oregon-large-energy-use-facilities-hb3546-2025",
      "pillarTags": [
        "power",
        "transparency",
        "climate"
      ],
      "mechanismTags": [
        "cost allocation",
        "financial security",
        "monitoring/disclosure"
      ],
      "plainLanguageRule": "The PUC must provide a separate retail electric service classification and tariff for covered large energy use facilities. Tariffs must allocate or directly assign service costs and mitigate unwarranted cross-class cost shifts. Electric companies must enter into service contracts of at least ten years specifying start timing and a commission-determined minimum payment based on projected use; tariffs and contracts must also meet public-interest conditions.",
      "coveredEntities": "Electric companies and retail electricity consumers that are large energy use facilities, as defined by the act.",
      "thresholdText": "At least 20 MW used or able to be used and primarily engaged in NAICS 2022 code 518210 services; statutory facility definition aggregates buildings/equipment at single, contiguous, or adjacent sites under common control.",
      "exemptions": "Section 3 states use of the separate class is not required if PUC has not approved a tariff for the electric company. Direct access, green-power rate, voluntary renewable tariff, and special contract remain available subject to statutory requirements.",
      "existingFacilityTreatment": "Section 6 applies to new service contracts and to certain earlier contracts when post-effective-date significant investments/costs could increase other customers' cost or risk.",
      "enforcementAuthority": "Oregon Public Utility Commission; regulated electric companies",
      "enforcementTools": "Commission-approved tariffs, contracts, and public-interest conditions; related enforcement under utility law.",
      "sourceIds": [
        "oregon-hb3546-enrolled"
      ],
      "pinpoint": "2025 Or. Laws ch. 323, §§ 2(1)–(3), 3, 5–6; enrolled HB 3546 pp. 1–3",
      "residentSummary": "Qualifying very large computing facilities are assigned a separate utility service class and long-term contract with a minimum payment set by the PUC.",
      "researcherNote": "Statutory framework is verified. Specific PGE implementation terms arise in separate Commission orders/tariffs, whose review and appeal status are not resolved here."
    },
    {
      "id": "loudoun-data-center-noise-controls",
      "instrumentId": "loudoun-zoning-noise-2023",
      "pillarTags": [
        "noise",
        "land",
        "transparency"
      ],
      "mechanismTags": [
        "operating/performance limit",
        "study/assessment",
        "monitoring/disclosure",
        "enforcement/remedy"
      ],
      "plainLanguageRule": "Available County-hosted ordinance text sets all-times A-weighted sound limits by receiving development, requires sound-meter procedures and repeat samples, and requires pre- and post-construction noise studies by a Virginia PE for covered uses subject to a study condition. Certain data-center exterior mechanical equipment next to existing or planned residential property must have four-sided acoustical barriers under Chapter 4.",
      "coveredEntities": "Uses governed by Loudoun County zoning; data-center-specific standards apply under § 4.06.02 in the districts where data centers are permitted, subject to exceptions and transition rules.",
      "thresholdText": "§ 7.05.03 table: 55 dBA residential/rural economy, 60 mixed-use residential, 65 commercial/civic/institutional, 70 industrial, at all times; measure at receiving lot line for most categories. Mixed-use residential measurement is at the nearest dwelling aperture.",
      "exemptions": "Table exceptions include emergency/utility operation and testing of generators/accessory equipment, power equipment, construction/maintenance, utilities and certain other sources. § 7.05.03.G study requirement may still apply under Chapter 4; do not collapse separate provisions.",
      "existingFacilityTreatment": "Ordinance applies subject to vested/statutory rights; seven incorporated towns are outside County zoning; certain Route 28 properties remain under 1972 ordinance and grandfathered applications may use prior ordinance.",
      "enforcementAuthority": "Loudoun County Zoning Administrator and County zoning enforcement under ordinance",
      "enforcementTools": "Required studies and mitigation, site-plan review, zoning enforcement; exact complaint/remedy process not fully reviewed here.",
      "sourceIds": [
        "loudoun-chapter7-official-comparison",
        "loudoun-chapter4-current-url",
        "loudoun-zoning-scope"
      ],
      "pinpoint": "Zoning Ordinance §§ 4.06.02 (Chapter 4 official PDF endpoint unresolved), 7.05.03(A)–(G), official Chapter 7 comparison PDF pp. 56–57",
      "residentSummary": "The County text pairs sound limits and measurement rules with project noise studies and, in some residential-adjacent cases, acoustic barriers for exterior mechanical equipment. Several power-equipment exceptions qualify the general table.",
      "researcherNote": "Chapter 7 source is an official County-hosted comparison PDF; current clean Chapter 4 PDF link returned 404. Confirm live code, amendment history, the mitigation clause's 55 dBA reference, and whether exceptions cover data-center generator testing before legal reliance."
    },
    {
      "id": "prov-ab1577-2026",
      "instrumentId": "ca-ab1577-2026",
      "pillarTags": [
        "transparency"
      ],
      "mechanismTags": [
        "information reporting"
      ],
      "plainLanguageRule": "For data centers of at least 10 MW, the operator reports specified facility and load information upon energization and annually; when seeking a covered discretionary local land-use approval, it submits estimated annual energy use, onsite generation, and average/maximum A-weighted operating sound at the property boundary.",
      "coveredEntities": "Entities and projects within the enacted chapter",
      "thresholdText": "Data-center definition excludes facilities with electrical capacity below 10 MW. Separate local disclosure obligation applies upon application for covered discretionary land-use authorization.",
      "exemptions": "Specified public research, public safety, public national-security, publicly owned, and utility facilities are excluded. Customer-specific energy data and personally identifiable information may not be disclosed in the manner prohibited by the act.",
      "existingFacilityTreatment": "Reporting and disclosure transition provisions control.",
      "enforcementAuthority": "California Energy Commission and local permitting authorities",
      "enforcementTools": "Statutory filing, review, approval, or tariff procedures as applicable",
      "sourceIds": [
        "ab1577-ca"
      ],
      "pinpoint": "2026 Cal. Stats. ch. 434, §§ 1–3; Gov. Code §§ 7927.303, 65909.3; Pub. Res. Code § 25302.10(a)–(f)",
      "residentSummary": "Requires the California Energy Commission to collect specified facility information and requires local permit applicants to disclose certain energy and sound information.",
      "researcherNote": "This source record is based on the official bill/chapter page. Check chaptered text and any implementing CPUC/CEC/local action before relying on details; summaries do not substitute for statutory definitions. Clause-level effective dates, thresholds, and exceptions need review against the complete official chaptered act before legal reliance."
    },
    {
      "id": "prov-ab2383-2026",
      "instrumentId": "ca-ab2383-2026",
      "pillarTags": [
        "power"
      ],
      "mechanismTags": [
        "tariff filing and cost allocation"
      ],
      "plainLanguageRule": "The CPUC must require electrical corporations to file T&D and generation tariffs for participating customers. The generation tariff includes at least a 10-year minimum payment mechanism, non-interconnection/early termination fees, upfront collateral or prepayment, and a cost-recovery floor based on projected load; commission threshold cannot exceed 25 MW. CCAs and ESPs must adopt generation tariffs by January 1, 2028.",
      "coveredEntities": "Entities and projects within the enacted chapter",
      "thresholdText": "CPUC sets a minimum peak-demand threshold for generation tariff applicability, which cannot exceed 25 MW; CCA/ESP threshold also cannot exceed 25 MW.",
      "exemptions": "Statutory exclusions include specified publicly funded research, public safety, publicly funded national-security, publicly owned, and utility facilities; electrical corporation definition excludes electric cooperatives.",
      "existingFacilityTreatment": "Provider and customer applicability is set by statutory terms.",
      "enforcementAuthority": "California Public Utilities Commission and covered providers",
      "enforcementTools": "Statutory filing, review, approval, or tariff procedures as applicable",
      "sourceIds": [
        "ab2383-ca"
      ],
      "pinpoint": "2026 Cal. Stats. ch. 435, Pub. Util. Code §§ 945.1, 945.4–945.6, 945.8",
      "residentSummary": "Directs electrical corporations to file transmission and distribution tariffs for participating data-center customers and establishes related requirements for community choice aggregators and energy service providers.",
      "researcherNote": "This source record is based on the official bill/chapter page. Check chaptered text and any implementing CPUC/CEC/local action before relying on details; summaries do not substitute for statutory definitions. Clause-level effective dates, thresholds, and exceptions need review against the complete official chaptered act before legal reliance."
    },
    {
      "id": "prov-ab2469-2026",
      "instrumentId": "ca-ab2469-2026",
      "pillarTags": [
        "water",
        "land"
      ],
      "mechanismTags": [
        "assessment and discretionary approval"
      ],
      "plainLanguageRule": "A city, county, or city-and-county may not approve a discretionary or ministerial entitlement for covered construction or expansion increasing maximum peak water use unless the applicant provides a Water Code water-supply assessment, projected water use and efficiency measures, and workforce information; starting January 1, 2028 it must also provide a drought-stage water-scarcity plan. The applicant assumes full cost of required water conveyance, treatment, storage, or distribution improvements as determined by the water supplier.",
      "coveredEntities": "Entities and projects within the enacted chapter",
      "thresholdText": "New data center or expansion increasing maximum peak water use; no numeric facility size threshold in § 65964.7.",
      "exemptions": "Statutory requirements are not themselves an entitlement to approval; water-infrastructure cost paragraph is severable.",
      "existingFacilityTreatment": "Covers applications within statutory scope; verify project timing and transition rules from chapter text.",
      "enforcementAuthority": "Local city/county permitting authorities",
      "enforcementTools": "Statutory filing, review, approval, or tariff procedures as applicable",
      "sourceIds": [
        "ab2469-ca"
      ],
      "pinpoint": "2026 Cal. Stats. ch. 436, § 1; Gov. Code § 65964.7(a)–(c)",
      "residentSummary": "For covered new data centers and expansions, bars a local government from approving a permit or entitlement increasing peak water use unless a water-supply assessment, projected-use/efficiency information, and workforce disclosure are provided; a water-scarcity plan is required beginning in 2028.",
      "researcherNote": "This source record is based on the official bill/chapter page. Check chaptered text and any implementing CPUC/CEC/local action before relying on details; summaries do not substitute for statutory definitions. Clause-level effective dates, thresholds, and exceptions need review against the complete official chaptered act before legal reliance."
    },
    {
      "id": "prov-ab2619-2026",
      "instrumentId": "ca-ab2619-2026",
      "pillarTags": [
        "water",
        "transparency"
      ],
      "mechanismTags": [
        "monitoring and disclosure"
      ],
      "plainLanguageRule": "Before an initial city or county business license, equivalent instrument, or permit application, owner/operator supplies the water supplier projected water use/source and maximum day/month/annual volumes under penalty of perjury and includes estimates on the application. At renewal, reports prior-year total, direct and indirect water use and cooling type; urban water suppliers include data-center demand in annual supply-demand assessment and shortage planning.",
      "coveredEntities": "Entities and projects within the enacted chapter",
      "thresholdText": "Type I >25 MW; Type II 2–25 MW; Type III <2 MW. Type definitions determine applicable code sections; confirm each operative paragraph.",
      "exemptions": "No general numerical water cap. Business and Professions Code sections apply through the covered license/permit system; Water Code amendments govern urban water supplier planning.",
      "existingFacilityTreatment": "Renewal reporting applies as specified; exact transitions depend on license timing.",
      "enforcementAuthority": "Water suppliers and local licensing authorities",
      "enforcementTools": "Statutory filing, review, approval, or tariff procedures as applicable",
      "sourceIds": [
        "ab2619-ca"
      ],
      "pinpoint": "2026 Cal. Stats. ch. 437, §§ 2–4; Bus. & Prof. Code §§ 16000.4, 16100.4; Water Code §§ 10609.1, 10632, 10632.1",
      "residentSummary": "Requires covered data centers to provide water-use information to water suppliers and local licensing authorities, including estimates at application and actual annual use at renewal, with cooling-system information.",
      "researcherNote": "Chaptered text distinguishes Type I (>25 MW), Type II (2–25 MW), and Type III (<2 MW); the exact reporting provisions and water-supplier duties have different scope. Map each type and threshold to each code section before publishing as a verified requirement."
    },
    {
      "id": "prov-sb886-2026",
      "instrumentId": "ca-sb886-2026",
      "pillarTags": [
        "power",
        "finance",
        "transparency"
      ],
      "mechanismTags": [
        "tariff and cost allocation"
      ],
      "plainLanguageRule": "For a data center entering a new transmission-level interconnection agreement on or after January 1, 2027, the CPUC must establish a tariff requiring disclosure of applications in other service territories, assigning transmission upgrade/usage costs to the customer, and imposing an early termination fee if the customer departs within 10 years or fails adequate load ramp-up. By January 1, 2028 CPUC must establish/update interconnection and retail-service rules protecting nonparticipating customers from stranded costs.",
      "coveredEntities": "Entities and projects within the enacted chapter",
      "thresholdText": "Applies to data centers with new transmission-level interconnection agreements on or after January 1, 2027; statutory definition of participating customer and facility controls.",
      "exemptions": "Detailed eligibility, tariff, and transition requirements control.",
      "existingFacilityTreatment": "Statutory cutoff dates distinguish covered applications.",
      "enforcementAuthority": "California Public Utilities Commission and electrical corporations",
      "enforcementTools": "Statutory filing, review, approval, or tariff procedures as applicable",
      "sourceIds": [
        "sb886-ca"
      ],
      "pinpoint": "2026 Cal. Stats. ch. 438, Pub. Util. Code §§ 945.2–945.3, 945.7, 945.9",
      "residentSummary": "Requires CPUC rules and tariffs addressing service for specified large data-center customers, including protections against shifting costs or stranded investments to other customers and customer-specific commitments.",
      "researcherNote": "This source record is based on the official bill/chapter page. Check chaptered text and any implementing CPUC/CEC/local action before relying on details; summaries do not substitute for statutory definitions. Clause-level effective dates, thresholds, and exceptions need review against the complete official chaptered act before legal reliance."
    },
    {
      "id": "prov-sb887-2026",
      "instrumentId": "ca-sb887-2026",
      "pillarTags": [
        "land",
        "transparency"
      ],
      "mechanismTags": [
        "environmental review and discretionary approval"
      ],
      "plainLanguageRule": "Makes CEQA applicable to covered data-center entitlements and constrains specified categorical-exemption pathways; an optional environmental-leadership certification route is subject to statutory conditions.",
      "coveredEntities": "Entities and projects within the enacted chapter",
      "thresholdText": "Covered project/entitlement scope and optional certification criteria are specified in the act.",
      "exemptions": "The act contains exclusions and does not categorically eliminate all exemptions.",
      "existingFacilityTreatment": "Application depends on project and entitlement timing under the act.",
      "enforcementAuthority": "Lead agencies under CEQA; Governor’s office for optional certification",
      "enforcementTools": "Statutory filing, review, approval, or tariff procedures as applicable",
      "sourceIds": [
        "sb887-ca"
      ],
      "pinpoint": "Cal. SB 887, ch. 439, §§ 1–3",
      "residentSummary": "Provides that CEQA applies to covered data-center entitlements and specifies limits on categorical exemptions, while establishing an optional certification route subject to statutory conditions.",
      "researcherNote": "This source record is based on the official bill/chapter page. Check chaptered text and any implementing CPUC/CEC/local action before relying on details; summaries do not substitute for statutory definitions. Clause-level effective dates, thresholds, and exceptions need review against the complete official chaptered act before legal reliance. Chaptered statutory text needs section-level review before legal reliance."
    },
    {
      "id": "prov-sb1168-2026",
      "instrumentId": "ca-sb1168-2026",
      "pillarTags": [
        "power",
        "finance"
      ],
      "mechanismTags": [
        "regulatory assessment"
      ],
      "plainLanguageRule": "Directs the CPUC to assess rate opportunities that allocate a reasonable share of transmission, distribution, and procurement costs to large data-center customers and address residential rate pressure.",
      "coveredEntities": "Entities and projects within the enacted chapter",
      "thresholdText": "Commission assessment; the act does not itself set a final rate.",
      "exemptions": "Assessment directive only.",
      "existingFacilityTreatment": "Commission action follows statutory direction.",
      "enforcementAuthority": "California Public Utilities Commission",
      "enforcementTools": "Statutory filing, review, approval, or tariff procedures as applicable",
      "sourceIds": [
        "sb1168-ca"
      ],
      "pinpoint": "Cal. SB 1168, ch. 440, § 1",
      "residentSummary": "Directs the CPUC to assess rate opportunities intended to ensure large data-center customers bear a reasonable share of transmission/distribution and procurement costs and to alleviate residential cost pressure.",
      "researcherNote": "This source record is based on the official bill/chapter page. Check chaptered text and any implementing CPUC/CEC/local action before relying on details; summaries do not substitute for statutory definitions. Clause-level effective dates, thresholds, and exceptions need review against the complete official chaptered act before legal reliance. Chaptered statutory text needs section-level review before legal reliance."
    },
    {
      "id": "prov-fl-water-allocation-2026",
      "instrumentId": "fl-large-data-center-water-2026",
      "pillarTags": [
        "water",
        "land",
        "transparency"
      ],
      "mechanismTags": [
        "prohibition/condition",
        "monitoring/disclosure",
        "participation"
      ],
      "plainLanguageRule": "A water district or DEP may not grant a covered allocation when proposed use would harm local water resources or conflict with local zoning/comprehensive-plan limits; reclaimed water must be used instead of some or all groundwater/surface water where statutory suitability and feasibility conditions are satisfied. Applications averaging at least 100,000 gallons per day must include all water sources and a conservation plan and cannot be approved without a hearing.",
      "coveredEntities": "Large-scale data centers applying for water allocations from a water management district or DEP.",
      "thresholdText": "Average allocation of at least 100,000 gallons/day triggers specified source disclosure, conservation-plan, and hearing conditions.",
      "exemptions": "Reclaimed-water substitution is conditioned on available permitted supply, adequate lines/capacity/quality/access, technical/economic/environmental feasibility, and discharge-permit consistency.",
      "existingFacilityTreatment": "Applies to allocation applications within statutory scope; verify transition and permit facts for each facility.",
      "enforcementAuthority": "Florida water management districts or DEP",
      "enforcementTools": "Allocation denial, conservation-plan review, and public hearing under the statute",
      "sourceIds": [
        "fl-statute-373-262-2026"
      ],
      "pinpoint": "Fla. Stat. § 373.262(1)–(5), especially (2), (4)–(5)",
      "residentSummary": "Certain large water-allocation applications require conservation planning and a public hearing; supply, land-use compatibility, and reclaimed-water criteria also matter.",
      "researcherNote": "The hearing/plan threshold is distinct from the separate statutory grounds for denying an allocation. The act does not create a universal water-volume cap."
    },
    {
      "id": "prov-pa-grid-permit-review-2026",
      "instrumentId": "pa-data-center-executive-order-2026-05",
      "pillarTags": [
        "power",
        "land",
        "water",
        "transparency"
      ],
      "mechanismTags": [
        "discretionary approval",
        "participation",
        "monitoring/disclosure",
        "cost allocation"
      ],
      "plainLanguageRule": "The order directs covered agencies to provide a coordinated public permit-review pathway for qualifying projects; projects above 25 MW seeking the GRID pathway must execute the template consent order and agreement. If an applicant declines GRID, permit review cannot proceed until required local approvals; fast-track treatment is removed for data-center projects.",
      "coveredEntities": "Pennsylvania executive agencies and covered data-center permit applications; GRID pathway threshold applies to projects above 25 MW peak demand.",
      "thresholdText": "More than 25 MW peak demand for specified GRID pathway commitments.",
      "exemptions": "Applies to the Governor’s executive agencies and permits filed after its effective date; independent agencies and local governments are not necessarily bound.",
      "existingFacilityTreatment": "Applies to permit applications filed after the effective date as specified in the order.",
      "enforcementAuthority": "Pennsylvania executive agencies administering covered permit programs",
      "enforcementTools": "Permit sequencing, conditions where authorized, public reporting, and executive-branch oversight.",
      "sourceIds": [
        "pa-eo-2026-05-bulletin"
      ],
      "pinpoint": "56 Pa. Bull. 5950 et seq.; 4 Pa. Code §§ 7.1081–7.1089",
      "residentSummary": "State agencies must follow a public review pathway for covered projects; large projects opting into GRID accept additional commitments and local approvals remain important.",
      "researcherNote": "Do not describe the order as a statewide local zoning mandate. Authority is limited to the Governor’s executive agencies and applicable permits; separate independent PUC proceedings are not final regulatory terms."
    },
    {
      "id": "prov-sd-large-load-power-2026",
      "instrumentId": "sd-large-load-and-water-reporting-sb135-2026",
      "pillarTags": [
        "power",
        "finance"
      ],
      "mechanismTags": [
        "cost allocation",
        "financial security"
      ],
      "plainLanguageRule": "For a data center with peak demand of at least 10 MW, an electricity provider must maintain separate service terms requiring the customer to reimburse all costs fairly attributed to its demand and consumption, including costs incurred if the data center departs the system or materially reduces load.",
      "coveredEntities": "Electric providers and covered data-center customers meeting statutory load criteria.",
      "thresholdText": "Peak demand of 10 MW or greater.",
      "exemptions": "Provider tariff and contract implementation and statutory scope govern application.",
      "existingFacilityTreatment": "Specific customer/service timing provisions apply; review current provider terms.",
      "enforcementAuthority": "South Dakota Public Utilities Commission or relevant public-power provider, depending on provider type.",
      "enforcementTools": "Separate service terms and cost-reimbursement mechanisms.",
      "sourceIds": [
        "sd-sb135-enrolled-2026"
      ],
      "pinpoint": "2026 S.D. SB 135, enrolled §§ 2–4 (new Title 49 provisions)",
      "residentSummary": "Covered large loads may face separate service terms and responsibility for costs attributable to the load.",
      "researcherNote": "The act preserves the authority of counties, municipalities, and other political subdivisions to limit, prohibit, or otherwise regulate data center construction, development, or operation."
    },
    {
      "id": "prov-sd-water-reporting-2026",
      "instrumentId": "sd-large-load-and-water-reporting-sb135-2026",
      "pillarTags": [
        "water",
        "transparency",
        "land"
      ],
      "mechanismTags": [
        "study/assessment",
        "monitoring/disclosure",
        "participation"
      ],
      "plainLanguageRule": "Before operations commence, the operator notifies each local water provider in the proposed area of projected consumption. Each provider issues a written compatibility determination; the operator submits notices/determinations to the Board. The Board may set consumption limits after allocating water to residential and essential public services. Operators submit semiannual water-use reports, including average use and compliance certification, and the Board makes usage data public.",
      "coveredEntities": "Covered water providers, data centers, and South Dakota Board of Water Management.",
      "thresholdText": "Data center as defined by act: peak demand of 10 MW or greater.",
      "exemptions": "Provider and locality scope is controlled by the act.",
      "existingFacilityTreatment": "Reporting schedule includes periodic public reporting; exact facility transition terms require act-level review.",
      "enforcementAuthority": "Water provider and Board of Water Management",
      "enforcementTools": "Written compatibility determination and public/semiannual reporting.",
      "sourceIds": [
        "sd-sb135-enrolled-2026"
      ],
      "pinpoint": "2026 S.D. SB 135, enrolled §§ 5–6 (new Title 49 provisions)",
      "residentSummary": "Water service compatibility and public reporting are part of the state framework.",
      "researcherNote": "Board compliance statement does not authorize consumption above a later Board-set allocation limit. Rulemaking/orders remain implementation matters."
    },
    {
      "id": "prov-ne-large-load-power-2026",
      "instrumentId": "ne-large-load-customer-act-lb1010-2026",
      "pillarTags": [
        "power",
        "finance",
        "transparency"
      ],
      "mechanismTags": [
        "study/assessment",
        "cost allocation",
        "financial security",
        "monitoring/disclosure"
      ],
      "plainLanguageRule": "For covered large-load customers, a public-power supplier may require disclosures about other interconnection requests and onsite backup generation, a study fee, site control, and financial commitments for generation and transmission investment. The act also contains distinct data-center reporting and infrastructure-cost provisions.",
      "coveredEntities": "Nebraska public-power suppliers and large-load customers within the act.",
      "thresholdText": "Large Load Customer Regulation Act generally applies to a customer with more than 20 MW of load at a single site; separate data-center definitions and provisions can use different thresholds.",
      "exemptions": "Provider type, statutory definitions, project timing, and section-specific effective dates control.",
      "existingFacilityTreatment": "Section-specific effective dates and application provisions must be checked before applying to existing customers.",
      "enforcementAuthority": "Nebraska public-power supplier and applicable state authorities.",
      "enforcementTools": "Interconnection studies, fees, service terms, financial commitments, and statutory reporting.",
      "sourceIds": [
        "ne-lb1010-slip-law"
      ],
      "pinpoint": "2026 Neb. LB 1010, enrolled/slip law, Large Load Customer Regulation Act provisions; Neb. Rev. Stat. § 70-1506",
      "residentSummary": "Large-load applications can trigger detailed supplier studies, disclosure, and commitments intended to allocate infrastructure risk.",
      "researcherNote": "Verify section-by-section effective dates and distinguish the act’s general large-load category from its separate data-center reporting definitions."
    },
    {
      "id": "prov-nv-community-support-tax-2026",
      "instrumentId": "nv-data-center-tax-abatement-eo-2026-005",
      "pillarTags": [
        "water",
        "power",
        "air",
        "finance",
        "transparency",
        "land"
      ],
      "mechanismTags": [
        "incentive/eligibility",
        "monitoring/disclosure",
        "enforcement/remedy"
      ],
      "plainLanguageRule": "For covered pending sales/use-tax abatement applications, the applicant must satisfy the order’s Community Support Commitment addressing specified community, water, ratepayer, reliability, workforce, siting, and transparency topics; noncompliance can lead to suspension or recapture within statutory limits.",
      "coveredEntities": "Applicants for specified Nevada state sales/use tax partial abatements whose applications had not been acted upon by the Economic Development Board at the order’s cutoff.",
      "thresholdText": "Program eligibility and the order’s scope are tied to pending state tax-abatement applications; the order specifies a 4.6% tax floor.",
      "exemptions": "Previously approved applications and matters outside the state sales/use tax abatement program are outside the order’s stated scope.",
      "existingFacilityTreatment": "Does not reopen abatements already approved by the Board.",
      "enforcementAuthority": "Nevada Economic Development Board and administering state agencies.",
      "enforcementTools": "Commitment requirements and statutory suspension/recapture mechanisms.",
      "sourceIds": [
        "nv-eo-2026-005"
      ],
      "pinpoint": "EO 2026-005, §§ 1–8",
      "residentSummary": "Some pending tax incentive applicants must make commitments addressing community and infrastructure concerns.",
      "researcherNote": "This is an incentive-eligibility condition, not a generally applicable operating permit, PUC tariff, or local zoning rule."
    },
    {
      "id": "pa-eo-2026-05-framework",
      "instrumentId": "pa-data-center-executive-order-2026-05",
      "pillarTags": [
        "power",
        "water",
        "air",
        "transparency",
        "land",
        "finance",
        "community"
      ],
      "mechanismTags": [
        "permit sequencing",
        "monitoring/disclosure",
        "agency rulemaking",
        "utility tariff",
        "curtailment",
        "public engagement"
      ],
      "plainLanguageRule": "For a project over 25 MW using the GRID pathway, DEP must develop a consent-order template; applicants must commit to GRID conditions, identify local approvals, and execute a project agreement. DEP may issue qualifying permits on a rolling basis only after local-plan consistency and required local approvals are documented. For a >25 MW project without that agreement, DEP cannot begin review until local approvals and any required water-withdrawal/wastewater authorizations are documented; permits cannot be issued on a rolling basis, and PAyback/Permit Decision Guarantee timelines do not apply. Governor-controlled agencies may not use NDAs for a data-center project; DEP must publish a current project map and notify operating centers to report annual energy and water data starting July 1, 2027. The order directs the Governor's special counsel to advocate for PUC rules on curtailment and cost allocation; DEP to recommend any needed backup-generator/air/water regulations; and DCED to prepare local zoning and community-benefit best practices.",
      "coveredEntities": "Projects over 25 MW and agencies within the Governor's jurisdiction; separate provisions address all data-center-related NDAs with covered agencies and annual reporting by operating centers.",
      "thresholdText": "Peak demand over 25 MW for the DEP project review paths. Annual reporting begins July 1, 2027 for operating data centers under the referenced Fiscal Code reporting provision.",
      "exemptions": "The order is limited to existing law and Governor-controlled agencies. GRID review is optional; projects using it must execute an agreement. The alternative non-GRID path has separate sequencing and no rolling permits. Curtailment/tariff language calls for PUC advocacy, not an already-adopted tariff.",
      "existingFacilityTreatment": "Section 7.1083(c) directs DEP to notify currently operating centers to comply with annual energy/water reporting by July 1, 2027 and each year thereafter.",
      "enforcementAuthority": "Governor-controlled agencies; Pennsylvania PUC retains its statutory and regulatory decision-making authority.",
      "enforcementTools": "Project-specific consent agreements and permit conditions; local and water authorization sequencing; annual reports and public map; directions to advocate for PUC action and recommend agency rulemaking; local-government best-practice guidance.",
      "sourceIds": [
        "pa-eo-2026-05-bulletin"
      ],
      "pinpoint": "4 Pa. Code §§ 7.1082(a)–(e), 7.1083(a)–(c), 7.1084(a)–(c), 7.1085(a)–(c), 7.1087, 7.1089; 56 Pa.B. 5898 et seq.",
      "residentSummary": "The order pairs a state-agency review pathway for larger projects with transparency, consumer-protection advocacy, environmental study, and local-government best practices.",
      "researcherNote": "Keep existing directives to agencies distinct from completed PUC rulemaking or DEP regulation. The order creates no private right of action; § 7.1087 limits implementation to existing legal authority."
    },
    {
      "id": "ca-sb887-ceqa-review",
      "instrumentId": "ca-sb887-2026",
      "pillarTags": [
        "land",
        "air",
        "water",
        "power",
        "climate",
        "community",
        "transparency"
      ],
      "mechanismTags": [
        "environmental review",
        "exemption restriction",
        "conditional certification",
        "impact mitigation",
        "community benefits agreement",
        "cost responsibility"
      ],
      "plainLanguageRule": "CEQA applies to the issuance of entitlements related to covered data-center development and operation, and a public-agency project for that purpose cannot use a categorical exemption unless it falls within the specified statutory facility exclusions. Separately, a lead agency may certify a data-center project as meeting criteria for the Governor’s optional environmental-leadership certification pathway. Conditions include advance payment of full interconnection costs; no increase in statewide fossil-fuel consumption; zero-carbon storage sized for four hours at 100% of forecasted peak and used for demand response; behind-the-meter zero-carbon generation to the maximum extent feasible; enforceable payment for grid investments, including new generation, with an early-termination fee; recycled water and water-efficient or waterless cooling; 100% zero-carbon hourly electricity within five years (75% newly developed); specified program conditions; and a legally binding community benefits agreement. The lead agency and Governor certification steps are required for the optional pathway.",
      "coveredEntities": "Public agencies issuing entitlements and lead agencies reviewing data-center projects; Governor and Office of Land Use and Climate Innovation for the optional environmental-leadership certification route.",
      "thresholdText": null,
      "exemptions": "Definition exclusions include publicly funded research, public safety, publicly funded national security, publicly owned, other utility/telecommunications facilities, and independent higher-education research facilities. Categorical exemptions are separately unavailable to covered data-center projects. The leadership route is conditional and does not exempt a project from CEQA.",
      "existingFacilityTreatment": "Applies to covered project entitlements related to development and operation; applicability to a particular existing facility or later permit depends on whether a new entitlement or covered project approval is involved.",
      "enforcementAuthority": "CEQA lead agencies; Governor for environmental-leadership certification; Office of Land Use and Climate Innovation develops uniform statewide certification standards.",
      "enforcementTools": "CEQA environmental review and mitigation; categorical-exemption restriction; conditional environmental-leadership certification with a concurrent administrative record and specified streamlining benefits; legally binding project conditions and community-benefits agreement.",
      "sourceIds": [
        "sb887-ca"
      ],
      "pinpoint": "Cal. Pub. Res. Code §§ 21061.6, 21080.08, 21084(f), 21180(b)(5), 21183.6; 2026 Cal. Stats. ch. 439, §§ 2–6.",
      "residentSummary": "Covered data-center entitlements go through CEQA without categorical exemptions; a separate, optional streamlining path requires the project to meet strict clean-energy, grid-cost, water, and community conditions.",
      "researcherNote": "Do not equate loss of a categorical exemption with an automatic EIR. The chaptered text states that CEQA applies and categorical exemption is unavailable; normal CEQA determinations remain fact- and record-dependent. The CEQA statutory definition and § 21084(f) exclusion list are related but not identical."
    },
    {
      "id": "ok-hb2992-cost-protection",
      "instrumentId": "ok-hb2992-2026",
      "pillarTags": [
        "power",
        "finance"
      ],
      "mechanismTags": [
        "cost allocation",
        "financial security",
        "service conditions"
      ],
      "plainLanguageRule": "Reviewing governing bodies must protect residential, commercial, and industrial customers from unjust rates directly resulting from large-load service and allocate costs and revenues consistent with cost causation. Every electric supplier must maintain separate large-load terms and tariffs, including credit or other measures to recover fairly allocated direct-service costs that may be stranded if load departs or materially falls. Service term must be at least ten years, subject to the stated tax-exempt municipal-financing exception.",
      "coveredEntities": "New data centers, cryptocurrency mining operations, and primary AI-computing facilities contracting for at least 75 MW per facility or in aggregate behind one interconnection after July 1, 2026; electric suppliers and rate-reviewing governing bodies.",
      "thresholdText": "75 MW or greater, per facility or aggregated behind a single point of interconnection; new qualifying loads after July 1, 2026.",
      "exemptions": "Large-load definition excludes entities building generation for behind-the-meter projects and the ordinary listed residential/commercial/agricultural/industrial ratepayer categories. For public-power utilities using tax-exempt municipal financing, agreement term is the lesser of ten years or the applicable IRS guideline.",
      "existingFacilityTreatment": "The statutory definition is framed around new loads after July 1, 2026; application to existing service/load is not assumed.",
      "enforcementAuthority": "Applicable rate-review governing body; Oklahoma Corporation Commission has exclusive enforcement jurisdiction over suppliers subject to its electric-rate jurisdiction.",
      "enforcementTools": "Separate tariffs and service terms; credit and cost-recovery protections; OCC rules/enforcement within its jurisdiction; service compliance obligations for other suppliers.",
      "sourceIds": [
        "ok-hb2992-enrolled-2026"
      ],
      "pinpoint": "2026 Okla. H.B. 2992, §§ 2–6 (new 17 O.S. §§ 901–905), pp. 2–4",
      "residentSummary": "Large computing customers must have separate utility service terms that assign their directly caused costs to them, including costs left behind if they sharply reduce use or leave.",
      "researcherNote": "The act establishes a framework, not a specific rate or approved tariff. Track utility-specific implementation and clarify how the § 8 date interacts with the emergency clause."
    },
    {
      "id": "ok-hb2992-neighbor-notice",
      "instrumentId": "ok-hb2992-2026",
      "pillarTags": [
        "land",
        "transparency",
        "community"
      ],
      "mechanismTags": [
        "notice",
        "participation",
        "enforcement/remedy"
      ],
      "plainLanguageRule": "A covered large-load customer or its developer/owner/agent that purchases land outside an industrial development park or municipality must notify the Corporation Commission, county commissioners, and owners of abutting properties within 60 days by certified mail. Failure carries a $1,500-per-day-per-violation administrative penalty enforced by the county commissioners.",
      "coveredEntities": "Covered large-load customers and their developers, owners, or representatives purchasing qualifying land in Oklahoma.",
      "thresholdText": "The purchaser must meet the act’s large-load definition (75 MW or more); property must be outside an industrial development park or municipality.",
      "exemptions": "This notice section does not apply to land inside an industrial development park or municipality.",
      "existingFacilityTreatment": "Triggered by land purchase for the covered large load; no retroactive notice rule identified in the enrolled text.",
      "enforcementAuthority": "Oklahoma Corporation Commission and relevant county commissioners; county commissioners collect and enforce the stated penalty.",
      "enforcementTools": "Certified-mail notice within 60 days; administrative penalty of $1,500 per day per violation.",
      "sourceIds": [
        "ok-hb2992-enrolled-2026"
      ],
      "pinpoint": "2026 Okla. H.B. 2992, § 7 (new 17 O.S. § 906), pp. 4–5",
      "residentSummary": "In some locations, neighbors whose properties touch a site must receive mailed notice within 60 days after land is purchased for a qualifying large computing project.",
      "researcherNote": "This is post-purchase notice, not a zoning hearing, public-comment right, permit prerequisite, or general statewide notice for every proposed project."
    },
    {
      "id": "ok-sb259-data-center-cooling",
      "instrumentId": "ok-sb259-2026",
      "pillarTags": [
        "water"
      ],
      "mechanismTags": [
        "permit condition",
        "technology standard",
        "enforcement/remedy"
      ],
      "plainLanguageRule": "The Water Resources Board may not permit groundwater use for cooling a data-processing facility or data center through open-air evaporative systems or another cooling technology that consumes groundwater through evaporation or discharge without recirculation. A permit may issue only if the applicant demonstrates closed-loop, dielectric-immersion, or another comparably low-consumptive technology that substantially recirculates groundwater and minimizes consumptive loss as the Board determines.",
      "coveredEntities": "Applicants and users seeking Oklahoma groundwater permits for cooling a data-processing facility or data center.",
      "thresholdText": "No data-center size threshold is stated in this paragraph; groundwater permit requirement and covered cooling use control.",
      "exemptions": "The statutory provision targets groundwater consumed through evaporation or discharge without recirculation. It does not categorically prohibit data centers, non-groundwater cooling supplies, or all evaporative cooling using other sources.",
      "existingFacilityTreatment": "Effective November 1, 2026; transition or grandfathering for existing permits requires review of implementation and other applicable permit provisions.",
      "enforcementAuthority": "Oklahoma Water Resources Board.",
      "enforcementTools": "Groundwater permit denial/conditions; complaint investigation; cease-and-desist, fines, penalties, more frequent reporting, injunction, permit suspension, and other administrative remedies under the amended provisions.",
      "sourceIds": [
        "ok-sb259-enrolled-2026"
      ],
      "pinpoint": "2026 Okla. S.B. 259, § 2 (amending 82 O.S. § 1020.15(A)(11), (B)), pp. 2–4; § 4, p. 6",
      "residentSummary": "A data center cannot obtain a groundwater cooling permit for a system that loses groundwater to evaporation or discharge without recirculation; the applicant must demonstrate a qualifying recirculating, low-consumption design.",
      "researcherNote": "This rule is specific to groundwater permitting and the statutory consumptive-loss formulation. Do not describe it as a statewide ban on cooling towers or as a restriction on municipal/reclaimed water."
    },
    {
      "id": "nj-s3379-usage-reports",
      "instrumentId": "nj-data-center-reporting-2026",
      "pillarTags": [
        "power",
        "water",
        "transparency",
        "air"
      ],
      "mechanismTags": [
        "monitoring/disclosure",
        "public reporting",
        "advance notice"
      ],
      "plainLanguageRule": "Owners/operators submit water-and-energy reports to BPU initially within three months (facilities operating at least a year when the law took effect) or six months (others), then semiannually. Reports include identity/location/start date; total energy, cooling energy, utility and service agreements, onsite primary and backup power and permit/emissions information; IT-equipment energy; total and peak-daily water input; and water source, potability/reclaimed status, supplier agreements, and percentages by source. State-incentivized facilities also report specified energy/water efficiency, renewable energy, temperature, and waste-heat metrics. BPU publishes subsection (b) information within 30 days. Substantial operational or technology changes requiring a report update must be reported at least 60 days before implementation.",
      "coveredEntities": "Owners/operators of New Jersey data centers, excluding qualifying internal-only healthcare facilities that do not provide unaffiliated commercial processing/colocation.",
      "thresholdText": "No MW threshold appears in the data-center definition in this act. Reporting applies to in-state facilities meeting the statutory functional definition.",
      "exemptions": "Qualifying internal healthcare facilities are excluded. Non-incentivized facilities may submit subsection (c) performance/sustainability metrics voluntarily; those metrics are not publicly disclosed and receive statutory confidentiality treatment, subject to the statute’s aggregation exception.",
      "existingFacilityTreatment": "Facilities operating at least one year at the effective date had a three-month initial deadline; other facilities had six months. Reporting continues for three years from each center’s first report, after which BPU determines whether to make it permanent through rulemaking.",
      "enforcementAuthority": "New Jersey Board of Public Utilities, coordinating with the Department of Environmental Protection.",
      "enforcementTools": "Mandatory periodic reporting; publication within 30 days; advance notice of material report-update changes; possible future rulemaking after the three-year reporting period.",
      "sourceIds": [
        "nj-s3379-enacted-status",
        "nj-s3379-2r-text"
      ],
      "pinpoint": "P.L. 2026, c.75 (S3379/A4096), §§ 1(b)–(g), 2; official second-reprint text §§ 1(b)–(g)",
      "residentSummary": "The state will publish core facility energy and water details, including cooling power, backup generators, peak daily water input, and water sources. Some efficiency and sustainability metrics are mandatory only for facilities receiving state incentives.",
      "researcherNote": "The data available to the public is not identical to the full report: performance/sustainability information is not publicly posted and receives a specific confidentiality rule, with anonymized aggregation for at least five facilities. This statute creates transparency duties, not quantitative resource caps."
    },
    {
      "id": "nj-c32-bpu-standards",
      "instrumentId": "nj-data-center-fair-share-2026",
      "pillarTags": [
        "power",
        "finance",
        "climate",
        "participation"
      ],
      "mechanismTags": [
        "cost allocation",
        "financial security",
        "incentive/eligibility",
        "monitoring/disclosure",
        "participation",
        "operating/performance limit"
      ],
      "plainLanguageRule": "By July 7, 2027, the BPU must establish standards by order for each electric public utility, with stakeholder input. The utility-specific definition of a large data center must use a minimum MW threshold no greater than 50 MW and aggregate related facilities sharing ownership/control, location, or substantial infrastructure. Standards must address full attribution of generation, transmission, distribution, and substation costs; stranded-cost protection; efficiency and new clean generation/storage incentives; co-located-generation treatment; demand-reduction trade programs; interconnection priority for binding clean-resource or demand-reduction commitments; priority curtailment of covered data-center loads before residential load during system emergencies (excluding designated critical load); and screening against duplicate or speculative interconnection requests.",
      "coveredEntities": "New Jersey electric public utilities and their customers that meet the BPU-defined large data center/customer criteria; utility tariffs and specific threshold definitions are implementation-dependent.",
      "thresholdText": "BPU must choose a minimum MW threshold for each electric public utility that is not greater than 50 MW; related facilities must be aggregated under the statutory ownership, site, or shared-infrastructure criteria.",
      "exemptions": "The BPU defines the exact qualifying characteristics. Statute preserves FERC jurisdiction over wholesale sales and transmission. Specified pre-effective-date approved service receives limited treatment under subsection g.",
      "existingFacilityTreatment": "Large data centers approved for utility service before July 7, 2026 are exempt from selected subsection d requirements for approved service only; the BPU may phase in specified cost allocation. New or expanded service above the BPU threshold is not covered by that exemption. Applications pending when an approved tariff takes effect are generally covered upon service commencement unless BPU finds application inequitable.",
      "enforcementAuthority": "New Jersey Board of Public Utilities; electric public utilities implement BPU-approved standards and tariffs.",
      "enforcementTools": "BPU standards by order; utility rate-class/tariff petitions within 180 days after the order; approved tariff conditions, cost-allocation rules, demand-flexibility commitments, curtailment, and screening requirements.",
      "sourceIds": [
        "nj-c32-chapter-law",
        "nj-bpu-c32-rfi-2026"
      ],
      "pinpoint": "N.J.S.A. 48:7-6.2(1)(b)(1)–(13), (1)(c), (1)(f)–(j); P.L. 2026, c.32",
      "residentSummary": "The BPU must decide which data-center loads qualify for each utility, set a threshold no higher than 50 MW, and require utility tariffs that assign project-related grid costs to the customer and address efficiency, new clean capacity, demand flexibility, and emergency curtailment.",
      "researcherNote": "These are statutory design instructions for standards and tariffs; some precise obligations do not attach until BPU orders and approved utility tariffs. BPU published an implementation RFI on October 19, 2026, and scheduled a public stakeholder meeting for November 4 with written responses due November 13, 2026 at 5 p.m. The RFI is not itself a final order or tariff."
    },
    {
      "id": "nj-c32-ratepayer-protections",
      "instrumentId": "nj-data-center-fair-share-2026",
      "pillarTags": [
        "power",
        "finance",
        "participation"
      ],
      "mechanismTags": [
        "financial security",
        "cost allocation",
        "monitoring/disclosure",
        "operating/performance limit",
        "enforcement/remedy"
      ],
      "plainLanguageRule": "BPU-approved terms must require adequate guarantees that covered customers pay for at least 85 percent of requested electricity supply for ten years (or as otherwise set in BPU standards), plus deposits, security, or qualifying financial commitments against lower-than-expected use or closure. Tariffs must require demand-flexibility commitments using at least one statutory pathway, annual actual-performance reporting to BPU, and payment of reasonable utility interconnection and study costs by new customers. A stranded-cost mechanism may recover amounts not otherwise secured from the large-data-center customer class.",
      "coveredEntities": "Large data center customers of New Jersey electric public utilities under BPU standards and approved tariffs; existing approved-service customers have the limited exception described in subsection g.",
      "thresholdText": "Applies through the utility-specific BPU definition, which must use an MW threshold no greater than 50 MW and aggregate related facilities. The 85% guarantee concerns requested electricity supply, not a universal 85% total-bill minimum.",
      "exemptions": "The BPU may set the guarantee differently in its standards. Pre-effective-date approved service is exempt from paragraphs d(1), d(2), and d(8) for only the approved MW, subject to other listed provisions and possible cost-allocation phase-in.",
      "existingFacilityTreatment": "New large data-center service is subject to the financial-guarantee, security, and interconnection-study conditions in approved tariffs. Specified pre-July 7, 2026 approved service is exempt from selected provisions; later added load is not exempt under the statutory text.",
      "enforcementAuthority": "New Jersey Board of Public Utilities and electric public utilities through approved tariffs.",
      "enforcementTools": "Financial guarantees, deposits/security, customer-class stranded-cost recovery, tariffed demand-flexibility requirements and financial penalties for nonperformance, annual actual-flexibility reporting, and recovery of reasonable interconnection/study costs.",
      "sourceIds": [
        "nj-c32-chapter-law",
        "nj-bpu-c32-rfi-2026"
      ],
      "pinpoint": "N.J.S.A. 48:7-6.2(1)(d)(1)–(10), (1)(g), (1)(i); P.L. 2026, c.32",
      "residentSummary": "The tariff framework must include a 10-year, 85% requested-supply guarantee for covered loads, financial security against early exit or lower use, demand-flexibility terms, annual performance reporting, and customer payment for reasonable utility study costs.",
      "researcherNote": "The 85% figure applies to electricity supply requested and is subject to BPU standards. Do not say it requires customers to pay 85% of all service charges. The current BPU RFI asks how minimum payment, ramping, penalties, verification, and creditworthiness should work; final tariff details remain undecided."
    }
  ],
  "verificationEvents": [
    {
      "id": "verify-fairfax-2026-10-28",
      "instrumentId": "fairfax-data-center-zoning-2024",
      "checkedAt": "2026-10-28",
      "checkedBy": "Research batch",
      "reviewStatus": "Source-verified",
      "sourcesChecked": [
        "fairfax-text",
        "fairfax-history"
      ],
      "statusEvidence": "Official amendment page states adoption September 10, 2024 and effectiveness September 11, 2024; official recent-amendments page lists the data-center amendment and current other amendments.",
      "findings": "Read the adopted five-page amendment text and cross-checked the county's adopted-amendment history.",
      "unresolvedQuestions": "Verify current Chapter 108.1 noise limits and enforcement details in a later batch; independently check subsequent amendment history before each refresh."
    },
    {
      "id": "verify-virginia-2026-10-28",
      "instrumentId": "virginia-heuf-site-assessment-2026",
      "checkedAt": "2026-10-28",
      "checkedBy": "Research batch",
      "reviewStatus": "Source-verified",
      "sourcesChecked": [
        "virginia-code"
      ],
      "statusEvidence": "Official Code of Virginia displays the provision in the current code, with 2026 Acts chapters 567 and 568 noted.",
      "findings": "Verified threshold, mandatory and discretionary assessment items, utility information, preserved SCC jurisdiction, and expansion exception.",
      "unresolvedQuestions": "Confirm effective date from chapter text and review any later amendment or controlling appellate decision."
    },
    {
      "id": "verify-ecfr-2026-10-28",
      "instrumentId": "federal-stationary-rice-zzzz",
      "checkedAt": "2026-10-28",
      "checkedBy": "Research batch",
      "reviewStatus": "Source-verified",
      "sourcesChecked": [
        "ecfr-63-6640",
        "epa"
      ],
      "statusEvidence": "Current eCFR displayed Title 40 through October 26, 2026; EPA's data-center resource page describes the emergency-order treatment under the referenced sections.",
      "findings": "Verified emergency-engine status condition, emergency-operation rule, testing/maintenance limit, conditional 50-hour non-emergency allowance, and compliance provisions.",
      "unresolvedQuestions": "Assess the complete subpart applicability and permit-specific conditions for any actual facility; separately research other engine subparts."
    },
    {
      "id": "verify-mn-water-preapp-2025",
      "instrumentId": "mn-water-preapp-2025",
      "checkedAt": "2026-10-28",
      "checkedBy": "Research batch",
      "reviewStatus": "Source-verified",
      "sourcesChecked": [
        "mn-water-preapp"
      ],
      "statusEvidence": "Current official statute/code or eCFR provision and cited session-law history checked; current legal status is represented only within the stated scope.",
      "findings": "Verified threshold, written response duty, nonpublic data classification, and no-supplant clause from current official statute and chapter.",
      "unresolvedQuestions": "Check any changes after 2025 statutory codification and relevant agency rules."
    },
    {
      "id": "verify-mn-water-permit-2025",
      "instrumentId": "mn-water-permit-2025",
      "checkedAt": "2026-10-28",
      "checkedBy": "Research batch",
      "reviewStatus": "Source-verified",
      "sourcesChecked": [
        "mn-water-permit"
      ],
      "statusEvidence": "Current official statute/code or eCFR provision and cited session-law history checked; current legal status is represented only within the stated scope.",
      "findings": "Verified 100 million gallons annual consumptive-use trigger, permit types, conservation/watershed requirements, conflict treatment, and conditional aquifer test.",
      "unresolvedQuestions": "Review Minnesota Rules part 6115.0740 and permit application guidance for implementation details."
    },
    {
      "id": "verify-mn-large-customer-2025",
      "instrumentId": "mn-large-customer-2025",
      "checkedAt": "2026-10-28",
      "checkedBy": "Research batch",
      "reviewStatus": "Source-verified",
      "sourcesChecked": [
        "mn-large-customer"
      ],
      "statusEvidence": "Current official statute/code or eCFR provision and cited session-law history checked; current legal status is represented only within the stated scope.",
      "findings": "Verified statutory PUC-class deadline, tariff/service-agreement considerations, and exclusions for existing agreements/pre-2020 service.",
      "unresolvedQuestions": "Search PUC dockets for implementation order before or after the Dec. 15, 2026 deadline."
    },
    {
      "id": "verify-mn-large-fee-2025",
      "instrumentId": "mn-large-fee-2025",
      "checkedAt": "2026-10-28",
      "checkedBy": "Research batch",
      "reviewStatus": "Source-verified",
      "sourcesChecked": [
        "mn-fee"
      ],
      "statusEvidence": "Current official statute/code or eCFR provision and cited session-law history checked; current legal status is represented only within the stated scope.",
      "findings": "Verified current codified annual fee tiers and nonpublic classification; checked enabling 2025 session law.",
      "unresolvedQuestions": "Check Commerce collection schedule and current statutory definition of qualified large-scale center."
    },
    {
      "id": "verify-mn-tax-exemption-2025",
      "instrumentId": "mn-tax-exemption-2025",
      "checkedAt": "2026-10-28",
      "checkedBy": "Research batch",
      "reviewStatus": "Source-verified",
      "sourcesChecked": [
        "mn-tax-exemption"
      ],
      "statusEvidence": "Current official statute/code or eCFR provision and cited session-law history checked; current legal status is represented only within the stated scope.",
      "findings": "Verified current 2025 code and session-law amendments, 35-year qualification period, large-scale eligibility, labor/sustainability conditions, and recapture.",
      "unresolvedQuestions": "Monitor subsequent tax amendments and certify exact category-specific eligibility before application."
    },
    {
      "id": "verify-pa-tax-exemption-2021",
      "instrumentId": "pa-tax-exemption-2021",
      "checkedAt": "2026-10-28",
      "checkedBy": "Research batch",
      "reviewStatus": "Source-verified",
      "sourcesChecked": [
        "pa-data-center-tax"
      ],
      "statusEvidence": "Current official statute/code or eCFR provision and cited session-law history checked; current legal status is represented only within the stated scope.",
      "findings": "Verified official Pennsylvania code text, equipment exclusions, qualification-period endpoints, and 2024 crypto exclusion effective after 2025.",
      "unresolvedQuestions": "Review certification criteria and other related sections; independently recheck 2026 session changes."
    },
    {
      "id": "verify-federal-stationary-ci-2026",
      "instrumentId": "federal-stationary-ci-2026",
      "checkedAt": "2026-10-28",
      "checkedBy": "Research batch",
      "reviewStatus": "Source-verified",
      "sourcesChecked": [
        "ecfr-ci-4211"
      ],
      "statusEvidence": "Current official statute/code or eCFR provision and cited session-law history checked; current legal status is represented only within the stated scope.",
      "findings": "Verified current eCFR selected compliance and emergency-engine paragraphs through Oct. 26, 2026.",
      "unresolvedQuestions": "Determine exact equipment applicability and associated permit requirements for any facility."
    },
    {
      "id": "verify-utah-water-2026-10-28",
      "instrumentId": "utah-data-center-water-transparency-2026",
      "checkedAt": "2026-10-28",
      "checkedBy": "Research batch",
      "reviewStatus": "Source-verified",
      "sourcesChecked": [
        "utah-hb76-enrolled"
      ],
      "statusEvidence": "Enrolled HB 76 § 3 says the act takes effect May 6, 2026; § 73-5-8.3 separately defines new large data center by operations beginning on/after July 1, 2026.",
      "findings": "Read enrolled statutory text and verified threshold, preconstruction reporting, annual reporting, disclosure protections, penalties, and effective-date clause.",
      "unresolvedQuestions": "Check implementing rules and first annual disclosure once due; separately research water rights and discharge permit requirements."
    },
    {
      "id": "verify-virginia-gen-set-2026-10-28",
      "instrumentId": "virginia-data-center-gen-set-air-2026",
      "checkedAt": "2026-10-28",
      "checkedBy": "Research batch",
      "reviewStatus": "Source-verified",
      "sourcesChecked": [
        "virginia-gen-set-air-code",
        "virginia-hb507-history"
      ],
      "statusEvidence": "Current Code § 10.1-1322.6 and LIS HB 507 history identify Chapter 397 and July 1, 2026 effective date.",
      "findings": "Read definitions, permit issuance condition, application date threshold, and express preservation of more stringent standards.",
      "unresolvedQuestions": "Review implementing regulations and any DEQ permit guidance; equipment-specific permit application is outside this record."
    },
    {
      "id": "verify-ohio-dct-2026-10-28",
      "instrumentId": "ohio-power-schedule-dct-2026",
      "checkedAt": "2026-10-28",
      "checkedBy": "Research batch",
      "reviewStatus": "Source-verified",
      "sourcesChecked": [
        "ohio-power-schedule-dct-current",
        "ohio-puco-2026-sso"
      ],
      "statusEvidence": "Official Ohio Power tariff sheets 223-2–223-5 state Aug. 28, 2026 issue/effective date; PUCO official release describes August 5 order and 180-day SSO notice process.",
      "findings": "Read current eligibility, definitions, billing-demand formulas, and notice description; distinguished utility territory from statewide scope.",
      "unresolvedQuestions": "Verify appellate docket No. 2025-1458, stay/disposition, exact order text for 26-113-EL-ATA, and tariff terms on next refresh."
    },
    {
      "id": "verify-oregon-hb3546-2026-10-28",
      "instrumentId": "oregon-large-energy-use-facilities-hb3546-2025",
      "checkedAt": "2026-10-28",
      "checkedBy": "Research batch",
      "reviewStatus": "Source-verified",
      "sourcesChecked": [
        "oregon-hb3546-enrolled",
        "oregon-puc-um2377-docket"
      ],
      "statusEvidence": "Enrolled act states effective upon passage; official PUC legislative report dates passage to June 16, 2025. Official UM 2377 docket identifies orders and judicial review filing through cutoff.",
      "findings": "Read enrolled statutory definitions, tariff principles, 10-year contract minimum, applicability, and sunset of separate provisions; checked PUC docket status but not the very large order PDF.",
      "unresolvedQuestions": "Read Order 26-154, Schedule 96, Order 26-309, and Court of Appeals docket before adding implementation details."
    },
    {
      "id": "verify-loudoun-noise-2026-10-28",
      "instrumentId": "loudoun-zoning-noise-2023",
      "checkedAt": "2026-10-28",
      "checkedBy": "Research batch",
      "reviewStatus": "Source-verified; current clean codification needs review",
      "sourcesChecked": [
        "loudoun-chapter7-official-comparison",
        "loudoun-chapter4-current-url",
        "loudoun-zoning-scope"
      ],
      "statusEvidence": "County-hosted Chapter 7 comparison PDF is readable and County pages establish Dec. 13, 2023 ordinance adoption/effective date and important applicability exceptions; current clean Chapter 4 and Chapter 7 endpoint links returned 404.",
      "findings": "Extracted measurement, sound thresholds, exemptions, studies and scope from County-hosted text; Chapter 4 data-center barrier cross-reference is supported by County-hosted search-indexed text but clean source could not be retrieved in this pass.",
      "unresolvedQuestions": "Reviewer should confirm current codified sections, exact amendment dates, Chapter 4 acoustical-barrier language, generator testing exceptions, and mitigation threshold against live source before legal reliance."
    },
    {
      "id": "verify-ca-ab1577-2026",
      "instrumentId": "ca-ab1577-2026",
      "checkedAt": "2026-10-28",
      "checkedBy": "Research batch",
      "reviewStatus": "Source-verified",
      "sourcesChecked": [
        "official Legislature bill/chapter page",
        "chaptered act text read; accessible mirror used where official reader returns 403"
      ],
      "statusEvidence": "Official California Legislature pages identify chaptered bill and chapter number; chaptered act text was read in accessible format. Date/effective clauses and scope checked as noted in instrument record.",
      "findings": "Read chaptered act text and extracted operative scope, definitions, exclusions, and duties. CPUC/agency implementations remain distinct.",
      "unresolvedQuestions": "For AB 2619, map facility types to each code section and confirm statutory effective dates; for tariff statutes, review current implementing tariffs and proceedings."
    },
    {
      "id": "verify-ca-ab2383-2026",
      "instrumentId": "ca-ab2383-2026",
      "checkedAt": "2026-10-28",
      "checkedBy": "Research batch",
      "reviewStatus": "Source-verified",
      "sourcesChecked": [
        "official Legislature bill/chapter page",
        "chaptered act text read; accessible mirror used where official reader returns 403"
      ],
      "statusEvidence": "Official California Legislature pages identify chaptered bill and chapter number; chaptered act text was read in accessible format. Date/effective clauses and scope checked as noted in instrument record.",
      "findings": "Read chaptered act text and extracted operative scope, definitions, exclusions, and duties. CPUC/agency implementations remain distinct.",
      "unresolvedQuestions": "For AB 2619, map facility types to each code section and confirm statutory effective dates; for tariff statutes, review current implementing tariffs and proceedings."
    },
    {
      "id": "verify-ca-ab2469-2026",
      "instrumentId": "ca-ab2469-2026",
      "checkedAt": "2026-10-28",
      "checkedBy": "Research batch",
      "reviewStatus": "Source-verified",
      "sourcesChecked": [
        "official Legislature bill/chapter page",
        "chaptered act text read; accessible mirror used where official reader returns 403"
      ],
      "statusEvidence": "Official California Legislature pages identify chaptered bill and chapter number; chaptered act text was read in accessible format. Date/effective clauses and scope checked as noted in instrument record.",
      "findings": "Read chaptered act text and extracted operative scope, definitions, exclusions, and duties. CPUC/agency implementations remain distinct.",
      "unresolvedQuestions": "For AB 2619, map facility types to each code section and confirm statutory effective dates; for tariff statutes, review current implementing tariffs and proceedings."
    },
    {
      "id": "verify-ca-ab2619-2026",
      "instrumentId": "ca-ab2619-2026",
      "checkedAt": "2026-10-28",
      "checkedBy": "Research batch",
      "reviewStatus": "Needs clause-level review",
      "sourcesChecked": [
        "official Legislature bill/chapter page",
        "chaptered act text read; accessible mirror used where official reader returns 403"
      ],
      "statusEvidence": "Official California Legislature pages identify chaptered bill and chapter number; chaptered act text was read in accessible format. Date/effective clauses and scope checked as noted in instrument record.",
      "findings": "Read chaptered act text and extracted operative scope, definitions, exclusions, and duties. CPUC/agency implementations remain distinct.",
      "unresolvedQuestions": "For AB 2619, map facility types to each code section and confirm statutory effective dates; for tariff statutes, review current implementing tariffs and proceedings."
    },
    {
      "id": "verify-ca-sb886-2026",
      "instrumentId": "ca-sb886-2026",
      "checkedAt": "2026-10-28",
      "checkedBy": "Research batch",
      "reviewStatus": "Source-verified",
      "sourcesChecked": [
        "official Legislature bill/chapter page",
        "chaptered act text read; accessible mirror used where official reader returns 403"
      ],
      "statusEvidence": "Official California Legislature pages identify chaptered bill and chapter number; chaptered act text was read in accessible format. Date/effective clauses and scope checked as noted in instrument record.",
      "findings": "Read chaptered act text and extracted operative scope, definitions, exclusions, and duties. CPUC/agency implementations remain distinct.",
      "unresolvedQuestions": "For AB 2619, map facility types to each code section and confirm statutory effective dates; for tariff statutes, review current implementing tariffs and proceedings."
    },
    {
      "id": "verify-ca-sb887-2026",
      "instrumentId": "ca-sb887-2026",
      "checkedAt": "2026-10-28",
      "checkedBy": "Research batch",
      "reviewStatus": "Needs clause-level review",
      "sourcesChecked": [
        "sb887-ca"
      ],
      "statusEvidence": "California Governor announced signature of the 2026 data-center package on September 21, 2026; official Legislature bill pages identify chapter numbers. Chapter text was also reviewed in the research batch; verify clause-level applicability against the controlling chapter source.",
      "findings": "Added a concise policy summary for the chaptered measure, with applicability and non-overclaim caveats.",
      "unresolvedQuestions": "Retrieve and check chaptered/enrolled text for section-level thresholds, dates, exemptions, grandfathering, and enforcement before presenting as verified requirements."
    },
    {
      "id": "verify-ca-sb1168-2026",
      "instrumentId": "ca-sb1168-2026",
      "checkedAt": "2026-10-28",
      "checkedBy": "Research batch",
      "reviewStatus": "Needs clause-level review",
      "sourcesChecked": [
        "sb1168-ca"
      ],
      "statusEvidence": "California Governor announced signature of the 2026 data-center package on September 21, 2026; official Legislature bill pages identify chapter numbers. Chapter text was also reviewed in the research batch; verify clause-level applicability against the controlling chapter source.",
      "findings": "Added a concise policy summary for the chaptered measure, with applicability and non-overclaim caveats.",
      "unresolvedQuestions": "Retrieve and check chaptered/enrolled text for section-level thresholds, dates, exemptions, grandfathering, and enforcement before presenting as verified requirements."
    },
    {
      "id": "verify-fl-large-data-center-water-2026",
      "instrumentId": "fl-large-data-center-water-2026",
      "checkedAt": "2026-10-28",
      "checkedBy": "Research batch",
      "reviewStatus": "Source-verified",
      "sourcesChecked": [
        "fl-statute-373-262-2026"
      ],
      "statusEvidence": "Florida Statutes 2026 text includes § 373.262; official session law 2026-65 § 5 effective date checked.",
      "findings": "Read current official section on allocation standards, reclaimed water, reporting, conservation plans, and hearing.",
      "unresolvedQuestions": "Review § 163.326 local large-load land-use provisions separately and monitor implementation."
    },
    {
      "id": "verify-pa-data-center-executive-order-2026-05",
      "instrumentId": "pa-data-center-executive-order-2026-05",
      "checkedAt": "2026-10-28",
      "checkedBy": "Research batch",
      "reviewStatus": "Source-verified",
      "sourcesChecked": [
        "pa-eo-2026-05-bulletin"
      ],
      "statusEvidence": "Official Pennsylvania Bulletin signed order text, Executive Order 2026-05, August 18, 2026; codified at 4 Pa. Code ch. 7, subch. RRR.",
      "findings": "Read official bulletin text covering permit pathways, GRID commitments, sequencing, transparency, and reporting.",
      "unresolvedQuestions": "Check each agency implementation and distinguish Governor-controlled from independent agencies; review any subsequent litigation or amendment."
    },
    {
      "id": "verify-sd-large-load-and-water-reporting-sb135-2026",
      "instrumentId": "sd-large-load-and-water-reporting-sb135-2026",
      "checkedAt": "2026-10-28",
      "checkedBy": "Research batch",
      "reviewStatus": "Source-verified",
      "sourcesChecked": [
        "official enrolled SB 135 text",
        "official bill status page"
      ],
      "statusEvidence": "Enrolled SB 135 text reviewed: §§ 2–6 set >=10 MW scope, separate electricity service/cost terms, preserved local authority, written water compatibility, Board priority allocation limits, semiannual public-use reports. Bill status confirms enactment/signature.",
      "findings": "Read the full enrolled primary text rather than relying on the prior summary.",
      "unresolvedQuestions": "Board of Water Management reporting schedule/orders and provider-specific tariff implementation are not yet reviewed."
    },
    {
      "id": "verify-ne-large-load-customer-act-lb1010-2026",
      "instrumentId": "ne-large-load-customer-act-lb1010-2026",
      "checkedAt": "2026-10-28",
      "checkedBy": "Research batch",
      "reviewStatus": "Needs clause-level review",
      "sourcesChecked": [
        "ne-lb1010-slip-law"
      ],
      "statusEvidence": "Official Nebraska Legislature slip law and bill page identify LB 1010 as enacted and approved April 14, 2026.",
      "findings": "Reviewed enacted framework for single-site threshold, supplier disclosures, study fees, site control, and financial commitments.",
      "unresolvedQuestions": "Retrieve and check chaptered/enrolled text for section-level thresholds, dates, exemptions, grandfathering, and enforcement before presenting as verified requirements."
    },
    {
      "id": "verify-nv-data-center-tax-abatement-eo-2026-005",
      "instrumentId": "nv-data-center-tax-abatement-eo-2026-005",
      "checkedAt": "2026-10-28",
      "checkedBy": "Research batch",
      "reviewStatus": "Source-verified",
      "sourcesChecked": [
        "nv-eo-2026-005"
      ],
      "statusEvidence": "Official signed executive order states effective date September 17, 2026 and applicability to pending applications not yet acted upon by the Board.",
      "findings": "Read official order provisions concerning tax-abatement scope, community commitments, and remedy.",
      "unresolvedQuestions": "Monitor standard form and agency administration; confirm exact date/form for applicants and any subsequent order."
    },
    {
      "id": "verify-nj-c32-2026-10-28",
      "instrumentId": "nj-data-center-fair-share-2026",
      "checkedAt": "2026-10-28",
      "checkedBy": "Research batch",
      "reviewStatus": "Source-verified",
      "sourcesChecked": [
        "nj-c32-chapter-law",
        "nj-bpu-c32-rfi-2026"
      ],
      "statusEvidence": "Official chapter text identifies P.L. 2026, c.32, N.J.S.A. 48:7-6.2, and an immediate effective date; official BPU notice opens implementation RFI docket EO26080463 with a November 13, 2026 response deadline.",
      "findings": "Read the clean official chapter law and BPU implementation RFI. Verified BPU deadline, utility-specific threshold cap and aggregation rule, cost-allocation and stranded-cost direction, clean-resource/demand-flexibility design, tariff sequence, ratepayer security terms, reporting, curtailment, exceptions for previously approved service, and FERC savings clause.",
      "unresolvedQuestions": "BPU standards and utility-specific threshold definitions/tariffs remain pending. Track docket EO26080463 and later utility tariff cases; audit the transition for pending and previously approved load, implementation, enforcement, and any litigation."
    }
  ],
  "coverage": [
    {
      "id": "coverage-va-noise",
      "jurisdictionId": "virginia",
      "pillar": "noise",
      "coverageStatus": "Reviewed within stated scope: relevant measures identified",
      "scope": "Fairfax County zoning noise-study provisions and Virginia HEUF sound assessment statute",
      "sourceSetSearched": [
        "fairfax county adopted zoning amendment/history",
        "Virginia Code § 15.2-2209.5"
      ],
      "searchedAt": "2026-10-28",
      "limitations": "Only one locality and one state statute reviewed; not a Virginia-wide local ordinance survey. Fairfax noise limits remain to be checked in Chapter 108.1.",
      "nextAction": "Verify Fairfax Chapter 108.1 limits; add locality samples and statutory effective-date source."
    },
    {
      "id": "coverage-us-air",
      "jurisdictionId": "us",
      "pillar": "air",
      "coverageStatus": "Research in progress",
      "scope": "Selected emergency stationary RICE provision in 40 C.F.R. pt. 63, subpt. ZZZZ",
      "sourceSetSearched": [
        "current eCFR § 63.6640",
        "EPA data-center Clean Air Act resource"
      ],
      "searchedAt": "2026-10-28",
      "limitations": "No inventory of permits or other engine/turbine rules; applicability is equipment and source specific.",
      "nextAction": "Research CI and SI engine subparts, turbine standards, Title V/major-source thresholds, and state permitting."
    },
    {
      "id": "coverage-us-map",
      "jurisdictionId": "us",
      "pillar": "all",
      "coverageStatus": "Research in progress",
      "scope": "27 source-verified legal instrument records, 4 needs-review records, 38 linked provisions, and official proposal/source leads across 15 states plus federal, local, and utility authorities; not a comprehensive national survey.",
      "sourceSetSearched": [
        "official statutes",
        "official county ordinance text/history",
        "current eCFR",
        "agency resource pages"
      ],
      "searchedAt": "2026-10-28",
      "limitations": "Not a national survey; no state or federal absence findings. Local and utility-service-area coverage is sharply limited. Map shading indicates research records or official bill leads only. Four instruments need review, including California AB 2619, Nebraska LB 1010, Loudoun County current codification, and New Jersey P.L. 2026, c.75 final-text reconciliation. Arizona HB 2467 and the listed Illinois bills are proposal leads, not binding rules.",
      "nextAction": "Resolve four needs-review instruments; refresh and assess Arizona/Illinois proposal leads; follow New Jersey BPU Fair Share Act implementation; continue the 50-state and D.C. source matrix; independently review high-impact provisions."
    },
    {
      "id": "coverage-mn-pilot",
      "jurisdictionId": "minnesota",
      "pillar": "water",
      "coverageStatus": "Reviewed within stated scope: relevant measures identified",
      "scope": "Selected 2025 Minnesota data-center-specific water, large-load tariff-process, annual-fee, and tax-incentive statutes; no environmental-review/EIS measure confirmed in this cited chapter.",
      "sourceSetSearched": [
        "2025 Minnesota Laws, First Special Session, chapter 12",
        "2025 Minnesota Statutes §§ 103G.265, 103G.271, 216B.1622, 216B.72, 297A.68, subd. 42"
      ],
      "searchedAt": "2026-10-28",
      "limitations": "Selected statutes only; implementation dockets and permit-specific details not reviewed. A 2026 utility-class deadline was still pending on the search date.",
      "nextAction": "Check PUC implementation orders after Dec. 15, 2026; review DNR rules, actual permits, and environmental review triggers."
    },
    {
      "id": "coverage-utah-water",
      "jurisdictionId": "utah",
      "pillar": "water",
      "coverageStatus": "Reviewed within stated scope: relevant measures identified",
      "scope": "Utah HB 76 data-center water reporting, notice, and disclosure requirements only",
      "sourceSetSearched": [
        "enrolled 2026 Utah HB 76",
        "Utah legislative bill page"
      ],
      "searchedAt": "2026-10-28",
      "limitations": "Does not survey water rights, wastewater permits, drought allocation, or facility-specific approvals. Only the new statutory reporting framework was checked.",
      "nextAction": "Review implementing rules and first annual public reports; sample relevant water-right and discharge permits."
    },
    {
      "id": "coverage-oregon-power",
      "jurisdictionId": "oregon",
      "pillar": "power",
      "coverageStatus": "Reviewed within stated scope: relevant measures identified",
      "scope": "HB 3546 statewide statutory framework and PGE docket UM 2377 procedure; no tariff terms fully audited",
      "sourceSetSearched": [
        "enrolled Oregon HB 3546",
        "Oregon PUC UM 2377 docket summary"
      ],
      "searchedAt": "2026-10-28",
      "limitations": "The PUC implementation order PDF could not be retrieved due to reader size limit. PGE Schedule 96 terms and appellate status remain unresolved. Does not survey other utilities’ implementation.",
      "nextAction": "Retrieve order, current tariff sheets, and court record before adding implementation-level requirements."
    },
    {
      "id": "coverage-ohio-power",
      "jurisdictionId": "ohio-power",
      "pillar": "power",
      "coverageStatus": "Reviewed within stated scope: relevant measures identified",
      "scope": "Ohio Power Schedule DCT current tariff sheets and PUCO official SSO announcement",
      "sourceSetSearched": [
        "Ohio Power November 2026 tariff book, Schedule DCT sheets 223-2 to 223-5",
        "PUCO Aug. 5, 2026 announcement for Case 26-113-EL-ATA"
      ],
      "searchedAt": "2026-10-28",
      "limitations": "Ohio Power service territory only. Court status and underlying SSO order text were not verified; no other Ohio electric utilities surveyed.",
      "nextAction": "Check Ohio Supreme Court case 2025-1458 for stay/disposition and retrieve the 2026 PUCO order."
    },
    {
      "id": "coverage-va-gen-set-air",
      "jurisdictionId": "virginia",
      "pillar": "air",
      "coverageStatus": "Reviewed within stated scope: relevant measures identified",
      "scope": "Virginia Code § 10.1-1322.6 and official HB 507 history for new data-center air-permit emission gate",
      "sourceSetSearched": [
        "current Code of Virginia § 10.1-1322.6",
        "Virginia LIS HB 507 (2026) history"
      ],
      "searchedAt": "2026-10-28",
      "limitations": "One state statute only; existing permits, implementation guidance, facility-specific emissions and other source categories not surveyed.",
      "nextAction": "Monitor DEQ implementation rules and review actual permit applications/conditions."
    },
    {
      "id": "coverage-ok-power",
      "jurisdictionId": "oklahoma",
      "pillar": "power",
      "coverageStatus": "Reviewed within stated scope: relevant measures identified",
      "scope": "2026 HB 2992 enrolled act: large-load threshold, ratepayer/cost-causation framework, separate service terms, term and land-purchase notice",
      "sourceSetSearched": [
        "Oklahoma Legislature HB 2992 enrolled final version",
        "Oklahoma Legislature official bill history and version list"
      ],
      "searchedAt": "2026-10-28",
      "limitations": "No OCC rules, utility tariffs, supplier implementation, litigation, or codified text comparison reviewed. Emergency/effective-date language requires confirmation.",
      "nextAction": "Compare against codified 17 O.S. §§ 900–906 and audit OCC/utility implementation and any proceedings."
    },
    {
      "id": "coverage-ok-water",
      "jurisdictionId": "oklahoma",
      "pillar": "water",
      "coverageStatus": "Reviewed within stated scope: relevant measures identified",
      "scope": "2026 SB 259 groundwater permitting/reporting amendments, limited to express data-center cooling provision and general enforcement context",
      "sourceSetSearched": [
        "Oklahoma Legislature SB 259 enrolled final version",
        "Oklahoma Legislature official bill history and version list"
      ],
      "searchedAt": "2026-10-28",
      "limitations": "Effective date is November 1, 2026; no rules, permits, or existing-facility transition guidance reviewed. This is groundwater-specific, not an all-source water survey.",
      "nextAction": "Review Water Resources Board rules and codified §§ 1020.15/1020.19B after effective date; sample permit practice."
    },
    {
      "id": "coverage-nj-reporting",
      "jurisdictionId": "new-jersey",
      "pillar": "all",
      "coverageStatus": "Reviewed within stated scope: relevant measures identified",
      "scope": "P.L. 2026, c.75 semiannual energy/water reporting law; not a survey of other New Jersey siting, power, air, noise, or water requirements",
      "sourceSetSearched": [
        "New Jersey Governor signing announcement for S3379/A4096",
        "New Jersey Legislature S3379 second-reprint bill text",
        "New Jersey legislative digest and agency status references"
      ],
      "searchedAt": "2026-10-28",
      "limitations": "Final chapter-law pamphlet was not retrieved; second reprint is paired with official signing confirmation. No BPU implementation rules, first reports, enforcement, or municipal measures reviewed.",
      "nextAction": "Retrieve and compare P.L. 2026, c.75 pamphlet; track BPU implementation and first reports."
    },
    {
      "id": "coverage-arizona-leads",
      "jurisdictionId": "arizona",
      "pillar": "all",
      "coverageStatus": "Research in progress",
      "scope": "One introduced data-center bill (HB 2467) reviewed as a proposal lead; no systematic survey of current Arizona incentives, permits, or local rules.",
      "sourceSetSearched": [
        "Arizona Legislature HB 2467 proposed bill text",
        "Arizona Legislature 2026 session-law index and adjournment notice"
      ],
      "searchedAt": "2026-10-28",
      "limitations": "HB 2467 text contains proposed power and water requirements but no enacted chapter was identified in the 2026 session-law index. No comprehensive legal or bill-history review; no absence conclusion.",
      "nextAction": "Verify official bill-history action; search current Arizona statutes, incentives, utility tariffs, permits, and local zoning."
    },
    {
      "id": "coverage-illinois-leads",
      "jurisdictionId": "illinois",
      "pillar": "all",
      "coverageStatus": "Research in progress",
      "scope": "Selected 2026 bills SB 2181, SB 3120, SB 3761, SB 4004, SB 4016, and HB 4989; proposal/status leads only, not a survey of operative Illinois law.",
      "sourceSetSearched": [
        "Illinois General Assembly official bill status/synopsis pages",
        "Illinois General Assembly introduced SB 4016 text"
      ],
      "searchedAt": "2026-10-28",
      "limitations": "Most surfaced bills show last action May 22, 2026; text/status summaries are proposal discovery records. No complete current status/amendment audit and no existing statute, ICC tariff, permit, or local zoning analysis.",
      "nextAction": "Recheck current session/committee actions and any successor legislation, then review current data-center tax/incentive statute and utility tariff/permit implementation."
    },
    {
      "id": "coverage-nj-power-2026",
      "jurisdictionId": "new-jersey",
      "pillar": "power",
      "coverageStatus": "Reviewed within stated scope: relevant measure identified; implementation in progress",
      "scope": "P.L. 2026, c.32 Data Center Fair Share Act and BPU implementation RFI Docket EO26080463; no utility tariff has been audited in this batch.",
      "sourceSetSearched": [
        "official P.L. 2026, c.32 chapter text / N.J.S.A. 48:7-6.2",
        "New Jersey BPU Oct. 19, 2026 RFI and public notice",
        "Governor signing announcement and official bill status"
      ],
      "searchedAt": "2026-10-28",
      "limitations": "Statutory framework is operative, but BPU standards, the per-utility threshold, and individual tariff terms remain to be issued. Does not inventory utility tariff filings, wholesale/PJM rules, local permits, water, or air rules. The RFI is nonfinal input-seeking material.",
      "nextAction": "Track BPU Docket EO26080463, written responses due Nov. 13, 2026 at 5 p.m.; retrieve the BPU standards order due within 12 months of July 7, 2026 and the utility tariff petitions due within 180 days thereafter."
    }
  ],
  "changes": [
    {
      "id": "change-2026-10-28-calibration",
      "instrumentId": null,
      "recordedAt": "2026-10-28",
      "changeType": "Initial source-verified calibration records",
      "priorVersionReference": "schemaVersion 1: five discovery sources and zero verified legal instruments",
      "newVersionReference": "schemaVersion 2: three instruments and four extracted provisions",
      "explanation": "Added structured jurisdiction, legal instrument, provision, source, verification, coverage, and queue data; retained original source IDs and separated official leads from verified legal text.",
      "sourceIds": [
        "fairfax-text",
        "fairfax-history",
        "virginia-code",
        "ecfr-63-6640",
        "epa"
      ]
    },
    {
      "id": "change-2026-10-28-batch2",
      "instrumentId": null,
      "recordedAt": "2026-10-28",
      "changeType": "Completed initial calibration and expanded source-verified sample",
      "priorVersionReference": "2026-10-28 completed 10-instrument calibration sample; 11 provisions",
      "newVersionReference": "2026-10-28 bounded expansion: 15 instruments; 17 provisions",
      "explanation": "Added Utah water transparency, Virginia engine-generator air permitting, Ohio Power Schedule DCT, Oregon large-energy-use statute, and Loudoun County noise/zoning records. The Loudoun record is explicitly flagged for confirmation against the current clean codification; Oregon tariff implementation remains a queued procedural lead.",
      "sourceIds": [
        "mn-water-preapp",
        "mn-water-permit",
        "mn-large-customer",
        "mn-fee",
        "mn-tax-exemption",
        "pa-data-center-tax",
        "ecfr-ci-4211",
        "utah-hb76-enrolled",
        "virginia-gen-set-air-code",
        "ohio-power-schedule-dct-current",
        "oregon-hb3546-enrolled",
        "loudoun-chapter7-official-comparison"
      ]
    },
    {
      "id": "change-2026-10-28-batch3",
      "instrumentId": null,
      "recordedAt": "2026-10-28",
      "changeType": "Expanded multi-state statutory and executive-order sample; strengthened explainer",
      "priorVersionReference": "2026-10-28 bounded expansion: 15 source-verified instruments; 17 provisions",
      "newVersionReference": "2026-10-28 batch 3 refined in batch 4: 27 instruments (22 source-verified, 5 needs-review); 30 provisions.",
      "explanation": "Added seven California 2026 chaptered data-center measures, Florida water allocation statute, Pennsylvania Executive Order 2026-05, South Dakota SB 135, Nebraska LB 1010, and Nevada Executive Order 2026-005. Expanded the illustrated guide’s regulatory-authority pathway and regulatory tools by concern. The new records require independent legal review; some section-level implementation details remain queued. Batch 4 read accessible chaptered California text and promoted AB 1577, AB 2383, AB 2469, and SB 886 after extracting operative provisions; AB 2619 remains needs-review pending type-to-section mapping. Other California bills remain needs-review.",
      "sourceIds": [
        "ab1577-ca",
        "ab2383-ca",
        "ab2469-ca",
        "ab2619-ca",
        "sb886-ca",
        "sb887-ca",
        "sb1168-ca",
        "fl-statute-373-262-2026",
        "pa-eo-2026-05-bulletin",
        "sd-sb135-enrolled-2026",
        "ne-lb1010-slip-law",
        "nv-eo-2026-005"
      ]
    },
    {
      "id": "change-2026-10-28-batch4",
      "instrumentId": null,
      "recordedAt": "2026-10-28",
      "changeType": "Primary-text review of California 2026 laws and status correction",
      "priorVersionReference": "Batch 3: California and Nebraska laws categorized Needs clause-level review",
      "newVersionReference": "2026-10-28 batch 4: 27 instruments (22 source-verified, 5 needs-review); 30 provisions.",
      "explanation": "Read chaptered texts for AB 1577, AB 2383, AB 2469, AB 2619, SB 886, SB 887 and SB 1168 using official bill pages plus accessible chaptered text. Promoted statutes with provision-level duties and scope extracted; retained AB 2619, SB 887, SB 1168 and Nebraska LB 1010 as needs-review where thresholds, exceptions, or code section mapping remain incomplete. Also read the South Dakota enrolled act and confirmed its 10 MW threshold, provider cost-recovery requirement, preserved local authority, written water compatibility, Board limits, and semiannual public reporting.",
      "sourceIds": [
        "ab1577-ca",
        "ab2383-ca",
        "ab2469-ca",
        "ab2619-ca",
        "sb886-ca",
        "sb887-ca",
        "sb1168-ca"
      ]
    },
    {
      "id": "change-2026-10-28-batch5",
      "instrumentId": null,
      "recordedAt": "2026-10-28",
      "changeType": "Status reconciliation and Pennsylvania provision-level extraction",
      "priorVersionReference": "Batch 4: 27 instruments (22 source-verified, 5 needs-review); 30 provisions.",
      "newVersionReference": "Batch 5 local source: 27 instruments (23 source-verified, 4 needs-review); 31 provisions.",
      "explanation": "Promoted California SB 1168 after chaptered-text review and clarified that it directs a cost-allocation assessment rather than adopting a tariff. Added a Pennsylvania EO 2026-05 provision record covering its >25 MW GRID review pathway, public disclosure, agency advocacy on curtailment and cost-protective tariffs, environmental rule recommendations, and local best-practice guidance. Kept operative agency directions distinct from future PUC/DEP rulemaking. Live Sites source synchronization remains pending after DNS resolution failure.",
      "sourceIds": [
        "sb1168-ca",
        "pa-eo-2026-05-bulletin"
      ]
    },
    {
      "id": "change-2026-10-28-batch6",
      "instrumentId": "ca-sb887-2026",
      "recordedAt": "2026-10-28",
      "changeType": "Chaptered-text review and CEQA scope clarification",
      "priorVersionReference": "Batch 5: 27 instruments (23 source-verified, 4 needs-review); 31 provisions.",
      "newVersionReference": "Batch 6 local source: 27 instruments (24 source-verified, 3 needs-review); 32 provisions.",
      "explanation": "Reviewed California SB 887 chaptered text sections 2–6, linked the CEQA entitlement and categorical-exemption rules to their sections, extracted the conditional environmental-leadership certification criteria, and clarified that loss of categorical exemption does not automatically require an EIR. Official California Legislature page confirmed chapter status; its full-text endpoint returned 403, so the chaptered mirror text must be rechecked against the official enrolled act when available.",
      "sourceIds": [
        "sb887-ca"
      ]
    },
    {
      "id": "change-2026-10-28-batch7",
      "instrumentId": null,
      "recordedAt": "2026-10-28",
      "changeType": "Oklahoma ratepayer/groundwater statutes and New Jersey resource-reporting act",
      "priorVersionReference": "Batch 6: 27 instruments (24 source-verified, 3 needs-review); 32 provisions.",
      "newVersionReference": "2026-10-28 batch 7 local source: 30 instruments (26 source-verified, 4 needs-review); 36 provisions.",
      "explanation": "Read the Oklahoma HB 2992 and SB 259 enrolled final acts and official bill histories; added separate provisions for large-load cost allocation, land-purchase notice, and groundwater-dependent data-center cooling. Read New Jersey S3379 second-reprint text and official Governor signing announcement confirming P.L. 2026, c.75; added a provisional semiannual reporting/disclosure provision; status remains needs-review pending comparison of the official chapter-law pamphlet to the second reprint. New Jersey final chapter pamphlet was not retrievable, so its enacted status is confirmed but clause-level text remains needs-review pending reconciliation. Updated queue and scoped state coverage.",
      "sourceIds": [
        "ok-hb2992-enrolled-2026",
        "ok-hb2992-history-2026",
        "ok-sb259-enrolled-2026",
        "nj-s3379-enacted-status",
        "nj-s3379-2r-text"
      ]
    },
    {
      "id": "change-2026-10-28-batch8",
      "instrumentId": null,
      "recordedAt": "2026-10-28",
      "changeType": "Arizona and Illinois official proposal coverage leads",
      "priorVersionReference": "Batch 7: 30 instruments (26 source-verified, 4 needs-review); 36 provisions; research records in 13 states.",
      "newVersionReference": "Batch 8 local source: 30 instruments (26 source-verified, 4 needs-review); 36 provisions; official source leads in 15 states.",
      "explanation": "Added Arizona HB 2467 as a proposal-only source lead after reviewing its official bill text and checking the 2026 session-law index (no chapter identified); do not present proposed renewable/storage or water-intensity requirements as effective. Added six Illinois official bill leads spanning water disclosure/aquifer protection, large-load tariffs, incentives, energy/water reporting, heat reuse/cooling, and a proposed hyperscale framework. Official bill pages show proposals/re-referrals; no Illinois operative framework or current complete bill status was audited. Added two scoped coverage records and queue tasks; instrument/provision counts do not change.",
      "sourceIds": [
        "az-hb2467-2026-lead",
        "il-sb3761-2026-lead",
        "il-sb4004-2026-lead",
        "il-sb3120-2026-lead",
        "il-sb2181-2026-lead",
        "il-sb4016-2026-lead",
        "il-hb4989-2026-lead"
      ]
    },
    {
      "id": "change-2026-10-28-batch9",
      "instrumentId": "nj-data-center-fair-share-2026",
      "recordedAt": "2026-10-28",
      "changeType": "New Jersey Data Center Fair Share Act and implementation RFI",
      "priorVersionReference": "Batch 8: 30 instrument records (26 source-verified, 4 needs-review); 36 provisions; 51 sources.",
      "newVersionReference": "2026-10-28 batch 9 local source: 31 instrument records (27 source-verified, 4 needs-review); 38 provisions; 53 sources.",
      "explanation": "Read the official chaptered P.L. 2026, c.32 (N.J.S.A. 48:7-6.2) and New Jersey BPU RFI Docket EO26080463. Added the enacted statewide electric-service framework as a source-verified statute and separated standards/tariff design from customer financial-security and demand-flexibility requirements. The chapter law is in force; the BPU threshold and utility tariffs are still implementation-dependent. Added a scoped New Jersey power coverage record and a queue item for the November 2026 RFI and subsequent order/tariffs.",
      "sourceIds": [
        "nj-c32-chapter-law",
        "nj-bpu-c32-rfi-2026"
      ]
    }
  ],
  "researchQueue": [
    {
      "id": "queue-ohio-tariff",
      "jurisdictionId": "ohio-power",
      "instrumentId": "ohio-power-schedule-dct-2026",
      "priority": "High",
      "reason": "Large-load cost allocation can affect ratepayers, but this tariff is utility-territory-specific and related judicial status remains unresolved.",
      "nextAction": "Check Supreme Court of Ohio case 2025-1458 for disposition/stay and retrieve the August 2026 PUCO 26-113-EL-ATA order text to confirm current SSO tariff terms.",
      "officialSourceLead": "https://www.aepohio.com/lib/docs/ratesandtariffs/Ohio/November_2026_Ohio_Power_Tariff_Book.pdf",
      "status": "In progress"
    },
    {
      "id": "queue-loudoun-noise",
      "jurisdictionId": "loudoun-county",
      "instrumentId": "loudoun-zoning-noise-2023",
      "priority": "High",
      "reason": "A County-hosted comparison text is available, but clean current Chapter 4/7 ordinance endpoints return 404; confirm amendment history and exact current data-center standards before legal reliance.",
      "nextAction": "Retrieve current codified Chapters 4 and 7 and amendment history; confirm acoustical-barrier language, noise-study timing, table values/exemptions, mitigation wording, and generator testing rules.",
      "officialSourceLead": "https://www.loudoun.gov/zoningordinance",
      "status": "In progress"
    },
    {
      "id": "queue-minnesota-permits-and-puc",
      "jurisdictionId": "minnesota",
      "instrumentIdIfKnown": null,
      "priority": "High",
      "reason": "Map selected statutes but no individual permit, implementation PUC decision, or environmental-review triggers have been audited.",
      "nextAction": "After statutory deadline, inspect PUC orders; review water appropriation rules and permits, MPCA/MEPA review thresholds, and site-specific air/wastewater permits.",
      "officialSourceLead": "https://www.revisor.mn.gov/laws/2025/1/12/",
      "status": "Queued"
    },
    {
      "id": "queue-independent-review",
      "jurisdictionId": "us",
      "instrumentIdIfKnown": null,
      "priority": "High",
      "reason": "The source-verified calibration records have not yet been independently reviewed.",
      "nextAction": "Ask a legal researcher to audit pinpoints, instrument status, applicability, exceptions, and normalized summaries for all ten entries; record review findings without silently replacing the source record.",
      "officialSourceLead": null,
      "status": "Queued"
    },
    {
      "id": "queue-fairfax-noise-code",
      "jurisdictionId": "fairfax-county",
      "instrumentIdIfKnown": "fairfax-data-center-zoning-2024",
      "priority": "High",
      "reason": "The zoning amendment cross-references Chapter 108.1 but does not itself state noise limits or measurement conditions.",
      "nextAction": "Read current Chapter 108.1 and verify receiving points, day/night periods, dBA/dBC, averaging, tonal treatment, testing and enforcement.",
      "officialSourceLead": "https://www.fairfaxcounty.gov/planning-development/zoning/noise-ordinance",
      "status": "Queued"
    },
    {
      "id": "queue-virginia-act-date",
      "jurisdictionId": "virginia",
      "instrumentIdIfKnown": "virginia-heuf-site-assessment-2026",
      "priority": "Medium",
      "reason": "The exact effective date for the separate Virginia siting assessment statute remains unresolved, unlike the verified air-permit statute.",
      "nextAction": "Retrieve signed Acts chapters 567/568 and confirm effective date, applicability, and any transition clause.",
      "officialSourceLead": "https://lis.virginia.gov/",
      "status": "Queued"
    },
    {
      "id": "queue-oregon-puc-implementation",
      "jurisdictionId": "oregon",
      "instrumentIdIfKnown": "oregon-large-energy-use-facilities-hb3546-2025",
      "priority": "High",
      "reason": "PUC docket reflects adoption, reconsideration, compliance filings, and an appeal; actual current tariff terms and appellate status are material to application.",
      "nextAction": "Retrieve Order 26-154, PGE Schedule 96 and Advice 26-39, Order 26-309, and Court of Appeals docket; compare effective tariff sheets.",
      "officialSourceLead": "https://apps.puc.state.or.us/edockets/DocketNoLayout.asp?DocketID=24470",
      "status": "In progress"
    },
    {
      "id": "queue-utah-water-implementation",
      "jurisdictionId": "utah",
      "instrumentIdIfKnown": "utah-data-center-water-transparency-2026",
      "priority": "Medium",
      "reason": "Statutory reporting requirements are effective for covered new large data centers, but implementing rules and first public reports are not reviewed.",
      "nextAction": "Check Utah Division of Water Rights rules and guidance, first annual report/public disclosure, and separate water-right/wastewater permits.",
      "officialSourceLead": "https://waterrights.utah.gov/data-centers/",
      "status": "Queued"
    },
    {
      "id": "queue-state-coverage",
      "jurisdictionId": "us",
      "instrumentIdIfKnown": null,
      "priority": "High",
      "reason": "The bounded sample has legal instrument records in 13 states plus official bill leads in Arizona and Illinois; no systematic state-by-state or complete local/utility survey has occurred.",
      "nextAction": "Build a 50-state and D.C. primary-source coverage matrix, refresh official leads to current session status, and distinguish researched measures from absence findings.",
      "officialSourceLead": null,
      "status": "In progress"
    },
    {
      "id": "queue-pa-tax-eligibility",
      "jurisdictionId": "pennsylvania",
      "instrumentIdIfKnown": "pa-tax-exemption-2021",
      "priority": "Medium",
      "reason": "The mapped Pennsylvania tax section cross-references program certification and qualification requirements elsewhere in the code.",
      "nextAction": "Review 61 P.S. §§ 2913-D, 2917-D, and 2942-D for current certification thresholds, application, recapture, and sunset.",
      "officialSourceLead": "https://www.legis.state.pa.us/WU01/LI/LI/US/HTM/1971/0/0002.029D000.031.000..HTM",
      "status": "Queued"
    },
    {
      "id": "queue-illinois-proposals",
      "jurisdictionId": "illinois",
      "instrumentIdIfKnown": null,
      "priority": "High",
      "reason": "Several data-center water, energy, tariff, and disclosure proposals were identified, but bill statuses are stale or limited to introduced text and no operative Illinois framework has been audited.",
      "nextAction": "Recheck official status/amendments for SB 2181, SB 3120, SB 3761, SB 4004, SB 4016, and HB 4989; then review current incentives, utility tariffs, environmental permits, and local zoning.",
      "officialSourceLead": "https://www.ilga.gov/Legislation/BillStatus?DocNum=3761&DocTypeID=SB&GAID=18&LegId=167068&SessionID=114",
      "status": "In progress"
    },
    {
      "id": "queue-arizona-proposal",
      "jurisdictionId": "arizona",
      "instrumentIdIfKnown": null,
      "priority": "Medium",
      "reason": "HB 2467 proposed strict water and renewable-power requirements but was not located in the 2026 session-law index; bill-history action and operative Arizona framework remain unaudited.",
      "nextAction": "Confirm official bill-history disposition and audit current data-center incentives, water, air, utility, and local siting requirements.",
      "officialSourceLead": "https://www.azleg.gov/legtext/57leg/2r/bills/hb2467p.htm",
      "status": "Queued"
    },
    {
      "id": "queue-nj-fair-share-implementation",
      "jurisdictionId": "new-jersey",
      "instrumentIdIfKnown": "nj-data-center-fair-share-2026",
      "priority": "High",
      "reason": "P.L. 2026, c.32 establishes important large-load ratepayer protections but leaves utility-specific qualifying thresholds and detailed tariffs to BPU and utility implementation. BPU has opened RFI Docket EO26080463.",
      "nextAction": "Track RFI comments (due 2026-11-13 17:00 Eastern), stakeholder meeting (2026-11-04), BPU standards order (within 12 months of 2026-07-07), and utility tariff petitions (within 180 days after the standards order); check resulting tariffs and implementation.",
      "officialSourceLead": "https://www.nj.gov/bpu/pdf/publicnotice/Webposting-Notice-EO26080463-%20Data%20Center%20Fair%20Share%20Act%20RFI.pdf",
      "status": "In progress"
    }
  ],
  "sources": [
    {
      "id": "fairfax",
      "state": "Virginia",
      "jurisdiction": "Fairfax County",
      "authority": "Local",
      "title": "Data center zoning: noise, design, and proximity",
      "pillars": [
        "noise",
        "land",
        "transparency"
      ],
      "summary": "The adopted county amendment requires noise studies at approval and pre-occupancy stages, screening of operating equipment, and residential setbacks, with approval exceptions and transition provisions.",
      "publisher": "Fairfax County Government",
      "url": "https://www.fairfaxcounty.gov/planning-development/sites/planning-development/files/Assets/Documents/zoning%20ordinance/adopted%20amendments/ZO_112_1-2024-9.pdf",
      "pinpoint": "ZO 112.1-2024-9 / 112.2-2024-8, § 4102.6.A; Appendix 1, § 2.B",
      "checked": "2026-10-28",
      "review": "Source-verified legal instrument",
      "legalStatus": "Effective; local zoning scope",
      "next": "Review Chapter 108.1 noise limits separately and check later amendments on refresh.",
      "instrumentId": "fairfax-data-center-zoning-2024"
    },
    {
      "id": "loudoun",
      "state": "Virginia",
      "jurisdiction": "Loudoun County",
      "authority": "Local",
      "title": "Noise studies and neighborhood concerns",
      "pillars": [
        "noise",
        "air"
      ],
      "summary": "County’s official page reports data-center noise studies and a residential property-line limit. This remains an agency summary, not a substitute for the ordinance text. A separate ordinance record is linked with current-codification caveats.",
      "publisher": "Loudoun County",
      "url": "https://www.loudoun.gov/6405/Noise-Air-Quality-Concerns",
      "pinpoint": "Data Centers: Noise & Air Quality Concerns; noise subsection",
      "checked": "2026-10-28",
      "review": "Official summary checked; controlling text pending",
      "legalStatus": "Not represented as a verified instrument",
      "next": "Use the linked ordinance record’s follow-up to retrieve current clean codification and confirm amendment history; do not treat this summary as the controlling standard."
    },
    {
      "id": "ohio",
      "state": "Ohio",
      "jurisdiction": "Ohio Power Company service area",
      "authority": "Utility",
      "title": "Ohio Power Company data-center tariff",
      "pillars": [
        "power",
        "finance"
      ],
      "summary": "Ohio Power Company reports PUCO adopted the 2024 Data Center Tariff settlement in July 2025 and its compliance tariff took effect July 23, 2025. Exact current tariff obligations and appellate status remain under review.",
      "publisher": "Ohio Power Company / AEP Ohio",
      "url": "https://www.aepohio.com/company/about/rates/data-center-tariff/",
      "pinpoint": "Data Center Tariff; tariff effective date and study process",
      "checked": "2026-10-28",
      "review": "Official utility summary checked; current text/status pending",
      "legalStatus": "Not represented as a verified instrument",
      "next": "Retrieve approved Schedule DCT and order text; verify tariff conditions and current court docket. Scope is Ohio Power's service territory, not the State of Ohio."
    },
    {
      "id": "minnesota",
      "state": "Minnesota",
      "jurisdiction": "Minnesota",
      "authority": "State",
      "title": "Environmental review and pollution permits",
      "pillars": [
        "water",
        "air",
        "transparency"
      ],
      "summary": "MPCA describes its environmental-review role and air, water, and stormwater permitting. It identifies cooling-water and wastewater discharges, generators, and fuel storage as relevant permitting subjects.",
      "publisher": "Minnesota Pollution Control Agency",
      "url": "https://www.pca.state.mn.us/data-centers",
      "pinpoint": "The MPCA’s role; Environmental review; Permitting",
      "checked": "2026-10-28",
      "review": "Official summary checked",
      "legalStatus": "Project-specific applicability not yet verified",
      "next": "Identify controlling statutes and rules, permit triggers, and the appropriate water-supply authority."
    },
    {
      "id": "epa",
      "state": "Federal",
      "jurisdiction": "United States",
      "authority": "Federal",
      "title": "Air standards and permitting for power equipment",
      "pillars": [
        "air"
      ],
      "summary": "EPA identifies emissions standards for stationary engines and turbines and explains that state and local air agencies issue most data center air permits under approved programs. EPA also clarifies how specified 2026 emergency orders are treated for cited engine rules.",
      "publisher": "U.S. Environmental Protection Agency",
      "url": "https://www.epa.gov/stationary-sources-air-pollution/clean-air-act-resources-data-centers",
      "pinpoint": "Clean Air Act Resources for Data Centers; Spring and Summer 2026 DOE 202(c) Emergency Orders",
      "checked": "2026-10-28",
      "review": "Official summary checked",
      "legalStatus": "Equipment-specific applicability not yet verified",
      "next": "Verify equipment type, source classification, construction date, permit conditions, and the relevant engine/turbine subpart."
    },
    {
      "id": "fairfax-text",
      "state": "Virginia",
      "jurisdiction": "Fairfax County",
      "authority": "Local",
      "title": "Adopted Fairfax County data-center zoning amendment text",
      "pillars": [
        "noise",
        "land"
      ],
      "summary": "Controlling amendment text including § 4102.6.A standards, noise-study submission requirements, and transition provisions.",
      "publisher": "Fairfax County Board of Supervisors",
      "url": "https://www.fairfaxcounty.gov/planning-development/sites/planning-development/files/Assets/Documents/zoning%20ordinance/adopted%20amendments/ZO_112_1-2024-9.pdf",
      "pinpoint": "pp. 0–4; §§ 4102.6.A(1), (4), (6), 8101.2.E(12), 8101.3.D(8), Appendix 1 § 2.B",
      "checked": "2026-10-28",
      "review": "Official adopted legal text",
      "legalStatus": "Effective per county amendment history",
      "next": "Check Chapter 108.1 noise code."
    },
    {
      "id": "fairfax-history",
      "state": "Virginia",
      "jurisdiction": "Fairfax County",
      "authority": "Local",
      "title": "Fairfax County adopted amendment history",
      "pillars": [
        "noise",
        "land"
      ],
      "summary": "Official history confirms the data-center amendment's adoption and effective dates and lists later adopted zoning amendments.",
      "publisher": "Fairfax County Department of Planning and Development",
      "url": "https://www.fairfaxcounty.gov/planning-development/zoning-ordinance/amendments/recently-adopted",
      "pinpoint": "112.1-2024-9 and 112.2-2024-8 – Data Centers",
      "checked": "2026-10-28",
      "review": "Official amendment history checked",
      "legalStatus": "Adopted 2024-09-10; effective 2024-09-11",
      "next": "Recheck this page during each update."
    },
    {
      "id": "virginia-code",
      "state": "Virginia",
      "jurisdiction": "Commonwealth of Virginia",
      "authority": "State",
      "title": "Virginia Code § 15.2-2209.5",
      "pillars": [
        "noise",
        "water",
        "power",
        "transparency",
        "land"
      ],
      "summary": "Current codified statute governing site assessments for new high-energy-use facilities in specified land-use proceedings.",
      "publisher": "Virginia General Assembly / Legislative Information System",
      "url": "https://law.lis.virginia.gov/vacode/title15.2/chapter22/section15.2-2209.5/",
      "pinpoint": "Subsections A–G",
      "checked": "2026-10-28",
      "review": "Current codified statute checked",
      "legalStatus": "Codified as effective; effective date not independently verified",
      "next": "Read 2026 Acts chapters 567 and 568 for effective date and legislative history."
    },
    {
      "id": "ecfr-63-6640",
      "state": "Federal",
      "jurisdiction": "United States",
      "authority": "Federal",
      "title": "40 C.F.R. § 63.6640",
      "pillars": [
        "air",
        "power"
      ],
      "summary": "Current eCFR text on compliance demonstrations and emergency stationary RICE operating limits.",
      "publisher": "Office of the Federal Register / EPA",
      "url": "https://www.ecfr.gov/current/title-40/chapter-I/subchapter-C/part-63/subpart-ZZZZ/section-63.6640",
      "pinpoint": "§ 63.6640(a)–(f); particularly (f)(1)–(4)",
      "checked": "2026-10-28",
      "review": "Current eCFR provision checked",
      "legalStatus": "Effective as displayed through 2026-10-26; applicability is equipment-specific",
      "next": "Check each engine's design, source status, and permit."
    },
    {
      "id": "mn-laws-2025-c12",
      "state": "Minnesota",
      "jurisdiction": "Minnesota",
      "authority": "State",
      "title": "Minnesota Laws 2025, First Special Session, chapter 12",
      "publisher": "Minnesota Office of the Revisor of Statutes",
      "url": "https://www.revisor.mn.gov/laws/2025/1/12/",
      "pinpoint": "Sections 3–4, 9, 16–17; signed June 14, 2025",
      "summary": "Data-center-specific water, very-large-customer, annual-fee, and sales-tax provisions; the chapter separately states the effective date for each section.",
      "pillars": [],
      "checked": "2026-10-28",
      "review": "Official legal text checked",
      "legalStatus": "Current official source reviewed",
      "next": "Recheck current codification and amendments on refresh."
    },
    {
      "id": "mn-water-preapp",
      "state": "Minnesota",
      "jurisdiction": "Minnesota",
      "authority": "State",
      "title": "Minn. Stat. § 103G.265, subd. 5",
      "publisher": "Minnesota Office of the Revisor of Statutes",
      "url": "https://www.revisor.mn.gov/statutes/2025/cite/103G.265",
      "pinpoint": "Subd. 5(a)–(g); 2025 Minn. Laws 1st Spec. Sess., ch. 12, § 3",
      "summary": "Preapplication evaluation for certain data-center water appropriation projects above the annual consumptive-use threshold; agency communications/data under this subdivision are nonpublic.",
      "pillars": [
        "water",
        "transparency"
      ],
      "checked": "2026-10-28",
      "review": "Official legal text checked",
      "legalStatus": "Current official source reviewed",
      "next": "Recheck current codification and amendments on refresh."
    },
    {
      "id": "mn-water-permit",
      "state": "Minnesota",
      "jurisdiction": "Minnesota",
      "authority": "State",
      "title": "Minn. Stat. § 103G.271, subd. 5b",
      "publisher": "Minnesota Office of the Revisor of Statutes",
      "url": "https://www.revisor.mn.gov/statutes/2025/cite/103G.271",
      "pinpoint": "Subd. 5b(a)–(b); 2025 Minn. Laws 1st Spec. Sess., ch. 12, § 4",
      "summary": "Water-conservation and watershed-health considerations for new or modified permits serving data centers above 100 million gallons per year.",
      "pillars": [
        "water",
        "transparency"
      ],
      "checked": "2026-10-28",
      "review": "Official legal text checked",
      "legalStatus": "Current official source reviewed",
      "next": "Recheck current codification and amendments on refresh."
    },
    {
      "id": "mn-large-customer",
      "state": "Minnesota",
      "jurisdiction": "Minnesota",
      "authority": "State",
      "title": "Minn. Stat. § 216B.1622",
      "publisher": "Minnesota Office of the Revisor of Statutes",
      "url": "https://www.revisor.mn.gov/statutes/2025/cite/216B.1622",
      "pinpoint": "Subds. 1–3; 2025 Minn. Laws 1st Spec. Sess., ch. 12, § 9",
      "summary": "Requires PUC definition of a very-large-customer class by December 15, 2026 and lays out considerations for tariffs/service agreements, including cost assignment, clean-energy benchmarks, and stranded-cost protections.",
      "pillars": [
        "power",
        "finance"
      ],
      "checked": "2026-10-28",
      "review": "Official legal text checked",
      "legalStatus": "Current official source reviewed",
      "next": "Recheck current codification and amendments on refresh."
    },
    {
      "id": "mn-fee",
      "state": "Minnesota",
      "jurisdiction": "Minnesota",
      "authority": "State",
      "title": "Minn. Stat. § 216B.72",
      "publisher": "Minnesota Office of the Revisor of Statutes",
      "url": "https://www.revisor.mn.gov/statutes/2025/cite/216B.72",
      "pinpoint": "Subds. (a)–(c); 2025 Minn. Laws 1st Spec. Sess., ch. 12, § 16",
      "summary": "Annual fee for qualified large-scale data centers based on forecast peak demand arranged by the utility; fee data are nonpublic.",
      "pillars": [
        "power",
        "finance"
      ],
      "checked": "2026-10-28",
      "review": "Official legal text checked",
      "legalStatus": "Current official source reviewed",
      "next": "Recheck current codification and amendments on refresh."
    },
    {
      "id": "mn-tax-exemption",
      "state": "Minnesota",
      "jurisdiction": "Minnesota",
      "authority": "State",
      "title": "Minn. Stat. § 297A.68, subd. 42",
      "publisher": "Minnesota Office of the Revisor of Statutes",
      "url": "https://www.revisor.mn.gov/statutes/2025/cite/297A.68",
      "pinpoint": "Subd. 42(a), (e)–(n); 2025 Minn. Laws 1st Spec. Sess., ch. 12, § 17; ch. 13, art. 3, § 4",
      "summary": "Sales/use tax exemption for qualifying data-center IT equipment and software; large-scale facilities have additional labor and green-building conditions, with recapture for failure to meet the green-building deadline.",
      "pillars": [
        "finance",
        "power"
      ],
      "checked": "2026-10-28",
      "review": "Official legal text checked",
      "legalStatus": "Current official source reviewed",
      "next": "Recheck current codification and amendments on refresh."
    },
    {
      "id": "pa-data-center-tax",
      "state": "Pennsylvania",
      "jurisdiction": "Pennsylvania",
      "authority": "State",
      "title": "61 P.S. § 2931-D",
      "publisher": "Pennsylvania General Assembly",
      "url": "https://www.legis.state.pa.us/WU01/LI/LI/US/HTM/1971/0/0002.029D000.031.000..HTM",
      "pinpoint": "§ 2931-D(a)–(d); as amended by 2024 Act 56, § 30(12)",
      "summary": "Sales/use tax exemption for equipment purchased for installation in a certified computer data center, subject to exclusions and time-limited owner/tenant qualification periods.",
      "pillars": [
        "finance",
        "power"
      ],
      "checked": "2026-10-28",
      "review": "Official legal text checked",
      "legalStatus": "Current official source reviewed",
      "next": "Recheck current codification and amendments on refresh."
    },
    {
      "id": "ecfr-ci-4211",
      "state": "Federal",
      "jurisdiction": "United States",
      "authority": "Federal",
      "title": "40 C.F.R. § 60.4211",
      "publisher": "Office of the Federal Register / U.S. EPA",
      "url": "https://www.ecfr.gov/current/title-40/chapter-I/subchapter-C/part-60/subpart-IIII/section-60.4211",
      "pinpoint": "§ 60.4211(a), (f)–(g), current eCFR displayed through 2026-10-26",
      "summary": "Selected compliance provisions for stationary compression-ignition engines, including conditional emergency-engine hours and restrictions on non-emergency dispatch.",
      "pillars": [
        "air",
        "power"
      ],
      "checked": "2026-10-28",
      "review": "Official legal text checked",
      "legalStatus": "Current official source reviewed",
      "next": "Recheck current codification and amendments on refresh."
    },
    {
      "id": "utah-hb76-enrolled",
      "state": "Utah",
      "jurisdiction": "Utah",
      "authority": "State",
      "title": "HB 76 — Data Center Water Transparency Amendments (enrolled act)",
      "publisher": "Utah Legislature",
      "url": "https://le.utah.gov/~2026/bills/hbillenr/HB0076.pdf",
      "pinpoint": "Utah Code § 73-5-8.3(1)–(6), enrolled HB 76 §§ 2–3, pp. 3–7",
      "summary": "Defines covered large data centers and requires preconstruction water-provider notice and projected-use reporting, annual withdrawal/conservation reporting, public disclosure with specified proprietary protections, and enforcement.",
      "pillars": [
        "water",
        "land",
        "transparency"
      ],
      "checked": "2026-10-28",
      "review": "Official enrolled law checked",
      "legalStatus": "Effective May 6, 2026; covered new-facility duties have July 1, 2026 applicability terms",
      "next": "Check implementing rules and first public reports; research separate water-right and wastewater permit conditions.",
      "instrumentId": "utah-data-center-water-transparency-2026"
    },
    {
      "id": "virginia-gen-set-air-code",
      "state": "Virginia",
      "jurisdiction": "Virginia",
      "authority": "State",
      "title": "Va. Code § 10.1-1322.6 — data-center engine-generator emission limits",
      "publisher": "Virginia Legislative Information System",
      "url": "https://law.lis.virginia.gov/vacode/title10.1/chapter13/section10.1-1322.6/",
      "pinpoint": "Subsections A–C; Tier 4 equivalent definition and permit application trigger",
      "summary": "Air permits for covered data-center applications submitted on/after July 1, 2026 must set each engine-generator's emissions limit at or below Tier 4-equivalent emissions, with stricter standards preserved.",
      "pillars": [
        "air",
        "climate"
      ],
      "checked": "2026-10-28",
      "review": "Official codified text checked",
      "legalStatus": "Effective July 1, 2026",
      "next": "Check current DEQ implementation rules and facility-specific permit conditions.",
      "instrumentId": "virginia-data-center-gen-set-air-2026"
    },
    {
      "id": "virginia-hb507-history",
      "state": "Virginia",
      "jurisdiction": "Virginia",
      "authority": "State",
      "title": "HB 507 (2026), official bill history and Chapter 397 effective date",
      "publisher": "Virginia Legislative Information System",
      "url": "https://lis.virginia.gov/bill-details/20261/HB507",
      "pinpoint": "History: Approved by Governor Apr. 8, 2026; Chapter 397; effective July 1, 2026",
      "summary": "Official bill history confirms enactment as Chapter 397 and July 1, 2026 effective date.",
      "pillars": [
        "air"
      ],
      "checked": "2026-10-28",
      "review": "Official legislative history checked",
      "legalStatus": "Enacted",
      "next": "Use current codified text for the controlling rule.",
      "instrumentId": "virginia-data-center-gen-set-air-2026"
    },
    {
      "id": "ohio-power-schedule-dct-current",
      "state": "Ohio",
      "jurisdiction": "Ohio Power Company service territory",
      "authority": "Utility",
      "title": "Ohio Power Company current tariff book — Schedule DCT",
      "publisher": "Ohio Power Company / AEP Ohio",
      "url": "https://www.aepohio.com/lib/docs/ratesandtariffs/Ohio/November_2026_Ohio_Power_Tariff_Book.pdf",
      "pinpoint": "P.U.C.O. No. 22, Schedule DCT, sheets 223-2–223-5; issued/effective Aug. 28, 2026",
      "summary": "Current official tariff text sets applicability above 25 MW and separate minimum demand billing rules for existing and new data-center loads.",
      "pillars": [
        "power",
        "transparency"
      ],
      "checked": "2026-10-28",
      "review": "Official approved tariff sheets checked",
      "legalStatus": "Effective; Ohio Power territory only; challenged status requires docket refresh",
      "next": "Verify Ohio Supreme Court case 2025-1458 and current PUCO order status; do not generalize to statewide utility service.",
      "instrumentId": "ohio-power-schedule-dct-2026"
    },
    {
      "id": "ohio-puco-2026-sso",
      "state": "Ohio",
      "jurisdiction": "Ohio Power Company service territory",
      "authority": "State utility commission",
      "title": "PUCO Aug. 5, 2026 data-center Standard Service Offer safeguards",
      "publisher": "Public Utilities Commission of Ohio",
      "url": "https://content.govdelivery.com/accounts/OHPUC/bulletins/423b896",
      "pinpoint": "Official Aug. 5, 2026 announcement; PUCO Case 26-113-EL-ATA",
      "summary": "PUCO described 180-day customer notice, separate procurement/spot purchases, and assignment of related costs to the data-center customer; current tariff sheets cite the order.",
      "pillars": [
        "power",
        "transparency"
      ],
      "checked": "2026-10-28",
      "review": "Official agency summary checked; underlying order text not separately retrieved",
      "legalStatus": "Order issued; appeal/stay status unresolved in this batch",
      "next": "Retrieve order text and check subsequent docket and court status.",
      "instrumentId": "ohio-power-schedule-dct-2026"
    },
    {
      "id": "oregon-hb3546-enrolled",
      "state": "Oregon",
      "jurisdiction": "Oregon",
      "authority": "State",
      "title": "Oregon HB 3546 (2025), enrolled act",
      "publisher": "Oregon Legislative Assembly",
      "url": "https://olis.oregonlegislature.gov/liz/2025R1/Downloads/MeasureDocument/HB3546",
      "pinpoint": "2025 Or. Laws ch. 323, §§ 2–9; enrolled HB 3546, pp. 1–3",
      "summary": "Creates separate utility classification/tariff principles and requires long-term contracts and minimum payments for covered large energy use facilities.",
      "pillars": [
        "power",
        "transparency",
        "climate"
      ],
      "checked": "2026-10-28",
      "review": "Official enrolled law checked",
      "legalStatus": "Effective on passage, June 16, 2025",
      "next": "Check PUC implementation Order 26-154, tariff sheets, reconsideration order, and judicial review.",
      "instrumentId": "oregon-large-energy-use-facilities-hb3546-2025"
    },
    {
      "id": "oregon-puc-um2377-docket",
      "state": "Oregon",
      "jurisdiction": "Oregon / Portland General Electric implementation proceeding",
      "authority": "State utility commission",
      "title": "Oregon PUC eDockets UM 2377 docket history",
      "publisher": "Oregon Public Utility Commission",
      "url": "https://apps.puc.state.or.us/edockets/DocketNoLayout.asp?DocketID=24470",
      "pinpoint": "Orders 26-154 (May 7), 26-239 (July 10), 26-309 (Aug. 31), compliance advice filing (Sept. 15), appeal filing (Sept. 10, 2026)",
      "summary": "Official docket lists Schedule 96 adoption, later reconsideration, compliance filings, and a petition for judicial review. Order PDF was too large to retrieve in this batch.",
      "pillars": [
        "power",
        "transparency"
      ],
      "checked": "2026-10-28",
      "review": "Official docket summary checked; underlying order not retrieved",
      "legalStatus": "Implementation under procedural review; legal effect and final status require follow-up",
      "next": "Read orders, Schedule 96, and judicial review record before recording implementation terms.",
      "instrumentId": "oregon-large-energy-use-facilities-hb3546-2025"
    },
    {
      "id": "loudoun-chapter7-official-comparison",
      "state": "Virginia",
      "jurisdiction": "Loudoun County",
      "authority": "Local",
      "title": "Loudoun County Zoning Ordinance Chapter 7 official comparison PDF",
      "publisher": "Loudoun County Government",
      "url": "https://sheriff.loudoun.gov/DocumentCenter/View/178347/Ch-7-Dev-Standards-Compare",
      "pinpoint": "§ 7.05.03(A)–(G), PDF pp. 56–57",
      "summary": "County-hosted comparison text specifies A-weighted limits, measurement procedures, exceptions, use-specific noise rules, and pre/post-construction study and mitigation standards.",
      "pillars": [
        "noise",
        "land",
        "transparency"
      ],
      "checked": "2026-10-28",
      "review": "Official County-hosted comparison text checked; current codification needs review",
      "legalStatus": "Effective ordinance section represented from official comparison copy; amendment version caveat",
      "next": "Retrieve current clean ordinance and confirm all later amendments and data-center-specific Chapter 4 cross-reference.",
      "instrumentId": "loudoun-zoning-noise-2023"
    },
    {
      "id": "loudoun-chapter4-current-url",
      "state": "Virginia",
      "jurisdiction": "Loudoun County",
      "authority": "Local",
      "title": "Loudoun County Zoning Ordinance Chapter 4 current PDF endpoint",
      "publisher": "Loudoun County Government",
      "url": "https://www.loudoun.gov/DocumentCenter/View/180046/Chapter-4-Use-Specific-Standards",
      "pinpoint": "§ 4.06.02 data-center use-specific standards; endpoint returned 404 on 2026-10-28",
      "summary": "Official County source endpoint is retained for follow-up; clean current PDF could not be retrieved in this batch. Search-indexed official text indicates data-center noise-study and acoustical-barrier provisions, not separately validated against a retrieved current file.",
      "pillars": [
        "noise",
        "land"
      ],
      "checked": "2026-10-28",
      "review": "Official source unavailable; not evidence that the rule is absent",
      "legalStatus": "Unresolved current text",
      "next": "Retrieve from County ordinance interface or obtain a current official PDF through authorized County channel; verify against clean codification.",
      "instrumentId": "loudoun-zoning-noise-2023"
    },
    {
      "id": "loudoun-zoning-scope",
      "state": "Virginia",
      "jurisdiction": "Loudoun County",
      "authority": "Local",
      "title": "Loudoun County official zoning ordinance scope and exceptions",
      "publisher": "Loudoun County Government",
      "url": "https://www.sheriff.loudoun.gov/1755/Zoning-Ordinance",
      "pinpoint": "Ordinance scope/exception notice; adopted and effective Dec. 13, 2023",
      "summary": "County page identifies the 2023 ordinance effective date and exceptions for incorporated towns, Route 28 Tax District 1972 zoning, and grandfathered applications.",
      "pillars": [
        "land"
      ],
      "checked": "2026-10-28",
      "review": "Official agency page checked",
      "legalStatus": "Official explanatory page; zoning text controls",
      "next": "Consult official ordinance and amendment history for site-specific applicability.",
      "instrumentId": "loudoun-zoning-noise-2023"
    },
    {
      "id": "ab1577-ca",
      "state": "California",
      "jurisdiction": "California",
      "authority": "State",
      "title": "AB 1577, Data centers: energy and local-permit information",
      "pillars": [
        "transparency"
      ],
      "summary": "Requires the California Energy Commission to collect specified facility information and requires local permit applicants to disclose certain energy and sound information.",
      "publisher": "California Legislature",
      "url": "https://leginfo.legislature.ca.gov/faces/billNavClient.xhtml?bill_id=202520260AB1577",
      "pinpoint": "Chaptered act and corresponding Government Code, Public Resources Code, Water Code, or Public Utilities Code provisions; see linked instrument pinpoint.",
      "checked": "2026-10-28",
      "review": "Official bill/chapter status verified; chaptered act text reviewed",
      "legalStatus": "Enacted chapter; text reviewed via accessible chaptered copy; official Legislature bill page linked",
      "next": "Confirm chaptered-text effective date, applicability details, subsequent amendments, and implementing agency action.",
      "instrumentId": "ca-ab1577-2026"
    },
    {
      "id": "ab2383-ca",
      "state": "California",
      "jurisdiction": "California",
      "authority": "State",
      "title": "AB 2383, Data centers: electric service tariffs",
      "pillars": [
        "power"
      ],
      "summary": "Directs electrical corporations to file transmission and distribution tariffs for participating data-center customers and establishes related requirements for community choice aggregators and energy service providers.",
      "publisher": "California Legislature",
      "url": "https://leginfo.legislature.ca.gov/faces/billNavClient.xhtml?bill_id=202520260AB2383",
      "pinpoint": "Chaptered act and corresponding Government Code, Public Resources Code, Water Code, or Public Utilities Code provisions; see linked instrument pinpoint.",
      "checked": "2026-10-28",
      "review": "Official bill/chapter status verified; chaptered act text reviewed",
      "legalStatus": "Enacted chapter; text reviewed via accessible chaptered copy; official Legislature bill page linked",
      "next": "Confirm chaptered-text effective date, applicability details, subsequent amendments, and implementing agency action.",
      "instrumentId": "ca-ab2383-2026"
    },
    {
      "id": "ab2469-ca",
      "state": "California",
      "jurisdiction": "California",
      "authority": "State",
      "title": "AB 2469, Data centers: water-supply assessment",
      "pillars": [
        "water",
        "land"
      ],
      "summary": "For covered new data centers and expansions, bars a local government from approving a permit or entitlement increasing peak water use unless a water-supply assessment, projected-use/efficiency information, and workforce disclosure are provided; a water-scarcity plan is required beginning in 2028.",
      "publisher": "California Legislature",
      "url": "https://leginfo.legislature.ca.gov/faces/billNavClient.xhtml?bill_id=202520260AB2469",
      "pinpoint": "Chaptered act and corresponding Government Code, Public Resources Code, Water Code, or Public Utilities Code provisions; see linked instrument pinpoint.",
      "checked": "2026-10-28",
      "review": "Official bill/chapter status verified; chaptered act text reviewed",
      "legalStatus": "Enacted chapter; text reviewed via accessible chaptered copy; official Legislature bill page linked",
      "next": "Confirm chaptered-text effective date, applicability details, subsequent amendments, and implementing agency action.",
      "instrumentId": "ca-ab2469-2026"
    },
    {
      "id": "ab2619-ca",
      "state": "California",
      "jurisdiction": "California",
      "authority": "State",
      "title": "AB 2619, Data centers: water-use disclosure",
      "pillars": [
        "water",
        "transparency"
      ],
      "summary": "Requires covered data centers to provide water-use information to water suppliers and local licensing authorities, including estimates at application and actual annual use at renewal, with cooling-system information.",
      "publisher": "California Legislature",
      "url": "https://leginfo.legislature.ca.gov/faces/billNavClient.xhtml?bill_id=202520260AB2619",
      "pinpoint": "Chaptered act and corresponding Government Code, Public Resources Code, Water Code, or Public Utilities Code provisions; see linked instrument pinpoint.",
      "checked": "2026-10-28",
      "review": "Official bill/chapter status verified; chaptered act text reviewed",
      "legalStatus": "Enacted chapter; text reviewed via accessible chaptered copy; official Legislature bill page linked",
      "next": "Confirm chaptered-text effective date, applicability details, subsequent amendments, and implementing agency action.",
      "instrumentId": "ca-ab2619-2026"
    },
    {
      "id": "sb886-ca",
      "state": "California",
      "jurisdiction": "California",
      "authority": "State",
      "title": "SB 886, Data centers: electrical service and cost allocation",
      "pillars": [
        "power",
        "finance",
        "transparency"
      ],
      "summary": "Requires CPUC rules and tariffs addressing service for specified large data-center customers, including protections against shifting costs or stranded investments to other customers and customer-specific commitments.",
      "publisher": "California Legislature",
      "url": "https://leginfo.legislature.ca.gov/faces/billNavClient.xhtml?bill_id=202520260SB886",
      "pinpoint": "Chaptered act and corresponding Government Code, Public Resources Code, Water Code, or Public Utilities Code provisions; see linked instrument pinpoint.",
      "checked": "2026-10-28",
      "review": "Official bill/chapter status verified; chaptered act text reviewed",
      "legalStatus": "Enacted chapter; text reviewed via accessible chaptered copy; official Legislature bill page linked",
      "next": "Confirm chaptered-text effective date, applicability details, subsequent amendments, and implementing agency action.",
      "instrumentId": "ca-sb886-2026"
    },
    {
      "id": "sb887-ca",
      "state": "California",
      "jurisdiction": "California",
      "authority": "State",
      "title": "SB 887, Data centers: environmental review",
      "pillars": [
        "land",
        "transparency"
      ],
      "summary": "Chapter 439 adds data-center CEQA definitions and entitlement coverage, bars categorical exemptions subject to listed exclusions, and adds a conditional Governor certification pathway with strict electricity, grid-cost, water, and community-benefit criteria.",
      "publisher": "California Legislature",
      "url": "https://leginfo.legislature.ca.gov/faces/billNavClient.xhtml?bill_id=202520260SB887",
      "pinpoint": "Cal. Pub. Res. Code §§ 21061.6, 21080.08, 21084(f), 21180(b)(5), 21183.6; 2026 Cal. Stats. ch. 439, §§ 2–6. Official bill page confirms chapter status; chaptered text read from mirror because official endpoint returned 403.",
      "checked": "2026-10-28",
      "review": "Chaptered text reviewed from accessible mirror; chapter status cross-checked on official California Legislature bill page",
      "legalStatus": "Enacted as 2026 Cal. Stats. ch. 439; full official chaptered text recheck queued",
      "next": "Recheck full enrolled/chaptered text on the official California source when accessible; track implementing uniform standards and project certifications. ",
      "instrumentId": "ca-sb887-2026"
    },
    {
      "id": "sb1168-ca",
      "state": "California",
      "jurisdiction": "California",
      "authority": "State",
      "title": "SB 1168, Data centers: electrical service rate assessment",
      "pillars": [
        "power",
        "finance"
      ],
      "summary": "Directs the CPUC to assess rate opportunities intended to ensure large data-center customers bear a reasonable share of transmission/distribution and procurement costs and to alleviate residential cost pressure.",
      "publisher": "California Legislature",
      "url": "https://leginfo.legislature.ca.gov/faces/billNavClient.xhtml?bill_id=202520260SB1168",
      "pinpoint": "Cal. SB 1168, ch. 440, § 1",
      "checked": "2026-10-28",
      "review": "Source-verified legal instrument; chapter text reviewed",
      "legalStatus": "Official chaptered act text checked",
      "next": "Recheck implementing CPUC assessment and any resulting tariff proceedings.",
      "instrumentId": "ca-sb1168-2026"
    },
    {
      "id": "fl-statute-373-262-2026",
      "state": "Florida",
      "jurisdiction": "Florida",
      "authority": "State",
      "title": "Large-scale data centers: water allocation safeguards and conservation plans",
      "pillars": [
        "water",
        "land",
        "transparency"
      ],
      "summary": "Limits water allocations for covered large-scale data centers where statutory resource-harm or land-use conditions apply; requires conservation plans and public hearings for specified high-volume applications.",
      "publisher": "Florida Senate / Florida Statutes",
      "url": "https://www.flsenate.gov/Laws/Statutes/2026/373.262",
      "pinpoint": "Fla. Stat. § 373.262(1)–(5); 2026 ch. 2026-65, § 5",
      "checked": "2026-10-28",
      "review": "Source-verified legal instrument",
      "legalStatus": "Official legal text checked",
      "next": "Recheck amendments and implementation on the next refresh.",
      "instrumentId": "fl-large-data-center-water-2026"
    },
    {
      "id": "pa-eo-2026-05-bulletin",
      "state": "Pennsylvania",
      "jurisdiction": "Pennsylvania",
      "authority": "State",
      "title": "Executive Order 2026-05: responsible data-center development",
      "pillars": [
        "power",
        "water",
        "land",
        "transparency",
        "finance"
      ],
      "summary": "Effective executive order requires public agency procedures for qualifying >25 MW projects, local/water-permit sequencing, no NDAs with covered agencies, a DEP project map and annual energy/water reporting beginning July 1, 2027. It directs special-counsel advocacy for future PUC curtailment and cost rules; DEP environmental rule review; and DCED local best practices.",
      "publisher": "Pennsylvania Bulletin / Governor",
      "url": "https://www.pacodeandbulletin.gov/secure/pabulletin/data/vol56/56-36/1274.html",
      "pinpoint": "56 Pa.B. 5898 et seq.; 4 Pa. Code §§ 7.1082(a)–(e), 7.1083(a)–(c), 7.1084(a)–(c), 7.1085(a)–(c), 7.1087, 7.1089",
      "checked": "2026-10-28",
      "review": "Official Pennsylvania Bulletin order checked",
      "legalStatus": "Effective immediately under § 7.1089",
      "next": "Track implementing DEP procedures, PUC proceedings, reporting, and any amendment or rescission.",
      "instrumentId": "pa-data-center-executive-order-2026-05"
    },
    {
      "id": "sd-sb135-enrolled-2026",
      "state": "South Dakota",
      "jurisdiction": "South Dakota",
      "authority": "State",
      "title": "SB 135: large-load customer terms and data-center water reporting",
      "pillars": [
        "power",
        "water",
        "transparency",
        "land"
      ],
      "summary": "Enrolled SB 135 defines a data center at 10 MW and addresses provider terms, cost attribution, local authority, water-provider compatibility, and public water-use reporting.",
      "publisher": "South Dakota Legislature",
      "url": "https://mylrc.sdlegislature.gov/api/Documents/306610.html",
      "pinpoint": "2026 S.D. SB 135, enrolled §§ 2–6",
      "checked": "2026-10-28",
      "review": "Enrolled act text verified",
      "legalStatus": "Enacted; implementation details remain",
      "next": "Recheck amendments and implementation on the next refresh.",
      "instrumentId": "sd-large-load-and-water-reporting-sb135-2026"
    },
    {
      "id": "ne-lb1010-slip-law",
      "state": "Nebraska",
      "jurisdiction": "Nebraska",
      "authority": "State",
      "title": "LB 1010: Large Load Customer Regulation Act and data-center provisions",
      "pillars": [
        "power",
        "finance",
        "transparency"
      ],
      "summary": "Slip law adds large-load customer provisions for public-power suppliers, including disclosures about competing interconnection requests and backup generation, study fees, site control, and cost commitments.",
      "publisher": "Nebraska Legislature",
      "url": "https://www.nebraskalegislature.gov/FloorDocs/109/PDF/Slip/LB1010.pdf",
      "pinpoint": "2026 Neb. LB 1010, enrolled/slip law; Neb. Rev. Stat. §§ 70-1506 et seq.",
      "checked": "2026-10-28",
      "review": "Source-verified legal instrument",
      "legalStatus": "Official slip law checked; implementation effective dates require clause-level review",
      "next": "Verify operative dates by section and Public Power District implementation rules.",
      "instrumentId": "ne-large-load-customer-act-lb1010-2026"
    },
    {
      "id": "nv-eo-2026-005",
      "state": "Nevada",
      "jurisdiction": "Nevada",
      "authority": "State",
      "title": "Executive Order 2026-005: data-center tax abatements and community commitments",
      "pillars": [
        "water",
        "power",
        "air",
        "finance",
        "transparency",
        "land"
      ],
      "summary": "Sets additional Community Support Commitment conditions for specified pending applications for state sales/use tax abatements, covering water, ratepayers, reliability, siting, workforce, community benefit, and transparency.",
      "publisher": "Office of the Governor, State of Nevada",
      "url": "https://www.gov.nv.gov/executive-actions/executive-orders/2026-executive-orders/eo-2026-005",
      "pinpoint": "Executive Order 2026-005, §§ 1–8; signed September 17, 2026",
      "checked": "2026-10-28",
      "review": "Source-verified legal instrument",
      "legalStatus": "Official legal text checked",
      "next": "Recheck amendments and implementation on the next refresh.",
      "instrumentId": "nv-data-center-tax-abatement-eo-2026-005"
    },
    {
      "id": "ok-hb2992-enrolled-2026",
      "state": "Oklahoma",
      "jurisdiction": "Oklahoma",
      "authority": "State",
      "title": "HB 2992, enrolled final version",
      "pillars": [
        "power",
        "finance",
        "transparency",
        "land"
      ],
      "summary": "Enrolled text of the Data Center Customer Ratepayer Protection Act of 2026.",
      "publisher": "Oklahoma Legislature",
      "url": "https://www.oklegislature.gov/cf_pdf/2025-26%20ENR/hB/HB2992%20ENR.PDF",
      "pinpoint": "2026 Okla. H.B. 2992, §§ 2–9, pp. 2–5",
      "checked": "2026-10-28",
      "review": "Source-verified controlling text",
      "legalStatus": "Enacted; approved 2026-05-11; effective-date clauses require careful reading",
      "next": "Confirm codification and reconcile § 8 July 1 effective date with § 9 emergency clause against official session law/codification.",
      "instrumentId": "ok-hb2992-2026"
    },
    {
      "id": "ok-hb2992-history-2026",
      "state": "Oklahoma",
      "jurisdiction": "Oklahoma",
      "authority": "State",
      "title": "HB 2992 bill history and version record",
      "pillars": [
        "power",
        "finance",
        "transparency",
        "land"
      ],
      "summary": "Official bill history records gubernatorial approval May 11, 2026 and identifies the enrolled final version.",
      "publisher": "Oklahoma Legislature",
      "url": "https://www.oklegislature.gov/BillInfo.aspx?Bill=HB+2992&Session=2600",
      "pinpoint": "History; Versions (Enrolled final version, May 5, 2026)",
      "checked": "2026-10-28",
      "review": "Official status/history",
      "legalStatus": "Approved by Governor 2026-05-11",
      "next": "On refresh, compare enrolled text to codified 17 O.S. §§ 900–906 and any OCC rules.",
      "instrumentId": "ok-hb2992-2026"
    },
    {
      "id": "ok-sb259-enrolled-2026",
      "state": "Oklahoma",
      "jurisdiction": "Oklahoma",
      "authority": "State",
      "title": "SB 259, enrolled final version",
      "pillars": [
        "water",
        "transparency"
      ],
      "summary": "Enrolled act amending groundwater waste and reporting laws, including restrictions on certain data-center cooling uses of groundwater.",
      "publisher": "Oklahoma Legislature",
      "url": "https://www.oklegislature.gov/cf_pdf/2025-26%20ENR/SB/SB259%20ENR.PDF",
      "pinpoint": "2026 Okla. S.B. 259, §§ 1–4, pp. 1–6",
      "checked": "2026-10-28",
      "review": "Source-verified controlling text",
      "legalStatus": "Enacted; approved 2026-05-20; effective 2026-11-01",
      "next": "Check Oklahoma Water Resources Board rules and confirm codified 82 O.S. §§ 1020.15 and 1020.19B after effective date.",
      "instrumentId": "ok-sb259-2026"
    },
    {
      "id": "nj-s3379-enacted-status",
      "state": "New Jersey",
      "jurisdiction": "New Jersey",
      "authority": "State",
      "title": "S3379/A4096 enactment and signing announcement",
      "pillars": [
        "water",
        "power",
        "transparency"
      ],
      "summary": "Governor confirms enactment of P.L. 2026, c.75 and describes the reporting program.",
      "publisher": "Office of the Governor of New Jersey",
      "url": "https://www.nj.gov/governor/news/2026/approved/20260827a.shtml",
      "pinpoint": "Governor announcement, Aug. 27, 2026",
      "checked": "2026-10-28",
      "review": "Official enactment/status confirmation; not operative-text verification",
      "legalStatus": "Signed 2026-08-27; P.L. 2026, c.75",
      "next": "Retrieve final chapter-law pamphlet and compare against enrolled/2R text before next substantive refresh.",
      "instrumentId": "nj-data-center-reporting-2026"
    },
    {
      "id": "nj-s3379-2r-text",
      "state": "New Jersey",
      "jurisdiction": "New Jersey",
      "authority": "State",
      "title": "S3379, Second Reprint text",
      "pillars": [
        "water",
        "power",
        "transparency"
      ],
      "summary": "Official legislative text for the final reported bill, used with the Governor’s signing confirmation to identify reporting duties and exceptions.",
      "publisher": "New Jersey Legislature",
      "url": "https://pub.njleg.state.nj.us/Bills/2026/S3500/3379_R2.HTM",
      "pinpoint": "P.L. 2026, c.75 (S3379/A4096), §§ 1(b)–(g), 2; compare chapter pamphlet on refresh",
      "checked": "2026-10-28",
      "review": "Official bill reprint; chapter-text comparison outstanding",
      "legalStatus": "Final reprint text; enacted as P.L. 2026, c.75 but chapter pamphlet not retrieved",
      "next": "Obtain official chapter-law text and confirm the enacted version word-for-word.",
      "instrumentId": "nj-data-center-reporting-2026"
    },
    {
      "id": "az-hb2467-2026-lead",
      "state": "Arizona",
      "jurisdiction": "Arizona",
      "authority": "State legislature",
      "title": "HB 2467 (2026), data-center incentives and requirements — proposal lead",
      "pillars": [
        "power",
        "water",
        "finance"
      ],
      "summary": "The introduced proposal would have imposed renewable-energy-plus-storage and a water-intensity limit on data centers, and repealed existing incentive provisions. The official 2026 session-law index does not list HB 2467 among enacted chapters; treat this only as a proposal lead, not current law.",
      "publisher": "Arizona Legislature",
      "url": "https://www.azleg.gov/legtext/57leg/2r/bills/hb2467p.htm",
      "pinpoint": "HB 2467, 57th Legislature, 2nd Regular Session (2026), proposed §§ 44-1799.101–.102; session-law index checked 2026-10-28",
      "checked": "2026-10-28",
      "review": "Official proposal text; not an effective legal requirement",
      "legalStatus": "Proposed bill; no enacted chapter identified in the 2026 session-law index",
      "next": "Retrieve official bill-history record/committee action and preserve as a historical proposal; do not map its proposed standards as operative.",
      "instrumentId": null
    },
    {
      "id": "il-sb3761-2026-lead",
      "state": "Illinois",
      "jurisdiction": "Illinois",
      "authority": "State legislature",
      "title": "SB 3761 (2026), large-load tariff and disclosure proposal",
      "pillars": [
        "power",
        "water",
        "transparency",
        "finance"
      ],
      "summary": "The introduced proposal addresses a data-center self-direct tariff program, preconstruction disclosure to the Illinois Commerce Commission, annual water-use disclosure to DNR beginning in 2027, public aggregation, penalties, and utility tariff review. Official bill status lists a May 22, 2026 re-referral to Assignments; these are proposed provisions.",
      "publisher": "Illinois General Assembly",
      "url": "https://www.ilga.gov/Legislation/BillStatus?DocNum=3761&DocTypeID=SB&GAID=18&LegId=167068&SessionID=114",
      "pinpoint": "SB 3761, 104th General Assembly, Synopsis As Introduced; Actions through May 22, 2026",
      "checked": "2026-10-28",
      "review": "Official bill status/synopsis; proposed, not law",
      "legalStatus": "Proposed; last displayed action May 22, 2026, re-referred to Assignments",
      "next": "Check current session action, amendments, committee disposition, and any successor bill before citing any proposal terms.",
      "instrumentId": null
    },
    {
      "id": "il-sb4004-2026-lead",
      "state": "Illinois",
      "jurisdiction": "Illinois",
      "authority": "State legislature",
      "title": "SB 4004 (2026), Mahomet Aquifer data-center protection proposal",
      "pillars": [
        "water",
        "transparency"
      ],
      "summary": "The introduced bill would prohibit data centers from using Mahomet Aquifer water, restrict state permits for such withdrawals, require existing facilities to transition by 2028, and limit local NDAs that conceal data-center water use. Official bill status lists a May 22, 2026 re-referral to Assignments; proposal only.",
      "publisher": "Illinois General Assembly",
      "url": "https://www.ilga.gov/Legislation/BillStatus?DocNum=4004&DocTypeID=SB&GAID=18&LegId=167531&SessionID=114",
      "pinpoint": "SB 4004, 104th General Assembly, Synopsis As Introduced; Actions through May 22, 2026",
      "checked": "2026-10-28",
      "review": "Official bill status/synopsis; proposed, not law",
      "legalStatus": "Proposed; last displayed action May 22, 2026, re-referred to Assignments",
      "next": "Check current session action and amendments; separately research operative groundwater and public-water rules.",
      "instrumentId": null
    },
    {
      "id": "il-sb3120-2026-lead",
      "state": "Illinois",
      "jurisdiction": "Illinois",
      "authority": "State legislature",
      "title": "SB 3120 (2026), water-stewardship eligibility proposal",
      "pillars": [
        "water",
        "finance",
        "transparency"
      ],
      "summary": "The introduced bill would condition qualifying data-center status for an economic-development program on providing water-stewardship strategy details and require the state’s annual data-center investment report to include those strategies. Official bill status lists a May 22, 2026 re-referral to Assignments; proposal only.",
      "publisher": "Illinois General Assembly",
      "url": "https://www.ilga.gov/ftp/legislation/104/BillStatus/HTML/10400SB3120.html",
      "pinpoint": "SB 3120, 104th General Assembly, Synopsis As Introduced; Actions through May 22, 2026",
      "checked": "2026-10-28",
      "review": "Official bill status/synopsis; proposed, not law",
      "legalStatus": "Proposed; last displayed action May 22, 2026, re-referred to Assignments",
      "next": "Check current session action and amendments; review existing qualifying-data-center incentive law separately.",
      "instrumentId": null
    },
    {
      "id": "il-sb2181-2026-lead",
      "state": "Illinois",
      "jurisdiction": "Illinois",
      "authority": "State legislature",
      "title": "SB 2181 (2026), energy and water reporting proposal",
      "pillars": [
        "power",
        "water",
        "transparency",
        "finance"
      ],
      "summary": "The introduced bill would require annual energy and water consumption reports to the Illinois Power Agency and a study of data centers’ effects on ratepayers. Official bill status lists a May 22, 2026 re-referral to Assignments; proposal only.",
      "publisher": "Illinois General Assembly",
      "url": "https://www.ilga.gov/Legislation/BillStatus?DocNum=2181&DocTypeID=SB&GAID=18&LegId=161884&SessionID=114",
      "pinpoint": "SB 2181, 104th General Assembly, Synopsis As Introduced; Actions through May 22, 2026",
      "checked": "2026-10-28",
      "review": "Official bill status/synopsis; proposed, not law",
      "legalStatus": "Proposed; last displayed action May 22, 2026, re-referred to Assignments",
      "next": "Check current session action and amendments; distinguish any enacted successor from this introduced text.",
      "instrumentId": null
    },
    {
      "id": "il-sb4016-2026-lead",
      "state": "Illinois",
      "jurisdiction": "Illinois",
      "authority": "State legislature",
      "title": "SB 4016 (2026), hyperscale data-center framework proposal",
      "pillars": [
        "water",
        "power",
        "air",
        "land",
        "transparency",
        "finance",
        "lifecycle"
      ],
      "summary": "The introduced proposal would establish a broad hyperscale data-center framework covering water-impact permits, reporting, cumulative impacts, energy, community process, and financial programs. The enrolled dataset does not treat this introduced text as binding law.",
      "publisher": "Illinois General Assembly",
      "url": "https://www.ilga.gov/documents/legislation/104/SB/PDF/10400SB4016.pdf",
      "pinpoint": "SB 4016, 104th General Assembly, introduced version, Feb. 6, 2026",
      "checked": "2026-10-28",
      "review": "Official introduced bill text; proposed, not law",
      "legalStatus": "Proposed bill; introduced version only",
      "next": "Retrieve current official bill status and amendments; identify any provisions advanced in a successor vehicle.",
      "instrumentId": null
    },
    {
      "id": "il-hb4989-2026-lead",
      "state": "Illinois",
      "jurisdiction": "Illinois",
      "authority": "State legislature",
      "title": "HB 4989 (2026), data-center heat-reuse and cooling proposal",
      "pillars": [
        "water",
        "air",
        "power",
        "transparency"
      ],
      "summary": "The introduced proposal would require data centers to adopt a heat-reuse plan and require liquid cooling for new centers with aggregate demand of at least 20 MW. Official bill status lists referral to the Rules Committee on February 6, 2026; proposal only.",
      "publisher": "Illinois General Assembly",
      "url": "https://www.ilga.gov/Legislation/BillStatus?DocNum=4989&DocTypeID=HB&GAID=18&LegId=166403&SessionID=114",
      "pinpoint": "HB 4989, 104th General Assembly, Synopsis As Introduced; Actions through Feb. 6, 2026",
      "checked": "2026-10-28",
      "review": "Official bill status/synopsis; proposed, not law",
      "legalStatus": "Proposed; last displayed action Feb. 6, 2026, referred to Rules Committee",
      "next": "Check current session action and amendments; do not present proposed cooling technology requirements as binding.",
      "instrumentId": null
    },
    {
      "id": "nj-c32-chapter-law",
      "state": "New Jersey",
      "jurisdiction": "New Jersey",
      "authority": "State",
      "title": "P.L. 2026, c.32 — Data Center Fair Share Act (chaptered text)",
      "pillars": [
        "power",
        "finance",
        "participation",
        "climate"
      ],
      "summary": "Official chapter law codified at N.J.S.A. 48:7-6.2. Directs BPU standards and electric-utility tariff filings for large data-center customers, with cost, stranded-investment, financial-security, demand-flexibility, clean-resource, and curtailment provisions.",
      "publisher": "New Jersey Legislature",
      "url": "https://pub.njleg.state.nj.us/Bills/2026/PL26/32_.HTM",
      "pinpoint": "P.L. 2026, c.32; N.J.S.A. 48:7-6.2, §§ 1(b)–(j), 2",
      "checked": "2026-10-28",
      "review": "Official chapter law text checked",
      "legalStatus": "Signed and effective 2026-07-07; standards and tariffs pending",
      "next": "Read subsequent BPU docket filings and final standards/tariffs as they issue.",
      "instrumentId": "nj-data-center-fair-share-2026"
    },
    {
      "id": "nj-bpu-c32-rfi-2026",
      "state": "New Jersey",
      "jurisdiction": "New Jersey",
      "authority": "State utility commission",
      "title": "BPU Data Center Fair Share Act implementation RFI — Docket EO26080463",
      "pillars": [
        "power",
        "finance",
        "participation"
      ],
      "summary": "BPU staff requests public input on implementation standards and utility tariffs. Notice schedules a public stakeholder meeting for November 4, 2026 and written responses by November 13, 2026 at 5 p.m.; it is not a final order or tariff.",
      "publisher": "New Jersey Board of Public Utilities",
      "url": "https://www.nj.gov/bpu/pdf/publicnotice/Webposting-Notice-EO26080463-%20Data%20Center%20Fair%20Share%20Act%20RFI.pdf",
      "pinpoint": "Docket EO26080463, Notice and Request for Information, Oct. 19, 2026, pp. 1–3",
      "checked": "2026-10-28",
      "review": "Official implementation request for information; not a final order or tariff",
      "legalStatus": "Implementation proceeding; written response deadline 2026-11-13 17:00 Eastern",
      "next": "Review public comments after the deadline and track BPU standards order and utility tariff petitions.",
      "instrumentId": "nj-data-center-fair-share-2026"
    }
  ]
}
