Data Center Record.
Corrections

Every correction, dated.

When the Record gets something wrong, the fix is published here and on the record itself, with the date and what changed. Nothing is quietly replaced.

  1. · 3,809 source labels corrected (1,044 entries in record source lists, 989 figures, 486 statements, 837 scorecard events, 453 timeline entries)

    What changed
    3,393 from tier 1 to tier 4; 221 from tier 1 to tier 5; 152 from tier 1 to tier 3; 43 from tier 1 to tier 2. The link on each row did not change.
    Why
    Each row carried the kind of the Google News search that found the story (a lead) rather than the kind of outlet it cites. A source takes its outlet's kind: a government or public meeting page, the trade press, a news outlet or a video. Every row, with the outlet named, is in the corrections file.

  2. · 418 source labels corrected (1 news items, 417 statements)

    What changed
    383 from tier 1 to tier 4; 19 from tier 1 to tier 3; 16 from tier 1 to tier 2. The link on each row did not change.
    Why
    Each row carried the kind of the Google News search that found the story (a lead) rather than the kind of outlet it cites. A source takes its outlet's kind: a government or public meeting page, the trade press, a news outlet or a video. Every row, with the outlet named, is in the corrections file.

  1. · 385 date labels corrected (385 scorecard events)

    What changed
    67 now labeled the day of the act; 318 now labeled the day of the report that carried it. The day on each row did not change.
    Why
    A date says what it is: the day of the act where the event's own sentence names that day, or the day of the report that carried the event where the sentence names none (how dates are read). Each row had carried the other label. Every row, with the event it belongs to, is in the corrections file.

  1. · Vantage Phoenix (Goodyear AZ1) · the folded into of a record

    Before
    vantage-goodyear-campus-az
    After
    vantage-phoenix-az
    Why
    Jordan approved folding duplicate draft row vantage-goodyear-campus-az into canonical Vantage Phoenix (Goodyear AZ1) campus record vantage-phoenix-az at 14537 W Broadway Rd, Goodyear, AZ 85338 (EPA FRS ID 110071864472, 160 MW, 3 buildings) (2026-10-26).

  2. · Edged Mesa data center · the folded into of a record

    Before
    edged-phoenix-data-center-mesa-az
    After
    edged-mesa-data-center-az
    Why
    Jordan approved folding duplicate trade press row edged-phoenix-data-center-mesa-az into canonical Edged Mesa (PHX01) record edged-mesa-data-center-az at 8927 E Ray Rd, Mesa, AZ 85212 (36 MW) (2026-10-26).

  3. · NTT Global Data Centers Garland (TX1) · the folded into of a record

    Before
    ntt-data-garland-campus-tx
    After
    ntt-garland-tx1-water-tx
    Why
    Jordan approved folding ntt-data-garland-campus-tx (2008 Lookout Dr, Garland) into ntt-garland-tx1-water-tx (2001 Lookout Dr, Garland, EPA FRS ID 110070358446) as a single NTT Global Data Centers Garland (TX1) campus record (2026-10-25).

  4. · Wildcat Ridge Data Center Campus · the slug of a record

    Before
    ppl-archbald-data-center-power-plants-pa
    After
    wildcat-ridge-data-center-campus-archbald-pa
    Why
    Folded duplicate Archbald power plant land deal lead into the canonical PA DEP tracker record for Wildcat Ridge Data Center Campus.

  5. · Lower Mount Bethel Technology Center · the slug of a record

    Before
    northampton-county-data-center-pa
    After
    lower-mount-bethel-technology-center-pa
    Why
    Folded duplicate Northampton County news lead into the canonical PA DEP tracker record for Lower Mount Bethel Technology Center.

  6. · Project Hazelnut · the slug of a record

    Before
    northpoint-hazle-township-data-center-campus-pa
    After
    project-hazelnut-hazle-township-pa
    Why
    Folded duplicate news lead for NorthPoint Hazle Township into the canonical PA DEP tracker record for Project Hazelnut.

  7. · Novva West Jordan Data Center Campus · the slug of a record

    Before
    novva-west-jordan-campus-expansion-ut
    After
    novva-salt-lake-city-data-center-ut
    Why
    Folded duplicate expansion lead for Novva West Jordan into the canonical campus record at 6800 W. 9800 South, West Jordan.

  8. · Novva West Jordan Data Center Campus · the slug of a record

    Before
    novva-west-jordan-campus-ut
    After
    novva-salt-lake-city-data-center-ut
    Why
    Folded duplicate news lead for Novva West Jordan into the canonical campus record at 6800 W. 9800 South, West Jordan.

  9. · Viawest INC, Englewood Data Center · the city of a record

    Before
    Parker Area
    After
    Parker
    Why
    The EPA's registry spells the town "Parker Area"; the Census Bureau's name for the place in Douglas County is Parker. Corrected under the record's rules (October 20, 2026).

  10. · United Fiber & Data York Data Center · the city of a record

    Before
    York, City Of
    After
    York
    Why
    The EPA's registry spells the town "York, City Of"; the Census Bureau's name for the place in York County is York. Corrected under the record's rules (October 20, 2026).

  11. · One Neck Denver Data Center · the city of a record

    Before
    Englewood
    After
    Why
    The EPA's registry names the town "Englewood", which is not a Census place in Douglas County; the record is filed at the county level. Corrected under the record's rules (October 20, 2026).

  12. · Novva Data Centers · the city of a record

    Before
    Sparks
    After
    Why
    The EPA's registry names the town "Sparks", which is not a Census place in Storey County; the record is filed at the county level. Corrected under the record's rules (October 20, 2026).

  13. · NJ-1 Data Center · the city of a record

    Before
    Piscataway TWP
    After
    Piscataway
    Why
    The EPA's registry spells the town "Piscataway TWP"; the Census Bureau's name for the place in Middlesex County is Piscataway. Corrected under the record's rules (October 20, 2026).

  14. · Jordan Feeder, Flexential Project (de) · the city of a record

    Before
    Unincorporated Arapahoe County
    After
    Why
    The EPA's registry names the town "Unincorporated Arapahoe County", which is not a Census place in Arapahoe County; the record is filed at the county level. Corrected under the record's rules (October 20, 2026).

  15. · Jacobs Project Management Co, Hut 8 DC Corp-river Bend Data Center · the city of a record

    Before
    Saint Francisville
    After
    St. Francisville
    Why
    The EPA's registry spells the town "Saint Francisville"; the Census Bureau's name for the place in West Feliciana Parish is St. Francisville. Corrected under the record's rules (October 20, 2026).

  16. · Compark Data Center · the city of a record

    Before
    Centennial
    After
    Why
    The EPA's registry names the town "Centennial", which is not a Census place in Douglas County; the record is filed at the county level. Corrected under the record's rules (October 20, 2026).

  17. · Comcast XSDC Data Center · the city of a record

    Before
    North Fayette, Township Of
    After
    North Fayette
    Why
    The EPA's registry spells the town "North Fayette, Township Of"; the Census Bureau's name for the place in Allegheny County is North Fayette. Corrected under the record's rules (October 20, 2026).

  18. · Bitpower Data Center · the city of a record

    Before
    Anaconda
    After
    Why
    The EPA's registry names the town "Anaconda", which is not a Census place in Deer Lodge County; the record is filed at the county level. Corrected under the record's rules (October 20, 2026).

  19. · Aiken 5 MW Data Center · the city of a record

    Before
    Aiken
    After
    Why
    The EPA's registry names the town "Aiken", which is not a Census place in Edgefield County; the record is filed at the county level. Corrected under the record's rules (October 20, 2026).

  20. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Taken off under the record's rules: the line names no data center or crypto mining subject; a bulk path wrote it without the subject check (October 20, 2026).

  21. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Taken off under the record's rules: the line names no data center or crypto mining subject; a bulk path wrote it without the subject check (October 20, 2026).

  22. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Taken off under the record's rules: the line names no data center or crypto mining subject; a bulk path wrote it without the subject check (October 20, 2026).

  23. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Taken off under the record's rules: the line names no data center or crypto mining subject; a bulk path wrote it without the subject check (October 20, 2026).

  24. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Taken off under the record's rules: the line names no data center or crypto mining subject; a bulk path wrote it without the subject check (October 20, 2026).

  25. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Taken off under the record's rules: the line names no data center or crypto mining subject; a bulk path wrote it without the subject check (October 20, 2026).

  26. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Taken off under the record's rules: the line names no data center or crypto mining subject; a bulk path wrote it without the subject check (October 20, 2026).

  27. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Taken off under the record's rules: the line names no data center or crypto mining subject; a bulk path wrote it without the subject check (October 20, 2026).

  28. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Taken off under the record's rules: the line names no data center or crypto mining subject; a bulk path wrote it without the subject check (October 20, 2026).

  29. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Taken off under the record's rules: the line names no data center or crypto mining subject; a bulk path wrote it without the subject check (October 20, 2026).

  30. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Taken off under the record's rules: the line names no data center or crypto mining subject; a bulk path wrote it without the subject check (October 20, 2026).

  31. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Taken off under the record's rules: the line names no data center or crypto mining subject; a bulk path wrote it without the subject check (October 20, 2026).

  32. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Taken off under the record's rules: the line names no data center or crypto mining subject; a bulk path wrote it without the subject check (October 20, 2026).

  33. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Taken off under the record's rules: the line names no data center or crypto mining subject; a bulk path wrote it without the subject check (October 20, 2026).

  34. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Taken off under the record's rules: the line names no data center or crypto mining subject; a bulk path wrote it without the subject check (October 20, 2026).

  35. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Taken off under the record's rules: the line names no data center or crypto mining subject; a bulk path wrote it without the subject check (October 20, 2026).

  36. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Taken off under the record's rules: the line names no data center or crypto mining subject; a bulk path wrote it without the subject check (October 20, 2026).

  37. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Taken off under the record's rules: the line names no data center or crypto mining subject; a bulk path wrote it without the subject check (October 20, 2026).

  38. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Taken off under the record's rules: the line names no data center or crypto mining subject; a bulk path wrote it without the subject check (October 20, 2026).

  39. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Taken off under the record's rules: the line names no data center or crypto mining subject; a bulk path wrote it without the subject check (October 20, 2026).

  40. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Taken off under the record's rules: the line names no data center or crypto mining subject; a bulk path wrote it without the subject check (October 20, 2026).

  41. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Taken off under the record's rules: the line names no data center or crypto mining subject; a bulk path wrote it without the subject check (October 20, 2026).

  42. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Taken off under the record's rules: the line names no data center or crypto mining subject; a bulk path wrote it without the subject check (October 20, 2026).

  43. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Taken off under the record's rules: the line names no data center or crypto mining subject; a bulk path wrote it without the subject check (October 20, 2026).

  44. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Taken off under the record's rules: the line names no data center or crypto mining subject; a bulk path wrote it without the subject check (October 20, 2026).

  45. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Taken off under the record's rules: the line names no data center or crypto mining subject; a bulk path wrote it without the subject check (October 20, 2026).

  46. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Taken off under the record's rules: the line names no data center or crypto mining subject; a bulk path wrote it without the subject check (October 20, 2026).

  47. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Taken off under the record's rules: the line names no data center or crypto mining subject; a bulk path wrote it without the subject check (October 20, 2026).

  48. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Taken off under the record's rules: the line names no data center or crypto mining subject; a bulk path wrote it without the subject check (October 20, 2026).

  49. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Taken off under the record's rules: the line names no data center or crypto mining subject; a bulk path wrote it without the subject check (October 20, 2026).

  50. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Taken off under the record's rules: the line names no data center or crypto mining subject; a bulk path wrote it without the subject check (October 20, 2026).

  51. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Taken off under the record's rules: the line names no data center or crypto mining subject; a bulk path wrote it without the subject check (October 20, 2026).

  52. · TierPoint Lehigh Valley Data Center · the city of a record

    Before
    Valley
    After
    Bethlehem
    Why
    TierPoint's own page prints the facility's street address, which the Census Bureau's geocoder places in Northampton County (Bethlehem); the record had filed it under Chester County. Corrected on the editor's word.

  53. · TierPoint Lehigh Valley Data Center · the county of a record

    Before
    Chester County
    After
    Northampton County
    Why
    TierPoint's own page prints the facility's street address, which the Census Bureau's geocoder places in Northampton County (Bethlehem); the record had filed it under Chester County. Corrected on the editor's word.

  54. · TierPoint Kansas City - Lenexa Data Center · the city of a record

    Before
    Kansas City
    After
    Lenexa
    Why
    TierPoint's own page prints the facility's street address, which the Census Bureau's geocoder places in Johnson County (Lenexa); the record had filed it under Wyandotte County. Corrected on the editor's word.

  55. · TierPoint Kansas City - Lenexa Data Center · the county of a record

    Before
    Wyandotte County
    After
    Johnson County
    Why
    TierPoint's own page prints the facility's street address, which the Census Bureau's geocoder places in Johnson County (Lenexa); the record had filed it under Wyandotte County. Corrected on the editor's word.

  56. · H5 New York · the county of a record

    Before
    Kings County
    After
    New York County
    Why
    H5 Data Centers's own page prints the facility's street address, which the Census Bureau's geocoder places in New York County; the record had filed it under Kings County. Corrected on the editor's word.

  57. · Digital Realty New York · the county of a record

    Before
    Kings County
    After
    New York County
    Why
    Digital Realty's own page prints the facility's street address, which the Census Bureau's geocoder places in New York County; the record had filed it under Kings County. Corrected on the editor's word.

  58. · TierPoint New York , Hawthorne Data Center · the city of a record

    Before
    New York
    After
    Hawthorne
    Why
    TierPoint's own page prints the facility's street address, which the Census Bureau's geocoder places in Westchester County (Hawthorne); the record had filed it under Kings County. Corrected on the editor's word.

  59. · TierPoint New York , Hawthorne Data Center · the county of a record

    Before
    Kings County
    After
    Westchester County
    Why
    TierPoint's own page prints the facility's street address, which the Census Bureau's geocoder places in Westchester County (Hawthorne); the record had filed it under Kings County. Corrected on the editor's word.

  60. · United States (federal) · the rating of a scorecard event

    Before
    case by case
    After
    no published rating
    Why
    The event carried Nevada's own rating, which the approve writes on an event with no accepted rating; the United States (federal) row carries no rating, so the moved event carries none. October 20, 2026.

  61. · United States (federal) · the scorecard row of a scorecard event

    Before
    NV/nevada
    After
    US/united-states
    Why
    The Interior Board of Land Appeals is a federal board; its stay is filed on the United States (federal) row, where the record files every federal body's act. Moved on the editor's word (October 20, 2026).

  62. · a record · the place of a figure

    Before
    Kuna, Idaho County, ID
    After
    Kuna, Ada County, ID
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  63. · a record · the place of a figure

    Before
    Kuna, Idaho County, ID
    After
    Kuna, Ada County, ID
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  64. · a record · the place of a figure

    Before
    Wilson, Arkansas County, AR
    After
    Wilson, Mississippi County, AR
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  65. · a record · the place of a figure

    Before
    Wilson, Arkansas County, AR
    After
    Wilson, Mississippi County, AR
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  66. · a record · the place of a figure

    Before
    Claremore, Oklahoma County, OK
    After
    Claremore, Rogers County, OK
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  67. · a record · the place of a figure

    Before
    Claremore, Oklahoma County, OK
    After
    Claremore, Rogers County, OK
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  68. · a record · the place of a figure

    Before
    Piketon, Ohio County, OH
    After
    Piketon, Pike County, OH
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  69. · a record · the place of a figure

    Before
    Piketon, Ohio County, OH
    After
    Piketon, Pike County, OH
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  70. · a record · the place of a figure

    Before
    Hawesville, Ohio County, KY
    After
    Hawesville, Hancock County, KY
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  71. · a record · the place of a figure

    Before
    Hawesville, Ohio County, KY
    After
    Hawesville, Hancock County, KY
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  72. · a record · the place of a figure

    Before
    Kuna, Idaho County, ID
    After
    Kuna, Ada County, ID
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  73. · a record · the place of a figure

    Before
    Kuna, Idaho County, ID
    After
    Kuna, Ada County, ID
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  74. · a record · the place of a figure

    Before
    West Jordan, Utah County, UT
    After
    West Jordan, Salt Lake County, UT
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  75. · a record · the place of a figure

    Before
    West Jordan, Utah County, UT
    After
    West Jordan, Salt Lake County, UT
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  76. · a record · the place of a figure

    Before
    Wilson, Arkansas County, AR
    After
    Wilson, Mississippi County, AR
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  77. · a record · the place of a figure

    Before
    Wilson, Arkansas County, AR
    After
    Wilson, Mississippi County, AR
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  78. · a record · the place of a figure

    Before
    Claremore, Oklahoma County, OK
    After
    Claremore, Rogers County, OK
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  79. · a record · the place of a figure

    Before
    Claremore, Oklahoma County, OK
    After
    Claremore, Rogers County, OK
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  80. · a record · the place of a figure

    Before
    Wilson, Arkansas County, AR
    After
    Wilson, Mississippi County, AR
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  81. · a record · the place of a figure

    Before
    Wilson, Arkansas County, AR
    After
    Wilson, Mississippi County, AR
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  82. · a record · the place of a figure

    Before
    Hawesville, Ohio County, KY
    After
    Hawesville, Hancock County, KY
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  83. · a record · the place of a figure

    Before
    Hawesville, Ohio County, KY
    After
    Hawesville, Hancock County, KY
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  84. · a record · the place of a figure

    Before
    Salix, O'Brien County, IA
    After
    Salix, Woodbury County, IA
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  85. · a record · the place of a figure

    Before
    Salix, O'Brien County, IA
    After
    Salix, Woodbury County, IA
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  86. · a record · the place of a figure

    Before
    Enid, Oklahoma County, OK
    After
    Enid, Garfield County, OK
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  87. · a record · the place of a figure

    Before
    Enid, Oklahoma County, OK
    After
    Enid, Garfield County, OK
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  88. · a record · the place of a figure

    Before
    Kuna, Idaho County, ID
    After
    Kuna, Ada County, ID
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  89. · a record · the place of a figure

    Before
    Kuna, Idaho County, ID
    After
    Kuna, Ada County, ID
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  90. · a record · the place of a figure

    Before
    Enid, Oklahoma County, OK
    After
    Enid, Garfield County, OK
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  91. · a record · the place of a figure

    Before
    Enid, Oklahoma County, OK
    After
    Enid, Garfield County, OK
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  92. · a record · the place of a figure

    Before
    Enid, Oklahoma County, OK
    After
    Enid, Garfield County, OK
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  93. · a record · the place of a figure

    Before
    Enid, Oklahoma County, OK
    After
    Enid, Garfield County, OK
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  94. · a record · the place of a figure

    Before
    Prineville, Marion County, OR
    After
    Prineville, Crook County, OR
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  95. · a record · the place of a figure

    Before
    Prineville, Marion County, OR
    After
    Prineville, Crook County, OR
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  96. · a record · the place of a figure

    Before
    Quincy, Skagit County, WA
    After
    Quincy, Grant County, WA
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  97. · a record · the place of a figure

    Before
    Quincy, Skagit County, WA
    After
    Quincy, Grant County, WA
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  98. · a record · the place of a figure

    Before
    Prineville, Marion County, OR
    After
    Prineville, Crook County, OR
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  99. · a record · the place of a figure

    Before
    Prineville, Marion County, OR
    After
    Prineville, Crook County, OR
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  100. · a record · the place of a figure

    Before
    Desloge, St. Louis County, MO
    After
    Desloge, St. Francois County, MO
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  101. · a record · the place of a figure

    Before
    Desloge, St. Louis County, MO
    After
    Desloge, St. Francois County, MO
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  102. · a record · the place of a figure

    Before
    Piketon, Ohio County, OH
    After
    Piketon, Pike County, OH
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  103. · a record · the place of a figure

    Before
    Piketon, Ohio County, OH
    After
    Piketon, Pike County, OH
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  104. · a record · the place of a figure

    Before
    Mona, Utah County, UT
    After
    Mona, Juab County, UT
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  105. · a record · the place of a figure

    Before
    Mona, Utah County, UT
    After
    Mona, Juab County, UT
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  106. · a record · the place of a figure

    Before
    Piketon, Ohio County, OH
    After
    Piketon, Pike County, OH
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  107. · a record · the place of a figure

    Before
    Piketon, Ohio County, OH
    After
    Piketon, Pike County, OH
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  108. · a record · the place of a figure

    Before
    Hawesville, Ohio County, KY
    After
    Hawesville, Hancock County, KY
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  109. · a record · the place of a figure

    Before
    Hawesville, Ohio County, KY
    After
    Hawesville, Hancock County, KY
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  110. · a record · the place of a figure

    Before
    Kuna, Idaho County, ID
    After
    Kuna, Ada County, ID
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  111. · a record · the place of a figure

    Before
    Kuna, Idaho County, ID
    After
    Kuna, Ada County, ID
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  112. · a record · the place of a figure

    Before
    Claremore, Oklahoma County, OK
    After
    Claremore, Rogers County, OK
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  113. · a record · the place of a figure

    Before
    Claremore, Oklahoma County, OK
    After
    Claremore, Rogers County, OK
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  114. · a record · the place of a figure

    Before
    Prineville, Marion County, OR
    After
    Prineville, Crook County, OR
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  115. · a record · the place of a figure

    Before
    Prineville, Marion County, OR
    After
    Prineville, Crook County, OR
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  116. · a record · the place of a figure

    Before
    Kearney, NE County, NE
    After
    Kearney, Buffalo County, NE
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  117. · a record · the place of a figure

    Before
    Kearney, NE County, NE
    After
    Kearney, Buffalo County, NE
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  118. · a record · the place of a figure

    Before
    Quincy, Skagit County, WA
    After
    Quincy, Grant County, WA
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  119. · a record · the place of a figure

    Before
    Quincy, Skagit County, WA
    After
    Quincy, Grant County, WA
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  120. · a record · the place of a figure

    Before
    West Jordan, Utah County, UT
    After
    West Jordan, Salt Lake County, UT
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  121. · a record · the place of a figure

    Before
    West Jordan, Utah County, UT
    After
    West Jordan, Salt Lake County, UT
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  122. · a record · the place of a figure

    Before
    Wilson, Arkansas County, AR
    After
    Wilson, Mississippi County, AR
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  123. · a record · the place of a figure

    Before
    Wilson, Arkansas County, AR
    After
    Wilson, Mississippi County, AR
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  124. · a record · the place of a figure

    Before
    Wilson, Arkansas County, AR
    After
    Wilson, Mississippi County, AR
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  125. · a record · the place of a figure

    Before
    Wilson, Arkansas County, AR
    After
    Wilson, Mississippi County, AR
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  126. · a record · the place of a figure

    Before
    Mona, Utah County, UT; Box Elder County, UT
    After
    Mona, Juab County, UT; Box Elder County, UT
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  127. · a record · the place of a figure

    Before
    Mona, Utah County, UT; Box Elder County, UT
    After
    Mona, Juab County, UT; Box Elder County, UT
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  128. · a record · the place of a figure

    Before
    Wilson, Arkansas County, AR
    After
    Wilson, Mississippi County, AR
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  129. · a record · the place of a figure

    Before
    Wilson, Arkansas County, AR
    After
    Wilson, Mississippi County, AR
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  130. · a record · the place of a figure

    Before
    Kuna, Idaho County, ID
    After
    Kuna, Ada County, ID
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  131. · a record · the place of a figure

    Before
    Kuna, Idaho County, ID
    After
    Kuna, Ada County, ID
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  132. · a record · the place of a figure

    Before
    Wilson, Arkansas County, AR
    After
    Wilson, Mississippi County, AR
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  133. · a record · the place of a figure

    Before
    Wilson, Arkansas County, AR
    After
    Wilson, Mississippi County, AR
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  134. · a record · the place of a figure

    Before
    Kuna, Idaho County, ID
    After
    Kuna, Ada County, ID
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  135. · a record · the place of a figure

    Before
    Kuna, Idaho County, ID
    After
    Kuna, Ada County, ID
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  136. · a record · the place of a figure

    Before
    Wilson, Arkansas County, AR
    After
    Wilson, Mississippi County, AR
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  137. · a record · the place of a figure

    Before
    Wilson, Arkansas County, AR
    After
    Wilson, Mississippi County, AR
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  138. · a record · the place of a figure

    Before
    Piketon, Ohio County, OH
    After
    Piketon, Pike County, OH
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  139. · a record · the place of a figure

    Before
    Piketon, Ohio County, OH
    After
    Piketon, Pike County, OH
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  140. · a record · the place of a figure

    Before
    Boulder City, Nevada County, NV
    After
    Boulder City, Clark County, NV
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  141. · a record · the place of a figure

    Before
    Boulder City, Nevada County, NV
    After
    Boulder City, Clark County, NV
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  142. · a record · the place of a figure

    Before
    Claremore, Oklahoma County, OK
    After
    Claremore, Rogers County, OK
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  143. · a record · the place of a figure

    Before
    Claremore, Oklahoma County, OK
    After
    Claremore, Rogers County, OK
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  144. · a record · the place of a figure

    Before
    Wilson, Arkansas County, AR
    After
    Wilson, Mississippi County, AR
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  145. · a record · the place of a figure

    Before
    Wilson, Arkansas County, AR
    After
    Wilson, Mississippi County, AR
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  146. · a record · the place of a figure

    Before
    Hawesville, Ohio County, KY
    After
    Hawesville, Hancock County, KY
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  147. · a record · the place of a figure

    Before
    Hawesville, Ohio County, KY
    After
    Hawesville, Hancock County, KY
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  148. · a record · the place of a figure

    Before
    Piketon, Ohio County, OH
    After
    Piketon, Pike County, OH
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  149. · a record · the place of a figure

    Before
    Piketon, Ohio County, OH
    After
    Piketon, Pike County, OH
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  150. · a record · the place of a figure

    Before
    Kearney, NE County, NE
    After
    Kearney, Buffalo County, NE
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  151. · a record · the place of a figure

    Before
    Kearney, NE County, NE
    After
    Kearney, Buffalo County, NE
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  152. · a record · the place of a figure

    Before
    Kearney, NE County, NE
    After
    Kearney, Buffalo County, NE
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  153. · a record · the place of a figure

    Before
    Kearney, NE County, NE
    After
    Kearney, Buffalo County, NE
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  154. · a record · the place of a figure

    Before
    Claremore, Oklahoma County, OK
    After
    Claremore, Rogers County, OK
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  155. · a record · the place of a figure

    Before
    Claremore, Oklahoma County, OK
    After
    Claremore, Rogers County, OK
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  156. · a record · the place of a figure

    Before
    Piketon, Ohio County, OH
    After
    Piketon, Pike County, OH
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  157. · a record · the place of a figure

    Before
    Piketon, Ohio County, OH
    After
    Piketon, Pike County, OH
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  158. · a record · the place of a figure

    Before
    Hawesville, Ohio County, KY
    After
    Hawesville, Hancock County, KY
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  159. · a record · the place of a figure

    Before
    Hawesville, Ohio County, KY
    After
    Hawesville, Hancock County, KY
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  160. · a record · the place of a figure

    Before
    Mona, Utah County, UT
    After
    Mona, Juab County, UT
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  161. · a record · the place of a figure

    Before
    Mona, Utah County, UT
    After
    Mona, Juab County, UT
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  162. · a record · the place of a figure

    Before
    Wilson, Arkansas County, AR
    After
    Wilson, Mississippi County, AR
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  163. · a record · the place of a figure

    Before
    Wilson, Arkansas County, AR
    After
    Wilson, Mississippi County, AR
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  164. · a record · the place of a figure

    Before
    Claremore, Oklahoma County, OK
    After
    Claremore, Rogers County, OK
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  165. · a record · the place of a figure

    Before
    Claremore, Oklahoma County, OK
    After
    Claremore, Rogers County, OK
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  166. · a record · the place of a figure

    Before
    Kearney, NE County, NE
    After
    Kearney, Buffalo County, NE
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  167. · a record · the place of a figure

    Before
    Kearney, NE County, NE
    After
    Kearney, Buffalo County, NE
    Why
    The figure's county did not agree with the Census Bureau's 2020 places by county file and is corrected to the Census's county (the editor's word, batch review-fixes-1019b, item 2).

  168. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Taken off the record: the source gives the output of the 45 Mile Hydroelectric plant, which is not a data center (the editor's word, batch review-fixes-1019b, item 2).

  169. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Taken off the record: the source gives Flexential's capacity across 18 U.S. markets, not Hillsboro's (the editor's word, batch review-fixes-1019b, item 2).

  170. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Taken off the record: the source gives Morrow County's property value off its tax rolls, which is not a tax paid each year and not an Oregon figure (the editor's word, batch review-fixes-1019b, item 2).

  171. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Taken off the record: the source gives Morrow County's assessed value of tax exempt property, which is not a tax paid each year and not an Oregon figure (the editor's word, batch review-fixes-1019b, item 2).

  172. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Taken off the record: the source says almost 1 in every 100 jobs in Oregon, a share and not a count of 100 jobs (the editor's word, batch review-fixes-1019b, item 2).

  173. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Taken off the record: the card filed it under Wasco County, the Census puts Prineville in Crook County, and the sentence names no place (the editor's word, batch review-fixes-1019b, item 2).

  174. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Taken off the record: the card filed it under Marion County, the Census puts Prineville in Crook County, and the sentence names no place (the editor's word, batch review-fixes-1019b, item 2).

  175. · a record · the outlet of a news item

    Before
    Taipei Times
    After
    AFP
    Why
    a syndicated copy is labeled with the outlet that wrote it (the syndicated page's dateline reads AFP, Hazle Township, Pennsylvania)

  176. · a record · the outlet of a news item

    Before
    Free Malaysia Today
    After
    AFP
    Why
    a syndicated copy is labeled with the outlet that wrote it (the syndicated page's own author field reads AFP)

  177. · Washington County · the scorecard row of a scorecard event

    Before
    WA/washington-county
    After
    ID/washington-county
    Why
    Washington State has no Washington County. The event, KTVB of Boise reporting that Washington County residents raised data center concerns as the county weighs an ordinance, is about Washington County, Idaho (Census county 16087), which had no row. The Idaho row is created and the event moves onto it. The new row carries no rating, so the event carries none (the editor's word of 2026-10-20).

  178. · a record · the publication of a scorecard event

    Before
    published
    After
    draft
    Why
    The Lehigh Valley is a region of two counties, not a government, and the record carries no row for a region. Its one published event, Lehigh Valley lawmakers considering regulation, is a plan, not an act. The event returns to draft and stays on file; nothing is deleted (the editor's word of 2026-10-20).

  179. · a record · the publication of a scorecard event

    Before
    published
    After
    draft
    Why
    The Tri State area is the Cincinnati area across three states, not a government, and the record carries no row for a region. Its one published event, a resident suing to block an emergency rezoning, names no body or place in its words. The event returns to draft and stays on file; nothing is deleted (the editor's word of 2026-10-20).

  180. · a record · the publication of a scorecard event

    Before
    published
    After
    draft
    Why
    The Magic Valley is a region of south central Idaho, not a government, and the record carries no row for a region. Its one published event, tax cuts continuing to support data center development, states no act of a body. The event returns to draft and stays on file; nothing is deleted (the editor's word of 2026-10-20).

  181. · a record · the publication of a scorecard event

    Before
    published
    After
    draft
    Why
    The Bay Area is a region of nine counties, not a government, and the record carries no row for a region. Its one published event, Bay Area lawmakers pushing transparency bills sent to the governor, is about state bills, and California's own row carries the bills sent to the governor. The event returns to draft and stays on file; nothing is deleted (the editor's word of 2026-10-20).

  182. · Dan S. Sullivan · the FEC candidate id of a candidate listing

    Before
    S6AK00326
    After
    S4AK00214
    Why
    The Federal Election Commission's own file gives this candidate id to Daniel J. Sullivan and gives Senator Dan Sullivan the id S4AK00214. The record had put the first id on both Alaska Sullivans' listings; this listing now carries its own.

  183. · Rio Phillips · the status of a candidacy

    Before
    On the ballot
    After
    Certified write in
    Why
    The state's own list names this candidate as a certified write in, not as a name printed on the ballot; the record changed the status to say so.

  184. · Babak "BOBBY" Darvish · the status of a candidacy

    Before
    On the ballot
    After
    Certified write in
    Why
    The state's own list names this candidate as a certified write in, not as a name printed on the ballot; the record changed the status to say so.

  185. · Randy Wilcox · the status of a candidacy

    Before
    On the ballot
    After
    Certified write in
    Why
    The state's own list names this candidate as a certified write in, not as a name printed on the ballot; the record changed the status to say so.

  186. · John Glowa · the status of a candidacy

    Before
    On the ballot
    After
    Certified write in
    Why
    The state's own list names this candidate as a certified write in, not as a name printed on the ballot; the record changed the status to say so.

  187. · Gregory A. Ward · the status of a candidacy

    Before
    On the ballot
    After
    Certified write in
    Why
    The state's own list names this candidate as a certified write in, not as a name printed on the ballot; the record changed the status to say so.

  188. · Ashley J. Webb · the status of a candidacy

    Before
    On the ballot
    After
    Certified write in
    Why
    The state's own list names this candidate as a certified write in, not as a name printed on the ballot; the record changed the status to say so.

  189. · Michael Turcotte · the status of a candidacy

    Before
    On the ballot
    After
    Certified write in
    Why
    The state's own list names this candidate as a certified write in, not as a name printed on the ballot; the record changed the status to say so.

  190. · Joseph Steinberger · the status of a candidacy

    Before
    On the ballot
    After
    Certified write in
    Why
    The state's own list names this candidate as a certified write in, not as a name printed on the ballot; the record changed the status to say so.

  191. · Gina Oswald · the status of a candidacy

    Before
    On the ballot
    After
    Certified write in
    Why
    The state's own list names this candidate as a certified write in, not as a name printed on the ballot; the record changed the status to say so.

  192. · Sigrid Ann Olson · the status of a candidacy

    Before
    On the ballot
    After
    Certified write in
    Why
    The state's own list names this candidate as a certified write in, not as a name printed on the ballot; the record changed the status to say so.

  193. · Brent Andrews · the status of a candidacy

    Before
    On the ballot
    After
    Certified write in
    Why
    The state's own list names this candidate as a certified write in, not as a name printed on the ballot; the record changed the status to say so.

  194. · Mildred Marie Hall · the status of a candidacy

    Before
    On the ballot
    After
    Certified write in
    Why
    The state's own list names this candidate as a certified write in, not as a name printed on the ballot; the record changed the status to say so.

  195. · Robert L. Coffman · the status of a candidacy

    Before
    On the ballot
    After
    Certified write in
    Why
    The state's own list names this candidate as a certified write in, not as a name printed on the ballot; the record changed the status to say so.

  196. · Edward Shlikas · the status of a candidacy

    Before
    On the ballot
    After
    Certified write in
    Why
    The state's own list names this candidate as a certified write in, not as a name printed on the ballot; the record changed the status to say so.

  197. · Robert Quigley · the source of the status of a candidacy

    Before
    Source: web.sos.ky.gov
    After
    Source: Kentucky Secretary of State, Candidate Filings, US Representative, 2026 General Election
    Why
    The page the record cited for this certified write in did not name them; the record now cites the list that does.

  198. · Billy Ray Wilson · the source of the status of a candidacy

    Before
    Source: web.sos.ky.gov
    After
    Source: Kentucky Secretary of State, Candidate Filings, US Representative, 2026 General Election
    Why
    The page the record cited for this certified write in did not name them; the record now cites the list that does.

  199. · Peter Harmon Williams · the source of the status of a candidacy

    Before
    Source: web.sos.ky.gov
    After
    Source: Kentucky Secretary of State, Candidate Filings, US Representative, 2026 General Election
    Why
    The page the record cited for this certified write in did not name them; the record now cites the list that does.

  200. · Jacob Burnett · the status of a candidacy

    Before
    On the ballot
    After
    Certified write in
    Why
    The state's own list names this candidate as a certified write in, not as a name printed on the ballot; the record changed the status to say so.

  201. · Rob Ruszkowski · the source of the status of a candidacy

    Before
    Source: assets.cobbcounty.gov
    After
    Source: Georgia Secretary of State, Elections Division, Final list of certified write in candidates for the November 3, 2026 gen
    Why
    The page the record cited for this certified write in did not name them; the record now cites the list that does.

  202. · Jonathan R. McHugh · the source of the status of a candidacy

    Before
    Source: assets.cobbcounty.gov
    After
    Source: Georgia Secretary of State, Elections Division, Final list of certified write in candidates for the November 3, 2026 gen
    Why
    The page the record cited for this certified write in did not name them; the record now cites the list that does.

  203. · Antoine F. Kelley Jr. · the source of the status of a candidacy

    Before
    Source: dekalbcountyga.gov
    After
    Source: Georgia Secretary of State, Elections Division, Final list of certified write in candidates for the November 3, 2026 gen
    Why
    The page the record cited for this certified write in did not name them; the record now cites the list that does.

  204. · Natalie Richoz · the source of the status of a candidacy

    Before
    Source: assets.cobbcounty.gov
    After
    Source: Georgia Secretary of State, Elections Division, Final list of certified write in candidates for the November 3, 2026 gen
    Why
    The page the record cited for this certified write in did not name them; the record now cites the list that does.

  205. · Amanda Carter James · the source of the status of a candidacy

    Before
    Source: assets.cobbcounty.gov
    After
    Source: Georgia Secretary of State, Elections Division, Final list of certified write in candidates for the November 3, 2026 gen
    Why
    The page the record cited for this certified write in did not name them; the record now cites the list that does.

  206. · Tabitha Johnson-Green · the source of the status of a candidacy

    Before
    Source: www.gwinnettcounty.com
    After
    Source: Georgia Secretary of State, Elections Division, Final list of certified write in candidates for the November 3, 2026 gen
    Why
    The page the record cited for this certified write in did not name them; the record now cites the list that does.

  207. · Cassandra Easton · the source of the status of a candidacy

    Before
    Source: www.fultoncountyga.gov
    After
    Source: Georgia Secretary of State, Elections Division, Final list of certified write in candidates for the November 3, 2026 gen
    Why
    The page the record cited for this certified write in did not name them; the record now cites the list that does.

  208. · Christina Loren Truste Clement · the source of the status of a candidacy

    Before
    Source: www.fultoncountyga.gov
    After
    Source: Georgia Secretary of State, Elections Division, Final list of certified write in candidates for the November 3, 2026 gen
    Why
    The page the record cited for this certified write in did not name them; the record now cites the list that does.

  209. · Elbert Arthur Bartell · the source of the status of a candidacy

    Before
    Source: www.fultoncountyga.gov
    After
    Source: Georgia Secretary of State, Elections Division, Final list of certified write in candidates for the November 3, 2026 gen
    Why
    The page the record cited for this certified write in did not name them; the record now cites the list that does.

  210. · Andrew Pacetti · the source of the status of a candidacy

    Before
    Source: www.fultoncountyga.gov
    After
    Source: Georgia Secretary of State, Elections Division, Final list of certified write in candidates for the November 3, 2026 gen
    Why
    The page the record cited for this certified write in did not name them; the record now cites the list that does.

  211. · Leland Jake Olinger II · the source of the status of a candidacy

    Before
    Source: www.fultoncountyga.gov
    After
    Source: Georgia Secretary of State, Elections Division, Final list of certified write in candidates for the November 3, 2026 gen
    Why
    The page the record cited for this certified write in did not name them; the record now cites the list that does.

  212. · David Leon Moreland · the source of the status of a candidacy

    Before
    Source: www.fultoncountyga.gov
    After
    Source: Georgia Secretary of State, Elections Division, Final list of certified write in candidates for the November 3, 2026 gen
    Why
    The page the record cited for this certified write in did not name them; the record now cites the list that does.

  213. · Milton J. Lofton · the source of the status of a candidacy

    Before
    Source: www.fultoncountyga.gov
    After
    Source: Georgia Secretary of State, Elections Division, Final list of certified write in candidates for the November 3, 2026 gen
    Why
    The page the record cited for this certified write in did not name them; the record now cites the list that does.

  214. · Deb Broughton Davis · the source of the status of a candidacy

    Before
    Source: www.fultoncountyga.gov
    After
    Source: Georgia Secretary of State, Elections Division, Final list of certified write in candidates for the November 3, 2026 gen
    Why
    The page the record cited for this certified write in did not name them; the record now cites the list that does.

  215. · Jacqueline Angela DaCosta · the source of the status of a candidacy

    Before
    Source: www.fultoncountyga.gov
    After
    Source: Georgia Secretary of State, Elections Division, Final list of certified write in candidates for the November 3, 2026 gen
    Why
    The page the record cited for this certified write in did not name them; the record now cites the list that does.

  216. · David C. Byrne · the source of the status of a candidacy

    Before
    Source: www.fultoncountyga.gov
    After
    Source: Georgia Secretary of State, Elections Division, Final list of certified write in candidates for the November 3, 2026 gen
    Why
    The page the record cited for this certified write in did not name them; the record now cites the list that does.

  217. · Michaelangelo Hamilton · the status of a candidacy

    Before
    On the ballot
    After
    Certified write in
    Why
    The state's own list names this candidate as a certified write in, not as a name printed on the ballot; the record changed the status to say so.

  218. · Patricia Gonzalez · the status of a candidacy

    Before
    On the ballot
    After
    Certified write in
    Why
    The state's own list names this candidate as a certified write in, not as a name printed on the ballot; the record changed the status to say so.

  219. · David Fabrikant · the status of a candidacy

    Before
    On the ballot
    After
    Certified write in
    Why
    The state's own list names this candidate as a certified write in, not as a name printed on the ballot; the record changed the status to say so.

  220. · Alexandra Zakhvatayev · the status of a candidacy

    Before
    On the ballot
    After
    Certified write in
    Why
    The state's own list names this candidate as a certified write in, not as a name printed on the ballot; the record changed the status to say so.

  221. · Angie Boone · the status of a candidacy

    Before
    On the ballot
    After
    Certified write in
    Why
    The state's own list names this candidate as a certified write in, not as a name printed on the ballot; the record changed the status to say so.

  222. · Keith Varian · the status of a candidacy

    Before
    On the ballot
    After
    Certified write in
    Why
    The state's own list names this candidate as a certified write in, not as a name printed on the ballot; the record changed the status to say so.

  223. · Salomon Hernandez Sr. · the status of a candidacy

    Before
    On the ballot
    After
    Certified write in
    Why
    The state's own list names this candidate as a certified write in, not as a name printed on the ballot; the record changed the status to say so.

  224. · Alec Pavlik · the status of a candidacy

    Before
    On the ballot
    After
    Certified write in
    Why
    The state's own list names this candidate as a certified write in, not as a name printed on the ballot; the record changed the status to say so.

  225. · William Lintag Upham · the status of a candidacy

    Before
    On the ballot
    After
    Certified write in
    Why
    The state's own list names this candidate as a certified write in, not as a name printed on the ballot; the record changed the status to say so.

  226. · Erik Morris · the status of a candidacy

    Before
    On the ballot
    After
    Certified write in
    Why
    The state's own list names this candidate as a certified write in, not as a name printed on the ballot; the record changed the status to say so.

  227. · Kathy Anderson · the status of a candidacy

    Before
    On the ballot
    After
    Certified write in
    Why
    The state's own list names this candidate as a certified write in, not as a name printed on the ballot; the record changed the status to say so.

  228. · David Solana · the status of a candidacy

    Before
    On the ballot
    After
    Certified write in
    Why
    The state's own list names this candidate as a certified write in, not as a name printed on the ballot; the record changed the status to say so.

  229. · Rebekkah Green · the status of a candidacy

    Before
    On the ballot
    After
    Certified write in
    Why
    The state's own list names this candidate as a certified write in, not as a name printed on the ballot; the record changed the status to say so.

  230. · Steven Fuller · the status of a candidacy

    Before
    On the ballot
    After
    Certified write in
    Why
    The state's own list names this candidate as a certified write in, not as a name printed on the ballot; the record changed the status to say so.

  231. · Luis Galvan · the status of a candidacy

    Before
    On the ballot
    After
    Certified write in
    Why
    The state's own list names this candidate as a certified write in, not as a name printed on the ballot; the record changed the status to say so.

  232. · Stephen Replin · the status of a candidacy

    Before
    On the ballot
    After
    Certified write in
    Why
    The state's own list names this candidate as a certified write in, not as a name printed on the ballot; the record changed the status to say so.

  233. · John Wren · the status of a candidacy

    Before
    On the ballot
    After
    Certified write in
    Why
    The state's own list names this candidate as a certified write in, not as a name printed on the ballot; the record changed the status to say so.

  234. · Kevin StClair · the status of a candidacy

    Before
    On the ballot
    After
    Certified write in
    Why
    The state's own list names this candidate as a certified write in, not as a name printed on the ballot; the record changed the status to say so.

  235. · Ryan Apelbaum · the status of a candidacy

    Before
    On the ballot
    After
    Certified write in
    Why
    The state's own list names this candidate as a certified write in, not as a name printed on the ballot; the record changed the status to say so.

  236. · Will Powers · the status of a candidacy

    Before
    On the ballot
    After
    Certified write in
    Why
    The state's own list names this candidate as a certified write in, not as a name printed on the ballot; the record changed the status to say so.

  237. · Donald Willoughby · the status of a candidacy

    Before
    On the ballot
    After
    Certified write in
    Why
    The state's own list names this candidate as a certified write in, not as a name printed on the ballot; the record changed the status to say so.

  238. · Sidney "Sid" Hill · the status of a candidacy

    Before
    On the ballot
    After
    Certified write in
    Why
    The state's own list names this candidate as a certified write in, not as a name printed on the ballot; the record changed the status to say so.

  239. · James W. "JP4" Parkin / Ramadhani "Ram" Greer · the status of a candidacy

    Before
    On the ballot
    After
    Certified write in
    Why
    The state's own list names this candidate as a certified write in, not as a name printed on the ballot; the record changed the status to say so.

  240. · a candidate · the publication of a candidate listing

    Before
    Published
    After
    Not published
    Why
    The state's list marks this write in declaration rejected, so the state does not certify the candidacy; the record took it off its public pages.

  241. · a candidate · the publication of a candidate listing

    Before
    Published
    After
    Not published
    Why
    A template line the state's list prints for write in votes. It is not a candidate, so it is off the public pages.

  242. · a candidate · the publication of a candidate listing

    Before
    Published
    After
    Not published
    Why
    A template line the state's list prints for write in votes. It is not a candidate, so it is off the public pages.

  243. · a candidate · the publication of a candidate listing

    Before
    Published
    After
    Not published
    Why
    A template line the state's list prints for write in votes. It is not a candidate, so it is off the public pages.

  244. · a candidate · the publication of a candidate listing

    Before
    Published
    After
    Not published
    Why
    A template line the state's list prints for write in votes. It is not a candidate, so it is off the public pages.

  245. · a candidate · the publication of a candidate listing

    Before
    Published
    After
    Not published
    Why
    A template line the state's list prints for write in votes. It is not a candidate, so it is off the public pages.

  246. · a candidate · the publication of a candidate listing

    Before
    Published
    After
    Not published
    Why
    A template line the state's list prints for write in votes. It is not a candidate, so it is off the public pages.

  247. · a candidate · the publication of a candidate listing

    Before
    Published
    After
    Not published
    Why
    A template line the state's list prints for write in votes. It is not a candidate, so it is off the public pages.

  248. · a candidate · the publication of a candidate listing

    Before
    Published
    After
    Not published
    Why
    A template line the state's list prints for write in votes. It is not a candidate, so it is off the public pages.

  249. · a candidate · the publication of a candidate listing

    Before
    Published
    After
    Not published
    Why
    A template line the state's list prints for write in votes. It is not a candidate, so it is off the public pages.

  250. · a candidate · the publication of a candidate listing

    Before
    Published
    After
    Not published
    Why
    A template line the state's list prints for write in votes. It is not a candidate, so it is off the public pages.

  251. · a candidate · the publication of a candidate listing

    Before
    Published
    After
    Not published
    Why
    No state list or filing confirms this candidacy. The record took it off its public pages until an official list or filing does.

  252. · a candidate · the publication of a candidate listing

    Before
    Published
    After
    Not published
    Why
    No state list or filing confirms this candidacy. The record took it off its public pages until an official list or filing does.

  253. · a candidate · the publication of a candidate listing

    Before
    Published
    After
    Not published
    Why
    No state list or filing confirms this candidacy. The record took it off its public pages until an official list or filing does.

  254. · a candidate · the publication of a candidate listing

    Before
    Published
    After
    Not published
    Why
    No state list or filing confirms this candidacy. The record took it off its public pages until an official list or filing does.

  255. · a candidate · the publication of a candidate listing

    Before
    Published
    After
    Not published
    Why
    No state list or filing confirms this candidacy. The record took it off its public pages until an official list or filing does.

  256. · a candidate · the publication of a candidate listing

    Before
    Published
    After
    Not published
    Why
    No state list or filing confirms this candidacy. The record took it off its public pages until an official list or filing does.

  257. · a candidate · the publication of a candidate listing

    Before
    Published
    After
    Not published
    Why
    No state list or filing confirms this candidacy. The record took it off its public pages until an official list or filing does.

  258. · a candidate · the publication of a candidate listing

    Before
    Published
    After
    Not published
    Why
    No state list or filing confirms this candidacy. The record took it off its public pages until an official list or filing does.

  259. · a candidate · the publication of a candidate listing

    Before
    Published
    After
    Not published
    Why
    No state list or filing confirms this candidacy. The record took it off its public pages until an official list or filing does.

  260. · a candidate · the publication of a candidate listing

    Before
    Published
    After
    Not published
    Why
    No state list or filing confirms this candidacy. The record took it off its public pages until an official list or filing does.

  261. · a candidate · the publication of a candidate listing

    Before
    Published
    After
    Not published
    Why
    No state list or filing confirms this candidacy. The record took it off its public pages until an official list or filing does.

  262. · a candidate · the publication of a candidate listing

    Before
    Published
    After
    Not published
    Why
    No state list or filing confirms this candidacy. The record took it off its public pages until an official list or filing does.

  263. · a candidate · the publication of a candidate listing

    Before
    Published
    After
    Not published
    Why
    No state list or filing confirms this candidacy. The record took it off its public pages until an official list or filing does.

  264. · a candidate · the publication of a candidate listing

    Before
    Published
    After
    Not published
    Why
    No state list or filing confirms this candidacy. The record took it off its public pages until an official list or filing does.

  265. · a candidate · the publication of a candidate listing

    Before
    Published
    After
    Not published
    Why
    The same candidate stands on another listing of the same race; this listing was set aside and its address redirects to the other.

  266. · a candidate · the publication of a candidate listing

    Before
    Published
    After
    Not published
    Why
    The same candidate stands on another listing of the same race; this listing was set aside and its address redirects to the other.

  267. · a candidate · the publication of a candidate listing

    Before
    Published
    After
    Not published
    Why
    The same candidate stands on another listing of the same race; this listing was set aside and its address redirects to the other.

  268. · a candidate · the publication of a candidate listing

    Before
    Published
    After
    Not published
    Why
    The same candidate stands on another listing of the same race; this listing was set aside and its address redirects to the other.

  269. · Louisville · the duplicate mark of a scorecard event

    Before
    After
    7969
    Why
    The Louisville Metro Council's six month moratorium of August 14, 2026, the same act as event 7969 (the mayor signing it that day); marked its duplicate when it moved to the Louisville row, its source kept as a citation on 7969 (October 20, 2026).

  270. · Louisville · the scorecard row of a scorecard event

    Before
    KY/louisville-metro
    After
    KY/louisville
    Why
    Louisville Metro is the consolidated government of Louisville and Jefferson County, and its Metro Council is the city's council; the record files the council's acts on the Louisville row, and the Census Bureau names no place Louisville Metro. Moved under the record's rules (October 20, 2026).

  271. · a record · the summary of a news item

    Before
    Pennsylvania H.B. 2535, 2025-2026 Regular Session: went to committee on September 29, 2026. Matched on large load.
    After
    H.B. 2535 in Pennsylvania was sent to a committee on September 29, 2026.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  272. · a record · the summary of a news item

    Before
    New Jersey A. 4801, 2026-2027 Regular Session: went to committee on September 28, 2026. Matched on large load.
    After
    A. 4801 in New Jersey was sent to a committee on September 28, 2026.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  273. · a record · the summary of a news item

    Before
    Virginia S.B. 417, 2026 Regular Session: went to committee on February 4, 2026. Matched on data center.
    After
    S.B. 417 in Virginia was sent to a committee on February 4, 2026.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  274. · a record · the summary of a news item

    Before
    Virginia S.B. 334, 2026 Regular Session: went to committee on February 27, 2026. Matched on data center.
    After
    S.B. 334 in Virginia was sent to a committee on February 27, 2026.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  275. · a record · the summary of a news item

    Before
    Virginia H.B. 658, 2026 Regular Session: went to committee on January 13, 2026. Matched on data center.
    After
    H.B. 658 in Virginia was sent to a committee on January 13, 2026.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  276. · a record · the summary of a news item

    Before
    Pennsylvania S.B. 1442, 2025-2026 Regular Session: went to committee on September 25, 2026. Matched on data center.
    After
    S.B. 1442 in Pennsylvania was sent to a committee on September 25, 2026.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  277. · a record · the summary of a news item

    Before
    Pennsylvania S.B. 1459, 2025-2026 Regular Session: went to committee on September 24, 2026. Matched on data center.
    After
    S.B. 1459 in Pennsylvania was sent to a committee on September 24, 2026.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  278. · a record · the summary of a news item

    Before
    Pennsylvania S.B. 1455, 2025-2026 Regular Session: went to committee on September 24, 2026. Matched on data center.
    After
    S.B. 1455 in Pennsylvania was sent to a committee on September 24, 2026.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  279. · a record · the summary of a news item

    Before
    Pennsylvania S.B. 1470, 2025-2026 Regular Session: went to committee on September 24, 2026. Matched on data center.
    After
    S.B. 1470 in Pennsylvania was sent to a committee on September 24, 2026.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  280. · a record · the summary of a news item

    Before
    Pennsylvania S.B. 1460, 2025-2026 Regular Session: went to committee on September 24, 2026. Matched on data center.
    After
    S.B. 1460 in Pennsylvania was sent to a committee on September 24, 2026.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  281. · a record · the summary of a news item

    Before
    Pennsylvania S.B. 1461, 2025-2026 Regular Session: went to committee on September 24, 2026. Matched on data center, hyperscale.
    After
    S.B. 1461 in Pennsylvania was sent to a committee on September 24, 2026.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  282. · a record · the summary of a news item

    Before
    Pennsylvania S.B. 1469, 2025-2026 Regular Session: went to committee on September 24, 2026. Matched on data center, large load, hyperscale.
    After
    S.B. 1469 in Pennsylvania was sent to a committee on September 24, 2026.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  283. · a record · the summary of a news item

    Before
    Michigan H.B. 6388, 103rd Legislature: went to committee on September 24, 2026. Matched on data center.
    After
    H.B. 6388 in Michigan was sent to a committee on September 24, 2026.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  284. · a record · the summary of a news item

    Before
    Michigan H.B. 6391, 103rd Legislature: went to committee on September 24, 2026. Matched on data center.
    After
    H.B. 6391 in Michigan was sent to a committee on September 24, 2026.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  285. · a record · the summary of a news item

    Before
    United States H.R. 10570, 119th Congress: went to committee on September 24, 2026. Matched on data center.
    After
    H.R. 10570 in Congress was sent to a committee on September 24, 2026.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  286. · a record · the summary of a news item

    Before
    West Virginia H.B. 5611, 2026 Regular Session: went to committee on February 16, 2026. Matched on data center.
    After
    H.B. 5611 in West Virginia was sent to a committee on February 16, 2026.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  287. · a record · the summary of a news item

    Before
    West Virginia H.B. 4832, 2026 Regular Session: went to committee on January 26, 2026. Matched on data center.
    After
    H.B. 4832 in West Virginia was sent to a committee on January 26, 2026.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  288. · a record · the summary of a news item

    Before
    West Virginia H.B. 4683, 2026 Regular Session: went to committee on January 21, 2026. Matched on data center.
    After
    H.B. 4683 in West Virginia was sent to a committee on January 21, 2026.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  289. · a record · the summary of a news item

    Before
    West Virginia H.B. 4509, 2026 Regular Session: went to committee on January 19, 2026. Matched on data center.
    After
    H.B. 4509 in West Virginia was sent to a committee on January 19, 2026.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  290. · a record · the summary of a news item

    Before
    Tennessee H.B. 2054, 114th General Assembly: went to committee on February 4, 2026. Matched on data center.
    After
    H.B. 2054 in Tennessee was sent to a committee on February 4, 2026.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  291. · a record · the summary of a news item

    Before
    Tennessee S.B. 2053, 114th General Assembly: was introduced on January 22, 2026. Matched on digital asset mining. Indirect match.
    After
    S.B. 2053 in Tennessee was introduced on January 22, 2026.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  292. · a record · the summary of a news item

    Before
    Tennessee S.B. 1999, 114th General Assembly: was introduced on January 22, 2026. Matched on data center.
    After
    S.B. 1999 in Tennessee was introduced on January 22, 2026.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  293. · a record · the summary of a news item

    Before
    Tennessee H.B. 1827, 114th General Assembly: went to committee on March 24, 2026. Matched on digital asset mining. Indirect match.
    After
    H.B. 1827 in Tennessee was sent to a committee on March 24, 2026.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  294. · a record · the summary of a news item

    Before
    Tennessee S.B. 875, 114th General Assembly: was signed on May 27, 2025. Matched on data center.
    After
    S.B. 875 in Tennessee was signed into law on May 27, 2025.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  295. · a record · the summary of a news item

    Before
    Tennessee H.B. 780, 114th General Assembly: was signed on May 27, 2025. Matched on data center.
    After
    H.B. 780 in Tennessee was signed into law on May 27, 2025.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  296. · a record · the summary of a news item

    Before
    Tennessee S.B. 427, 114th General Assembly: was introduced on January 28, 2025. Matched on data center.
    After
    S.B. 427 in Tennessee was introduced on January 28, 2025.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  297. · a record · the summary of a news item

    Before
    Tennessee H.B. 330, 114th General Assembly: went to committee on February 3, 2025. Matched on data center.
    After
    H.B. 330 in Tennessee was sent to a committee on February 3, 2025.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  298. · a record · the summary of a news item

    Before
    South Carolina H. 5484, 126th General Assembly: went to committee on April 1, 2026. Matched on data center.
    After
    H. 5484 in South Carolina was sent to a committee on April 1, 2026.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  299. · a record · the summary of a news item

    Before
    South Carolina H. 5122, 126th General Assembly: was signed on June 3, 2026. Matched on data center.
    After
    H. 5122 in South Carolina was signed into law on June 3, 2026.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  300. · a record · the summary of a news item

    Before
    South Carolina S. 784, 126th General Assembly: went to committee on January 13, 2026. Matched on data center.
    After
    S. 784 in South Carolina was sent to a committee on January 13, 2026.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  301. · a record · the summary of a news item

    Before
    South Carolina S. 163, 126th General Assembly: was signed on June 2, 2026. Matched on digital asset mining. Indirect match.
    After
    S. 163 in South Carolina was signed into law on June 2, 2026.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  302. · a record · the summary of a news item

    Before
    Pennsylvania H.R. 630, 2025-2026 Regular Session: went to committee on September 24, 2026. Matched on data center.
    After
    H.R. 630 in Pennsylvania was sent to a committee on September 24, 2026.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  303. · a record · the summary of a news item

    Before
    Oregon H.B. 4084, 2026 Legislative Measures: was signed on April 6, 2026. Matched on data center.
    After
    H.B. 4084 in Oregon was signed into law on April 6, 2026.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  304. · a record · the summary of a news item

    Before
    Ohio H.B. 142, 136th General Assembly: was introduced on March 3, 2025. Matched on large load.
    After
    H.B. 142 in Ohio was introduced on March 3, 2025.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  305. · a record · the summary of a news item

    Before
    Ohio S.B. 103, 136th General Assembly: was signed on March 20, 2026. Matched on large load.
    After
    S.B. 103 in Ohio was signed into law on March 20, 2026.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  306. · a record · the summary of a news item

    Before
    Mississippi H.B. 4045, 2026 Regular Session: died when the session adjourned on February 25, 2026. Matched on data center.
    After
    H.B. 4045 in Mississippi died when the session ended on February 25, 2026.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  307. · a record · the summary of a news item

    Before
    Maryland S.B. 853, 2026 Regular Session: went to committee on February 6, 2026. Matched on data center.
    After
    S.B. 853 in Maryland was sent to a committee on February 6, 2026.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  308. · a record · the summary of a news item

    Before
    Maryland H.B. 799, 2026 Regular Session: went to committee on February 4, 2026. Matched on data center.
    After
    H.B. 799 in Maryland was sent to a committee on February 4, 2026.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  309. · a record · the summary of a news item

    Before
    Kentucky S.B. 32, 2026 Regular Session: died when the session adjourned on February 18, 2026. Matched on digital asset mining. Indirect match.
    After
    S.B. 32 in Kentucky died when the session ended on February 18, 2026.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  310. · a record · the summary of a news item

    Before
    Wyoming H.B. 64, 2013 Regular Session: was signed on February 14, 2013. Matched on data center. Enacted before 2025.
    After
    H.B. 64 in Wyoming was signed into law on February 14, 2013.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  311. · a record · the summary of a news item

    Before
    Washington S.B. 6789, 2009-2010 Regular Session: was signed on March 25, 2010. Matched on data center. Enacted before 2025.
    After
    S.B. 6789 in Washington was signed into law on March 25, 2010.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  312. · a record · the summary of a news item

    Before
    Washington H.B. 1846, 2021-2022 Regular Session: was signed on March 31, 2022. Matched on data center. Enacted before 2025.
    After
    H.B. 1846 in Washington was signed into law on March 31, 2022.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  313. · a record · the summary of a news item

    Before
    Texas H.B. 1223, 83rd Legislature Regular Session: was signed on June 14, 2013. Matched on data center. Enacted before 2025.
    After
    H.B. 1223 in Texas was signed into law on June 14, 2013.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  314. · a record · the summary of a news item

    Before
    Texas H.B. 2712, 84th Legislature Regular Session: was signed on June 10, 2015. Matched on data center. Enacted before 2025.
    After
    H.B. 2712 in Texas was signed into law on June 10, 2015.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  315. · a record · the summary of a news item

    Before
    Texas H.B. 4038, 85th Legislature Regular Session: was signed on June 1, 2017. Matched on data center. Enacted before 2025.
    After
    H.B. 4038 in Texas was signed into law on June 1, 2017.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  316. · a record · the summary of a news item

    Before
    Texas S.B. 1929, 88th Legislature Regular Session: was signed on June 9, 2023. Matched on large load. Enacted before 2025.
    After
    S.B. 1929 in Texas was signed into law on June 9, 2023.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  317. · a record · the summary of a news item

    Before
    Tennessee S.B. 2537, 109th General Assembly: was signed on May 2, 2016. Matched on data center. Enacted before 2025.
    After
    S.B. 2537 in Tennessee was signed into law on May 2, 2016.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  318. · a record · the summary of a news item

    Before
    Tennessee H.B. 1535, 109th General Assembly: was signed on May 2, 2016. Matched on data center. Enacted before 2025.
    After
    H.B. 1535 in Tennessee was signed into law on May 2, 2016.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  319. · a record · the summary of a news item

    Before
    Tennessee S.B. 2266, 110th General Assembly: was signed on May 18, 2018. Matched on data center, computing facility. Enacted before 2025.
    After
    S.B. 2266 in Tennessee was signed into law on May 18, 2018.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  320. · a record · the summary of a news item

    Before
    Tennessee H.B. 2531, 110th General Assembly: was signed on May 18, 2018. Matched on data center, computing facility. Enacted before 2025.
    After
    H.B. 2531 in Tennessee was signed into law on May 18, 2018.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  321. · a record · the summary of a news item

    Before
    Tennessee S.B. 2583, 113th General Assembly: was signed on May 13, 2024. Matched on data center. Enacted before 2025.
    After
    S.B. 2583 in Tennessee was signed into law on May 13, 2024.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  322. · a record · the summary of a news item

    Before
    Tennessee H.B. 2182, 113th General Assembly: was signed on May 13, 2024. Matched on data center. Enacted before 2025.
    After
    H.B. 2182 in Tennessee was signed into law on May 13, 2024.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  323. · a record · the summary of a news item

    Before
    Pennsylvania H.B. 2370, 2015-2016 Regular Session: was signed on November 21, 2016. Matched on data center. Enacted before 2025.
    After
    H.B. 2370 in Pennsylvania was signed into law on November 21, 2016.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  324. · a record · the summary of a news item

    Before
    Pennsylvania S.R. 264, 2019-2020 Regular Session: was signed on October 29, 2019. Matched on data center. Enacted before 2025.
    After
    S.R. 264 in Pennsylvania was signed into law on October 29, 2019.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  325. · a record · the summary of a news item

    Before
    Pennsylvania H.R. 559, 2019-2020 Regular Session: was signed on October 30, 2019. Matched on data center. Enacted before 2025.
    After
    H.R. 559 in Pennsylvania was signed into law on October 30, 2019.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  326. · a record · the summary of a news item

    Before
    Pennsylvania H.B. 262, 2019-2020 Regular Session: was sent to the executive on June 28, 2019. Matched on data center. Enacted before 2025.
    After
    H.B. 262 in Pennsylvania was sent to the governor on June 28, 2019.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  327. · a record · the summary of a news item

    Before
    Pennsylvania H.B. 1342, 2021-2022 Regular Session: was sent to the executive on July 8, 2022. Matched on data center. Enacted before 2025.
    After
    H.B. 1342 in Pennsylvania was sent to the governor on July 8, 2022.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  328. · a record · the summary of a news item

    Before
    Pennsylvania H.B. 952, 2021-2022 Regular Session: was signed on June 30, 2021. Matched on data center. Enacted before 2025.
    After
    H.B. 952 in Pennsylvania was signed into law on June 30, 2021.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  329. · a record · the summary of a news item

    Before
    Oregon S.B. 611, 2015 Legislative Measures: was signed on April 7, 2015. Matched on data center. Enacted before 2025.
    After
    S.B. 611 in Oregon was signed into law on April 7, 2015.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  330. · a record · the summary of a news item

    Before
    Oklahoma H.B. 3594, 2024 Regular Session: was signed on May 13, 2024. Matched on digital asset mining. Indirect match. Enacted before 2025.
    After
    H.B. 3594 in Oklahoma was signed into law on May 13, 2024.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  331. · a record · the summary of a news item

    Before
    Oklahoma H.B. 1600, 2024 Regular Session: was signed on May 30, 2024. Matched on digital asset mining. Indirect match. Enacted before 2025.
    After
    H.B. 1600 in Oklahoma was signed into law on May 30, 2024.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  332. · a record · the summary of a news item

    Before
    Ohio S.B. 243, 130th General Assembly (2013-2014): was signed on December 19, 2014. Matched on data center. Enacted before 2025.
    After
    S.B. 243 in Ohio was signed into law on December 19, 2014.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  333. · a record · the summary of a news item

    Before
    North Dakota 1089, 64th Legislative Assembly: was signed on April 10, 2015. Matched on data center, sales tax exemption. Enacted before 2025.
    After
    Bill 1089 in North Dakota was signed into law on April 10, 2015.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  334. · a record · the summary of a news item

    Before
    North Dakota 2137, 67th Legislative Assembly: was signed on April 22, 2021. Matched on data center. Enacted before 2025.
    After
    Bill 2137 in North Dakota was signed into law on April 22, 2021.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  335. · a record · the summary of a news item

    Before
    New York A. 7389, 2021-2022 General Assembly: was sent to the executive on November 22, 2022. Matched on cryptocurrency mining, moratorium. Indirect match. Enacted before 2025.
    After
    A. 7389 in New York was sent to the governor on November 22, 2022.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  336. · a record · the summary of a news item

    Before
    Nevada S.B. 170, 78th Legislature (2015): was signed on June 9, 2015. Matched on data center. Enacted before 2025.
    After
    S.B. 170 in Nevada was signed into law on June 9, 2015.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  337. · a record · the summary of a news item

    Before
    Nevada S.B. 547, 80th Legislature (2019): was signed on June 13, 2019. Matched on data center. Enacted before 2025.
    After
    S.B. 547 in Nevada was signed into law on June 13, 2019.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  338. · a record · the summary of a news item

    Before
    Nebraska L.B. 1118, 102nd Legislature: was signed on March 7, 2012. Matched on data center. Enacted before 2025.
    After
    L.B. 1118 in Nebraska was signed into law on March 7, 2012.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  339. · a record · the summary of a news item

    Before
    Nebraska L.B. 1080, 102nd Legislature: was signed on April 11, 2012. Matched on data center. Enacted before 2025.
    After
    L.B. 1080 in Nebraska was signed into law on April 11, 2012.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  340. · a record · the summary of a news item

    Before
    Montana S.B. 359, 2017 Regular Session: was signed on May 22, 2017. Matched on data center. Enacted before 2025.
    After
    S.B. 359 in Montana was signed into law on May 22, 2017.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  341. · a record · the summary of a news item

    Before
    Montana H.B. 507, 2019 Regular Session: was signed on May 8, 2019. Matched on data center. Enacted before 2025.
    After
    H.B. 507 in Montana was signed into law on May 8, 2019.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  342. · a record · the summary of a news item

    Before
    Indiana H.B. 1210, 2026 Regular Session: was signed on March 12, 2026. Matched on data center.
    After
    H.B. 1210 in Indiana was signed into law on March 12, 2026.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  343. · a record · the summary of a news item

    Before
    Indiana H.B. 1333, 2026 Regular Session: went to committee on February 5, 2026. Matched on data center.
    After
    H.B. 1333 in Indiana was sent to a committee on February 5, 2026.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  344. · a record · the summary of a news item

    Before
    Indiana S.B. 234, 2026 Regular Session: went to committee on January 8, 2026. Matched on large load.
    After
    S.B. 234 in Indiana was sent to a committee on January 8, 2026.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  345. · a record · the summary of a news item

    Before
    Indiana S.B. 83, 2026 Regular Session: went to committee on December 8, 2025. Matched on data center.
    After
    S.B. 83 in Indiana was sent to a committee on December 8, 2025.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  346. · a record · the summary of a news item

    Before
    Indiana H.B. 1042, 2026 Regular Session: was signed on March 3, 2026. Matched on digital asset mining. Indirect match.
    After
    H.B. 1042 in Indiana was signed into law on March 3, 2026.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  347. · a record · the summary of a news item

    Before
    Illinois S.B. 2502, 104th General Assembly: went to committee on April 11, 2025. Matched on data center.
    After
    S.B. 2502 in Illinois was sent to a committee on April 11, 2025.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  348. · a record · the summary of a news item

    Before
    Illinois H.B. 3587, 104th General Assembly: went to committee on February 18, 2025. Matched on data center.
    After
    H.B. 3587 in Illinois was sent to a committee on February 18, 2025.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  349. · a record · the summary of a news item

    Before
    Illinois S.B. 4004, 104th General Assembly: went to committee on May 22, 2026. Matched on data center.
    After
    S.B. 4004 in Illinois was sent to a committee on May 22, 2026.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  350. · a record · the summary of a news item

    Before
    Illinois S.B. 2290, 104th General Assembly: went to committee on June 2, 2025. Matched on data center.
    After
    S.B. 2290 in Illinois was sent to a committee on June 2, 2025.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  351. · a record · the summary of a news item

    Before
    Illinois H.B. 5607, 104th General Assembly: went to committee on March 27, 2026. Matched on data center.
    After
    H.B. 5607 in Illinois was sent to a committee on March 27, 2026.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  352. · a record · the summary of a news item

    Before
    Illinois S.B. 3030, 104th General Assembly: went to committee on May 22, 2026. Matched on cryptocurrency mining. Indirect match.
    After
    S.B. 3030 in Illinois was sent to a committee on May 22, 2026.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  353. · a record · the summary of a news item

    Before
    Illinois S.B. 1429, 104th General Assembly: went to committee on January 31, 2025. Matched on cryptocurrency mining. Indirect match.
    After
    S.B. 1429 in Illinois was sent to a committee on January 31, 2025.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  354. · a record · the summary of a news item

    Before
    Illinois H.B. 4116, 104th General Assembly: went to committee on October 15, 2025. Matched on large load, colocation.
    After
    H.B. 4116 in Illinois was sent to a committee on October 15, 2025.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  355. · a record · the summary of a news item

    Before
    Illinois H.B. 4120, 104th General Assembly: went to committee on October 15, 2025. Matched on large load, colocation.
    After
    H.B. 4120 in Illinois was sent to a committee on October 15, 2025.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  356. · a record · the summary of a news item

    Before
    United States H.R. 10467, 119th Congress: went to committee on September 16, 2026. Matched on data center.
    After
    H.R. 10467 in Congress was sent to a committee on September 16, 2026.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  357. · a record · the summary of a news item

    Before
    United States H.R. 10579, 119th Congress: went to committee on September 24, 2026. Matched on large load.
    After
    H.R. 10579 in Congress was sent to a committee on September 24, 2026.
    Why
    The bill watch's match words taken out and the sentence written in plain words from the stage and the day it states (the editor's word of 2026-10-20).

  358. · Derek Dooley · the end date of a candidate listing

    Before
    2026-05-19
    After
    2026-06-16
    Why
    The source the record cites reports the runoff held on 2026-06-16, so the loss is dated that day; it had been filed under the primary's day.

  359. · Rob Adkerson · the end date of a candidate listing

    Before
    2026-05-19
    After
    2026-06-16
    Why
    The source the record cites reports the runoff held on 2026-06-16, so the loss is dated that day; it had been filed under the primary's day.

  360. · Casey Norton · the end date of a candidate listing

    Before
    2026-05-19
    After
    2026-06-16
    Why
    The source the record cites reports the runoff held on 2026-06-16, so the loss is dated that day; it had been filed under the primary's day.

  361. · Joyce Marie Griggs · the end date of a candidate listing

    Before
    2026-05-19
    After
    2026-06-16
    Why
    The source the record cites reports the runoff held on 2026-06-16, so the loss is dated that day; it had been filed under the primary's day.

  362. · h5-virginia-va · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    the record's rules: the entry describes another company's project and was filed on this record by the extraction; returned to draft on the editor's word (2026-10-13)

  363. · h5-virginia-va · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    the record's rules: the entry describes another company's project and was filed on this record by the extraction; returned to draft on the editor's word (2026-10-13)

  364. · h5-virginia-va · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    the record's rules: the entry describes another company's project and was filed on this record by the extraction; returned to draft on the editor's word (2026-10-13)

  365. · microsoft-wellington-data-center-prince-william-va · the record of a timeline entry

    Before
    h5-virginia-va
    After
    microsoft-wellington-data-center-prince-william-va
    Why
    The entry describes Microsoft's MNZ07 Wellington Data Center in Prince William County, which its source reports, and not an H5 site; it was filed on the H5 Virginia draft by the extraction and moves to the Microsoft record on the editor's word (2026-10-13).

  366. · microsoft-wellington-data-center-prince-william-va · the record of a timeline entry

    Before
    h5-virginia-va
    After
    microsoft-wellington-data-center-prince-william-va
    Why
    The entry describes Microsoft's MNZ07 Wellington Data Center in Prince William County, which its source reports, and not an H5 site; it was filed on the H5 Virginia draft by the extraction and moves to the Microsoft record on the editor's word (2026-10-13).

  367. · microsoft-wellington-data-center-prince-william-va · the record of a timeline entry

    Before
    h5-virginia-va
    After
    microsoft-wellington-data-center-prince-william-va
    Why
    The entry describes Microsoft's MNZ07 Wellington Data Center in Prince William County, which its source reports, and not an H5 site; it was filed on the H5 Virginia draft by the extraction and moves to the Microsoft record on the editor's word (2026-10-13).

  368. · microsoft-wellington-data-center-prince-william-va · the record of a timeline entry

    Before
    h5-virginia-va
    After
    microsoft-wellington-data-center-prince-william-va
    Why
    The entry describes Microsoft's MNZ07 Wellington Data Center in Prince William County, which its source reports, and not an H5 site; it was filed on the H5 Virginia draft by the extraction and moves to the Microsoft record on the editor's word (2026-10-13).

  369. · microsoft-wellington-data-center-prince-william-va · the record of a timeline entry

    Before
    h5-virginia-va
    After
    microsoft-wellington-data-center-prince-william-va
    Why
    The entry describes Microsoft's MNZ07 Wellington Data Center in Prince William County, which its source reports, and not an H5 site; it was filed on the H5 Virginia draft by the extraction and moves to the Microsoft record on the editor's word (2026-10-13).

  370. · microsoft-wellington-data-center-prince-william-va · the record of a timeline entry

    Before
    h5-virginia-va
    After
    microsoft-wellington-data-center-prince-william-va
    Why
    The entry describes Microsoft's MNZ07 Wellington Data Center in Prince William County, which its source reports, and not an H5 site; it was filed on the H5 Virginia draft by the extraction and moves to the Microsoft record on the editor's word (2026-10-13).

  371. · microsoft-wellington-data-center-prince-william-va · the record of a timeline entry

    Before
    h5-virginia-va
    After
    microsoft-wellington-data-center-prince-william-va
    Why
    The entry describes Microsoft's MNZ07 Wellington Data Center in Prince William County, which its source reports, and not an H5 site; it was filed on the H5 Virginia draft by the extraction and moves to the Microsoft record on the editor's word (2026-10-13).

  372. · microsoft-wellington-data-center-prince-william-va · the record of a timeline entry

    Before
    h5-virginia-va
    After
    microsoft-wellington-data-center-prince-william-va
    Why
    The entry describes Microsoft's MNZ07 Wellington Data Center in Prince William County, which its source reports, and not an H5 site; it was filed on the H5 Virginia draft by the extraction and moves to the Microsoft record on the editor's word (2026-10-13).

  373. · microsoft-wellington-data-center-prince-william-va · the record of a timeline entry

    Before
    h5-virginia-va
    After
    microsoft-wellington-data-center-prince-william-va
    Why
    The entry describes Microsoft's MNZ07 Wellington Data Center in Prince William County, which its source reports, and not an H5 site; it was filed on the H5 Virginia draft by the extraction and moves to the Microsoft record on the editor's word (2026-10-13).

  374. · microsoft-compass-creek-data-center-leesburg-va · the record of a timeline entry

    Before
    h5-virginia-va
    After
    microsoft-compass-creek-data-center-leesburg-va
    Why
    The entry describes Microsoft's data center at 19515 Compass Creek Parkway in Leesburg, which its source names, and not an H5 site; it was filed on the H5 Virginia draft by the extraction and moves to the Microsoft Leesburg record on the editor's word (2026-10-13).

  375. · the ended how of 6 candidacies

    Before
    Listed on the race page as a candidate on the November 3, 2026 ballot.
    After
    Off the race and leaders pages; the person's page says the candidate is not on the November 3, 2026 ballot as the state certified it, with its source.
    Why
    Texas: 6 independent candidates (two for governor, four for the U.S. House) whose declarations the Secretary of State's candidate list marks REJECTED come off the race pages, which list only the names the certified ballot prints. On the editor's word of October 19, 2026.

  376. · Missoula County · the duplicate mark of a scorecard event

    Before
    After
    8175
    Why
    The same July 9, 2026 moratorium as event 8175 on the Missoula County row; marked its duplicate (October 16, 2026).

  377. · Missoula County · the duplicate mark of a scorecard event

    Before
    After
    8175
    Why
    The same July 9, 2026 moratorium as event 8175 on the Missoula County row; marked its duplicate (October 16, 2026).

  378. · Missoula County · the rating of a scorecard event

    Before
    case by case
    After
    restrictive
    Why
    The event takes its new row's rating when it moves; no rating travels with it (October 16, 2026).

  379. · Missoula County · the rating of a scorecard event

    Before
    case by case
    After
    restrictive
    Why
    The event takes its new row's rating when it moves; no rating travels with it (October 16, 2026).

  380. · Missoula County · the scorecard row of a scorecard event

    Before
    MT/montana
    After
    MT/missoula-county
    Why
    Missoula County's commissioners adopted the moratorium; a county's act belongs on its own row, not the state's. Moved under the record's rules (October 16, 2026).

  381. · Missoula County · the scorecard row of a scorecard event

    Before
    MT/montana
    After
    MT/missoula-county
    Why
    Missoula County's commissioners adopted the moratorium; a county's act belongs on its own row, not the state's. Moved under the record's rules (October 16, 2026).

  382. · Montgomery County · the duplicate mark of a scorecard event

    Before
    After
    8620
    Why
    The same October 6, 2026 Montgomery County Commission discussion of draft zoning rules as event 8620, from the same report; marked its duplicate. On the editor's word of October 16, 2026.

  383. · Montgomery County · the duplicate mark of a scorecard event

    Before
    After
    8620
    Why
    The same October 6, 2026 Montgomery County Commission discussion of draft zoning rules as event 8620, from the same report; marked its duplicate. On the editor's word of October 16, 2026.

  384. · Montgomery County · the duplicate mark of a scorecard event

    Before
    After
    8620
    Why
    The same October 6, 2026 Montgomery County Commission discussion of draft zoning rules as event 8620, from the same report; marked its duplicate. On the editor's word of October 16, 2026.

  385. · Montgomery County · the duplicate mark of a scorecard event

    Before
    After
    8620
    Why
    The same October 6, 2026 Montgomery County Commission discussion of draft zoning rules as event 8620, from the same report; marked its duplicate. On the editor's word of October 16, 2026.

  386. · Montgomery County · the duplicate mark of a scorecard event

    Before
    After
    8620
    Why
    The same October 6, 2026 Montgomery County Commission discussion of draft zoning rules as event 8620, from the same report; marked its duplicate. On the editor's word of October 16, 2026.

  387. · Memphis · the kind of a scorecard event

    Before
    moratorium
    After
    hearing
    Why
    The council voted to postpone its vote on a moratorium; that is a hearing, not a moratorium. On the editor's word of October 16, 2026.

  388. · a record · the publication of a scorecard event

    Before
    published
    After
    draft
    Why
    A count of generation the commission approved in 2025, dated by the year alone and not about data centers; it comes off the rules list. On the editor's word of October 16, 2026.

  389. · a record · the publication of a scorecard event

    Before
    published
    After
    draft
    Why
    The Attorney General's announcement that he will investigate data center developments is a statement, not an act of the state; it comes off the rules list and stays on the record as his statement. On the editor's word of October 16, 2026.

  390. · Applied Digital Polaris Forge 3 (Oliver County) · the name of a record

    Before
    Applied Digital North Dakota (Oliver County third data center)
    After
    Applied Digital Polaris Forge 3 (Oliver County)
    Why
    The campus's own name, as Montana-Dakota Utilities' release names it; the old name stays as an alias. On the editor's word of October 16, 2026.

  391. · Google Papillion data center · the record of a timeline entry

    Before
    meta-sarpy-data-center-ne
    After
    google-papillion-data-center-ne
    Why
    The entry is Google's data center in Sarpy County, as its source (3 News Now) says, not Meta's; moved to the Google Papillion record on the editor's word of October 16, 2026.

  392. · Applied Digital Polaris Forge 1 (Ellendale) · the record of a timeline entry

    Before
    applied-digital-north-dakota-oliver-county-third-data-center-nd
    After
    applied-digital-polaris-forge-1-ellendale-nd
    Why
    The entry describes Applied Digital's Polaris Forge 1 at Ellendale, Dickey County, which its source names; it had been filed on the Oliver County record, which mixed the three campuses. Moved on the editor's word of October 16, 2026.

  393. · Applied Digital Polaris Forge 1 (Ellendale) · the record of a timeline entry

    Before
    applied-digital-north-dakota-oliver-county-third-data-center-nd
    After
    applied-digital-polaris-forge-1-ellendale-nd
    Why
    The entry describes Applied Digital's Polaris Forge 1 at Ellendale, Dickey County, which its source names; it had been filed on the Oliver County record, which mixed the three campuses. Moved on the editor's word of October 16, 2026.

  394. · Applied Digital Polaris Forge 2 (Harwood) · the record of a timeline entry

    Before
    applied-digital-north-dakota-oliver-county-third-data-center-nd
    After
    applied-digital-harwood-data-center-nd
    Why
    The entry describes Applied Digital's Polaris Forge 2 at Harwood, Cass County, which its source names; it had been filed on the Oliver County record, which mixed the three campuses. Moved on the editor's word of October 16, 2026.

  395. · Applied Digital Polaris Forge 2 (Harwood) · the record of a timeline entry

    Before
    applied-digital-north-dakota-oliver-county-third-data-center-nd
    After
    applied-digital-harwood-data-center-nd
    Why
    The entry describes Applied Digital's Polaris Forge 2 at Harwood, Cass County, which its source names; it had been filed on the Oliver County record, which mixed the three campuses. Moved on the editor's word of October 16, 2026.

  396. · Applied Digital Polaris Forge 2 (Harwood) · the record of a timeline entry

    Before
    applied-digital-north-dakota-oliver-county-third-data-center-nd
    After
    applied-digital-harwood-data-center-nd
    Why
    The entry describes Applied Digital's Polaris Forge 2 at Harwood, Cass County, which its source names; it had been filed on the Oliver County record, which mixed the three campuses. Moved on the editor's word of October 16, 2026.

  397. · Applied Digital Polaris Forge 3 (Oliver County) · the location of a record

    Before
    47.115, -101.30028 (county)
    After
    47.1180789, -101.3314198 (county)
    Why
    The record mixed Applied Digital's three North Dakota campuses; it keeps Polaris Forge 3 in Oliver County at the county level, and the Harwood (Cass County) and Ellendale (Dickey County) entries move to those campuses' records. On the editor's word of October 16, 2026.

  398. · Meta Henrico Data Center · the location of a record

    Before
    37.4375205, -77.300333 (city)
    After
    37.4375205, -77.300333 (county)
    Why
    Henrico is the county; no city of that name exists, so the record files at the county level. On the editor's word of October 16, 2026.

  399. · Switch Tahoe Reno campus · the location of a record

    Before
    39.5491398, -119.8476064 (city)
    After
    39.4383853, -119.5246462 (county)
    Why
    The campus is in the Tahoe Reno Industrial Center, unincorporated Storey County; Reno is in Washoe County, and the record had placed it at Reno's center. On the editor's word of October 16, 2026.

  400. · Meta Sarpy Data Center · the location of a record

    Before
    41.1150635, -96.1091254 (city)
    After
    41.1150635, -96.1091254 (county)
    Why
    No place is named Sarpy; Meta's own list names the county, so the record files at the county level. On the editor's word of October 16, 2026.

  401. · Quantica Broadview Data Center · the location of a record

    Before
    45.6383, -109.252 (county)
    After
    46.09879, -108.87887 (city)
    Why
    Broadview is in Yellowstone County, whose commissioners the record's sources report on; the record had filed it under Stillwater County. On the editor's word of October 16, 2026.

  402. · Amazon Clinton Data Center · the location of a record

    Before
    32.6119, -90.0317 (county)
    After
    32.35444, -90.34189 (city)
    Why
    Clinton, Mississippi is in Hinds County; the record had filed it under Madison County and placed it at Canton. On the editor's word of October 16, 2026.

  403. · PathOne Arthur Data Center · the location of a record

    Before
    43.08778, -95.62778 (county)
    After
    42.33535, -95.34691 (city)
    Why
    Arthur, Iowa is in Ida County, as the record's source (KTIV, Sioux City) reports; the record had filed it under O'Brien County. On the editor's word of October 16, 2026.

  404. · ValorC3 Boise Data Center · the location of a record

    Before
    43.82861, -115.83222 (county)
    After
    43.60023, -116.2298 (city)
    Why
    Boise is in Ada County; the record had filed it under Boise County and placed it at Idaho City, that county's seat. On the editor's word of October 16, 2026.

  405. · Applied Digital Polaris Forge 3 (Oliver County) · the city of a record

    Before
    Harwood area
    After
    Why
    The record mixed Applied Digital's three North Dakota campuses; it keeps Polaris Forge 3 in Oliver County at the county level, and the Harwood (Cass County) and Ellendale (Dickey County) entries move to those campuses' records. On the editor's word of October 16, 2026.

  406. · Starwood Digital Ventures Mason County Data Center · the city of a record

    Before
    West Columbia
    After
    Why
    West Columbia is an unincorporated community and not a Census place, so the record files at the county level in Mason County. On the editor's word of October 16, 2026.

  407. · Edgeconnex Richmond Holdings LLC · the city of a record

    Before
    Richmond
    After
    Why
    1450 East Parham Road is in unincorporated Henrico County with a Richmond mailing address; the City of Richmond is independent and not in Henrico, so the record files at the county level; the address and the permit point stay. On the editor's word of October 16, 2026.

  408. · Meta Henrico Data Center · the city of a record

    Before
    Henrico
    After
    Why
    Henrico is the county; no city of that name exists, so the record files at the county level. On the editor's word of October 16, 2026.

  409. · Carmel Church Data Center · the city of a record

    Before
    Caroline
    After
    Why
    Caroline is the county, not a town, and Carmel Church is not a Census place, so the record files at the county level; the permit point stays. On the editor's word of October 16, 2026.

  410. · Switch Tahoe Reno campus · the city of a record

    Before
    Reno
    After
    Why
    The campus is in the Tahoe Reno Industrial Center, unincorporated Storey County; Reno is in Washoe County, and the record had placed it at Reno's center. On the editor's word of October 16, 2026.

  411. · Meta Sarpy Data Center · the city of a record

    Before
    Sarpy
    After
    Why
    No place is named Sarpy; Meta's own list names the county, so the record files at the county level. On the editor's word of October 16, 2026.

  412. · Atmosphere Dickerson data center · the city of a record

    Before
    Dickerson
    After
    Why
    Dickerson is an unincorporated community and not a Census place, so the record files at the county level in Montgomery County. On the editor's word of October 16, 2026.

  413. · Quantica Broadview Data Center · the county of a record

    Before
    Stillwater
    After
    Yellowstone
    Why
    Broadview is in Yellowstone County, whose commissioners the record's sources report on; the record had filed it under Stillwater County. On the editor's word of October 16, 2026.

  414. · Amazon Clinton Data Center · the county of a record

    Before
    Madison
    After
    Hinds
    Why
    Clinton, Mississippi is in Hinds County; the record had filed it under Madison County and placed it at Canton. On the editor's word of October 16, 2026.

  415. · PathOne Arthur Data Center · the county of a record

    Before
    O'Brien
    After
    Ida
    Why
    Arthur, Iowa is in Ida County, as the record's source (KTIV, Sioux City) reports; the record had filed it under O'Brien County. On the editor's word of October 16, 2026.

  416. · ValorC3 Boise Data Center · the county of a record

    Before
    Boise County
    After
    Ada County
    Why
    Boise is in Ada County; the record had filed it under Boise County and placed it at Idaho City, that county's seat. On the editor's word of October 16, 2026.

  417. · a record · the publication of a figure

    Before
    draft
    After
    published
    Why
    Restored on October 16, 2026: the figure is about Louisiana, inside the record's US scope; it was taken off with the rest of its card's rows about Bahrain and the United Arab Emirates by mistake.

  418. · a record · the publication of a figure

    Before
    draft
    After
    published
    Why
    Restored on October 16, 2026: the figure is about Louisiana, inside the record's US scope; it was taken off with the rest of its card's rows about Bahrain and the United Arab Emirates by mistake.

  419. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Outside the record's US scope: the source is about South Africa, and its card (11292) was dismissed for that on October 16, 2026. Taken off on the editor's word of October 16, 2026; kept, never deleted, and it can be restored.

  420. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Outside the record's US scope: the source is about South Africa, and its card (11292) was dismissed for that on October 16, 2026. Taken off on the editor's word of October 16, 2026; kept, never deleted, and it can be restored.

  421. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Outside the record's US scope: the source is about South Africa, and its card (11292) was dismissed for that on October 16, 2026. Taken off on the editor's word of October 16, 2026; kept, never deleted, and it can be restored.

  422. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Outside the record's US scope: the source is about South Africa, and its card (11292) was dismissed for that on October 16, 2026. Taken off on the editor's word of October 16, 2026; kept, never deleted, and it can be restored.

  423. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Outside the record's US scope: the source is about South Africa, and its card (11292) was dismissed for that on October 16, 2026. Taken off on the editor's word of October 16, 2026; kept, never deleted, and it can be restored.

  424. · Amazon Web Services Louisiana data centers · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Outside the record's US scope: the source is about AWS data centers in Bahrain and the United Arab Emirates, and its card (12394) was dismissed for that on October 16, 2026. Taken off on the editor's word of October 16, 2026; kept, never deleted, and it can be restored.

  425. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Outside the record's US scope: the source is about AWS data centers in Bahrain and the United Arab Emirates, and its card (12394) was dismissed for that on October 16, 2026. Taken off on the editor's word of October 16, 2026; kept, never deleted, and it can be restored.

  426. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Outside the record's US scope: the source is about AWS data centers in Bahrain and the United Arab Emirates, and its card (12394) was dismissed for that on October 16, 2026. Taken off on the editor's word of October 16, 2026; kept, never deleted, and it can be restored.

  427. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Outside the record's US scope: the source is about AWS data centers in Bahrain and the United Arab Emirates, and its card (12394) was dismissed for that on October 16, 2026. Taken off on the editor's word of October 16, 2026; kept, never deleted, and it can be restored.

  428. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Outside the record's US scope: the source is about AWS data centers in Bahrain and the United Arab Emirates, and its card (12394) was dismissed for that on October 16, 2026. Taken off on the editor's word of October 16, 2026; kept, never deleted, and it can be restored.

  429. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Outside the record's US scope: the source is about Africa, and its card (20563) was dismissed for that on October 16, 2026. Taken off on the editor's word of October 16, 2026; kept, never deleted, and it can be restored.

  430. · the ended how of 4 candidacies

    Before
    Listed on the race page as a candidate on the November 3, 2026 ballot.
    After
    Off the race and leaders pages; the person's page says the candidate is a certified write in, with its source.
    Why
    Kentucky: 4 certified write in candidates, whose names are not printed on the ballot, come off the race pages, which list only the names the certified ballot prints. On the editor's word of October 16, 2026.

  431. · the ended how of 11 candidacies

    Before
    Listed on the race page as a candidate on the November 3, 2026 ballot.
    After
    Off the race and leaders pages; the person's page says the candidate is a certified write in, with its source.
    Why
    Texas: 11 certified write in candidates, whose names are not printed on the ballot, come off the race pages, which list only the names the certified ballot prints. On the editor's word of October 16, 2026.

  432. · the ended how of 5 candidacies

    Before
    Listed on the race page as a candidate on the November 3, 2026 ballot.
    After
    Off the race and leaders pages; the person's page says the candidate is a certified write in, with its source.
    Why
    Indiana: 5 certified write in candidates, whose names are not printed on the ballot, come off the race pages, which list only the names the certified ballot prints. On the editor's word of October 16, 2026.

  433. · the removed reason of 3 news items

    Before
    The note named a person.
    After
    The note names the editor's word.
    Why
    3 news items taken off the record on 2026-10-16 carried a note naming a person; a note names no person, so it reads the editor's word. Nothing else changed.

  434. · the removed reason of 35 news items

    Before
    The note named a person.
    After
    The note names the editor's word.
    Why
    35 news items taken off the record on 2026-10-16 carried a note naming a person; a note names no person, so it reads the editor's word. Nothing else changed.

  435. · United States (federal) · the citation of a scorecard event

    Before
    After
    https://elibrary.ferc.gov/eLibrary/filelist?accession_number=20260813-5118
    Why
    the date confirmed from FERC's eLibrary record of the document (accession 20260813-5118) on the editor's word of 2026-10-16; the Commission's own copy beside the copy the row cites.

  436. · United States (federal) · the citation of a scorecard event

    Before
    After
    https://elibrary.ferc.gov/eLibrary/filelist?accession_number=20260731-5214
    Why
    the date confirmed from FERC's eLibrary record of the document (accession 20260731-5214) on the editor's word of 2026-10-16; the Commission's own copy beside the copy the row cites.

  437. · United States (federal) · the citation of a scorecard event

    Before
    After
    https://elibrary.ferc.gov/eLibrary/filelist?accession_number=20261009-3055
    Why
    the date confirmed from FERC's eLibrary record of the document (accession 20261009-3055) on the editor's word of 2026-10-16; the Commission's own copy beside the copy the row cites.

  438. · United States (federal) · the citation of a scorecard event

    Before
    After
    https://elibrary.ferc.gov/eLibrary/filelist?accession_number=20260929-3099
    Why
    the date confirmed from FERC's eLibrary record of the document (accession 20260929-3099) on the editor's word of 2026-10-16; the Commission's own copy beside the copy the row cites.

  439. · United States (federal) · the act the rating rests on of a scorecard row

    Before
    More than ten states paused or canceled data center tax exemptions (2026-09-09)
    After
    none
    Why
    The editor's word of 2026-10-16: no binding act is in force on the federal row, so the rubric allows no rating, and the rule of 2026-09-09 that federal actions carry no rating stands; the case by case word of 2026-10-13 (decisions-1013) and the act it rested on come off.

  440. · United States (federal) · the rating of a scorecard row

    Before
    case by case
    After
    no published rating
    Why
    The editor's word of 2026-10-16: no binding act is in force on the federal row, so the rubric allows no rating, and the rule of 2026-09-09 that federal actions carry no rating stands; the case by case word of 2026-10-13 (decisions-1013) and the act it rested on come off.

  441. · the ended how of 16 candidacies

    Before
    Listed on the race page as a candidate on the November 3, 2026 ballot.
    After
    Off the race and leaders pages; the person's page says the candidate is a certified write in, with its source.
    Why
    Georgia: 16 certified write in candidates, whose names are not printed on the ballot, come off the race pages, which list only the names the certified ballot prints. On the editor's word, 2026-10-15.

  442. · the ended how of 11 candidacies

    Before
    Listed on the race page as a candidate on the November 3, 2026 ballot.
    After
    Off the race and leaders pages; the person's page says the candidate is a certified write in, with its source.
    Why
    Ohio: 11 certified write in candidates, whose names are not printed on the ballot, come off the race pages, which list only the names the certified ballot prints. On the editor's word, 2026-10-15.

  443. · the note of 4 person sources

    Before
    A date printed as numbers, such as 2026-08-26.
    After
    The same date in words: August 26, 2026.
    Why
    4 person sources carried a date written as numbers in this text. Each such date now reads in words, the month, the day and the year. No date and no other word changed. On the editor's word, 2026-10-15.

  444. · the list date of 22 races

    Before
    A date printed as numbers, such as 2026-08-26.
    After
    The same date in words: August 26, 2026.
    Why
    22 races carried a date written as numbers in this text. Each such date now reads in words, the month, the day and the year. No date and no other word changed. On the editor's word, 2026-10-15.

  445. · the list date of 64 candidate listings

    Before
    A date printed as numbers, such as 2026-08-26.
    After
    The same date in words: August 26, 2026.
    Why
    64 candidates carried a date written as numbers in this text. Each such date now reads in words, the month, the day and the year. No date and no other word changed. On the editor's word, 2026-10-15.

  446. · the ended how of 61 candidacies

    Before
    Listed as a candidate for the November 3, 2026 ballot.
    After
    Off the race and leaders pages; the person's page says how the candidacy ended, with its source.
    Why
    Wisconsin: 61 candidates on file are not on the state's certified November 3, 2026 ballot (24 lost the primary, 37 did not qualify, 0 withdrew), read against the official list and the official primary record (https://manitowoccountywi.gov/wp-content/uploads/2026/08/8-11-2026-Official-Election-Results.pdf). On the editor's word, 2026-10-15.

  447. · the ended how of 28 candidacies

    Before
    Listed as a candidate for the November 3, 2026 ballot.
    After
    Off the race and leaders pages; the person's page says how the candidacy ended, with its source.
    Why
    Pennsylvania: 28 candidates on file are not on the state's certified November 3, 2026 ballot (9 lost the primary, 14 did not qualify, 5 withdrew), read against the official list and the official primary record (https://www.pa.gov/agencies/dos/newsroom/secretary-of-the-commonwealth-certifies-2026-primary-election-re). On the editor's word, 2026-10-15.

  448. · the ended how of 29 candidacies

    Before
    Listed as a candidate for the November 3, 2026 ballot.
    After
    Off the race and leaders pages; the person's page says how the candidacy ended, with its source.
    Why
    Ohio: 29 candidates on file are not on the state's certified November 3, 2026 ballot (24 lost the primary, 5 did not qualify, 0 withdrew), read against the official list and the official primary record (https://vote.franklincountyohio.gov/getmedia/8f366b7c-bc97-4f5c-8d15-659b0e35283d/Franklin-s-Official-Canvass-Summary-with-Group-Detail). On the editor's word, 2026-10-15.

  449. · the ended how of 25 candidacies

    Before
    Listed as a candidate for the November 3, 2026 ballot.
    After
    Off the race and leaders pages; the person's page says how the candidacy ended, with its source.
    Why
    Nevada: 25 candidates on file are not on the state's certified November 3, 2026 ballot (17 lost the primary, 8 did not qualify, 0 withdrew), read against the official list and the official primary record (https://www.clarkcountynv.gov/adobe/assets/urn:aaid:aem:0a98e045-e98d-491b-964f-ab56273bb5e8/original/as/Notice-Primary-Election-26P-ENG.pdf). On the editor's word, 2026-10-15.

  450. · the ended how of 19 candidacies

    Before
    Listed as a candidate for the November 3, 2026 ballot.
    After
    Off the race and leaders pages; the person's page says how the candidacy ended, with its source.
    Why
    New Hampshire: 19 candidates on file are not on the state's certified November 3, 2026 ballot (13 lost the primary, 6 did not qualify, 0 withdrew), read against the official list and the official primary record (https://www.sos.nh.gov/sites/g/files/ehbemt561/files/docs/cumulative-filings-8.14.26.pdf). On the editor's word, 2026-10-15.

  451. · the ended how of 13 candidacies

    Before
    Listed as a candidate for the November 3, 2026 ballot.
    After
    Off the race and leaders pages; the person's page says how the candidacy ended, with its source.
    Why
    Kansas: 13 candidates on file are not on the state's certified November 3, 2026 ballot (12 lost the primary, 1 did not qualify, 0 withdrew), read against the official list and the official primary record (https://sos.ks.gov/elections/26elec/2026-Primary-Election-Official-Vote-Totals.pdf). On the editor's word, 2026-10-15.

  452. · the ended how of 76 candidacies

    Before
    Listed as a candidate for the November 3, 2026 ballot.
    After
    Off the race and leaders pages; the person's page says how the candidacy ended, with its source.
    Why
    Georgia: 76 candidates on file are not on the state's certified November 3, 2026 ballot (46 lost the primary, 30 did not qualify, 0 withdrew), read against the official list and the official primary record (https://results.sos.ga.gov/results/public/Georgia/elections/GeneralPrimary51926). On the editor's word, 2026-10-15.

  453. · the ended how of 6 candidacies

    Before
    Listed as a candidate for the November 3, 2026 ballot.
    After
    Off the race and leaders pages; the person's page says how the candidacy ended, with its source.
    Why
    Arkansas: 6 candidates on file are not on the state's certified November 3, 2026 ballot (5 lost the primary, 1 did not qualify, 0 withdrew), read against the official list and the official primary record (https://votepulaskiar.gov/wp-content/uploads/Official-Primary-Summary-Results-1.pdf). On the editor's word, 2026-10-15.

  454. · the ended how of 5 candidacies

    Before
    Listed as a candidate for the November 3, 2026 ballot.
    After
    Off the race and leaders pages; the person's page says how the candidacy ended, with its source.
    Why
    Arizona: 5 candidates on file are not on the state's certified November 3, 2026 ballot (0 lost the primary, 5 did not qualify, 0 withdrew), read against the official list and the official primary record (https://mohave-002-us.govstack.com/media/amsjmtha/primary-summary-results-report.pdf). On the editor's word, 2026-10-15.

  455. · Stratos Project · the date of a timeline entry

    Before
    2026-08-24
    After
    2026-06-04
    Why
    Dated by its source: the Utah Senate's release on O'Leary's commitment is dated June 4, 2026; the entry had carried the day a later report was read. On the editor's word, 2026-10-15.

  456. · Stratos Project · the summary of a record

    Before
    O'Leary Digital and the Military Installation Development Authority propose a data center campus of approximately 9 GW at full buildout, with an onsite natural gas power plant, on about 40,000 acres of unincorporated land in Hansel Valley, north of the Great Salt Lake, after Box Elder County commissioners consented to the MIDA project area on May 4, 2026.
    After
    O'Leary Digital and the Military Installation Development Authority propose a data center campus of approximately 9 GW at full buildout, with an onsite natural gas power plant, on about 40,000 acres of unincorporated land in Hansel Valley, north of the Great Salt Lake, after Box Elder County commissioners consented to the MIDA project area on May 4, 2026. In a letter of June 4, 2026 answering Senate President J. Stuart Adams, O'Leary agreed to remove about 20,000 of those acres, roughly half the project area.
    Why
    The summary named the 40,000 acre project area alone; O'Leary's June 4, 2026 commitment to remove about half of it (KUER, June 4, 2026) now sits beside it. On the editor's word, 2026-10-15.

  457. · Stratos Project · the site acres source url of a record

    Before
    https://utahnewsdispatch.com/2026/05/19/renderings-show-massive-data-center-box-elder-utah-permits-could-take-years/
    After
    https://www.midaut.org/stratos
    Why
    Sourced to the authority's own Stratos page, which states the project area as approximately 40,000 acres. On the editor's word, 2026-10-15.

  458. · Stratos Project · the site acres disclosed as of a record

    Before
    third_party_estimate
    After
    permitted
    Why
    The 40,000 acres is the project area the Military Installation Development Authority designated, which the Box Elder County Commission consented to on May 4, 2026; it is not an outside estimate. On the editor's word, 2026-10-15.

  459. · the note of 1 bill relations

    Before
    A date printed as numbers, such as 2026-08-26.
    After
    The same date in words: August 26, 2026.
    Why
    1 bill relations carried a date written as numbers in this text. Each such date now reads in words, the month, the day and the year. No date and no other word changed. On the editor's word, 2026-10-15.

  460. · the wording of 1 statements

    Before
    A date printed as numbers, such as 2026-08-26.
    After
    The same date in words: August 26, 2026.
    Why
    1 statements carried a date written as numbers in this text. Each such date now reads in words, the month, the day and the year. No date and no other word changed. On the editor's word, 2026-10-15.

  461. · the rule of 156 measure effects

    Before
    A date printed as numbers, such as 2026-08-26.
    After
    The same date in words: August 26, 2026.
    Why
    156 measure effects carried a date written as numbers in this text. Each such date now reads in words, the month, the day and the year. No date and no other word changed. On the editor's word, 2026-10-15.

  462. · the rule of 731 statement labels

    Before
    A date printed as numbers, such as 2026-08-26.
    After
    The same date in words: August 26, 2026.
    Why
    731 statement labels carried a date written as numbers in this text. Each such date now reads in words, the month, the day and the year. No date and no other word changed. On the editor's word, 2026-10-15.

  463. · the note of 12 person sources

    Before
    A date printed as numbers, such as 2026-08-26.
    After
    The same date in words: August 26, 2026.
    Why
    12 person sources carried a date written as numbers in this text. Each such date now reads in words, the month, the day and the year. No date and no other word changed. On the editor's word, 2026-10-15.

  464. · the list date of 297 races

    Before
    A date printed as numbers, such as 2026-08-26.
    After
    The same date in words: August 26, 2026.
    Why
    297 races carried a date written as numbers in this text. Each such date now reads in words, the month, the day and the year. No date and no other word changed. On the editor's word, 2026-10-15.

  465. · the list date of 1,052 candidate listings

    Before
    A date printed as numbers, such as 2026-08-26.
    After
    The same date in words: August 26, 2026.
    Why
    1052 candidates carried a date written as numbers in this text. Each such date now reads in words, the month, the day and the year. No date and no other word changed. On the editor's word, 2026-10-15.

  466. · the last check result of 51 bill coverage

    Before
    A date printed as numbers, such as 2026-08-26.
    After
    The same date in words: August 26, 2026.
    Why
    51 bill coverage carried a date written as numbers in this text. Each such date now reads in words, the month, the day and the year. No date and no other word changed. On the editor's word, 2026-10-15.

  467. · the notes of 1 large load rules

    Before
    A date printed as numbers, such as 2026-08-26.
    After
    The same date in words: August 26, 2026.
    Why
    1 large load rules carried a date written as numbers in this text. Each such date now reads in words, the month, the day and the year. No date and no other word changed. On the editor's word, 2026-10-15.

  468. · the act the rating rests on of 1 scorecard rows

    Before
    A date printed as numbers, such as 2026-08-26.
    After
    The same date in words: August 26, 2026.
    Why
    1 scorecard rows carried a date written as numbers in this text. Each such date now reads in words, the month, the day and the year. No date and no other word changed. On the editor's word, 2026-10-15.

  469. · the rationale of 3 scorecard rows

    Before
    A date printed as numbers, such as 2026-08-26.
    After
    The same date in words: August 26, 2026.
    Why
    3 scorecard rows carried a date written as numbers in this text. Each such date now reads in words, the month, the day and the year. No date and no other word changed. On the editor's word, 2026-10-15.

  470. · the conditions of 2 figures

    Before
    A date printed as numbers, such as 2026-08-26.
    After
    The same date in words: August 26, 2026.
    Why
    2 figures carried a date written as numbers in this text. Each such date now reads in words, the month, the day and the year. No date and no other word changed. On the editor's word, 2026-10-15.

  471. · the notes of 18 figures

    Before
    A date printed as numbers, such as 2026-08-26.
    After
    The same date in words: August 26, 2026.
    Why
    18 figures carried a date written as numbers in this text. Each such date now reads in words, the month, the day and the year. No date and no other word changed. On the editor's word, 2026-10-15.

  472. · the location source of 3 records

    Before
    A date printed as numbers, such as 2026-08-26.
    After
    The same date in words: August 26, 2026.
    Why
    3 records carried a date written as numbers in this text. Each such date now reads in words, the month, the day and the year. No date and no other word changed. On the editor's word, 2026-10-15.

  473. · the summary of 6 records

    Before
    A date printed as numbers, such as 2026-08-26.
    After
    The same date in words: August 26, 2026.
    Why
    6 records carried a date written as numbers in this text. Each such date now reads in words, the month, the day and the year. No date and no other word changed. On the editor's word, 2026-10-15.

  474. · the companion note of 2 laws

    Before
    A date printed as numbers, such as 2026-08-26.
    After
    The same date in words: August 26, 2026.
    Why
    2 laws carried a date written as numbers in this text. Each such date now reads in words, the month, the day and the year. No date and no other word changed. On the editor's word, 2026-10-15.

  475. · the summary of 128 laws

    Before
    A date printed as numbers, such as 2026-08-26.
    After
    The same date in words: August 26, 2026.
    Why
    128 laws carried a date written as numbers in this text. Each such date now reads in words, the month, the day and the year. No date and no other word changed. On the editor's word, 2026-10-15.

  476. · the summary of 99 news items

    Before
    A date printed as numbers, such as 2026-08-26.
    After
    The same date in words: August 26, 2026.
    Why
    99 news items carried a date written as numbers in this text. Each such date now reads in words, the month, the day and the year. No date and no other word changed. On the editor's word, 2026-10-15.

  477. · the summary of 241 scorecard events

    Before
    A date printed as numbers, such as 2026-08-26.
    After
    The same date in words: August 26, 2026.
    Why
    241 scorecard events carried a date written as numbers in this text. Each such date now reads in words, the month, the day and the year. No date and no other word changed. On the editor's word, 2026-10-15.

  478. · the unplaced reason of 22 timeline entries

    Before
    A date printed as numbers, such as 2026-08-26.
    After
    The same date in words: August 26, 2026.
    Why
    22 timeline entries carried a date written as numbers in this text. Each such date now reads in words, the month, the day and the year. No date and no other word changed. On the editor's word, 2026-10-15.

  479. · the summary of 7 timeline entries

    Before
    A date printed as numbers, such as 2026-08-26.
    After
    The same date in words: August 26, 2026.
    Why
    7 timeline entries carried a date written as numbers in this text. Each such date now reads in words, the month, the day and the year. No date and no other word changed. On the editor's word, 2026-10-15.

  480. · a record · the definition of a glossary entry

    Before
    The record's rating of how a jurisdiction handles data centers, derived from its dated events: open, case by case, restrictive or closed. Never typed in; the latest event sets it.
    After
    The record's rating of how a jurisdiction handles data centers: open, case by case, restrictive, closed or not rated. A rating rests only on a binding act in force by that body, such as an ordinance, a statute, a vote that took effect, a commission order or a court order. Statements, hearings, proposals, protests and lawsuits never move it, and the row shows the most restrictive act in force.
    Why
    The definition followed the record's first rating rule; it now follows the ratings rubric (DECISIONS 32, approved 2026-10-09): a rating rests only on a binding act in force. Corrected on the editor's word, 2026-10-15.

  481. · a record · the definition of a glossary entry

    Before
    A temporary ban on approving new data centers, or on one kind of approval, adopted by a council, a commission or a legislature for a stated period or until a rule is written. The record rates a jurisdiction closed while one is in force.
    After
    A temporary ban on approving new data centers, or on one kind of approval, adopted by a council, a commission or a legislature for a stated period or until a rule is written. While one is in force the row is restrictive when it ends within 12 months or its end is not stated, and closed when it runs longer than 12 months or the source calls it permanent or indefinite.
    Why
    The definition followed the record's first rating rule; it now follows the ratings rubric (DECISIONS 32, approved 2026-10-09): a rating rests only on a binding act in force. Corrected on the editor's word, 2026-10-15.

  482. · a record · the value of a figure

    Before
    16 to 33 billion gal/yr
    After
    60 to 124 billion liters a year
    Why
    Stored as the LBNL 2024 report prints it ("between 60 and 124 billion liters"), as its 2023 figure is; the gallons are the conversion (60 and 124 billion liters at 3.785411784 liters a gallon are 15.85 and 32.76 billion gallons). Corrected on the editor's word, 2026-10-15.

  483. · Aligned PIT-01 (Project Phoenix) · the stated stage of a timeline entry

    Before
    operational
    After
    under_construction
    Why
    Read again: Aligned's Pennsylvania page says the company is building the campus and links its groundbreaking release; it does not say the site is running. The record's stage was already being built. Corrected on the editor's word, 2026-10-15.

  484. · Aligned PIT-01 (Project Phoenix) · the kind of a timeline entry

    Before
    opening
    After
    other
    Why
    The entry describes the campus's closed loop cooling; nothing opened. Typed other on the editor's word, 2026-10-15.

  485. · Aligned PIT-01 (Project Phoenix) · the kind of a timeline entry

    Before
    opening
    After
    other
    Why
    The entry describes the campus's closed loop cooling; nothing opened. Typed other on the editor's word, 2026-10-15.

  486. · Aligned PIT-01 (Project Phoenix) · the kind of a timeline entry

    Before
    opening
    After
    other
    Why
    The entry describes the campus's closed loop cooling; nothing opened. Typed other on the editor's word, 2026-10-15.

  487. · Aligned PIT-01 (Project Phoenix) · the kind of a timeline entry

    Before
    opening
    After
    other
    Why
    The entry records Aligned's page listing the Shippingport campus; nothing opened. Typed other on the editor's word, 2026-10-15.

  488. · Aligned PIT-01 (Project Phoenix) · the summary of a record

    Before
    Aligned Data Centers lists a data center at Shippingport, Pennsylvania among the sites it operates.
    After
    Aligned Data Centers broke ground on September 10, 2026 on Project Phoenix, a three building, 2 GW campus at Shippingport, Pennsylvania, on the site of the former Bruce Mansfield coal plant.
    Why
    The summary said Aligned operates a data center at Shippingport; its Pennsylvania page says it is building the campus, and its release and the local reports date the groundbreaking to September 10, 2026. Corrected on the editor's word, 2026-10-15.

  489. · Aligned PIT-01 (Project Phoenix) · the capacity source url of a record

    Before
    https://stocktwits.com/news-articles/markets/equity/bloom-energy-gains-another-meaningful-proof-point-with-project-phoenix-says-rbc-2-gw-build-reinforces-data-center-opportunity/cZtnKFhRBcp
    After
    https://aligneddc.com/press-release/project-phoenix-data-center-shippingport-pa/
    Why
    Sourced to Aligned's own release in place of a market news page relaying an analyst note. Corrected on the editor's word, 2026-10-15.

  490. · Aligned PIT-01 (Project Phoenix) · the capacity disclosed as of a record

    Before
    third_party_estimate
    After
    developer_estimate
    Why
    Aligned's own release announces the groundbreaking of a 2 GW campus; the figure is the developer's, not an analyst's. Corrected on the editor's word, 2026-10-15.

  491. · Volition Industries Spanish Fork · the summary of a record

    Before
    Volition Industries proposes to convert the former Fingerhut warehouse at the mouth of Spanish Fork Canyon into a self powered data center running on natural gas fuel cells, pending Spanish Fork City Council amendments to Title 15.
    After
    Volition Industries proposed converting the former Fingerhut warehouse at the mouth of Spanish Fork Canyon into a self powered data center running on natural gas fuel cells. Spanish Fork City Council approved the Title 15 amendments on September 21, 2026, and Volition's chief executive said the project would move to Stockman Flats, an industrial area west of Interstate 15, a plan not yet final; residents have filed for a referendum on the amendment.
    Why
    The summary said the Title 15 amendments were pending; FOX 13 reports the council approved them on September 21, 2026 and that Volition said it would move the project to Stockman Flats (https://www.fox13now.com/news/local-news/utah-county/spanish-fork-citizens-file-referendum-on-data-center-amendment-county-works-on-ordinance-to-bring-protections). Corrected on the editor's word, 2026-10-15.

  492. · Stratos Project · the date of a timeline entry

    Before
    2026-05-18
    After
    2026-05-04
    Why
    Dated by the vote: the Box Elder County Commission voted on May 4, 2026; the entry had carried Grist's publication date. Corrected on the editor's word, 2026-10-15.

  493. · Stratos Project · the date of a timeline entry

    Before
    2026-08-24
    After
    2026-06-01
    Why
    Dated by the letter itself: Senate President J. Stuart Adams's letter to Kevin O'Leary is dated June 1, 2026; the entry had carried the day a later report was read. Corrected on the editor's word, 2026-10-15.

  494. · Stratos Project · the summary of a timeline entry

    Before
    Box Elder County commissioners approved Stratos Project in April 2026
    After
    Box Elder County commissioners approved the Stratos Project's agreements with the Military Installation Development Authority on May 4, 2026
    Why
    Grist placed the commission's vote in April 2026; the commissioners voted on May 4, 2026 (Utah News Dispatch, May 4, 2026, entry 13). Corrected on the editor's word, 2026-10-15.

  495. · Volition Industries Spanish Fork · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    The entry is about the Antelope Data Center, a separate proposal 20 miles west of Cedar City in Iron County, named in the same video; it is not Volition's project in Spanish Fork. Held off the record on the editor's word, 2026-10-15.

  496. · Stratos Project · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    The entry is background about Meta's Eagle Mountain campus in Utah County (ground broken 2018, opened 2021), not the Stratos Project in Box Elder County. Held off the record on the editor's word, 2026-10-15.

  497. · Stratos Project · the capacity source url of a record

    Before
    https://grist.org/accountability/data-center-natural-gas-utah-cox-box-elder-stratos/
    After
    https://www.midaut.org/stratos
    Why
    The 9 GW full buildout is the project's own stated plan (the Military Installation Development Authority's Stratos page: "at approximately 9GW buildout"), not an outside estimate; Grist reports the figure without estimating it. Corrected on the editor's word, 2026-10-15.

  498. · Stratos Project · the capacity disclosed as of a record

    Before
    third_party_estimate
    After
    developer_estimate
    Why
    The 9 GW full buildout is the project's own stated plan (the Military Installation Development Authority's Stratos page: "at approximately 9GW buildout"), not an outside estimate; Grist reports the figure without estimating it. Corrected on the editor's word, 2026-10-15.

  499. · a record · the summary of a law

    Before
    S.B. 312 of the 153rd General Assembly was signed on 2026-08-26. The legislature titles it: An Act To Amend Title 9, Title 22, And Title 29 Of The Delaware Code Relating To Data Centers.
    After
    S.B. 312 of the 153rd General Assembly was signed on August 26, 2026. The legislature titles it: An Act To Amend Title 9, Title 22, And Title 29 Of The Delaware Code Relating To Data Centers.
    Why
    The summary printed the signing date as a machine date; it now reads the day in words, as every other date on the site does.

  500. · Keller · the rating of a scorecard event

    Before
    restrictive
    After
    no published rating
    Why
    The event carried Texas's own rating, which the approve writes on an event whose proposed rating nobody accepted; on TX/keller it carries that row's own rating, none. No row's rating changed.

  501. · Westlake · the rating of a scorecard event

    Before
    restrictive
    After
    no published rating
    Why
    The event carried Texas's own rating, which the approve writes on an event whose proposed rating nobody accepted; on TX/westlake it carries that row's own rating, none. No row's rating changed.

  502. · Tarrant County · the rating of a scorecard event

    Before
    case by case
    After
    no published rating
    Why
    The event carried Texas's own rating, which the approve writes on an event whose proposed rating nobody accepted; on TX/tarrant-county it carries that row's own rating, none. No row's rating changed.

  503. · Bee County · the rating of a scorecard event

    Before
    case by case
    After
    no published rating
    Why
    The event carried Texas's own rating, which the approve writes on an event whose proposed rating nobody accepted; on TX/bee-county it carries that row's own rating, none. No row's rating changed.

  504. · El Paso · the rating of a scorecard event

    Before
    case by case
    After
    no published rating
    Why
    The event carried Texas's own rating, which the approve writes on an event whose proposed rating nobody accepted; on TX/el-paso it carries that row's own rating, none. No row's rating changed.

  505. · El Paso · the rating of a scorecard event

    Before
    case by case
    After
    no published rating
    Why
    The event carried Texas's own rating, which the approve writes on an event whose proposed rating nobody accepted; on TX/el-paso it carries that row's own rating, none. No row's rating changed.

  506. · Taylor · the rating of a scorecard event

    Before
    case by case
    After
    no published rating
    Why
    The event carried Texas's own rating, which the approve writes on an event whose proposed rating nobody accepted; on TX/taylor it carries that row's own rating, none. No row's rating changed.

  507. · Taylor · the rating of a scorecard event

    Before
    case by case
    After
    no published rating
    Why
    The event carried Texas's own rating, which the approve writes on an event whose proposed rating nobody accepted; on TX/taylor it carries that row's own rating, none. No row's rating changed.

  508. · Taylor · the rating of a scorecard event

    Before
    case by case
    After
    no published rating
    Why
    The event carried Texas's own rating, which the approve writes on an event whose proposed rating nobody accepted; on TX/taylor it carries that row's own rating, none. No row's rating changed.

  509. · Taylor · the rating of a scorecard event

    Before
    case by case
    After
    no published rating
    Why
    The event carried Texas's own rating, which the approve writes on an event whose proposed rating nobody accepted; on TX/taylor it carries that row's own rating, none. No row's rating changed.

  510. · Taylor · the rating of a scorecard event

    Before
    case by case
    After
    no published rating
    Why
    The event carried Texas's own rating, which the approve writes on an event whose proposed rating nobody accepted; on TX/taylor it carries that row's own rating, none. No row's rating changed.

  511. · Taylor · the rating of a scorecard event

    Before
    case by case
    After
    no published rating
    Why
    The event carried Texas's own rating, which the approve writes on an event whose proposed rating nobody accepted; on TX/taylor it carries that row's own rating, none. No row's rating changed.

  512. · San Marcos · the rating of a scorecard event

    Before
    case by case
    After
    closed
    Why
    The event carried Texas's own rating, which the approve writes on an event whose proposed rating nobody accepted; on TX/san-marcos it carries that row's own rating, closed. No row's rating changed.

  513. · Keller · the scorecard row of a scorecard event

    Before
    TX/texas
    After
    TX/keller
    Why
    The resolution is the Keller City Council's (Newsweek); the row was Texas's own. Moved to the Keller row, Tarrant County, on the editor's word (docs/batch-scorecard-collapse-0929.md).

  514. · Westlake · the scorecard row of a scorecard event

    Before
    TX/texas
    After
    TX/westlake
    Why
    The suit is against the Town of Westlake (Newsweek); the row was Texas's own. Moved to the Westlake row, Tarrant County, on the editor's word (docs/batch-scorecard-collapse-0929.md).

  515. · Tarrant County · the scorecard row of a scorecard event

    Before
    TX/texas
    After
    TX/tarrant-county
    Why
    The town hall is a Tarrant County commissioner's (KERA); the row was Texas's own. Moved to the Tarrant County row on the editor's word (docs/batch-scorecard-collapse-0929.md).

  516. · Bee County · the scorecard row of a scorecard event

    Before
    TX/texas
    After
    TX/bee-county
    Why
    The resolution is the Bee County Commissioners' (Bee Picayune); the row was Texas's own. Moved to the Bee County row on the editor's word (docs/batch-scorecard-collapse-0929.md).

  517. · El Paso · the scorecard row of a scorecard event

    Before
    TX/texas
    After
    TX/el-paso
    Why
    The direction is the El Paso City Council's (KFOX); the row was Texas's own. Moved to the El Paso row, El Paso County, on the editor's word (docs/batch-scorecard-collapse-0929.md).

  518. · El Paso · the scorecard row of a scorecard event

    Before
    TX/texas
    After
    TX/el-paso
    Why
    The vote is the El Paso City Council's (Spectrum News); the row was Texas's own. Moved to the El Paso row, El Paso County, on the editor's word (docs/batch-scorecard-collapse-0929.md).

  519. · Taylor · the scorecard row of a scorecard event

    Before
    TX/texas
    After
    TX/taylor
    Why
    The meeting is the Taylor City Council's (Texas Standard); the row was Texas's own. Moved to the Taylor row, Williamson County, on the editor's word (docs/batch-scorecard-collapse-0929.md).

  520. · Taylor · the scorecard row of a scorecard event

    Before
    TX/texas
    After
    TX/taylor
    Why
    The purchase is the City of Taylor's (Dallas Express); the row was Texas's own. Moved to the Taylor row, Williamson County, on the editor's word (docs/batch-scorecard-collapse-0929.md).

  521. · Taylor · the scorecard row of a scorecard event

    Before
    TX/texas
    After
    TX/taylor
    Why
    The transfer is to the City of Taylor's development corporation (Dallas Express); the row was Texas's own. Moved to the Taylor row, Williamson County, on the editor's word (docs/batch-scorecard-collapse-0929.md).

  522. · Taylor · the scorecard row of a scorecard event

    Before
    TX/texas
    After
    TX/taylor
    Why
    The investigation is into the Taylor data center's parkland tract, an event of the city named in the sentence (Dallas Express); the row was Texas's own. Moved to the Taylor row, Williamson County, on the editor's word (docs/batch-scorecard-collapse-0929.md).

  523. · Taylor · the scorecard row of a scorecard event

    Before
    TX/texas
    After
    TX/taylor
    Why
    The petition drive is Taylor residents' before the Taylor City Council (Texas Standard); the row was Texas's own. Moved to the Taylor row, Williamson County, on the editor's word (docs/batch-scorecard-collapse-0929.md).

  524. · Taylor · the scorecard row of a scorecard event

    Before
    TX/texas
    After
    TX/taylor
    Why
    The motion is against the City of Taylor over its council's inaction (Texas Standard); the row was Texas's own. Moved to the Taylor row, Williamson County, on the editor's word (docs/batch-scorecard-collapse-0929.md).

  525. · San Marcos · the scorecard row of a scorecard event

    Before
    TX/texas
    After
    TX/san-marcos
    Why
    The zoning change is the San Marcos City Council's, an act of the city (Texas Standard); the row was Texas's own. Moved to the San Marcos row, Hays County, on the editor's word (docs/batch-scorecard-collapse-0929.md).

  526. · a record · the decision of a bill

    Before
    on_record
    After
    not_on_record
    Why
    The enacted text, read from the state's own site (https://publications.tnsosfiles.com/acts/114/pub/pc0501.pdf), names no data center and no crypto or digital asset mining: the public chapter's only data center is the Tennessee state data center at the University of Tennessee, which makes population estimates for allocations to counties and cities. Off the record on the editor's word of 2026-10-12 (batch bills-watch-1013).

  527. · a record · the publication of a bill

    Before
    published
    After
    draft
    Why
    The enacted text, read from the state's own site (https://publications.tnsosfiles.com/acts/114/pub/pc0501.pdf), names no data center and no crypto or digital asset mining: the public chapter's only data center is the Tennessee state data center at the University of Tennessee, which makes population estimates for allocations to counties and cities. Off the record on the editor's word of 2026-10-12 (batch bills-watch-1013).

  528. · a record · the decision of a bill

    Before
    on_record
    After
    not_on_record
    Why
    The enacted text, read from the state's own site (https://www.oklegislature.gov/cf_pdf/2023-24%20ENR/hB/HB3240%20ENR.PDF), names no data center and no crypto or digital asset mining: the enacted text's only data center is the State Data Center, the agency that works with the Census Bureau, to which county assessors submit location data. Off the record on the editor's word of 2026-10-12 (batch bills-watch-1013).

  529. · a record · the publication of a bill

    Before
    published
    After
    draft
    Why
    The enacted text, read from the state's own site (https://www.oklegislature.gov/cf_pdf/2023-24%20ENR/hB/HB3240%20ENR.PDF), names no data center and no crypto or digital asset mining: the enacted text's only data center is the State Data Center, the agency that works with the Census Bureau, to which county assessors submit location data. Off the record on the editor's word of 2026-10-12 (batch bills-watch-1013).

  530. · a record · the decision of a bill

    Before
    on_record
    After
    not_on_record
    Why
    The enacted text, read from the state's own site (https://search-prod.lis.state.oh.us/api/v2/general_assembly_136/legislation/sb103/05_EN/pdf/), names no data center and no crypto or digital asset mining: the enacted text names no data center and no crypto or digital asset mining: alternative rate plans for natural gas companies serving large load customers. Off the record on the editor's word of 2026-10-12 (batch bills-watch-1013).

  531. · a record · the publication of a bill

    Before
    published
    After
    draft
    Why
    The enacted text, read from the state's own site (https://search-prod.lis.state.oh.us/api/v2/general_assembly_136/legislation/sb103/05_EN/pdf/), names no data center and no crypto or digital asset mining: the enacted text names no data center and no crypto or digital asset mining: alternative rate plans for natural gas companies serving large load customers. Off the record on the editor's word of 2026-10-12 (batch bills-watch-1013).

  532. · Shon Hiatt · the scorecard row of a statement

    Before
    After
    ut/utah
    Why
    the editor's word of 2026-10-12 (batch decisions-1013), item 15: the statement's words describe Utah as a whole, so it sits on Utah's state row.

  533. · Humans First / Data Center Revolt tour · the scorecard row of a statement

    Before
    After
    ut/utah
    Why
    the editor's word of 2026-10-12 (batch decisions-1013), item 15: the statement's words describe Utah as a whole, so it sits on Utah's state row.

  534. · Stratos Project · the publication of a statement

    Before
    true
    After
    false
    Why
    the editor's word of 2026-10-12 (batch decisions-1013), item 14: Governor Cox's remark that the Stratos process was not good is from May 2026 (Grist, May 28), a separate occasion from his August 20 press conference; a report of something said on a different occasion stands on its own.

  535. · Stratos Project · the folded into of a statement

    Before
    40ba2c40-3842-436d-9ddb-18959bd0612c
    After
    Why
    the editor's word of 2026-10-12 (batch decisions-1013), item 14: Governor Cox's remark that the Stratos process was not good is from May 2026 (Grist, May 28), a separate occasion from his August 20 press conference; a report of something said on a different occasion stands on its own.

  536. · Volition Industries Spanish Fork · the publication of a statement

    Before
    true
    After
    false
    Why
    the editor's word of 2026-10-12 (batch decisions-1013), item 14: Jeff Chavez's September 2026 line comes from KSL's report of the Spanish Fork council meeting of that month, a separate occasion from his August 18 remark; a report of something said on a different occasion stands on its own.

  537. · Volition Industries Spanish Fork · the folded into of a statement

    Before
    026861b0-4e2d-46db-aa17-bc747fdce2fe
    After
    Why
    the editor's word of 2026-10-12 (batch decisions-1013), item 14: Jeff Chavez's September 2026 line comes from KSL's report of the Spanish Fork council meeting of that month, a separate occasion from his August 18 remark; a report of something said on a different occasion stands on its own.

  538. · Spokane County · the rating's end date of a scorecard row

    Before
    none
    After
    2026-12-18
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-18, which ends 2026-12-18.

  539. · Spokane County · the act the rating rests on of a scorecard row

    Before
    none
    After
    Spokane County Board of Commissioners unanimously approved a four month pause on new data center permits on Tuesday. (2026-08-18)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-18, which ends 2026-12-18.

  540. · Prince William County · the act the rating rests on of a scorecard row

    Before
    none
    After
    Several high profile projects in Prince William County were recently halted due to sustained community opposition (2026-09-18)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-18.

  541. · Loudoun County · the rating's end date of a scorecard row

    Before
    none
    After
    2027-09-18
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-18, which ends 2027-09-18.

  542. · Loudoun County · the act the rating rests on of a scorecard row

    Before
    none
    After
    Loudoun County Board of Supervisors voted 7-1 on motion to pause data center applications for 12 months, effective immediately (2026-09-18)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-18, which ends 2027-09-18.

  543. · Fort Worth · the act the rating rests on of a scorecard row

    Before
    none
    After
    Fort Worth City Council voted for a moratorium on data center development (2026-09-18)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-18.

  544. · Memphis · the act the rating rests on of a scorecard row

    Before
    none
    After
    Memphis imposed data center moratorium while SpaceXAI continues expansion in Mississippi less than a mile away (2026-09-21)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-21.

  545. · Hillsboro · the rating's end date of a scorecard row

    Before
    none
    After
    2026-11-24
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-07-27, which ends 2026-11-24.

  546. · Hillsboro · the act the rating rests on of a scorecard row

    Before
    none
    After
    Hillsboro, Oregon also approved its own pause at a last minute July 27 meeting (2026-07-27)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-07-27, which ends 2026-11-24.

  547. · Oakville · the rating's end date of a scorecard row

    Before
    none
    After
    2027-08-13
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-13, which ends 2027-08-13.

  548. · Oakville · the act the rating rests on of a scorecard row

    Before
    none
    After
    Oakville city council voted unanimously to enact a one year moratorium on data centres (2026-08-13)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-13, which ends 2027-08-13.

  549. · Nottingham · the rating's end date of a scorecard row

    Before
    none
    After
    2027-09-09
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-09, which ends 2027-09-09.

  550. · Nottingham · the act the rating rests on of a scorecard row

    Before
    none
    After
    Nottingham residents voted in favor of a 12 month moratorium on any data center development within town limits (2026-09-09)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-09, which ends 2027-09-09.

  551. · Minneapolis · the rating's end date of a scorecard row

    Before
    none
    After
    2026-11-01
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-07-12, which ends 2026-11-01.

  552. · Minneapolis · the act the rating rests on of a scorecard row

    Before
    none
    After
    Minneapolis City Council halts new data center developments until November (2026-07-12)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-07-12, which ends 2026-11-01.

  553. · Ypsilanti Township · the rating's end date of a scorecard row

    Before
    none
    After
    2027-08-17
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-17, which ends 2027-08-17.

  554. · Ypsilanti Township · the act the rating rests on of a scorecard row

    Before
    none
    After
    The Ypsilanti Community Utilities Authority enacted a one year moratorium on water and sewage use for the U M facility in April (2026-08-17)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-17, which ends 2027-08-17.

  555. · Eastport · the rating's end date of a scorecard row

    Before
    none
    After
    2027-02-20
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-24, which ends 2027-02-20.

  556. · Eastport · the act the rating rests on of a scorecard row

    Before
    none
    After
    Eastport City Council unanimously enacted a 180 day moratorium on data center projects in August 2026 (2026-08-24)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-24, which ends 2027-02-20.

  557. · Lowell · the rating's end date of a scorecard row

    Before
    none
    After
    2027-02-24
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-03-01, which ends 2027-02-24.

  558. · Lowell · the act the rating rests on of a scorecard row

    Before
    none
    After
    Lowell City Council imposed a 360 day moratorium on data centers in March (2026-03-01)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-03-01, which ends 2027-02-24.

  559. · Lake County · the rating's end date of a scorecard row

    Before
    none
    After
    2027-05-31
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-09, which ends 2027-05-31.

  560. · Lake County · the act the rating rests on of a scorecard row

    Before
    none
    After
    Lake County board approved eight month moratorium on data centers in unincorporated areas, effective through May 2027. (2026-09-09)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-09, which ends 2027-05-31.

  561. · Pinellas Park · the rating's end date of a scorecard row

    Before
    none
    After
    2027-08-29
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-16, which ends 2027-08-29.

  562. · Pinellas Park · the act the rating rests on of a scorecard row

    Before
    none
    After
    Pinellas Park approved data center moratorium (2026-08-16)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-16, which ends 2027-08-29.

  563. · Palm Beach County · the rating's end date of a scorecard row

    Before
    none
    After
    2027-08-27
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-27, which ends 2027-08-27.

  564. · Palm Beach County · the act the rating rests on of a scorecard row

    Before
    none
    After
    Palm Beach County commissioners unanimously approved language for the proposed moratorium ordinance on a one year ban on large scale data centers (2026-08-27)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-27, which ends 2027-08-27.

  565. · West Haven · the rating's end date of a scorecard row

    Before
    none
    After
    2027-06-10
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-06-10, which ends 2027-06-10.

  566. · West Haven · the act the rating rests on of a scorecard row

    Before
    none
    After
    West Haven approved a one year moratorium on new data centers (2026-06-10)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-06-10, which ends 2027-06-10.

  567. · Colorado Springs · the act the rating rests on of a scorecard row

    Before
    none
    After
    Data center on Garden of the Gods Road administratively approved by Colorado Springs (2026-06-12)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-06-12.

  568. · Uinta County · the act the rating rests on of a scorecard row

    Before
    none
    After
    Uinta County Commission voted to approve a conditional use permit for Prometheus Hyperscale data centre near Evanston with 15 conditions (2026-08-25)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-25.

  569. · Uinta County · the rating of a scorecard row

    Before
    no published rating
    After
    case by case
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-25.

  570. · Natrona County · the rating of a scorecard row

    Before
    case by case
    After
    no published rating
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): no binding act in force on the row under the rubric as clarified on 2026-10-10.

  571. · Cheyenne · the act the rating rests on of a scorecard row

    Before
    none
    After
    City Council committee approved three aspects of Cox Ranch annexation and rezoning on Tuesday (2026-09-08)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-08.

  572. · Cheyenne · the rating of a scorecard row

    Before
    no published rating
    After
    case by case
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-08.

  573. · Port Washington · the act the rating rests on of a scorecard row

    Before
    none
    After
    The Port Washington City Council in November approved a resolution creating a tax increment district to fund around $175 million in infrastructure improvements to serve the data center development. (2026-02-13)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-02-13.

  574. · Port Washington · the rating of a scorecard row

    Before
    no published rating
    After
    case by case
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-02-13.

  575. · Marathon County · the rating's end date of a scorecard row

    Before
    none
    After
    2027-08-25
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-25, which ends 2027-08-25.

  576. · Marathon County · the act the rating rests on of a scorecard row

    Before
    none
    After
    Marathon County Board approved on Aug. 25 a 12 month moratorium on data center development in townships governed by county zoning (2026-08-25)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-25, which ends 2027-08-25.

  577. · Marathon County · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-25, which ends 2027-08-25.

  578. · Madison · the act the rating rests on of a scorecard row

    Before
    none
    After
    Madison passed a moratorium on AI data centers amid concerns about water use and high energy demands (2026-08-25)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-25.

  579. · Madison · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-25.

  580. · Virginia Beach · the rating's end date of a scorecard row

    Before
    none
    After
    2027-09-18
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-18, which ends 2027-09-18.

  581. · Virginia Beach · the act the rating rests on of a scorecard row

    Before
    none
    After
    Virginia Beach approved one year moratorium on data centers (2026-09-18)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-18, which ends 2027-09-18.

  582. · Virginia Beach · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-18, which ends 2027-09-18.

  583. · Stafford County · the act the rating rests on of a scorecard row

    Before
    none
    After
    In 2024, the Stafford County Board of Supervisors approved the Stafford Technology Campus, the largest data center project in county history. (2026-02-26)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-02-26.

  584. · Stafford County · the rating of a scorecard row

    Before
    no published rating
    After
    case by case
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-02-26.

  585. · Richmond · the rating of a scorecard row

    Before
    restrictive
    After
    no published rating
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): no binding act in force on the row under the rubric as clarified on 2026-10-10.

  586. · Pulaski County · the rating of a scorecard row

    Before
    restrictive
    After
    no published rating
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): no binding act in force on the row under the rubric as clarified on 2026-10-10.

  587. · Chesapeake · the rating's end date of a scorecard row

    Before
    none
    After
    2027-05-18
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-18, which ends 2027-05-18.

  588. · Chesapeake · the act the rating rests on of a scorecard row

    Before
    none
    After
    Chesapeake implemented eight month moratorium on data center applications (2026-09-18)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-18, which ends 2027-05-18.

  589. · Chesapeake · the rating of a scorecard row

    Before
    case by case
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-18, which ends 2027-05-18.

  590. · Carroll County · the act the rating rests on of a scorecard row

    Before
    none
    After
    Carroll County Board of Supervisors passed emergency ordinance to regulate hyperscale data centers on Monday September 14 at called meeting; vote was 5 to 1 against Jody Early. (2026-09-14)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-14.

  591. · Carroll County · the rating of a scorecard row

    Before
    no published rating
    After
    case by case
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-14.

  592. · Tooele County · the rating of a scorecard row

    Before
    restrictive
    After
    no published rating
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): no binding act in force on the row under the rubric as clarified on 2026-10-10.

  593. · Spanish Fork · the act the rating rests on of a scorecard row

    Before
    Title 15 amendment vote tabled a second time (2026-09-01)
    After
    Spanish Fork City Council voted to approve changes to city code for a data center. (2026-09-24)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-24.

  594. · Spanish Fork · the rating of a scorecard row

    Before
    restrictive
    After
    case by case
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-24.

  595. · Juab County · the act the rating rests on of a scorecard row

    Before
    none
    After
    Juab County commissioners approved a conditional use permit for a data center project in April 2026 (2026-09-16)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-16.

  596. · Juab County · the rating of a scorecard row

    Before
    no published rating
    After
    case by case
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-16.

  597. · Iron County · the rating's end date of a scorecard row

    Before
    none
    After
    2026-10-28
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-05-01, which ends 2026-10-28.

  598. · Iron County · the act the rating rests on of a scorecard row

    Before
    none
    After
    Iron County imposed a 180 day moratorium on other data center proposals in May 2026. (2026-05-01)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-05-01, which ends 2026-10-28.

  599. · Iron County · the rating of a scorecard row

    Before
    case by case
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-05-01, which ends 2026-10-28.

  600. · Eagle Mountain · the act the rating rests on of a scorecard row

    Before
    none
    After
    Meta and Google received tax incentives or breaks for data centers in Eagle Mountain (2026-08-22)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-22.

  601. · Eagle Mountain · the rating of a scorecard row

    Before
    no published rating
    After
    case by case
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-22.

  602. · Lubbock · the rating of a scorecard row

    Before
    restrictive
    After
    no published rating
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): no binding act in force on the row under the rubric as clarified on 2026-10-10.

  603. · Hood County · the rating of a scorecard row

    Before
    restrictive
    After
    no published rating
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): no binding act in force on the row under the rubric as clarified on 2026-10-10.

  604. · Hays County · the rating of a scorecard row

    Before
    case by case
    After
    no published rating
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): no binding act in force on the row under the rubric as clarified on 2026-10-10.

  605. · Austin · the rating of a scorecard row

    Before
    case by case
    After
    no published rating
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): no binding act in force on the row under the rubric as clarified on 2026-10-10.

  606. · Wilson County · the act the rating rests on of a scorecard row

    Before
    none
    After
    Wilson County data center committee passed resolution on September 15, 2026 working out final details of zoning ordinance (2026-09-15)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-15.

  607. · Wilson County · the rating of a scorecard row

    Before
    no published rating
    After
    case by case
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-15.

  608. · Nashville · the act the rating rests on of a scorecard row

    Before
    none
    After
    Nashville Davidson Metro placed temporary moratorium on data center development after D.C. Blox announced facility near Nashville Zoo (2026-09-08)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-08.

  609. · Nashville · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-08.

  610. · Cleveland · the act the rating rests on of a scorecard row

    Before
    none
    After
    City requiring nine studies to be performed before project gets final approval (2026-09-17)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-17.

  611. · Cleveland · the rating of a scorecard row

    Before
    no published rating
    After
    case by case
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-17.

  612. · Minnehaha County · the rating of a scorecard row

    Before
    case by case
    After
    no published rating
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): no binding act in force on the row under the rubric as clarified on 2026-10-10.

  613. · McPherson County · the rating of a scorecard row

    Before
    case by case
    After
    no published rating
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): no binding act in force on the row under the rubric as clarified on 2026-10-10.

  614. · Spartanburg County · the rating's end date of a scorecard row

    Before
    none
    After
    2027-09-22
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-22, which ends 2027-09-22.

  615. · Spartanburg County · the act the rating rests on of a scorecard row

    Before
    none
    After
    Spartanburg County Council voted 5-1 to approve a one year freeze on new data centers larger than 65 megawatts (2026-09-22)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-22, which ends 2027-09-22.

  616. · Spartanburg County · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-22, which ends 2027-09-22.

  617. · Laurens County · the rating's end date of a scorecard row

    Before
    none
    After
    2027-09-16
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-16, which ends 2027-09-16.

  618. · Laurens County · the act the rating rests on of a scorecard row

    Before
    none
    After
    Laurens County Council unanimously adopts Ordinance 1012 imposing 12 month moratorium on new data center applications and permits (2026-09-16)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-16, which ends 2027-09-16.

  619. · Laurens County · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-16, which ends 2027-09-16.

  620. · Kershaw County · the rating's end date of a scorecard row

    Before
    none
    After
    2027-09-23
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-22, which ends 2027-09-23.

  621. · Kershaw County · the act the rating rests on of a scorecard row

    Before
    none
    After
    Kershaw County Council voted unanimously to pass the final reading of the data center moratorium ordinance on Tuesday night (2026-09-22)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-22, which ends 2027-09-23.

  622. · Kershaw County · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-22, which ends 2027-09-23.

  623. · Colleton County · the rating's end date of a scorecard row

    Before
    none
    After
    2027-03-14
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-14, which ends 2027-03-14.

  624. · Colleton County · the act the rating rests on of a scorecard row

    Before
    none
    After
    The council passed a six month moratorium on data centers back in July. But that moratorium is now partially repealed and no longer applies west of Interstate 95, or in areas already zoned industrial with this overlay. (2026-09-14)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-14, which ends 2027-03-14.

  625. · Colleton County · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-14, which ends 2027-03-14.

  626. · Anderson County · the rating's end date of a scorecard row

    Before
    none
    After
    2027-02-20
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-20, which ends 2027-02-20.

  627. · Anderson County · the act the rating rests on of a scorecard row

    Before
    none
    After
    Anderson County Council passed a six month moratorium on data centers (2026-08-20)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-20, which ends 2027-02-20.

  628. · Anderson County · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-20, which ends 2027-02-20.

  629. · Hopkinton · the rating's end date of a scorecard row

    Before
    none
    After
    2026-11-03
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-04, which ends 2026-11-03.

  630. · Hopkinton · the act the rating rests on of a scorecard row

    Before
    none
    After
    Hopkinton Council adopted a 60 day data center moratorium (2026-09-04)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-04, which ends 2026-11-03.

  631. · Hopkinton · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-04, which ends 2026-11-03.

  632. · Wyoming County · the act the rating rests on of a scorecard row

    Before
    none
    After
    Wyoming County Commissioners approved an amendment to the SALDO on September 8, 2026 to regulate high intensity nonresidential land developments such as data centers, applying to commercial projects 10,000 square feet or larger. (2026-09-08)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-08.

  633. · Wyoming County · the rating of a scorecard row

    Before
    no published rating
    After
    case by case
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-08.

  634. · Wellsboro · the act the rating rests on of a scorecard row

    Before
    none
    After
    The amendment passed unanimously and now requires all data centers to comply with ordinances about light levels, water usage and environmental impact (2026-09-15)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-15.

  635. · Wellsboro · the rating of a scorecard row

    Before
    restrictive
    After
    case by case
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-15.

  636. · Upper Merion · the act the rating rests on of a scorecard row

    Before
    none
    After
    Upper Merion Township board rejected proposal for five data centers totaling over 4.6 million square feet relying on natural gas turbines and diesel backup generators (2026-09-13)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-13.

  637. · Upper Merion · the rating of a scorecard row

    Before
    restrictive
    After
    case by case
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-13.

  638. · Salem Township · the rating of a scorecard row

    Before
    closed
    After
    no published rating
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): no binding act in force on the row under the rubric as clarified on 2026-10-10.

  639. · Philadelphia · the rating of a scorecard row

    Before
    case by case
    After
    no published rating
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): no binding act in force on the row under the rubric as clarified on 2026-10-10.

  640. · North Coventry · the rating of a scorecard row

    Before
    restrictive
    After
    no published rating
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): no binding act in force on the row under the rubric as clarified on 2026-10-10.

  641. · Montour County · the act the rating rests on of a scorecard row

    Before
    none
    After
    Citizens of Montour County won a rare victory in February when county leaders denied a rezoning application for a data center (2026-09-22)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-22.

  642. · Montour County · the rating of a scorecard row

    Before
    no published rating
    After
    case by case
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-22.

  643. · Marple Township · the act the rating rests on of a scorecard row

    Before
    none
    After
    Marple Township ordinance requires environmental, traffic, and economic impact studies, noise and vibration standards with tighter limits during overnight hours, and proof that adequate water is available without groundwater damage (2026-08-27)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-27.

  644. · Marple Township · the rating of a scorecard row

    Before
    no published rating
    After
    case by case
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-27.

  645. · Lancaster · the rating of a scorecard row

    Before
    restrictive
    After
    no published rating
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): no binding act in force on the row under the rubric as clarified on 2026-10-10.

  646. · Lackawanna County · the rating of a scorecard row

    Before
    case by case
    After
    no published rating
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): no binding act in force on the row under the rubric as clarified on 2026-10-10.

  647. · Indiana County · the rating of a scorecard row

    Before
    case by case
    After
    no published rating
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): no binding act in force on the row under the rubric as clarified on 2026-10-10.

  648. · Berks County · the act the rating rests on of a scorecard row

    Before
    none
    After
    Berks County township adopted ordinance setting limits for future AI data centers (2026-04-29)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-04-29.

  649. · Berks County · the rating of a scorecard row

    Before
    no published rating
    After
    case by case
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-04-29.

  650. · Archbald · the rating of a scorecard row

    Before
    case by case
    After
    no published rating
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): no binding act in force on the row under the rubric as clarified on 2026-10-10.

  651. · Woodburn · the rating's end date of a scorecard row

    Before
    none
    After
    2027-01-13
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-15, which ends 2027-01-13.

  652. · Woodburn · the act the rating rests on of a scorecard row

    Before
    none
    After
    Woodburn City Council unanimously approved 120 day moratorium on data center development on September 15, 2026 (2026-09-15)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-15, which ends 2027-01-13.

  653. · Woodburn · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-15, which ends 2027-01-13.

  654. · Salem · the rating's end date of a scorecard row

    Before
    none
    After
    2027-01-19
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-24, which ends 2027-01-19.

  655. · Salem · the act the rating rests on of a scorecard row

    Before
    none
    After
    Salem and Woodburn have adopted moratoriums on data centers (2026-08-24)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-24, which ends 2027-01-19.

  656. · Salem · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-24, which ends 2027-01-19.

  657. · Marion County · the rating of a scorecard row

    Before
    closed
    After
    no published rating
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): no binding act in force on the row under the rubric as clarified on 2026-10-10.

  658. · Wilmington · the act the rating rests on of a scorecard row

    Before
    none
    After
    Wilmington City Council passed rezoning ordinance from Rural Residential to Light Industrial in early September 2026 for data center project (2026-09-19)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-19.

  659. · Wilmington · the rating of a scorecard row

    Before
    no published rating
    After
    case by case
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-19.

  660. · Pioneer · the rating's end date of a scorecard row

    Before
    none
    After
    2027-03-17
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-15, which ends 2027-03-17.

  661. · Pioneer · the act the rating rests on of a scorecard row

    Before
    none
    After
    Village of Pioneer approved a data center moratorium (2026-09-15)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-15, which ends 2027-03-17.

  662. · Pioneer · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-15, which ends 2027-03-17.

  663. · Ontario · the rating's end date of a scorecard row

    Before
    none
    After
    2026-11-12
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-05-12, which ends 2026-11-12.

  664. · Ontario · the act the rating rests on of a scorecard row

    Before
    none
    After
    Ontario City Council approved a six month moratorium on data centers supporting artificial intelligence (2026-05-12)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-05-12, which ends 2026-11-12.

  665. · Ontario · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-05-12, which ends 2026-11-12.

  666. · McDonald · the rating's end date of a scorecard row

    Before
    none
    After
    2027-09-23
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-23, which ends 2027-09-23.

  667. · McDonald · the act the rating rests on of a scorecard row

    Before
    none
    After
    Village of McDonald enacted a 12 month moratorium on data centers (2026-09-23)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-23, which ends 2027-09-23.

  668. · McDonald · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-23, which ends 2027-09-23.

  669. · Defiance · the rating's end date of a scorecard row

    Before
    none
    After
    2027-03-19
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-19, which ends 2027-03-19.

  670. · Defiance · the act the rating rests on of a scorecard row

    Before
    none
    After
    Defiance city government announced a six month moratorium on approving new data center projects (2026-09-19)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-19, which ends 2027-03-19.

  671. · Defiance · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-19, which ends 2027-03-19.

  672. · Athens Township · the rating's end date of a scorecard row

    Before
    none
    After
    2027-09-11
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-11, which ends 2027-09-11.

  673. · Athens Township · the act the rating rests on of a scorecard row

    Before
    none
    After
    Athens Township Trustees instituted a yearlong moratorium on approval of zoning permits for data center in early August 2026 (2026-09-11)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-11, which ends 2027-09-11.

  674. · Athens Township · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-11, which ends 2027-09-11.

  675. · Canton · the rating's end date of a scorecard row

    Before
    none
    After
    2027-07-01
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-17, which ends 2027-07-01.

  676. · Canton · the act the rating rests on of a scorecard row

    Before
    none
    After
    The town of Canton imposed a moratorium in July to give a data center committee time to research the issue (2026-09-17)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-17, which ends 2027-07-01.

  677. · Canton · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-17, which ends 2027-07-01.

  678. · Reno · the rating's end date of a scorecard row

    Before
    none
    After
    2027-08-31
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-07, which ends 2027-08-31.

  679. · Reno · the act the rating rests on of a scorecard row

    Before
    none
    After
    Reno extended the moratorium through August 2027 and determined to adopt new regulations at that time (2026-09-07)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-07, which ends 2027-08-31.

  680. · Reno · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-07, which ends 2027-08-31.

  681. · Boulder City · the rating of a scorecard row

    Before
    case by case
    After
    no published rating
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): no binding act in force on the row under the rubric as clarified on 2026-10-10.

  682. · Socorro County · the rating's end date of a scorecard row

    Before
    none
    After
    2027-09-15
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-15, which ends 2027-09-15.

  683. · Socorro County · the act the rating rests on of a scorecard row

    Before
    none
    After
    Socorro County adopted a yearlong moratorium on data centers (2026-09-15)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-15, which ends 2027-09-15.

  684. · Socorro County · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-15, which ends 2027-09-15.

  685. · Colfax County · the rating's end date of a scorecard row

    Before
    none
    After
    2027-09-15
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-15, which ends 2027-09-15.

  686. · Colfax County · the act the rating rests on of a scorecard row

    Before
    none
    After
    Colfax County adopted a one year moratorium on data centers in unincorporated areas (2026-09-15)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-15, which ends 2027-09-15.

  687. · Colfax County · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-15, which ends 2027-09-15.

  688. · Vineland · the act the rating rests on of a scorecard row

    Before
    none
    After
    No permits issued nor any permit applications under review for power generators at DataOne (2026-08-28)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-28.

  689. · Vineland · the rating of a scorecard row

    Before
    no published rating
    After
    case by case
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-28.

  690. · Bridgewater Township · the act the rating rests on of a scorecard row

    Before
    none
    After
    The ordinance amends Chapter 126 of the township code and follows the township's September 30, 2025 Comprehensive Master Plan (2026-08-25)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-25.

  691. · Bridgewater Township · the rating of a scorecard row

    Before
    no published rating
    After
    case by case
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-25.

  692. · Rochester · the act the rating rests on of a scorecard row

    Before
    none
    After
    Rochester adopted ordinance prohibiting data centers in every zoning district except recycling industrial district, which requires conditional use permit (2026-08-18)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-18.

  693. · Rochester · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-18.

  694. · Lancaster County · the rating of a scorecard row

    Before
    case by case
    After
    no published rating
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): no binding act in force on the row under the rubric as clarified on 2026-10-10.

  695. · Kearney · the act the rating rests on of a scorecard row

    Before
    none
    After
    Kearney City Council approved Tech One Crossing data center on Tuesday, September 8, 2026 (2026-09-08)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-08.

  696. · Kearney · the rating of a scorecard row

    Before
    no published rating
    After
    case by case
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-08.

  697. · Gage County · the rating's end date of a scorecard row

    Before
    none
    After
    2027-09-16
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-16, which ends 2027-09-16.

  698. · Gage County · the act the rating rests on of a scorecard row

    Before
    none
    After
    Gage County supervisors approved a 12 month moratorium on data center permits on Wednesday (2026-09-16)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-16, which ends 2027-09-16.

  699. · Gage County · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-16, which ends 2027-09-16.

  700. · Cass County · the rating's end date of a scorecard row

    Before
    none
    After
    2027-08-11
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-11, which ends 2027-08-11.

  701. · Cass County · the act the rating rests on of a scorecard row

    Before
    none
    After
    Cass County Board of Commissioners voted 5-0 to approve a 12 month moratorium on permitting for data centers. (2026-08-11)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-11, which ends 2027-08-11.

  702. · Cass County · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-11, which ends 2027-08-11.

  703. · Williston · the act the rating rests on of a scorecard row

    Before
    none
    After
    Project Fighting Pike Critical Data House approved by Williston City Commission on March 25, 2025 (2025-03-25)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2025-03-25.

  704. · Williston · the rating of a scorecard row

    Before
    no published rating
    After
    case by case
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2025-03-25.

  705. · Williams County · the act the rating rests on of a scorecard row

    Before
    none
    After
    Williams County Commission approved conditional use permit for Enerfore Digital Data Center in Feb. 2025 but permit expired Aug. 4, 2026 due to inactivity (2026-09-02)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-02.

  706. · Williams County · the rating of a scorecard row

    Before
    no published rating
    After
    case by case
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-02.

  707. · Morton County · the act the rating rests on of a scorecard row

    Before
    none
    After
    Ordinance passed 5-1, with Tokach voting against due to tonal noise issue (2026-09-19)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-19.

  708. · Morton County · the rating of a scorecard row

    Before
    no published rating
    After
    case by case
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-19.

  709. · Swain County · the rating's end date of a scorecard row

    Before
    none
    After
    2027-09-15
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-15, which ends 2027-09-15.

  710. · Swain County · the act the rating rests on of a scorecard row

    Before
    none
    After
    Swain County adopted a one year moratorium on data center development (2026-09-15)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-15, which ends 2027-09-15.

  711. · Swain County · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-15, which ends 2027-09-15.

  712. · Shallotte · the act the rating rests on of a scorecard row

    Before
    none
    After
    Shallotte adopted unified development ordinance amendment in January limiting data center uses to Heavy Industrial zoning district (2026-08-24)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-24.

  713. · Shallotte · the rating of a scorecard row

    Before
    no published rating
    After
    case by case
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-24.

  714. · Newport · the act the rating rests on of a scorecard row

    Before
    none
    After
    Newport approves a moratorium on data center development (2026-09-16)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-16.

  715. · Newport · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-16.

  716. · McDowell County · the rating's end date of a scorecard row

    Before
    none
    After
    2027-03-11
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-11, which ends 2027-03-11.

  717. · McDowell County · the act the rating rests on of a scorecard row

    Before
    none
    After
    McDowell County approved six month moratorium on data center development (2026-09-11)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-11, which ends 2027-03-11.

  718. · McDowell County · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-11, which ends 2027-03-11.

  719. · Macon County · the rating's end date of a scorecard row

    Before
    none
    After
    2027-09-15
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-15, which ends 2027-09-15.

  720. · Macon County · the act the rating rests on of a scorecard row

    Before
    none
    After
    Macon County and the Town of Franklin adopted a one year moratorium on data center development (2026-09-15)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-15, which ends 2027-09-15.

  721. · Macon County · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-15, which ends 2027-09-15.

  722. · Lee County · the act the rating rests on of a scorecard row

    Before
    none
    After
    Lee County commissioners signed off on changes to permit data centers in light industrial zones (2026-08-27)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-27.

  723. · Lee County · the rating of a scorecard row

    Before
    no published rating
    After
    case by case
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-27.

  724. · Jackson County · the rating's end date of a scorecard row

    Before
    none
    After
    2027-09-15
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-15, which ends 2027-09-15.

  725. · Jackson County · the act the rating rests on of a scorecard row

    Before
    none
    After
    Jackson County adopted a one year moratorium on data center development (2026-09-15)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-15, which ends 2027-09-15.

  726. · Jackson County · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-15, which ends 2027-09-15.

  727. · Hendersonville · the rating's end date of a scorecard row

    Before
    none
    After
    2027-09-15
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-15, which ends 2027-09-15.

  728. · Hendersonville · the act the rating rests on of a scorecard row

    Before
    none
    After
    Hendersonville adopted a one year moratorium on data center development (2026-09-15)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-15, which ends 2027-09-15.

  729. · Hendersonville · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-15, which ends 2027-09-15.

  730. · Haywood County · the rating's end date of a scorecard row

    Before
    none
    After
    2027-09-15
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-15, which ends 2027-09-15.

  731. · Haywood County · the act the rating rests on of a scorecard row

    Before
    none
    After
    Haywood County and Canton adopted a one year moratorium on data center development (2026-09-15)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-15, which ends 2027-09-15.

  732. · Haywood County · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-15, which ends 2027-09-15.

  733. · Chatham County · the act the rating rests on of a scorecard row

    Before
    none
    After
    Chatham County enacted a moratorium on new data centers in February 2026. (2026-09-18)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-18.

  734. · Chatham County · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-18.

  735. · Charlotte · the rating's end date of a scorecard row

    Before
    none
    After
    2027-02-01
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-04, which ends 2027-02-01.

  736. · Charlotte · the act the rating rests on of a scorecard row

    Before
    none
    After
    Charlotte Water imposed a 150 day moratorium on new data center applications in June while officials study infrastructure capacity and environmental concerns (2026-09-04)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-04, which ends 2027-02-01.

  737. · Charlotte · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-04, which ends 2027-02-01.

  738. · Buncombe County · the rating's end date of a scorecard row

    Before
    none
    After
    2027-09-15
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-15, which ends 2027-09-15.

  739. · Buncombe County · the act the rating rests on of a scorecard row

    Before
    none
    After
    Buncombe County and Asheville adopted a one year moratorium on data center development (2026-09-15)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-15, which ends 2027-09-15.

  740. · Buncombe County · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-15, which ends 2027-09-15.

  741. · Brevard · the act the rating rests on of a scorecard row

    Before
    none
    After
    Brevard adopted permanent zoning regulations governing data center development instead of a temporary moratorium (2026-09-15)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-15.

  742. · Brevard · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-15.

  743. · Missoula County · the rating's end date of a scorecard row

    Before
    none
    After
    2027-07-10
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-07-09, which ends 2027-07-10.

  744. · Missoula County · the act the rating rests on of a scorecard row

    Before
    none
    After
    Missoula County adopted temporary moratorium on data centers (2026-07-09)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-07-09, which ends 2027-07-10.

  745. · Missoula County · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-07-09, which ends 2027-07-10.

  746. · Olive Branch · the act the rating rests on of a scorecard row

    Before
    none
    After
    Olive Branch Board of Mayor and Aldermen approved new zoning ordinance changes restricting data center development (2026-08-19)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-19.

  747. · Olive Branch · the rating of a scorecard row

    Before
    no published rating
    After
    case by case
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-19.

  748. · St. Louis · the act the rating rests on of a scorecard row

    Before
    none
    After
    St. Louis cleared a permit for the Armory data center as part of a $3 billion Innovation District (2026-04-21)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-04-21.

  749. · St. Louis · the rating of a scorecard row

    Before
    no published rating
    After
    case by case
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-04-21.

  750. · Springfield · the act the rating rests on of a scorecard row

    Before
    none
    After
    Springfield city council voted to put an administrative delay on any data center development (2026-08-27)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-27.

  751. · Springfield · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-27.

  752. · Independence · the act the rating rests on of a scorecard row

    Before
    none
    After
    John Perkins, Independence councilman, was recalled after voting to approve a multibillion dollar data center (2026-09-02)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-02.

  753. · Independence · the rating of a scorecard row

    Before
    no published rating
    After
    case by case
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-02.

  754. · Franklin County · the act the rating rests on of a scorecard row

    Before
    none
    After
    Franklin County commissioners voted to approve data center development regulations (2026-09-15)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-15.

  755. · Franklin County · the rating of a scorecard row

    Before
    no published rating
    After
    case by case
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-15.

  756. · Ferguson · the act the rating rests on of a scorecard row

    Before
    none
    After
    Ferguson City Council voted 4-3 to give tax incentives for a tech hub and data center at the former Emerson campus (2026-09-23)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-23.

  757. · Ferguson · the rating of a scorecard row

    Before
    no published rating
    After
    case by case
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-23.

  758. · Lonsdale · the rating's end date of a scorecard row

    Before
    none
    After
    2027-09-16
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-16, which ends 2027-09-16.

  759. · Lonsdale · the act the rating rests on of a scorecard row

    Before
    none
    After
    Lonsdale passes one year moratorium on data center construction (2026-09-16)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-16, which ends 2027-09-16.

  760. · Lonsdale · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-16, which ends 2027-09-16.

  761. · Inver Grove Heights · the rating's end date of a scorecard row

    Before
    none
    After
    2027-09-15
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-15, which ends 2027-09-15.

  762. · Inver Grove Heights · the act the rating rests on of a scorecard row

    Before
    none
    After
    Inver Grove Heights passed a pause on data centers (2026-09-15)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-15, which ends 2027-09-15.

  763. · Inver Grove Heights · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-15, which ends 2027-09-15.

  764. · Ypsilanti · the rating's end date of a scorecard row

    Before
    none
    After
    2026-11-13
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-14, which ends 2026-11-13.

  765. · Ypsilanti · the act the rating rests on of a scorecard row

    Before
    none
    After
    Ypsilanti City Council preliminarily passed a 60 day emergency data center moratorium, pending final vote. (2026-09-14)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-14, which ends 2026-11-13.

  766. · Ypsilanti · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-14, which ends 2026-11-13.

  767. · Wixom · the rating's end date of a scorecard row

    Before
    none
    After
    2027-02-27
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-31, which ends 2027-02-27.

  768. · Wixom · the act the rating rests on of a scorecard row

    Before
    none
    After
    Wixom implemented a 180 day data center moratorium (2026-08-31)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-31, which ends 2027-02-27.

  769. · Wixom · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-31, which ends 2027-02-27.

  770. · Marshall · the rating's end date of a scorecard row

    Before
    none
    After
    2027-08-03
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-03, which ends 2027-08-03.

  771. · Marshall · the act the rating rests on of a scorecard row

    Before
    none
    After
    Marshall City Council approved a one year moratorium on new data center developments on Aug. 3 (2026-08-03)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-03, which ends 2027-08-03.

  772. · Marshall · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-03, which ends 2027-08-03.

  773. · Gibraltar · the rating's end date of a scorecard row

    Before
    none
    After
    2027-03-09
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-03-09, which ends 2027-03-09.

  774. · Gibraltar · the act the rating rests on of a scorecard row

    Before
    none
    After
    Gibraltar city council approved data center moratorium on March 9, 2026 (2026-03-09)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-03-09, which ends 2027-03-09.

  775. · Gibraltar · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-03-09, which ends 2027-03-09.

  776. · Dowagiac · the act the rating rests on of a scorecard row

    Before
    none
    After
    Dowagiac city imposed tougher noise ordinance setting new daytime and nighttime decibel limits for industrial facilities (2026-09-21)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-21.

  777. · Dowagiac · the rating of a scorecard row

    Before
    no published rating
    After
    case by case
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-21.

  778. · Westbrook · the rating's end date of a scorecard row

    Before
    none
    After
    2027-03-21
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-22, which ends 2027-03-21.

  779. · Westbrook · the act the rating rests on of a scorecard row

    Before
    none
    After
    Westbrook passed a 180 day data center moratorium in June 2026. (2026-09-22)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-22, which ends 2027-03-21.

  780. · Westbrook · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-22, which ends 2027-03-21.

  781. · Scarborough · the rating's end date of a scorecard row

    Before
    none
    After
    2027-03-21
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-22, which ends 2027-03-21.

  782. · Scarborough · the act the rating rests on of a scorecard row

    Before
    none
    After
    Scarborough passed a 180 day data center moratorium in June 2026. (2026-09-22)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-22, which ends 2027-03-21.

  783. · Scarborough · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-22, which ends 2027-03-21.

  784. · Sanford · the rating's end date of a scorecard row

    Before
    none
    After
    2027-03-02
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-03, which ends 2027-03-02.

  785. · Sanford · the act the rating rests on of a scorecard row

    Before
    none
    After
    Sanford voted to extend its emergency moratorium on data centers for 180 days in August. (2026-09-03)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-03, which ends 2027-03-02.

  786. · Sanford · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-03, which ends 2027-03-02.

  787. · Ellsworth · the rating's end date of a scorecard row

    Before
    none
    After
    2027-02-10
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-14, which ends 2027-02-10.

  788. · Ellsworth · the act the rating rests on of a scorecard row

    Before
    none
    After
    Ellsworth City Council voted to enact a 180 day preemptive AI data center moratorium (2026-08-14)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-14, which ends 2027-02-10.

  789. · Ellsworth · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-14, which ends 2027-02-10.

  790. · Bangor · the rating's end date of a scorecard row

    Before
    none
    After
    2027-02-14
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-14, which ends 2027-02-14.

  791. · Bangor · the act the rating rests on of a scorecard row

    Before
    none
    After
    Bangor City Council approved a six month hold on data center construction in mid April 2026 (2026-08-14)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-14, which ends 2027-02-14.

  792. · Bangor · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-14, which ends 2027-02-14.

  793. · Frederick County · the rating's end date of a scorecard row

    Before
    none
    After
    2026-12-31
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-10, which ends 2026-12-31.

  794. · Frederick County · the act the rating rests on of a scorecard row

    Before
    none
    After
    Frederick County Executive Jessica Fitzwater signed an order pausing new data center permitting until the end of the year (2026-08-10)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-10, which ends 2026-12-31.

  795. · Frederick County · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-10, which ends 2026-12-31.

  796. · Calvert County · the rating's end date of a scorecard row

    Before
    none
    After
    2027-03-23
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-23, which ends 2027-03-23.

  797. · Calvert County · the act the rating rests on of a scorecard row

    Before
    none
    After
    Calvert County voted unanimously 5-0 in August 2026 to pause new data center applications for six months (2026-09-23)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-23, which ends 2027-03-23.

  798. · Calvert County · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-23, which ends 2027-03-23.

  799. · Baltimore City · the act the rating rests on of a scorecard row

    Before
    none
    After
    Baltimore has staunched the creation of data centers within city limits. (2026-09-24)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-24.

  800. · Baltimore City · the rating of a scorecard row

    Before
    no published rating
    After
    case by case
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-24.

  801. · Westfield · the rating's end date of a scorecard row

    Before
    none
    After
    2027-09-08
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-08, which ends 2027-09-08.

  802. · Westfield · the act the rating rests on of a scorecard row

    Before
    none
    After
    City councilors in Westfield voted earlier this year to enact a one year moratorium on additional data centers (2026-09-08)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-08, which ends 2027-09-08.

  803. · Westfield · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-08, which ends 2027-09-08.

  804. · Agawam · the act the rating rests on of a scorecard row

    Before
    none
    After
    Agawam city council approved a temporary hold on data center developments while drafting a preliminary ordinance. (2026-09-22)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-22.

  805. · Agawam · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-22.

  806. · Caddo Parish · the rating of a scorecard row

    Before
    case by case
    After
    no published rating
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): no binding act in force on the row under the rubric as clarified on 2026-10-10.

  807. · Boyce · the rating of a scorecard row

    Before
    restrictive
    After
    no published rating
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): no binding act in force on the row under the rubric as clarified on 2026-10-10.

  808. · Winchester · the rating's end date of a scorecard row

    Before
    none
    After
    2027-09-17
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-17, which ends 2027-09-17.

  809. · Winchester · the act the rating rests on of a scorecard row

    Before
    none
    After
    The city of Winchester has already approved a one year moratorium on new AI data center construction (2026-09-17)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-17, which ends 2027-09-17.

  810. · Winchester · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-17, which ends 2027-09-17.

  811. · Louisville · the rating's end date of a scorecard row

    Before
    none
    After
    2027-02-14
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-14, which ends 2027-02-14.

  812. · Louisville · the act the rating rests on of a scorecard row

    Before
    none
    After
    Louisville mayor signs 6 month moratorium on new data center projects on 2026-08-14 (2026-08-14)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-14, which ends 2027-02-14.

  813. · Louisville · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-14, which ends 2027-02-14.

  814. · Daviess County · the act the rating rests on of a scorecard row

    Before
    none
    After
    Daviess County has placed a moratorium on proceeding with data center construction (2026-09-18)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-18.

  815. · Daviess County · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-18.

  816. · Rose Hill · the act the rating rests on of a scorecard row

    Before
    none
    After
    Rose Hill adopted data center regulations in 2017. (2026-09-22)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-22.

  817. · Rose Hill · the rating of a scorecard row

    Before
    restrictive
    After
    case by case
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-22.

  818. · Ottawa · the rating of a scorecard row

    Before
    case by case
    After
    no published rating
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): no binding act in force on the row under the rubric as clarified on 2026-10-10.

  819. · Emporia · the rating of a scorecard row

    Before
    restrictive
    After
    no published rating
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): no binding act in force on the row under the rubric as clarified on 2026-10-10.

  820. · El Dorado · the rating of a scorecard row

    Before
    restrictive
    After
    no published rating
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): no binding act in force on the row under the rubric as clarified on 2026-10-10.

  821. · Butler County · the rating of a scorecard row

    Before
    case by case
    After
    no published rating
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): no binding act in force on the row under the rubric as clarified on 2026-10-10.

  822. · Barber County · the act the rating rests on of a scorecard row

    Before
    none
    After
    Barber County commissioners approved a 1.7 million square foot Google data center (2026-08-31)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-31.

  823. · Barber County · the rating of a scorecard row

    Before
    no published rating
    After
    case by case
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-31.

  824. · South Bend · the act the rating rests on of a scorecard row

    Before
    none
    After
    South Bend Mayor James Mueller issued an executive order banning city staff from signing non disclosure agreements about data centers on September 16, 2026 (2026-09-16)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-16.

  825. · South Bend · the rating of a scorecard row

    Before
    no published rating
    After
    case by case
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-16.

  826. · Posey County · the act the rating rests on of a scorecard row

    Before
    none
    After
    Posey County commissioners signed a non disclosure agreement amidst data center concerns (2026-07-21)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-07-21.

  827. · Posey County · the rating of a scorecard row

    Before
    no published rating
    After
    case by case
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-07-21.

  828. · Kokomo · the act the rating rests on of a scorecard row

    Before
    none
    After
    Ordinance requires data centers to be at least 200 feet from residential districts and 300 feet from any home but does not add stricter rules on utility use, noise, or infrastructure beyond current industrial regulations. (2026-08-30)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-30.

  829. · Kokomo · the rating of a scorecard row

    Before
    no published rating
    After
    case by case
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-30.

  830. · Gary · the rating's end date of a scorecard row

    Before
    none
    After
    2027-09-16
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-16, which ends 2027-09-16.

  831. · Gary · the act the rating rests on of a scorecard row

    Before
    none
    After
    Gary Mayor Eddie Melton issued an executive order establishing a one year moratorium on new data centers. (2026-09-16)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-16, which ends 2027-09-16.

  832. · Gary · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-16, which ends 2027-09-16.

  833. · Woodford County · the rating's end date of a scorecard row

    Before
    none
    After
    2027-02-28
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-21, which ends 2027-02-28.

  834. · Woodford County · the act the rating rests on of a scorecard row

    Before
    none
    After
    Woodford County Board approved six month moratorium on data center applications with option for six month extension, running through February 2027 (2026-08-21)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-21, which ends 2027-02-28.

  835. · Woodford County · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-21, which ends 2027-02-28.

  836. · Troy · the rating's end date of a scorecard row

    Before
    none
    After
    2027-03-18
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-18, which ends 2027-03-18.

  837. · Troy · the act the rating rests on of a scorecard row

    Before
    none
    After
    In March 2026, Troy City Council voted to put a six month moratorium on any data center project. (2026-09-18)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-18, which ends 2027-03-18.

  838. · Troy · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-18, which ends 2027-03-18.

  839. · Stickney · the act the rating rests on of a scorecard row

    Before
    none
    After
    Stickney board of trustees voted unanimously to block any data center proposals with a moratorium on zoning changes and approvals for data centers (2026-08-21)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-21.

  840. · Stickney · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-21.

  841. · South Elgin · the act the rating rests on of a scorecard row

    Before
    none
    After
    South Elgin village board denied data center application following resident uproar (2026-09-15)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-15.

  842. · South Elgin · the rating of a scorecard row

    Before
    no published rating
    After
    case by case
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-15.

  843. · Sangamon County · the act the rating rests on of a scorecard row

    Before
    none
    After
    Sangamon County Board approved a conditional permitted use for a data center on 280 acres of farmland by a vote of 17-10 on April 7, 2026 (2026-04-07)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-04-07.

  844. · Sangamon County · the rating of a scorecard row

    Before
    no published rating
    After
    case by case
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-04-07.

  845. · Logan County · the rating's end date of a scorecard row

    Before
    none
    After
    2026-10-18
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-18, which ends 2026-10-18.

  846. · Logan County · the act the rating rests on of a scorecard row

    Before
    none
    After
    Logan County ordinance amendment requires 30 day written notice period followed by 60 day cure period for environmental discharge (2026-09-18)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-18, which ends 2026-10-18.

  847. · Logan County · the rating of a scorecard row

    Before
    no published rating
    After
    case by case
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-18, which ends 2026-10-18.

  848. · Cook County · the act the rating rests on of a scorecard row

    Before
    none
    After
    More than a dozen data centers near O'Hare airport received local property tax breaks in 2026. (2026-08-29)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-29.

  849. · Cook County · the rating of a scorecard row

    Before
    no published rating
    After
    case by case
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-29.

  850. · Chicago · the act the rating rests on of a scorecard row

    Before
    none
    After
    Chicago Mayor Brandon Johnson signed an executive order for stricter data center regulations (2026-08-11)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-11.

  851. · Chicago · the rating of a scorecard row

    Before
    no published rating
    After
    case by case
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-11.

  852. · Champaign County · the rating's end date of a scorecard row

    Before
    none
    After
    2027-04-01
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-04-01, which ends 2027-04-01.

  853. · Champaign County · the act the rating rests on of a scorecard row

    Before
    none
    After
    Champaign County Board enacted a moratorium in April halting all data center construction, set to expire the following year. (2026-04-01)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-04-01, which ends 2027-04-01.

  854. · Champaign County · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-04-01, which ends 2027-04-01.

  855. · Aurora · the rating's end date of a scorecard row

    Before
    none
    After
    2027-03-14
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-15, which ends 2027-03-14.

  856. · Aurora · the act the rating rests on of a scorecard row

    Before
    none
    After
    Aurora enacted 180 day moratorium on data center and warehouse developments last year and passed ordinance in March requiring council approval for all new data centers (2026-09-15)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-15, which ends 2027-03-14.

  857. · Aurora · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-15, which ends 2027-03-14.

  858. · Sioux County · the rating's end date of a scorecard row

    Before
    none
    After
    2027-06-16
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-06-16, which ends 2027-06-16.

  859. · Sioux County · the act the rating rests on of a scorecard row

    Before
    none
    After
    Sioux County Board of Supervisors passed one year moratorium on construction of data centers and industrial battery storage facilities at June 16 meeting. (2026-06-16)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-06-16, which ends 2027-06-16.

  860. · Sioux County · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-06-16, which ends 2027-06-16.

  861. · Osceola County · the act the rating rests on of a scorecard row

    Before
    none
    After
    Osceola County Board of Supervisors approved waiving the second and third consideration of zoning ordinance to include data center definition (2026-08-24)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-24.

  862. · Osceola County · the rating of a scorecard row

    Before
    no published rating
    After
    case by case
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-24.

  863. · Marshalltown · the rating's end date of a scorecard row

    Before
    none
    After
    2026-12-25
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-25, which ends 2026-12-25.

  864. · Marshalltown · the act the rating rests on of a scorecard row

    Before
    none
    After
    Marshalltown City Council voted to approve a four month moratorium on data center construction (2026-08-25)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-25, which ends 2026-12-25.

  865. · Marshalltown · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-25, which ends 2026-12-25.

  866. · Linn County · the act the rating rests on of a scorecard row

    Before
    none
    After
    Linn County implemented a data center moratorium (2026-08-05)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-05.

  867. · Linn County · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-05.

  868. · Dubuque County · the rating's end date of a scorecard row

    Before
    none
    After
    2027-05-01
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-15, which ends 2027-05-01.

  869. · Dubuque County · the act the rating rests on of a scorecard row

    Before
    none
    After
    A moratorium on new data center applications remains in place in Dubuque County (2026-09-15)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-15, which ends 2027-05-01.

  870. · Dubuque County · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-15, which ends 2027-05-01.

  871. · Adair County · the act the rating rests on of a scorecard row

    Before
    none
    After
    Adair County Board of Supervisors established and imposed a temporary moratorium on construction of data centers in the unincorporated areas of Adair County in March 2026 (2026-09-21)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-21.

  872. · Adair County · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-21.

  873. · Walker County · the act the rating rests on of a scorecard row

    Before
    none
    After
    Walker County commissioners enacted a data center moratorium. (2026-09-06)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-06.

  874. · Walker County · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-06.

  875. · Statesboro · the act the rating rests on of a scorecard row

    Before
    none
    After
    city amended its Unified Development Code on June 2, 2026, to allow data centers in an O office/business zoning district and prohibited hyperscale data centers within city limits (2026-06-02)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-06-02.

  876. · Statesboro · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-06-02.

  877. · Savannah · the rating's end date of a scorecard row

    Before
    none
    After
    2027-02-03
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-01, which ends 2027-02-03.

  878. · Savannah · the act the rating rests on of a scorecard row

    Before
    none
    After
    Savannah City Council approved a 155 day moratorium on large scale data centers (2026-09-01)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-01, which ends 2027-02-03.

  879. · Savannah · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-01, which ends 2027-02-03.

  880. · Marietta · the rating's end date of a scorecard row

    Before
    none
    After
    2027-02-13
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-13, which ends 2027-02-13.

  881. · Marietta · the act the rating rests on of a scorecard row

    Before
    none
    After
    Marietta City Council approved a six month temporary moratorium on new data center applications. (2026-08-13)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-13, which ends 2027-02-13.

  882. · Marietta · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-13, which ends 2027-02-13.

  883. · Floyd County · the act the rating rests on of a scorecard row

    Before
    none
    After
    Floyd County ordinance limits data centers to Heavy Industrial zones and requires impact studies showing anticipated electricity, water, broadband requirements and construction phases. (2026-09-07)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-07.

  884. · Floyd County · the rating of a scorecard row

    Before
    no published rating
    After
    case by case
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-07.

  885. · Chatham County · the rating's end date of a scorecard row

    Before
    none
    After
    2027-02-14
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-14, which ends 2027-02-14.

  886. · Chatham County · the act the rating rests on of a scorecard row

    Before
    none
    After
    Chatham County Commissioners passed a moratorium on large scale data centers of at least 10 megawatts lasting approximately five months (2026-09-14)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-14, which ends 2027-02-14.

  887. · Chatham County · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-14, which ends 2027-02-14.

  888. · Byron · the act the rating rests on of a scorecard row

    Before
    none
    After
    Byron City Council voted to extend moratorium on data centers (2026-09-15)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-15.

  889. · Byron · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-15.

  890. · Martin County · the rating's end date of a scorecard row

    Before
    none
    After
    2027-08-26
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-26, which ends 2027-08-26.

  891. · Martin County · the act the rating rests on of a scorecard row

    Before
    none
    After
    Martin County commissioners voted to have staff return with a proposal for a possible one year moratorium on large scale hyperscale data center development. (2026-08-26)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-26, which ends 2027-08-26.

  892. · Martin County · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-26, which ends 2027-08-26.

  893. · Lake County · the act the rating rests on of a scorecard row

    Before
    none
    After
    Lake County in Central Florida has paused or outright banned permits for new data centers (2026-09-11)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-11.

  894. · Lake County · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-11.

  895. · Fort Meade · the act the rating rests on of a scorecard row

    Before
    none
    After
    Fort Meade data center project was approved by city commission in April (2026-09-22)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-22.

  896. · Fort Meade · the rating of a scorecard row

    Before
    no published rating
    After
    case by case
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-22.

  897. · Kent County · the act the rating rests on of a scorecard row

    Before
    none
    After
    Kent County approved new data center rules (2026-07-25)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-07-25.

  898. · Kent County · the rating of a scorecard row

    Before
    no published rating
    After
    case by case
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-07-25.

  899. · Weld County · the act the rating rests on of a scorecard row

    Before
    none
    After
    Weld County adopted a regulatory framework in April requiring evidence of water availability and electricity provider commitment, imposing noise limits and prohibiting data centers on agricultural land (2026-09-10)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-10.

  900. · Weld County · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-10.

  901. · Douglas County · the act the rating rests on of a scorecard row

    Before
    none
    After
    Tax rebate agreement provides 100% rebate for Douglas County's share of business personal property taxes over 35 years (2026-08-11)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-11.

  902. · Douglas County · the rating of a scorecard row

    Before
    no published rating
    After
    case by case
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-11.

  903. · Denver · the rating's end date of a scorecard row

    Before
    none
    After
    2027-09-07
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-07, which ends 2027-09-07.

  904. · Denver · the act the rating rests on of a scorecard row

    Before
    none
    After
    Denver approved one year moratorium on new data centers in May, scheduled to lift spring 2027 (2026-09-07)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-07, which ends 2027-09-07.

  905. · Denver · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-07, which ends 2027-09-07.

  906. · Aurora · the act the rating rests on of a scorecard row

    Before
    none
    After
    Aurora City Council approved resolution directing city management to update data center development standards (2026-08-22)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-22.

  907. · Aurora · the rating of a scorecard row

    Before
    no published rating
    After
    case by case
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-22.

  908. · Richmond · the act the rating rests on of a scorecard row

    Before
    none
    After
    Richmond recently adopted a temporary moratorium while officials develop local rules (2026-09-22)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-22.

  909. · Richmond · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-22.

  910. · Morgan Hill · the act the rating rests on of a scorecard row

    Before
    none
    After
    Morgan Hill City Council adopted a temporary moratorium on data centers and battery storage facilities while staff develops possibly permanent guidelines (2026-09-14)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-14.

  911. · Morgan Hill · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-14.

  912. · Gilroy · the rating's end date of a scorecard row

    Before
    none
    After
    2026-10-30
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-14, which ends 2026-10-30.

  913. · Gilroy · the act the rating rests on of a scorecard row

    Before
    none
    After
    The moratorium would not affect the Amazon data center already approved and under construction on Camino Arroyo (2026-09-14)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-14, which ends 2026-10-30.

  914. · Gilroy · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-14, which ends 2026-10-30.

  915. · Pinal County · the act the rating rests on of a scorecard row

    Before
    none
    After
    Pinal County Board of Supervisors voted 4-1 against rezoning land for Vermaland data center project south of Eloy (2026-08-26)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-26.

  916. · Pinal County · the rating of a scorecard row

    Before
    no published rating
    After
    case by case
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-26.

  917. · Pima County · the rating's end date of a scorecard row

    Before
    none
    After
    2026-12-24
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-26, which ends 2026-12-24.

  918. · Pima County · the act the rating rests on of a scorecard row

    Before
    none
    After
    On Aug. 26, Pima County Board of Health passed unanimous motion advising supervisors to adopt the 120 day moratorium to prevent irrevocable public harm. (2026-08-26)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-26, which ends 2026-12-24.

  919. · Pima County · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-26, which ends 2026-12-24.

  920. · Mesa · the act the rating rests on of a scorecard row

    Before
    none
    After
    Mesa City Council unanimously approved data center amendments on July 8, 2025, with two members absent (2025-07-08)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2025-07-08.

  921. · Mesa · the rating of a scorecard row

    Before
    restrictive
    After
    case by case
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2025-07-08.

  922. · Maricopa County · the act the rating rests on of a scorecard row

    Before
    none
    After
    The modernized ordinance updated how the county defines a data center and restricts them to industrial areas (2025-12-11)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2025-12-11.

  923. · Maricopa County · the rating of a scorecard row

    Before
    no published rating
    After
    case by case
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2025-12-11.

  924. · Chandler · the act the rating rests on of a scorecard row

    Before
    none
    After
    Chandler capped data center water use (2026-06-22)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-06-22.

  925. · Chandler · the rating of a scorecard row

    Before
    no published rating
    After
    case by case
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-06-22.

  926. · Pulaski County · the act the rating rests on of a scorecard row

    Before
    none
    After
    Pulaski County Quorum Court on September 22, 2026 passed 11-4 an ordinance to regulate large data centers in unincorporated parts of the county, covering noise, fire safety, and water consumption. AVAIO Digital's proposed $6 billion, 1 gigawatt Wrightsville campus will be subject to the new rules. (2026-09-22)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-22.

  927. · Pulaski County · the rating of a scorecard row

    Before
    no published rating
    After
    case by case
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-22.

  928. · North Little Rock · the act the rating rests on of a scorecard row

    Before
    none
    After
    North Little Rock approved new zoning regulations establishing where data center campuses can operate and what requirements developments must meet before receiving approval. (2026-09-15)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-15.

  929. · North Little Rock · the rating of a scorecard row

    Before
    no published rating
    After
    case by case
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-15.

  930. · Fayetteville · the act the rating rests on of a scorecard row

    Before
    none
    After
    Existing regulations were approved June 16 (2026-06-16)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-06-16.

  931. · Fayetteville · the rating of a scorecard row

    Before
    restrictive
    After
    case by case
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-06-16.

  932. · Westover · the rating's end date of a scorecard row

    Before
    none
    After
    2027-02-18
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-18, which ends 2027-02-18.

  933. · Westover · the act the rating rests on of a scorecard row

    Before
    none
    After
    Westover approved a 6 month moratorium on data centers (2026-08-18)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-18, which ends 2027-02-18.

  934. · Westover · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-18, which ends 2027-02-18.

  935. · Tarrant · the rating's end date of a scorecard row

    Before
    none
    After
    2027-09-09
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-09, which ends 2027-09-09.

  936. · Tarrant · the act the rating rests on of a scorecard row

    Before
    none
    After
    City of Tarrant approved a 12 month moratorium on data centers (2026-09-09)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-09, which ends 2027-09-09.

  937. · Tarrant · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-09, which ends 2027-09-09.

  938. · Homewood · the act the rating rests on of a scorecard row

    Before
    none
    After
    Homewood temporarily paused new data center applications (2026-09-08)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-08.

  939. · Homewood · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-08.

  940. · Harpersville · the rating's end date of a scorecard row

    Before
    none
    After
    2027-03-01
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-01, which ends 2027-03-01.

  941. · Harpersville · the act the rating rests on of a scorecard row

    Before
    none
    After
    Harpersville city council approved six month pause on data center projects in August 2026, followed by first of six public information sessions (2026-09-01)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-01, which ends 2027-03-01.

  942. · Harpersville · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-01, which ends 2027-03-01.

  943. · Chelsea · the rating's end date of a scorecard row

    Before
    none
    After
    2027-07-21
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-07-21, which ends 2027-07-21.

  944. · Chelsea · the act the rating rests on of a scorecard row

    Before
    none
    After
    Chelsea adopted a one year data center moratorium on July 21, 2026. (2026-07-21)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-07-21, which ends 2027-07-21.

  945. · Chelsea · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-07-21, which ends 2027-07-21.

  946. · Baldwin County · the rating of a scorecard row

    Before
    restrictive
    After
    no published rating
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): no binding act in force on the row under the rubric as clarified on 2026-10-10.

  947. · Anniston · the rating's end date of a scorecard row

    Before
    none
    After
    2027-08-18
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-18, which ends 2027-08-18.

  948. · Anniston · the act the rating rests on of a scorecard row

    Before
    none
    After
    Anniston City Council adopted Resolution No. 26 R-97 on August 18, 2026, imposing a 12 month moratorium on data center permitting, development, expansion and licensing. (2026-08-18)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-18, which ends 2027-08-18.

  949. · Anniston · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-18, which ends 2027-08-18.

  950. · Wyoming · the act the rating rests on of a scorecard row

    Before
    none
    After
    Wyoming Gov. Mark Gordon signed Executive Order 2026-03 titled Data Centers the Wyoming Way on June 3, 2026 to create a framework for responsible development (2026-06-03)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-06-03.

  951. · Wyoming · the rating of a scorecard row

    Before
    no published rating
    After
    case by case
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-06-03.

  952. · West Virginia · the act the rating rests on of a scorecard row

    Before
    none
    After
    Half of all revenue from certified data center projects goes toward reducing the State Personal Income Tax, host counties receive 30 percent, all other counties share 10 percent, and 10 percent goes to local infrastructure upgrades (2026-08-11)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-11.

  953. · West Virginia · the rating of a scorecard row

    Before
    no published rating
    After
    case by case
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-11.

  954. · Wisconsin · the act the rating rests on of a scorecard row

    Before
    none
    After
    Wisconsin Department of Natural Resources found Vantage will meet air pollution limits and granted preliminary approval for air pollution control permits (2026-04-15)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-04-15.

  955. · Wisconsin · the rating of a scorecard row

    Before
    restrictive
    After
    case by case
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-04-15.

  956. · Washington · the act the rating rests on of a scorecard row

    Before
    none
    After
    Washington law Senate Bill 6231 removed tax exemptions for replacement server equipment and ended eligibility for certain refurbished data centers in 2026. (2026-09-09)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-09.

  957. · Washington · the rating of a scorecard row

    Before
    no published rating
    After
    case by case
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-09.

  958. · Virginia · the act the rating rests on of a scorecard row

    Before
    none
    After
    In Virginia, state lawmakers in the General Assembly passed legislation this year to tighten restrictions on backup generators and introduce a new energy consumption tax (2026-01-01)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-01-01.

  959. · Virginia · the rating of a scorecard row

    Before
    no published rating
    After
    case by case
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-01-01.

  960. · Utah · the act the rating rests on of a scorecard row

    Before
    none
    After
    Governor Spencer Cox signed an executive order establishing a framework for data center development (2026-06-01)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-06-01.

  961. · Utah · the rating of a scorecard row

    Before
    restrictive
    After
    case by case
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-06-01.

  962. · United States (federal) · the act the rating rests on of a scorecard row

    Before
    none
    After
    More than ten states paused or canceled data center tax exemptions (2026-09-09)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-09.

  963. · United States (federal) · the rating of a scorecard row

    Before
    no published rating
    After
    case by case
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-09.

  964. · Texas · the rating's end date of a scorecard row

    Before
    none
    After
    2027-08-01
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-03, which ends 2027-08-01.

  965. · Texas · the act the rating rests on of a scorecard row

    Before
    none
    After
    Governor Abbott paused ERCOT Batch Zero on August 3, 2026 to audit grid usage. (2026-08-03)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-03, which ends 2027-08-01.

  966. · Texas · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-03, which ends 2027-08-01.

  967. · Tennessee · the act the rating rests on of a scorecard row

    Before
    none
    After
    TVA Board of Directors approves rate increase for data centers (2026-08-20)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-20.

  968. · Tennessee · the rating of a scorecard row

    Before
    no published rating
    After
    case by case
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-20.

  969. · Saskatchewan · the act the rating rests on of a scorecard row

    Before
    none
    After
    Saskatchewan Government announces new data centre framework with six key principles: domestic ownership and sovereignty, creation of Saskatchewan jobs, industry experience, centralized provincial intake process, and self supplied power generation (2026-08-27)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-27.

  970. · Saskatchewan · the rating of a scorecard row

    Before
    no published rating
    After
    case by case
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-27.

  971. · South Dakota · the act the rating rests on of a scorecard row

    Before
    none
    After
    South Dakota passed a law requiring data center operators to cover their own electrical usage and infrastructure expenses (2026-09-02)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-02.

  972. · South Dakota · the rating of a scorecard row

    Before
    no published rating
    After
    case by case
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-02.

  973. · South Carolina · the rating's end date of a scorecard row

    Before
    none
    After
    2027-09-05
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-05, which ends 2027-09-05.

  974. · South Carolina · the act the rating rests on of a scorecard row

    Before
    none
    After
    A one year water reporting requirement for data centers passed in the South Carolina state budget (2026-09-05)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-05, which ends 2027-09-05.

  975. · South Carolina · the rating of a scorecard row

    Before
    no published rating
    After
    case by case
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-05, which ends 2027-09-05.

  976. · Pennsylvania · the act the rating rests on of a scorecard row

    Before
    none
    After
    PUC established model large load tariff in May 2026 to ensure customers requiring 50 megawatts or more bear the costs they add to electric system (2026-05-01)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-05-01.

  977. · Pennsylvania · the rating of a scorecard row

    Before
    no published rating
    After
    case by case
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-05-01.

  978. · Oregon · the rating's end date of a scorecard row

    Before
    none
    After
    2027-07-01
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-08, which ends 2027-07-01.

  979. · Oregon · the act the rating rests on of a scorecard row

    Before
    none
    After
    Governor Kotek issued executive order pausing all state agency action on data center land requests on September 8, 2026 (2026-09-08)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-08, which ends 2027-07-01.

  980. · Ontario · the rating of a scorecard row

    Before
    case by case
    After
    no published rating
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): no binding act in force on the row under the rubric as clarified on 2026-10-10.

  981. · Ohio · the rating's end date of a scorecard row

    Before
    none
    After
    2027-05-01
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-03, which ends 2027-05-01.

  982. · Ohio · the act the rating rests on of a scorecard row

    Before
    none
    After
    Ohio Governor Mike DeWine put a pause on all new data centers beginning October 1, 2026. (2026-09-03)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-03, which ends 2027-05-01.

  983. · Ohio · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-03, which ends 2027-05-01.

  984. · New York · the rating's end date of a scorecard row

    Before
    none
    After
    2027-07-01
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-07-01, which ends 2027-07-01.

  985. · New York · the act the rating rests on of a scorecard row

    Before
    none
    After
    New York Gov. Kathy Hochul issued executive order in July 2026 to pause for up to one year permits for new data centers that are at least 50 megawatts (2026-07-01)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-07-01, which ends 2027-07-01.

  986. · Nevada · the act the rating rests on of a scorecard row

    Before
    none
    After
    Nevada approved $17.6 million in tax breaks for 9 companies, including data center partners. (2026-08-10)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-10.

  987. · Nevada · the rating of a scorecard row

    Before
    no published rating
    After
    case by case
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-10.

  988. · New Mexico · the act the rating rests on of a scorecard row

    Before
    none
    After
    New Mexico Commissioner of Public Lands Stephanie Garcia Richard blocked the Aetherion data center proposal at Spaceport America (2026-09-03)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-03.

  989. · New Mexico · the rating of a scorecard row

    Before
    no published rating
    After
    case by case
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-03.

  990. · New Jersey · the rating's end date of a scorecard row

    Before
    none
    After
    2027-02-27
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-27, which ends 2027-02-27.

  991. · New Jersey · the act the rating rests on of a scorecard row

    Before
    none
    After
    Governor Mikie Sherrill signed legislation S3379 on August 27, 2026 requiring data centers to self report water and energy usage every six months to the New Jersey Board of Public Utilities (2026-08-27)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-27, which ends 2027-02-27.

  992. · New Jersey · the rating of a scorecard row

    Before
    restrictive
    After
    case by case
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-27, which ends 2027-02-27.

  993. · Nebraska · the act the rating rests on of a scorecard row

    Before
    none
    After
    Nebraska ended one data center tax break (2026-06-05)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-06-05.

  994. · North Carolina · the act the rating rests on of a scorecard row

    Before
    none
    After
    North Carolina Senate Bill 730 (Ratepayer Protection Act) defines data centers as facilities with peak monthly electricity demand of 100 megawatts or greater and passed state house 69-44 (2026-08-24)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-24.

  995. · Montana · the act the rating rests on of a scorecard row

    Before
    none
    After
    NorthWestern Energy filed a large load tariff with the Montana PSC in March to require data centers to pay separate higher rates for energy use. (2026-09-08)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-08.

  996. · Missouri · the act the rating rests on of a scorecard row

    Before
    none
    After
    Missouri enacted legislation in 2025 requiring regulators to establish rates for large load customers, including data centers, to reflect those customers' costs. (2026-09-12)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-12.

  997. · Missouri · the rating of a scorecard row

    Before
    no published rating
    After
    case by case
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-12.

  998. · Minnesota · the act the rating rests on of a scorecard row

    Before
    none
    After
    Minnesota repealed the sales tax exemption for electricity used by qualified data centers effective for sales and purchases after June 30, 2025. (2026-09-09)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-09.

  999. · Minnesota · the rating of a scorecard row

    Before
    no published rating
    After
    case by case
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-09.

  1000. · Michigan · the act the rating rests on of a scorecard row

    Before
    none
    After
    Michigan incentives exempt qualifying data center projects from 6% tax on construction materials and computer equipment through at least 2050 (2026-09-11)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-11.

  1001. · Michigan · the rating of a scorecard row

    Before
    restrictive
    After
    case by case
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-11.

  1002. · Maryland · the act the rating rests on of a scorecard row

    Before
    none
    After
    Governor Wes Moore signed executive order requiring community and state approval for data center development, encouraging private financing for energy costs, and requiring compliance with environmental guidelines (2026-09-23)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-23.

  1003. · Maryland · the rating of a scorecard row

    Before
    no published rating
    After
    case by case
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-23.

  1004. · Massachusetts · the act the rating rests on of a scorecard row

    Before
    none
    After
    Healey paused new applications for the state's data center sales tax exemption in June 2026 (2026-06-01)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-06-01.

  1005. · Massachusetts · the rating of a scorecard row

    Before
    restrictive
    After
    case by case
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-06-01.

  1006. · Louisiana · the act the rating rests on of a scorecard row

    Before
    none
    After
    On August 20, 2025, the Louisiana PSC voted to approve Entergy's settlement to build generation and transmission infrastructure for Meta's $50 billion data center in Richland Parish (2025-08-20)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2025-08-20.

  1007. · Louisiana · the rating of a scorecard row

    Before
    no published rating
    After
    case by case
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2025-08-20.

  1008. · Kentucky · the act the rating rests on of a scorecard row

    Before
    none
    After
    Gov. Beshear issued an executive order on Aug. 6 directing the Kentucky Public Service Commission and Energy and Environment Cabinet to limit data center harms. (2026-08-06)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-06.

  1009. · Kentucky · the rating of a scorecard row

    Before
    no published rating
    After
    case by case
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-06.

  1010. · Illinois · the act the rating rests on of a scorecard row

    Before
    none
    After
    Governor Pritzker paused new state data center tax credit agreements starting July 1, 2026 (2026-08-24)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-24.

  1011. · Illinois · the rating of a scorecard row

    Before
    no published rating
    After
    case by case
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-24.

  1012. · Georgia · the act the rating rests on of a scorecard row

    Before
    none
    After
    Georgia Public Service Commission approved Georgia Power's contract to supply electricity to OpenAI's Effingham County data center (2026-08-27)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-27.

  1013. · Georgia · the rating of a scorecard row

    Before
    no published rating
    After
    case by case
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-27.

  1014. · Florida · the act the rating rests on of a scorecard row

    Before
    none
    After
    Senate Bill 484 passed the Florida legislature and requires that minimum tariff and service requirements must reasonably ensure that each large load customer bears its own cost of service and that those costs are not shifted to the general body of ratepayers. (2026-08-28)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-28.

  1015. · Florida · the rating of a scorecard row

    Before
    restrictive
    After
    case by case
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-28.

  1016. · Delaware · the act the rating rests on of a scorecard row

    Before
    none
    After
    Delaware Governor Matt Meyer signed legislation requiring data centers to build clean energy to power their facilities (2026-08-26)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-26.

  1017. · Delaware · the rating of a scorecard row

    Before
    no published rating
    After
    case by case
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-26.

  1018. · Connecticut · the rating of a scorecard row

    Before
    case by case
    After
    no published rating
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): no binding act in force on the row under the rubric as clarified on 2026-10-10.

  1019. · California · the act the rating rests on of a scorecard row

    Before
    none
    After
    California enacted regulations for data center electricity rates (2026-09-01)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-01.

  1020. · California · the rating of a scorecard row

    Before
    no published rating
    After
    case by case
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-01.

  1021. · Arizona · the act the rating rests on of a scorecard row

    Before
    none
    After
    Arizona Corporation Commission approved an Energy Supply Agreement between Tucson Electric Power and the developers of Project Blue (2025-12-10)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2025-12-10.

  1022. · Arizona · the rating of a scorecard row

    Before
    no published rating
    After
    case by case
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2025-12-10.

  1023. · Arkansas · the act the rating rests on of a scorecard row

    Before
    none
    After
    $300 million allocated from state budget for economic incentives and infrastructure for advanced manufacturing super project in West Memphis (2026-04-24)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-04-24.

  1024. · Arkansas · the rating of a scorecard row

    Before
    no published rating
    After
    case by case
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-04-24.

  1025. · Alabama · the act the rating rests on of a scorecard row

    Before
    none
    After
    Alabama Public Service Commission approved two year electric rate freeze and two solar projects for Meta data center (2025-12-03)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2025-12-03.

  1026. · Alabama · the rating of a scorecard row

    Before
    no published rating
    After
    case by case
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2025-12-03.

  1027. · Alaska · the rating of a scorecard row

    Before
    case by case
    After
    no published rating
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): no binding act in force on the row under the rubric as clarified on 2026-10-10.

  1028. · Alberta · the act the rating rests on of a scorecard row

    Before
    none
    After
    Alberta Utilities Commission paused an application tied to a massive data centre planned for Olds (2026-08-17)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-17.

  1029. · Alberta · the rating of a scorecard row

    Before
    no published rating
    After
    case by case
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): case by case under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-17.

  1030. · Effingham County · the act the rating rests on of a scorecard row

    Before
    none
    After
    Ordinance 2026-352 changed county zoning rules to allow data centers on property already zoned for industrial use (2026-09-03)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): open under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-03.

  1031. · Effingham County · the rating of a scorecard row

    Before
    restrictive
    After
    open
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): open under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-03.

  1032. · North Dakota · the act the rating rests on of a scorecard row

    Before
    none
    After
    The 2015 Legislature approved the original data center tax exemption with the current version set by the 2021 Legislature (2026-08-27)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): open under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-27.

  1033. · North Dakota · the rating of a scorecard row

    Before
    case by case
    After
    open
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): open under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-27.

  1034. · Kansas · the act the rating rests on of a scorecard row

    Before
    none
    After
    Kansas enacted Senate Bill 98 in 2025 providing data centers with 20 year exemption from state and local sales taxes (2026-09-09)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): open under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-09.

  1035. · Kansas · the rating of a scorecard row

    Before
    no published rating
    After
    open
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): open under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-09.

  1036. · Idaho · the act the rating rests on of a scorecard row

    Before
    none
    After
    Idaho provided sales tax exemption for data centers approved in 2020 legislative session (2026-09-11)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): open under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-11.

  1037. · Idaho · the rating of a scorecard row

    Before
    no published rating
    After
    open
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): open under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-11.

  1038. · Shawnee · the rating's end date of a scorecard row

    Before
    none
    After
    2027-12-31
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): closed under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-19, which ends 2027-12-31.

  1039. · Shawnee · the act the rating rests on of a scorecard row

    Before
    none
    After
    Shawnee approved a temporary moratorium on new data centers effective immediately through end of 2027 (2026-08-19)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): closed under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-19, which ends 2027-12-31.

  1040. · Shawnee · the rating of a scorecard row

    Before
    no published rating
    After
    closed
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): closed under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-19, which ends 2027-12-31.

  1041. · Ralls County · the rating's end date of a scorecard row

    Before
    none
    After
    2027-08-25
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-25, which ends 2027-08-25 (item 8: the commission adopted a one year moratorium; its end is the act's own term, a year from August 25, 2026).

  1042. · Ralls County · the act the rating rests on of a scorecard row

    Before
    none
    After
    Ralls County Commission approved a one year moratorium on data centers halting economic development applications until September 2027. (2026-08-25)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-25, which ends 2027-08-25 (item 8: the commission adopted a one year moratorium; its end is the act's own term, a year from August 25, 2026).

  1043. · Ralls County · the rating of a scorecard row

    Before
    no published rating
    After
    restrictive
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): restrictive under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-25, which ends 2027-08-25 (item 8: the commission adopted a one year moratorium; its end is the act's own term, a year from August 25, 2026).

  1044. · Baltimore County · the rating's end date of a scorecard row

    Before
    none
    After
    2027-12-31
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): closed under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-23, which ends 2027-12-31.

  1045. · Baltimore County · the act the rating rests on of a scorecard row

    Before
    none
    After
    Baltimore County Council voted unanimously to extend the data center moratorium through at least the end of 2027 (2026-09-23)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): closed under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-23, which ends 2027-12-31.

  1046. · Baltimore County · the rating of a scorecard row

    Before
    no published rating
    After
    closed
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): closed under the rubric as clarified on 2026-10-10, resting on the act of 2026-09-23, which ends 2027-12-31.

  1047. · Indianapolis · the rating's end date of a scorecard row

    Before
    none
    After
    2027-12-31
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): closed under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-29, which ends 2027-12-31.

  1048. · Indianapolis · the act the rating rests on of a scorecard row

    Before
    none
    After
    Indianapolis approved construction of three data centers before agreeing to a moratorium through 2027 (2026-08-29)
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): closed under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-29, which ends 2027-12-31.

  1049. · Indianapolis · the rating of a scorecard row

    Before
    no published rating
    After
    closed
    Why
    the editor's word of 2026-10-12 (batch decisions-1013): closed under the rubric as clarified on 2026-10-10, resting on the act of 2026-08-29, which ends 2027-12-31.

  1050. · Hyperscale Data Dowagiac AI Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Held unplaced under the record's rules (2026-10-13): the entry's words are about Kansas, and this record is in Michigan. Kept off the record, never deleted; it can be restored.

  1051. · Hyperscale Data Dowagiac AI Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Held unplaced under the record's rules (2026-10-13): the entry's words are about Kansas, and this record is in Michigan. Kept off the record, never deleted; it can be restored.

  1052. · Hyperscale Data Dowagiac AI Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Held unplaced under the record's rules (2026-10-13): the entry's words are about Kansas, and this record is in Michigan. Kept off the record, never deleted; it can be restored.

  1053. · Meta Eagle Mountain Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Held unplaced under the record's rules (2026-10-13): the entry's words are about Iowa, and this record is in Utah. Kept off the record, never deleted; it can be restored.

  1054. · Meta Eagle Mountain Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Held unplaced under the record's rules (2026-10-13): the entry's words are about Ohio, and this record is in Utah. Kept off the record, never deleted; it can be restored.

  1055. · Novva West Jordan Data Center Campus · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Held unplaced under the record's rules (2026-10-13): the entry's words are about Nevada, and this record is in Utah. Kept off the record, never deleted; it can be restored.

  1056. · bell-ai-fabric-saskatchewan-data-centre-sherwood-sk · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Held unplaced under the record's rules (2026-10-13): the entry's words are about Alberta, and this record is in Saskatchewan. Kept off the record, never deleted; it can be restored.

  1057. · Amazon Web Services Louisiana data centers · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Held unplaced under the record's rules (2026-10-13): the entry's words are about UAE, and this record is in Louisiana. Kept off the record, never deleted; it can be restored.

  1058. · Amazon Web Services Louisiana data centers · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Held unplaced under the record's rules (2026-10-13): the entry's words are about Bahrain, and this record is in Louisiana. Kept off the record, never deleted; it can be restored.

  1059. · Amazon Web Services Louisiana data centers · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Held unplaced under the record's rules (2026-10-13): the entry's words are about Bahrain, UAE, and this record is in Louisiana. Kept off the record, never deleted; it can be restored.

  1060. · Google New Florence data center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Held unplaced under the record's rules (2026-10-13): the entry's words are about Alberta, and this record is in Missouri. Kept off the record, never deleted; it can be restored.

  1061. · NScale Mason County Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Held unplaced under the record's rules (2026-10-13): the entry's words are about Norway, and this record is in West Virginia. Kept off the record, never deleted; it can be restored.

  1062. · Google Hermantown Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Held unplaced under the record's rules (2026-10-13): the entry's words are about North Dakota, and this record is in Minnesota. Kept off the record, never deleted; it can be restored.

  1063. · Hyperscale Data Dowagiac AI Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Held unplaced under the record's rules (2026-10-13): the entry's words are about Kansas, and this record is in Michigan. Kept off the record, never deleted; it can be restored.

  1064. · Hyperscale Data Dowagiac AI Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Held unplaced under the record's rules (2026-10-13): the entry's words are about Kansas, and this record is in Michigan. Kept off the record, never deleted; it can be restored.

  1065. · Hyperscale Data Dowagiac AI Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Held unplaced under the record's rules (2026-10-13): the entry's words are about Kansas, and this record is in Michigan. Kept off the record, never deleted; it can be restored.

  1066. · Google Hermantown Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Held unplaced under the record's rules (2026-10-13): the entry's words are about North Dakota, and this record is in Minnesota. Kept off the record, never deleted; it can be restored.

  1067. · Google Hermantown Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Held unplaced under the record's rules (2026-10-13): the entry's words are about North Dakota, and this record is in Minnesota. Kept off the record, never deleted; it can be restored.

  1068. · Google Hermantown Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Held unplaced under the record's rules (2026-10-13): the entry's words are about North Dakota, and this record is in Minnesota. Kept off the record, never deleted; it can be restored.

  1069. · Montgomery Meta Investment · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Held unplaced under the record's rules (2026-10-13): the entry's words are about South Carolina, and this record is in Alabama. Kept off the record, never deleted; it can be restored.

  1070. · TierPoint Allentown TekPark Data Center · the location of a record

    Before
    40.5960948, -75.4755779 (city)
    After
    40.543123, -75.659852 (address)
    Why
    TierPoint names the site for Allentown, and the record had placed it at Allentown's center. The Pennsylvania DEP's Data Center Permit Tracker places the TekPark campus in Upper Macungie Township, Lehigh County, and TierPoint's own TekPark page prints its address, 9999 Hamilton Boulevard, Building #4, Breinigsville, PA 18031, which the Census Bureau's geocoder places in that township. Corrected on the editor's word.

  1071. · TierPoint Allentown TekPark Data Center · the city of a record

    Before
    Allentown
    After
    Upper Macungie Township
    Why
    TierPoint names the site for Allentown, and the record had placed it at Allentown's center. The Pennsylvania DEP's Data Center Permit Tracker places the TekPark campus in Upper Macungie Township, Lehigh County, and TierPoint's own TekPark page prints its address, 9999 Hamilton Boulevard, Building #4, Breinigsville, PA 18031, which the Census Bureau's geocoder places in that township. Corrected on the editor's word.

  1072. · 1205 Commonwealth Dr. Data Center (Pennhurst) · the developer of a record

    Before
    After
    Pennhurst Holdings LLC
    Why
    Filled from the draft record merged into this one, whose source (The Cool Down, on East Vincent Township's vote of May 2026) names Pennhurst Holdings LLC as the developer. Corrected on the editor's word.

  1073. · QTS Howard County · the summary of a record

    Before
    QTS Data Centers lists a data center at Howard County, Texas among the sites it operates.
    After
    A QTS Data Centers site in Howard County, Texas, which QTS lists as in consideration.
    Why
    The summary said QTS operates a site in Howard County; QTS lists the site as in consideration. Corrected on the editor's word.

  1074. · QTS Howard County · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    QTS lists its Howard County, Texas site as in consideration, which the read of QTS's page of September 14, 2026 took for a running site. An operator's in consideration or planned never reads as running: the entry comes off the record, QTS's listing stays among its sources, and an entry at the stage the page supports goes on. Returned to draft on the editor's word.

  1075. · TECfusions Keystone Connect AI Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    The entry's words report Building J live and serving a tenant while its stage read reported. It returns to draft and the report goes back on the record at the stage its words support, beside TECfusions' own announcement of August 27, 2026. Returned to draft on the editor's word.

  1076. · TECfusions Keystone Connect AI Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    The Pennsylvania DEP's Data Center Permit Tracker lists TECfusions' campus as DEP review complete, which the record shows as the state permit status. TECfusions announced on August 27, 2026 that its New Kensington data center is live, and a permit register never moves a record backward. Returned to draft on the editor's word.

  1077. · Homer City Energy Campus Redevelopment · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    The Pennsylvania DEP's Data Center Permit Tracker lists the Homer City project as proposed with no permit applications received. That is the state permit status, which the record shows, and not the project's stage: reporting from the site, the Post-Gazette's of September 4, 2026 among it, has the plant redevelopment being built, and a permit register never moves a record backward. Returned to draft on the editor's word.

  1078. · QTS Salem Township · the location of a record

    Before
    41.225282, -79.615019 (city)
    After
    41.069512, -76.170543 (permit point)
    Why
    QTS's own list of data centers was read as placing its Salem campus at Salem, Clarion County; the Pennsylvania DEP's Data Center Permit Tracker places it in Salem Township, Luzerne County, at the point its permits name, where the record's own sources report it. Corrected on the editor's word.

  1079. · QTS Salem Township · the city of a record

    Before
    Salem
    After
    Salem Township
    Why
    QTS's own list of data centers was read as placing its Salem campus at Salem, Clarion County; the Pennsylvania DEP's Data Center Permit Tracker places it in Salem Township, Luzerne County, at the point its permits name, where the record's own sources report it. Corrected on the editor's word.

  1080. · QTS Salem Township · the county of a record

    Before
    Clarion County
    After
    Luzerne County
    Why
    QTS's own list of data centers was read as placing its Salem campus at Salem, Clarion County; the Pennsylvania DEP's Data Center Permit Tracker places it in Salem Township, Luzerne County, at the point its permits name, where the record's own sources report it. Corrected on the editor's word.

  1081. · the date label of 36 timeline entries

    Before
    content
    After
    source
    Why
    36 timeline entries say the Pennsylvania DEP's Data Center Permit Tracker listed a project as proposed as of the day the record read it; they were labeled as having happened that day, so a record read "proposed since" that day. Each is now labeled as reported that day. No date or word changed.

  1082. · the last verified date of 12 records and scorecard rows

    Before
    The day of an entry not yet published, printed as the day the page was last verified.
    After
    The day of the newest published entry.
    Why
    11 scorecard rows and 1 records had taken the day of an entry still awaiting review as the day they were last verified, so their pages printed a day no published entry stands behind. Each now carries its newest published entry's day. No entry, date or word changed.

  1083. · Butte-Silver Bow Data Center (ballot initiative) · the kind of a timeline entry

    Before
    approval
    After
    other
    Why
    The sentence says an approval is still needed or would be required, which no body has given; the entry's kind corrected on the editor's word.

  1084. · NTT Mesa data center campus · the kind of a timeline entry

    Before
    approval
    After
    other
    Why
    The sentence says an approval is still needed or would be required, which no body has given; the entry's kind corrected on the editor's word.

  1085. · 900 Conshohocken Rd. Data Center · the kind of a timeline entry

    Before
    approval
    After
    filing
    Why
    The sentence says the developer is seeking approval, which is a request before the township, not an approval; the entry's kind corrected on the editor's word.

  1086. · MLP Ventures King of Prussia Data Center Campus · the kind of a timeline entry

    Before
    approval
    After
    filing
    Why
    The sentence says the developer is seeking approval, which is a request before the township, not an approval; the entry's kind corrected on the editor's word.

  1087. · 900 Conshohocken Rd. Data Center · the record of a timeline entry

    Before
    mlp-ventures-king-of-prussia-data-center-campus-pa
    After
    900-conshohocken-rd-data-center-plymouth-township-pa
    Why
    The entry describes MLP Ventures' facility at 900 Conshohocken Road in Plymouth Township, which the Pennsylvania DEP's tracker lists apart from the King of Prussia campus; moved to that site's record on the editor's word.

  1088. · MLP Ventures King of Prussia Data Center Campus · the publication of a record

    Before
    published
    After
    draft
    Why
    The same proposal as MLP Ventures' King of Prussia data center campus: the Pennsylvania DEP's Data Center Permit Tracker lists MLP's Upper Merion project at five addresses on one campus. The record is folded into the campus record, its sources, entries and items with it, and its address leads there; returned to draft on the editor's word so the two can be merged.

  1089. · 1205 Commonwealth Dr. Data Center (Pennhurst) · the developer of a record

    Before
    former Pennhurst Asylum
    After
    Why
    The Pennsylvania DEP's tracker names this project "1205 Commonwealth Dr. Data Center (former Pennhurst Asylum)": the words in brackets describe the site and name no applicant, and were read as its developer. Corrected on the editor's word.

  1090. · QTS Salem Township · the summary of a record

    Before
    QTS Data Centers lists a data center at Salem, Pennsylvania among the sites it operates.
    After
    A QTS Data Centers campus in Salem Township, Luzerne County, Pennsylvania.
    Why
    The summary said QTS operates a site at Salem; the campus is in Salem Township, Luzerne County, and is not running. Corrected on the editor's word.

  1091. · QTS Salem Township · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    QTS lists its Salem Township campus as in consideration, which the read of QTS's page took for a running site; the Pennsylvania DEP's Data Center Permit Tracker lists the campus with permits under review. The entry comes off the record and QTS's listing stays among its sources; returned to draft on the editor's word.

  1092. · Boyce · the county of a scorecard row

    Before
    After
    Rapides Parish
    Why
    The row named no parish, so its page sat on the state of Louisiana; the Census Bureau's places file puts Boyce in Rapides Parish.

  1093. · Edgeconnex New Orleans Holdings LLC · the county of a record

    Before
    ST. Tammany Parish
    After
    St. Tammany Parish
    Why
    Louisiana's county equivalents are parishes, as the Census Bureau names them; the record stored ST. Tammany Parish, which the pages printed as ST. Tammany Parish, and its page sat apart from the parish's own.

  1094. · One Nuclear / Project Cayman Data Center Campus · the county of a record

    Before
    Vermilion
    After
    Vermilion Parish
    Why
    Louisiana's county equivalents are parishes, as the Census Bureau names them; the record stored Vermilion, which the pages printed as Vermilion County, and its page sat apart from the parish's own.

  1095. · Meta Louisiana data center · the county of a record

    Before
    Richland
    After
    Richland Parish
    Why
    Louisiana's county equivalents are parishes, as the Census Bureau names them; the record stored Richland, which the pages printed as Richland County, and its page sat apart from the parish's own.

  1096. · Caddo Parish Data Center · the county of a record

    Before
    Caddo
    After
    Caddo Parish
    Why
    Louisiana's county equivalents are parishes, as the Census Bureau names them; the record stored Caddo, which the pages printed as Caddo County, and its page sat apart from the parish's own.

  1097. · Livingston Parish Data Center · the county of a record

    Before
    Livingston
    After
    Livingston Parish
    Why
    Louisiana's county equivalents are parishes, as the Census Bureau names them; the record stored Livingston, which the pages printed as Livingston County, and its page sat apart from the parish's own.

  1098. · SpaceX Starbase Louisiana / orbital data center · the county of a record

    Before
    Vermilion
    After
    Vermilion Parish
    Why
    Louisiana's county equivalents are parishes, as the Census Bureau names them; the record stored Vermilion, which the pages printed as Vermilion County, and its page sat apart from the parish's own.

  1099. · Delta Forge 1 · the county of a record

    Before
    Rapides
    After
    Rapides Parish
    Why
    Louisiana's county equivalents are parishes, as the Census Bureau names them; the record stored Rapides, which the pages printed as Rapides County, and its page sat apart from the parish's own.

  1100. · a record · the publication of a scorecard event

    Before
    published
    After
    draft
    Why
    A line an article about Pennsylvania wrote about Texas: Texas's large load rules are on Texas's row, from the Public Utility Commission's own adoption. It is not Pennsylvania's act.

  1101. · a record · the publication of a scorecard event

    Before
    published
    After
    draft
    Why
    A line an article about Pennsylvania wrote about two other states: New York's moratorium and Illinois's pause of its data center incentives are each on their own state's row, from their own sources (New York's executive order of July 14, 2026; Illinois's pause from July 1, 2026). It is not Pennsylvania's act.

  1102. · a record · the publication of a scorecard event

    Before
    published
    After
    draft
    Why
    A line a South Dakota page wrote about Oklahoma: Oklahoma's law is on the record as H.B. 2992 of 2026 on Oklahoma's laws page. It is not South Dakota's act.

  1103. · a record · the publication of a scorecard event

    Before
    published
    After
    draft
    Why
    A line an article on Louisiana's politics wrote about Texas: Governor Abbott's moratorium is on Texas's row. It is not Louisiana's act.

  1104. · a record · the publication of a scorecard event

    Before
    published
    After
    draft
    Why
    A line an article on Louisiana's politics wrote about Pennsylvania: Governor Shapiro's executive order is on Pennsylvania's row. It is not Louisiana's act.

  1105. · a record · the publication of a scorecard event

    Before
    published
    After
    draft
    Why
    A line an article on Louisiana's politics wrote about New York: Governor Hochul's moratorium is on New York's row. It is not Louisiana's act.

  1106. · the last verified date of 12 records and scorecard rows

    Before
    The day of a planned hearing or vote, printed as the day last verified: Updated November 17, 2026 on the Pennsylvania page.
    After
    The day of the newest event that happened: September 23, 2026 on the Pennsylvania page.
    Why
    12 records and scorecard rows had taken the day of a planned hearing or vote, a day that had not come or had not yet been reported as held, as the day they were last verified, so their pages printed it as the day the page was updated. Each now carries the newest event on it that happened. No event, date or word of any entry changed.

  1107. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    The row is The Lever's claim about Ken Paxton (his holdings, a 2013 vote, his office's brief), not words he said; a statement on the record is the speaker's own words (DECISIONS 27). Unpublished by the record's rules on 2026-10-13; the article stays cited where it is a source.

  1108. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    The row is The Lever's claim about Ken Paxton (his holdings, a 2013 vote, his office's brief), not words he said; a statement on the record is the speaker's own words (DECISIONS 27). Unpublished by the record's rules on 2026-10-13; the article stays cited where it is a source.

  1109. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    The row is The Lever's claim about Ken Paxton (his holdings, a 2013 vote, his office's brief), not words he said; a statement on the record is the speaker's own words (DECISIONS 27). Unpublished by the record's rules on 2026-10-13; the article stays cited where it is a source.

  1110. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    The row is The Lever's claim about Ken Paxton (his holdings, a 2013 vote, his office's brief), not words he said; a statement on the record is the speaker's own words (DECISIONS 27). Unpublished by the record's rules on 2026-10-13; the article stays cited where it is a source.

  1111. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    The row is The Lever's claim about Ken Paxton (his holdings, a 2013 vote, his office's brief), not words he said; a statement on the record is the speaker's own words (DECISIONS 27). Unpublished by the record's rules on 2026-10-13; the article stays cited where it is a source.

  1112. · Texas · the kind of a scorecard event

    Before
    other
    After
    acquisition
    Why
    The event reports a purchase or a sale of land, a change of hands; its kind was other and is acquisition (the record's rules, on the editor's word).

  1113. · Taylor · the kind of a scorecard event

    Before
    other
    After
    acquisition
    Why
    The event reports a purchase or a sale of land, a change of hands; its kind was other and is acquisition (the record's rules, on the editor's word).

  1114. · SkyBox Data Center at Cox Ranch · the kind of a timeline entry

    Before
    other
    After
    acquisition
    Why
    The entry reports a purchase of land, a building or a company, a change of hands and not a stage; its kind was other and is acquisition (the record's rules, on the editor's word).

  1115. · Amazon Walla Walla County Data Center · the kind of a timeline entry

    Before
    other
    After
    acquisition
    Why
    The entry reports a purchase of land, a building or a company, a change of hands and not a stage; its kind was other and is acquisition (the record's rules, on the editor's word).

  1116. · Switch Las Vegas campus · the kind of a timeline entry

    Before
    other
    After
    acquisition
    Why
    The entry reports a purchase of land, a building or a company, a change of hands and not a stage; its kind was other and is acquisition (the record's rules, on the editor's word).

  1117. · Boston Neighborhood Data Center · the kind of a timeline entry

    Before
    other
    After
    acquisition
    Why
    The entry reports a purchase of land, a building or a company, a change of hands and not a stage; its kind was other and is acquisition (the record's rules, on the editor's word).

  1118. · Data Center near Hallam (unnamed developers) · the kind of a timeline entry

    Before
    other
    After
    acquisition
    Why
    The entry reports a purchase of land, a building or a company, a change of hands and not a stage; its kind was other and is acquisition (the record's rules, on the editor's word).

  1119. · microsoft-wellington-data-center-prince-william-va · the kind of a timeline entry

    Before
    other
    After
    acquisition
    Why
    The entry reports a purchase of land, a building or a company, a change of hands and not a stage; its kind was other and is acquisition (the record's rules, on the editor's word).

  1120. · microsoft-wellington-data-center-prince-william-va · the kind of a timeline entry

    Before
    other
    After
    acquisition
    Why
    The entry reports a purchase of land, a building or a company, a change of hands and not a stage; its kind was other and is acquisition (the record's rules, on the editor's word).

  1121. · OpenAI Effingham County Data Center · the kind of a timeline entry

    Before
    other
    After
    acquisition
    Why
    The entry reports a purchase of land, a building or a company, a change of hands and not a stage; its kind was other and is acquisition (the record's rules, on the editor's word).

  1122. · NTT Mesa data center campus · the kind of a timeline entry

    Before
    other
    After
    acquisition
    Why
    The entry reports a purchase of land, a building or a company, a change of hands and not a stage; its kind was other and is acquisition (the record's rules, on the editor's word).

  1123. · EdgeCore Mesa North Campus · the kind of a timeline entry

    Before
    other
    After
    acquisition
    Why
    The entry reports a purchase of land, a building or a company, a change of hands and not a stage; its kind was other and is acquisition (the record's rules, on the editor's word).

  1124. · NTT Mesa data center campus · the kind of a timeline entry

    Before
    other
    After
    acquisition
    Why
    The entry reports a purchase of land, a building or a company, a change of hands and not a stage; its kind was other and is acquisition (the record's rules, on the editor's word).

  1125. · NTT Mesa data center campus · the kind of a timeline entry

    Before
    other
    After
    acquisition
    Why
    The entry reports a purchase of land, a building or a company, a change of hands and not a stage; its kind was other and is acquisition (the record's rules, on the editor's word).

  1126. · Yondr Group Manassas data center campus · the kind of a timeline entry

    Before
    other
    After
    acquisition
    Why
    The entry reports a purchase of land, a building or a company, a change of hands and not a stage; its kind was other and is acquisition (the record's rules, on the editor's word).

  1127. · Clearfield City · the rating's end date of a scorecard row

    Before
    none
    After
    2027-03-10
    Why
    The editor's word of 2026-10-10 (batch rubric-1013): restrictive under the rubric of 2026-10-09, resting on the act of 2026-09-11.

  1128. · Clearfield City · the act the rating rests on of a scorecard row

    Before
    none
    After
    Clearfield City Council approved a 180 day moratorium on data center development (2026-09-11)
    Why
    The editor's word of 2026-10-10 (batch rubric-1013): restrictive under the rubric of 2026-10-09, resting on the act of 2026-09-11.

  1129. · Box Elder County · the rating's end date of a scorecard row

    Before
    none
    After
    2026-12-07
    Why
    The editor's word of 2026-10-10 (batch rubric-1013): restrictive under the rubric of 2026-10-09, resting on the act of 2026-06-10.

  1130. · Montgomery County · the rating's end date of a scorecard row

    Before
    none
    After
    2028-03-23
    Why
    The editor's word of 2026-10-10 (batch rubric-1013): closed under the rubric of 2026-10-09, resting on the act of 2026-09-23.

  1131. · Montgomery County · the act the rating rests on of a scorecard row

    Before
    none
    After
    Montgomery County, Maryland approved 18 month pause on data center reviews in July 2026 (2026-09-23)
    Why
    The editor's word of 2026-10-10 (batch rubric-1013): closed under the rubric of 2026-10-09, resting on the act of 2026-09-23.

  1132. · Lima · the rating's end date of a scorecard row

    Before
    none
    After
    2028-03-15
    Why
    The editor's word of 2026-10-10 (batch rubric-1013): closed under the rubric of 2026-10-09, resting on the act of 2026-09-15.

  1133. · Lima · the act the rating rests on of a scorecard row

    Before
    none
    After
    City of Lima approved an 18 month data center moratorium (2026-09-15)
    Why
    The editor's word of 2026-10-10 (batch rubric-1013): closed under the rubric of 2026-10-09, resting on the act of 2026-09-15.

  1134. · Lima · the rating of a scorecard row

    Before
    no published rating
    After
    closed
    Why
    The editor's word of 2026-10-10 (batch rubric-1013): closed under the rubric of 2026-10-09, resting on the act of 2026-09-15.

  1135. · Sierra County · the rating's end date of a scorecard row

    Before
    none
    After
    2028-03-15
    Why
    The editor's word of 2026-10-10 (batch rubric-1013): closed under the rubric of 2026-10-09, resting on the act of 2026-09-15.

  1136. · Sierra County · the act the rating rests on of a scorecard row

    Before
    none
    After
    Sierra County adopted an 18 month moratorium on data centers (2026-09-15)
    Why
    The editor's word of 2026-10-10 (batch rubric-1013): closed under the rubric of 2026-10-09, resting on the act of 2026-09-15.

  1137. · Sierra County · the rating of a scorecard row

    Before
    no published rating
    After
    closed
    Why
    The editor's word of 2026-10-10 (batch rubric-1013): closed under the rubric of 2026-10-09, resting on the act of 2026-09-15.

  1138. · Santa Fe County · the rating's end date of a scorecard row

    Before
    none
    After
    2028-03-15
    Why
    The editor's word of 2026-10-10 (batch rubric-1013): closed under the rubric of 2026-10-09, resting on the act of 2026-09-15.

  1139. · Santa Fe County · the act the rating rests on of a scorecard row

    Before
    none
    After
    Santa Fe County unanimously approved an 18 month moratorium on data centers without a project pending (2026-09-15)
    Why
    The editor's word of 2026-10-10 (batch rubric-1013): closed under the rubric of 2026-10-09, resting on the act of 2026-09-15.

  1140. · Santa Fe County · the rating of a scorecard row

    Before
    no published rating
    After
    closed
    Why
    The editor's word of 2026-10-10 (batch rubric-1013): closed under the rubric of 2026-10-09, resting on the act of 2026-09-15.

  1141. · Southport · the rating's end date of a scorecard row

    Before
    none
    After
    2027-12-11
    Why
    The editor's word of 2026-10-10 (batch rubric-1013): closed under the rubric of 2026-10-09, resting on the act of 2026-09-11.

  1142. · Southport · the act the rating rests on of a scorecard row

    Before
    none
    After
    Southport Board of Aldermen unanimously approved a 15 month moratorium on new data center approvals (2026-09-11)
    Why
    The editor's word of 2026-10-10 (batch rubric-1013): closed under the rubric of 2026-10-09, resting on the act of 2026-09-11.

  1143. · Southport · the rating of a scorecard row

    Before
    no published rating
    After
    closed
    Why
    The editor's word of 2026-10-10 (batch rubric-1013): closed under the rubric of 2026-10-09, resting on the act of 2026-09-11.

  1144. · Prince George's County · the rating's end date of a scorecard row

    Before
    none
    After
    2028-09-23
    Why
    The editor's word of 2026-10-10 (batch rubric-1013): closed under the rubric of 2026-10-09, resting on the act of 2026-09-23.

  1145. · Prince George's County · the act the rating rests on of a scorecard row

    Before
    none
    After
    Prince George's County established a two year moratorium on data center proposals and development in June to review environmental impacts, energy demands, and infrastructure capacity. (2026-09-23)
    Why
    The editor's word of 2026-10-10 (batch rubric-1013): closed under the rubric of 2026-10-09, resting on the act of 2026-09-23.

  1146. · Prince George's County · the rating of a scorecard row

    Before
    no published rating
    After
    closed
    Why
    The editor's word of 2026-10-10 (batch rubric-1013): closed under the rubric of 2026-10-09, resting on the act of 2026-09-23.

  1147. · Anne Arundel County · the rating's end date of a scorecard row

    Before
    none
    After
    2027-12-22
    Why
    The editor's word of 2026-10-10 (batch rubric-1013): closed under the rubric of 2026-10-09, resting on the act of 2026-09-22.

  1148. · Anne Arundel County · the act the rating rests on of a scorecard row

    Before
    none
    After
    Anne Arundel County Council unanimously passed a 15 month data center moratorium on Monday, September 22, 2026. (2026-09-22)
    Why
    The editor's word of 2026-10-10 (batch rubric-1013): closed under the rubric of 2026-10-09, resting on the act of 2026-09-22.

  1149. · Anne Arundel County · the rating of a scorecard row

    Before
    no published rating
    After
    closed
    Why
    The editor's word of 2026-10-10 (batch rubric-1013): closed under the rubric of 2026-10-09, resting on the act of 2026-09-22.

  1150. · Rowan County · the rating's end date of a scorecard row

    Before
    none
    After
    2028-09-01
    Why
    The editor's word of 2026-10-10 (batch rubric-1013): closed under the rubric of 2026-10-09, resting on the act of 2026-09-01.

  1151. · Rowan County · the act the rating rests on of a scorecard row

    Before
    none
    After
    Rowan County Fiscal Court approved a two year moratorium on large scale data centers (2026-09-01)
    Why
    The editor's word of 2026-10-10 (batch rubric-1013): closed under the rubric of 2026-10-09, resting on the act of 2026-09-01.

  1152. · Rowan County · the rating of a scorecard row

    Before
    no published rating
    After
    closed
    Why
    The editor's word of 2026-10-10 (batch rubric-1013): closed under the rubric of 2026-10-09, resting on the act of 2026-09-01.

  1153. · Trumbull · the rating's end date of a scorecard row

    Before
    none
    After
    2028-09-11
    Why
    The editor's word of 2026-10-10 (batch rubric-1013): closed under the rubric of 2026-10-09, resting on the act of 2026-09-11.

  1154. · Trumbull · the act the rating rests on of a scorecard row

    Before
    none
    After
    Trumbull passes a 2 year moratorium on new data centers (2026-09-11)
    Why
    The editor's word of 2026-10-10 (batch rubric-1013): closed under the rubric of 2026-10-09, resting on the act of 2026-09-11.

  1155. · Trumbull · the rating of a scorecard row

    Before
    restrictive
    After
    closed
    Why
    The editor's word of 2026-10-10 (batch rubric-1013): closed under the rubric of 2026-10-09, resting on the act of 2026-09-11.

  1156. · Madison County · the rating's end date of a scorecard row

    Before
    none
    After
    2029-08-31
    Why
    The editor's word of 2026-10-10 (batch rubric-1013): closed under the rubric of 2026-10-09, resting on the act of 2026-08-24.

  1157. · Madison County · the act the rating rests on of a scorecard row

    Before
    none
    After
    Madison County Quorum Court unanimously voted to approve a data center moratorium running through August 31, 2029 (2026-08-24)
    Why
    The editor's word of 2026-10-10 (batch rubric-1013): closed under the rubric of 2026-10-09, resting on the act of 2026-08-24.

  1158. · Madison County · the rating of a scorecard row

    Before
    restrictive
    After
    closed
    Why
    The editor's word of 2026-10-10 (batch rubric-1013): closed under the rubric of 2026-10-09, resting on the act of 2026-08-24.

  1159. · Smithfield · the act the rating rests on of a scorecard row

    Before
    none
    After
    Smithfield passed a data center ban ordinance on May 5 (2026-05-05)
    Why
    The editor's word of 2026-10-10 (batch rubric-1013): closed under the rubric of 2026-10-09, resting on the act of 2026-05-05.

  1160. · Holyoke · the act the rating rests on of a scorecard row

    Before
    none
    After
    Holyoke approved a ban on data centers earlier this year (2026-09-08)
    Why
    The editor's word of 2026-10-10 (batch rubric-1013): closed under the rubric of 2026-10-09, resting on the act of 2026-09-08.

  1161. · San Marcos · the act the rating rests on of a scorecard row

    Before
    none
    After
    In June 2026, San Marcos City Council voted 4-3 to change zoning regulations to make data centers ineligible for development within city limits (2026-08-19)
    Why
    The editor's word of 2026-10-10 (batch rubric-1013): closed under the rubric of 2026-10-09, resting on the act of 2026-08-19.

  1162. · San Marcos · the rating of a scorecard row

    Before
    restrictive
    After
    closed
    Why
    The editor's word of 2026-10-10 (batch rubric-1013): closed under the rubric of 2026-10-09, resting on the act of 2026-08-19.

  1163. · Dryden · the act the rating rests on of a scorecard row

    Before
    none
    After
    The town of Dryden in Tompkins County adopted zoning changes banning data centers and cryptocurrency mines over concerns about their energy use (2026-09-17)
    Why
    The editor's word of 2026-10-10 (batch rubric-1013): closed under the rubric of 2026-10-09, resting on the act of 2026-09-17.

  1164. · Dryden · the rating of a scorecard row

    Before
    no published rating
    After
    closed
    Why
    The editor's word of 2026-10-10 (batch rubric-1013): closed under the rubric of 2026-10-09, resting on the act of 2026-09-17.

  1165. · Nye County · the act the rating rests on of a scorecard row

    Before
    none
    After
    Nye County has banned the development of data centers (2026-09-18)
    Why
    The editor's word of 2026-10-10 (batch rubric-1013): closed under the rubric of 2026-10-09, resting on the act of 2026-09-18.

  1166. · Nye County · the rating of a scorecard row

    Before
    no published rating
    After
    closed
    Why
    The editor's word of 2026-10-10 (batch rubric-1013): closed under the rubric of 2026-10-09, resting on the act of 2026-09-18.

  1167. · Harford County · the act the rating rests on of a scorecard row

    Before
    none
    After
    Harford County, Maryland banned new data centers outright in June 2026 (2026-09-23)
    Why
    The editor's word of 2026-10-10 (batch rubric-1013): closed under the rubric of 2026-10-09, resting on the act of 2026-09-23.

  1168. · Harford County · the rating of a scorecard row

    Before
    no published rating
    After
    closed
    Why
    The editor's word of 2026-10-10 (batch rubric-1013): closed under the rubric of 2026-10-09, resting on the act of 2026-09-23.

  1169. · Mansfield · the act the rating rests on of a scorecard row

    Before
    none
    After
    Mansfield voters passed near total ban on data centers in May 2026. (2026-09-08)
    Why
    The editor's word of 2026-10-10 (batch rubric-1013): closed under the rubric of 2026-10-09, resting on the act of 2026-09-08.

  1170. · Mansfield · the rating of a scorecard row

    Before
    no published rating
    After
    closed
    Why
    The editor's word of 2026-10-10 (batch rubric-1013): closed under the rubric of 2026-10-09, resting on the act of 2026-09-08.

  1171. · Monterey Park · the act the rating rests on of a scorecard row

    Before
    none
    After
    Monterey Park voted in June 2026 to permanently ban data centers (2026-09-14)
    Why
    The editor's word of 2026-10-10 (batch rubric-1013): closed under the rubric of 2026-10-09, resting on the act of 2026-09-14.

  1172. · Monterey Park · the rating of a scorecard row

    Before
    no published rating
    After
    closed
    Why
    The editor's word of 2026-10-10 (batch rubric-1013): closed under the rubric of 2026-10-09, resting on the act of 2026-09-14.

  1173. · Coachella · the act the rating rests on of a scorecard row

    Before
    none
    After
    Coachella passed permanent ban on data centers in late August 2026 (2026-09-14)
    Why
    The editor's word of 2026-10-10 (batch rubric-1013): closed under the rubric of 2026-10-09, resting on the act of 2026-09-14.

  1174. · Coachella · the rating of a scorecard row

    Before
    no published rating
    After
    closed
    Why
    The editor's word of 2026-10-10 (batch rubric-1013): closed under the rubric of 2026-10-09, resting on the act of 2026-09-14.

  1175. · Box Elder County · the rating of a scorecard event

    Before
    restrictive
    After
    case by case
    Why
    An approval of one project is case by case under the rubric of 2026-10-09 as clarified on 2026-10-10 (rule 9); the label had read restrictive. The editor's word of 2026-10-10 (batch rubric-1013).

  1176. · Box Elder County · the rating of a scorecard event

    Before
    restrictive
    After
    case by case
    Why
    An approval of one project is case by case under the rubric of 2026-10-09 as clarified on 2026-10-10 (rule 9); the label had read restrictive. The editor's word of 2026-10-10 (batch rubric-1013).

  1177. · Box Elder County · the rating of a scorecard event

    Before
    closed
    After
    restrictive
    Why
    A moratorium with an end date (180 days from June 10, 2026) is restrictive under the rubric of 2026-10-09; the label had read closed. The editor's word of 2026-10-10 (batch rubric-1013).

  1178. · DataBank Eagan Data Center · the summary of a timeline entry

    Before
    DataBank acquired the building housing its MSP2 data center at 3255 Neil Armstrong Boulevard in Eagan, Minnesota, a facility it had leased.
    After
    DataBank acquired the building that houses its MSP2 data center at 3255 Neil Armstrong Boulevard in Eagan, Minnesota, which it had leased. The release describes MSP2 as a carrier hotel serving the Minneapolis market whose clients rely on its services, so the data center was running before the purchase.
    Why
    The entry had read as the day the data center went live, being the record's first entry with the stage operational. The release of October 1, 2026 says the company bought the building that houses its MSP2 data center, which it had leased and whose services clients rely on, so the entry is an acquisition and the running stage rests on the release's words that the facility was in service (the record's rules, on the editor's word).

  1179. · DataBank Eagan Data Center · the kind of a timeline entry

    Before
    other
    After
    acquisition
    Why
    The entry is the purchase of the building that houses a data center already in service; its kind was other and is acquisition, a change of hands and not a stage (the record's rules, on the editor's word).

  1180. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    "Utah voters" is not a speaker; the fact stays on the Daily Record as a news item (The editor's word of 2026-10-10 (batch rubric-1012).)

  1181. · Steve Scalise · the scorecard row of a statement

    Before
    After
    us/united-states
    Why
    Filed on the national row: the statement is about Congress or a federal bill, not the state it was reported in (The editor's word of 2026-10-10 (batch rubric-1012).)

  1182. · Steve Scalise · the state of a statement

    Before
    NH
    After
    US
    Why
    Filed on the national row: the statement is about Congress or a federal bill, not the state it was reported in (The editor's word of 2026-10-10 (batch rubric-1012).)

  1183. · Steve Scalise · the scorecard row of a statement

    Before
    After
    us/united-states
    Why
    Filed on the national row: the statement is about Congress or a federal bill, not the state it was reported in (The editor's word of 2026-10-10 (batch rubric-1012).)

  1184. · Steve Scalise · the state of a statement

    Before
    NH
    After
    US
    Why
    Filed on the national row: the statement is about Congress or a federal bill, not the state it was reported in (The editor's word of 2026-10-10 (batch rubric-1012).)

  1185. · Mike Johnson · the scorecard row of a statement

    Before
    After
    us/united-states
    Why
    Filed on the national row: the statement is about Congress or a federal bill, not the state it was reported in (The editor's word of 2026-10-10 (batch rubric-1012).)

  1186. · Mike Johnson · the state of a statement

    Before
    PA
    After
    US
    Why
    Filed on the national row: the statement is about Congress or a federal bill, not the state it was reported in (The editor's word of 2026-10-10 (batch rubric-1012).)

  1187. · Hakeem Jeffries · the scorecard row of a statement

    Before
    After
    us/united-states
    Why
    Filed on the national row: the statement is about Congress or a federal bill, not the state it was reported in (The editor's word of 2026-10-10 (batch rubric-1012).)

  1188. · Hakeem Jeffries · the state of a statement

    Before
    VA
    After
    US
    Why
    Filed on the national row: the statement is about Congress or a federal bill, not the state it was reported in (The editor's word of 2026-10-10 (batch rubric-1012).)

  1189. · Stratos Project · the citation of a statement

    Before
    After
    https://grist.org/accountability/data-center-natural-gas-utah-cox-box-elder-stratos/
    Why
    Cites the report of the same claim by the same speaker (said again on 2026-05-28; the editor's edit, 2026-10-10).

  1190. · Stratos Project · the wording of a statement

    Before
    After
    Governor Cox acknowledged the process for Stratos Project approval was not good
    Why
    Split into its two claims, the editor's edit: the process sentence folds under the August 20 line and the future decisions sentence under the May 21 line (The editor's word of 2026-10-10 (batch rubric-1012).) This row is the second claim of statement 9a8e5381-f700-404a-86b7-06a1011d4125.

  1191. · Stratos Project · the wording of a statement

    Before
    Governor Cox acknowledged the process for Stratos Project approval was not good and said future decisions should involve his office and elected representatives
    After
    Governor Cox said future decisions should involve his office and elected representatives
    Why
    Split into its two claims, the editor's edit: the process sentence folds under the August 20 line and the future decisions sentence under the May 21 line (The editor's word of 2026-10-10 (batch rubric-1012).)

  1192. · Ken Paxton · the publication of a statement

    Before
    true
    After
    false
    Why
    Unfolded: two announcements, not one said again (The editor's word of 2026-10-10 (batch rubric-1012).)

  1193. · Ken Paxton · the folded into of a statement

    Before
    51eabdf7-a7f3-4406-9a20-f2d8d1f24de7
    After
    Why
    Unfolded: two announcements, not one said again (The editor's word of 2026-10-10 (batch rubric-1012).)

  1194. · Google Mesa data center · the publication of a statement

    Before
    true
    After
    false
    Why
    Unfolded: two announcements, not one said again (The editor's word of 2026-10-10 (batch rubric-1012).)

  1195. · Google Mesa data center · the folded into of a statement

    Before
    03eb0b2a-adc9-46d5-8fe1-346ed7ffe7ae
    After
    Why
    Unfolded: two announcements, not one said again (The editor's word of 2026-10-10 (batch rubric-1012).)

  1196. · Energy experts cited by The Salt Lake Tribune and Grist · the wording of a statement

    Before
    Energy experts have calculated the Stratos project would raise Utah's emissions by as much as 64 percent, producing more carbon pollution than the state's entire transportation sector, Cache Valley Daily reported on May 20, 2026; the outlet did not name the experts.
    After
    Energy experts have calculated the Stratos project would raise Utah's emissions by as much as 64 percent, producing more carbon pollution than the state's entire transportation sector, The Salt Lake Tribune and Grist reported on May 18, 2026, in a story published through their partnership; the outlets did not name the experts.
    Why
    Attributed to the original publication, The Salt Lake Tribune and Grist's story of May 18, 2026, published through their partnership (the editor's word, 2026-10-10); Cache Valley Daily's copy of May 20, 2026, where the record first read the claim, stays as a citation. The experts remain unnamed.

  1197. · Energy experts cited by The Salt Lake Tribune and Grist · the source date of a statement

    Before
    2026-05-20
    After
    2026-05-18
    Why
    Attributed to the original publication, The Salt Lake Tribune and Grist's story of May 18, 2026, published through their partnership (the editor's word, 2026-10-10); Cache Valley Daily's copy of May 20, 2026, where the record first read the claim, stays as a citation. The experts remain unnamed.

  1198. · Energy experts cited by The Salt Lake Tribune and Grist · the date of a statement

    Before
    2026-05-20
    After
    2026-05-18
    Why
    Attributed to the original publication, The Salt Lake Tribune and Grist's story of May 18, 2026, published through their partnership (the editor's word, 2026-10-10); Cache Valley Daily's copy of May 20, 2026, where the record first read the claim, stays as a citation. The experts remain unnamed.

  1199. · Energy experts cited by The Salt Lake Tribune and Grist · the source url of a statement

    Before
    https://www.cachevalleydaily.com/news/utahns-will-have-more-chances-to-weigh-in-on-kevin-o-leary-s-data-center/article_7a89907b-679e-478d-a691-5de64bbb5c7c.html
    After
    https://grist.org/business/utah-data-center-salt-lake-hyperscale-box-elder/
    Why
    Attributed to the original publication, The Salt Lake Tribune and Grist's story of May 18, 2026, published through their partnership (the editor's word, 2026-10-10); Cache Valley Daily's copy of May 20, 2026, where the record first read the claim, stays as a citation. The experts remain unnamed.

  1200. · Energy experts cited by The Salt Lake Tribune and Grist · the source outlet of a statement

    Before
    Cache Valley Daily
    After
    The Salt Lake Tribune and Grist
    Why
    Attributed to the original publication, The Salt Lake Tribune and Grist's story of May 18, 2026, published through their partnership (the editor's word, 2026-10-10); Cache Valley Daily's copy of May 20, 2026, where the record first read the claim, stays as a citation. The experts remain unnamed.

  1201. · Energy experts cited by The Salt Lake Tribune and Grist · the speaker's role of a statement

    Before
    not named by the outlet
    After
    not named by the outlets
    Why
    Attributed to the original publication, The Salt Lake Tribune and Grist's story of May 18, 2026, published through their partnership (the editor's word, 2026-10-10); Cache Valley Daily's copy of May 20, 2026, where the record first read the claim, stays as a citation. The experts remain unnamed.

  1202. · Energy experts cited by The Salt Lake Tribune and Grist · the speaker of a statement

    Before
    Energy experts cited by Cache Valley Daily
    After
    Energy experts cited by The Salt Lake Tribune and Grist
    Why
    Attributed to the original publication, The Salt Lake Tribune and Grist's story of May 18, 2026, published through their partnership (the editor's word, 2026-10-10); Cache Valley Daily's copy of May 20, 2026, where the record first read the claim, stays as a citation. The experts remain unnamed.

  1203. · Volition Industries Spanish Fork · the changed from of a statement

    Before
    After
    ba02ce52-9645-460a-8996-dfa0e9646e46
    Why
    The same speaker's position on this claim changed from an earlier statement (the record's rules, 2026-10-10): both stand with their dates.

  1204. · Volition Industries Spanish Fork · the changed from of a statement

    Before
    After
    ba02ce52-9645-460a-8996-dfa0e9646e46
    Why
    The same speaker's position on this claim changed from an earlier statement (the record's rules, 2026-10-10): both stand with their dates.

  1205. · William Lawrence · the citation of a statement

    Before
    After
    https://lansingcitypulse.com/will-lawrence-rolls-out-plan-for-regulating-big-tech-data-centers-in-michigan-and-beyond/
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-23; the record's rules, 2026-10-10).

  1206. · a statement · the folded into of a statement

    Before
    After
    d0bb785e-7b16-44c0-9e18-e00d025cc2d4
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1207. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1208. · Will Lawrence · the citation of a statement

    Before
    After
    https://www.cbsnews.com/detroit/news/ai-fears-fueling-progressive-democrats-campaign-michigan-battleground-district/
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-19; the record's rules, 2026-10-10).

  1209. · a statement · the folded into of a statement

    Before
    After
    e90534ed-6ac4-4a4a-9c0a-feddb47f954e
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1210. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1211. · Will Lawrence · the citation of a statement

    Before
    After
    https://gandernewsroom.com/news/elections/lawrence-ai-data-center-plan/
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-17; the record's rules, 2026-10-10).

  1212. · a statement · the folded into of a statement

    Before
    After
    e90534ed-6ac4-4a4a-9c0a-feddb47f954e
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1213. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1214. · Wes Moore · the citation of a statement

    Before
    After
    https://www.nbcwashington.com/news/local/maryland-gov-moore-unveils-ai-framework-limits-tax-exemptions-for-data-centers/4158116/
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-23; the record's rules, 2026-10-10).

  1215. · a statement · the folded into of a statement

    Before
    After
    5326cbea-412e-456f-bc71-9c1ec77d5493
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1216. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1217. · Wes Moore · the citation of a statement

    Before
    After
    https://www.wmdt.com/2026/09/gov-moore-signs-exec-order-setting-new-guardrails-for-data-center-development/
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-23; the record's rules, 2026-10-10).

  1218. · a statement · the folded into of a statement

    Before
    After
    5326cbea-412e-456f-bc71-9c1ec77d5493
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1219. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1220. · Vivek Ramaswamy · the citation of a statement

    Before
    After
    https://tiffinohio.net/posts/ramaswamy-follows-acton-gas-tax-data-center-proposals/
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-24; the record's rules, 2026-10-10).

  1221. · a statement · the folded into of a statement

    Before
    After
    e0331f29-5338-42d2-9d5a-ebbde7e41229
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1222. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1223. · Vern Thompson · the citation of a statement

    Before
    After
    https://www.am1100theflag.com/news/local-news/vern-thompson-to-host-public-forum-on-north-dakota-data-center-developments-in-mapleton/
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-09; the record's rules, 2026-10-10).

  1224. · a statement · the folded into of a statement

    Before
    After
    895fa323-63e2-4b6e-abd4-d97b6ec24d6e
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1225. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1226. · Vayujeet Gokhale · the citation of a statement

    Before
    After
    https://www.stltoday.com/news/local/government-politics/article_a7671f48-03f3-4f5d-ac0e-9d5b4d61240e.html
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-22; the record's rules, 2026-10-10).

  1227. · a statement · the folded into of a statement

    Before
    After
    1f17fa6e-726e-4a56-bc6b-d54704f82011
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1228. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1229. · Vayujeet Gokhale · the citation of a statement

    Before
    After
    https://lailluminator.com/2026/09/12/data-center-light/
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-12; the record's rules, 2026-10-10).

  1230. · a statement · the folded into of a statement

    Before
    After
    1f17fa6e-726e-4a56-bc6b-d54704f82011
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1231. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1232. · Val Hoyle · the citation of a statement

    Before
    After
    https://www.klcc.org/politics-government/2026-09-21/ai-data-centers-and-tech-money-take-center-stage-in-rematch-for-4th-congressional-district
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-21; the record's rules, 2026-10-10).

  1233. · a statement · the folded into of a statement

    Before
    After
    0eb12ba4-9bac-4a1a-a787-a7f811c7ab6c
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1234. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1235. · Tommy Tuberville · the citation of a statement

    Before
    After
    https://yellowhammernews.com/tuberville-backed-ratepayer-protections-advance-in-u-s-house-to-make-sure-alabamians-arent-left-footing-the-bill-for-data-centers/
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-17; the record's rules, 2026-10-10).

  1236. · a statement · the folded into of a statement

    Before
    After
    0e2f05f4-ec4f-4dc7-aae8-4af831d6d5b2
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1237. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1238. · Tom Tiffany · the citation of a statement

    Before
    After
    https://wcti12.com/news/nation-world/democrats-tied-to-2028-pivot-toward-data-center-regulation-as-trump-pushes-for-progress-arizona-mark-kelly-pennsylvania-josh-shapiro-maryland-wes-moore-political-analyst-jone-dedie-artificial-intelligence
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-21; the record's rules, 2026-10-10).

  1239. · a statement · the folded into of a statement

    Before
    After
    4285008c-3146-43a0-8e34-a00883195f93
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1240. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1241. · Tina Kotek · the citation of a statement

    Before
    After
    https://www.wweek.com/news/state/2026/09/08/kotek-pauses-all-consideration-of-state-land-for-data-centers/
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-09; the record's rules, 2026-10-10).

  1242. · a statement · the folded into of a statement

    Before
    After
    8017e432-002b-48ee-af62-38cd3b395ae7
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1243. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1244. · Tina Kotek · the citation of a statement

    Before
    After
    https://www.opb.org/article/2026/09/08/oregon-data-centers-tina-kotek-politics-climate/
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-08; the record's rules, 2026-10-10).

  1245. · a statement · the folded into of a statement

    Before
    After
    0b7832e8-4e59-4f54-8510-b6db83b2c13e
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1246. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1247. · Terry Kilgore · the citation of a statement

    Before
    After
    https://www.foxnews.com/politics/spanbergers-data-center-plan-collision-course-partys-green-energy-push-critics-warn
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-22; the record's rules, 2026-10-10).

  1248. · a statement · the folded into of a statement

    Before
    After
    19e35f7b-65d0-4311-bf4f-a3f9b1d35b70
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1249. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1250. · Vantage Port Washington Data Center · the citation of a statement

    Before
    After
    https://urbanmilwaukee.com/2026/03/15/neighbors-push-back-on-24-hour-data-center-work-in-port-washington/
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-03-15; the record's rules, 2026-10-10).

  1251. · Vantage Port Washington Data Center · the folded into of a statement

    Before
    After
    436f01f9-1afe-4c1c-ab13-f7630921e0a1
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1252. · Vantage Port Washington Data Center · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1253. · Suhas Subramanyam · the citation of a statement

    Before
    After
    https://www.insidenova.com/news/prince_william/rep-subramanyam-announces-national-data-center-plan-in-ashburn/article_e3c08b55-a7b5-4e11-bc40-945fe0a5326a.html
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-10; the record's rules, 2026-10-10).

  1254. · a statement · the folded into of a statement

    Before
    After
    68384851-4340-44a8-9379-43a4c86a8408
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1255. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1256. · Stratos Project · the citation of a statement

    Before
    After
    https://www.standard.net/news/2026/jun/04/oleary-concedes-to-president-adams-demands-on-data-center/
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-06-04; the record's rules, 2026-10-10).

  1257. · Stratos Project · the folded into of a statement

    Before
    After
    9f12ff9c-3013-45d0-bba8-f143edd85169
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1258. · Stratos Project · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1259. · Stratos Project · the citation of a statement

    Before
    After
    https://www.standard.net/news/2026/jun/04/oleary-concedes-to-president-adams-demands-on-data-center/
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-06-04; the record's rules, 2026-10-10).

  1260. · Stratos Project · the folded into of a statement

    Before
    After
    4263698f-973d-4e60-bc79-092089e7f018
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1261. · Stratos Project · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1262. · Steve DeFrank · the citation of a statement

    Before
    After
    https://www.thecentersquare.com/issues/economy/article_71fd6dae-a027-4bed-8ebc-7ca560a18e4a.amp.html
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-14; the record's rules, 2026-10-10).

  1263. · a statement · the folded into of a statement

    Before
    After
    ddebadb2-e1db-4ad6-819b-d3ae82e4c108
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1264. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1265. · Stacy Garrity · the citation of a statement

    Before
    After
    https://www.foxnews.com/politics/maga-begins-crack-2026-gop-roster-backs-away-from-trumps-tech-vision
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-03; the record's rules, 2026-10-10).

  1266. · a statement · the folded into of a statement

    Before
    After
    72556211-26f8-4cbd-9f7c-a3b6c4023f89
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1267. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1268. · Stratos Project · the citation of a statement

    Before
    After
    https://www.yahoo.com/news/politics/articles/utah-governor-calls-box-elder-020000590.html
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-08-29; the record's rules, 2026-10-10).

  1269. · Stratos Project · the folded into of a statement

    Before
    After
    8b7ad3f9-f5d7-4d04-95da-dad9bafb7684
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1270. · Stratos Project · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1271. · Stratos Project · the citation of a statement

    Before
    After
    https://www.yahoo.com/news/politics/articles/utah-governor-calls-box-elder-020000590.html
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-08-29; the record's rules, 2026-10-10).

  1272. · Stratos Project · the folded into of a statement

    Before
    After
    d4bd5a96-bd4d-4d6d-ae26-c87e3fbfe4a1
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1273. · Stratos Project · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1274. · Stratos Project · the citation of a statement

    Before
    After
    https://www.yahoo.com/news/politics/articles/utah-governor-calls-box-elder-020000590.html
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-08-28; the record's rules, 2026-10-10).

  1275. · Stratos Project · the folded into of a statement

    Before
    After
    725d3cd0-5a2d-4406-a61a-c36d91a8a66c
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1276. · Stratos Project · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1277. · Stratos Project · the citation of a statement

    Before
    After
    https://www.sltrib.com/news/politics/2026/08/20/utah-gov-cox-calls-stratos-data/
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-08-20; the record's rules, 2026-10-10).

  1278. · Stratos Project · the folded into of a statement

    Before
    After
    725d3cd0-5a2d-4406-a61a-c36d91a8a66c
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1279. · Stratos Project · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1280. · Stratos Project · the citation of a statement

    Before
    After
    https://www.yahoo.com/news/politics/articles/utah-governor-calls-box-elder-020000590.html
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-08-29; the record's rules, 2026-10-10).

  1281. · Stratos Project · the folded into of a statement

    Before
    After
    40ba2c40-3842-436d-9ddb-18959bd0612c
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1282. · Stratos Project · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1283. · Stratos Project · the citation of a statement

    Before
    After
    https://www.ksl.com/article/51614434/cox-calls-for-major-reform-to-mida-after-data-center-pushback
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-08-21; the record's rules, 2026-10-10).

  1284. · Stratos Project · the folded into of a statement

    Before
    After
    40ba2c40-3842-436d-9ddb-18959bd0612c
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1285. · Stratos Project · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1286. · Stratos Project · the citation of a statement

    Before
    After
    https://www.fox13now.com/news/politics/cox-pushes-mida-reforms-after-data-center-blowup
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-08-20; the record's rules, 2026-10-10).

  1287. · Stratos Project · the folded into of a statement

    Before
    After
    40ba2c40-3842-436d-9ddb-18959bd0612c
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1288. · Stratos Project · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1289. · Stratos Project · the citation of a statement

    Before
    After
    https://grist.org/accountability/data-center-natural-gas-utah-cox-box-elder-stratos/
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-05-28; the record's rules, 2026-10-10).

  1290. · Stratos Project · the folded into of a statement

    Before
    After
    b228e54f-e3ab-4223-ba4e-ad88f7e6839e
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1291. · Stratos Project · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1292. · Stratos Project · the citation of a statement

    Before
    After
    https://www.ksl.com/article/news/utah/science-and-tech/utah-data-centers-promise-jobs-and-revenue-but-opponents-say-benefits-disappear/51619417
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-06; the record's rules, 2026-10-10).

  1293. · Stratos Project · the folded into of a statement

    Before
    After
    d371cc0d-0ad6-4d61-80b0-a5ca6cf83508
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1294. · Stratos Project · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1295. · Stratos Project · the citation of a statement

    Before
    After
    https://www.ksl.com/article/news/utah/science-and-tech/utah-data-centers-promise-jobs-and-revenue-but-opponents-say-benefits-disappear/51619417
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-02; the record's rules, 2026-10-10).

  1296. · Stratos Project · the folded into of a statement

    Before
    After
    d371cc0d-0ad6-4d61-80b0-a5ca6cf83508
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1297. · Stratos Project · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1298. · Stratos Project · the citation of a statement

    Before
    After
    https://www.deseret.com/business/2026/09/02/utah-data-centers-face-scrutiny-from-state-officials-rural-communities/
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-02; the record's rules, 2026-10-10).

  1299. · Stratos Project · the folded into of a statement

    Before
    After
    69e166bb-608b-40bb-9e7e-681d71271c9f
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1300. · Stratos Project · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1301. · Sam Altman · the citation of a statement

    Before
    After
    https://www.wral.com/news/state/data-center-almond-farm-water-use-fact-check-chatgpt-september-14/
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-14; the record's rules, 2026-10-10).

  1302. · a statement · the folded into of a statement

    Before
    After
    d4bfa3f3-90b1-4575-a1b3-431e18580083
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1303. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1304. · Roxanne Gourneau · the citation of a statement

    Before
    After
    https://www.datacenterdynamics.com/en/news/first-nations-on-fort-peck-reservation-in-montana-banned-from-discussions-with-data-center-firms/
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-08-20; the record's rules, 2026-10-10).

  1305. · a statement · the folded into of a statement

    Before
    After
    cc2ba6ed-75d7-4189-90df-c4fdf670b8a8
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1306. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1307. · Livingston Parish Data Center · the citation of a statement

    Before
    After
    https://www.facebook.com/WBRZNews2/videos/livingston-parish-president-randy-delatte-announced-on-tuesday-that-he-has-not-s/1075986291565820/
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-03; the record's rules, 2026-10-10).

  1308. · Livingston Parish Data Center · the folded into of a statement

    Before
    After
    12ab932f-3b12-4398-92d6-e3c9554a1928
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1309. · Livingston Parish Data Center · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1310. · Nicole Flowers-Kimmerle · the citation of a statement

    Before
    After
    https://lailluminator.com/2026/09/12/data-center-light/
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-12; the record's rules, 2026-10-10).

  1311. · a statement · the folded into of a statement

    Before
    After
    dbe3aaf5-a718-4523-b7ba-13b0b95a4e29
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1312. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1313. · Nicholas Preservati · the citation of a statement

    Before
    After
    https://www.herald-dispatch.com/news/lawmakers-told-data-centers-could-be-key-to-improving-wv-water-issues/article_1fee8766-b43e-40b8-8ec3-c535d78f8fa1.html
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-17; the record's rules, 2026-10-10).

  1314. · a statement · the folded into of a statement

    Before
    After
    7823a7ea-62e3-4dd4-b002-30422612dd63
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1315. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1316. · Nicholas Preservati · the citation of a statement

    Before
    After
    https://www.register-herald.com/news/local_news/lawmakers-told-data-centers-could-be-key-to-improving-w-va-water-issues/article_f304af6a-0536-4b43-9ded-4af5fad6000f.html
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-16; the record's rules, 2026-10-10).

  1317. · a statement · the folded into of a statement

    Before
    After
    7823a7ea-62e3-4dd4-b002-30422612dd63
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1318. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1319. · Nicholas Preservati · the citation of a statement

    Before
    After
    https://www.herald-dispatch.com/news/lawmakers-told-data-centers-could-be-key-to-improving-wv-water-issues/article_1fee8766-b43e-40b8-8ec3-c535d78f8fa1.html
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-17; the record's rules, 2026-10-10).

  1320. · a statement · the folded into of a statement

    Before
    After
    77058655-ab65-4548-8dca-b5d09cf49d68
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1321. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1322. · Nicholas Preservati · the citation of a statement

    Before
    After
    https://www.register-herald.com/news/local_news/lawmakers-told-data-centers-could-be-key-to-improving-w-va-water-issues/article_f304af6a-0536-4b43-9ded-4af5fad6000f.html
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-16; the record's rules, 2026-10-10).

  1323. · a statement · the folded into of a statement

    Before
    After
    77058655-ab65-4548-8dca-b5d09cf49d68
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1324. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1325. · Mike Rogers · the citation of a statement

    Before
    After
    https://www.foxnews.com/politics/maga-begins-crack-2026-gop-roster-backs-away-from-trumps-tech-vision
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-03; the record's rules, 2026-10-10).

  1326. · a statement · the folded into of a statement

    Before
    After
    fcff7c88-cee4-422e-8ad6-2932285e09e9
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1327. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1328. · Mike Rogers · the citation of a statement

    Before
    After
    https://cbsaustin.com/news/connect-to-congress/michigan-republican-gop-mike-rogers-backs-temporary-ban-on-data-center-construction-democrat-abdul-el-sayed-us-senate-race-election
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-08-21; the record's rules, 2026-10-10).

  1329. · a statement · the folded into of a statement

    Before
    After
    c4500b01-83f5-4442-af4b-997175b63482
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1330. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1331. · Mike Rogers · the citation of a statement

    Before
    After
    https://michiganadvance.com/2026/08/20/after-data-center-investments-revealed-rogers-backs-statewide-moratorium/
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-08-20; the record's rules, 2026-10-10).

  1332. · a statement · the folded into of a statement

    Before
    After
    c4500b01-83f5-4442-af4b-997175b63482
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1333. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1334. · Mike Koerber · the citation of a statement

    Before
    After
    https://kutv.com/news/eye-on-your-money/epa-proposal-could-limit-public-access-to-data-center-plans
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-03; the record's rules, 2026-10-10).

  1335. · a statement · the folded into of a statement

    Before
    After
    56676dd4-3f47-4c2e-bb0a-6705f1af84a8
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1336. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1337. · Mike Kehoe · the citation of a statement

    Before
    After
    https://www.kcur.org/housing-development-section/2026-09-17/data-center-protest-missouri-capitol-legislature-construction-moratorium
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-17; the record's rules, 2026-10-10).

  1338. · a statement · the folded into of a statement

    Before
    After
    be1b2acb-ec82-4096-a899-6c662e60a8b9
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1339. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1340. · Equinix Secaucus · the citation of a statement

    Before
    After
    https://streamlinefeed.co.ke/news/equinix-data-center-diesel-spill-contaminates-new-jersey-meadowlands-creek
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-15; the record's rules, 2026-10-10).

  1341. · Equinix Secaucus · the folded into of a statement

    Before
    After
    c32cae76-d203-41bc-834a-201c10c7298e
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1342. · Equinix Secaucus · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1343. · Montgomery Meta Investment · the citation of a statement

    Before
    After
    https://www.meta.com/actions/building-montgomery-alabama/
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-01; the record's rules, 2026-10-10).

  1344. · Montgomery Meta Investment · the folded into of a statement

    Before
    After
    356c6e2f-e7bc-4af3-ab82-d1169ff51e8f
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1345. · Montgomery Meta Investment · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1346. · Montgomery Meta Investment · the citation of a statement

    Before
    After
    https://www.alreporter.com/2025/09/24/meta-to-expand-montgomery-data-center-upping-local-investments-to-1-5-billion/
    Why
    Cites the later report of the same claim by the same speaker (said again on 2025-09-24; the record's rules, 2026-10-10).

  1347. · Montgomery Meta Investment · the folded into of a statement

    Before
    After
    356c6e2f-e7bc-4af3-ab82-d1169ff51e8f
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1348. · Montgomery Meta Investment · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1349. · Montgomery Meta Investment · the citation of a statement

    Before
    After
    https://acppubs.com/DXC/article/1FB9B438-hensel-phelps-builds-with-mass-timber-at-meta-data-center
    Why
    Cites the later report of the same claim by the same speaker (said again on 2025-09-12; the record's rules, 2026-10-10).

  1350. · Montgomery Meta Investment · the folded into of a statement

    Before
    After
    7191a497-f8a2-404a-8bd6-4a0d5609718c
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1351. · Montgomery Meta Investment · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1352. · Mark Zatezalo · the citation of a statement

    Before
    After
    https://www.herald-dispatch.com/news/lawmakers-told-data-centers-could-be-key-to-improving-wv-water-issues/article_1fee8766-b43e-40b8-8ec3-c535d78f8fa1.html
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-17; the record's rules, 2026-10-10).

  1353. · a statement · the folded into of a statement

    Before
    After
    12cf77b9-0e56-4111-96c3-73154fd40a3b
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1354. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1355. · Maria Russo · the citation of a statement

    Before
    After
    https://www.herald-dispatch.com/news/lawmakers-told-data-centers-could-be-key-to-improving-wv-water-issues/article_1fee8766-b43e-40b8-8ec3-c535d78f8fa1.html
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-17; the record's rules, 2026-10-10).

  1356. · a statement · the folded into of a statement

    Before
    After
    74ec2b57-3f61-4699-951e-10d951884003
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1357. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1358. · Maria Russo · the citation of a statement

    Before
    After
    https://www.register-herald.com/news/local_news/lawmakers-told-data-centers-could-be-key-to-improving-w-va-water-issues/article_f304af6a-0536-4b43-9ded-4af5fad6000f.html
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-16; the record's rules, 2026-10-10).

  1359. · a statement · the folded into of a statement

    Before
    After
    74ec2b57-3f61-4699-951e-10d951884003
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1360. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1361. · Google West Memphis Data Center · the citation of a statement

    Before
    After
    https://www.youtube.com/watch?v=6a70EZAkVLc
    Why
    Cites the later report of the same claim by the same speaker (said again on 2025-10-08; the record's rules, 2026-10-10).

  1362. · Google West Memphis Data Center · the folded into of a statement

    Before
    After
    ef9860b3-15e0-44ee-a5d8-caeef645d1a7
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1363. · Google West Memphis Data Center · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1364. · Google West Memphis Data Center · the citation of a statement

    Before
    After
    https://www.youtube.com/watch?v=ODCdw4FF6Oc
    Why
    Cites the later report of the same claim by the same speaker (said again on 2025-10-02; the record's rules, 2026-10-10).

  1365. · Google West Memphis Data Center · the folded into of a statement

    Before
    After
    ef9860b3-15e0-44ee-a5d8-caeef645d1a7
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1366. · Google West Memphis Data Center · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1367. · Lee Zeldin · the citation of a statement

    Before
    After
    https://www.abc4.com/news/national/ap-epa-proposal-could-leave-the-public-in-the-dark-on-data-center-plans/amp/
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-03; the record's rules, 2026-10-10).

  1368. · a statement · the folded into of a statement

    Before
    After
    18fb487e-7b72-44df-8be0-812bd72b8325
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1369. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1370. · Lee Zeldin · the citation of a statement

    Before
    After
    https://kutv.com/news/eye-on-your-money/epa-proposal-could-limit-public-access-to-data-center-plans
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-03; the record's rules, 2026-10-10).

  1371. · a statement · the folded into of a statement

    Before
    After
    18fb487e-7b72-44df-8be0-812bd72b8325
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1372. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1373. · Meta Louisiana data center · the citation of a statement

    Before
    After
    https://www.thecentersquare.com/louisiana/article_f5fe155f-eab3-46be-872a-17c18608f4d9.html
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-02; the record's rules, 2026-10-10).

  1374. · Meta Louisiana data center · the folded into of a statement

    Before
    After
    40373bc1-4b01-4a66-80e9-a33447d56d54
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1375. · Meta Louisiana data center · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1376. · Kris Mayes · the citation of a statement

    Before
    After
    https://www.abc15.com/how-should-arizona-handle-data-centers-attorney-general-kris-mayes-warren-petersen-disagree
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-25; the record's rules, 2026-10-10).

  1377. · a statement · the folded into of a statement

    Before
    After
    192d0734-5c87-4b5a-9e9a-8477d45a91d3
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1378. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1379. · Kris Mayes · the citation of a statement

    Before
    After
    https://www.kjzz.org/business/2026-09-19/dont-blame-data-centers-for-arizonas-colorado-river-cuts-water-experts-say
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-19; the record's rules, 2026-10-10).

  1380. · a statement · the folded into of a statement

    Before
    After
    192d0734-5c87-4b5a-9e9a-8477d45a91d3
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1381. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1382. · Stratos Project · the citation of a statement

    Before
    After
    https://finance.yahoo.com/technology/ai/articles/kevin-oleary-admits-not-properly-003010592.html
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-08-19; the record's rules, 2026-10-10).

  1383. · Stratos Project · the folded into of a statement

    Before
    After
    590c27db-0cb1-4035-9543-1f21e1b2a474
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1384. · Stratos Project · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1385. · Stratos Project · the citation of a statement

    Before
    After
    https://finance.yahoo.com/technology/ai/articles/kevin-oleary-admits-not-properly-003010592.html
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-08-19; the record's rules, 2026-10-10).

  1386. · Stratos Project · the folded into of a statement

    Before
    After
    23170510-0599-460a-b1ff-3c1d5a0e32dd
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1387. · Stratos Project · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1388. · Stratos Project · the citation of a statement

    Before
    After
    https://moneywise.com/news/top-stories/kevin-oleary-utah-data-center-stratos-project-backlash
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-08-13; the record's rules, 2026-10-10).

  1389. · Stratos Project · the folded into of a statement

    Before
    After
    23170510-0599-460a-b1ff-3c1d5a0e32dd
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1390. · Stratos Project · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1391. · Stratos Project · the citation of a statement

    Before
    After
    https://utahnewsdispatch.com/2026/08/20/utah-lawmakers-discuss-data-centers-after-protests-and-political-fallout/
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-08-20; the record's rules, 2026-10-10).

  1392. · Stratos Project · the folded into of a statement

    Before
    After
    1e9f3514-7801-4161-bb59-c083bd3ca9b6
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1393. · Stratos Project · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1394. · Stratos Project · the citation of a statement

    Before
    After
    https://www.ksl.com/article/news/utah/kevin-oleary-agrees-to-cut-box-elder-county-data-center-project-area-in-half/51592076
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-06-05; the record's rules, 2026-10-10).

  1395. · Stratos Project · the folded into of a statement

    Before
    After
    bc423b78-cb98-44c1-a876-fc68190be9ec
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1396. · Stratos Project · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1397. · Keri Powell · the citation of a statement

    Before
    After
    https://kutv.com/news/eye-on-your-money/epa-proposal-could-limit-public-access-to-data-center-plans
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-03; the record's rules, 2026-10-10).

  1398. · a statement · the folded into of a statement

    Before
    After
    315cac33-5235-46d1-a962-d5e6dc2855e2
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1399. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1400. · Kendell Joseph · the citation of a statement

    Before
    After
    https://www.wemu.org/michigan-news/2026-09-23/environmentalists-renew-call-for-action-on-data-center-regulations-in-michigan
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-23; the record's rules, 2026-10-10).

  1401. · a statement · the folded into of a statement

    Before
    After
    0f8b727a-596e-472b-b5aa-a08b434dcadb
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1402. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1403. · Ken Paxton · the citation of a statement

    Before
    After
    https://www.fox7austin.com/election/james-talarcio-ken-paxton-texas-data-center-plan
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-30; the record's rules, 2026-10-10).

  1404. · Ken Paxton · the folded into of a statement

    Before
    After
    51eabdf7-a7f3-4406-9a20-f2d8d1f24de7
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1405. · Ken Paxton · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1406. · Bow Data Center · the citation of a statement

    Before
    After
    https://www.nhtalkradio.com/?p=27098
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-05; the record's rules, 2026-10-10).

  1407. · Bow Data Center · the folded into of a statement

    Before
    After
    8fcfe714-599e-4a41-8298-0ca93a1ac8a0
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1408. · Bow Data Center · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1409. · Bow Data Center (350 MW) · the citation of a statement

    Before
    After
    https://www.bostonglobe.com/2026/09/02/metro/bow-nh-data-center/
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-02; the record's rules, 2026-10-10).

  1410. · Bow Data Center (350 MW) · the folded into of a statement

    Before
    After
    4c0ffd4a-3c61-48cc-8648-3aaff5b974d8
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1411. · Bow Data Center (350 MW) · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1412. · Google Mesa data center · the citation of a statement

    Before
    After
    https://azbigmedia.com/business/google-breaks-ground-on-massive-600-million-mesa-data-center/
    Why
    Cites the later report of the same claim by the same speaker (said again on 2023-09-09; the record's rules, 2026-10-10).

  1413. · Google Mesa data center · the folded into of a statement

    Before
    After
    f446f516-14d8-4702-acdd-b93748231f5e
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1414. · Google Mesa data center · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1415. · Kathy Castor · the citation of a statement

    Before
    After
    https://www.cnbc.com/2026/09/15/congress-ai-data-center-utility-costs.html
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-16; the record's rules, 2026-10-10).

  1416. · a statement · the folded into of a statement

    Before
    After
    4895a88c-bce9-4ea3-8b32-3474667a0a84
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1417. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1418. · Kate Gallego · the citation of a statement

    Before
    After
    https://www.youtube.com/watch?v=cdiPM4pHwkU
    Why
    Cites the later report of the same claim by the same speaker (said again on 2025-09-13; the record's rules, 2026-10-10).

  1419. · a statement · the folded into of a statement

    Before
    After
    0b12268d-137d-44fe-9d00-14186e2e0c7d
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1420. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1421. · Jonathan Kreiss-Tomkins · the citation of a statement

    Before
    After
    https://alaskapublic.org/news/politics/elections/2026-09-21/where-do-alaskas-four-governor-candidates-stand-on-data-centers
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-21; the record's rules, 2026-10-10).

  1422. · a statement · the folded into of a statement

    Before
    After
    3dd177bf-26ba-4d85-a866-589164813440
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1423. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1424. · John Williamson · the citation of a statement

    Before
    After
    https://unpublished.ca/news-feed-item/2026-09-18/mp-calls-on-new-brunswick-to-reject-proposed-ai-data-centre-in-open-letter?page=895
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-18; the record's rules, 2026-10-10).

  1425. · a statement · the folded into of a statement

    Before
    After
    b48d4566-ea0e-4433-bfc7-85500a93116f
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1426. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1427. · John James · the citation of a statement

    Before
    After
    https://www.theoaklandpress.com/2026/09/28/fact-check-james-link-to-data-center-tax-breaks-donations/
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-28; the record's rules, 2026-10-10).

  1428. · a statement · the folded into of a statement

    Before
    After
    5b18aeb5-a7d7-4477-b6c9-8752640b4aba
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1429. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1430. · Google Mesa data center · the citation of a statement

    Before
    After
    https://www.azcentral.com/picture-gallery/news/local/mesa/2023/09/06/arizonas-1st-google-facility-will-be-600m-data-center-in-mesa/70778940007/
    Why
    Cites the later report of the same claim by the same speaker (said again on 2023-09-06; the record's rules, 2026-10-10).

  1431. · Google Mesa data center · the folded into of a statement

    Before
    After
    03eb0b2a-adc9-46d5-8fe1-346ed7ffe7ae
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1432. · Google Mesa data center · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1433. · Google Mesa data center · the citation of a statement

    Before
    After
    https://www.constructiondive.com/news/google-data-center-mesa-arizona/693029/
    Why
    Cites the later report of the same claim by the same speaker (said again on 2023-09-08; the record's rules, 2026-10-10).

  1434. · Google Mesa data center · the folded into of a statement

    Before
    After
    8368fdc3-8d8d-4e17-8a58-96f22dcf6f4a
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1435. · Google Mesa data center · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1436. · Jim Justice · the citation of a statement

    Before
    After
    https://albemarleobserver.news/2026/09/14/wv-data-center-secrecy-and-pollution-issues-loom-large-amid-growing-ai-risks/
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-14; the record's rules, 2026-10-10).

  1437. · a statement · the folded into of a statement

    Before
    After
    d87d0a78-bacc-4d48-8b57-ddb70760b88c
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1438. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1439. · Google Columbia County data center · the citation of a statement

    Before
    After
    https://www.aol.com/articles/google-representative-speaks-columbia-county-201222000.html
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-10; the record's rules, 2026-10-10).

  1440. · Google Columbia County data center · the folded into of a statement

    Before
    After
    33088d8a-490e-49af-aa85-8e10f6eba7be
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1441. · Google Columbia County data center · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1442. · Google Columbia County data center · the citation of a statement

    Before
    After
    https://www.yahoo.com/news/articles/google-representative-speaks-columbia-county-201222936.html
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-10; the record's rules, 2026-10-10).

  1443. · Google Columbia County data center · the folded into of a statement

    Before
    After
    32fea6ac-617c-4396-b03c-b0059de9373e
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1444. · Google Columbia County data center · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1445. · Jeff Jackson · the citation of a statement

    Before
    After
    https://nsjonline.com/article/2026/09/jackson-seeks-separate-duke-energy-rate-class-for-data-centers/
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-19; the record's rules, 2026-10-10).

  1446. · a statement · the folded into of a statement

    Before
    After
    c314f03e-4249-4300-8036-b6b4f4567975
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1447. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1448. · Jeff Jackson · the citation of a statement

    Before
    After
    https://nsjonline.com/article/2026/09/jackson-seeks-separate-duke-energy-rate-class-for-data-centers/
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-19; the record's rules, 2026-10-10).

  1449. · a statement · the folded into of a statement

    Before
    After
    7c97213d-f5cc-45e9-80e4-d283f92cba8b
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1450. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1451. · Jeff Jackson · the citation of a statement

    Before
    After
    https://journalnow.com/news/local/business/development/article_8abee666-ff36-49f0-8c7c-83288cdf877b.html
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-14; the record's rules, 2026-10-10).

  1452. · a statement · the folded into of a statement

    Before
    After
    7c97213d-f5cc-45e9-80e4-d283f92cba8b
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1453. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1454. · Jeff Jackson · the citation of a statement

    Before
    After
    https://www.rtoinsider.com/143725-north-carolina-ag-urges-creation-data-center-tariff/
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-17; the record's rules, 2026-10-10).

  1455. · a statement · the folded into of a statement

    Before
    After
    49d575b5-f72f-435c-b686-03f23d943756
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1456. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1457. · Jeff Jackson · the citation of a statement

    Before
    After
    https://ncnewsline.com/2026/09/14/nc-ag-jackson-requests-new-duke-rate-class-for-data-centers/
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-14; the record's rules, 2026-10-10).

  1458. · a statement · the folded into of a statement

    Before
    After
    49d575b5-f72f-435c-b686-03f23d943756
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1459. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1460. · Volition Industries Spanish Fork · the citation of a statement

    Before
    After
    https://www.ksl.com/article/51618421/spanish-fork-residents-frustrated-after-mayor-voices-approval-of-data-center-proposal
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-01; the record's rules, 2026-10-10).

  1461. · Volition Industries Spanish Fork · the folded into of a statement

    Before
    After
    2d0e0a0a-bf48-4dbc-a5a5-1cd6524b92b2
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1462. · Volition Industries Spanish Fork · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1463. · Volition Industries Spanish Fork · the citation of a statement

    Before
    After
    https://www.sltrib.com/news/2026/08/21/spanish-fork-data-center-what-know/
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-08-21; the record's rules, 2026-10-10).

  1464. · Volition Industries Spanish Fork · the folded into of a statement

    Before
    After
    2d0e0a0a-bf48-4dbc-a5a5-1cd6524b92b2
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1465. · Volition Industries Spanish Fork · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1466. · Volition Industries Spanish Fork · the citation of a statement

    Before
    After
    https://www.ksl.com/article/51627727/spanish-fork-city-council-approves-changes-to-city-code-for-data-centers
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-24; the record's rules, 2026-10-10).

  1467. · Volition Industries Spanish Fork · the folded into of a statement

    Before
    After
    026861b0-4e2d-46db-aa17-bc747fdce2fe
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1468. · Volition Industries Spanish Fork · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1469. · Jason Roe · the citation of a statement

    Before
    After
    https://www.michiganpublic.org/politics-government/2026-09-18/will-lawrence-rolls-out-plan-for-regulating-big-tech-data-centers-in-michigan-and-beyond
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-18; the record's rules, 2026-10-10).

  1470. · a statement · the folded into of a statement

    Before
    After
    aaa55b8a-a53d-4223-bdf3-b09d97ad0a1a
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1471. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1472. · Stratos Project · the citation of a statement

    Before
    After
    https://finance.yahoo.com/technology/ai/articles/kevin-oleary-admits-not-properly-003010592.html
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-08-19; the record's rules, 2026-10-10).

  1473. · Stratos Project · the folded into of a statement

    Before
    After
    31ba3f38-91ed-48e5-869c-b3a2262f457f
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1474. · Stratos Project · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1475. · International Brotherhood of Electrical Workers · the citation of a statement

    Before
    After
    https://wmky.org/news/2026-09-11/pro-data-center-labor-union-gives-big-to-kentucky-governor/
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-11; the record's rules, 2026-10-10).

  1476. · a statement · the folded into of a statement

    Before
    After
    5e48faa2-7f07-43da-b07e-0656ff18ffaa
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1477. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1478. · International Brotherhood of Electrical Workers · the citation of a statement

    Before
    After
    https://www.wmky.org/news/2026-09-11/pro-data-center-labor-union-gives-big-to-kentucky-governor?_amp=true
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-11; the record's rules, 2026-10-10).

  1479. · a statement · the folded into of a statement

    Before
    After
    d3f57274-b6b9-4d2d-8f4b-0dae6dbd9057
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1480. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1481. · Illinois Clean Jobs Coalition · the citation of a statement

    Before
    After
    https://www.thecentersquare.com/illinois/article_864f644b-8aa0-4a7b-89b1-42041c9db8c8.amp.html
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-09; the record's rules, 2026-10-10).

  1482. · a statement · the folded into of a statement

    Before
    After
    68336342-ce60-4261-bb2c-75d6a70f1e6b
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1483. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1484. · Greg Abbott · the citation of a statement

    Before
    After
    https://www.cbsnews.com/texas/video/abbott-takes-steps-to-regulate-data-centers-in-texas-as-the-governors-race-tightens/
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-25; the record's rules, 2026-10-10).

  1485. · a statement · the folded into of a statement

    Before
    After
    f1d97eec-95fd-43c7-b61e-0171410b409c
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1486. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1487. · Greg Abbott · the citation of a statement

    Before
    After
    https://www.insurancejournal.com/news/southcentral/2026/09/22/886377.htm
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-22; the record's rules, 2026-10-10).

  1488. · a statement · the folded into of a statement

    Before
    After
    42865815-4c0c-490e-a5e2-5168289b5b64
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1489. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1490. · Greg Abbott · the citation of a statement

    Before
    After
    https://texasscorecard.com/state/abbott-orders-halt-on-data-center-permits-during-state-audit/
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-21; the record's rules, 2026-10-10).

  1491. · a statement · the folded into of a statement

    Before
    After
    07b406e3-aea1-47ac-812c-2a8d443c6a6e
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1492. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1493. · Greg Abbott · the citation of a statement

    Before
    After
    https://abc13.com/story/gov-greg-abbott-directs-texas-commission-environmental-quality-halt-data-center-permits-office-says/19855560/
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-21; the record's rules, 2026-10-10).

  1494. · a statement · the folded into of a statement

    Before
    After
    ce97c765-5ab0-47af-976e-94c132d6749d
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1495. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1496. · Greg Abbott · the citation of a statement

    Before
    After
    https://www.timesrecordnews.com/story/news/local/2026/09/22/governor-says-new-data-centers-must-lower-texans-electricity-bills/91879022007/
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-22; the record's rules, 2026-10-10).

  1497. · a statement · the folded into of a statement

    Before
    After
    009c7cfc-ea53-41a2-81f9-825d53e48cc2
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1498. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1499. · Greg Abbott · the citation of a statement

    Before
    After
    https://abc13.com/story/gov-greg-abbott-directs-texas-commission-environmental-quality-halt-data-center-permits-office-says/19855560/
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-21; the record's rules, 2026-10-10).

  1500. · a statement · the folded into of a statement

    Before
    After
    009c7cfc-ea53-41a2-81f9-825d53e48cc2
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1501. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1502. · Greg Abbott · the citation of a statement

    Before
    After
    https://www.yahoo.com/news/politics/articles/abbott-orders-halt-texas-data-220754654.html
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-21; the record's rules, 2026-10-10).

  1503. · a statement · the folded into of a statement

    Before
    After
    009c7cfc-ea53-41a2-81f9-825d53e48cc2
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1504. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1505. · Greg Abbott · the citation of a statement

    Before
    After
    https://abc13.com/story/gov-greg-abbott-directs-texas-commission-environmental-quality-halt-data-center-permits-office-says/19855560/
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-21; the record's rules, 2026-10-10).

  1506. · a statement · the folded into of a statement

    Before
    After
    009c7cfc-ea53-41a2-81f9-825d53e48cc2
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1507. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1508. · a statement · the citation of a statement

    Before
    After
    https://247wallst.com/personal-finance/social-security/2026/09/19/texas-data-centers-dug-their-own-grave-abbott-says-at-63-a-rancher-can-lease-his-land-and-give-social-security-more-time-to-grow/
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-19; the record's rules, 2026-10-10).

  1509. · a statement · the folded into of a statement

    Before
    After
    51f50fcf-0ada-440e-ae9b-4e59f8ac849e
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1510. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1511. · Greg Abbott · the citation of a statement

    Before
    After
    https://texasstandard.org/stories/austin-area-residents-data-center-bans-texas-leaders-divided/
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-24; the record's rules, 2026-10-10).

  1512. · a statement · the folded into of a statement

    Before
    After
    95df6aba-de5c-49df-82ac-0abe7734d35c
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1513. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1514. · Greg Abbott · the citation of a statement

    Before
    After
    https://texasstandard.org/stories/austin-area-residents-data-center-bans-texas-leaders-divided/
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-24; the record's rules, 2026-10-10).

  1515. · a statement · the folded into of a statement

    Before
    After
    0087d131-89aa-4e9c-86ad-11e815921410
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1516. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1517. · Google West Memphis Data Center · the citation of a statement

    Before
    After
    https://www.yahoo.com/news/us/articles/west-memphis-utilities-no-rate-183236485.html
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-03; the record's rules, 2026-10-10).

  1518. · Google West Memphis Data Center · the folded into of a statement

    Before
    After
    783b0713-44a3-44f0-9a96-68751f164787
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1519. · Google West Memphis Data Center · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1520. · Google West Memphis Data Center · the citation of a statement

    Before
    After
    https://www.actionnews5.com/2026/04/28/google-announces-first-recipients-west-memphis-energy-impact-fund/
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-04-28; the record's rules, 2026-10-10).

  1521. · Google West Memphis Data Center · the folded into of a statement

    Before
    After
    8b64d148-6897-4a38-92d0-08afff61eee0
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1522. · Google West Memphis Data Center · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1523. · Glen Sturtevant Jr. · the citation of a statement

    Before
    After
    https://dailyprogress.com/news/state-regional/government-politics/article_242d5d6c-a221-5450-8d2d-dd748f9b34e1.html
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-19; the record's rules, 2026-10-10).

  1524. · a statement · the folded into of a statement

    Before
    After
    13be9773-cbbf-40c4-84fd-19da1009f7bc
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1525. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1526. · OpenAI Effingham County Data Center · the citation of a statement

    Before
    After
    https://www.wjcl.com/article/effingham-county-openai-data-center-proposal/73554517
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-08-28; the record's rules, 2026-10-10).

  1527. · OpenAI Effingham County Data Center · the folded into of a statement

    Before
    After
    c2444dab-0bdb-424a-9fb6-41d02ee9c0fe
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1528. · OpenAI Effingham County Data Center · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1529. · Gabe Evans · the citation of a statement

    Before
    After
    https://www.utilitydive.com/news/house-passes-ratepayer-protection-bill-data-centers/830658/
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-17; the record's rules, 2026-10-10).

  1530. · a statement · the folded into of a statement

    Before
    After
    3d3ec554-1a28-41fe-aa5c-f04b1ae80249
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1531. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1532. · Gabe Evans · the citation of a statement

    Before
    After
    https://www.foxnews.com/politics/first-data-center-bill-clears-house-republicans-democrats-scramble-answers-affordability-energy
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-16; the record's rules, 2026-10-10).

  1533. · a statement · the folded into of a statement

    Before
    After
    3d3ec554-1a28-41fe-aa5c-f04b1ae80249
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1534. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1535. · OpenAI Effingham County Data Center · the citation of a statement

    Before
    After
    https://www.effinghamherald.net/data-centers/effingham-county-property-taxes-could-see-one-of-largest-cuts-openai-data-center-project-camellia-ida-school-district-millage-rate-6-mills/
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-08-24; the record's rules, 2026-10-10).

  1536. · OpenAI Effingham County Data Center · the folded into of a statement

    Before
    After
    83e31d4c-1f8e-48e4-8e98-1948190c2b75
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1537. · OpenAI Effingham County Data Center · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1538. · OpenAI Effingham County Data Center · the citation of a statement

    Before
    After
    https://www.savannahnow.com/story/news/2026/08/03/local-officials-explain-abatement-agreement-for-new-data-center/91087706007/
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-08-03; the record's rules, 2026-10-10).

  1539. · OpenAI Effingham County Data Center · the folded into of a statement

    Before
    After
    83e31d4c-1f8e-48e4-8e98-1948190c2b75
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1540. · OpenAI Effingham County Data Center · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1541. · Dr. Amy Acton · the citation of a statement

    Before
    After
    https://www.dominionpost.com/2026/09/25/data-centers-a-hot-topic-in-congressional-state-elections/
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-26; the record's rules, 2026-10-10).

  1542. · a statement · the folded into of a statement

    Before
    After
    6e07a12e-06fb-454c-8da6-b6656245d0ce
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1543. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1544. · Donald Trump · the citation of a statement

    Before
    After
    https://www.inquirer.com/wires/ap/trump-dismisses-new-ai-guardrails-says-there-is-sick-conspiracy-against-ai-data-centers-20260914.html
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-14; the record's rules, 2026-10-10).

  1545. · a statement · the folded into of a statement

    Before
    After
    1d1b34a2-7f29-4aee-8f59-03d282c71331
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1546. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1547. · Donald Trump · the citation of a statement

    Before
    After
    https://www.douglas-budget.com/article/1561,trump-remains-popular-in-wyoming-even-as-his-beef-data-center-policies-put-him-at-odds
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-16; the record's rules, 2026-10-10).

  1548. · a statement · the folded into of a statement

    Before
    After
    9e0e5623-c9bb-4648-a46e-a13932aa7220
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1549. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1550. · Donald Trump · the citation of a statement

    Before
    After
    https://kutv.com/news/nation-world/epa-proposal-could-limit-public-access-to-data-center-plans
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-03; the record's rules, 2026-10-10).

  1551. · a statement · the folded into of a statement

    Before
    After
    854f5bbd-919e-4374-9bb8-2e68e8d2a638
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1552. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1553. · Bow Data Center (350 MW) · the citation of a statement

    Before
    After
    https://www.wmur.com/article/eversource-assess-350-mw-facility-bow-9226/73594468
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-02; the record's rules, 2026-10-10).

  1554. · Bow Data Center (350 MW) · the folded into of a statement

    Before
    After
    35718753-3f9a-40ef-acfb-8923a2af5c64
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1555. · Bow Data Center (350 MW) · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1556. · Dianne Triplett · the citation of a statement

    Before
    After
    https://www.utilitydive.com/news/duke-energy-florida-psc-large-load-rate/828951/
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-08-27; the record's rules, 2026-10-10).

  1557. · a statement · the folded into of a statement

    Before
    After
    2f33bcde-9399-4f61-9d30-3bb1d835efc9
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1558. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1559. · Derrick Van Orden · the citation of a statement

    Before
    After
    https://www.moorenews.com/news/national/data-centers-a-hot-issue-in-wisconsins-3rd-congressional-race/article_bb1ee839-851b-55a9-978f-8d7e4ee267d1.html
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-18; the record's rules, 2026-10-10).

  1560. · a statement · the folded into of a statement

    Before
    After
    956775ad-6de3-4130-90ea-08e207728545
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1561. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1562. · Ypsilanti Township / University of Michigan & Los Alamos Data Center · the citation of a statement

    Before
    After
    https://www.quiverquant.com/news/Press+Release%3A+Debbie+Dingell+Seeks+EPA%2C+EGLE+Review+of+Proposed+Los+Alamos+Site+in+Ypsilanti+Township
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-17; the record's rules, 2026-10-10).

  1563. · Ypsilanti Township / University of Michigan & Los Alamos Data Center · the folded into of a statement

    Before
    After
    e91ad0ec-e13e-478d-b9a9-38072f01b5f9
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1564. · Ypsilanti Township / University of Michigan & Los Alamos Data Center · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1565. · David Jolly · the citation of a statement

    Before
    After
    https://www.fox13news.com/news/ai-data-centers-erupt-major-battleground-florida-governors-race
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-28; the record's rules, 2026-10-10).

  1566. · a statement · the folded into of a statement

    Before
    After
    46759b8f-5425-484f-920e-539f2447ced7
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1567. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1568. · David Jolly · the citation of a statement

    Before
    After
    https://www.cltampa.com/news/florida-residents-are-raising-the-alarms-over-data-centers-and-ai-where-do-byron-donalds-and-david-jolly-stand/
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-16; the record's rules, 2026-10-10).

  1569. · a statement · the folded into of a statement

    Before
    After
    9cbff144-aaa0-4021-b71e-6e696938ace9
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1570. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1571. · David Jolly · the citation of a statement

    Before
    After
    https://baynews9.com/fl/tampa/political-connections/2026/09/22/political-connections-florida-september-22-2026
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-23; the record's rules, 2026-10-10).

  1572. · a statement · the folded into of a statement

    Before
    After
    bf182751-5bee-4226-bf91-39a6f7d211c7
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1573. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1574. · David Jolly · the citation of a statement

    Before
    After
    https://www.islandernews.com/lifestyle/technology/20-data-centers-are-operating-or-planned-in-florida-as-candidates-clash/article_b0061310-e0e2-4d40-beb9-05f3284fb118.html
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-20; the record's rules, 2026-10-10).

  1575. · a statement · the folded into of a statement

    Before
    After
    bf182751-5bee-4226-bf91-39a6f7d211c7
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1576. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1577. · David Jolly · the citation of a statement

    Before
    After
    https://suaragarut.id/en/florida-candidates-debate-insurance-data-centers
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-17; the record's rules, 2026-10-10).

  1578. · a statement · the folded into of a statement

    Before
    After
    bf182751-5bee-4226-bf91-39a6f7d211c7
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1579. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1580. · David Jolly · the citation of a statement

    Before
    After
    https://www.wtxl.com/news/state/david-jolly-byron-donalds-turn-ai-data-centers-into-florida-campaign-battleground
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-16; the record's rules, 2026-10-10).

  1581. · a statement · the folded into of a statement

    Before
    After
    bf182751-5bee-4226-bf91-39a6f7d211c7
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1582. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1583. · David Jolly · the citation of a statement

    Before
    After
    https://www.yahoo.com/news/politics/articles/jolly-said-majority-floridians-oppose-180000798.html
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-07; the record's rules, 2026-10-10).

  1584. · a statement · the folded into of a statement

    Before
    After
    bf182751-5bee-4226-bf91-39a6f7d211c7
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1585. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1586. · David Jolly · the citation of a statement

    Before
    After
    https://www.orlandosentinel.com/2026/09/10/byron-donalds-doubles-down-on-ai-data-centers-at-ucf-turning-point-event/
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-11; the record's rules, 2026-10-10).

  1587. · a statement · the folded into of a statement

    Before
    After
    5e4ddb66-daf0-4ab0-b75d-20bf9e8a23c8
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1588. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1589. · Vantage Port Washington Data Center · the citation of a statement

    Before
    After
    https://www.youtube.com/watch?v=JAuA8zKgdAs
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-07-28; the record's rules, 2026-10-10).

  1590. · Vantage Port Washington Data Center · the folded into of a statement

    Before
    After
    262c9d3b-45cc-4192-be85-0d7b216154fa
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1591. · Vantage Port Washington Data Center · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1592. · Clark County Education Association · the citation of a statement

    Before
    After
    https://thenevadaglobe.com/702times/lombardo-overhauls-nevada-data-center-tax-breaks-in-executive-order-mandating-school-funding-and-grid-defenses/
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-18; the record's rules, 2026-10-10).

  1593. · a statement · the folded into of a statement

    Before
    After
    c8753fe6-6e85-4701-bf23-1c50bc3ac00a
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1594. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1595. · Bow Data Center · the citation of a statement

    Before
    After
    https://www.nhtalkradio.com/?p=27098
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-05; the record's rules, 2026-10-10).

  1596. · Bow Data Center · the folded into of a statement

    Before
    After
    edddb29c-87aa-4beb-b560-e7aea9178683
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1597. · Bow Data Center · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1598. · Chrissy Lynch · the citation of a statement

    Before
    After
    https://www.briefs.co/news/massachusetts-tightens-the-rules-on-data-centers-as-energy-a/
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-10; the record's rules, 2026-10-10).

  1599. · a statement · the folded into of a statement

    Before
    After
    be92b6b3-2388-468c-8a90-4bee2083eae7
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1600. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1601. · Byron Donalds · the citation of a statement

    Before
    After
    https://floridaphoenix.com/2026/09/16/debate-about-data-centers-emerges-in-donalds-jolly-gubernatorial-race/
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-16; the record's rules, 2026-10-10).

  1602. · a statement · the folded into of a statement

    Before
    After
    4da8d0e3-cf23-4666-a057-e75f93b7f960
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1603. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1604. · Byron Donalds · the citation of a statement

    Before
    After
    https://www.cltampa.com/news/florida-residents-are-raising-the-alarms-over-data-centers-and-ai-where-do-byron-donalds-and-david-jolly-stand/
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-16; the record's rules, 2026-10-10).

  1605. · a statement · the folded into of a statement

    Before
    After
    24760d3a-62eb-4799-8adc-2d8322f39c1e
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1606. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1607. · Byron Donalds · the citation of a statement

    Before
    After
    https://www.wusf.org/politics-issues/2026-09-16/debate-about-data-centers-emerges-in-donalds-jolly-gubernatorial-race
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-16; the record's rules, 2026-10-10).

  1608. · a statement · the folded into of a statement

    Before
    After
    24760d3a-62eb-4799-8adc-2d8322f39c1e
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1609. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1610. · Byron Donalds · the citation of a statement

    Before
    After
    https://www.cltampa.com/news/florida-residents-are-raising-the-alarms-over-data-centers-and-ai-where-do-byron-donalds-and-david-jolly-stand/
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-16; the record's rules, 2026-10-10).

  1611. · a statement · the folded into of a statement

    Before
    After
    17899cfb-8aad-4f01-a42a-45e3688491a4
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1612. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1613. · Byron Donalds · the citation of a statement

    Before
    After
    https://www.cltampa.com/news/florida-residents-are-raising-the-alarms-over-data-centers-and-ai-where-do-byron-donalds-and-david-jolly-stand/
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-16; the record's rules, 2026-10-10).

  1614. · a statement · the folded into of a statement

    Before
    After
    1376696e-e406-4d83-bab2-c1ae9fdc6d72
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1615. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1616. · Byron Donalds · the citation of a statement

    Before
    After
    https://www.wusf.org/politics-issues/2026-09-16/debate-about-data-centers-emerges-in-donalds-jolly-gubernatorial-race
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-16; the record's rules, 2026-10-10).

  1617. · a statement · the folded into of a statement

    Before
    After
    1376696e-e406-4d83-bab2-c1ae9fdc6d72
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1618. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1619. · Byron Donalds · the citation of a statement

    Before
    After
    https://floridapolitics.com/archives/820851-byron-donalds-undaunted-by-polling-that-shows-democrats-more-trusted-on-data-center-issue/
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-20; the record's rules, 2026-10-10).

  1620. · a statement · the folded into of a statement

    Before
    After
    d89fc25f-a9d3-4bb9-a2c2-96ba73375a0b
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1621. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1622. · Byron Donalds · the citation of a statement

    Before
    After
    https://floridapolitics.com/archives/820851-byron-donalds-undaunted-by-polling-that-shows-democrats-more-trusted-on-data-center-issue/
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-19; the record's rules, 2026-10-10).

  1623. · a statement · the folded into of a statement

    Before
    After
    d89fc25f-a9d3-4bb9-a2c2-96ba73375a0b
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1624. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1625. · Stratos Project · the citation of a statement

    Before
    After
    https://www.ksl.com/article/news/utah/science-and-tech/utah-data-centers-promise-jobs-and-revenue-but-opponents-say-benefits-disappear/51619417
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-06; the record's rules, 2026-10-10).

  1626. · Stratos Project · the folded into of a statement

    Before
    After
    4949e0d0-71fe-4587-a412-dc8f8b08710c
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1627. · Stratos Project · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1628. · Stratos Project · the citation of a statement

    Before
    After
    https://www.ksl.com/article/news/utah/science-and-tech/utah-data-centers-promise-jobs-and-revenue-but-opponents-say-benefits-disappear/51619417
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-02; the record's rules, 2026-10-10).

  1629. · Stratos Project · the folded into of a statement

    Before
    After
    4949e0d0-71fe-4587-a412-dc8f8b08710c
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1630. · Stratos Project · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1631. · Bob Harvie · the citation of a statement

    Before
    After
    https://punchbowl.news/article/house/pennsylvania-democrat-data-center-ad/
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-10; the record's rules, 2026-10-10).

  1632. · a statement · the folded into of a statement

    Before
    After
    65989220-6d4c-4007-b6a1-a0941a48ff3a
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1633. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1634. · Bob Harvie · the citation of a statement

    Before
    After
    https://www.huffpost.com/entry/bob-harvie-brian-fitzpatrick-data-centers_n_6aa2c032e4b0f1a7ac691c2c
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-10; the record's rules, 2026-10-10).

  1635. · a statement · the folded into of a statement

    Before
    After
    65989220-6d4c-4007-b6a1-a0941a48ff3a
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1636. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1637. · Equinix Secaucus · the citation of a statement

    Before
    After
    https://njtoday.news/2026/09/16/5000-gallons-of-diesel-spill-from-secaucus-data-center-into-hackensack-river-tributary/
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-16; the record's rules, 2026-10-10).

  1638. · Equinix Secaucus · the folded into of a statement

    Before
    After
    bd7f3c92-9fea-4fb2-a57f-e4bd9fb02d97
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1639. · Equinix Secaucus · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1640. · Equinix Secaucus · the citation of a statement

    Before
    After
    https://attackofthefanboy.com/news/5000-gallons-of-diesel-leaked-from-a-data-center-into-a-new-jersey-creek-so-crews-rushed-to-contain-it-before-it-reached-the-river/
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-15; the record's rules, 2026-10-10).

  1641. · Equinix Secaucus · the folded into of a statement

    Before
    After
    bd7f3c92-9fea-4fb2-a57f-e4bd9fb02d97
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1642. · Equinix Secaucus · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1643. · Equinix Secaucus · the citation of a statement

    Before
    After
    https://patch.com/new-jersey/secaucus/update-fuel-spill-creek-north-jersey-data-center
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-15; the record's rules, 2026-10-10).

  1644. · Equinix Secaucus · the folded into of a statement

    Before
    After
    bd7f3c92-9fea-4fb2-a57f-e4bd9fb02d97
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1645. · Equinix Secaucus · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1646. · Ben Dziobek · the citation of a statement

    Before
    After
    https://www.northjersey.com/story/news/environment/2026/09/14/nj-data-center-ban-secaucus-diesel-spill-advocates/91758140007/
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-14; the record's rules, 2026-10-10).

  1647. · a statement · the folded into of a statement

    Before
    After
    f2597ebd-b209-49d9-b21e-b5cb71859868
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1648. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1649. · Ashley Brown · the citation of a statement

    Before
    After
    https://actonforgovernor.com/ramaswamys-data-center-plan-faces-legal-and-practical-barriers-and-far-fetched-attempt-to-pander-to-voters/
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-16; the record's rules, 2026-10-10).

  1650. · a statement · the folded into of a statement

    Before
    After
    184f9c25-72dd-4069-bc04-3c8de5d61f5a
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1651. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1652. · Amy Acton · the citation of a statement

    Before
    After
    https://www.wvxu.org/2026-09-30/watch-ohios-3-candidates-for-governor-weigh-in-on-data-centers-cost-of-living-and-more
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-30; the record's rules, 2026-10-10).

  1653. · a statement · the folded into of a statement

    Before
    After
    488c356b-4e33-4ce4-b601-3473acb4da24
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1654. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1655. · Amy Acton · the citation of a statement

    Before
    After
    https://actonforgovernor.com/icymi-dr-amy-acton-pledges-to-not-own-individual-stocks-as-governor-calls-on-opponent-to-sell-individual-stocks-and-divest-of-data-centers/
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-18; the record's rules, 2026-10-10).

  1656. · a statement · the folded into of a statement

    Before
    After
    c4fcf556-6efe-453a-bdfa-fd6ecff550f5
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1657. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1658. · Aaron Ford · the citation of a statement

    Before
    After
    https://nevadacurrent.com/2026/09/18/lombardo-doubles-down-on-data-centers-offers-trimmed-tax-breaks-commitments-to-wary-public/
    Why
    Cites the later report of the same claim by the same speaker (said again on 2026-09-18; the record's rules, 2026-10-10).

  1659. · a statement · the folded into of a statement

    Before
    After
    6c102e2b-68de-4da0-a09b-e5e895406e00
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1660. · a statement · the publication of a statement

    Before
    false
    After
    true
    Why
    Folded into the earlier line of the same claim by the same speaker on the same subject (the record's rules, 2026-10-10): the earliest dated wording is the line and this report is cited there as said again on its date. Nothing is deleted.

  1661. · Sioux Falls · the rating of a scorecard event

    Before
    case by case
    After
    no published rating
    Why
    The event carried Minnehaha County's own rating; on its new row, which carries none, it carries none. No row's rating changed.

  1662. · Sioux Falls · the rating of a scorecard event

    Before
    case by case
    After
    no published rating
    Why
    The event carried Minnehaha County's own rating; on its new row, which carries none, it carries none. No row's rating changed.

  1663. · Lincoln County · the rating of a scorecard event

    Before
    case by case
    After
    no published rating
    Why
    The event carried Minnehaha County's own rating; on its new row, which carries none, it carries none. No row's rating changed.

  1664. · Lincoln County · the rating of a scorecard event

    Before
    case by case
    After
    no published rating
    Why
    The event carried Minnehaha County's own rating; on its new row, which carries none, it carries none. No row's rating changed.

  1665. · Sioux Falls · the scorecard row of a scorecard event

    Before
    SD/minnehaha-county
    After
    SD/sioux-falls
    Why
    The act is the Sioux Falls City Council's; a city's act goes on the city's row, never the county's, on the editor's word (docs/batch-candidates-1011.md).

  1666. · Sioux Falls · the scorecard row of a scorecard event

    Before
    SD/minnehaha-county
    After
    SD/sioux-falls
    Why
    The act is the Sioux Falls City Council's; a city's act goes on the city's row, never the county's, on the editor's word (docs/batch-candidates-1011.md).

  1667. · Lincoln County · the scorecard row of a scorecard event

    Before
    SD/minnehaha-county
    After
    SD/lincoln-county
    Why
    The act is the Lincoln County Commission's; moved to the Lincoln County row on the editor's word (docs/batch-candidates-1011.md).

  1668. · Lincoln County · the scorecard row of a scorecard event

    Before
    SD/minnehaha-county
    After
    SD/lincoln-county
    Why
    The act is the Lincoln County Commission's; moved to the Lincoln County row on the editor's word (docs/batch-candidates-1011.md).

  1669. · a record · the publication of a scorecard row

    Before
    draft
    After
    published
    Why
    Published with no rating to hold its own acts, on the editor's word (docs/batch-candidates-1011.md).

  1670. · a record · the publication of a scorecard row

    Before
    draft
    After
    published
    Why
    Published with no rating to hold its own acts, on the editor's word (docs/batch-candidates-1011.md).

  1671. · a record · the publication of a scorecard event

    Before
    published
    After
    draft
    Why
    Held until the Saline Township row publishes, on the editor's word (docs/batch-candidates-1011.md); the row stays and publishes with its row.

  1672. · a record · the scorecard row of a scorecard event

    Before
    MI/michigan
    After
    MI/saline-township
    Why
    The hearing is on a Saline Township permit and the body is a state agency; it is held on the Saline Township row until that row publishes, on the editor's word (docs/batch-candidates-1011.md). It had been moved to Michigan's own row on 2026-10-09.

  1673. · Sioux Falls · the citation of a scorecard event

    Before
    After
    https://www.sfsimplified.com/meeting-over-moratorium-where-lincoln-county-stands-on-data-centers/
    Why
    names the public meeting's date, Tuesday, October 27; cited beside the report on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1674. · Sioux Falls · the citation of a scorecard event

    Before
    After
    https://www.dakotanewsnow.com/2026/08/26/data-center-debate-fuels-fiery-lincoln-county-sioux-falls-joint-meeting/
    Why
    the moratorium amendment failed 3 to 2 at the Lincoln County Commission and the late October meeting is a general discussion; the Argus Leader story the row cites cannot be read from here; cited beside the report on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1675. · Wiscasset · the citation of a scorecard event

    Before
    After
    https://www.wiscassetnewspaper.com/article/temp-bans-other-questions-head-november-ballot/274032
    Why
    the selectmen passed the warrant on September 1; the Daily Yonder had the moratorium as proposed; cited beside the report on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1676. · Defiance · the citation of a scorecard event

    Before
    After
    https://ohiocapitaljournal.com/2026/09/14/data-centers-are-on-the-november-ballot-in-these-18-ohio-communities/
    Why
    a US outlet naming Defiance among the nine petitions filed for the November election, beside the foreign relay the row cites; cited beside the report on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1677. · Ashville · the citation of a scorecard event

    Before
    After
    https://www.circlevilleherald.com/community/pickaway-county-board-of-elections-votes-unanimously-to-put-the-ashville-referendum-on-the-ballot/article_baa1518a-0afa-4aa0-a339-547e0cdd2dde.html
    Why
    the board of elections vote of August 24 that placed the referendum; the Ohio Capital Journal's text names Ashville nowhere; cited beside the report on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1678. · Ashville · the citation of a scorecard event

    Before
    After
    https://courtnewsohio.gov/cases/2026/SCO/0807/260906.asp
    Why
    the Supreme Court of Ohio's own account of its order; cited beside the report on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1679. · Emporia · the citation of a scorecard event

    Before
    After
    https://www.emporiaks.gov/CivicAlerts.aspx?AID=514
    Why
    the city's own notice of the court order and of the ordinance's effect pending the ruling; cited beside the report on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1680. · Boulder City · the citation of a scorecard event

    Before
    After
    https://www.bcnv.org/ballotquestions
    Why
    the city's own ballot page names Question 1 and the council's referral of February 24; cited beside the report on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1681. · North Berwick · the duplicate mark of a scorecard event

    Before
    After
    4494
    Why
    The event repeats 4494's act from a source about another place or another masthead: the Press Herald's South Berwick story repeats what WGME reported of North Berwick on August 25; the WGME story is about North Berwick itself; marked a duplicate with its source kept as a citation, on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1682. · Boulder City · the duplicate mark of a scorecard event

    Before
    After
    2464
    Why
    The event repeats 2464's act from a source about another place or another masthead: the same Mountain West News Bureau story under a second masthead; the Nevada station's copy carries the Boulder City line; marked a duplicate with its source kept as a citation, on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1683. · a statement · the scorecard row of a statement

    Before
    After
    us/united-states
    Why
    Filed on the national row: the speaker sits in Congress and the words describe a federal bill or the country; the speaker's state page lists it under What your members of Congress said and counts it in no total (DECISIONS 27), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1684. · a statement · the state of a statement

    Before
    CO
    After
    US
    Why
    Filed on the national row: the speaker sits in Congress and the words describe a federal bill or the country; the speaker's state page lists it under What your members of Congress said and counts it in no total (DECISIONS 27), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1685. · Bernie Moreno · the scorecard row of a statement

    Before
    After
    us/united-states
    Why
    Filed on the national row: the speaker sits in Congress and the words describe a federal bill or the country; the speaker's state page lists it under What your members of Congress said and counts it in no total (DECISIONS 27), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1686. · Bernie Moreno · the state of a statement

    Before
    OH
    After
    US
    Why
    Filed on the national row: the speaker sits in Congress and the words describe a federal bill or the country; the speaker's state page lists it under What your members of Congress said and counts it in no total (DECISIONS 27), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1687. · Mark Kelly · the scorecard row of a statement

    Before
    After
    us/united-states
    Why
    Filed on the national row: the speaker sits in Congress and the words describe a federal bill or the country; the speaker's state page lists it under What your members of Congress said and counts it in no total (DECISIONS 27), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1688. · Mark Kelly · the state of a statement

    Before
    AZ
    After
    US
    Why
    Filed on the national row: the speaker sits in Congress and the words describe a federal bill or the country; the speaker's state page lists it under What your members of Congress said and counts it in no total (DECISIONS 27), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1689. · Martin Heinrich · the scorecard row of a statement

    Before
    After
    us/united-states
    Why
    Filed on the national row: the speaker sits in Congress and the words describe a federal bill or the country; the speaker's state page lists it under What your members of Congress said and counts it in no total (DECISIONS 27), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1690. · Martin Heinrich · the state of a statement

    Before
    NM
    After
    US
    Why
    Filed on the national row: the speaker sits in Congress and the words describe a federal bill or the country; the speaker's state page lists it under What your members of Congress said and counts it in no total (DECISIONS 27), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1691. · a statement · the scorecard row of a statement

    Before
    After
    us/united-states
    Why
    Filed on the national row: the speaker sits in Congress and the words describe a federal bill or the country; the speaker's state page lists it under What your members of Congress said and counts it in no total (DECISIONS 27), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1692. · a statement · the state of a statement

    Before
    CO
    After
    US
    Why
    Filed on the national row: the speaker sits in Congress and the words describe a federal bill or the country; the speaker's state page lists it under What your members of Congress said and counts it in no total (DECISIONS 27), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1693. · a statement · the scorecard row of a statement

    Before
    After
    us/united-states
    Why
    Filed on the national row: the speaker sits in Congress and the words describe a federal bill or the country; the speaker's state page lists it under What your members of Congress said and counts it in no total (DECISIONS 27), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1694. · a statement · the state of a statement

    Before
    FL
    After
    US
    Why
    Filed on the national row: the speaker sits in Congress and the words describe a federal bill or the country; the speaker's state page lists it under What your members of Congress said and counts it in no total (DECISIONS 27), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1695. · Martin Heinrich · the scorecard row of a statement

    Before
    After
    us/united-states
    Why
    Filed on the national row: the speaker sits in Congress and the words describe a federal bill or the country; the speaker's state page lists it under What your members of Congress said and counts it in no total (DECISIONS 27), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1696. · Martin Heinrich · the state of a statement

    Before
    NM
    After
    US
    Why
    Filed on the national row: the speaker sits in Congress and the words describe a federal bill or the country; the speaker's state page lists it under What your members of Congress said and counts it in no total (DECISIONS 27), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1697. · Jon Husted · the scorecard row of a statement

    Before
    After
    us/united-states
    Why
    Filed on the national row: the speaker sits in Congress and the words describe a federal bill or the country; the speaker's state page lists it under What your members of Congress said and counts it in no total (DECISIONS 27), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1698. · Jon Husted · the state of a statement

    Before
    OH
    After
    US
    Why
    Filed on the national row: the speaker sits in Congress and the words describe a federal bill or the country; the speaker's state page lists it under What your members of Congress said and counts it in no total (DECISIONS 27), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1699. · Ro Khanna · the scorecard row of a statement

    Before
    After
    us/united-states
    Why
    Filed on the national row: the speaker sits in Congress and the words describe a federal bill or the country; the speaker's state page lists it under What your members of Congress said and counts it in no total (DECISIONS 27), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1700. · Ro Khanna · the state of a statement

    Before
    CA
    After
    US
    Why
    Filed on the national row: the speaker sits in Congress and the words describe a federal bill or the country; the speaker's state page lists it under What your members of Congress said and counts it in no total (DECISIONS 27), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1701. · Gabe Evans · the scorecard row of a statement

    Before
    After
    us/united-states
    Why
    Filed on the national row: the speaker sits in Congress and the words describe a federal bill or the country; the speaker's state page lists it under What your members of Congress said and counts it in no total (DECISIONS 27), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1702. · Gabe Evans · the state of a statement

    Before
    CO
    After
    US
    Why
    Filed on the national row: the speaker sits in Congress and the words describe a federal bill or the country; the speaker's state page lists it under What your members of Congress said and counts it in no total (DECISIONS 27), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1703. · Kathy Castor · the scorecard row of a statement

    Before
    After
    us/united-states
    Why
    Filed on the national row: the speaker sits in Congress and the words describe a federal bill or the country; the speaker's state page lists it under What your members of Congress said and counts it in no total (DECISIONS 27), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1704. · Kathy Castor · the state of a statement

    Before
    FL
    After
    US
    Why
    Filed on the national row: the speaker sits in Congress and the words describe a federal bill or the country; the speaker's state page lists it under What your members of Congress said and counts it in no total (DECISIONS 27), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1705. · Gabe Evans · the scorecard row of a statement

    Before
    After
    us/united-states
    Why
    Filed on the national row: the speaker sits in Congress and the words describe a federal bill or the country; the speaker's state page lists it under What your members of Congress said and counts it in no total (DECISIONS 27), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1706. · Gabe Evans · the state of a statement

    Before
    CO
    After
    US
    Why
    Filed on the national row: the speaker sits in Congress and the words describe a federal bill or the country; the speaker's state page lists it under What your members of Congress said and counts it in no total (DECISIONS 27), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1707. · Martin Heinrich · the scorecard row of a statement

    Before
    After
    us/united-states
    Why
    Filed on the national row: the speaker sits in Congress and the words describe a federal bill or the country; the speaker's state page lists it under What your members of Congress said and counts it in no total (DECISIONS 27), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1708. · Martin Heinrich · the state of a statement

    Before
    NM
    After
    US
    Why
    Filed on the national row: the speaker sits in Congress and the words describe a federal bill or the country; the speaker's state page lists it under What your members of Congress said and counts it in no total (DECISIONS 27), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1709. · Ro Khanna · the scorecard row of a statement

    Before
    After
    us/united-states
    Why
    Filed on the national row: the speaker sits in Congress and the words describe a federal bill or the country; the speaker's state page lists it under What your members of Congress said and counts it in no total (DECISIONS 27), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1710. · Ro Khanna · the state of a statement

    Before
    CA
    After
    US
    Why
    Filed on the national row: the speaker sits in Congress and the words describe a federal bill or the country; the speaker's state page lists it under What your members of Congress said and counts it in no total (DECISIONS 27), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1711. · Martin Heinrich · the scorecard row of a statement

    Before
    After
    us/united-states
    Why
    Filed on the national row: the speaker sits in Congress and the words describe a federal bill or the country; the speaker's state page lists it under What your members of Congress said and counts it in no total (DECISIONS 27), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1712. · Martin Heinrich · the state of a statement

    Before
    NM
    After
    US
    Why
    Filed on the national row: the speaker sits in Congress and the words describe a federal bill or the country; the speaker's state page lists it under What your members of Congress said and counts it in no total (DECISIONS 27), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1713. · Stratos Project · the record link of a statement

    Before
    After
    stratos-box-elder-ut
    Why
    The statement describes the mayor's vote on the Box Elder County project, which the Stratos record is; attached on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1714. · Stratos Project · the publication of a source list entry

    Before
    published
    After
    draft
    Why
    The story is about Clearfield's own moratorium and names Stratos only in passing; off the record's source list on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10). The row stays and the Drafts tab can put it back. (https://www.ksl.com/article/51622427/clearfield-leaders-ok-180-day-moratorium-on-data-center-development)

  1715. · Ypsilanti Township / University of Michigan & Los Alamos Data Center · the record link of a statement

    Before
    ypsilanti-township-university-of-michigan-and-los-alamos-data-center-mi
    After
    Why
    The statement's words describe New Jersey, not the ypsilanti-township-university-of-michigan-and-los-alamos-data-center-mi record; detached on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1716. · Young people protesters · the state of a statement

    Before
    MI
    After
    NJ
    Why
    Filed under New Jersey: the march was in Union County, New Jersey; the Ypsilanti Township record is not its subject; a statement sits on the place its words describe (DECISIONS 31), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1717. · Portland Press Herald fact check · the scorecard row of a statement

    Before
    After
    me/eastport
    Why
    Filed on ME/eastport: the row Eastport's ban sits on; the Pennsylvania filing came from the fact check's subject; a statement sits on the place its words describe (DECISIONS 31), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1718. · Portland Press Herald fact check · the state of a statement

    Before
    PA
    After
    ME
    Why
    Filed on ME/eastport: the row Eastport's ban sits on; the Pennsylvania filing came from the fact check's subject; a statement sits on the place its words describe (DECISIONS 31), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1719. · Megan Gill · the scorecard row of a statement

    Before
    After
    qc/quebec
    Why
    Filed on QC/quebec: the claim describes Quebec's rate; a statement sits on the place its words describe (DECISIONS 31), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1720. · Megan Gill · the state of a statement

    Before
    AB
    After
    QC
    Why
    Filed on QC/quebec: the claim describes Quebec's rate; a statement sits on the place its words describe (DECISIONS 31), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1721. · Josh Riley · the scorecard row of a statement

    Before
    After
    us/united-states
    Why
    Filed on the national row: a member of Congress introducing a federal bill, which item 9's rule files on the national row (the October 9 proposal said New York, before that rule); New York's page lists it under What your members of Congress said; a statement sits on the place its words describe (DECISIONS 31), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1722. · Steamfitters UA Local 602 · the state of a statement

    Before
    CA
    After
    VA
    Why
    Filed under Virginia: the union's ground is the capital region; Virginia is the one of the three with a page that reads it as data center alley; a statement sits on the place its words describe (DECISIONS 31), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1723. · James Hensen · the state of a statement

    Before
    LA
    After
    TX
    Why
    Filed under Texas: the project polls Texas voters; a statement sits on the place its words describe (DECISIONS 31), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1724. · AEP Ohio · the state of a statement

    Before
    AR
    After
    OH
    Why
    Filed under Ohio: the claim describes AEP Ohio's pipeline; a statement sits on the place its words describe (DECISIONS 31), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1725. · National Republican Senatorial Committee · the state of a statement

    Before
    MI
    After
    OH
    Why
    Filed under Ohio: the claim describes Ohio's Senate race; a statement sits on the place its words describe (DECISIONS 31), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1726. · Maura McDermott · the state of a statement

    Before
    US
    After
    ME
    Why
    Filed under Maine: the claim describes Maine; a statement sits on the place its words describe (DECISIONS 31), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1727. · Meta · the state of a statement

    Before
    IN
    After
    LA
    Why
    Filed under Louisiana: the claim describes where the program's first cohort meets; the attachment to the Meta Indianapolis record is kept; a statement sits on the place its words describe (DECISIONS 31), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1728. · Jim Beam · the state of a statement

    Before
    LA
    After
    TN
    Why
    Filed under Tennessee: the column puts the site in Tennessee, so the statement is filed where its words put it; a statement sits on the place its words describe (DECISIONS 31), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1729. · Calgary Herald · the scorecard row of a statement

    Before
    After
    az/chandler
    Why
    Filed on AZ/chandler: the claim describes Chandler, Arizona; a statement sits on the place its words describe (DECISIONS 31), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1730. · Calgary Herald · the state of a statement

    Before
    AB
    After
    AZ
    Why
    Filed on AZ/chandler: the claim describes Chandler, Arizona; a statement sits on the place its words describe (DECISIONS 31), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1731. · Ypsilanti Township / University of Michigan & Los Alamos Data Center · the record link of a statement

    Before
    ypsilanti-township-university-of-michigan-and-los-alamos-data-center-mi
    After
    Why
    The statement's words describe New York, not the ypsilanti-township-university-of-michigan-and-los-alamos-data-center-mi record; detached on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1732. · New York City protesters · the state of a statement

    Before
    MI
    After
    NY
    Why
    Filed under New York: the rally was at Palantir's New York office; the Ypsilanti Township record is not its subject; a statement sits on the place its words describe (DECISIONS 31), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1733. · article author · the state of a statement

    Before
    WI
    After
    IL
    Why
    Filed under Illinois: the claim describes Illinois; a statement sits on the place its words describe (DECISIONS 31), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1734. · Hassane El-Khoury · the state of a statement

    Before
    NY
    After
    AZ
    Why
    Filed under Arizona: the claim describes discussions with Arizona lawmakers; a statement sits on the place its words describe (DECISIONS 31), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1735. · Oracle · the scorecard row of a statement

    Before
    After
    us/united-states
    Why
    Filed on the national row: a company claim across four states; a statement sits on the place its words describe (DECISIONS 31), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1736. · Oracle · the state of a statement

    Before
    CA
    After
    US
    Why
    Filed on the national row: a company claim across four states; a statement sits on the place its words describe (DECISIONS 31), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1737. · Jeremy Merrill · the scorecard row of a statement

    Before
    After
    us/united-states
    Why
    Filed on the national row: a national reporter's observation about two governors; a statement sits on the place its words describe (DECISIONS 31), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1738. · Jeremy Merrill · the state of a statement

    Before
    TX
    After
    US
    Why
    Filed on the national row: a national reporter's observation about two governors; a statement sits on the place its words describe (DECISIONS 31), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1739. · Hyperscale Data Dowagiac AI Data Center · the record link of a statement

    Before
    hyperscale-data-dowagiac-ai-data-center-mi
    After
    Why
    The statement's words describe Montana, not the hyperscale-data-dowagiac-ai-data-center-mi record; detached on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1740. · Hyperscale Data · the state of a statement

    Before
    MI
    After
    MT
    Why
    Filed under Montana: the claim describes the Montana site, not the Michigan conversion; a statement sits on the place its words describe (DECISIONS 31), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1741. · Brian Bengs · the state of a statement

    Before
    US
    After
    SD
    Why
    Filed under South Dakota: the claim describes South Dakota legislative races; a statement sits on the place its words describe (DECISIONS 31), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1742. · Kathy Castor · the scorecard row of a statement

    Before
    After
    us/united-states
    Why
    Filed on the national row: a member of Congress co sponsoring a federal bill, which item 9's rule files on the national row (the October 9 proposal said Florida, before that rule); Florida's page lists it under What your members of Congress said; a statement sits on the place its words describe (DECISIONS 31), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1743. · Kathy Castor · the state of a statement

    Before
    VA
    After
    US
    Why
    Filed on the national row: a member of Congress co sponsoring a federal bill, which item 9's rule files on the national row (the October 9 proposal said Florida, before that rule); Florida's page lists it under What your members of Congress said; a statement sits on the place its words describe (DECISIONS 31), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1744. · Joseph Verruni · the state of a statement

    Before
    KY
    After
    IN
    Why
    Filed under Indiana: the claim describes an Indiana utility's rates; a statement sits on the place its words describe (DECISIONS 31), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1745. · Sean Farney · the scorecard row of a statement

    Before
    After
    us/united-states
    Why
    Filed on the national row: a national market statement from a brokerage report; a statement sits on the place its words describe (DECISIONS 31), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1746. · Sean Farney · the state of a statement

    Before
    VA
    After
    US
    Why
    Filed on the national row: a national market statement from a brokerage report; a statement sits on the place its words describe (DECISIONS 31), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1747. · Gabe Evans · the scorecard row of a statement

    Before
    After
    us/united-states
    Why
    Filed on the national row: a member of Congress sponsoring a federal bill, which item 9's rule files on the national row (the October 9 proposal said Colorado, before that rule); Colorado's page lists it under What your members of Congress said; a statement sits on the place its words describe (DECISIONS 31), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1748. · Gabe Evans · the state of a statement

    Before
    VA
    After
    US
    Why
    Filed on the national row: a member of Congress sponsoring a federal bill, which item 9's rule files on the national row (the October 9 proposal said Colorado, before that rule); Colorado's page lists it under What your members of Congress said; a statement sits on the place its words describe (DECISIONS 31), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1749. · Ypsilanti Township / University of Michigan & Los Alamos Data Center · the record link of a statement

    Before
    ypsilanti-township-university-of-michigan-and-los-alamos-data-center-mi
    After
    Why
    The statement's words describe Pennsylvania, not the ypsilanti-township-university-of-michigan-and-los-alamos-data-center-mi record; detached on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1750. · Hazleton protesters · the state of a statement

    Before
    MI
    After
    PA
    Why
    Filed under Pennsylvania: the protest was in Hazleton, Pennsylvania; the In These Times story covered several protests and the card was Michigan's; a statement sits on the place its words describe (DECISIONS 31), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1751. · Tom Barrett · the state of a statement

    Before
    US
    After
    MI
    Why
    Filed under Michigan: the claim describes his Michigan House votes; a statement sits on the place its words describe (DECISIONS 31), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1752. · Jo Borrás · the state of a statement

    Before
    IN
    After
    VA
    Why
    Filed under Virginia: the claim describes Dominion Energy Virginia's rates; a statement sits on the place its words describe (DECISIONS 31), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1753. · Lee Zeldin · the state of a statement

    Before
    TN
    After
    NY
    Why
    Filed under New York: the claim describes New York's moratorium; a statement sits on the place its words describe (DECISIONS 31), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1754. · a record · the place of a figure

    Before
    Utah, statewide
    After
    New Albany, Franklin County, OH
    Why
    Moved to New Albany, Franklin County, OH: the Utah article used the New Albany campus as an example; a figure sits on the place its words describe (DECISIONS 31), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1755. · a record · the place of a figure

    Before
    Utah, statewide
    After
    New Albany, Franklin County, OH
    Why
    Moved to New Albany, Franklin County, OH: the Utah article used the New Albany campus as an example; a figure sits on the place its words describe (DECISIONS 31), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1756. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Off the record: not about data centers; a comparison in an essay; on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10). The row stays.

  1757. · a record · the place of a figure

    Before
    Cheyenne, Laramie County, WY
    After
    Austin, Travis County, TX
    Why
    Moved to Austin, Travis County, TX: the figure describes the Austin site; a figure sits on the place its words describe (DECISIONS 31), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1758. · a record · the place of a figure

    Before
    Cheyenne, Laramie County, WY
    After
    Austin, Travis County, TX
    Why
    Moved to Austin, Travis County, TX: the figure describes the Austin site; a figure sits on the place its words describe (DECISIONS 31), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1759. · a record · the place of a figure

    Before
    Doña Ana County, NM; statewide in NY, TX, PA, MI, GA
    After
    United States, national
    Why
    Moved to United States, national: a count across two states from a national story; a figure sits on the place its words describe (DECISIONS 31), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1760. · a record · the place of a figure

    Before
    Doña Ana County, NM; statewide in NY, TX, PA, MI, GA
    After
    United States, national
    Why
    Moved to United States, national: a count across two states from a national story; a figure sits on the place its words describe (DECISIONS 31), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1761. · a record · the place of a figure

    Before
    Iowa, United States
    After
    Kuna, Ada County, ID
    Why
    Moved to Kuna, Ada County, ID: the words describe the Meta Kuna campus; a figure sits on the place its words describe (DECISIONS 31), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1762. · a record · the place of a figure

    Before
    Iowa, United States
    After
    Kuna, Ada County, ID
    Why
    Moved to Kuna, Ada County, ID: the words describe the Meta Kuna campus; a figure sits on the place its words describe (DECISIONS 31), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1763. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Off the record: a vendor's market share claim about its products, not a figure about any place or data center; on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10). The row stays.

  1764. · a record · the place of a figure

    Before
    Sherwood, Saskatchewan
    After
    Ontario, provincewide
    Why
    Moved to Ontario, provincewide: the stored value is Ontario's share; a figure sits on the place its words describe (DECISIONS 31), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1765. · a record · the place of a figure

    Before
    Sherwood, Saskatchewan
    After
    Ontario, provincewide
    Why
    Moved to Ontario, provincewide: the stored value is Ontario's share; a figure sits on the place its words describe (DECISIONS 31), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1766. · a record · the place of a figure

    Before
    Marshalltown, Iowa, IA
    After
    North Carolina, statewide
    Why
    Moved to North Carolina, statewide: an Iowa speaker's example about North Carolina; a figure sits on the place its words describe (DECISIONS 31), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1767. · a record · the place of a figure

    Before
    Marshalltown, Iowa, IA
    After
    North Carolina, statewide
    Why
    Moved to North Carolina, statewide: an Iowa speaker's example about North Carolina; a figure sits on the place its words describe (DECISIONS 31), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1768. · a record · the place of a figure

    Before
    West Memphis, Crittenden County, AR; Memphis, Shelby County, TN
    After
    Jefferson County, AR
    Why
    Moved to Jefferson County, AR: the plant is in Jefferson County; the figure is its cost; a figure sits on the place its words describe (DECISIONS 31), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1769. · a record · the place of a figure

    Before
    West Memphis, Crittenden County, AR; Memphis, Shelby County, TN
    After
    Jefferson County, AR
    Why
    Moved to Jefferson County, AR: the plant is in Jefferson County; the figure is its cost; a figure sits on the place its words describe (DECISIONS 31), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1770. · a record · the place of a figure

    Before
    Louisiana, Loudoun County Virginia, Montgomery County Missouri, statewide
    After
    Montgomery County, MO
    Why
    Moved to Montgomery County, MO: the words describe one county; a figure sits on the place its words describe (DECISIONS 31), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1771. · a record · the place of a figure

    Before
    Louisiana, Loudoun County Virginia, Montgomery County Missouri, statewide
    After
    Montgomery County, MO
    Why
    Moved to Montgomery County, MO: the words describe one county; a figure sits on the place its words describe (DECISIONS 31), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1772. · a record · the place of a figure

    Before
    Louisiana, statewide
    After
    United States, national
    Why
    Moved to United States, national: a national count; a figure sits on the place its words describe (DECISIONS 31), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1773. · a record · the place of a figure

    Before
    Louisiana, statewide
    After
    United States, national
    Why
    Moved to United States, national: a national count; a figure sits on the place its words describe (DECISIONS 31), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1774. · a record · the place of a figure

    Before
    Utah, statewide
    After
    New Albany, Franklin County, OH
    Why
    Moved to New Albany, Franklin County, OH: the Utah article used the New Albany campus as an example; a figure sits on the place its words describe (DECISIONS 31), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1775. · a record · the place of a figure

    Before
    Utah, statewide
    After
    New Albany, Franklin County, OH
    Why
    Moved to New Albany, Franklin County, OH: the Utah article used the New Albany campus as an example; a figure sits on the place its words describe (DECISIONS 31), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1776. · a record · the place of a figure

    Before
    Richland Parish, LA
    After
    Ouachita Parish, LA
    Why
    Moved to Ouachita Parish, LA: the words describe Ouachita Parish's hotel tax; a figure sits on the place its words describe (DECISIONS 31), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1777. · a record · the place of a figure

    Before
    Richland Parish, LA
    After
    Ouachita Parish, LA
    Why
    Moved to Ouachita Parish, LA: the words describe Ouachita Parish's hotel tax; a figure sits on the place its words describe (DECISIONS 31), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1778. · a record · the place of a figure

    Before
    Allentown, Pennsylvania; United States, statewide
    After
    United States, national
    Why
    Moved to United States, national: a federal program; the Allentown record is where the article was read, not what the figure describes; a figure sits on the place its words describe (DECISIONS 31), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1779. · a record · the place of a figure

    Before
    Allentown, Pennsylvania; United States, statewide
    After
    United States, national
    Why
    Moved to United States, national: a federal program; the Allentown record is where the article was read, not what the figure describes; a figure sits on the place its words describe (DECISIONS 31), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1780. · a record · the place of a figure

    Before
    Port Washington, Ozaukee County, WI
    After
    Virginia, statewide
    Why
    Moved to Virginia, statewide: the campus is in Virginia and not named, so the state carries it; a figure sits on the place its words describe (DECISIONS 31), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1781. · a record · the place of a figure

    Before
    Port Washington, Ozaukee County, WI
    After
    Virginia, statewide
    Why
    Moved to Virginia, statewide: the campus is in Virginia and not named, so the state carries it; a figure sits on the place its words describe (DECISIONS 31), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1782. · a record · the place of a figure

    Before
    Port Washington, Ozaukee County, WI
    After
    Virginia, statewide
    Why
    Moved to Virginia, statewide: the words describe Vantage's Virginia campuses; a figure sits on the place its words describe (DECISIONS 31), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1783. · a record · the place of a figure

    Before
    Port Washington, Ozaukee County, WI
    After
    Virginia, statewide
    Why
    Moved to Virginia, statewide: the words describe Vantage's Virginia campuses; a figure sits on the place its words describe (DECISIONS 31), on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10).

  1784. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Off the record as a figure: the 64 percent is energy experts' calculation as the outlet reported it, with no document behind it the record can read, and it stays on Stratos as a reported claim attributed to Cache Valley Daily; on the editor's word (the editor's batch trust-fixes-1010 of 2026-10-10). The row stays.

  1785. · a statement · the source outlet of a statement

    Before
    yahoo.com
    After
    The Cool Down
    Why
    The outlet label named the copy's host, not the publisher; corrected to The Cool Down, the page's provider field as read on 2026-10-09 (the page did not answer now) (the editor's batch trust-fixes-1009 of 2026-10-09).

  1786. · Michael Turner · the source outlet of a statement

    Before
    localsyr.com
    After
    WSYR Syracuse
    Why
    The outlet label named the copy's host, not the publisher; corrected to WSYR Syracuse, the page's own provider field, read now (the editor's batch trust-fixes-1009 of 2026-10-09).

  1787. · Suhas Subramanyam · the source outlet of a statement

    Before
    Yahoo
    After
    Virginia Mercury
    Why
    The outlet label named the copy's host, not the publisher; corrected to Virginia Mercury, the url is on the publisher's own site (the editor's batch trust-fixes-1009 of 2026-10-09).

  1788. · a statement · the source outlet of a statement

    Before
    yahoo.com
    After
    The Cool Down
    Why
    The outlet label named the copy's host, not the publisher; corrected to The Cool Down, the page's provider field as read on 2026-10-09 (the page did not answer now) (the editor's batch trust-fixes-1009 of 2026-10-09).

  1789. · Suhas Subramanyam · the source outlet of a statement

    Before
    Yahoo
    After
    Virginia Mercury
    Why
    The outlet label named the copy's host, not the publisher; corrected to Virginia Mercury, the url is on the publisher's own site (the editor's batch trust-fixes-1009 of 2026-10-09).

  1790. · Suhas Subramanyam · the source outlet of a statement

    Before
    Yahoo
    After
    Virginia Mercury
    Why
    The outlet label named the copy's host, not the publisher; corrected to Virginia Mercury, the url is on the publisher's own site (the editor's batch trust-fixes-1009 of 2026-10-09).

  1791. · a statement · the source outlet of a statement

    Before
    yahoo.com
    After
    The Cool Down
    Why
    The outlet label named the copy's host, not the publisher; corrected to The Cool Down, the page's provider field as read on 2026-10-09 (the page did not answer now) (the editor's batch trust-fixes-1009 of 2026-10-09).

  1792. · a statement · the source outlet of a statement

    Before
    yahoo.com
    After
    The Cool Down
    Why
    The outlet label named the copy's host, not the publisher; corrected to The Cool Down, the page's provider field as read on 2026-10-09 (the page did not answer now) (the editor's batch trust-fixes-1009 of 2026-10-09).

  1793. · Ryan McMahon · the source outlet of a statement

    Before
    localsyr.com
    After
    WSYR Syracuse
    Why
    The outlet label named the copy's host, not the publisher; corrected to WSYR Syracuse, the page's own provider field, read now (the editor's batch trust-fixes-1009 of 2026-10-09).

  1794. · a statement · the source outlet of a statement

    Before
    Yahoo
    After
    WTTG
    Why
    The outlet label named the copy's host, not the publisher; corrected to WTTG, the page's provider field as read on 2026-10-09 (the page did not answer now) (the editor's batch trust-fixes-1009 of 2026-10-09).

  1795. · Suhas Subramanyam · the source outlet of a statement

    Before
    Yahoo
    After
    Virginia Mercury
    Why
    The outlet label named the copy's host, not the publisher; corrected to Virginia Mercury, the url is on the publisher's own site (the editor's batch trust-fixes-1009 of 2026-10-09).

  1796. · a record · the outlet of a news item

    Before
    Yahoo
    After
    WTTG
    Why
    The outlet label named the copy's host, not the publisher; corrected to WTTG, the page's provider field as read on 2026-10-09 (the page did not answer now) (the editor's batch trust-fixes-1009 of 2026-10-09).

  1797. · a record · the outlet of a news item

    Before
    Yahoo Finance
    After
    Zacks
    Why
    The outlet label named the copy's host, not the publisher; corrected to Zacks, the page's provider field as read on 2026-10-09 (the page did not answer now) (the editor's batch trust-fixes-1009 of 2026-10-09).

  1798. · a record · the outlet of a news item

    Before
    yahoo.com
    After
    The Cool Down
    Why
    The outlet label named the copy's host, not the publisher; corrected to The Cool Down, the page's provider field as read on 2026-10-09 (the page did not answer now) (the editor's batch trust-fixes-1009 of 2026-10-09).

  1799. · a record · the outlet of a news item

    Before
    localsyr.com
    After
    WSYR Syracuse
    Why
    The outlet label named the copy's host, not the publisher; corrected to WSYR Syracuse, the page's own provider field, read now (the editor's batch trust-fixes-1009 of 2026-10-09).

  1800. · a record · the outlet of a news item

    Before
    Yahoo
    After
    Kiplinger
    Why
    The outlet label named the copy's host, not the publisher; corrected to Kiplinger, the page's provider field as read on 2026-10-09 (the page did not answer now) (the editor's batch trust-fixes-1009 of 2026-10-09).

  1801. · a record · the outlet of a news item

    Before
    Yahoo
    After
    Fox News
    Why
    The outlet label named the copy's host, not the publisher; corrected to Fox News, the url is on the publisher's own site (the editor's batch trust-fixes-1009 of 2026-10-09).

  1802. · a record · the outlet of a news item

    Before
    Yahoo
    After
    WTVR
    Why
    The outlet label named the copy's host, not the publisher; corrected to WTVR, the page's provider field as read on 2026-10-09 (the page did not answer now) (the editor's batch trust-fixes-1009 of 2026-10-09).

  1803. · a record · the outlet of a news item

    Before
    Yahoo
    After
    The Cool Down
    Why
    The outlet label named the copy's host, not the publisher; corrected to The Cool Down, the url is on the publisher's own site (the editor's batch trust-fixes-1009 of 2026-10-09).

  1804. · a record · the outlet of a news item

    Before
    Yahoo
    After
    Backyard Garden Lover
    Why
    The outlet label named the copy's host, not the publisher; corrected to Backyard Garden Lover, the page's provider field as read on 2026-10-09 (the page did not answer now) (the editor's batch trust-fixes-1009 of 2026-10-09).

  1805. · Loudoun County · the moratorium step of a scorecard event

    Before
    After
    adopted
    Why
    The board voted to pause data center applications for 12 months, effective immediately; the step adopted on the editor's word (the editor's batch trust-fixes-1009 of 2026-10-09), so the county's pause count reads it.

  1806. · Loudoun County · the duplicate mark of a scorecard event

    Before
    1836
    After
    Why
    The vote to pause applications is its own act, not a repeat of the vote to direct staff; it stands on its own on the editor's word (the editor's batch trust-fixes-1009 of 2026-10-09).

  1807. · Box Elder County · the duplicate mark of a scorecard event

    Before
    935
    After
    5
    Why
    The event repeats the county's own June 10 moratorium as the Clearfield story reported it, dated to that story; marked a duplicate of event 5 with the story kept as a citation there, on the editor's word (the editor's batch trust-fixes-1009 of 2026-10-09). An act is filed on the row of the body that took it, so it does not move to the Clearfield City row.

  1808. · Box Elder County · the duplicate mark of a scorecard event

    Before
    After
    5
    Why
    The event repeats the county's own June 10 moratorium as the Clearfield story reported it, dated to that story; marked a duplicate of event 5 with the story kept as a citation there, on the editor's word (the editor's batch trust-fixes-1009 of 2026-10-09). An act is filed on the row of the body that took it, so it does not move to the Clearfield City row.

  1809. · Stratos Project · the record link of a statement

    Before
    stratos-box-elder-ut
    After
    Why
    The statement is about Clearfield's zoning, not the Stratos record; detached on the editor's word (the editor's batch trust-fixes-1009 of 2026-10-09).

  1810. · Mark Shepherd · the scorecard row of a statement

    Before
    After
    ut/clearfield-city
    Why
    Filed on the Clearfield City row: the mayor speaks of the city's own zones; on the editor's word (the editor's batch trust-fixes-1009 of 2026-10-09).

  1811. · the reason of 13 corrections

    Before
    Jordan's batch trust-fixes-1009
    After
    the editor's batch trust-fixes-1009
    Why
    The record's rules: a correction reason names no person; the batch label in these reasons rewritten once (docs/batch-trust-fixes-1010.md).

  1812. · a record · the scorecard row of a scorecard event

    Before
    MI/ypsilanti-township
    After
    MI/michigan
    Why
    The hearing is the Michigan Department of Environment, Great Lakes, and Energy's, on a Saline Township permit; the row was Ypsilanti Township's, which the sentence does not name. Moved to Michigan's own row, the body's, on the editor's word (docs/batch-trust-fixes-1010.md); the Saline Township row is a draft.

  1813. · a statement · the state of a statement

    Before
    UT
    After
    TX
    Why
    Filed under Texas: the claim's own words describe that state, not Utah; on the editor's word (the editor's batch trust-fixes-1009 of 2026-10-09).

  1814. · TRG Datacenters · the state of a statement

    Before
    UT
    After
    VA
    Why
    Filed under Virginia: the claim's own words describe that state, not Utah; on the editor's word (the editor's batch trust-fixes-1009 of 2026-10-09).

  1815. · Sherrod Brown · the state of a statement

    Before
    UT
    After
    OH
    Why
    Filed under Ohio: the speaker holds office there and the statement is about that office's own ground; on the editor's word (the editor's batch trust-fixes-1009 of 2026-10-09). It stays attached to the Stratos record it was reported beside.

  1816. · Josh Shapiro · the state of a statement

    Before
    UT
    After
    PA
    Why
    Filed under Pennsylvania: the speaker holds office there and the statement is about that office's own ground; on the editor's word (the editor's batch trust-fixes-1009 of 2026-10-09). It stays attached to the Stratos record it was reported beside.

  1817. · Gina Hinojosa · the state of a statement

    Before
    UT
    After
    TX
    Why
    Filed under Texas: the speaker holds office there and the statement is about that office's own ground; on the editor's word (the editor's batch trust-fixes-1009 of 2026-10-09). It stays attached to the Stratos record it was reported beside.

  1818. · Greg Abbott · the state of a statement

    Before
    UT
    After
    TX
    Why
    Filed under Texas: the speaker holds office there and the statement is about that office's own ground; on the editor's word (the editor's batch trust-fixes-1009 of 2026-10-09). It stays attached to the Stratos record it was reported beside.

  1819. · a record · the place of a figure

    Before
    Box Elder County, UT
    After
    Delta, Millard County, UT
    Why
    Moved to Delta, Millard County, UT: the figure's own words name the Creekstone Energy project in Millard County, and the record carries that project at Delta; a figure sits on the place it describes, on the editor's word (the editor's batch trust-fixes-1009 of 2026-10-09).

  1820. · a record · the place of a figure

    Before
    Box Elder County, UT
    After
    Delta, Millard County, UT
    Why
    Moved to Delta, Millard County, UT: the figure's own words name the Creekstone Energy project in Millard County, and the record carries that project at Delta; a figure sits on the place it describes, on the editor's word (the editor's batch trust-fixes-1009 of 2026-10-09).

  1821. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Taken off Stratos and Box Elder County: the figure's own words describe another place (A May Gallup survey found that 71% of Americans oppose building data centers in…) and it is a comparison made in the article, not a figure on the record; on the editor's word (the editor's batch trust-fixes-1009 of 2026-10-09). The row stays and can be published again.

  1822. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Taken off Stratos and Box Elder County: the figure's own words describe another place (O'Leary Digital is also building a 70 billion dollar AI data center in Alberta,…) and it is a comparison made in the article, not a figure on the record; on the editor's word (the editor's batch trust-fixes-1009 of 2026-10-09). The row stays and can be published again.

  1823. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Taken off Stratos and Box Elder County: the figure's own words describe another place (Kevin O'Leary stated the entire state of Utah consumes about 4 gigawatts of pow…) and it is a comparison made in the article, not a figure on the record; on the editor's word (the editor's batch trust-fixes-1009 of 2026-10-09). The row stays and can be published again.

  1824. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Taken off Stratos and Box Elder County: the figure's own words describe another place (Loudoun County data centers combined use 6 gigawatts of power.) and it is a comparison made in the article, not a figure on the record; on the editor's word (the editor's batch trust-fixes-1009 of 2026-10-09). The row stays and can be published again.

  1825. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Taken off Stratos and Box Elder County: the figure's own words describe another place (New York City uses 10.4 gigawatts during the hottest summer months) and it is a comparison made in the article, not a figure on the record; on the editor's word (the editor's batch trust-fixes-1009 of 2026-10-09). The row stays and can be published again.

  1826. · DataBank Minneapolis data center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    the record's rules: the entry describes the Eagan building (MSP2, 3255 Neil Armstrong Boulevard, Dakota County) and sat on the Minneapolis record; returned to draft on the editor's word, and the Eagan record carries the acquisition

  1827. · a statement · the state of a statement

    Before
    AZ
    After
    WI
    Why
    Filed under Wisconsin: the speaker's office is in Wisconsin, the row is filed under Arizona; a statement is filed under its speaker's state, as the site already read it (the trust fixes of 2026-10-08).

  1828. · John Fetterman · the state of a statement

    Before
    NY
    After
    PA
    Why
    Filed under Pennsylvania: the speaker's office is in Pennsylvania, the row is filed under New York; a statement is filed under its speaker's state, as the site already read it (the trust fixes of 2026-10-08).

  1829. · a statement · the state of a statement

    Before
    NC
    After
    CO
    Why
    Filed under Colorado: the speaker's office is in Colorado, the row is filed under North Carolina; a statement is filed under its speaker's state, as the site already read it (the trust fixes of 2026-10-08).

  1830. · John Fetterman · the state of a statement

    Before
    NY
    After
    PA
    Why
    Filed under Pennsylvania: the speaker's office is in Pennsylvania, the row is filed under New York; a statement is filed under its speaker's state, as the site already read it (the trust fixes of 2026-10-08).

  1831. · Bernie Moreno · the state of a statement

    Before
    CO
    After
    OH
    Why
    Filed under Ohio: the speaker's office is in Ohio, the row is filed under Colorado; a statement is filed under its speaker's state, as the site already read it (the trust fixes of 2026-10-08).

  1832. · Jon Husted · the state of a statement

    Before
    TX
    After
    OH
    Why
    Filed under Ohio: the speaker's office is in Ohio, the row is filed under Texas; a statement is filed under its speaker's state, as the site already read it (the trust fixes of 2026-10-08).

  1833. · Mark Kelly · the state of a statement

    Before
    MD
    After
    AZ
    Why
    Filed under Arizona: the speaker's office is in Arizona, the row is filed under Maryland; a statement is filed under its speaker's state, as the site already read it (the trust fixes of 2026-10-08).

  1834. · Martin Heinrich · the state of a statement

    Before
    OH
    After
    NM
    Why
    Filed under New Mexico: the speaker's office is in New Mexico, the row is filed under Ohio; a statement is filed under its speaker's state, as the site already read it (the trust fixes of 2026-10-08).

  1835. · a statement · the state of a statement

    Before
    KS
    After
    CO
    Why
    Filed under Colorado: the speaker's office is in Colorado, the row is filed under Kansas; a statement is filed under its speaker's state, as the site already read it (the trust fixes of 2026-10-08).

  1836. · Ralph Norman · the state of a statement

    Before
    TX
    After
    SC
    Why
    Filed under South Carolina: the speaker's office is in South Carolina, the row is filed under Texas; a statement is filed under its speaker's state, as the site already read it (the trust fixes of 2026-10-08).

  1837. · Michael Turner · the state of a statement

    Before
    NY
    After
    VA
    Why
    Filed under Virginia: the speaker's office is in Virginia, the row is filed under New York; a statement is filed under its speaker's state, as the site already read it (the trust fixes of 2026-10-08).

  1838. · a statement · the state of a statement

    Before
    VA
    After
    FL
    Why
    Filed under Florida: the speaker's office is in Florida, the row is filed under Virginia; a statement is filed under its speaker's state, as the site already read it (the trust fixes of 2026-10-08).

  1839. · a statement · the state of a statement

    Before
    WV
    After
    OH
    Why
    Filed under Ohio: the speaker's office is in Ohio, the row is filed under West Virginia; a statement is filed under its speaker's state, as the site already read it (the trust fixes of 2026-10-08).

  1840. · Martin Heinrich · the state of a statement

    Before
    UT
    After
    NM
    Why
    Filed under New Mexico: the speaker's office is in New Mexico, the row is filed under Utah; a statement is filed under its speaker's state, as the site already read it (the trust fixes of 2026-10-08).

  1841. · Ken Paxton · the state of a statement

    Before
    MI
    After
    TX
    Why
    Filed under Texas: the speaker's office is in Texas, the row is filed under Michigan; a statement is filed under its speaker's state, as the site already read it (the trust fixes of 2026-10-08).

  1842. · Jon Husted · the state of a statement

    Before
    MI
    After
    OH
    Why
    Filed under Ohio: the speaker's office is in Ohio, the row is filed under Michigan; a statement is filed under its speaker's state, as the site already read it (the trust fixes of 2026-10-08).

  1843. · Ro Khanna · the state of a statement

    Before
    TX
    After
    CA
    Why
    Filed under California: the speaker's office is in California, the row is filed under Texas; a statement is filed under its speaker's state, as the site already read it (the trust fixes of 2026-10-08).

  1844. · Jon Husted · the state of a statement

    Before
    CO
    After
    OH
    Why
    Filed under Ohio: the speaker's office is in Ohio, the row is filed under Colorado; a statement is filed under its speaker's state, as the site already read it (the trust fixes of 2026-10-08).

  1845. · Abdul El-Sayed · the state of a statement

    Before
    US
    After
    MI
    Why
    Filed under Michigan: the speaker's office is in Michigan, the row is filed under US; a statement is filed under its speaker's state, as the site already read it (the trust fixes of 2026-10-08).

  1846. · Josh Shapiro · the state of a statement

    Before
    MD
    After
    PA
    Why
    Filed under Pennsylvania: the speaker's office is in Pennsylvania, the row is filed under Maryland; a statement is filed under its speaker's state, as the site already read it (the trust fixes of 2026-10-08).

  1847. · Greg Abbott · the state of a statement

    Before
    MI
    After
    TX
    Why
    Filed under Texas: the speaker's office is in Texas, the row is filed under Michigan; a statement is filed under its speaker's state, as the site already read it (the trust fixes of 2026-10-08).

  1848. · Haley Stevens · the state of a statement

    Before
    TX
    After
    MI
    Why
    Filed under Michigan: the speaker's office is in Michigan, the row is filed under Texas; a statement is filed under its speaker's state, as the site already read it (the trust fixes of 2026-10-08).

  1849. · Tom Tiffany · the state of a statement

    Before
    MI
    After
    WI
    Why
    Filed under Wisconsin: the speaker's office is in Wisconsin, the row is filed under Michigan; a statement is filed under its speaker's state, as the site already read it (the trust fixes of 2026-10-08).

  1850. · Erin Brockovich · the state of a statement

    Before
    NY
    After
    TN
    Why
    Filed under Tennessee: the speaker's office is in Tennessee, the row is filed under New York; a statement is filed under its speaker's state, as the site already read it (the trust fixes of 2026-10-08).

  1851. · Michael Rulli · the state of a statement

    Before
    NH
    After
    OH
    Why
    Filed under Ohio: the speaker's office is in Ohio, the row is filed under New Hampshire; a statement is filed under its speaker's state, as the site already read it (the trust fixes of 2026-10-08).

  1852. · Jonathan Jackson · the state of a statement

    Before
    TX
    After
    IL
    Why
    Filed under Illinois: the speaker's office is in Illinois, the row is filed under Texas; a statement is filed under its speaker's state, as the site already read it (the trust fixes of 2026-10-08).

  1853. · Nancy Mace · the state of a statement

    Before
    TX
    After
    SC
    Why
    Filed under South Carolina: the speaker's office is in South Carolina, the row is filed under Texas; a statement is filed under its speaker's state, as the site already read it (the trust fixes of 2026-10-08).

  1854. · a statement · the state of a statement

    Before
    MI
    After
    PA
    Why
    Filed under Pennsylvania: the speaker's office is in Pennsylvania, the row is filed under Michigan; a statement is filed under its speaker's state, as the site already read it (the trust fixes of 2026-10-08).

  1855. · Byron Donalds · the state of a statement

    Before
    OH
    After
    FL
    Why
    Filed under Florida: the speaker's office is in Florida, the row is filed under Ohio; a statement is filed under its speaker's state, as the site already read it (the trust fixes of 2026-10-08).

  1856. · Katie Britt · the state of a statement

    Before
    US
    After
    AL
    Why
    Filed under Alabama: the speaker's office is in Alabama, the row is filed under US; a statement is filed under its speaker's state, as the site already read it (the trust fixes of 2026-10-08).

  1857. · Gavin Newsom · the state of a statement

    Before
    TX
    After
    CA
    Why
    Filed under California: the speaker's office is in California, the row is filed under Texas; a statement is filed under its speaker's state, as the site already read it (the trust fixes of 2026-10-08).

  1858. · Gabe Evans · the state of a statement

    Before
    VA
    After
    CO
    Why
    Filed under Colorado: the speaker's office is in Colorado, the row is filed under Virginia; a statement is filed under its speaker's state, as the site already read it (the trust fixes of 2026-10-08).

  1859. · Michael Whatley · the state of a statement

    Before
    NH
    After
    NC
    Why
    Filed under North Carolina: the speaker's office is in North Carolina, the row is filed under New Hampshire; a statement is filed under its speaker's state, as the site already read it (the trust fixes of 2026-10-08).

  1860. · a statement · the state of a statement

    Before
    NY
    After
    TX
    Why
    Filed under Texas: the speaker's office is in Texas, the row is filed under New York; a statement is filed under its speaker's state, as the site already read it (the trust fixes of 2026-10-08).

  1861. · Kathy Castor · the state of a statement

    Before
    NC
    After
    FL
    Why
    Filed under Florida: the speaker's office is in Florida, the row is filed under North Carolina; a statement is filed under its speaker's state, as the site already read it (the trust fixes of 2026-10-08).

  1862. · John Fetterman · the state of a statement

    Before
    NY
    After
    PA
    Why
    Filed under Pennsylvania: the speaker's office is in Pennsylvania, the row is filed under New York; a statement is filed under its speaker's state, as the site already read it (the trust fixes of 2026-10-08).

  1863. · Wes Moore · the state of a statement

    Before
    VA
    After
    MD
    Why
    Filed under Maryland: the speaker's office is in Maryland, the row is filed under Virginia; a statement is filed under its speaker's state, as the site already read it (the trust fixes of 2026-10-08).

  1864. · Tom Tiffany · the state of a statement

    Before
    MD
    After
    WI
    Why
    Filed under Wisconsin: the speaker's office is in Wisconsin, the row is filed under Maryland; a statement is filed under its speaker's state, as the site already read it (the trust fixes of 2026-10-08).

  1865. · Rich McCormick · the state of a statement

    Before
    TX
    After
    GA
    Why
    Filed under Georgia: the speaker's office is in Georgia, the row is filed under Texas; a statement is filed under its speaker's state, as the site already read it (the trust fixes of 2026-10-08).

  1866. · Gabe Evans · the state of a statement

    Before
    VA
    After
    CO
    Why
    Filed under Colorado: the speaker's office is in Colorado, the row is filed under Virginia; a statement is filed under its speaker's state, as the site already read it (the trust fixes of 2026-10-08).

  1867. · Martin Heinrich · the state of a statement

    Before
    CO
    After
    NM
    Why
    Filed under New Mexico: the speaker's office is in New Mexico, the row is filed under Colorado; a statement is filed under its speaker's state, as the site already read it (the trust fixes of 2026-10-08).

  1868. · Vivek Ramaswamy · the state of a statement

    Before
    MI
    After
    OH
    Why
    Filed under Ohio: the speaker's office is in Ohio, the row is filed under Michigan; a statement is filed under its speaker's state, as the site already read it (the trust fixes of 2026-10-08).

  1869. · Dave McCormick · the state of a statement

    Before
    NY
    After
    PA
    Why
    Filed under Pennsylvania: the speaker's office is in Pennsylvania, the row is filed under New York; a statement is filed under its speaker's state, as the site already read it (the trust fixes of 2026-10-08).

  1870. · Raphael Warnock · the state of a statement

    Before
    TX
    After
    GA
    Why
    Filed under Georgia: the speaker's office is in Georgia, the row is filed under Texas; a statement is filed under its speaker's state, as the site already read it (the trust fixes of 2026-10-08).

  1871. · Ro Khanna · the state of a statement

    Before
    US
    After
    CA
    Why
    Filed under California: the speaker's office is in California, the row is filed under US; a statement is filed under its speaker's state, as the site already read it (the trust fixes of 2026-10-08).

  1872. · Dave McCormick · the state of a statement

    Before
    NY
    After
    PA
    Why
    Filed under Pennsylvania: the speaker's office is in Pennsylvania, the row is filed under New York; a statement is filed under its speaker's state, as the site already read it (the trust fixes of 2026-10-08).

  1873. · Doug Fiefia · the state of a statement

    Before
    AZ
    After
    UT
    Why
    Filed under Utah: the speaker's office is in Utah, the row is filed under Arizona; a statement is filed under its speaker's state, as the site already read it (the trust fixes of 2026-10-08).

  1874. · Martin Heinrich · the state of a statement

    Before
    UT
    After
    NM
    Why
    Filed under New Mexico: the speaker's office is in New Mexico, the row is filed under Utah; a statement is filed under its speaker's state, as the site already read it (the trust fixes of 2026-10-08).

  1875. · Yassamin Ansari · the state of a statement

    Before
    TX
    After
    AZ
    Why
    Filed under Arizona: the speaker's office is in Arizona, the row is filed under Texas; a statement is filed under its speaker's state, as the site already read it (the trust fixes of 2026-10-08).

  1876. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Taken off as reported: its words names the country, not the place it sits on, and its own words are not about data centers, so it is a comparison with somewhere else and not a figure on the record it sat on (the trust fixes of 2026-10-08). The row stays and can be published again.

  1877. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Taken off Ohio, statewide: its words names the country, not the place it sits on, and its own words are not about data centers, so it is a comparison with somewhere else and not a figure on the record it sat on (the trust fixes of 2026-10-08). The row stays and can be published again.

  1878. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Taken off Iowa, United States: its words names the country, not the place it sits on, and its own words are not about data centers, so it is a comparison with somewhere else and not a figure on the record it sat on (the trust fixes of 2026-10-08). The row stays and can be published again.

  1879. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Taken off Texas, TX: its words names the country, not the place it sits on, and its own words are not about data centers, so it is a comparison with somewhere else and not a figure on the record it sat on (the trust fixes of 2026-10-08). The row stays and can be published again.

  1880. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Taken off Richmond County, NC: its words names the country, not the place it sits on, and its own words are not about data centers, so it is a comparison with somewhere else and not a figure on the record it sat on (the trust fixes of 2026-10-08). The row stays and can be published again.

  1881. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Taken off NJ: its words names the country, not the place it sits on, and its own words are not about data centers, so it is a comparison with somewhere else and not a figure on the record it sat on (the trust fixes of 2026-10-08). The row stays and can be published again.

  1882. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Taken off UT: its words names the country, not the place it sits on, and its own words are not about data centers, so it is a comparison with somewhere else and not a figure on the record it sat on (the trust fixes of 2026-10-08). The row stays and can be published again.

  1883. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Taken off Beaver County, UT: its words names the country, not the place it sits on, and its own words are not about data centers, so it is a comparison with somewhere else and not a figure on the record it sat on (the trust fixes of 2026-10-08). The row stays and can be published again.

  1884. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Taken off Delta, Millard County, UT: its words names the whole of Utah, not Delta, and its own words are not about data centers, so it is a comparison with somewhere else and not a figure on the record it sat on (the trust fixes of 2026-10-08). The row stays and can be published again.

  1885. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Taken off CA: its words names the country, not the place it sits on, and its own words are not about data centers, so it is a comparison with somewhere else and not a figure on the record it sat on (the trust fixes of 2026-10-08). The row stays and can be published again.

  1886. · a record · the place of a figure

    Before
    ME
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1887. · a record · the place of a figure

    Before
    ME
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1888. · a record · the place of a figure

    Before
    Georgia, statewide
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1889. · a record · the place of a figure

    Before
    Georgia, statewide
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1890. · a record · the place of a figure

    Before
    Texas, United States
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1891. · a record · the place of a figure

    Before
    Texas, United States
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1892. · a record · the place of a figure

    Before
    Santa Clara County, CA
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1893. · a record · the place of a figure

    Before
    Santa Clara County, CA
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1894. · a record · the place of a figure

    Before
    Utah, statewide
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1895. · a record · the place of a figure

    Before
    Utah, statewide
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1896. · a record · the place of a figure

    Before
    Montana, statewide
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1897. · a record · the place of a figure

    Before
    Montana, statewide
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1898. · a record · the place of a figure

    Before
    North Carolina
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1899. · a record · the place of a figure

    Before
    North Carolina
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1900. · a record · the place of a figure

    Before
    Ohio, OH
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1901. · a record · the place of a figure

    Before
    Ohio, OH
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1902. · a record · the place of a figure

    Before
    NY
    After
    Texas, statewide
    Why
    Moved to Texas, statewide: the figure's own words names Texas, not New York; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1903. · a record · the place of a figure

    Before
    NY
    After
    Texas, statewide
    Why
    Moved to Texas, statewide: the figure's own words names Texas, not New York; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1904. · a record · the place of a figure

    Before
    Missouri
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1905. · a record · the place of a figure

    Before
    Missouri
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1906. · a record · the place of a figure

    Before
    Gage County, NE
    After
    Cheyenne, Laramie County, WY
    Why
    Moved to Cheyenne, Laramie County, WY: the figure's own words name Cheyenne, Wyoming, which has a page; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1907. · a record · the place of a figure

    Before
    Gage County, NE
    After
    Cheyenne, Laramie County, WY
    Why
    Moved to Cheyenne, Laramie County, WY: the figure's own words name Cheyenne, Wyoming, which has a page; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1908. · a record · the place of a figure

    Before
    Utah, statewide
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1909. · a record · the place of a figure

    Before
    Utah, statewide
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1910. · a record · the place of a figure

    Before
    Virginia, statewide
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1911. · a record · the place of a figure

    Before
    Virginia, statewide
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1912. · a record · the place of a figure

    Before
    Texas, TX
    After
    Virginia, statewide
    Why
    Moved to Virginia, statewide: the figure's own words names Virginia, not Texas; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1913. · a record · the place of a figure

    Before
    Texas, TX
    After
    Virginia, statewide
    Why
    Moved to Virginia, statewide: the figure's own words names Virginia, not Texas; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1914. · a record · the place of a figure

    Before
    Santa Clara County, CA
    After
    Loudoun County, VA
    Why
    Moved to Loudoun County, VA: the figure's own words names Virginia (Loudoun County), not California; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1915. · a record · the place of a figure

    Before
    Santa Clara County, CA
    After
    Loudoun County, VA
    Why
    Moved to Loudoun County, VA: the figure's own words names Virginia (Loudoun County), not California; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1916. · a record · the place of a figure

    Before
    OH
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1917. · a record · the place of a figure

    Before
    OH
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1918. · a record · the place of a figure

    Before
    KS
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1919. · a record · the place of a figure

    Before
    KS
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1920. · a record · the place of a figure

    Before
    Colorado River basin (Colorado, Utah, Arizona, Nevada, California, New Mexico)
    After
    Nevada, statewide
    Why
    Moved to Nevada, statewide: the figure's own words names Nevada, not Utah; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1921. · a record · the place of a figure

    Before
    Colorado River basin (Colorado, Utah, Arizona, Nevada, California, New Mexico)
    After
    Nevada, statewide
    Why
    Moved to Nevada, statewide: the figure's own words names Nevada, not Utah; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1922. · a record · the place of a figure

    Before
    Grant County and Lea County, NM
    After
    Lea County, NM
    Why
    Moved to Lea County, NM: the figure's own words names Lea County, not Grant County and Lea County; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1923. · a record · the place of a figure

    Before
    Grant County and Lea County, NM
    After
    Lea County, NM
    Why
    Moved to Lea County, NM: the figure's own words names Lea County, not Grant County and Lea County; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1924. · a record · the place of a figure

    Before
    California, Virginia, Texas, Illinois, Georgia, Ohio, Arizona, statewide
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1925. · a record · the place of a figure

    Before
    California, Virginia, Texas, Illinois, Georgia, Ohio, Arizona, statewide
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1926. · a record · the place of a figure

    Before
    KS
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1927. · a record · the place of a figure

    Before
    KS
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1928. · a record · the place of a figure

    Before
    Louisiana, Loudoun County Virginia, Montgomery County Missouri, statewide
    After
    Montgomery County, MO
    Why
    Moved to Montgomery County, MO: the figure's own words names Missouri (Montgomery County), not Louisiana; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1929. · a record · the place of a figure

    Before
    Louisiana, Loudoun County Virginia, Montgomery County Missouri, statewide
    After
    Montgomery County, MO
    Why
    Moved to Montgomery County, MO: the figure's own words names Missouri (Montgomery County), not Louisiana; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1930. · a record · the place of a figure

    Before
    Huntsville, AL
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1931. · a record · the place of a figure

    Before
    Huntsville, AL
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1932. · a record · the place of a figure

    Before
    CT
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1933. · a record · the place of a figure

    Before
    CT
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1934. · a record · the place of a figure

    Before
    OR
    After
    Virginia, statewide
    Why
    Moved to Virginia, statewide: the figure's own words names Virginia, not Oregon; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1935. · a record · the place of a figure

    Before
    OR
    After
    Virginia, statewide
    Why
    Moved to Virginia, statewide: the figure's own words names Virginia, not Oregon; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1936. · a record · the place of a figure

    Before
    Texas, TX
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1937. · a record · the place of a figure

    Before
    Texas, TX
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1938. · a record · the place of a figure

    Before
    Mississippi, Arkansas, Louisiana
    After
    Louisiana, statewide
    Why
    Moved to Louisiana, statewide: the figure's own words names Louisiana, not Mississippi; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1939. · a record · the place of a figure

    Before
    Mississippi, Arkansas, Louisiana
    After
    Louisiana, statewide
    Why
    Moved to Louisiana, statewide: the figure's own words names Louisiana, not Mississippi; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1940. · a record · the place of a figure

    Before
    Nevada, statewide
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1941. · a record · the place of a figure

    Before
    Nevada, statewide
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1942. · a record · the place of a figure

    Before
    Florida, statewide
    After
    Loudoun County, VA
    Why
    Moved to Loudoun County, VA: the figure's own words names Virginia (Loudoun County), not Florida; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1943. · a record · the place of a figure

    Before
    Florida, statewide
    After
    Loudoun County, VA
    Why
    Moved to Loudoun County, VA: the figure's own words names Virginia (Loudoun County), not Florida; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1944. · a record · the place of a figure

    Before
    Lake Mariner, New York; Richland Parish, Louisiana
    After
    Louisiana, statewide
    Why
    Moved to Louisiana, statewide: the figure's own words names Louisiana, not New York; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1945. · a record · the place of a figure

    Before
    Lake Mariner, New York; Richland Parish, Louisiana
    After
    Louisiana, statewide
    Why
    Moved to Louisiana, statewide: the figure's own words names Louisiana, not New York; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1946. · a record · the place of a figure

    Before
    Nevada, statewide
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1947. · a record · the place of a figure

    Before
    Nevada, statewide
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1948. · a record · the place of a figure

    Before
    Sherwood, Saskatchewan
    After
    Alberta, statewide
    Why
    Moved to Alberta, statewide: the figure's own words names Alberta, not Saskatchewan; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1949. · a record · the place of a figure

    Before
    Sherwood, Saskatchewan
    After
    Alberta, statewide
    Why
    Moved to Alberta, statewide: the figure's own words names Alberta, not Saskatchewan; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1950. · a record · the place of a figure

    Before
    Minnesota, MN
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1951. · a record · the place of a figure

    Before
    Minnesota, MN
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1952. · a record · the place of a figure

    Before
    Mississippi, Arkansas, Louisiana
    After
    Louisiana, statewide
    Why
    Moved to Louisiana, statewide: the figure's own words names Louisiana, not Mississippi; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1953. · a record · the place of a figure

    Before
    Mississippi, Arkansas, Louisiana
    After
    Louisiana, statewide
    Why
    Moved to Louisiana, statewide: the figure's own words names Louisiana, not Mississippi; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1954. · a record · the place of a figure

    Before
    Kentucky, statewide
    After
    Indiana, statewide
    Why
    Moved to Indiana, statewide: the figure's own words names Indiana, not Kentucky; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1955. · a record · the place of a figure

    Before
    Kentucky, statewide
    After
    Indiana, statewide
    Why
    Moved to Indiana, statewide: the figure's own words names Indiana, not Kentucky; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1956. · a record · the place of a figure

    Before
    Illinois, statewide
    After
    Maryland, statewide
    Why
    Moved to Maryland, statewide: the figure's own words names Maryland, not Illinois; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1957. · a record · the place of a figure

    Before
    Illinois, statewide
    After
    Maryland, statewide
    Why
    Moved to Maryland, statewide: the figure's own words names Maryland, not Illinois; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1958. · a record · the place of a figure

    Before
    Missouri, MO
    After
    Minnesota, statewide
    Why
    Moved to Minnesota, statewide: the figure's own words names Minnesota, not Missouri; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1959. · a record · the place of a figure

    Before
    Missouri, MO
    After
    Minnesota, statewide
    Why
    Moved to Minnesota, statewide: the figure's own words names Minnesota, not Missouri; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1960. · a record · the place of a figure

    Before
    Pinal County, AZ
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1961. · a record · the place of a figure

    Before
    Pinal County, AZ
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1962. · a record · the place of a figure

    Before
    Pennsylvania and Texas, multi-state
    After
    Georgia, statewide
    Why
    Moved to Georgia, statewide: the figure's own words names Georgia, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1963. · a record · the place of a figure

    Before
    KS
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1964. · a record · the place of a figure

    Before
    KS
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1965. · a record · the place of a figure

    Before
    Utah, statewide
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1966. · a record · the place of a figure

    Before
    Utah, statewide
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1967. · a record · the place of a figure

    Before
    Posey County, IN
    After
    Quincy, Grant County, WA
    Why
    Moved to Quincy, Grant County, WA: the figure's own words name Quincy, Washington, which has a page; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1968. · a record · the place of a figure

    Before
    Posey County, IN
    After
    Quincy, Grant County, WA
    Why
    Moved to Quincy, Grant County, WA: the figure's own words name Quincy, Washington, which has a page; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1969. · a record · the place of a figure

    Before
    Gary, Indiana, Lake County, IN
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1970. · a record · the place of a figure

    Before
    Gary, Indiana, Lake County, IN
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1971. · a record · the place of a figure

    Before
    Pennsylvania and Texas, multi-state
    After
    Texas, statewide
    Why
    Moved to Texas, statewide: the figure's own words names Texas, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1972. · a record · the place of a figure

    Before
    UT
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1973. · a record · the place of a figure

    Before
    UT
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1974. · a record · the place of a figure

    Before
    Dorchester County and Berkeley County, SC
    After
    Dorchester County, SC
    Why
    Moved to Dorchester County, SC: the figure's own words names Dorchester County, not Dorchester County and Berkeley County; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1975. · a record · the place of a figure

    Before
    Dorchester County and Berkeley County, SC
    After
    Dorchester County, SC
    Why
    Moved to Dorchester County, SC: the figure's own words names Dorchester County, not Dorchester County and Berkeley County; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1976. · a record · the place of a figure

    Before
    Utah, statewide
    After
    Ohio, statewide
    Why
    Moved to Ohio, statewide: the figure's own words names Ohio, not Utah; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1977. · a record · the place of a figure

    Before
    Utah, statewide
    After
    Ohio, statewide
    Why
    Moved to Ohio, statewide: the figure's own words names Ohio, not Utah; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1978. · a record · the place of a figure

    Before
    Santa Clara County, CA
    After
    Loudoun County, VA
    Why
    Moved to Loudoun County, VA: the figure's own words names Virginia (Loudoun County), not California; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1979. · a record · the place of a figure

    Before
    Santa Clara County, CA
    After
    Loudoun County, VA
    Why
    Moved to Loudoun County, VA: the figure's own words names Virginia (Loudoun County), not California; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1980. · a record · the place of a figure

    Before
    Fairbanks North Star Borough and Anchorage, AK; Healy, AK
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1981. · a record · the place of a figure

    Before
    Fairbanks North Star Borough and Anchorage, AK; Healy, AK
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1982. · a record · the place of a figure

    Before
    NY
    After
    Quincy, Grant County, WA
    Why
    Moved to Quincy, Grant County, WA: the figure's own words name Quincy, Washington, which has a page; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1983. · a record · the place of a figure

    Before
    NY
    After
    Quincy, Grant County, WA
    Why
    Moved to Quincy, Grant County, WA: the figure's own words name Quincy, Washington, which has a page; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1984. · a record · the place of a figure

    Before
    Gary, Indiana, Lake County, IN
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1985. · a record · the place of a figure

    Before
    Gary, Indiana, Lake County, IN
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1986. · a record · the place of a figure

    Before
    Gage County, NE
    After
    Virginia, statewide
    Why
    Moved to Virginia, statewide: the figure's own words names Virginia, not Nebraska; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1987. · a record · the place of a figure

    Before
    Gage County, NE
    After
    Virginia, statewide
    Why
    Moved to Virginia, statewide: the figure's own words names Virginia, not Nebraska; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1988. · a record · the place of a figure

    Before
    Grant County and Lea County, NM
    After
    Lea County, NM
    Why
    Moved to Lea County, NM: the figure's own words names Lea County, not Grant County and Lea County; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1989. · a record · the place of a figure

    Before
    Grant County and Lea County, NM
    After
    Lea County, NM
    Why
    Moved to Lea County, NM: the figure's own words names Lea County, not Grant County and Lea County; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1990. · a record · the place of a figure

    Before
    CA
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1991. · a record · the place of a figure

    Before
    CA
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1992. · a record · the place of a figure

    Before
    Kansas, statewide
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1993. · a record · the place of a figure

    Before
    Kansas, statewide
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1994. · a record · the place of a figure

    Before
    Pennsylvania, statewide
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1995. · a record · the place of a figure

    Before
    Pennsylvania, statewide
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1996. · a record · the place of a figure

    Before
    Kansas, statewide
    After
    Loudoun County, VA
    Why
    Moved to Loudoun County, VA: the figure's own words names Virginia (Loudoun County), not Kansas; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1997. · a record · the place of a figure

    Before
    Kansas, statewide
    After
    Loudoun County, VA
    Why
    Moved to Loudoun County, VA: the figure's own words names Virginia (Loudoun County), not Kansas; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1998. · a record · the place of a figure

    Before
    Claremore, Oklahoma County, OK
    After
    Rogers County, OK
    Why
    Moved to Rogers County, OK: the figure's own words names Rogers County, not Oklahoma County; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  1999. · a record · the place of a figure

    Before
    Claremore, Oklahoma County, OK
    After
    Rogers County, OK
    Why
    Moved to Rogers County, OK: the figure's own words names Rogers County, not Oklahoma County; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2000. · a record · the place of a figure

    Before
    Arizona, statewide
    After
    Utah, statewide
    Why
    Moved to Utah, statewide: the figure's own words name Green River, Utah, a place with no page of its own; the state page carries it; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2001. · a record · the place of a figure

    Before
    Arizona, statewide
    After
    Utah, statewide
    Why
    Moved to Utah, statewide: the figure's own words name Green River, Utah, a place with no page of its own; the state page carries it; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2002. · a record · the place of a figure

    Before
    Nevada, statewide
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2003. · a record · the place of a figure

    Before
    Nevada, statewide
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2004. · a record · the place of a figure

    Before
    Oklahoma, statewide
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2005. · a record · the place of a figure

    Before
    Oklahoma, statewide
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2006. · a record · the place of a figure

    Before
    Mesa, Arizona
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2007. · a record · the place of a figure

    Before
    Mesa, Arizona
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2008. · a record · the place of a figure

    Before
    Woodburn, Marion County, OR
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2009. · a record · the place of a figure

    Before
    Woodburn, Marion County, OR
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2010. · a record · the place of a figure

    Before
    Salix, O'Brien County, IA
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2011. · a record · the place of a figure

    Before
    Salix, O'Brien County, IA
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2012. · a record · the place of a figure

    Before
    AR
    After
    Texas, statewide
    Why
    Moved to Texas, statewide: the figure's own words names Texas, not Arkansas; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2013. · a record · the place of a figure

    Before
    AR
    After
    Texas, statewide
    Why
    Moved to Texas, statewide: the figure's own words names Texas, not Arkansas; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2014. · a record · the place of a figure

    Before
    Pennsylvania and Texas, multi-state
    After
    Texas, statewide
    Why
    Moved to Texas, statewide: the figure's own words names Texas, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2015. · a record · the place of a figure

    Before
    Utah, statewide
    After
    Loudoun County, VA
    Why
    Moved to Loudoun County, VA: the figure's own words names Loudoun County, Virginia; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2016. · a record · the place of a figure

    Before
    Utah, statewide
    After
    Loudoun County, VA
    Why
    Moved to Loudoun County, VA: the figure's own words names Loudoun County, Virginia; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2017. · a record · the place of a figure

    Before
    South Carolina, statewide
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2018. · a record · the place of a figure

    Before
    South Carolina, statewide
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2019. · a record · the place of a figure

    Before
    Gary, Indiana, Lake County, IN
    After
    Virginia, statewide
    Why
    Moved to Virginia, statewide: the figure's own words names Virginia, not Indiana; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2020. · a record · the place of a figure

    Before
    Gary, Indiana, Lake County, IN
    After
    Virginia, statewide
    Why
    Moved to Virginia, statewide: the figure's own words names Virginia, not Indiana; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2021. · a record · the place of a figure

    Before
    MO
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2022. · a record · the place of a figure

    Before
    MO
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2023. · a record · the place of a figure

    Before
    CO
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2024. · a record · the place of a figure

    Before
    CO
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2025. · a record · the place of a figure

    Before
    CA
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2026. · a record · the place of a figure

    Before
    CA
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2027. · a record · the place of a figure

    Before
    Virginia, statewide
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2028. · a record · the place of a figure

    Before
    Virginia, statewide
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2029. · a record · the place of a figure

    Before
    Florida, statewide
    After
    Richland Parish, LA
    Why
    Moved to Richland Parish, LA: the figure's own words names Louisiana (Richland Parish), not Florida; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2030. · a record · the place of a figure

    Before
    Florida, statewide
    After
    Richland Parish, LA
    Why
    Moved to Richland Parish, LA: the figure's own words names Louisiana (Richland Parish), not Florida; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2031. · a record · the place of a figure

    Before
    Multiple states
    After
    Virginia, statewide
    Why
    Moved to Virginia, statewide: the figure's own words names Virginia, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2032. · a record · the place of a figure

    Before
    Multiple states
    After
    Virginia, statewide
    Why
    Moved to Virginia, statewide: the figure's own words names Virginia, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2033. · a record · the place of a figure

    Before
    Santa Clara County, CA
    After
    Maricopa County, AZ
    Why
    Moved to Maricopa County, AZ: the figure's own words names Maricopa County, Arizona; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2034. · a record · the place of a figure

    Before
    Santa Clara County, CA
    After
    Maricopa County, AZ
    Why
    Moved to Maricopa County, AZ: the figure's own words names Maricopa County, Arizona; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2035. · a record · the place of a figure

    Before
    Pennsylvania, statewide
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2036. · a record · the place of a figure

    Before
    Pennsylvania, statewide
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2037. · a record · the place of a figure

    Before
    Kentucky, KY
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2038. · a record · the place of a figure

    Before
    Kentucky, KY
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2039. · a record · the place of a figure

    Before
    KS
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2040. · a record · the place of a figure

    Before
    KS
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2041. · a record · the place of a figure

    Before
    California, Virginia, Texas, Illinois, Georgia, Ohio, Arizona, statewide
    After
    Virginia, statewide
    Why
    Moved to Virginia, statewide: the figure's own words names Virginia, not California; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2042. · a record · the place of a figure

    Before
    California, Virginia, Texas, Illinois, Georgia, Ohio, Arizona, statewide
    After
    Virginia, statewide
    Why
    Moved to Virginia, statewide: the figure's own words names Virginia, not California; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2043. · a record · the place of a figure

    Before
    Orange County, Florida, FL
    After
    Osceola County, FL
    Why
    Moved to Osceola County, FL: the figure's own words names Osceola County, not Orange County; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2044. · a record · the place of a figure

    Before
    Orange County, Florida, FL
    After
    Osceola County, FL
    Why
    Moved to Osceola County, FL: the figure's own words names Osceola County, not Orange County; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2045. · a record · the place of a figure

    Before
    TX
    After
    Ohio, statewide
    Why
    Moved to Ohio, statewide: the figure's own words names Ohio, not Texas; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2046. · a record · the place of a figure

    Before
    TX
    After
    Ohio, statewide
    Why
    Moved to Ohio, statewide: the figure's own words names Ohio, not Texas; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2047. · a record · the place of a figure

    Before
    Arizona, statewide
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2048. · a record · the place of a figure

    Before
    Arizona, statewide
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2049. · a record · the place of a figure

    Before
    Alabama, statewide
    After
    Louisiana, statewide
    Why
    Moved to Louisiana, statewide: the figure's own words names Louisiana, not Alabama; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2050. · a record · the place of a figure

    Before
    Alabama, statewide
    After
    Louisiana, statewide
    Why
    Moved to Louisiana, statewide: the figure's own words names Louisiana, not Alabama; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2051. · a record · the place of a figure

    Before
    Pennsylvania and Texas, multi-state
    After
    Ohio, statewide
    Why
    Moved to Ohio, statewide: the figure's own words names Ohio, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2052. · a record · the place of a figure

    Before
    Utah, statewide
    After
    Virginia, statewide
    Why
    Moved to Virginia, statewide: the figure's own words names Virginia, not Utah; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2053. · a record · the place of a figure

    Before
    Utah, statewide
    After
    Virginia, statewide
    Why
    Moved to Virginia, statewide: the figure's own words names Virginia, not Utah; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2054. · a record · the place of a figure

    Before
    Pima County, Arizona; Loudoun County, Virginia
    After
    Loudoun County, VA
    Why
    Moved to Loudoun County, VA: the figure's own words names Loudoun County, Virginia; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2055. · a record · the place of a figure

    Before
    Pima County, Arizona; Loudoun County, Virginia
    After
    Loudoun County, VA
    Why
    Moved to Loudoun County, VA: the figure's own words names Loudoun County, Virginia; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2056. · a record · the place of a figure

    Before
    AR
    After
    Texas, statewide
    Why
    Moved to Texas, statewide: the figure's own words names Texas, not Arkansas; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2057. · a record · the place of a figure

    Before
    AR
    After
    Texas, statewide
    Why
    Moved to Texas, statewide: the figure's own words names Texas, not Arkansas; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2058. · a record · the place of a figure

    Before
    TX
    After
    Virginia, statewide
    Why
    Moved to Virginia, statewide: the figure's own words names Virginia, not Texas; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2059. · a record · the place of a figure

    Before
    TX
    After
    Virginia, statewide
    Why
    Moved to Virginia, statewide: the figure's own words names Virginia, not Texas; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2060. · a record · the place of a figure

    Before
    Florida, statewide
    After
    New York, statewide
    Why
    Moved to New York, statewide: the figure's own words names New York, not Florida; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2061. · a record · the place of a figure

    Before
    Florida, statewide
    After
    New York, statewide
    Why
    Moved to New York, statewide: the figure's own words names New York, not Florida; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2062. · a record · the place of a figure

    Before
    Utah, UT
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2063. · a record · the place of a figure

    Before
    Utah, UT
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2064. · a record · the place of a figure

    Before
    Montville, Morris County, NJ
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2065. · a record · the place of a figure

    Before
    Montville, Morris County, NJ
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2066. · a record · the place of a figure

    Before
    TX
    After
    Ohio, statewide
    Why
    Moved to Ohio, statewide: the figure's own words names Ohio, not Texas; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2067. · a record · the place of a figure

    Before
    TX
    After
    Ohio, statewide
    Why
    Moved to Ohio, statewide: the figure's own words names Ohio, not Texas; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2068. · a record · the place of a figure

    Before
    NY
    After
    Pennsylvania, statewide
    Why
    Moved to Pennsylvania, statewide: the figure's own words names Pennsylvania, not New York; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2069. · a record · the place of a figure

    Before
    NY
    After
    Pennsylvania, statewide
    Why
    Moved to Pennsylvania, statewide: the figure's own words names Pennsylvania, not New York; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2070. · a record · the place of a figure

    Before
    Missouri, MO
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2071. · a record · the place of a figure

    Before
    Missouri, MO
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2072. · a record · the place of a figure

    Before
    Illinois, statewide
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2073. · a record · the place of a figure

    Before
    Illinois, statewide
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2074. · a record · the place of a figure

    Before
    UT
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2075. · a record · the place of a figure

    Before
    UT
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2076. · a record · the place of a figure

    Before
    Utah, statewide
    After
    Texas, statewide
    Why
    Moved to Texas, statewide: the figure's own words names Texas, not Utah; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2077. · a record · the place of a figure

    Before
    Utah, statewide
    After
    Texas, statewide
    Why
    Moved to Texas, statewide: the figure's own words names Texas, not Utah; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2078. · a record · the place of a figure

    Before
    Montana, statewide
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2079. · a record · the place of a figure

    Before
    Montana, statewide
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2080. · a record · the place of a figure

    Before
    Utah, statewide
    After
    Loudoun County, VA
    Why
    Moved to Loudoun County, VA: the figure's own words names Loudoun County, Virginia; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2081. · a record · the place of a figure

    Before
    Utah, statewide
    After
    Loudoun County, VA
    Why
    Moved to Loudoun County, VA: the figure's own words names Loudoun County, Virginia; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2082. · a record · the place of a figure

    Before
    CA
    After
    Texas, statewide
    Why
    Moved to Texas, statewide: the figure's own words names Texas, not California; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2083. · a record · the place of a figure

    Before
    CA
    After
    Texas, statewide
    Why
    Moved to Texas, statewide: the figure's own words names Texas, not California; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2084. · a record · the place of a figure

    Before
    Texas, statewide
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2085. · a record · the place of a figure

    Before
    Texas, statewide
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2086. · a record · the place of a figure

    Before
    Missouri, Louisiana, statewide; Mississippi River Basin
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2087. · a record · the place of a figure

    Before
    Missouri, Louisiana, statewide; Mississippi River Basin
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2088. · a record · the place of a figure

    Before
    Phoenix, Arizona, Maricopa County, AZ
    After
    Arizona, statewide
    Why
    Moved to Arizona, statewide: the figure's own words names the whole of Arizona, not Phoenix; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2089. · a record · the place of a figure

    Before
    Phoenix, Arizona, Maricopa County, AZ
    After
    Arizona, statewide
    Why
    Moved to Arizona, statewide: the figure's own words names the whole of Arizona, not Phoenix; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2090. · a record · the place of a figure

    Before
    Utah, statewide
    After
    Virginia, statewide
    Why
    Moved to Virginia, statewide: the figure's own words names Virginia, not Utah; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2091. · a record · the place of a figure

    Before
    Utah, statewide
    After
    Virginia, statewide
    Why
    Moved to Virginia, statewide: the figure's own words names Virginia, not Utah; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2092. · a record · the place of a figure

    Before
    Mississippi, Arkansas, Louisiana
    After
    Louisiana, statewide
    Why
    Moved to Louisiana, statewide: the figure's own words names Louisiana, not Mississippi; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2093. · a record · the place of a figure

    Before
    Mississippi, Arkansas, Louisiana
    After
    Louisiana, statewide
    Why
    Moved to Louisiana, statewide: the figure's own words names Louisiana, not Mississippi; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2094. · a record · the place of a figure

    Before
    Texas, TX
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2095. · a record · the place of a figure

    Before
    Texas, TX
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2096. · a record · the place of a figure

    Before
    CA
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2097. · a record · the place of a figure

    Before
    CA
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2098. · a record · the place of a figure

    Before
    Vineland, NJ
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2099. · a record · the place of a figure

    Before
    Vineland, NJ
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2100. · a record · the place of a figure

    Before
    Pennsylvania, statewide
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2101. · a record · the place of a figure

    Before
    Pennsylvania, statewide
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2102. · a record · the place of a figure

    Before
    Ohio, statewide
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2103. · a record · the place of a figure

    Before
    Ohio, statewide
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2104. · a record · the place of a figure

    Before
    Florida, statewide
    After
    Loudoun County, VA
    Why
    Moved to Loudoun County, VA: the figure's own words names Virginia (Loudoun County), not Florida; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2105. · a record · the place of a figure

    Before
    Florida, statewide
    After
    Loudoun County, VA
    Why
    Moved to Loudoun County, VA: the figure's own words names Virginia (Loudoun County), not Florida; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2106. · a record · the place of a figure

    Before
    Louisiana, Loudoun County Virginia, Montgomery County Missouri, statewide
    After
    Loudoun County, VA
    Why
    Moved to Loudoun County, VA: the figure's own words names Loudoun County, Virginia; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2107. · a record · the place of a figure

    Before
    Louisiana, Loudoun County Virginia, Montgomery County Missouri, statewide
    After
    Loudoun County, VA
    Why
    Moved to Loudoun County, VA: the figure's own words names Loudoun County, Virginia; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2108. · a record · the place of a figure

    Before
    Beaver County, UT
    After
    Nevada, statewide
    Why
    Moved to Nevada, statewide: the figure's own words names Nevada, not Utah; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2109. · a record · the place of a figure

    Before
    Beaver County, UT
    After
    Nevada, statewide
    Why
    Moved to Nevada, statewide: the figure's own words names Nevada, not Utah; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2110. · a record · the place of a figure

    Before
    Linden, New Jersey
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2111. · a record · the place of a figure

    Before
    Linden, New Jersey
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2112. · a record · the place of a figure

    Before
    Pima County, Arizona; Loudoun County, Virginia
    After
    Loudoun County, VA
    Why
    Moved to Loudoun County, VA: the figure's own words names Loudoun County, Virginia; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2113. · a record · the place of a figure

    Before
    Pima County, Arizona; Loudoun County, Virginia
    After
    Loudoun County, VA
    Why
    Moved to Loudoun County, VA: the figure's own words names Loudoun County, Virginia; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2114. · a record · the place of a figure

    Before
    Laramie, Albany County, WY
    After
    Pennsylvania, statewide
    Why
    Moved to Pennsylvania, statewide: the figure's own words names Pennsylvania, not Wyoming; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2115. · a record · the place of a figure

    Before
    Laramie, Albany County, WY
    After
    Pennsylvania, statewide
    Why
    Moved to Pennsylvania, statewide: the figure's own words names Pennsylvania, not Wyoming; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2116. · a record · the place of a figure

    Before
    Bahrain and United Arab Emirates
    After
    Louisiana, statewide
    Why
    Moved to Louisiana, statewide: the figure's own words names Louisiana, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2117. · a record · the place of a figure

    Before
    Bahrain and United Arab Emirates
    After
    Louisiana, statewide
    Why
    Moved to Louisiana, statewide: the figure's own words names Louisiana, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2118. · a record · the place of a figure

    Before
    Reno, Washoe County, NV
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2119. · a record · the place of a figure

    Before
    Reno, Washoe County, NV
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2120. · a record · the place of a figure

    Before
    Texas, United States
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2121. · a record · the place of a figure

    Before
    Texas, United States
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2122. · a record · the place of a figure

    Before
    Iowa, United States
    After
    Colleton County, SC
    Why
    Moved to Colleton County, SC: the figure's own words names South Carolina (Colleton County), not Iowa; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2123. · a record · the place of a figure

    Before
    Iowa, United States
    After
    Colleton County, SC
    Why
    Moved to Colleton County, SC: the figure's own words names South Carolina (Colleton County), not Iowa; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2124. · a record · the place of a figure

    Before
    Texas, United States
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2125. · a record · the place of a figure

    Before
    Texas, United States
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2126. · a record · the place of a figure

    Before
    Pima County, AZ
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2127. · a record · the place of a figure

    Before
    Pima County, AZ
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2128. · a record · the place of a figure

    Before
    Louisiana, Loudoun County Virginia, Montgomery County Missouri, statewide
    After
    Loudoun County, VA
    Why
    Moved to Loudoun County, VA: the figure's own words names Loudoun County, Virginia; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2129. · a record · the place of a figure

    Before
    Louisiana, Loudoun County Virginia, Montgomery County Missouri, statewide
    After
    Loudoun County, VA
    Why
    Moved to Loudoun County, VA: the figure's own words names Loudoun County, Virginia; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2130. · a record · the place of a figure

    Before
    NH
    After
    Arkansas, statewide
    Why
    Moved to Arkansas, statewide: the figure's own words names Arkansas, not New Hampshire; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2131. · a record · the place of a figure

    Before
    NH
    After
    Arkansas, statewide
    Why
    Moved to Arkansas, statewide: the figure's own words names Arkansas, not New Hampshire; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2132. · a record · the place of a figure

    Before
    PA
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2133. · a record · the place of a figure

    Before
    PA
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2134. · a record · the place of a figure

    Before
    Colorado River Basin, Western US
    After
    Orange County, CA
    Why
    Moved to Orange County, CA: the figure's own words names California (Orange County), not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2135. · a record · the place of a figure

    Before
    Colorado River Basin, Western US
    After
    Orange County, CA
    Why
    Moved to Orange County, CA: the figure's own words names California (Orange County), not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2136. · a record · the place of a figure

    Before
    CA
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2137. · a record · the place of a figure

    Before
    CA
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2138. · a record · the place of a figure

    Before
    Bahrain and United Arab Emirates
    After
    Louisiana, statewide
    Why
    Moved to Louisiana, statewide: the figure's own words names Louisiana, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2139. · a record · the place of a figure

    Before
    Bahrain and United Arab Emirates
    After
    Louisiana, statewide
    Why
    Moved to Louisiana, statewide: the figure's own words names Louisiana, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2140. · a record · the place of a figure

    Before
    Mississippi, Arkansas, Louisiana
    After
    Louisiana, statewide
    Why
    Moved to Louisiana, statewide: the figure's own words names Louisiana, not Mississippi; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2141. · a record · the place of a figure

    Before
    Mississippi, Arkansas, Louisiana
    After
    Louisiana, statewide
    Why
    Moved to Louisiana, statewide: the figure's own words names Louisiana, not Mississippi; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2142. · a record · the place of a figure

    Before
    Texas, United States
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2143. · a record · the place of a figure

    Before
    Texas, United States
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2144. · a record · the place of a figure

    Before
    Grand Junction, Colorado, CO
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2145. · a record · the place of a figure

    Before
    Grand Junction, Colorado, CO
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2146. · a record · the place of a figure

    Before
    Pike County, OH
    After
    Tennessee, statewide
    Why
    Moved to Tennessee, statewide: the figure's own words names Tennessee, not Ohio; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2147. · a record · the place of a figure

    Before
    Pike County, OH
    After
    Tennessee, statewide
    Why
    Moved to Tennessee, statewide: the figure's own words names Tennessee, not Ohio; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2148. · a record · the place of a figure

    Before
    West Memphis, Crittenden County, AR
    After
    Jefferson County, AR
    Why
    Moved to Jefferson County, AR: the figure's own words names Jefferson County, not Crittenden County; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2149. · a record · the place of a figure

    Before
    West Memphis, Crittenden County, AR
    After
    Jefferson County, AR
    Why
    Moved to Jefferson County, AR: the figure's own words names Jefferson County, not Crittenden County; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2150. · a record · the place of a figure

    Before
    KS
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2151. · a record · the place of a figure

    Before
    KS
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2152. · a record · the place of a figure

    Before
    North Carolina, statewide
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2153. · a record · the place of a figure

    Before
    North Carolina, statewide
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2154. · a record · the place of a figure

    Before
    Mississippi, statewide
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2155. · a record · the place of a figure

    Before
    Mississippi, statewide
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2156. · a record · the place of a figure

    Before
    PA
    After
    Richland Parish, LA
    Why
    Moved to Richland Parish, LA: the figure's own words names Richland Parish, Louisiana; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2157. · a record · the place of a figure

    Before
    PA
    After
    Richland Parish, LA
    Why
    Moved to Richland Parish, LA: the figure's own words names Richland Parish, Louisiana; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2158. · a record · the place of a figure

    Before
    NH
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2159. · a record · the place of a figure

    Before
    NH
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2160. · a record · the place of a figure

    Before
    OR
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2161. · a record · the place of a figure

    Before
    OR
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2162. · a record · the place of a figure

    Before
    Illinois, Texas
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2163. · a record · the place of a figure

    Before
    Illinois, Texas
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2164. · a record · the place of a figure

    Before
    Pima County, Arizona; Loudoun County, Virginia
    After
    Loudoun County, VA
    Why
    Moved to Loudoun County, VA: the figure's own words names Loudoun County, Virginia; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2165. · a record · the place of a figure

    Before
    Pima County, Arizona; Loudoun County, Virginia
    After
    Loudoun County, VA
    Why
    Moved to Loudoun County, VA: the figure's own words names Loudoun County, Virginia; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2166. · a record · the place of a figure

    Before
    Utah, statewide
    After
    Virginia, statewide
    Why
    Moved to Virginia, statewide: the figure's own words names Virginia, not Utah; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2167. · a record · the place of a figure

    Before
    Utah, statewide
    After
    Virginia, statewide
    Why
    Moved to Virginia, statewide: the figure's own words names Virginia, not Utah; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2168. · a record · the place of a figure

    Before
    CA
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2169. · a record · the place of a figure

    Before
    CA
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2170. · a record · the place of a figure

    Before
    Pima County, Arizona; Loudoun County, Virginia
    After
    Loudoun County, VA
    Why
    Moved to Loudoun County, VA: the figure's own words names Loudoun County, Virginia; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2171. · a record · the place of a figure

    Before
    Pima County, Arizona; Loudoun County, Virginia
    After
    Loudoun County, VA
    Why
    Moved to Loudoun County, VA: the figure's own words names Loudoun County, Virginia; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2172. · a record · the place of a figure

    Before
    West Virginia, statewide
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2173. · a record · the place of a figure

    Before
    West Virginia, statewide
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2174. · a record · the place of a figure

    Before
    Pennsylvania and Texas, multi-state
    After
    Mississippi, statewide
    Why
    Moved to Mississippi, statewide: the figure's own words names Mississippi, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2175. · a record · the place of a figure

    Before
    Frederick County, MD
    After
    Homer City, Indiana County, PA
    Why
    Moved to Homer City, Indiana County, PA: the figure's own words name Homer City, Pennsylvania, which has a page; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2176. · a record · the place of a figure

    Before
    Frederick County, MD
    After
    Homer City, Indiana County, PA
    Why
    Moved to Homer City, Indiana County, PA: the figure's own words name Homer City, Pennsylvania, which has a page; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2177. · a record · the place of a figure

    Before
    Missouri, statewide
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2178. · a record · the place of a figure

    Before
    Missouri, statewide
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2179. · a record · the place of a figure

    Before
    Bow, NH
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2180. · a record · the place of a figure

    Before
    Bow, NH
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2181. · a record · the place of a figure

    Before
    Chicago, IL
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2182. · a record · the place of a figure

    Before
    Chicago, IL
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2183. · a record · the place of a figure

    Before
    CA
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2184. · a record · the place of a figure

    Before
    CA
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2185. · a record · the place of a figure

    Before
    Mississippi, Arkansas, Louisiana
    After
    Crittenden County, AR
    Why
    Moved to Crittenden County, AR: the figure's own words names Arkansas (Crittenden County), not Mississippi; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2186. · a record · the place of a figure

    Before
    Mississippi, Arkansas, Louisiana
    After
    Crittenden County, AR
    Why
    Moved to Crittenden County, AR: the figure's own words names Arkansas (Crittenden County), not Mississippi; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2187. · a record · the place of a figure

    Before
    Mesa, Maricopa County, AZ
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2188. · a record · the place of a figure

    Before
    Mesa, Maricopa County, AZ
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2189. · a record · the place of a figure

    Before
    Utah, statewide
    After
    Georgia, statewide
    Why
    Moved to Georgia, statewide: the figure's own words names Georgia, not Utah; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2190. · a record · the place of a figure

    Before
    Utah, statewide
    After
    Georgia, statewide
    Why
    Moved to Georgia, statewide: the figure's own words names Georgia, not Utah; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2191. · a record · the place of a figure

    Before
    Kentucky, statewide
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2192. · a record · the place of a figure

    Before
    Kentucky, statewide
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2193. · a record · the place of a figure

    Before
    Santa Clara County, CA
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2194. · a record · the place of a figure

    Before
    Santa Clara County, CA
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2195. · a record · the place of a figure

    Before
    Virginia, statewide
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2196. · a record · the place of a figure

    Before
    Virginia, statewide
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2197. · a record · the place of a figure

    Before
    Missouri, Louisiana, statewide; Mississippi River Basin
    After
    Louisiana, statewide
    Why
    Moved to Louisiana, statewide: the figure's own words names Louisiana, not Missouri; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2198. · a record · the place of a figure

    Before
    Missouri, Louisiana, statewide; Mississippi River Basin
    After
    Louisiana, statewide
    Why
    Moved to Louisiana, statewide: the figure's own words names Louisiana, not Missouri; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2199. · a record · the place of a figure

    Before
    NY
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2200. · a record · the place of a figure

    Before
    NY
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2201. · a record · the place of a figure

    Before
    Virginia, statewide
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2202. · a record · the place of a figure

    Before
    Virginia, statewide
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2203. · a record · the place of a figure

    Before
    California, statewide
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2204. · a record · the place of a figure

    Before
    California, statewide
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2205. · a record · the place of a figure

    Before
    Nevada, statewide
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2206. · a record · the place of a figure

    Before
    Nevada, statewide
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2207. · a record · the place of a figure

    Before
    Texas, TX
    After
    California, statewide
    Why
    Moved to California, statewide: the figure's own words names California, not Texas; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2208. · a record · the place of a figure

    Before
    Texas, TX
    After
    California, statewide
    Why
    Moved to California, statewide: the figure's own words names California, not Texas; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2209. · a record · the place of a figure

    Before
    Quebec, statewide
    After
    Saskatchewan, statewide
    Why
    Moved to Saskatchewan, statewide: the figure's own words names Saskatchewan, not Quebec; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2210. · a record · the place of a figure

    Before
    Quebec, statewide
    After
    Saskatchewan, statewide
    Why
    Moved to Saskatchewan, statewide: the figure's own words names Saskatchewan, not Quebec; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2211. · a record · the place of a figure

    Before
    Utah, statewide
    After
    Texas, statewide
    Why
    Moved to Texas, statewide: the figure's own words names Texas, not Utah; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2212. · a record · the place of a figure

    Before
    Utah, statewide
    After
    Texas, statewide
    Why
    Moved to Texas, statewide: the figure's own words names Texas, not Utah; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2213. · a record · the place of a figure

    Before
    Louisiana, statewide
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2214. · a record · the place of a figure

    Before
    Louisiana, statewide
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2215. · a record · the place of a figure

    Before
    Alabama, statewide
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2216. · a record · the place of a figure

    Before
    Alabama, statewide
    After
    United States, national
    Why
    Moved to United States, national: the figure's own words names the country, not the place it sits on; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2217. · a record · the place of a figure

    Before
    Pataskala, Franklin County, OH
    After
    New Albany, Franklin County, OH
    Why
    Moved to New Albany, Franklin County, OH: the figure's own words name New Albany, Ohio, which has a page; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2218. · a record · the place of a figure

    Before
    Pataskala, Franklin County, OH
    After
    New Albany, Franklin County, OH
    Why
    Moved to New Albany, Franklin County, OH: the figure's own words name New Albany, Ohio, which has a page; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2219. · a record · the place of a figure

    Before
    Kentucky, statewide
    After
    Loudoun County, VA
    Why
    Moved to Loudoun County, VA: the figure's own words names Loudoun County, Virginia; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2220. · a record · the place of a figure

    Before
    Kentucky, statewide
    After
    Loudoun County, VA
    Why
    Moved to Loudoun County, VA: the figure's own words names Loudoun County, Virginia; a figure sits on the place it describes (the trust fixes of 2026-10-08).

  2221. · a record · the summary of a news item

    Before
    The Interstate Commission on the Potomac River Basin's assessment (dated March 2026, no day given, recorded here as the first of the month), part of the 2025 Washington Metropolitan Area Water Supply and Demand Study, puts data centers' onsite consumptive water use in the Washington metropolitan area at about 4 million gallons a day on average in 2025 and about 15 million on the peak day, from utility records linked to facility power capacities with a 75 percent consumptive use factor and estimates where no direct reporting exists. Under baseline assumptions it projects about 22 million a day on average and over 80 million at peak by 2050, with summer demand arriving when river flows are lowest. All four figures are regional totals, consumptive use, estimated. The two jurisdiction events need a rating from you before Approve writes them: the Virginia and Maryland state rows carry no rating yet and this assessment does not set one. Archived at data/archive/sources/icprb-2026 data centers potomac basin.html.
    After
    The Interstate Commission on the Potomac River Basin's assessment, part of the 2025 Washington Metropolitan Area Water Supply and Demand Study, puts data centers' onsite consumptive water use in the Washington metropolitan area at about 4 million gallons a day on average in 2025 and about 15 million on the peak day, from utility records linked to facility power capacities with a 75 percent consumptive use factor and estimates where no direct reporting exists. Under baseline assumptions it projects about 22 million a day on average and over 80 million at peak by 2050, with summer demand arriving when river flows are lowest.
    Why
    The sentence carried an editor's note (an archive path and a note to the person approving); the note is cut and the record's own sentence stays (the trust fixes of 2026-10-08).

  2222. · a record · the summary of a news item

    Before
    The Pacific Institute issue brief by Heather Cooley and Morgan Shimabuku (dated September 2026, no day given, recorded here as the first of the month) compiles facility level water records for 65 data centers from Google and Microsoft sustainability reports and a peer reviewed dataset. Average daily withdrawals calculated from annual records ranged from about 270 gallons to 3.9 million gallons, with a median of about 121,000 gallons a day; the records cover 2024 or 2025 and do not consistently distinguish a single building from a campus. Verified against pages 10 and 11 of the PDF, archived at data/archive/sources/pacific institute-2026 data center water.pdf. Both figures are drafted with withdrawal as the measure, facility as the level and measured as the basis; Approve publishes them.
    After
    The Pacific Institute issue brief by Heather Cooley and Morgan Shimabuku compiles facility level water records for 65 data centers from Google and Microsoft sustainability reports and a peer reviewed dataset. Average daily withdrawals calculated from annual records ranged from about 270 gallons to 3.9 million gallons, with a median of about 121,000 gallons a day; the records cover 2024 or 2025 and do not consistently distinguish a single building from a campus.
    Why
    The sentence carried an editor's note (an archive path and a note to the person approving); the note is cut and the record's own sentence stays (the trust fixes of 2026-10-08).

  2223. · Montgomery County · the summary of a scorecard event

    Before
    Montgomery County Council voted unanimously on July 28, 2026 for an 18 month moratorium on new data centers of 25 megawatts or more (threshold as reported by Bisnow, card 4220)
    After
    Montgomery County Council voted unanimously on July 28, 2026 for an 18 month moratorium on new data centers of 25 megawatts or more, the threshold as reported by Bisnow
    Why
    The event named the Inbox card it came from in brackets; the card number is the admin's, not the record's, and is removed (the trust fixes of 2026-10-08).

  2224. · OpenAI Effingham County Data Center · the summary of a timeline entry

    Before
    Construction is expected to begin in 2028 and finish by 2032, with operations planned from 2028; project discussions began in November 2023 (dates also on WTOC and the county video, card 3925)
    After
    Construction is expected to begin in 2028 and finish by 2032, with operations planned from 2028; project discussions began in November 2023, dates also on WTOC and the county video
    Why
    The entry named the Inbox card it came from in brackets; the card number is the admin's, not the record's, and is removed (the trust fixes of 2026-10-08).

  2225. · Montgomery Meta Investment · the summary of a timeline entry

    Before
    The facility will be Meta's 20th data center in the United States and its second in Alabama after Huntsville (as reported by AI Business, card 4202)
    After
    The facility will be Meta's 20th data center in the United States and its second in Alabama after Huntsville, as reported by AI Business
    Why
    The entry named the Inbox card it came from in brackets; the card number is the admin's, not the record's, and is removed (the trust fixes of 2026-10-08).

  2226. · project-patriot-granbury-tx · the summary of a record

    Before
    About 2,100 acres near Highway 377 in Granbury rezoned for a potential data center; residents sued the City of Granbury on April 10, 2026 under the Texas Open Meetings Act. Skeleton from the litigation packet of 2026-09-09; separate from the MARA Granbury site.
    After
    About 2,100 acres near Highway 377 in Granbury rezoned for a potential data center; residents sued the City of Granbury on April 10, 2026 under the Texas Open Meetings Act. Separate from the MARA Granbury site.
    Why
    The summary ended with a note from the review packet that drafted the record; the note is removed and the sentence that tells the two Granbury sites apart stays (the trust fixes of 2026-10-08).

  2227. · mara-granbury-data-center-tx · the summary of a record

    Before
    MARA Holdings took over the former Wolf Hollow site near Granbury in 2024; residents filed a noise suit in Hood County in October 2024 and the Hood County Commissioners Court declined a one year data center moratorium on February 11, 2026.
    After
    MARA Holdings took over the former Wolf Hollow site near Granbury in 2024; residents filed a noise suit in Hood County in October 2024 and the Hood County Commissioners Court declined a one year data center moratorium on February 11, 2026.
    Why
    The summary ended with a note from the review packet that drafted the record, not a fact about it; the note is removed (the trust fixes of 2026-10-08).

  2228. · Digi Power X North Tonawanda · the summary of a record

    Before
    Digi Power X, formerly Digihost, runs a crypto mining site with a 60 MW gas fired peaker plant at 1070 Erie Avenue in North Tonawanda; residents filed a class action in the Western District of New York in 2026 and the city's crypto mining moratorium blocks a proposed pivot to AI computing.
    After
    Digi Power X, formerly Digihost, runs a crypto mining site with a 60 MW gas fired peaker plant at 1070 Erie Avenue in North Tonawanda; residents filed a class action in the Western District of New York in 2026 and the city's crypto mining moratorium blocks a proposed pivot to AI computing.
    Why
    The summary ended with a note from the review packet that drafted the record, not a fact about it; the note is removed (the trust fixes of 2026-10-08).

  2229. · Jersey Avenue Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    the record's rules: the entry is about the province of New Brunswick's plan and was filed on a New Jersey record; returned to draft on the editor's word

  2230. · google-fervo-geothermal-utah-ut · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    the record's rules: a power purchase deal is not a data center site, and the record names no site; returned to draft on the editor's word

  2231. · google-fervo-geothermal-utah-ut · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    the record's rules: a power purchase deal is not a data center site, and the record names no site; returned to draft on the editor's word

  2232. · a record · the summary of a news item

    Before
    Jackson Walker partner Meghan Griffiths discusses Texas data center power procurement strategies at Data Center World Power Conference, focusing on ERCOT market structures.
    After
    Jackson Walker partner Meghan E. Griffiths spoke on a panel at the Data Center World Power Conference about how ERCOT's market structure shapes power buying by Texas data centers.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2233. · Meta Temple Data Center · the summary of a news item

    Before
    Meta pauses construction on its Temple, Texas data center as part of AI rescoping, with design changes still being finalized.
    After
    Meta paused construction on its data center in Temple, Texas, which was set to span 900,000 square feet, saying it is changing the design for artificial intelligence workloads.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2234. · a record · the summary of a news item

    Before
    California enacted seven data center bills effective January 1, 2027, establishing new tariff structures and reporting requirements for hyperscale facilities to ensure fair cost allocation to data centers.
    After
    California Gov. Newsom signed seven data center bills on September 21, 2026, most taking effect January 1, 2027, among them SB 886, which directs the state's Public Utilities Commission to set data center tariffs.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2235. · Project Jupiter · the summary of a news item

    Before
    U.S. Rep. Leger Fernández calls for data center pause in New Mexico and sets standards for future projects.
    After
    U.S. Rep. Teresa Leger Fernández called for a pause on New Mexico data centers, saying they should not raise electricity bills or harm water resources and must have community approval.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2236. · a record · the summary of a news item

    Before
    Cleveland residents invited to hearing on data centers.
    After
    Residents of Cleveland, Ohio, have been invited to a hearing about data centers.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2237. · a record · the summary of a news item

    Before
    Republican Dan Cox calls for statewide data center ban in Maryland and criticizes Gov. Moore's regulatory executive order.
    After
    Dan Cox, a Republican candidate for Maryland governor, called for banning data centers statewide, saying Gov. Wes Moore's executive order stops short of a moratorium on new projects.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2238. · a record · the summary of a news item

    Before
    DTE Energy plans two natural gas plants to meet data center demand in Michigan.
    After
    In Michigan, DTE Energy is planning two additional natural gas power plants to serve data center demand.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2239. · a record · the summary of a news item

    Before
    Data center proposed in Forward Township, Butler County, Pennsylvania.
    After
    A data center has been proposed for Forward Township in Butler County, Pennsylvania.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2240. · ValorC3 Boise Data Center · the summary of a news item

    Before
    A massive data center on thousands of acres of public land south of Boise enters early review stages, raising concerns about impacts.
    After
    A data center is proposed south of Boise, Idaho, on public land covering thousands of acres, and has entered the early stages of review.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2241. · a record · the summary of a news item

    Before
    Texas Gov. Abbott ordered TCEQ to pause environmental permits for data centers until audit of energy and water usage is complete.
    After
    Texas Gov. Greg Abbott ordered the Texas Commission on Environmental Quality on September 22 to pause air and water permits for data center infrastructure until an audit is complete.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2242. · a record · the summary of a news item

    Before
    FingerMotion subsidiary signed binding letter of intent for second Alberta data center site in Hanna, planned at 9.9 megawatts.
    After
    A FingerMotion subsidiary signed a binding letter of intent to buy about 20.2 acres in Hanna, Alberta, for a planned 9.9 megawatt site serving AI and high performance computing clients.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2243. · a record · the summary of a news item

    Before
    Pennsylvania DEP issues Section 401 water quality certification for restart of Constellation Energy Three Mile Island nuclear data center in Dauphin County.
    After
    Pennsylvania's Department of Environmental Protection issued Constellation Energy a Section 401 water quality certification to restart Three Mile Island, which may withdraw up to 73.2 million gallons a day from the Susquehanna at peak.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2244. · Butte-Silver Bow Data Center (ballot initiative) · the summary of a news item

    Before
    Sabey Data Centers backed out of a proposed data center in Butte-Silver Bow; local opposition continues through ballot initiative.
    After
    Sabey Data Centers has withdrawn from a data center that was planned for Butte-Silver Bow in Montana.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2245. · Lenox Township Data Center · the summary of a news item

    Before
    Lenox Township board meets to discuss I-94 Industrial District ordinance and data center development with public opposition.
    After
    The Lenox Township Board in Michigan met on July 13, 2026, to discuss data centers and its I-94 Industrial District Ordinance, hearing opposition during public comment.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2246. · a record · the summary of a news item

    Before
    City of Salisbury proposes one year moratorium on data center applications, joining jurisdictions across United States implementing restrictions.
    After
    The City of Salisbury proposed a one year moratorium on applications for data centers.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2247. · northampton-county-data-center-pa · the summary of a news item

    Before
    A data center proposal in Lower Mount Bethel Township, Northampton County, Pennsylvania sparked wildlife concerns.
    After
    A proposed data center in Lower Mount Bethel Township, in Northampton County, Pennsylvania, has drawn concerns about its effect on wildlife.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2248. · a record · the summary of a news item

    Before
    Northfield moves to ban hyperscale data centers following a packed public hearing, indicating a jurisdiction action to restrict data center development.
    After
    Northfield, Minnesota, took steps toward a ban on hyperscale data centers after a public hearing that filled the room.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2249. · Meta Beaver Dam Data Center · the summary of a news item

    Before
    Meta officially announces $1 billion, 26th U.S. data center campus in Beaver Dam, Wisconsin, optimized for AI workloads with wetland restoration partnership.
    After
    Meta named Beaver Dam, Wisconsin, as the site of its 26th U.S. data center, a $1 billion campus of more than 700,000 square feet to be optimized for AI workloads.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2250. · a record · the summary of a news item

    Before
    Will Lawrence, Democratic nominee for Michigan's 7th Congressional District, calls for nationwide data center moratoriums at MSU event.
    After
    Will Lawrence, running as the Democratic nominee in Michigan's 7th Congressional District, said he would push for nationwide moratoriums on data centers.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2251. · a record · the summary of a news item

    Before
    Serverfarm expands its North American data center development fund to $3.89 billion with an additional $895 million closing, supporting projects in Texas, Arkansas, and Georgia.
    After
    Serverfarm expanded its revolving credit facility to $3.89 billion in total commitments, with the funding supporting campus projects in Houston, Clarksville and Atlanta.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2252. · a record · the summary of a news item

    Before
    Microsoft ordered to pay nearly $2.5 million fine for air pollution from Northern Virginia data center.
    After
    Microsoft was ordered to pay a fine over air pollution from a data center in Northern Virginia.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2253. · Ypsilanti Township / University of Michigan & Los Alamos Data Center · the summary of a news item

    Before
    Rep. Debbie Dingell calls for pause on University of Michigan's $1.25 billion Ypsilanti Township supercomputing facility; Michigan cities advance data center moratoriums.
    After
    U.S. Rep. Debbie Dingell called for a pause on a $1.25 billion supercomputing facility the University of Michigan plans in Ypsilanti Township, citing a lack of transparency and unclear jurisdictional authority.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2254. · a record · the summary of a news item

    Before
    A poll finds 6 in 10 Pennsylvania voters oppose data center development, with 83 percent of ages 18-29 opposed.
    After
    A poll of 760 likely Pennsylvania voters taken August 17 to 21 found six in 10 do not want data centers built in the U.S. to house artificial intelligence.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2255. · Compass Red Oak campus · the summary of a news item

    Before
    A Texas developer secured a $2 billion loan to build Oracle data centers near Dallas.
    After
    A developer based in Texas obtained $2 billion in financing to build data centers for Oracle near Dallas.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2256. · DataBank Dallas data center · the summary of a news item

    Before
    Gigabit Fiber signs long term lease extension with DataBank at DFW1 downtown Dallas facility and deployed optical network.
    After
    Gigabit Fiber extended its lease at DataBank's DFW1 facility at 400 S. Akard in downtown Dallas, adding space for offices, a lab and a data center environment.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2257. · a record · the summary of a news item

    Before
    Pennsylvania DEP received Act 2 Land Recycling remediation report for former Cheswick Generating Station data center site.
    After
    Pennsylvania's Department of Environmental Protection is reviewing a cleanup plan for the data center site at the former Cheswick Generating Station in Springdale, where Allegheny DC PropCo reports contamination including lead and PCBs.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2258. · a record · the summary of a news item

    Before
    Tennessee Rep. Aftyn Behn proposes three year pause on data center tax exemptions and improved tracking of revenue loss.
    After
    Tennessee state Rep. Aftyn Behn plans to file a bill for the 2027 session that would pause new data center tax exemption certificates for three years and require reporting of their annual cost.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2259. · a record · the summary of a news item

    Before
    Dover Township, Ohio held public meeting on proposed 250 megawatt data center; trustee suggested public vote but noted uncertainty about regulatory authority.
    After
    Saadia Holdings asked in July 2026 about nearly 300 acres along U.S. 33 for a data center, and Dover Township Trustee Chris Russell signaled interest in a public vote on whether one is welcome.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2260. · a record · the summary of a news item

    Before
    Fluidstack breaks ground on first phase of $4 billion AI data center campus in Cameron County, Texas with local worksite permit and resource protections.
    After
    Fluidstack broke ground on the first phase of an AI data center campus near Rio Hondo, Texas, and Cameron County issued a worksite permit for site clearing, land grading and utility installation.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2261. · a record · the summary of a news item

    Before
    Fluidstack breaks ground on $4 billion data center campus in Cameron County, Texas, promising 2,500 construction jobs and closed loop water cooling.
    After
    Fluidstack broke ground near Rio Hondo in Cameron County, Texas, on a data center campus valued at 4 billion dollars and expected to create more than 2,500 construction jobs.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2262. · Project Jupiter · the summary of a news item

    Before
    Oracle plans public environmental dashboard for Project Jupiter data center to report air, noise, heat, light and water use.
    After
    Oracle plans a public dashboard on air, noise, heat, light and water use at Project Jupiter in Doña Ana County, New Mexico, with an independent expert assessing that information twice a year.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2263. · Ypsilanti Township / University of Michigan & Los Alamos Data Center · the summary of a news item

    Before
    Ypsilanti Township residents voiced opposition at town hall to University of Michigan and Los Alamos 100 megawatt computing center.
    After
    A town hall meeting in Ypsilanti Township, Michigan, on September 9, 2026, addressed the University of Michigan and Los Alamos data center project.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2264. · a record · the summary of a news item

    Before
    Climate reporter investigates the massive power demand of Nevada's data center boom and critics' concerns about local power bill impacts.
    After
    Data center growth in Nevada comes with large power demand, and critics say the risk to local power bills is not worth it.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2265. · a record · the summary of a news item

    Before
    Nye County commissioners approve data center ban in Pahrump and plan public hearing on countywide ordinance allowing data centers elsewhere.
    After
    Commissioners in Nye County, Nevada, changed the land use code to ban data centers in the Pahrump area and scheduled a public hearing on a countywide ordinance setting rules for data centers.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2266. · a record · the summary of a news item

    Before
    Clarksville City Council approves $55 billion in bonds for data center financing.
    After
    The city council in Clarksville, Arkansas, approved bonds totaling $55 billion for a data center.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2267. · a record · the summary of a news item

    Before
    Terrace explores possible zoning changes to increase scrutiny of proposed data centre projects.
    After
    Terrace, British Columbia, is weighing zoning changes that would subject data centers to closer scrutiny.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2268. · NorthMark Spartanburg County Data Center · the summary of a news item

    Before
    Residents stormed out during data center debate in Spartanburg County over NorthMark proposal.
    After
    Residents walked out of a debate over a data center in Spartanburg County, South Carolina.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2269. · a record · the summary of a news item

    Before
    Pennsylvania Governor signed executive order imposing strict requirements on data center developments, mandating local approval before permits issued.
    After
    Pennsylvania's governor signed an executive order requiring data center projects to receive all required local approvals before permits are issued.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2270. · a record · the summary of a news item

    Before
    Virginia advocacy groups seek local public hearings on Dominion NextEra merger, citing data center growth and community concerns.
    After
    Nine Virginia community groups called for four regional public hearings on the Dominion and NextEra merger, which Delegate Joshua Cole opposes over concerns about keeping up with energy demand from proposed data centers.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2271. · a record · the summary of a news item

    Before
    National Association of Realtors study of 3,200 counties finds data center impact on housing varies; higher values and jobs in host counties but mixed residential perceptions.
    After
    A National Association of Realtors study identified 1,474 data centers in 251 U.S. counties, and Nadia Evangelou said the research does not show a data center automatically raises or lowers nearby home values.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2272. · NorthMark Spartanburg County Data Center · the summary of a news item

    Before
    South Carolina approved nearly $3 billion data center in Spartanburg County despite pending lawsuit.
    After
    South Carolina approved a data center project in Spartanburg County valued at nearly 3 billion dollars.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2273. · a record · the summary of a news item

    Before
    Oregon Governor Kotek freezes state land deals for data centers and calls for legislative moratorium, citing need to understand water and energy impacts.
    After
    Oregon Governor Tina Kotek ordered state agencies to stop new data center land deals until July 2027 and said the legislature should pass a statewide moratorium in its 2027 session.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2274. · a record · the summary of a news item

    Before
    Plainsman Holdings proposes Project Thunderbird, a 1,735 acre four campus data center development near Enid with 3.3 gigawatts power generation and Vance Air Force Base connectivity.
    After
    Project Thunderbird would place four data center campuses on nearly 1,750 acres in and around Enid, Oklahoma, with about 2.75 gigawatts of information technology power and up to $35 billion in capital investment.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2275. · a record · the summary of a news item

    Before
    Massachusetts Governor Healey signed an executive order requiring local approval for data center projects and compliance with a state data center framework.
    After
    Massachusetts Governor Maura Healey signed an executive order that requires local approval and a community benefits agreement before the state permits a data center, and bars nondisclosure agreements with state agencies.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2276. · a record · the summary of a news item

    Before
    Oregon governor says she now supports a data center moratorium as facilities become political issue.
    After
    Oregon Governor Tina Kotek voiced support for a moratorium on data centers until the state develops stronger protections.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2277. · a record · the summary of a news item

    Before
    Convergent VA withdrew its rezoning application for a planned 1.6 million square foot data center near Remington, Fauquier County, in favor of residential development.
    After
    Convergent VA withdrew its bid to rezone about 104 acres south of Remington in Fauquier County for 1.584 million square feet of data center and office space, and will pursue residential development instead.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2278. · a record · the summary of a news item

    Before
    Thor Acquisition filed a $1 billion, 350,000 square foot data center proposal for Kingston Technology Hub in Bartow County, Georgia, with DRI completion target 2030.
    After
    The Kingston Technology Hub, a data center on 559 acres in Bartow County, Georgia, with an estimated value of 1 billion dollars when built out, filed for Development of Regional Impact.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2279. · a record · the summary of a news item

    Before
    New Jersey Legislature votes 74-4 in Assembly and near unanimously in Senate to eliminate $250 million in AI data center tax credits under End Data Center Tax Credits Act.
    After
    New Jersey lawmakers passed the End Data Center Tax Credits Act, which ends $250 million in uncommitted credits for AI and data center projects, by 74 to 4 in the Assembly on June 30.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2280. · a record · the summary of a news item

    Before
    New Jersey Governor Mikie Sherrill announced a four point plan requiring data centers to pay for their own electricity, report power and water use, and use union labor.
    After
    Under a four point plan from Governor Mikie Sherrill, New Jersey data centers would contract with their own power generators, pay for grid updates, disclose power and water consumption and use union labor.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2281. · a record · the summary of a news item

    Before
    Hamilton, Ontario data centre moratorium could be a Canadian first; researcher suggests other jurisdictions may follow.
    After
    The moratorium on data centers in Hamilton, Ontario, is described as the first in Canada, and other jurisdictions may follow.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2282. · Meta Louisiana data center · the summary of a news item

    Before
    Meta data center in North Louisiana reported to become largest in history; no details provided beyond headline.
    After
    Meta's data center in North Louisiana is reported to be the largest in history, and Jeff Landry said the commitment puts Louisiana at the center of America's future in artificial intelligence.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2283. · a record · the summary of a news item

    Before
    An Arizona county advanced a 4 month halt on new data centers citing water and power use concerns.
    After
    Pima County, Arizona, moved ahead with a 4 month pause on new data centers over concerns about water and power use.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2284. · a record · the summary of a news item

    Before
    Greensboro city leaders held a work session to examine potential data center opportunities and impacts. The headline indicates ongoing local deliberation about data center development in the city.
    After
    During a work session, city leaders in Greensboro, North Carolina, reviewed the possible opportunities and impacts of data centers.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2285. · a record · the summary of a news item

    Before
    North Carolina lawmakers are considering new regulations on data center construction. No details available from headline alone.
    After
    Legislators in North Carolina are weighing new rules for building data centers.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2286. · a record · the summary of a news item

    Before
    Governor Bill Lee visits Fisk University as it defends proposed 70,000 square foot data center amid student, alumni, and community opposition.
    After
    Tennessee Governor Bill Lee visited Fisk University in Nashville amid controversy over a data center.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2287. · a record · the summary of a news item

    Before
    Mayor Young hopes for clarity on data centers and TVA rates at an open session. The statement indicates municipal officials seeking regulatory clarity.
    After
    Memphis Mayor Young hopes an open session will bring clarity on data centers and TVA rates.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2288. · a record · the summary of a news item

    Before
    Evergy's disclosures connect five data center projects in Kansas and Missouri to a $5.3 billion power system overhaul that could raise residential bills by 10 percent.
    After
    Data center deals in Kansas and Missouri could bring 10% rate increases, and Parker Thompson said customers will pay for a $5.3 billion buildout.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2289. · a record · the summary of a news item

    Before
    Essex County took its first step to prepare for AI data centre proposals. No details are available from the headline alone about the nature of this preparation.
    After
    Essex County, Ontario, took a first step toward preparing for AI data center proposals.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2290. · a record · the summary of a news item

    Before
    North Carolina Gov. Josh Stein proposed phasing out the state's tax incentives for data centers by 2033. The proposal represents a significant policy shift toward restricting data center development in the state.
    After
    Governor Josh Stein proposed that North Carolina phase out its data center tax incentives by 2033, calling it unfair for taxpayers to subsidize data centers' energy use.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2291. · a record · the summary of a news item

    Before
    An AARP article discusses potential impacts on South Carolina utility customers from a data center bill. The headline indicates jurisdictional action or legislation affecting data centers in the state.
    After
    A data center bill under consideration in South Carolina could affect the state's utility customers.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2292. · a record · the summary of a news item

    Before
    Governor Newsom vetoed a data center water bill last year; the headline indicates a question of whether he will sign it again this year. The content is not readable.
    After
    Newsom vetoed a California bill on data center water use last year, and whether he will sign it this time is not yet known.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2293. · a record · the summary of a news item

    Before
    The city of Cheyenne held a community panel to address concerns about rapid data centre development in Laramie County. Around 120 residents attended to ask questions about water and electrical use by the 10 operational data centres already in or near the city.
    After
    Cheyenne, Wyoming, condensed 84 public responses on data centers into 30 questions for a panel, and Mayor Patrick Collins said residents and businesses should not subsidize data center operations.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2294. · Google Mesa data center · the summary of a news item

    Before
    Mesa City Council is poised to approve a development agreement with Google for a massive data center in the Elliot Road Technology Corridor, with a $600 million investment by July 2025 and eventual $1 billion commitment by July 2029. The project will generate an estimated $156.5 million in revenues for the city over 25 years.
    After
    Mesa City Council is expected to approve a development agreement for a Google data center on 186 acres in the Elliot Road Technology Corridor, requiring at least $1 billion invested by July 2029.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2295. · Google Mesa data center · the summary of a news item

    Before
    Mesa heard building design plans for the first phase of Google's $1 billion data center campus. The project is advancing through site plan review.
    After
    Google's data center campus in Mesa, Arizona, is a $1 billion project.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2296. · Google Mesa data center · the summary of a news item

    Before
    Google is building a $600 million data center in Mesa using air cooling rather than water cooling. The project represents Google's first physical infrastructure investment in the Phoenix area.
    After
    Google's data center in Mesa, Arizona, is a $600 million project cooled by air instead of water.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2297. · Google Mesa data center · the summary of a news item

    Before
    Google is pursuing phase two of its Mesa data center complex with a reported $1 billion total project cost. Details are limited from the headline alone.
    After
    Google is pursuing phase II of its approximately $1 billion data center complex in Mesa, Arizona.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2298. · Google Mesa data center · the summary of a news item

    Before
    Google detailed plans for its large data center underway in Mesa, Arizona. The headline indicates company communications about the project status and design.
    After
    Google gave details of its plans for the data center it has underway in Mesa, Arizona.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2299. · Google Mesa data center · the summary of a news item

    Before
    Google filed plans to build a second data center at its Mesa campus in Arizona. The filing indicates expansion of the company's Arizona footprint. Status: proposes under construction with this filing as the basis, since a second building filed on a campus that broke ground in July 2023 (card 5218) describes construction, not a proposal; nothing here says the first building operates.
    After
    Google filed to add a second data center to its campus in Mesa, Arizona.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2300. · a record · the summary of a news item

    Before
    Maricopa County issued a new ordinance that clarifies guidelines for data center development. No details are available beyond the headline.
    After
    Maricopa County, Arizona, adopted a new ordinance clarifying its guidelines for developing data centers.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2301. · EdgeCore Mesa North Campus · the summary of a news item

    Before
    EdgeCore announced an expansion of its Mesa data center campus in Arizona in May 2025. No details available from headline only.
    After
    In May 2025, EdgeCore Digital Infrastructure enlarged its Mesa campus with new land that Lee Kestler said enables another 250 MW or more of data center space.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2302. · NTT Mesa data center campus · the summary of a news item

    Before
    NTT Data Centers acquired a 173 acre planned data center park in Mesa, Arizona for $300 million in March 2025. The transaction represents a major expansion of NTT's presence in the Arizona data center market.
    After
    NTT Data Centers paid $300 million in March 2025 for a planned data center park of 173 acres in Mesa, Arizona.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2303. · EdgeCore Mesa North Campus · the summary of a news item

    Before
    EdgeCore Digital Infrastructure is seeking approval for a revised Mesa North Campus data center expansion, reducing the facility from 2.1 million square feet to approximately 1.2 million square feet. The March 11 planning and zoning board approval would move the project to Mesa City Council, pending available power.
    After
    EdgeCore's revised plan for its Mesa campus shrinks an expansion approved in January 2024 at 2.1 million square feet to two buildings totaling 1,236,960 square feet.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2304. · NTT Mesa data center campus · the summary of a news item

    Before
    A data center project in Mesa is moving forward, according to the headline. No additional detail is available from the headline alone.
    After
    In Mesa, Arizona, a data center project is advancing.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2305. · Google Mesa data center · the summary of a news item

    Before
    Google's December 14, 2023 blog post by Ben Townsend, its Global Head of Data Center Sustainability, describes a watershed risk framework and says the responsible use evaluation for its recently announced data center in Mesa, Arizona found the local water source at high risk of depletion and scarcity, so Google opted to air cool the data center. This is a company statement about its own planning decision, not an independent audit. No Mesa record existed, so a skeleton draft project (google mesa data center az, Google, Mesa, Maricopa County) was created with this post as its source; Approve writes the design fact as a timeline entry on it. Archived at data/archive/sources/google-2023 watershed health mesa.html. Status: the card proposes under construction, not proposed, because the latest sourced timeline events on this packet are the July 2023 groundbreaking (card 5218), the April 2024 filing for a second building (card 5221) and Construction Review's May 2026 report that the campus is under construction (card 5138). An earlier reading of the packet as operating was dropped for lack of a source: no card, and no Google page, says the campus is running.
    After
    Google said the water source for its data center in Mesa, Arizona, was at high risk of scarcity and depletion, so the company chose air cooling.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2306. · a record · the summary of a news item

    Before
    The Nature analysis by Husam Alissa and 22 coauthors (April 30, 2025, volume 641, pages 331 to 338, open access) is a life cycle assessment of cloud data center cooling that finds cold plate and immersion cooling reduce blue water consumption, meaning surface water and groundwater, by 31 to 52 percent against air cooling for the configurations assessed on US average grid electricity. Industry affiliation for the citation: 17 authors are at Microsoft Corporation and 6 at WSP Global, and the designs assessed are Microsoft's own. The draft figure records the range as consumptive use, facility level, estimated. Archived at data/archive/sources/nature-2025 alissa lca cool clouds.html.
    After
    A life cycle assessment by authors at Microsoft and WSP found cold plate and immersion cooling reduced blue water consumption by 31 to 52 percent compared with air cooling in the configurations it assessed.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2307. · a record · the summary of a news item

    Before
    The Environmental and Energy Study Institute briefing by Miguel Yañez Barnuevo (June 25, 2025) says large data centers can use up to 5 million gallons of water a day, about 1.8 billion a year, which it compares with a town of 10,000 to 50,000 people. The figure is a published high end, not measured use at a named facility, and the briefing does not say whether it means withdrawal or consumptive use; the draft figure records it as estimated, facility level, measure not stated. Archived at data/archive/sources/eesi-2025 data centers and water consumption.html.
    After
    Water use at large data centers can reach 5 million gallons a day, comparable to a town with 10,000 to 50,000 residents, by a published high end estimate rather than measurement.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2308. · a record · the summary of a news item

    Before
    Louisiana's use of non disclosure agreements in its AI data center expansion raises transparency concerns. The headline suggests public scrutiny of the state's deal making practices.
    After
    Louisiana has used nondisclosure agreements in its effort to attract AI data centers.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2309. · Meta Louisiana data center · the summary of a news item

    Before
    Meta plans a $40 billion expansion of its Louisiana AI data center, more than doubling its size. The headline indicates a major expansion of the Hyperion facility in Louisiana.
    After
    Meta intends to spend $40 billion expanding its AI data center in Louisiana.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2310. · Baltimore City Data Center (proposed bill) · the summary of a news item

    Before
    More than half of Maryland's counties have enacted data center moratoriums as deadlines approach. Harford County has implemented an outright ban while Anne Arundel County has pending restrictions.
    After
    Harford County has banned data centers outright and Anne Arundel County has restrictions pending, as a majority of Maryland's counties have put data centers on pause.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2311. · a record · the summary of a news item

    Before
    Prince George's County announced a pause on data center development for 2 years. Further details are not readable from the headline alone.
    After
    Prince George's County, Maryland, has paused data center development for two years.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2312. · a record · the summary of a news item

    Before
    Louisiana has secured $160 billion in capital investment over 2.5 years; $81.6 billion from four major data center projects.
    After
    Louisiana Economic Development secretary Susan Bourgeois said the state secured $160 billion in new capital investment over the last two and a half years, $81.6 billion of it from four data centers.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2313. · NScale Mason County Data Center · the summary of a news item

    Before
    Anthropic signed a $45 billion compute capacity agreement with Nscale for 460MW at the Monarch Compute Campus in West Virginia, with delivery expected late 2027. Microsoft also committed 1.35GW at the same campus.
    After
    Anthropic signed a $45 billion AI cloud capacity agreement with Nscale to lease 460MW for six years at Nscale's Monarch Compute Campus in West Virginia, where Microsoft signed on for 1.35GW.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2314. · a record · the summary of a news item

    Before
    A Mississippi state AI task force is considering whether data centers need state level regulations. The headline indicates ongoing policy consideration at the state level.
    After
    A Mississippi task force on AI is weighing whether the state should regulate data centers.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2315. · a record · the summary of a news item

    Before
    An under the radar bill could impact how Montana works with data centers. The headline suggests legislative action on data center regulation at the state level.
    After
    A Montana bill could affect how the state works with data centers, and Daniel Zolnikov described a declaration from the Legislature that Montanans have a right to use AI and operate data centers.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2316. · a record · the summary of a news item

    Before
    Alberta Premier Danielle Smith participated in third provincial town hall on AI data centre development with more than 12,500 attendees raising concerns about environmental risks and water usage.
    After
    Alberta Premier Danielle Smith and Technology Minister Nate Glubish are joining an online town hall about AI data centers, the third of four the province's government has organized.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2317. · a record · the summary of a news item

    Before
    Gov. Tina Kotek backed local data center moratoriums while stating Oregon lacks authority for a statewide ban. The headline indicates a policy position on data center development authority.
    After
    Oregon Gov. Tina Kotek said she supports local moratoriums on data centers but that the state lacks the authority for a statewide ban.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2318. · Meta Louisiana data center · the summary of a news item

    Before
    Gov. Landry announces Meta expansion in Richland Parish will be the world's largest data center, with $100 billion capital investment since 2024 and over $50 billion invested to date.
    After
    Louisiana Gov. Jeff Landry spoke about Meta's investment in the state through its Richland Parish data center, saying the foundation for what will become Louisiana's pivotal moment began with Meta.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2319. · Meta Louisiana data center · the summary of a news item

    Before
    Meta announces $40 billion expansion of Richland Parish AI data center to 5 gigawatts, raising total project investment to $50 billion with 2,600 construction and 1,000 operational jobs.
    After
    Meta's data center project in Richland Parish, Louisiana, now represents an investment of $50 billion.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2320. · Meta Louisiana data center · the summary of a news item

    Before
    Meta's Richland Parish data center under construction generates tax revenue boosting teacher bonuses to $50,000, up from $10,200 previously.
    After
    Teachers in Richland Parish, Louisiana, are getting bonuses of up to $50,000 from tax revenue tied to Meta's data center, and football coach Scott Wilcher said the bonus doubled his retirement.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2321. · Google West Memphis Data Center · the summary of a news item

    Before
    Google confirms it is behind West Memphis Project Pyramid data center on 1,178 acre property with five building campus through Groot LLC.
    After
    Google confirmed it is the developer of the West Memphis data center campus in Crittenden County, Arkansas, and Laurel Brown said Google will cover the full energy costs of powering it.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2322. · Google West Memphis Data Center · the summary of a news item

    Before
    West Memphis secured a $4 billion Google data center project, described as one of the biggest wins in state history. The project represents a major investment in Arkansas infrastructure.
    After
    Google is behind a $4 billion data center project in West Memphis, Arkansas.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2323. · Google West Memphis Data Center · the summary of a news item

    Before
    Photo gallery from Google's West Memphis Energy Impact Fund event on April 28, 2026, showing the announcement of first recipients of the community investment fund.
    After
    Google named the first recipients of the West Memphis Energy Impact Fund on April 28, 2026, at an event where Google's Katie Ottenweller spoke and Mayor Marco McClendon took part.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2324. · Google West Memphis Data Center · the summary of a news item

    Before
    Google, state and local officials marked the start of a $4 billion AI data center in West Memphis. The headline indicates a significant capital investment milestone for the project.
    After
    Google's AI data center project in West Memphis, Arkansas, carries a $4 billion cost.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2325. · Google West Memphis Data Center · the summary of a news item

    Before
    Entergy sues to block release of financial details on Google West Memphis data center and Arkansas Cypress solar project.
    After
    Entergy Arkansas filed a federal lawsuit seeking to restrict publication of information tied to Google's West Memphis data center, including financial details of the Arkansas Cypress Solar and Battery project.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2326. · Google West Memphis Data Center · the summary of a news item

    Before
    Google's 4 billion dollar West Memphis data center on 1,100 acres has begun construction with up to 300 jobs and community investments.
    After
    Construction on Google's $4 billion data center in West Memphis began in October 2025, and the West Memphis City Council approved up to $60 billion in industrial development bonds over 30 years.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2327. · a record · the summary of a news item

    Before
    A proposed data center in Colorado Springs off Garden of the Gods Road faced fierce backlash at a public meeting. Community opposition surfaced regarding the project's environmental and neighborhood impacts.
    After
    A data center proposed along Garden of the Gods Road in Colorado Springs met strong opposition at a public meeting.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2328. · a record · the summary of a news item

    Before
    Colorado lawmakers are preparing for significant legislative battles over AI data center development. The headline indicates major state level conflicts ahead over data center policy.
    After
    Colorado lawmakers are preparing for legislative battles over AI data centers, with Dan Diorio pointing to local tax revenue and jobs and Alana Miller calling for a strong framework to protect Coloradans.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2329. · Google West Memphis Data Center · the summary of a news item

    Before
    Opinion column draws historical parallels between Harvey Couch's 1926 vision of industrial development and current Silicon Valley data center expansion across Arkansas.
    After
    Guest columnist Guy Lancaster wrote that Silicon Valley billionaires want to build data centers across Arkansas, where Google has a $4 billion, 1,100 acre project near West Memphis.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2330. · Vantage Port Washington Data Center · the summary of a news item

    Before
    Cloverleaf Infrastructure, original developer of Port Washington hyperscale data center, funded $100K sculpture at Coal Dock Park, sparking community debate about priorities.
    After
    Cloverleaf Infrastructure, the original developer of the Port Washington data center before the project passed to Vantage, gave $100,000 for a sculpture at Coal Dock Park.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2331. · Vantage Port Washington Data Center · the summary of a news item

    Before
    Vantage topped out a second building at the OpenAI Lighthouse campus in Port Washington on June 26, 2026, marking another construction milestone. The headline alone confirms continued progress on the $15 billion data center project.
    After
    On June 26, 2026, Vantage topped out the second building on the Lighthouse campus in Port Washington, Wisconsin.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2332. · Vantage Port Washington Data Center · the summary of a news item

    Before
    Business Journals provided an exclusive behind the scenes look at Vantage Data Centers' massive Port Washington project. Without full text, specific details about the project status or developments cannot be determined from the headline alone.
    After
    Vantage Data Centers is the company behind the data center project in Port Washington, Wisconsin.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2333. · Vantage Port Washington Data Center · the summary of a news item

    Before
    The headline indicates a $15 billion data center project in Wisconsin involved OpenAI and Oracle, with farmers in the area becoming millionaires from land sales. Without the full text, specific figures and project details cannot be confirmed.
    After
    OpenAI and Oracle's data center in Wisconsin is a $15 billion project.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2334. · Vantage Port Washington Data Center · the summary of a news item

    Before
    Residents petitioned the Wisconsin Department of Natural Resources to deny an air pollution permit for the Port Washington data center project, citing environmental concerns. The headline indicates a regulatory proceeding affecting the data center.
    After
    Residents urged the Wisconsin Department of Natural Resources to refuse the Port Washington data center's air pollution permit.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2335. · Vantage Port Washington Data Center · the summary of a news item

    Before
    Vantage executive toured Virginia data center to demystify operations; Port Washington facility Lighthouse remains on track for 15 billion dollar investment and 4000 jobs.
    After
    Vantage forecasts $15 billion of investment and 4,000 construction jobs at its Port Washington facility, called Lighthouse, and expects 1,000 employees on site, counting customers Oracle and OpenAI.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2336. · a record · the summary of a news item

    Before
    Montgomery County Executive Marc Elrich signs executive order establishing six month moratorium on data center permit applications.
    After
    Marc Elrich, the Montgomery County Executive in Maryland, signed an order on June 12 pausing the acceptance and processing of data center permit applications for six months.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2337. · Montgomery Meta Investment · the summary of a news item

    Before
    Meta is building an $800 million AI data center in Alabama, its second facility in the state. The headline indicates a major capital investment and expansion in Alabama.
    After
    Meta is building a new data center in Alabama, an $800 million investment.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2338. · Montgomery Meta Investment · the summary of a news item

    Before
    Meta is piloting mass timber construction methods in a data center project. The headline suggests testing of a building material but does not name a specific project or location.
    After
    Meta is running a pilot using mass timber in the construction of its data centers.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2339. · a record · the summary of a news item

    Before
    Alabama regulators approved a two year electric rate freeze and two solar projects for a Meta data center. The action addresses power and renewable energy for the Montgomery campus.
    After
    The Alabama Public Service Commission approved two solar projects serving a Meta data center, along with a two year electric rate freeze.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2340. · Montgomery Meta Investment · the summary of a news item

    Before
    Meta is investing an additional $700 million into its Alabama data center facility. The headline alone indicates a major expansion to the project announced earlier in September 2025.
    After
    Meta plans to invest an additional $700 million in Alabama on top of its earlier investment in the state.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2341. · Montgomery Meta Investment · the summary of a news item

    Before
    Baldwin County community members are opposing the solar panel project planned to power Meta's Montgomery data center. Details of specific statements are not available from the headline alone.
    After
    Community members in south Alabama are opposing a solar farm project tied to the Montgomery data center.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2342. · Montgomery Meta Investment · the summary of a news item

    Before
    Meta announced plans to add two more buildings to its Alabama campus in Montgomery. The headline indicates an expansion of the existing data center project.
    After
    Meta plans to put up two additional buildings at its campus in Montgomery, Alabama.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2343. · Montgomery Meta Investment · the summary of a news item

    Before
    Meta launches $1 billion Future is for Everyone Fund to support data center communities including Montgomery, supporting schools and infrastructure.
    After
    Meta started a $1 billion fund for teachers, first responders, energy and water infrastructure and community needs where it owns and operates data centers, including Montgomery, Alabama.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2344. · DC Blox Montgomery data center · the summary of a news item

    Before
    DC Blox announces plans for $30 million data center at Interstate Industrial Park in Montgomery, with construction start scheduled for June 2027.
    After
    DC Blox announced a $30 million investment in Montgomery, a data center at the Interstate Industrial Park near the Hope Hull exit, with construction scheduled to start in June 2025.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2345. · Apple Prineville Campus · the summary of a news item

    Before
    Data centers will receive 450 million dollars in Oregon tax breaks this year, raising questions about whether the incentive policy is appropriate. The headline reflects ongoing debate about Oregon's data center tax incentive program.
    After
    Data centers in Oregon will receive tax breaks worth 450 million dollars this year.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2346. · a record · the summary of a news item

    Before
    Cheyenne LEADS clarified the number of data centres in Cheyenne and Laramie County according to a WyomingNews.com report. No details are available from the headline.
    After
    Cheyenne LEADS clarified how many data centers are in Cheyenne and Laramie County, Wyoming.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2347. · OpenAI Effingham County Data Center · the summary of a news item

    Before
    OpenAI plans a 3.2 GW data center campus in Effingham County, Georgia. The headline indicates a major capacity announcement for the Project Camellia facility.
    After
    A data center campus that OpenAI plans in Effingham County, Georgia, would have 3.2 GW of capacity.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2348. · OpenAI Effingham County Data Center · the summary of a news item

    Before
    OpenAI announced a $20 billion data center project in Effingham County, Georgia, sparking outrage among Coastal Georgia residents. The headline indicates community opposition to the project.
    After
    In Effingham County, Georgia, OpenAI has announced a $20 billion project to build a data center.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2349. · OpenAI Effingham County Data Center · the summary of a news item

    Before
    OpenAI announced plans to open a data center in Effingham County. The headline indicates the announcement of the Project Camellia data center.
    After
    OpenAI announced its plan for a data center in Georgia's Effingham County.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2350. · OpenAI Effingham County Data Center · the summary of a news item

    Before
    OpenAI announces $20 billion data center campus at Savannah Gateway Industrial Hub in Rincon; 400 permanent jobs and 1,400 acre facility planned.
    After
    OpenAI has chosen Effingham County, Georgia, for its first data center in the region, a project of about $20 billion in private capital expected to create 400 jobs.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2351. · OpenAI Effingham County Data Center · the summary of a news item

    Before
    Effingham County manager details OpenAI data center process. The manager outlined the municipal review steps required before construction can begin.
    After
    The Effingham County manager in Georgia laid out the process for the OpenAI data center.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2352. · OpenAI Effingham County Data Center · the summary of a news item

    Before
    Georgia Power's OpenAI contract in Effingham County approved, expected to lower residential bills.
    After
    The Georgia Public Service Commission approved a Georgia Power contract with OpenAI in Effingham County, a deal expected to lower bills for residential customers.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2353. · OpenAI Effingham County Data Center · the summary of a news item

    Before
    Georgia Power says OpenAI data center could bring $950 million in annual savings for customers and $15 monthly benefit from 2029.
    After
    Georgia Power says OpenAI will pay the full cost of the infrastructure needed to serve its Effingham County data center, whose contract the Georgia Public Service Commission approved.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2354. · OpenAI Effingham County Data Center · the summary of a news item

    Before
    OpenAI announced 20 billion dollar, 1400 acre data center campus in Effingham County; project required no rezoning due to existing industrial zoning and confidentiality agreements delayed public disclosure.
    After
    Effingham County Manager Tim Callanan said OpenAI's Project Camellia campus needed no rezoning because the Savannah Gateway site has been zoned industrial since 2006 and data centers are a permitted use there.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2355. · OpenAI Effingham County Data Center · the summary of a news item

    Before
    Georgia Public Service Commission approved Georgia Power's contract to serve OpenAI's 3200 megawatt data center in Effingham County, with expected residential bill savings.
    After
    Georgia Power's contract for OpenAI's Effingham County data center won Georgia Public Service Commission approval, and Matthew Kent said data centers pay mandatory minimums each month and put down collateral.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2356. · OpenAI Effingham County Data Center · the summary of a news item

    Before
    Georgia Power's contract to serve OpenAI's 3200 megawatt Effingham County data center received regulatory approval from the Georgia Public Service Commission.
    After
    The Georgia Public Service Commission approved Georgia Power's contract for OpenAI's Effingham County data center, and typical residential customers are expected to save about $15 per month starting in 2029.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2357. · OpenAI Effingham County Data Center · the summary of a news item

    Before
    Georgia PSC staff declined to object to Georgia Power's electricity contract for OpenAI's planned 3.2 GW Effingham County data center, clearing a major regulatory hurdle for the $20 billion project.
    After
    Georgia Power's contract to supply electricity to OpenAI's Effingham County data center, filed July 27, 2026, drew no objection from Georgia Public Service Commission staff.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2358. · OpenAI Effingham County Data Center · the summary of a news item

    Before
    OpenAI will cover school meal costs for all Effingham County students as a community benefit from the data center project.
    After
    OpenAI will pay school meal costs for every student in Effingham County, Georgia.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2359. · OpenAI Effingham County Data Center · the summary of a news item

    Before
    Georgia Public Service Commission approved Georgia Power's electricity contract to serve OpenAI's 3.2 GW Effingham County facility, with residential customer savings of $180 annually starting 2029.
    After
    The Georgia Public Service Commission has approved Georgia Power's contract to serve OpenAI's Effingham County data center, with typical residential customers expected to save $180 per year from 2029.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2360. · OpenAI Effingham County Data Center · the summary of a news item

    Before
    Effingham County commissioners held a Saturday work session where over 100 residents pressed officials over OpenAI's Project Camellia data center, raising concerns about power, water, noise and transparency.
    After
    At an Effingham County work session on Project Camellia, OpenAI's data center proposal, Commissioner Roger Burdette said he was wrong not to inform the community sooner.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2361. · OpenAI Effingham County Data Center · the summary of a news item

    Before
    Effingham County commissioners meet with 70 residents to address concerns about OpenAI data center noise, radiation, fire safety; construction planned 2028.
    After
    At an Effingham County workshop on August 29, Commissioner Beth Helmly said the county is under no timeline to approve OpenAI's proposed data center and committed to examining noise, radiation and battery fire safety.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2362. · OpenAI Effingham County Data Center · the summary of a news item

    Before
    OpenAI plans a 20 billion dollar data centre campus on 1400 acres in Effingham County, Georgia, with 3200 megawatts of power and 1000 jobs by 2032.
    After
    OpenAI proposes a $20 billion data center campus covering more than 1,400 acres on McCall Road in Effingham County, Georgia, that would use 3,200 megawatts supplied by Georgia Power.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2363. · a record · the summary of a news item

    Before
    Radio Canada reports on concerns about a data center bubble in Quebec. The headline suggests scrutiny of rapid data center development and potential market saturation.
    After
    In Quebec, concerns are emerging about the risk of a data center bubble.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2364. · Stratos Project · the summary of a news item

    Before
    Utah researchers testify to legislature on data center impacts: electricity costs vary by utility type, property taxes volatile as equipment depreciates, job creation modest at 106 per facility.
    After
    Shon Hiatt told a Utah interim committee on August 19, 2026 that data centers had no effect on prices at investor owned utilities like Rocky Mountain Power from 2020 to 2025.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2365. · a record · the summary of a news item

    Before
    Radio Canada reports on Quebec positioning itself as the new green data center destination. The headline frames Quebec's appeal to the sector.
    After
    Quebec is cast as a green haven for data centers, where Google has planned its first data center, a $735 million Canadian investment, and Microsoft has bought land.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2366. · a record · the summary of a news item

    Before
    Prince William County supervisors received nearly $300,000 in campaign donations, mostly from data center interests. The donations indicate data center industry engagement in local politics.
    After
    Prince William County supervisors in Virginia raised nearly $300,000 in campaign money, with $199,495 from data center companies, PACs funded by data center donations, and landowners and developers tied to such projects.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2367. · a record · the summary of a news item

    Before
    The Green Party called on Ontario government to pause all new AI data centres in the province. The statement represents a position by a political party on data centre policy.
    After
    The Green Party asked the Ontario government to put a pause on every new AI data center in the province.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2368. · a record · the summary of a news item

    Before
    A data centre proposal in Sault Ste. Marie, Ontario met with opposition. The headline indicates a specific project faces community resistance but lacks detail.
    After
    A proposal for a data center has been put forward in Sault Ste Marie, Ontario.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2369. · a record · the summary of a news item

    Before
    A motion to halt AI data centre proposals in Sault Ste. Marie was withdrawn before a vote. The action reflects local jurisdiction activity regarding data center development in the city.
    After
    In Sault Ste Marie, Ontario, a motion that would have halted AI data center proposals was withdrawn before a vote.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2370. · a record · the summary of a news item

    Before
    A New Brunswick minister stated that NB Power will not be blocked from selling electricity to AI data centres. The statement clarifies the province's regulatory stance on power sales.
    After
    A New Brunswick minister said NB Power will not be barred from selling power to AI data centers.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2371. · a record · the summary of a news item

    Before
    New Jersey residents defeated an AI data center proposal. The headline suggests a local rejection or withdrawal of a data center project.
    After
    Residents in New Jersey defeated an AI data center, casting the outcome as a message to Big Tech.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2372. · Monolith Data Center Expansion (Hallam) · the summary of a news item

    Before
    Hallam residents pack town hall for Monolith's proposed data center expansion. The high turnout indicates significant local engagement with the permitting process.
    After
    Residents of Hallam, Nebraska, held a town hall on Monolith's proposal to add a 35 megawatt data center and four more carbon black units at its Olive Creek facility.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2373. · a record · the summary of a news item

    Before
    Governor Pillen orders suspension of tax incentives for data center projects in Nebraska. The suspension is a significant change to state level incentive policy.
    After
    Gov. Jim Pillen orders a suspension of the tax incentives Nebraska gives data center projects, saying they are drawn to its available land, low electrical rates and abundant water.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2374. · a record · the summary of a news item

    Before
    A coalition argues that data centers should be regulated separately by the PSC. The item reports a policy position on regulatory treatment of the data center industry.
    After
    A coalition argued that the Montana Public Service Commission should regulate data centers separately, and Nick Fitzmaurice called for a dedicated data center customer class.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2375. · Quantica Broadview Data Center · the summary of a news item

    Before
    Yellowstone County commissioners refused to put a data center ballot measure on the November ballot despite collecting 14,980 signatures, citing a 2025 state law deadline change.
    After
    Yellowstone County commissioners in Montana took no action on a proposal to put a data center moratorium on the November 2026 ballot, whose signature deadline a 2025 legislative change had moved to July 13.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2376. · a record · the summary of a news item

    Before
    Montana voters seek oversight of data center construction, indicating public demand for regulatory control. The item reflects community engagement with data center development policy.
    After
    Voters in Montana are seeking oversight of how data centers are built, and Denise Kelley called a local ballot initiative the most direct way to protect wallets, water and way of life.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2377. · Oracle and OpenAI Saline Township Data Center · the summary of a news item

    Before
    Oracle and OpenAI's Saline Township data center, known as The Barn, is advancing construction at rapid pace.
    After
    The Barn, the Oracle and OpenAI data center on Braun Road in Saline Township, Michigan, was advancing quickly as of August 26, 2026.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2378. · Amazon / AWS Data Center Campus at Calvert Cliffs · the summary of a news item

    Before
    Amazon Web Services withdrew its application for a 2.5 million square foot data center adjacent to Calvert Cliffs Nuclear Power Plant in Maryland on August 4.
    After
    As of August 4, 2026, Amazon Web Services had withdrawn its application to build data centers in Calvert County, Maryland, beside the Calvert Cliffs Nuclear Power Plant, citing infrastructure priorities and development timelines.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2379. · a record · the summary of a news item

    Before
    Maine Data Center Advisory Council held public listening sessions; majority voiced concerns over water, energy, and environmental impacts; council reports to legislature in January 2027.
    After
    The Maine Data Center Advisory Council heard public concerns about data centers at two virtual listening sessions and is to give lawmakers a final report in January.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2380. · Meta Louisiana data center · the summary of a news item

    Before
    Meta data center in Richland Parish brings jobs and tax growth to northeast Louisiana. The facility contributes to local economic development.
    After
    Meta's Richland Parish data center is bringing jobs to northeast Louisiana and generating tax growth in the parish.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2381. · a record · the summary of a news item

    Before
    A Wyoming town of 66,000 residents expects to absorb 5,500 data center workers and locals report feeling powerless to stop the expansion. The report indicates community concerns about data center development scale and local control.
    After
    In Wyoming, a town of 66,000 is set to take in 5,500 data center workers, with residents saying they feel powerless to stop the expansion.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2382. · a record · the summary of a news item

    Before
    WyoFile published an opinion or report on water pollution caused by data center expansion in Wyoming. The headline indicates a claim linking data centers to environmental contamination.
    After
    Data centers operating in Wyoming have caused water pollution, according to WyoFile.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2383. · a record · the summary of a news item

    Before
    Trump and Wyoming residents disagree over whether data center opposition will leave communities poor and backwards. The headline reflects a political debate about data center development policy.
    After
    Trump characterized opponents of data centers as wanting to keep Wyoming backwards and poor.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2384. · a record · the summary of a news item

    Before
    Community and conservation groups asked courts to properly review challenges to data center permitting in West Virginia. The item reports legal action and court proceedings regarding data center project approval.
    After
    Courts in West Virginia have been asked by community and conservation groups to review challenges to the permitting of data centers.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2385. · a record · the summary of a news item

    Before
    A tax analysis report was released for two high profile data center projects in West Virginia. The report examines the tax implications and fiscal impact of these projects.
    After
    A tax analysis report on two West Virginia data center projects has been released.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2386. · Stratos Project · the summary of a news item

    Before
    Citizens filed formal protests against the Stratos project's water rights application in Box Elder County, Utah. The article addresses the steps involved in the formal protest process.
    After
    Formal protests were filed against the Stratos data center project's application for water rights in Box Elder County, Utah.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2387. · Stratos Project · the summary of a news item

    Before
    Box Elder County commissioners unanimously approved the Stratos project, a 40,000 acre hyperscale data center backed by Kevin O'Leary, designed to reach 9 gigawatt power capacity despite massive public opposition and concerns about water usage and carbon emissions.
    After
    The Stratos project, which Kevin O'Leary backs through O'Leary Digital, won unanimous approval from Box Elder County commissioners at a May 4 meeting they finished in closed session after leaving the room.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2388. · Stratos Project · the summary of a news item

    Before
    Kevin O'Leary addressed claims about his Utah data center project, expressing concern about AI competition with other countries and positioning his project as a national security measure. The headline indicates O'Leary's commitment to the project.
    After
    Kevin O'Leary of O'Leary Digital said that anyone who thinks they could beat "us" in AI has to be proven wrong.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2389. · Stratos Project · the summary of a news item

    Before
    Kevin O'Leary announced a 7.5GW Wonder Valley data center campus in Box Elder County, Utah, as a second project alongside his Alberta development for combined 15GW capacity. O'Leary Digital partnered with West GenCo for permitting and state level coordination.
    After
    Kevin O'Leary is planning a Wonder Valley data center campus of 7.5GW in Box Elder County, Utah, with West GenCo to oversee permitting and state regulatory coordination.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2390. · Stratos Project · the summary of a news item

    Before
    First images of the 60 building Stratos data center in Utah have been revealed by Dezeen. No details available from headline alone.
    After
    The design for the Stratos data center in Box Elder County, Utah, includes 60 buildings.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2391. · Stratos Project · the summary of a news item

    Before
    Residents continued to protest the Box Elder data center project, with local opposition to Kevin O'Leary's Stratos project. The headline indicates ongoing community resistance.
    After
    Residents are continuing to protest the Stratos data center project in Box Elder County, Utah.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2392. · a record · the summary of a news item

    Before
    Burgin residents spoke out on a proposed data center development. The headline indicates community input on a local data center project.
    After
    Residents of Burgin, Kentucky, spoke out about a proposed data center, and Bethany Corea said the annexation request for it was not brought to the council.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2393. · a record · the summary of a news item

    Before
    A data center developer in Kentucky is using a state law intended for housing development to advance a project. The headline indicates a jurisdictional or regulatory strategy in a Kentucky data center proposal.
    After
    A data center developer has relied on a Kentucky law intended to promote housing development.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2394. · Lex Developments Pocatello AI Data Center · the summary of a news item

    Before
    A data center project in Pocatello is the subject of ongoing coverage described as part three of a series. Details of the project status are not available from the headline alone.
    After
    Pocatello, Idaho, is the site of a data center project tied to Lex Developments.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2395. · a record · the summary of a news item

    Before
    Byron Donalds stated that Florida law will prevent electric bill hikes from data centers, though this outcome is not guaranteed. The claim questions the effectiveness of the law.
    After
    U.S. Representative Byron Donalds said Florida law ensures utility rates will not go up because of data centers, while Mark McNees said the statute does not deliver that outcome.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2396. · a record · the summary of a news item

    Before
    Florida enacted a law to protect consumers from data center costs. The law is being tested in practice regarding utility rate impacts.
    After
    A new Florida law is meant to shield consumers from costs tied to data centers.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2397. · a record · the summary of a news item

    Before
    Byron Donalds pledged to respect local data center bans if elected Florida governor. The statement indicates candidate positions on local autonomy over data center siting.
    After
    Byron Donalds, a candidate for Florida governor, pledged to respect local bans on data centers if he is elected.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2398. · a record · the summary of a news item

    Before
    The headline suggests data centers are becoming a political issue in Florida's governor's race. The item reports on candidate or voter positions on data center development.
    After
    Data centers are an issue in the Republican race for governor in Florida.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2399. · a record · the summary of a news item

    Before
    Delaware House passed bills intended to protect residents from data center energy costs. The legislation represents state action on data center impacts.
    After
    The Delaware House of Representatives passed bills meant to shield residents from energy costs tied to data centers.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2400. · a record · the summary of a news item

    Before
    A Connecticut town approved a two year ban on data center development. The action represents a temporary local moratorium on data center projects.
    After
    A town in Connecticut has approved a ban on data centers that will last two years.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2401. · a record · the summary of a news item

    Before
    Hartford Business Journal reports Connecticut is considering a bring your own power model for data center development. This indicates state level policy consideration affecting data center projects.
    After
    Connecticut is weighing an approach in which data center developers would bring their own power supply.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2402. · a record · the summary of a news item

    Before
    The article reports that data center controversies have transformed the midterm election landscape, with opposition uniting conservative and progressive communities. President Trump defends data centers as critical for AI competition with China and job creation.
    After
    Community opposition to data centers around the United States has reshaped the landscape of the midterm elections.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2403. · a record · the summary of a news item

    Before
    A judge is expected to strike down Imperial County's data center moratorium, according to KPBS. The ruling would overturn a local restriction on data center development.
    After
    A judge is poised to overturn the data center moratorium adopted by Imperial County, California.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2404. · a record · the summary of a news item

    Before
    California lawmakers passed bills targeting data center costs and AI chatbot safety. The item reports legislative passage of tech reform measures.
    After
    California lawmakers approved technology reforms aimed at data center costs and the safety of AI chatbots.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2405. · a record · the summary of a news item

    Before
    California passed bills requiring data centers to pay their own electricity costs. The legislation represents state action on data center operational expenses and utility policy.
    After
    California lawmakers passed bills requiring data centers to cover the costs of the electricity they use.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2406. · a record · the summary of a news item

    Before
    California is moving to hold big tech accountable in data center development. The state is implementing measures to regulate how technology companies develop data center projects.
    After
    California is taking steps to hold large technology companies accountable for data center development.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2407. · a record · the summary of a news item

    Before
    TVA announced it will raise data center rates affecting North Alabama facilities. The rate increase is a regulatory action affecting operational data centers.
    After
    The Tennessee Valley Authority plans to raise its rates for data centers, which would affect facilities in North Alabama.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2408. · a record · the summary of a news item

    Before
    Texas Governor Greg Abbott says data center developers dug their own grave by not winning local community support; explains data center moratorium requiring local approval.
    After
    Texas Gov. Greg Abbott said companies building data centers dug their own grave by failing to win local support, and his moratorium makes data centers get local approval before operating.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2409. · a record · the summary of a news item

    Before
    A regulatory loophole leaves Oklahoma data center water consumption largely untracked. The gap represents a jurisdictional issue affecting oversight of data center operations.
    After
    A loophole in Oklahoma's regulations means the water that data centers in the state consume is largely not tracked.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2410. · a record · the summary of a news item

    Before
    A Nevada town engaged in a dispute with the Trump administration over a data center project. The nature of the conflict is unclear from the headline alone.
    After
    A Nevada town and the Trump administration are in a dispute over a data center.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2411. · a record · the summary of a news item

    Before
    Nevada's Public Utilities Commission denied a public session on NV Energy's data center related resource plan. Advocates protested the decision.
    After
    The Public Utilities Commission of Nevada declined to hold a public session about NV Energy's resource plan, which is driven by data centers.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2412. · a record · the summary of a news item

    Before
    Nevada lawmakers plan to introduce a bill to scale back data center tax breaks. The proposed legislation would reduce tax incentives for data center projects.
    After
    Lawmakers in Nevada intend to introduce a bill that would reduce the tax breaks given to data centers.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2413. · a record · the summary of a news item

    Before
    Storey County, a hub for Nevada data centers, is seeking to rein in state tax breaks. The full text is unavailable but the headline indicates local jurisdiction action on data center taxation policy.
    After
    Storey County, a hub for data centers in Nevada, is weighing steps to curb the state tax breaks they receive.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2414. · a record · the summary of a news item

    Before
    Governor Abbott has ordered a pause on data center approvals in Texas. The action signals regulatory concern about data center development pace.
    After
    Texas Governor Abbott ordered that approvals of data centers in the state be paused.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2415. · a record · the summary of a news item

    Before
    Senator Fetterman joins Trump's embrace of data centers. The specific position or actions are not detailed in the headline.
    After
    Senator Fetterman of Pennsylvania has taken a position in favor of data centers.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2416. · a record · the summary of a news item

    Before
    An Ohio city illegally blocked a citizen effort to stop a data center development. The action raises legal questions about data center opposition and municipal oversight.
    After
    An Ohio city unlawfully blocked an effort by citizens to stop a data center.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2417. · OpenAI Effingham County Data Center · the summary of a news item

    Before
    Georgia Power extended the deadline for the Public Service Commission to consider its contract with data center operator OpenAI. The PSC decision affects power supply for a planned data center.
    After
    Georgia Power extended the deadline for the Georgia Public Service Commission to take up its contract with OpenAI.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2418. · Oakline at Mill Creek · the summary of a news item

    Before
    A 75 acre data center is proposed in Salem. The headline indicates a new project development but details are not readable.
    After
    A data center on 75 acres is proposed in Salem, Oregon, and Nelson Abraham said the company wants to address complaints about noise, air quality and water use.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2419. · a record · the summary of a news item

    Before
    Washington state data centers use 40% of Grant County's electricity despite the state requiring utilities to go carbon neutral by 2030. Investigative reporting shows data centers have not created the promised jobs and that Washington's renewable energy percentage has declined since 2004.
    After
    Data centers use about 40% of the electricity in Grant County, Washington, a state that had about 87 data centers in July 2024.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2420. · a record · the summary of a news item

    Before
    Governor Tina Kotek's seven member data center advisory committee decided against recommending a statewide moratorium on data centers, despite local action and calls from Democrats, conservation groups, and residents. The committee will instead recommend state local partnerships and transparency requirements to the legislature for the 2027 session.
    After
    In Oregon, Gov. Kotek's advisory committee on data centers will not recommend a statewide moratorium, and it will call for more state and local partnerships and more transparency from industry.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2421. · phoenix-data-center-firm-repurposing-portfolio-az · the summary of a news item

    Before
    Copia Power seeks rezoning for 3,100 acre Belmont Energy Center combining solar generation, gas facility, battery storage, and data centers near Tonopah, Arizona.
    After
    Copia Power is asking to rezone about 3,100 acres near Tonopah, Arizona, for the Belmont Energy Center, with about 320 acres planned for gas generation, battery storage and data centers.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2422. · Meta Louisiana data center · the summary of a news item

    Before
    Meta's Hyperion supercluster in Louisiana has seen its cost increase from $10 billion to $50 billion in under two years, dividing the community. The project involves tax incentives and impacts on local residents.
    After
    The cost of Meta's Hyperion supercluster in Richland Parish, Louisiana, climbed to $50 billion from $10 billion in less than 2 years.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2423. · Chicago Quantum Park · the summary of a news item

    Before
    FOX Chicago reports Illinois is the third largest data center market in the country and profiles the Illinois Quantum and Microelectronics Park, which has generated both support and concerns.
    After
    Illinois ranks as the country's third biggest data center market, and the Illinois Quantum and Microelectronics Park there focuses on quantum technology.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2424. · a record · the summary of a news item

    Before
    Kentucky Governor Andy Beshear issued an executive order directing state regulators to protect against harmful impacts of data centers through stricter environmental and utility oversight. The order sets conditions on energy costs, environmental impact, and tax payments before development is allowed.
    After
    Kentucky Governor Andy Beshear's executive order directs state regulators to deny permits for data center sites that would harm air or water quality and to refuse rate increases for data center costs.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2425. · a record · the summary of a news item

    Before
    Four Oregon Democratic lawmakers and two candidates backed a three year moratorium on new large data centers to be proposed during the 2027 legislative session, citing concerns over energy, water, farmland, and transparency. Oregon would join 15 other states that have proposed data center moratoriums.
    After
    Oregon state senators Jeff Golden and Courtney Neron Misslin and representatives Lesly Muñoz and Farrah Chaichi want a moratorium on new data centers for three years, proposed in the 2027 legislative session.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2426. · a record · the summary of a news item

    Before
    Texas has paused data centre development while Ontario's Premier Doug Ford is accelerating it. The headline compares different regional approaches to data centre policy.
    After
    Ontario Premier Doug Ford is moving data center development forward while Texas has paused it.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2427. · a record · the summary of a news item

    Before
    AI data centres could reshape Toronto's electricity grid, with questions about cost responsibility. The item discusses infrastructure impacts of data center development.
    After
    The electricity grid that serves Toronto, Ontario, could be reshaped by AI data centers.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2428. · a record · the summary of a news item

    Before
    Ontario states that AI data centres must pay their own power costs. The government statement establishes policy regarding data center operational expenses.
    After
    The Ontario government says AI data centers must cover the cost of their own electricity.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2429. · a record · the summary of a news item

    Before
    Advocates claim there are huge gaps in Doug Ford's data centre plan and suggest tech companies could pay higher electricity rates. The statement reflects criticism of provincial policy on data centers.
    After
    Advocates say Doug Ford's data center plan in Ontario has large gaps, and tech companies could pay a higher electricity rate.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2430. · Montgomery Meta Investment · the summary of a news item

    Before
    A report claims Alberta power prices could spike because of Meta's data centre; Meta disputes the claim. The report raises concerns about electricity cost impacts from the project.
    After
    Meta disputes a report's claim that its data center could cause power prices in Alberta to spike.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2431. · a record · the summary of a news item

    Before
    Alberta is pursuing AI data centre development and this push is affecting traditional political alignments. The headline indicates political debate over the strategy.
    After
    Alberta's pursuit of AI data center development is affecting political lines in the province.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2432. · a record · the summary of a news item

    Before
    Alberta government held a second AI data centre town hall in Sturgeon County. The event reflects ongoing public consultation on data centre policy.
    After
    In Sturgeon County, an Alberta minister held a second town hall on AI data centers.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2433. · a record · the summary of a news item

    Before
    A report stated Alberta data centre could cause power bills to spike. Analysis highlights electricity cost concerns from data centre development in the province.
    After
    A data center in Alberta could lead to a spike in power bills there.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2434. · a record · the summary of a news item

    Before
    Pembina Institute released a report estimating Alberta data centre could add up to $460 to electricity bills. The analysis raises concerns about cost impacts from data centre power consumption.
    After
    The Pembina Institute estimates a data center in Alberta could raise electricity bills by as much as $460.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2435. · a record · the summary of a news item

    Before
    A commentary argues that AI data centre opposition elsewhere creates opportunity for Alberta. Yogi Schulz presents a perspective on Alberta's competitive advantage in attracting data centre investment.
    After
    Commentator Yogi Schulz argues that opposition to AI data centers elsewhere opens an opportunity for Alberta.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2436. · a record · the summary of a news item

    Before
    New Hampshire is addressing data centers through state policy. The headline suggests state level action or decision on data center regulation.
    After
    The state government of New Hampshire has reached a decision on data centers.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2437. · a record · the summary of a news item

    Before
    The Nebraska governor signed an executive order halting tax incentives for data center developers. The order restricts financial support for the industry statewide.
    After
    Nebraska Governor Jim Pillen signed an executive order that halts tax incentives for companies developing data centers.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2438. · a record · the summary of a news item

    Before
    Governor Pillen rescinded ImagiNE Act tax incentives for new Nebraska data centers. The state removed financial incentives for data center development.
    After
    Nebraska Governor Pillen has rescinded tax incentives under the ImagiNE Act for new data centers in the state.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2439. · Quantica Broadview Data Center · the summary of a news item

    Before
    A proposed 5,000 acre AI data center near Broadview is raising questions from residents. The project's announcement prompted resident concerns about the development.
    After
    Residents have raised questions about a proposal for an AI data center covering 5,000 acres near Broadview, Montana.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2440. · Quantica Broadview Data Center · the summary of a news item

    Before
    A proposed AI data center near Broadview could use natural gas as a power source. The developer is exploring fuel options for the facility.
    After
    Natural gas could serve as a power source for an AI data center proposed near Broadview, Montana.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2441. · a record · the summary of a news item

    Before
    Montana residents are taking data center regulation into their own hands. The article describes grassroots efforts to control data center development statewide.
    After
    Some residents of Montana are taking it upon themselves to regulate data centers.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2442. · Jackson Lake Hico Data Center · the summary of a news item

    Before
    A judge questioned Jackson officials about Lake Hico data center discussion in Mississippi. The item indicates legal or official scrutiny of the project's status or proceedings.
    After
    A judge questioned officials in Jackson, Mississippi, about the discussion of a data center at Lake Hico.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2443. · Amazon Canton Data Centers · the summary of a news item

    Before
    Amazon announced plans to invest $25 billion in Mississippi data centers and create 2,000 jobs. The investment and job creation figure indicate significant project activity.
    After
    Amazon plans to put $25 billion into data centers in Mississippi and says the investment will create 2,000 jobs.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2444. · Compass Datacenters Meridian · the summary of a news item

    Before
    Meridian Community College launched Mississippi's first data center workforce training program. The program represents institutional support for data center industry workforce development.
    After
    Meridian Community College has launched a training program for data center workers, which the college calls the first in Mississippi.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2445. · Compass Datacenters Meridian · the summary of a news item

    Before
    Compass Datacenters and Meridian Community College launched Mississippi's first data center workforce training program on July 31, 2026. The program provides worker training for the data center industry.
    After
    On July 31, 2026, Meridian Community College and Compass Datacenters launched a training program for data center workers that they call the first in Mississippi.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2446. · xAI Southaven turbine site · the summary of a news item

    Before
    SpaceXAI shut off 11 temporary turbines powering Southaven data center and will remove all 69 by July 2027 when permanent 1.2 GW power plant becomes operational.
    After
    SpaceXAI has an agreement with the Mississippi Department of Environmental Quality to remove all 69 temporary turbines powering its Southaven data center by July 2027.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2447. · a record · the summary of a news item

    Before
    Michigan regulators ordered I&M to address data center reliability risks but failed to fill the gap in regulation of data center infrastructure.
    After
    Michigan regulators ordered Indiana Michigan Power to address reliability risks from data centers but, in the view of the Union of Concerned Scientists, did not fill a gap in data center regulation.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2448. · Boston Neighborhood Data Center · the summary of a news item

    Before
    Everett moves to rein in data centers as pushback grows across Massachusetts. The city is taking regulatory action in response to growing opposition to data center development.
    After
    Everett, Massachusetts, is taking steps to limit data centers while opposition to them grows around the state.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2449. · Markley Group Lowell Data Center · the summary of a news item

    Before
    Lowell residents file Massachusetts' first lawsuit against a data center. The litigation signals organized local opposition to a project.
    After
    Residents of Lowell, Massachusetts, have filed suit against a data center, the first such lawsuit in the state.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2450. · a record · the summary of a news item

    Before
    A Maryland county has adopted a two year moratorium on data center development. This is a jurisdictional action regulating data center projects.
    After
    A county in Maryland has adopted a moratorium that pauses data center development for two years.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2451. · a record · the summary of a news item

    Before
    West Virginia's plan to support data center development includes elimination of state income tax. This is a state level policy initiative affecting data center taxation.
    After
    A West Virginia plan in support of data center development includes eliminating the state's income tax.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2452. · a record · the summary of a news item

    Before
    The headline references West Virginia's revenue model as outdated relative to data center development, with a phrase suggesting taxation policy issues. This reflects analysis of state fiscal policy relative to data centers.
    After
    Data centers in West Virginia are outpacing the state's revenue model, which is described as outdated.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2453. · a record · the summary of a news item

    Before
    Residents of Mason County, West Virginia reacted to a second data center project coming to the area. The headline indicates community response to multiple data center developments.
    After
    Mason County in West Virginia is getting a second data center project.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2454. · a record · the summary of a news item

    Before
    A North Dakota senator advocates for a one year pause on data center development, expressing concern that the state could become a wasteland. The senator's name is not identified in the headline.
    After
    A North Dakota senator is seeking to pause data center development for one year and has voiced concern that data centers could make the state a wasteland.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2455. · a record · the summary of a news item

    Before
    An article addresses questions about whether data centers in North Dakota would increase electrical bills, water use, and noise levels. No specific numbers or answers are evident from the headline.
    After
    Data centers could raise electric bills in North Dakota and add to water use and noise.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2456. · a record · the summary of a news item

    Before
    Data centers in North Dakota have received millions of dollars in sales tax breaks from the state. The figure documents the fiscal incentive the state has provided to the industry.
    After
    North Dakota's data centers have been granted millions of dollars in sales tax breaks.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2457. · a record · the summary of a news item

    Before
    State Senator Kristen Gonzalez urged Governor Hochul to sign a data center bill. The bill's content and status are unclear from the headline.
    After
    New York State Senator Kristen Gonzalez called on Governor Kathy Hochul to sign the Responsible Data Center Development Act into law.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2458. · a record · the summary of a news item

    Before
    New York is restricting data centers, according to The New York Times. The specific restrictions and their scope are not detailed in the headline.
    After
    The state of New York is putting restrictions in place on data centers.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2459. · a record · the summary of a news item

    Before
    New Jersey's governor signed a law requiring data centers to report energy and water use. This establishes a new statewide regulatory requirement for data center operators.
    After
    The governor of New Jersey signed a law under which data centers in the state must report their energy and water use.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2460. · a record · the summary of a news item

    Before
    New Jersey enacted a law requiring data centers to disclose energy and water consumption. The legislation mandates transparency on resource use by facilities.
    After
    A New Jersey law requires data centers in the state to disclose how much energy and water they use.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2461. · Stratos Project · the summary of a news item

    Before
    Kevin O'Leary discussed the Box Elder County data center and pushed back against misinformation surrounding the project. No details are available from the headline alone.
    After
    Kevin O'Leary talked about the data center in Box Elder County, Utah, and pushed back against what he described as misinformation.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2462. · a record · the summary of a news item

    Before
    Governor Healey releases expectations for responsible data center development in Massachusetts. The guidance sets state policy parameters for future projects.
    After
    Massachusetts Governor Healey released expectations for the responsible development of data centers in the state.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2463. · a record · the summary of a news item

    Before
    Louisville Democratic Socialists of America campaign pushes for hyper scale AI data center ban. This represents organized advocacy for local regulation restricting data center development.
    After
    In Louisville, Kentucky, a DSA campaign is calling for a ban on hyperscale AI data centers.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2464. · a record · the summary of a news item

    Before
    Governor Beshear issued an executive order to protect Kentuckians from data center harmful impacts. The order reflects state action on data center regulation.
    After
    Kentucky Governor Andy Beshear issued an executive order whose stated aim is to protect Kentuckians from harmful impacts of data centers.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2465. · a record · the summary of a news item

    Before
    Winchester voted unanimously to pause data center development for one year. The action reflects local regulatory control over data center projects.
    After
    Winchester, Kentucky, voted unanimously for a one year pause on data center development.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2466. · a record · the summary of a news item

    Before
    Governor Beshear indicated he would support rolling back Kentucky's data center tax breaks. The statement reflects state policy reconsideration on data center incentives.
    After
    Kentucky Governor Andy Beshear said he would support rolling back the state's tax breaks for data centers.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2467. · a record · the summary of a news item

    Before
    Kentucky Governor Andy Beshear called for ending state tax incentives for data centers, according to Louisville Public Media. The statement signals potential change in state policy on data center subsidies.
    After
    Kentucky Governor Andy Beshear said the state should stop giving tax incentives to data centers.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2468. · a record · the summary of a news item

    Before
    Commonwealth Economics Partners released a study via NetChoice saying data centers would deliver hundreds of millions in tax revenue for Kentucky communities. The study projects significant economic benefits from data center development.
    After
    A study by Commonwealth Economics Partners says data centers would bring Kentucky communities hundreds of millions of dollars in tax revenue.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2469. · a record · the summary of a news item

    Before
    Louisville Public Media reports hyperscale data centers in Kentucky have provoked bipartisan outrage. The headline indicates political opposition to data center development in the state.
    After
    Hyperscale data centers have drawn anger from members of both parties throughout Kentucky.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2470. · a record · the summary of a news item

    Before
    A Kentucky city is considering seizing land to protect drinking water supply from a data center project. The action addresses water resource concerns posed by the facility.
    After
    A Kentucky city may seize land in order to protect its drinking water from a data center.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2471. · a record · the summary of a news item

    Before
    Trump called cities opposed to data centers backwards and poor; Kentucky politicians pushed back on the characterization. The exchange involves political statements about data center opposition.
    After
    Politicians in Kentucky pushed back after Trump described cities that oppose data centers as backwards and poor.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2472. · a record · the summary of a news item

    Before
    EPIC discussed a new Kentucky data center report. The headline indicates an organization made a statement or took action regarding data center analysis in the state.
    After
    EPIC talked about a new report that looks at data centers in Kentucky.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2473. · a record · the summary of a news item

    Before
    Trump faced backlash in Kentucky over data center comments, per WHAS11. The headline indicates controversy over his position on a data center project or policy.
    After
    In Kentucky, Trump drew a backlash over comments he made about data centers.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2474. · a record · the summary of a news item

    Before
    Trump made comments about data center critics, saying they want to be backwards and poor, drawing bipartisan rebuke in Kentucky. His statement on data center opposition is reported as controversial.
    After
    Trump described critics of data centers as wanting to be backwards and poor.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2475. · a record · the summary of a news item

    Before
    A WSJ article reports on residents who rejected a $26 million offer from an AI data center developer. The headline indicates a notable sum offered in negotiations over a data center project.
    After
    An offer of $26 million was made to residents by an AI data center developer.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2476. · a record · the summary of a news item

    Before
    Two large data centers are coming to Kuna, Idaho, and an article examines their water use. The headline indicates approval or announcement of two projects in the Kuna area.
    After
    Plans call for two large data centers to be built in Kuna, Idaho.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2477. · a record · the summary of a news item

    Before
    Palm Beach County is considering a one year freeze on data center projects. The proposal represents a jurisdiction level action to temporarily restrict data center development.
    After
    Palm Beach County, Florida, is considering whether to freeze data center projects for one year.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2478. · a record · the summary of a news item

    Before
    The Real Deal reported on the developers behind Florida's most controversial hyperscale data center projects. The article examines key players in contested data center development.
    After
    Florida is home to several hyperscale data center projects that have stirred public debate.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2479. · a record · the summary of a news item

    Before
    Byron Donalds, a Florida politician, said AI data centers help Elon Musk and Florida compete in the commercial space race. The statement supports data center development.
    After
    Florida politician Byron Donalds said AI data centers are helping both Florida and Elon Musk win the commercial space race.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2480. · a record · the summary of a news item

    Before
    Florida data center lawyers are advocating for new rules to keep development responsible. The specific rules and projects are not described in the headline.
    After
    Lawyers who work on data centers in Florida said they hope new rules will keep responsible development on track.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2481. · a record · the summary of a news item

    Before
    A new data center is proposed for western St. Lucie County near Interstate 95 in Florida. The location and developer are not identified in the headline.
    After
    A data center has been proposed near Interstate 95 in the western part of St. Lucie County, Florida.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2482. · a record · the summary of a news item

    Before
    North Port considers a pause on data center development as residents voice concerns. The city council is reviewing the policy in response to community opposition.
    After
    North Port, Florida, is weighing whether to pause data center development, and residents have voiced concerns about such projects.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2483. · a record · the summary of a news item

    Before
    David Jolly said the vast majority of Floridians oppose new data centers. Polls back that up.
    After
    David Jolly, a Florida politician, said a vast majority of people in the state oppose new data centers, and polls show most Floridians do.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2484. · a record · the summary of a news item

    Before
    A new bill was introduced to shield Delaware residents from high electric rates tied to data centers. The legislation addresses state level regulation of data center energy impacts.
    After
    A bill introduced in Delaware seeks to protect the state's residents from high electric rates linked to data centers.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2485. · a record · the summary of a news item

    Before
    Spotlight Delaware reports on a bill that would allow Delaware Electric Cooperative to reject data centers. The legislation would give the utility veto power over data center connections.
    After
    A bill proposed in Delaware would give the Delaware Electric Cooperative the power to reject data centers.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2486. · a record · the summary of a news item

    Before
    Meyer signed laws restricting future data center energy use in Delaware. The legislation imposes new energy consumption limits on data center projects.
    After
    Meyer signed laws in Delaware that place restrictions on the energy use of future data centers.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2487. · a record · the summary of a news item

    Before
    Bristol City Council asked the Zoning Commission to roll back data center rules. The action signals potential loosening of local data center restrictions.
    After
    Bristol's City Council in Connecticut asked that the Zoning Commission roll back the city's rules on data centers.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2488. · a record · the summary of a news item

    Before
    A study reports that data centers use more water than California cities. The item cites a finding about data center water consumption.
    After
    Data centers were found to use more water than cities in California.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2489. · a record · the summary of a news item

    Before
    Data center developers are showing interest in Riverbank, California and a project has emerged. The headline indicates early stage interest and rumored activity.
    After
    Data center developers have shown interest in Riverbank, California, where a project is taking shape.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2490. · a record · the summary of a news item

    Before
    Data centers have become a political issue in California's CEQA reform debate. The headline indicates public opposition is influencing state level environmental legislation.
    After
    Data centers have become a topic in the debate over a measure to reform the California Environmental Quality Act.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2491. · a record · the summary of a news item

    Before
    Records revealed a planned data center site in Miller County north of Texarkana, Arkansas. The site location became public through records disclosure.
    After
    A site north of Texarkana in Miller County, Arkansas, is planned for a data center.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2492. · a record · the summary of a news item

    Before
    Data center energy requests face skepticism or opposition. The headline indicates concerns about power requirements for data center projects.
    After
    Data center requests for electricity face doubt, and Thomas Gleeson of the Texas Public Utility Commission said that not knowing what is real means not knowing how to build the infrastructure.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2493. · DeepGreen Western Passage Underwater AI Data Center · the summary of a news item

    Before
    A Needham developer proposes underwater AI data centers off the Maine coast. The proposal is at an early stage with limited public details available.
    After
    A developer based in Needham has proposed placing AI data centers underwater off the coast of Maine.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2494. · a record · the summary of a news item

    Before
    A data center developer bought the Star Tribune's shuttered North Loop printing plant in Minneapolis. The acquisition signals site approval for conversion to a data center.
    After
    A data center developer signed an agreement to buy the Star Tribune's closed printing plant in the North Loop of Minneapolis.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2495. · a record · the summary of a news item

    Before
    Cities in Kansas are suing residents over petitions to ban data centers. The lawsuits represent jurisdictional conflict over efforts to block data center development.
    After
    Cities in Kansas are taking residents to court over petitions that seek to ban data centers.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2496. · a record · the summary of a news item

    Before
    Experts said Kansas communities can learn from painful data center lessons in other states. The statement documents expert commentary on data center policy implications.
    After
    Experts said communities across Kansas can learn from the painful lessons other states have had with data centers.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2497. · a record · the summary of a news item

    Before
    Berkshire CEO Abel said the AI data center boom is a major opportunity for the company's energy unit. The statement reflects executive views on data center growth benefits.
    After
    Berkshire's chief executive, Abel, said the growth of AI data centers offers a major opportunity to the company's energy unit.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2498. · a record · the summary of a news item

    Before
    Arthur residents question PathOne's data center plans in their community. Local opposition to a data center proposal by PathOne is documented.
    After
    PathOne Data Centers plans a data center in Arthur, in Ida County, Iowa.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2499. · a record · the summary of a news item

    Before
    Rob Sand announced a plan to hold big corporations and data centers accountable in Iowa. The statement marks a political position on data center regulation.
    After
    Rob Sand laid out a plan to hold data centers and big corporations accountable, saying as governor he would make sure anyone building in Iowa is contributing to Iowa rather than extracting from it.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2500. · a record · the summary of a news item

    Before
    Proposed data centers in Alabama could use more electricity than all Alabama homes combined. The report raises questions about cost allocation among consumers.
    After
    Data centers proposed in Alabama could draw more electricity than all of the state's homes use combined.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2501. · a record · the summary of a news item

    Before
    Alabama Attorney General Marshall told Fox Business that Alabama is on the forefront of keeping data center costs off consumers' bills. The statement indicates state policy focus on consumer protection related to data center power costs.
    After
    Alabama Attorney General Marshall said the state is a leader in keeping consumers from paying data center costs on their bills.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2502. · a record · the summary of a news item

    Before
    Doug Jones questioned Tommy Tuberville's stock trades and data center stance. The dispute reflects political disagreement over data center policy in Alabama.
    After
    Doug Jones raised questions about Tommy Tuberville's position on data centers and about his trades in stocks.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2503. · a record · the summary of a news item

    Before
    Britt stated Congress should turn Trump's data center pledge into law. This is a named figure making a claim about data center policy.
    After
    Britt said Congress should write Trump's pledge on data centers into law.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2504. · a record · the summary of a news item

    Before
    Claremore, Oklahoma addresses community concerns over a data center project. The specific project details are not available from the headline alone.
    After
    The city of Claremore, Oklahoma, responded to concerns from residents about a data center project there.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2505. · a record · the summary of a news item

    Before
    A hearing for Project Jupiter data center's air quality permit application has been rescheduled to September. The permit review proceeding continues in a permitting process.
    After
    The hearing on the air quality permit application for the Project Jupiter data center in New Mexico was moved to September 2026.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2506. · a record · the summary of a news item

    Before
    Concerns about water usage are raised as a large data center moves into the New Mexico desert. Water availability is a central issue for the regional project.
    After
    A large data center coming to the New Mexico desert is raising concerns about water.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2507. · a record · the summary of a news item

    Before
    Green Data faced additional regulatory setbacks. The headline indicates ongoing constraints on the data center developer's projects in New Mexico.
    After
    Green Data has faced constraints from regulators in the state of New Mexico.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2508. · a record · the summary of a news item

    Before
    U.S. Representative Stansbury called on New Mexico agencies to provide Project Jupiter water information. The representative demanded transparency on water use for the data center project.
    After
    U.S. Representative Stansbury asked New Mexico state agencies to share information on water for Project Jupiter.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2509. · a record · the summary of a news item

    Before
    New Mexico State Investment Council is capturing data center gains while addressing community concerns. The agency is pursuing data center development with attention to local impacts.
    After
    The New Mexico State Investment Council said it is capturing gains from data centers while responding to community concerns.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2510. · a record · the summary of a news item

    Before
    The contested hearing officer for Project Jupiter air quality permit hearing recused himself from the proceedings. The recusal affects the administrative process for the data center's environmental permit.
    After
    The hearing officer for the air quality permit hearing on Project Jupiter in New Mexico, who had been challenged, recused himself.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2511. · a record · the summary of a news item

    Before
    Project Jupiter data center faces criticism over water allocation in New Mexico. The massive project is subject to concerns from stakeholders regarding its impact on state water resources.
    After
    Project Jupiter, a data center in New Mexico, faces criticism over its water allocation, and Congresswoman Melanie Stansbury called for an inquiry into its long term water use.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2512. · a record · the summary of a news item

    Before
    An opinion piece argues data centers belong in Nevada's economic future. The article presents an advocacy position on data center development in the state.
    After
    A case was made for data centers as part of Nevada's economic future.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2513. · a record · the summary of a news item

    Before
    The Daily Collegian reports on booming data center development in Pennsylvania and how it is being opposed and regulated. Specific projects and regulations are not named in the headline.
    After
    Development of data centers is growing at a rapid pace across Pennsylvania.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2514. · a record · the summary of a news item

    Before
    Spotlight PA reports that bad actors can still skirt Governor Shapiro's new data center rules, but he is betting they won't. The specific rules and enforcement mechanisms are not detailed.
    After
    Pennsylvania Governor Shapiro issued a new set of rules for data centers in the state.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2515. · a record · the summary of a news item

    Before
    An opinion in The Morning Call calls for Pennsylvania to implement a mandatory data center moratorium. The author and specific jurisdiction are not identified in the headline.
    After
    A call was made for Pennsylvania to put a mandatory moratorium on data centers in place.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2516. · a record · the summary of a news item

    Before
    OpenAI has locked in a lease for a major data center in Ohio with backing from Nvidia. The deal signals a new data center commitment in the state.
    After
    OpenAI secured a lease for a data center in Ohio, a project Nvidia is backing.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2517. · a record · the summary of a news item

    Before
    NVIDIA guaranteed its compute capacity exclusively for SB Energy's PORTS Pike Technology Campus in Ohio. The commitment indicates the project will host NVIDIA AI infrastructure.
    After
    NVIDIA issued a guarantee for a technology campus in Pike County, Ohio, that is to host NVIDIA AI compute exclusively.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2518. · a record · the summary of a news item

    Before
    A data center developer plans to build a natural gas power plant near an Ohio lake town. The project would provide on site power generation for the facility.
    After
    Plans for a data center project in Ohio include a power plant fueled by natural gas near a lake town.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2519. · a record · the summary of a news item

    Before
    Cincinnati Enquirer reports OpenAI plans to build the world's biggest AI data center in Ohio. The project represents a major new data center development in the state.
    After
    OpenAI plans to build an AI data center in Ohio that would be the largest of its kind in the world.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2520. · a record · the summary of a news item

    Before
    The City of Statesville is considering a proposed data center moratorium. The action reflects growing local scrutiny of data center development.
    After
    The city of Statesville, North Carolina, is weighing a proposed moratorium on data centers.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2521. · a record · the summary of a news item

    Before
    Data centers may face new tariffs next year in Duke Energy's North Carolina region. The potential rate change would affect operating data center costs.
    After
    Data centers in the part of North Carolina served by Duke Energy could be subject to new tariffs starting next year.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2522. · a record · the summary of a news item

    Before
    A report examines what data centers get wrong about land, with a headline referencing a $26 million figure. The item addresses a financial or cost aspect of data center development.
    After
    A sum of $26 million is tied to land issues involving data centers in North Carolina.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2523. · a record · the summary of a news item

    Before
    The Cato Institute claims Senator Wyden's AI tax could push data center tax rates above 100 percent. The analysis comments on federal tax policy implications for the data center industry.
    After
    The Cato Institute said an AI tax from Senator Wyden could push tax rates on data centers above 100 percent.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2524. · a record · the summary of a news item

    Before
    A developer filed a letter of intent for a 130 acre multi billion dollar data center campus in Greenfield, Indiana. The filing indicates early stage proposal for a large facility.
    After
    A developer submitted a letter of intent to build a multibillion dollar data center campus on 130 acres in Greenfield, Indiana.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2525. · a record · the summary of a news item

    Before
    Indiana power provider proposes 59 million dollar rate cut, stating that data centers and other large customers are driving increased revenue. The move could save residential users 100 dollars annually.
    After
    An Indiana power provider proposed a 59 million dollar rate cut that could save residential customers 100 dollars a year and said large customers such as data centers are increasing its revenue.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2526. · a record · the summary of a news item

    Before
    A news segment reports on data center drama and power outage chaos alongside Illinois film industry impacts. The exact nature of the discussion cannot be determined from the headline alone.
    After
    Illinois has seen disputes over data centers as well as disruption from power outages.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2527. · a record · the summary of a news item

    Before
    An EPA plan could reduce public scrutiny of Georgia data center air permits. The item reports a potential regulatory change affecting data center permitting in the state.
    After
    Under an EPA plan, air permits for data centers in Georgia could face less public scrutiny.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2528. · a record · the summary of a news item

    Before
    Atlanta residents or officials questioned whether Georgia's data centers justify their cost. The headline reflects public debate over the value of data center development.
    After
    There is debate in Georgia over whether the state's data centers are worth their cost.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2529. · a record · the summary of a news item

    Before
    The Georgia Chamber announced plans to counter misinformation and disinformation about data centers. The headline suggests an organized response to public criticism of data center projects.
    After
    The Georgia Chamber plans to counter what it calls misinformation and disinformation about data centers.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2530. · a record · the summary of a news item

    Before
    A Bookman column in the Georgia Recorder claims secrecy and tax breaks are driving a surge of unpopular data center proposals in Georgia. The report alleges lack of transparency in data center development decisions.
    After
    Bookman said secrecy and tax breaks are clearing the way for a growing number of unpopular data center proposals across Georgia.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2531. · a record · the summary of a news item

    Before
    Bob Stump argues Arizona can be a model for public private data center collaboration, countering the narrative that data centers are to blame for rising electric bills. Jen Springman of the Goldwater Institute said most new data centers use minimal water and that moratoria send a bad message.
    After
    Bob Stump said data centers are wrongly blamed for higher electric bills, and the Goldwater Institute's Jen Springman said moratoria signal that areas are closed for business.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2532. · a record · the summary of a news item

    Before
    A Phoenix data center firm raised $1 billion to repurpose older facilities amid construction backlash. The funding reflects efforts to develop data centers in response to community opposition to new construction.
    After
    A data center company in Phoenix raised $1 billion for repurposing older facilities.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2533. · a record · the summary of a news item

    Before
    Attorney General Kris Mayes called for a halt to new data centers in Arizona. No further detail is available from the headline.
    After
    Kris Mayes, Arizona's attorney general, called for a stop to new data centers in the state.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2534. · a record · the summary of a news item

    Before
    Oregon moved toward a one year moratorium on some data center tax breaks. The state action restricts tax incentives for data center development.
    After
    Oregon moved toward suspending some of its data center tax breaks for a year.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2535. · a record · the summary of a news item

    Before
    Oregon regulators approved a 30 percent electricity rate hike for data centers near Portland on July 7, 2026. This regulatory action adjusts rates for facilities in the region.
    After
    State regulators in Oregon approved a 30 percent increase in electricity rates for data centers in the Portland area.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2536. · a record · the summary of a news item

    Before
    A poll found Oregonians want a data center moratorium and no more tax breaks for such projects. The survey indicates public opposition to continued data center development and incentives.
    After
    A poll found Oregon residents favor a data center moratorium and oppose giving data centers any more tax breaks.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2537. · a record · the summary of a news item

    Before
    Oregon Public Utility Commission approved Portland General Electric's large load tariff framework for data centers. The decision implements rate structures affecting how data centers pay for electricity.
    After
    Portland General Electric received approval from the Oregon Public Utility Commission for a large load tariff framework covering data centers.
    Why
    the record's rules: the sentence copied its source, was about its headline or carried a number the card's facts do not; written again from the card's facts, on the editor's word

  2538. · a record · the kind of a figure

    Before
    figure
    After
    forecast
    Why
    The sentence is a projection ("will surge from $20 billion to $65 billion by 2030"), another group's forecast and not a measured figure; it renders in the forecast panel and is never counted (the editor's word of 2026-10-06).

  2539. · a record · the value of a figure

    Before
    After
    214 data centers
    Why
    Added from the sentence of ffac7764, which held 75 MW for two counts; this row is the medium count, 25 to 75 megawatts (the editor's word of 2026-10-06).

  2540. · a record · the value of a figure

    Before
    After
    247 data centers
    Why
    Added from the sentence of ffac7764, which held 75 MW for two counts; this row is the large count (the editor's word of 2026-10-06).

  2541. · a record · the duplicate mark of a figure

    Before
    After
    3d8c83d8-34fa-4544-b302-45c0cc14cc13
    Why
    The row held 75 MW from a sentence that counts two groups of data centers by the power each requested. It is replaced by two count figures from the same sentence, 247 large data centers requesting at least 75 megawatts (3d8c83d8) and 214 medium data centers requesting 25 to 75 megawatts (e9c02986), on the editor's word of 2026-10-06.

  2542. · a record · the value of a figure

    Before
    After
    214 data centers
    Why
    Added from the sentence of 17ead76c, which held 75 MW for two counts; this row is the medium count, 25 to 75 megawatts (the editor's word of 2026-10-06).

  2543. · a record · the value of a figure

    Before
    After
    247 data centers
    Why
    Added from the sentence of 17ead76c, which held 75 MW for two counts; this row is the large count (the editor's word of 2026-10-06).

  2544. · a record · the duplicate mark of a figure

    Before
    After
    3418dc92-5760-4abb-9d7d-e6e11ce6cd08
    Why
    The row held 75 MW from a sentence that counts two groups of data centers by the power each requested. It is replaced by two count figures from the same sentence, 247 large data centers requesting at least 75 megawatts (3418dc92) and 214 medium data centers requesting 25 to 75 megawatts (4eac80c7), on the editor's word of 2026-10-06.

  2545. · Stratos Project · the kind of a timeline entry

    Before
    other
    After
    referendum
    Why
    A referendum step: the county attorney's rejection of the applications, typed other by the approve; the kind corrected on the editor's word (docs/batch-backlog-apply-1006.md).

  2546. · Stratos Project · the kind of a timeline entry

    Before
    other
    After
    referendum
    Why
    A referendum step: the referendum applications filed, typed other by the approve; the kind corrected on the editor's word (docs/batch-backlog-apply-1006.md).

  2547. · Milwaukee · the rating of a scorecard event

    Before
    restrictive
    After
    no published rating
    Why
    The event carried Wisconsin's own rating; on the Milwaukee row, which carries none, it carries none. No row's rating changed.

  2548. · Milwaukee · the scorecard row of a scorecard event

    Before
    WI/wisconsin
    After
    WI/milwaukee
    Why
    The Milwaukee City Plan Commission's hearing on the city's proposed moratorium is an act of the city (WTMJ); the row was Wisconsin's own. Moved to the Milwaukee row on the editor's word (docs/batch-backlog-apply-1006.md).

  2549. · a record · the summary of a bill's history entry

    Before
    H.R. 9340 passed the Senate.
    After
    H.R. 9340 was received in the Senate.
    Why
    The action the row rests on is "Received in the Senate.": a receipt, not a passage. The sentence named the receiving chamber as the chamber that passed the measure. The sentence now states the receipt; the chamber that passed it is the stage's.

  2550. · a record · the summary of a bill's history entry

    Before
    H.B. 1701 passed its second chamber.
    After
    H.B. 1701 passed the Senate.
    Why
    The action the row rests on is "Enrolled Bill Signed", recorded in one chamber's journal; the sentence named that chamber as the one that passed the measure. The chamber a passed stage names is read off the bill's own number: a House bill's first passage is the House's and its second the Senate's.

  2551. · a record · the summary of a bill's history entry

    Before
    H.B. 1450 passed its second chamber.
    After
    H.B. 1450 passed the Senate.
    Why
    The action the row rests on is "Enrolled Bill Signed", recorded in one chamber's journal; the sentence named that chamber as the one that passed the measure. The chamber a passed stage names is read off the bill's own number: a House bill's first passage is the House's and its second the Senate's.

  2552. · a record · the summary of a bill's history entry

    Before
    S.B. 2906 passed the Senate.
    After
    S.B. 2906 passed the House.
    Why
    The action the row rests on is "Enrolled Bill Signed", recorded in one chamber's journal; the sentence named that chamber as the one that passed the measure. The chamber a passed stage names is read off the bill's own number: a House bill's first passage is the House's and its second the Senate's.

  2553. · a record · the summary of a bill's history entry

    Before
    H.B. 1189 passed the House.
    After
    H.B. 1189 passed the Senate.
    Why
    The action the row rests on is "Enrolled Bill Signed", recorded in one chamber's journal; the sentence named that chamber as the one that passed the measure. The chamber a passed stage names is read off the bill's own number: a House bill's first passage is the House's and its second the Senate's.

  2554. · a record · the summary of a bill's history entry

    Before
    S.B. 2779 passed the Senate.
    After
    S.B. 2779 passed the House.
    Why
    The action the row rests on is "Enrolled Bill Signed", recorded in one chamber's journal; the sentence named that chamber as the one that passed the measure. The chamber a passed stage names is read off the bill's own number: a House bill's first passage is the House's and its second the Senate's.

  2555. · a record · the summary of a bill's history entry

    Before
    S.B. 2271 passed the Senate.
    After
    S.B. 2271 passed the House.
    Why
    The action the row rests on is "Enrolled Bill Signed", recorded in one chamber's journal; the sentence named that chamber as the one that passed the measure. The chamber a passed stage names is read off the bill's own number: a House bill's first passage is the House's and its second the Senate's.

  2556. · a record · the summary of a bill's history entry

    Before
    S.B. 2001 passed the Senate.
    After
    S.B. 2001 passed the House.
    Why
    The action the row rests on is "Enrolled Bill Signed", recorded in one chamber's journal; the sentence named that chamber as the one that passed the measure. The chamber a passed stage names is read off the bill's own number: a House bill's first passage is the House's and its second the Senate's.

  2557. · a record · the summary of a bill's history entry

    Before
    S.B. 617 passed the Senate.
    After
    S.B. 617 passed the House.
    Why
    The action the row rests on is "Ordered Enrolled", recorded in one chamber's journal; the sentence named that chamber as the one that passed the measure. The chamber a passed stage names is read off the bill's own number: a House bill's first passage is the House's and its second the Senate's.

  2558. · a record · the summary of a bill's history entry

    Before
    S.B. 616 passed the Senate.
    After
    S.B. 616 passed the House.
    Why
    The action the row rests on is "Ordered Enrolled", recorded in one chamber's journal; the sentence named that chamber as the one that passed the measure. The chamber a passed stage names is read off the bill's own number: a House bill's first passage is the House's and its second the Senate's.

  2559. · a record · the summary of a bill's history entry

    Before
    H.B. 827 passed the House.
    After
    H.B. 827 passed the Senate.
    Why
    The action the row rests on is "Enrolled and signed by the Speaker of the House.", recorded in one chamber's journal; the sentence named that chamber as the one that passed the measure. The chamber a passed stage names is read off the bill's own number: a House bill's first passage is the House's and its second the Senate's.

  2560. · a record · the summary of a bill's history entry

    Before
    H.B. 827 passed the Senate.
    After
    H.B. 827 was received in the Senate.
    Why
    The action the row rests on is "Received in the Senate. Read first time by title and placed on the Calendar for a second reading.": a receipt, not a passage. The sentence named the receiving chamber as the chamber that passed the measure. The sentence now states the receipt; the chamber that passed it is the stage's.

  2561. · a record · the summary of a bill's history entry

    Before
    H.B. 237 passed the House.
    After
    H.B. 237 passed the Senate.
    Why
    The action the row rests on is "enrolled, signed by each presiding officer", recorded in one chamber's journal; the sentence named that chamber as the one that passed the measure. The chamber a passed stage names is read off the bill's own number: a House bill's first passage is the House's and its second the Senate's.

  2562. · a record · the summary of a bill's history entry

    Before
    H.B. 237 passed the Senate.
    After
    H.B. 237 was received in the Senate.
    Why
    The action the row rests on is "received in Senate": a receipt, not a passage. The sentence named the receiving chamber as the chamber that passed the measure. The sentence now states the receipt; the chamber that passed it is the stage's.

  2563. · a record · the summary of a bill's history entry

    Before
    H.B. 230 passed the House.
    After
    H.B. 230 passed the Senate.
    Why
    The action the row rests on is "enrolled, signed by Speaker of the House", recorded in one chamber's journal; the sentence named that chamber as the one that passed the measure. The chamber a passed stage names is read off the bill's own number: a House bill's first passage is the House's and its second the Senate's.

  2564. · a record · the summary of a bill's history entry

    Before
    H.B. 230 passed the Senate.
    After
    H.B. 230 was received in the Senate.
    Why
    The action the row rests on is "received in Senate": a receipt, not a passage. The sentence named the receiving chamber as the chamber that passed the measure. The sentence now states the receipt; the chamber that passed it is the stage's.

  2565. · a record · the summary of a bill's history entry

    Before
    H.B. 8 passed the House.
    After
    H.B. 8 passed the Senate.
    Why
    The action the row rests on is "to Rules (H)", recorded in one chamber's journal; the sentence named that chamber as the one that passed the measure. The chamber a passed stage names is read off the bill's own number: a House bill's first passage is the House's and its second the Senate's.

  2566. · a record · the summary of a bill's history entry

    Before
    H.B. 8 passed the Senate.
    After
    H.B. 8 was received in the Senate.
    Why
    The action the row rests on is "received in Senate": a receipt, not a passage. The sentence named the receiving chamber as the chamber that passed the measure. The sentence now states the receipt; the chamber that passed it is the stage's.

  2567. · a record · the summary of a bill's history entry

    Before
    H.B. 1298 passed its second chamber.
    After
    H.B. 1298 passed the Senate.
    Why
    The action the row rests on is "House: Enrolled", recorded in one chamber's journal; the sentence named that chamber as the one that passed the measure. The chamber a passed stage names is read off the bill's own number: a House bill's first passage is the House's and its second the Senate's.

  2568. · a record · the summary of a bill's history entry

    Before
    H.B. 1298 passed its first chamber.
    After
    H.B. 1298 passed the House of Delegates.
    Why
    The action the row rests on is "House: Engrossed by House as amended HB1298E", recorded in one chamber's journal; the sentence named that chamber as the one that passed the measure. The chamber a passed stage names is read off the bill's own number: a House bill's first passage is the House's and its second the Senate's.

  2569. · a record · the summary of a bill's history entry

    Before
    S.B. 112 passed its second chamber.
    After
    S.B. 112 passed the House of Delegates.
    Why
    The action the row rests on is "Senate: Enrolled", recorded in one chamber's journal; the sentence named that chamber as the one that passed the measure. The chamber a passed stage names is read off the bill's own number: a House bill's first passage is the House's and its second the Senate's.

  2570. · a record · the summary of a bill's history entry

    Before
    S.B. 112 passed its first chamber.
    After
    S.B. 112 passed the Senate.
    Why
    The action the row rests on is "House: Engrossed by House - committee substitute SB112H1", recorded in one chamber's journal; the sentence named that chamber as the one that passed the measure. The chamber a passed stage names is read off the bill's own number: a House bill's first passage is the House's and its second the Senate's.

  2571. · a record · the summary of a bill's history entry

    Before
    S.B. 112 passed its first chamber.
    After
    S.B. 112 passed the Senate.
    Why
    The action the row rests on is "Senate: Engrossed by Senate - committee substitute SB112S1", recorded in one chamber's journal; the sentence named that chamber as the one that passed the measure. The chamber a passed stage names is read off the bill's own number: a House bill's first passage is the House's and its second the Senate's.

  2572. · a record · the summary of a bill's history entry

    Before
    H.B. 216 passed its second chamber.
    After
    H.B. 216 passed the Senate.
    Why
    The action the row rests on is "House: Enrolled", recorded in one chamber's journal; the sentence named that chamber as the one that passed the measure. The chamber a passed stage names is read off the bill's own number: a House bill's first passage is the House's and its second the Senate's.

  2573. · a record · the summary of a bill's history entry

    Before
    H.B. 216 passed its first chamber.
    After
    H.B. 216 passed the House of Delegates.
    Why
    The action the row rests on is "Senate: Engrossed by Senate as amended", recorded in one chamber's journal; the sentence named that chamber as the one that passed the measure. The chamber a passed stage names is read off the bill's own number: a House bill's first passage is the House's and its second the Senate's.

  2574. · a record · the summary of a bill's history entry

    Before
    H.B. 216 passed its first chamber.
    After
    H.B. 216 passed the House of Delegates.
    Why
    The action the row rests on is "House: Engrossed by House as amended HB216E", recorded in one chamber's journal; the sentence named that chamber as the one that passed the measure. The chamber a passed stage names is read off the bill's own number: a House bill's first passage is the House's and its second the Senate's.

  2575. · a record · the summary of a bill's history entry

    Before
    S.B. 1133 passed the Senate.
    After
    S.B. 1133 passed the House of Delegates.
    Why
    The action the row rests on is "Enrolled", recorded in one chamber's journal; the sentence named that chamber as the one that passed the measure. The chamber a passed stage names is read off the bill's own number: a House bill's first passage is the House's and its second the Senate's.

  2576. · a record · the summary of a bill's history entry

    Before
    S.B. 1133 passed the House of Delegates.
    After
    S.B. 1133 passed the Senate.
    Why
    The action the row rests on is "Engrossed by House as amended SB1133", recorded in one chamber's journal; the sentence named that chamber as the one that passed the measure. The chamber a passed stage names is read off the bill's own number: a House bill's first passage is the House's and its second the Senate's.

  2577. · a record · the summary of a bill's history entry

    Before
    H.B. 1699 passed the House of Delegates.
    After
    H.B. 1699 passed the Senate.
    Why
    The action the row rests on is "Enrolled", recorded in one chamber's journal; the sentence named that chamber as the one that passed the measure. The chamber a passed stage names is read off the bill's own number: a House bill's first passage is the House's and its second the Senate's.

  2578. · a record · the summary of a bill's history entry

    Before
    S.B. 1142 passed the Senate.
    After
    S.B. 1142 passed the House of Delegates.
    Why
    The action the row rests on is "Enrolled", recorded in one chamber's journal; the sentence named that chamber as the one that passed the measure. The chamber a passed stage names is read off the bill's own number: a House bill's first passage is the House's and its second the Senate's.

  2579. · a record · the summary of a bill's history entry

    Before
    H.B. 2162 passed the House of Delegates.
    After
    H.B. 2162 passed the Senate.
    Why
    The action the row rests on is "Enrolled", recorded in one chamber's journal; the sentence named that chamber as the one that passed the measure. The chamber a passed stage names is read off the bill's own number: a House bill's first passage is the House's and its second the Senate's.

  2580. · a record · the summary of a bill's history entry

    Before
    S.B. 64 passed the Senate.
    After
    S.B. 64 passed the House of Delegates.
    Why
    The action the row rests on is "Enrolled", recorded in one chamber's journal; the sentence named that chamber as the one that passed the measure. The chamber a passed stage names is read off the bill's own number: a House bill's first passage is the House's and its second the Senate's.

  2581. · a record · the summary of a bill's history entry

    Before
    H.B. 872 passed the House of Delegates.
    After
    H.B. 872 passed the Senate.
    Why
    The action the row rests on is "Enrolled", recorded in one chamber's journal; the sentence named that chamber as the one that passed the measure. The chamber a passed stage names is read off the bill's own number: a House bill's first passage is the House's and its second the Senate's.

  2582. · a record · the summary of a bill's history entry

    Before
    H.B. 15 passed the House of Delegates.
    After
    H.B. 15 passed the Senate.
    Why
    The action the row rests on is "Enrolled", recorded in one chamber's journal; the sentence named that chamber as the one that passed the measure. The chamber a passed stage names is read off the bill's own number: a House bill's first passage is the House's and its second the Senate's.

  2583. · a record · the summary of a bill's history entry

    Before
    S.B. 268 passed the Senate.
    After
    S.B. 268 passed the House of Delegates.
    Why
    The action the row rests on is "Enrolled", recorded in one chamber's journal; the sentence named that chamber as the one that passed the measure. The chamber a passed stage names is read off the bill's own number: a House bill's first passage is the House's and its second the Senate's.

  2584. · a record · the summary of a bill's history entry

    Before
    H.B. 828 passed the House of Delegates.
    After
    H.B. 828 passed the Senate.
    Why
    The action the row rests on is "Enrolled", recorded in one chamber's journal; the sentence named that chamber as the one that passed the measure. The chamber a passed stage names is read off the bill's own number: a House bill's first passage is the House's and its second the Senate's.

  2585. · a record · the summary of a bill's history entry

    Before
    S.B. 1423 passed the Senate.
    After
    S.B. 1423 passed the House of Delegates.
    Why
    The action the row rests on is "Enrolled", recorded in one chamber's journal; the sentence named that chamber as the one that passed the measure. The chamber a passed stage names is read off the bill's own number: a House bill's first passage is the House's and its second the Senate's.

  2586. · a record · the summary of a bill's history entry

    Before
    S.B. 1423 passed the House of Delegates.
    After
    S.B. 1423 passed the Senate.
    Why
    The action the row rests on is "Engrossed by House - committee substitute SB1423H1", recorded in one chamber's journal; the sentence named that chamber as the one that passed the measure. The chamber a passed stage names is read off the bill's own number: a House bill's first passage is the House's and its second the Senate's.

  2587. · a record · the summary of a bill's history entry

    Before
    H.B. 2273 passed the House of Delegates.
    After
    H.B. 2273 passed the Senate.
    Why
    The action the row rests on is "Enrolled", recorded in one chamber's journal; the sentence named that chamber as the one that passed the measure. The chamber a passed stage names is read off the bill's own number: a House bill's first passage is the House's and its second the Senate's.

  2588. · a record · the summary of a bill's history entry

    Before
    H.B. 2273 passed the Senate.
    After
    H.B. 2273 passed the House of Delegates.
    Why
    The action the row rests on is "Engrossed by Senate - committee substitute HB2273S1", recorded in one chamber's journal; the sentence named that chamber as the one that passed the measure. The chamber a passed stage names is read off the bill's own number: a House bill's first passage is the House's and its second the Senate's.

  2589. · a record · the summary of a bill's history entry

    Before
    S.B. 513 passed the Senate.
    After
    S.B. 513 passed the House of Delegates.
    Why
    The action the row rests on is "Enrolled", recorded in one chamber's journal; the sentence named that chamber as the one that passed the measure. The chamber a passed stage names is read off the bill's own number: a House bill's first passage is the House's and its second the Senate's.

  2590. · a record · the summary of a bill's history entry

    Before
    H.B. 791 passed the House of Delegates.
    After
    H.B. 791 passed the Senate.
    Why
    The action the row rests on is "Enrolled", recorded in one chamber's journal; the sentence named that chamber as the one that passed the measure. The chamber a passed stage names is read off the bill's own number: a House bill's first passage is the House's and its second the Senate's.

  2591. · a record · the summary of a bill's history entry

    Before
    S.B. 1522 passed the Senate.
    After
    S.B. 1522 passed the House of Delegates.
    Why
    The action the row rests on is "Enrolled", recorded in one chamber's journal; the sentence named that chamber as the one that passed the measure. The chamber a passed stage names is read off the bill's own number: a House bill's first passage is the House's and its second the Senate's.

  2592. · a record · the summary of a bill's history entry

    Before
    S.B. 1522 passed the House of Delegates.
    After
    S.B. 1522 passed the Senate.
    Why
    The action the row rests on is "Engrossed by House - committee substitute with amendment SB1522H1", recorded in one chamber's journal; the sentence named that chamber as the one that passed the measure. The chamber a passed stage names is read off the bill's own number: a House bill's first passage is the House's and its second the Senate's.

  2593. · a record · the summary of a bill's history entry

    Before
    H.B. 2479 passed the House of Delegates.
    After
    H.B. 2479 passed the Senate.
    Why
    The action the row rests on is "Enrolled", recorded in one chamber's journal; the sentence named that chamber as the one that passed the measure. The chamber a passed stage names is read off the bill's own number: a House bill's first passage is the House's and its second the Senate's.

  2594. · a record · the summary of a bill's history entry

    Before
    H.B. 2479 passed the Senate.
    After
    H.B. 2479 passed the House of Delegates.
    Why
    The action the row rests on is "Engrossed by Senate - floor substitute HB2479S2", recorded in one chamber's journal; the sentence named that chamber as the one that passed the measure. The chamber a passed stage names is read off the bill's own number: a House bill's first passage is the House's and its second the Senate's.

  2595. · a record · the summary of a bill's history entry

    Before
    H.B. 1769 passed the House of Delegates.
    After
    H.B. 1769 passed the Senate.
    Why
    The action the row rests on is "Enrolled", recorded in one chamber's journal; the sentence named that chamber as the one that passed the measure. The chamber a passed stage names is read off the bill's own number: a House bill's first passage is the House's and its second the Senate's.

  2596. · a record · the summary of a bill's history entry

    Before
    S.B. 540 passed the Senate.
    After
    S.B. 540 passed the House of Delegates.
    Why
    The action the row rests on is "Enrolled", recorded in one chamber's journal; the sentence named that chamber as the one that passed the measure. The chamber a passed stage names is read off the bill's own number: a House bill's first passage is the House's and its second the Senate's.

  2597. · a record · the summary of a bill's history entry

    Before
    S.B. 339 passed the Senate.
    After
    S.B. 339 passed the House of Delegates.
    Why
    The action the row rests on is "Enrolled", recorded in one chamber's journal; the sentence named that chamber as the one that passed the measure. The chamber a passed stage names is read off the bill's own number: a House bill's first passage is the House's and its second the Senate's.

  2598. · a record · the summary of a bill's history entry

    Before
    S.B. 339 passed the House of Delegates.
    After
    S.B. 339 passed the Senate.
    Why
    The action the row rests on is "Engrossed by House - committee substitute SB339H1", recorded in one chamber's journal; the sentence named that chamber as the one that passed the measure. The chamber a passed stage names is read off the bill's own number: a House bill's first passage is the House's and its second the Senate's.

  2599. · a record · the summary of a bill's history entry

    Before
    H.B. 991 passed the House of Delegates.
    After
    H.B. 991 passed the Senate.
    Why
    The action the row rests on is "Enrolled", recorded in one chamber's journal; the sentence named that chamber as the one that passed the measure. The chamber a passed stage names is read off the bill's own number: a House bill's first passage is the House's and its second the Senate's.

  2600. · a record · the summary of a bill's history entry

    Before
    H.B. 991 passed the Senate.
    After
    H.B. 991 passed the House of Delegates.
    Why
    The action the row rests on is "Engrossed by Senate as amended", recorded in one chamber's journal; the sentence named that chamber as the one that passed the measure. The chamber a passed stage names is read off the bill's own number: a House bill's first passage is the House's and its second the Senate's.

  2601. · a record · the summary of a bill's history entry

    Before
    H.B. 1009 passed its second chamber.
    After
    H.B. 1009 passed the Senate.
    Why
    The action the row rests on is "(H) Returned from Senate (Sen. Com. No. 528) in amended form (SD 2).", recorded in one chamber's journal; the sentence named that chamber as the one that passed the measure. The chamber a passed stage names is read off the bill's own number: a House bill's first passage is the House's and its second the Senate's.

  2602. · a record · the summary of a bill's history entry

    Before
    H.B. 2454 passed its second chamber.
    After
    H.B. 2454 passed the Senate.
    Why
    The action the row rests on is "(H) Returned from Senate (Sen. Com. No. 618) in amended form (SD 1).", recorded in one chamber's journal; the sentence named that chamber as the one that passed the measure. The chamber a passed stage names is read off the bill's own number: a House bill's first passage is the House's and its second the Senate's.

  2603. · a record · the summary of a bill's history entry

    Before
    H.B. 2246 passed the House.
    After
    H.B. 2246 passed the Senate.
    Why
    The action the row rests on is "Returned from Senate (Sen. Com. No. 619) in amended form (SD 1).", recorded in one chamber's journal; the sentence named that chamber as the one that passed the measure. The chamber a passed stage names is read off the bill's own number: a House bill's first passage is the House's and its second the Senate's.

  2604. · a record · the summary of a bill's history entry

    Before
    H.B. 2243 passed the House.
    After
    H.B. 2243 passed the Senate.
    Why
    The action the row rests on is "Returned from Senate (Sen. Com. No. 496) in amended form (SD 1).", recorded in one chamber's journal; the sentence named that chamber as the one that passed the measure. The chamber a passed stage names is read off the bill's own number: a House bill's first passage is the House's and its second the Senate's.

  2605. · a record · the summary of a bill's history entry

    Before
    S. 2020 passed its second chamber.
    After
    S. 2020 passed the House.
    Why
    The action the row rests on is "Ordered engrossed, then enrolled -SJ 01586", recorded in one chamber's journal; the sentence named that chamber as the one that passed the measure. The chamber a passed stage names is read off the bill's own number: a House bill's first passage is the House's and its second the Senate's.

  2606. · a record · the summary of a bill's history entry

    Before
    S. 2020 passed its first chamber.
    After
    S. 2020 passed the Senate.
    Why
    The action the row rests on is "In Messages", recorded in one chamber's journal; the sentence named that chamber as the one that passed the measure. The chamber a passed stage names is read off the bill's own number: a House bill's first passage is the House's and its second the Senate's.

  2607. · a record · the summary of a bill's history entry

    Before
    H. 7073 passed the Senate.
    After
    H. 7073 passed the House.
    Why
    The action the row rests on is "In Messages", recorded in one chamber's journal; the sentence named that chamber as the one that passed the measure. The chamber a passed stage names is read off the bill's own number: a House bill's first passage is the House's and its second the Senate's.

  2608. · a record · the summary of a bill's history entry

    Before
    H. 7061 passed the House.
    After
    H. 7061 passed the Senate.
    Why
    The action the row rests on is "In Messages", recorded in one chamber's journal; the sentence named that chamber as the one that passed the measure. The chamber a passed stage names is read off the bill's own number: a House bill's first passage is the House's and its second the Senate's.

  2609. · a record · the summary of a bill's history entry

    Before
    H. 7061 passed the Senate.
    After
    H. 7061 passed the House.
    Why
    The action the row rests on is "In Messages", recorded in one chamber's journal; the sentence named that chamber as the one that passed the measure. The chamber a passed stage names is read off the bill's own number: a House bill's first passage is the House's and its second the Senate's.

  2610. · a record · the summary of a bill's history entry

    Before
    S. 2518 passed the House.
    After
    S. 2518 passed the Senate.
    Why
    The action the row rests on is "In Messages", recorded in one chamber's journal; the sentence named that chamber as the one that passed the measure. The chamber a passed stage names is read off the bill's own number: a House bill's first passage is the House's and its second the Senate's.

  2611. · a record · the summary of a bill's history entry

    Before
    S. 2518 passed the House.
    After
    S. 2518 passed the Senate.
    Why
    The action the row rests on is "In Messages", recorded in one chamber's journal; the sentence named that chamber as the one that passed the measure. The chamber a passed stage names is read off the bill's own number: a House bill's first passage is the House's and its second the Senate's.

  2612. · a record · the summary of a bill's history entry

    Before
    S.B. 299 passed the House.
    After
    S.B. 299 passed the Senate.
    Why
    The action the row rests on is "Introduced In House - Assigned to Finance + Appropriations", recorded in one chamber's journal; the sentence named that chamber as the one that passed the measure. The chamber a passed stage names is read off the bill's own number: a House bill's first passage is the House's and its second the Senate's.

  2613. · a record · the summary of a bill's history entry

    Before
    S.B. 72 passed the Senate.
    After
    S.B. 72 passed the House.
    Why
    The action the row rests on is "Signed by the President of the Senate", recorded in one chamber's journal; the sentence named that chamber as the one that passed the measure. The chamber a passed stage names is read off the bill's own number: a House bill's first passage is the House's and its second the Senate's.

  2614. · a record · the summary of a bill's history entry

    Before
    S.B. 72 passed the House.
    After
    S.B. 72 passed the Senate.
    Why
    The action the row rests on is "Introduced In House - Assigned to Energy & Environment + Appropriations", recorded in one chamber's journal; the sentence named that chamber as the one that passed the measure. The chamber a passed stage names is read off the bill's own number: a House bill's first passage is the House's and its second the Senate's.

  2615. · a record · the summary of a bill's history entry

    Before
    H.B. 2649 passed the Senate.
    After
    H.B. 2649 passed the House.
    Why
    The action the row rests on is "Transmit to Senate", recorded in one chamber's journal; the sentence named that chamber as the one that passed the measure. The chamber a passed stage names is read off the bill's own number: a House bill's first passage is the House's and its second the Senate's.

  2616. · a record · the summary of a bill's history entry

    Before
    S.B. 1274 passed the House.
    After
    S.B. 1274 passed the Senate.
    Why
    The action the row rests on is "Transmit to House", recorded in one chamber's journal; the sentence named that chamber as the one that passed the measure. The chamber a passed stage names is read off the bill's own number: a House bill's first passage is the House's and its second the Senate's.

  2617. · a record · the summary of a bill's history entry

    Before
    H.R. 4173 passed its first chamber.
    After
    H.R. 4173 was received in the Senate.
    Why
    The action the row rests on is "Received in the Senate and Read twice and referred to the Committee on Banking, Housing, and Urban Affairs.": a receipt, not a passage. The sentence named the receiving chamber as the chamber that passed the measure. The sentence now states the receipt; the chamber that passed it is the stage's.

  2618. · a record · the summary of a bill's history entry

    Before
    H.R. 2701 passed its first chamber.
    After
    H.R. 2701 was received in the Senate.
    Why
    The action the row rests on is "Received in the Senate.": a receipt, not a passage. The sentence named the receiving chamber as the chamber that passed the measure. The sentence now states the receipt; the chamber that passed it is the stage's.

  2619. · a record · the summary of a bill's history entry

    Before
    H.R. 847 passed its first chamber.
    After
    H.R. 847 was received in the Senate.
    Why
    The action the row rests on is "Received in the Senate. Read the first time. Placed on Senate Legislative Calendar under Read the First Time.": a receipt, not a passage. The sentence named the receiving chamber as the chamber that passed the measure. The sentence now states the receipt; the chamber that passed it is the stage's.

  2620. · a record · the summary of a bill's history entry

    Before
    H.R. 3630 passed the Senate.
    After
    H.R. 3630 was received in the Senate.
    Why
    The action the row rests on is "Received in the Senate. Read the second time. Placed on Senate Legislative Calendar under General Orders. Calendar No. 257.": a receipt, not a passage. The sentence named the receiving chamber as the chamber that passed the measure. The sentence now states the receipt; the chamber that passed it is the stage's.

  2621. · a record · the summary of a bill's history entry

    Before
    S. 1356 passed the House.
    After
    S. 1356 was received in the House.
    Why
    The action the row rests on is "Received in the House.": a receipt, not a passage. The sentence named the receiving chamber as the chamber that passed the measure. The sentence now states the receipt; the chamber that passed it is the stage's.

  2622. · a record · the summary of a bill's history entry

    Before
    H.R. 3243 passed the Senate.
    After
    H.R. 3243 was received in the Senate.
    Why
    The action the row rests on is "Received in the Senate, read twice.": a receipt, not a passage. The sentence named the receiving chamber as the chamber that passed the measure. The sentence now states the receipt; the chamber that passed it is the stage's.

  2623. · a record · the summary of a bill's history entry

    Before
    H.B. 4983 passed the House of Delegates.
    After
    H.B. 4983 passed the Senate.
    Why
    The action the row rests on is "Completed legislative action", recorded in one chamber's journal; the sentence named that chamber as the one that passed the measure. The chamber a passed stage names is read off the bill's own number: a House bill's first passage is the House's and its second the Senate's.

  2624. · a record · the summary of a bill's history entry

    Before
    S.B. 94 passed the Senate.
    After
    S.B. 94 passed the House of Delegates.
    Why
    The action the row rests on is "Enrolled", recorded in one chamber's journal; the sentence named that chamber as the one that passed the measure. The chamber a passed stage names is read off the bill's own number: a House bill's first passage is the House's and its second the Senate's.

  2625. · a record · the summary of a bill's history entry

    Before
    S.B. 94 passed the House of Delegates.
    After
    S.B. 94 passed the Senate.
    Why
    The action the row rests on is "Engrossed by House - committee substitute", recorded in one chamber's journal; the sentence named that chamber as the one that passed the measure. The chamber a passed stage names is read off the bill's own number: a House bill's first passage is the House's and its second the Senate's.

  2626. · a record · the summary of a bill's history entry

    Before
    H.B. 507 passed the House of Delegates.
    After
    H.B. 507 passed the Senate.
    Why
    The action the row rests on is "Enrolled", recorded in one chamber's journal; the sentence named that chamber as the one that passed the measure. The chamber a passed stage names is read off the bill's own number: a House bill's first passage is the House's and its second the Senate's.

  2627. · a record · the summary of a bill's history entry

    Before
    H.B. 496 passed the House of Delegates.
    After
    H.B. 496 passed the Senate.
    Why
    The action the row rests on is "Enrolled", recorded in one chamber's journal; the sentence named that chamber as the one that passed the measure. The chamber a passed stage names is read off the bill's own number: a House bill's first passage is the House's and its second the Senate's.

  2628. · a record · the summary of a bill's history entry

    Before
    H.B. 496 passed the Senate.
    After
    H.B. 496 passed the House of Delegates.
    Why
    The action the row rests on is "Engrossed by Senate - committee substitute", recorded in one chamber's journal; the sentence named that chamber as the one that passed the measure. The chamber a passed stage names is read off the bill's own number: a House bill's first passage is the House's and its second the Senate's.

  2629. · a record · the summary of a bill's history entry

    Before
    S.B. 553 passed the Senate.
    After
    S.B. 553 passed the House of Delegates.
    Why
    The action the row rests on is "Enrolled", recorded in one chamber's journal; the sentence named that chamber as the one that passed the measure. The chamber a passed stage names is read off the bill's own number: a House bill's first passage is the House's and its second the Senate's.

  2630. · a record · the summary of a bill's history entry

    Before
    S.B. 553 passed the House of Delegates.
    After
    S.B. 553 passed the Senate.
    Why
    The action the row rests on is "Engrossed by House - committee substitute", recorded in one chamber's journal; the sentence named that chamber as the one that passed the measure. The chamber a passed stage names is read off the bill's own number: a House bill's first passage is the House's and its second the Senate's.

  2631. · a record · the summary of a bill's history entry

    Before
    H.B. 323 passed the House of Delegates.
    After
    H.B. 323 passed the Senate.
    Why
    The action the row rests on is "Enrolled", recorded in one chamber's journal; the sentence named that chamber as the one that passed the measure. The chamber a passed stage names is read off the bill's own number: a House bill's first passage is the House's and its second the Senate's.

  2632. · a record · the summary of a bill's history entry

    Before
    S.B. 960 passed the House of Delegates.
    After
    S.B. 960 passed the Senate.
    Why
    The action the row rests on is "Engrossed by House - committee substitute", recorded in one chamber's journal; the sentence named that chamber as the one that passed the measure. The chamber a passed stage names is read off the bill's own number: a House bill's first passage is the House's and its second the Senate's.

  2633. · a record · the summary of a bill's history entry

    Before
    H.B. 76 passed the House.
    After
    H.B. 76 passed the Senate.
    Why
    The action the row rests on is "House/ enrolled bill to Printing in Clerk of the House", recorded in one chamber's journal; the sentence named that chamber as the one that passed the measure. The chamber a passed stage names is read off the bill's own number: a House bill's first passage is the House's and its second the Senate's.

  2634. · a record · the summary of a bill's history entry

    Before
    H.B. 76 passed the Senate.
    After
    H.B. 76 passed the House.
    Why
    The action the row rests on is "Senate/ received from House in Waiting for Introduction in the Senate": a receipt, not a passage. The sentence named the receiving chamber as the chamber that passed the measure. The sentence now states the receipt; the chamber that passed it is the stage's.

  2635. · a record · the summary of a bill's history entry

    Before
    H.B. 1847 passed the House.
    After
    H.B. 1847 passed the Senate.
    Why
    The action the row rests on is "Enrolled; ready for sig. of H. Speaker.", recorded in one chamber's journal; the sentence named that chamber as the one that passed the measure. The chamber a passed stage names is read off the bill's own number: a House bill's first passage is the House's and its second the Senate's.

  2636. · a record · the summary of a bill's history entry

    Before
    H.B. 2992 passed the House.
    After
    H.B. 2992 passed the Senate.
    Why
    The action the row rests on is "Enrolled, signed, to Senate", recorded in one chamber's journal; the sentence named that chamber as the one that passed the measure. The chamber a passed stage names is read off the bill's own number: a House bill's first passage is the House's and its second the Senate's.

  2637. · a record · the summary of a bill's history entry

    Before
    S.B. 439 passed the House.
    After
    S.B. 439 passed the Senate.
    Why
    The action the row rests on is "Introduced (in recess of) 02/19/2026 and referred to Municipal and County Government House Journal 5 P. 124", recorded in one chamber's journal; the sentence named that chamber as the one that passed the measure. The chamber a passed stage names is read off the bill's own number: a House bill's first passage is the House's and its second the Senate's.

  2638. · a record · the summary of a bill's history entry

    Before
    H.B. 424 passed the House.
    After
    H.B. 424 passed the Senate.
    Why
    The action the row rests on is "(H) Sent to Enrolling", recorded in one chamber's journal; the sentence named that chamber as the one that passed the measure. The chamber a passed stage names is read off the bill's own number: a House bill's first passage is the House's and its second the Senate's.

  2639. · a record · the summary of a bill's history entry

    Before
    S.B. 3410 passed the Senate.
    After
    S.B. 3410 passed the House.
    Why
    The action the row rests on is "Enrolled Bill Signed", recorded in one chamber's journal; the sentence named that chamber as the one that passed the measure. The chamber a passed stage names is read off the bill's own number: a House bill's first passage is the House's and its second the Senate's.

  2640. · a record · the summary of a bill's history entry

    Before
    H.C.R. 61 passed the Senate.
    After
    H.C.R. 61 was received in the Senate.
    Why
    The action the row rests on is "Received in the Senate. Rules suspended. Read first time by title and placed on the Calendar for a second reading.": a receipt, not a passage. The sentence named the receiving chamber as the chamber that passed the measure. The sentence now states the receipt; the chamber that passed it is the stage's.

  2641. · a record · the summary of a bill's history entry

    Before
    H.B. 593 passed the Senate.
    After
    H.B. 593 was received in the Senate.
    Why
    The action the row rests on is "received in Senate": a receipt, not a passage. The sentence named the receiving chamber as the chamber that passed the measure. The sentence now states the receipt; the chamber that passed it is the stage's.

  2642. · a record · the summary of a bill's history entry

    Before
    S.B. 98 passed the House.
    After
    S.B. 98 was received in the House.
    Why
    The action the row rests on is "House Received and Introduced": a receipt, not a passage. The sentence named the receiving chamber as the chamber that passed the measure. The sentence now states the receipt; the chamber that passed it is the stage's.

  2643. · a record · the summary of a bill's history entry

    Before
    S.B. 92 passed the House.
    After
    S.B. 92 was received in the House.
    Why
    The action the row rests on is "House Received and Introduced": a receipt, not a passage. The sentence named the receiving chamber as the chamber that passed the measure. The sentence now states the receipt; the chamber that passed it is the stage's.

  2644. · a record · the summary of a bill's history entry

    Before
    S. 484 passed the Senate.
    After
    S. 484 passed the House.
    Why
    The action the row rests on is "Ordered engrossed, then enrolled", recorded in one chamber's journal; the sentence named that chamber as the one that passed the measure. The chamber a passed stage names is read off the bill's own number: a House bill's first passage is the House's and its second the Senate's.

  2645. · a record · the summary of a bill's history entry

    Before
    S. 484 passed the House.
    After
    S. 484 passed the Senate.
    Why
    The action the row rests on is "In Messages", recorded in one chamber's journal; the sentence named that chamber as the one that passed the measure. The chamber a passed stage names is read off the bill's own number: a House bill's first passage is the House's and its second the Senate's.

  2646. · a record · the summary of a bill's history entry

    Before
    H.B. 2756 passed the Senate.
    After
    H.B. 2756 passed the House.
    Why
    The action the row rests on is "Transmit to Senate", recorded in one chamber's journal; the sentence named that chamber as the one that passed the measure. The chamber a passed stage names is read off the bill's own number: a House bill's first passage is the House's and its second the Senate's.

  2647. · a record · the summary of a bill's history entry

    Before
    H.B. 2457 passed the Senate.
    After
    H.B. 2457 passed the House.
    Why
    The action the row rests on is "Transmit to Senate", recorded in one chamber's journal; the sentence named that chamber as the one that passed the measure. The chamber a passed stage names is read off the bill's own number: a House bill's first passage is the House's and its second the Senate's.

  2648. · a record · the summary of a bill's history entry

    Before
    S.B. 270 passed the Senate.
    After
    S.B. 270 passed the House.
    Why
    The action the row rests on is "Enrolled", recorded in one chamber's journal; the sentence named that chamber as the one that passed the measure. The chamber a passed stage names is read off the bill's own number: a House bill's first passage is the House's and its second the Senate's.

  2649. · Amazon Eastern Oregon Data Centers · the capacity mw of a record

    Before
    1000 MW
    After
    not disclosed
    Why
    The capacity carried no source url. It came from the state batch extraction of 2026-09-04, which read two entries that are still draft and never approved ("would require a gigawatt of electricity", "consuming up to 1 gigawatt of power"); no published source on the record states it, so the field reads Not disclosed until one does (the editor's word of 2026-10-06).

  2650. · a record · the value of a figure

    Before
    1 applications
    After
    200 applications, basis estimated, the source's word nearly in conditions
    Why
    The row held 1 for a sentence that gives nearly 200 large energy consumers applying to connect to the Texas grid; the number is 200 as the source gives it, with the basis estimated and the source's "nearly" recorded (the editor's word of 2026-10-06).

  2651. · a record · the value of a figure

    Before
    121,000 gallons per day
    After
    44,300,000 gallons per year
    Why
    The row stored the brief's annual median divided by 365. The record keeps the number and unit the source prints, 44.3 million gallons a year at the median; a conversion to a day is shown only at display time, labeled as a conversion (the editor's word of 2026-10-06).

  2652. · a record · the value of a figure

    Before
    0.32 mL/query
    After
    0.000085 gallons per query
    Why
    The row stored a conversion into millilitres of the figure the source prints, 0.000085 US gallons per query. The record keeps the number and unit the source prints; a conversion is shown only at display time, labeled as a conversion (the editor's word of 2026-10-06).

  2653. · a record · the value of a figure

    Before
    3 turbines
    After
    57 turbines
    Why
    The sentence states a change, from 3 to 57, and the row carried the starting number. The figure is the value the change ends at; the start stays in the sentence (the editor's word of 2026-10-06).

  2654. · a record · the value of a figure

    Before
    20,000,000,000 USD
    After
    65,000,000,000 USD
    Why
    The sentence states a change, from $20 billion to $65 billion by 2030, and the row carried the starting number. The figure is the value the change ends at; the start stays in the sentence (the editor's word of 2026-10-06).

  2655. · a record · the value of a figure

    Before
    424 USD
    After
    477 USD
    Why
    The sentence states a change, from $424 to $477, and the row carried the starting number. The figure is the value the change ends at; the start stays in the sentence (the editor's word of 2026-10-06).

  2656. · a record · the value of a figure

    Before
    29 USD
    After
    130 USD
    Why
    The sentence states a change, from $29 to $130, and the row carried the starting number. The figure is the value the change ends at; the start stays in the sentence (the editor's word of 2026-10-06).

  2657. · a record · the value of a figure

    Before
    85,000,000 USD
    After
    126,000,000 USD
    Why
    The sentence states a change, from $85 million to $126 million, and the row carried the starting number. The figure is the value the change ends at; the start stays in the sentence (the editor's word of 2026-10-06).

  2658. · a record · the value of a figure

    Before
    10000 workers
    After
    8000 to 10000 workers
    Why
    The sentence gives a range, 8,000 to 10,000 , and the row carried its high end alone as the value. A range stays a range (the record's rule of 2026-10-06): the value is cleared and both ends are kept as the source gives them.

  2659. · a record · the value of a figure

    Before
    132000000 dollars
    After
    132000000 to 489000000 dollars
    Why
    The sentence gives a range, 132 million to 489 million, and the row carried its low end alone as the value. A range stays a range (the record's rule of 2026-10-06): the value is cleared and both ends are kept as the source gives them.

  2660. · a record · the value of a figure

    Before
    1700 jobs
    After
    1700 to 2300 jobs
    Why
    The sentence gives a range, 1,700 to 2,300 , and the row carried its low end alone as the value. A range stays a range (the record's rule of 2026-10-06): the value is cleared and both ends are kept as the source gives them.

  2661. · a record · the value of a figure

    Before
    10 MW
    After
    5 to 10 MW
    Why
    The sentence gives a range, 5-10 , and the row carried its high end alone as the value. A range stays a range (the record's rule of 2026-10-06): the value is cleared and both ends are kept as the source gives them.

  2662. · a record · the value of a figure

    Before
    100 count
    After
    100 to 115 count
    Why
    The sentence gives a range, between 100 and 115 , and the row carried its low end alone as the value. A range stays a range (the record's rule of 2026-10-06): the value is cleared and both ends are kept as the source gives them.

  2663. · a record · the value of a figure

    Before
    800 jobs
    After
    800 to 1200 jobs
    Why
    The sentence gives a range, 800 to 1,200 , and the row carried its low end alone as the value. A range stays a range (the record's rule of 2026-10-06): the value is cleared and both ends are kept as the source gives them.

  2664. · a record · the value of a figure

    Before
    14 GW
    After
    8 to 14 GW
    Why
    The sentence gives a range, 8 to 14 , and the row carried its high end alone as the value. A range stays a range (the record's rule of 2026-10-06): the value is cleared and both ends are kept as the source gives them.

  2665. · a record · the value of a figure

    Before
    4000 jobs
    After
    2000 to 4000 jobs
    Why
    The sentence gives a range, 2,000 to 4,000 , and the row carried its high end alone as the value. A range stays a range (the record's rule of 2026-10-06): the value is cleared and both ends are kept as the source gives them.

  2666. · a record · the value of a figure

    Before
    22 USD
    After
    22 to 40 USD
    Why
    The sentence gives a range, $22 to $40 , and the row carried its low end alone as the value. A range stays a range (the record's rule of 2026-10-06): the value is cleared and both ends are kept as the source gives them.

  2667. · a record · the value of a figure

    Before
    400 MW
    After
    100 to 400 MW
    Why
    The sentence gives a range, 100 to 400 , and the row carried its high end alone as the value. A range stays a range (the record's rule of 2026-10-06): the value is cleared and both ends are kept as the source gives them.

  2668. · a record · the value of a figure

    Before
    30 jobs
    After
    30 to 50 jobs
    Why
    The sentence gives a range, 30 to 50 , and the row carried its low end alone as the value. A range stays a range (the record's rule of 2026-10-06): the value is cleared and both ends are kept as the source gives them.

  2669. · a record · the value of a figure

    Before
    13000 acres
    After
    10000 to 13000 acres
    Why
    The sentence gives a range, 10,000-13,000 , and the row carried its high end alone as the value. A range stays a range (the record's rule of 2026-10-06): the value is cleared and both ends are kept as the source gives them.

  2670. · a record · the value of a figure

    Before
    80000000 dollars
    After
    80000000 to 115000000 dollars
    Why
    The sentence gives a range, 80 million to 115 million, and the row carried its low end alone as the value. A range stays a range (the record's rule of 2026-10-06): the value is cleared and both ends are kept as the source gives them.

  2671. · a record · the value of a figure

    Before
    300 jobs
    After
    300 to 350 jobs
    Why
    The sentence gives a range, 300 to 350 , and the row carried its low end alone as the value. A range stays a range (the record's rule of 2026-10-06): the value is cleared and both ends are kept as the source gives them.

  2672. · a record · the value of a figure

    Before
    5 percent
    After
    4 to 5 percent
    Why
    The sentence gives a range, 4 to 5 , and the row carried its high end alone as the value. A range stays a range (the record's rule of 2026-10-06): the value is cleared and both ends are kept as the source gives them.

  2673. · a record · the value of a figure

    Before
    60 jobs
    After
    60 to 100 jobs
    Why
    The sentence gives a range, 60 to 100 , and the row carried its low end alone as the value. A range stays a range (the record's rule of 2026-10-06): the value is cleared and both ends are kept as the source gives them.

  2674. · Stratos Project · the kind of a timeline entry

    Before
    other
    After
    litigation
    Why
    The entry is about the litigation over the referendum and names no step; its kind was other and is litigation, with no step (the record's rules).

  2675. · Stratos Project · the court step of a timeline entry

    Before
    ruling
    After
    filed
    Why
    The entry says the appeal was filed and is pending before a state judge, and the Salt Lake Tribune article behind it says the judge has not ruled on the motions; the step was ruling and is filed (the record's rules).

  2676. · Stratos Project · the power source of a record

    Before
    8250
    After
    Generated on site: a natural gas plant paired with battery storage, and a solar array
    Why
    The field held 8250, the midpoint of the 7.5 to 9 gigawatts the Utah News Dispatch sentence of May 19, 2026 gives, written as a number into a words field by the approval of October 3, 2026. The article describes the power as generated on site, a natural gas plant paired with battery storage and a solar array, which the record's entries from the same article already say; the field now carries those words (the record's rules).

  2677. · Ohio · the duplicate mark of a scorecard event

    Before
    none
    After
    7741
    Why
    The sentence gives the Ohio Supreme Court's ruling as "20-18". The court has seven justices, so no vote of the court totals 38; the figure is the station's own and the record repeated it. The story (FOX19, published Friday, September 18, 2026, "dealt a blow Thursday") supports the ruling without a tally, dated September 17; the row was dated September 19. Superseded by an event stating the ruling as the story supports it.

  2678. · United States (federal) · the duplicate mark of a scorecard event

    Before
    none
    After
    1860
    Why
    The sentence dates the House's vote on H.R. 9340 Wednesday, September 18, 2026, and the row is dated September 20. The House Clerk's roll call 312 is dated Wednesday, September 16, 2026. Superseded by event 1860, the same row's line with the clerk's date.

  2679. · United States (federal) · the duplicate mark of a scorecard event

    Before
    none
    After
    1860
    Why
    The sentence dates the House's vote on H.R. 9340 September 18, 2026. The House Clerk's roll call 312 is dated September 16, 2026, the day the row itself carries. Superseded by event 1860, the same row's line with the clerk's date.

  2680. · a record · the publication of a news item

    Before
    published
    After
    draft
    Why
    The item names Nebraska's Ratepayer Protection Act. The act is H.R. 9340 in Congress and the vote was the United States Senate's cloture vote of September 30, 2026 (roll call 254, 57 to 43), which the station reported with Senator Ricketts's comment; the Daily Record carries that vote from other outlets. Returned to draft.

  2681. · Nebraska · the duplicate mark of a scorecard event

    Before
    none
    After
    7740
    Why
    The sentence places the vote in the Nebraska Senate. The source (News Channel Nebraska, October 1, 2026) reports the United States Senate's cloture vote on H.R. 9340 of September 30, 2026, roll call 254, rejected 57 to 43 with three fifths required; the Nebraska Legislature has 49 members in one chamber, so no vote of it totals 100. Superseded by the national row's event stating the Senate's vote from the Senate's own roll call.

  2682. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    The classifier marked this line as not a figure in its unit field, and the figure reader took the mark for a unit, so the row was published with that mark as its unit (card 9691, the bulk approve of 2026-09-25). The number is also a forecast for 2030, which the record does not carry as a disclosed figure. Returned to draft, off every page (docs/batch-held-lines-1002.md).

  2683. · Project Beehive · the record of a news item

    Before
    After
    valar-atomics-price-data-center-ut
    Why
    The item reports Valar Atomics' Project Beehive in Carbon County and is linked to its record.

  2684. · Project Beehive · the record of a news item

    Before
    volition-spanish-fork-ut
    After
    valar-atomics-price-data-center-ut
    Why
    The item reports Valar Atomics' Project Beehive in Carbon County; its card had been hinted to Volition Spanish Fork, a different Utah record, and the item linked there.

  2685. · Project Beehive · the headline of a news item

    Before
    2 big data centers are coming to Utah’s coal country. How they’ll be powered has residents ‘up in arms.’ - sltrib.com
    After
    2 big data centers are coming to Utah’s coal country. How they’ll be powered has residents ‘up in arms.’
    Why
    The publisher's name and the headline as the Tribune prints them, without Google News's suffix.

  2686. · Project Beehive · the outlet of a news item

    Before
    sltrib.com
    After
    The Salt Lake Tribune
    Why
    The publisher's name and the headline as the Tribune prints them, without Google News's suffix.

  2687. · Project Beehive · the record of a news item

    Before
    After
    valar-atomics-price-data-center-ut
    Why
    The item reports Valar Atomics' Project Beehive in Carbon County and is linked to its record.

  2688. · Project Beehive · the record of a news item

    Before
    volition-spanish-fork-ut
    After
    valar-atomics-price-data-center-ut
    Why
    The item reports Valar Atomics' Project Beehive in Carbon County; its card had been hinted to Volition Spanish Fork, a different Utah record, and the item linked there.

  2689. · Project Beehive · the summary of a news item

    Before
    Valar Atomics plans Project Beehive, a nuclear powered data center on 9,500 acres of federal land near Price, Utah with 456 small reactors producing 9.6 gigawatts of power.
    After
    Valar Atomics plans Project Beehive, data centers powered by some 456 small nuclear reactors producing around 9.6 gigawatts, on more than 9,000 acres of federal land near Price, Utah.
    Why
    NPR reported more than 9,000 acres of federal land; 9,500 acres is its total with the state land, which the item had given as federal.

  2690. · Project Beehive · the outlet of a news item

    Before
    Georgia Public Broadcasting
    After
    NPR
    Why
    Georgia Public Broadcasting's page carried NPR's story; the item cites NPR's own page.

  2691. · Project Beehive · the url of a news item

    Before
    https://www.gpb.org/news/2026/09/30/startup-wants-build-massive-nuclear-powered-data-center-on-public-land-in-utah
    After
    https://www.npr.org/2026/09/30/nx-s1-5983482/valar-atomic-nuclear-data-center-project-beehive-utah
    Why
    Georgia Public Broadcasting's page carried NPR's story; the item cites NPR's own page.

  2692. · Project Beehive · the record of a news item

    Before
    After
    valar-atomics-price-data-center-ut
    Why
    The item reports Valar Atomics' Project Beehive in Carbon County and is linked to its record.

  2693. · a record · the summary of a news item

    Before
    Mat-Su Borough mayor vetoed assembly resolution to help Terra Energy market borough land for data centers or large industrial facilities, citing risk and insufficient vetting.
    After
    Matanuska-Susitna Borough mayor vetoed assembly resolution to help Terra Energy market borough land for data centers or large industrial facilities, citing risk and insufficient vetting.
    Why
    The borough's short form, which the writing rule reads as a hyphenated compound, replaced by its own name, Matanuska-Susitna Borough; nothing else changed. Found when the sentence stopped the site build on 2026-10-01.

  2694. · a record · the summary of a news item

    Before
    Saskatchewan NDP calls for moratorium on construction of large scale AI data centers pending public consultation.
    After
    Saskatchewan's NDP called for a moratorium on construction of large scale AI data centre projects pending public consultations, citing concerns over power costs and environmental impacts.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2695. · a record · the summary of a news item

    Before
    Grayson County confirms $11 billion data center planned for Wildwood Commerce Park, dubbed Project Lightning.
    After
    Grayson County publicly confirmed an $11 billion data center project planned for Wildwood Commerce Park in neighboring Carroll County, known as Project Lightning.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2696. · a record · the summary of a news item

    Before
    Focus NJ report backs managed AI data center expansion in New Jersey.
    After
    A Focus NJ report backed expansion of managed AI data centers in New Jersey as part of the state's digital infrastructure strategy.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2697. · a record · the summary of a news item

    Before
    Tech giants pledge to pay more for data center electricity to protect ratepayers, signed at White House.
    After
    Tech executives from Google, Microsoft, Meta, Oracle, xAI, OpenAI and Amazon signed a White House pledge to pay for AI data center infrastructure and power costs without increasing utility bills.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2698. · a record · the summary of a news item

    Before
    Ohio lawmakers want data center deals made public.
    After
    Ohio lawmakers introduced the No Secrets for Data Centers Act, a bill aimed at requiring public disclosure of data center company agreements.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2699. · a record · the summary of a news item

    Before
    Sarasota County commissioners voted to halt acceptance and approval of large scale data centers for at least one year and signaled intent to pursue a permanent ban.
    After
    Sarasota County voted to halt acceptance of large data center proposals for at least one year, citing utility and environmental concerns, and commissioners indicated interest in a permanent ban.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2700. · Google Haskell County data center · the summary of a news item

    Before
    Google and Intersect launched construction on the Meitner Energy Center, a co located data center and generation complex in Gray and Roberts Counties, Texas, with over 1 GW of wind, solar, battery storage, and gas generation.
    After
    Google and Intersect launched construction on the Meitner Energy Center in the Texas Panhandle, pairing a data center with over 1 gigawatt of wind, solar, and battery storage plus gas backup.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2701. · a record · the summary of a news item

    Before
    Data centers emerge as key issue in Ohio's 9th congressional district race, with both candidates criticizing opponent positions.
    After
    Both candidates in Ohio's 9th congressional district race are criticizing their opponent over data center positions, making the issue central to the campaign.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2702. · a record · the summary of a news item

    Before
    Baltimore County Council unanimously extends data center moratorium for another year, citing need to study impacts and 30 pending applications.
    After
    Baltimore County Council unanimously extended its data center moratorium for another year, responding to resident and environmental group concerns while studying industry impacts.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2703. · a record · the summary of a news item

    Before
    Data center construction in the US boosts demand for skilled trades workers; job openings for welders and pipefitters rose 164 percent year over year.
    After
    US data center construction has raised demand for skilled trades workers; welders and pipefitters saw 164% job growth, with strongest gains in Houston and Birmingham.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2704. · Brookwood Proposed Data Center · the summary of a news item

    Before
    Former Brookwood mayor says residents had no transparency on planned $3.2 billion data center.
    After
    A former Brookwood mayor criticized a planned $3.2 billion data center for lacking transparency with residents, while supporters touted job and revenue potential.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2705. · a record · the summary of a news item

    Before
    Lincoln County Board of Commissioners to hear update on Nebraska Data Center Task Force.
    After
    Lincoln County Board of Commissioners will receive an update on the Nebraska Data Center Task Force at a meeting on September 25, 2026.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2706. · a record · the summary of a news item

    Before
    Pennsylvania DEP invites comments on air quality permit for 156 diesel generators at Greenfield Road Phase 2 data center in Lancaster.
    After
    Pennsylvania DEP invites public comments on air quality permit for 156 diesel generators at Greenfield Road data center Phase 2 project in Lancaster.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2707. · a record · the summary of a news item

    Before
    Mayor Joe Cobb discusses potential data center at Wood Haven Technology Park and addresses citizen concerns.
    After
    Mayor Joe Cobb discusses the City Council's role in a potential data center sale at Wood Haven Technology Park and attempts to address community concerns.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2708. · a record · the summary of a news item

    Before
    A potential data center coming to Wood Haven Technology Park faces neighbor concerns about cost of living, traffic, and environmental impacts.
    After
    Community members express concerns about a potential data center at Wood Haven Technology Park including higher cost of living, increased traffic and environmental impacts.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2709. · a record · the summary of a news item

    Before
    Facebook post claims permitting reform is popular in Washington but facilitating data centers is toxic with voters.
    After
    Permitting reform is popular in Washington state but facilitating data centers is politically toxic with voters according to reporting from Grist.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2710. · Stratos Project · the summary of a news item

    Before
    Box Elder County commissioners approved a massive 40,000 acre, 9 gigawatt AI data center project backed by Kevin O'Leary; residents seek November referendum.
    After
    Box Elder County commissioners approved the Stratos Project, a 9 gigawatt AI data center backed by Kevin O'Leary despite protests from residents citing environmental and community concerns.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2711. · Project Jupiter · the summary of a news item

    Before
    Oracle says Project Jupiter remains on track despite force majeure notice allowing up to three year rent payment deferral if power delays occur.
    After
    Oracle says Project Jupiter data center near Santa Teresa remains on schedule despite sending a force majeure notice allowing potential three year payment delay if power supply and natural gas pipeline are not ready on time.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2712. · a record · the summary of a news item

    Before
    Colleton County residents raise concerns over proposed data center near ACE Basin and power plant on Edisto River; developer seeks zoning changes.
    After
    Residents raised environmental concerns about Eagle Rock Partners' proposed data center near Colleton County's ACE Basin and an associated power plant, with the developer projecting six billion dollars in county tax revenue if completed by 2030.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2713. · a record · the summary of a news item

    Before
    Richmond Times-Dispatch provides index of its reporting on Gov. Spanberger's data center policies launched in September 2026.
    After
    Virginia Gov. Abigail Spanberger proposed a new data center accountability framework to give local and state officials more control over when, where, and how data centers are built.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2714. · Google West Memphis Data Center · the summary of a news item

    Before
    Little Rock Regional Chamber supports Google's Little Rock data center as needed investment.
    After
    Little Rock Regional Chamber expressed support for Google's data center as a needed investment for the region.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2715. · a record · the summary of a news item

    Before
    U.S. Representative Gabe Vasquez backs data center moratorium in Grant County and champions federal bills to end tax breaks and require developers to cover infrastructure costs.
    After
    U.S. Rep. Gabe Vasquez backed a Grant County, New Mexico moratorium on data centers and championed federal legislation to end tax breaks for data center developers and protect ratepayers from cost increases.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2716. · a record · the summary of a news item

    Before
    New Era Energy & Digital's Texas Critical Data Center secures 207 MW power agreement for Phase 1 on 493 acre Odessa campus; construction expected 2027.
    After
    Texas Critical Data Center Phase 1 secured 207 MW power commitment for its 493 acre Odessa campus with planned Q3 2027 deliveries, having obtained property, construction permits, and environmental approvals.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2717. · a record · the summary of a news item

    Before
    New Era Energy subsidiary secures 20 year power purchase agreement with Vistra affiliate Luminant for 200-207 MW at Texas Critical Data Center Phase 1 in Midland, power delivery Q3 2027.
    After
    New Era Energy secured a 20 year, 200-207 MW power purchase agreement with Luminant for Phase 1 of its Texas Critical Data Center in Midland, with power deliveries expected in Q3 2027.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2718. · a record · the summary of a news item

    Before
    Aligned Data Centers breaks ground on Project Caprock, a 540 MW data center campus in Hale County, Texas.
    After
    Aligned Data Centers announced groundbreaking on Project Caprock, a 540 MW campus in Hale County near Abernathy, Texas, with 1.65 million square feet across six buildings and expected Q1 2027 opening of first facility.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2719. · a record · the summary of a news item

    Before
    Survey finds some North Texas governments feel unprepared for data center growth but content blocked from view.
    After
    A survey of North Texas local governments found many feel unprepared for rapid data center development and growth in the region.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2720. · a record · the summary of a news item

    Before
    President Trump announces creation of AI Force and calls fears of AI superintelligence a hoax, dismissing opposition to data center development.
    After
    President Trump announced creation of an AI Force and AI czar position, dismissed AI safety concerns as a hoax, and characterized opposition to data center development as a distraction from AI growth.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2721. · a record · the summary of a news item

    Before
    Democratic gubernatorial candidate David Jolly calls for a complete ban on data centers in Florida after visiting Northern Virginia.
    After
    Former U.S. Representative David Jolly said a complete ban on large data centers in Florida should be considered, citing public opposition to the facilities.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2722. · Google Michigan City data center · the summary of a news item

    Before
    Union reaches agreement with developer over Google data center in Michigan City, resolving labor dispute by requiring local workers through union contractors for Phase II.
    After
    Union agreement reached on Google Michigan City data center Phase II with developer Phoenix Construction to hire local workers through IUOE Local 150.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2723. · a record · the summary of a news item

    Before
    Soluna completes 83 MW Kati 1 data center in Texas with renewable power integration and achieves Base Load classification.
    After
    Soluna completed 83 MW Kati 1 data center in Willacy County, Texas with renewable power; ERCOT classified 166 MW full campus as Base Load.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2724. · OpenAI Effingham County Data Center · the summary of a news item

    Before
    State DRI report on OpenAI's Effingham County data center discloses 1,400 acres, 3,210 MW power demand, 30,000 gallons daily water use, and protected wetlands.
    After
    Georgia state development report reveals OpenAI Project Camellia data center seeks $20 billion investment with record 3,210 MW peak electrical load in Effingham County.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2725. · Hyperscale Data Dowagiac AI Data Center · the summary of a news item

    Before
    Hyperscale Data invests more than $70 million in Michigan AI data center and announces potential 20 year contract revenue exceeding $3 billion with a neocloud provider beginning operations in November 2026.
    After
    Hyperscale Data invested $70 million in Michigan AI data center with potential contract revenue exceeding $3 billion over 20 years.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2726. · Miller County Data Center · the summary of a news item

    Before
    Proposals for large scale AI data centers in Bowie County, Texas face community and political resistance.
    After
    Large scale AI data center proposals in Bowie County, Texas face community and political resistance.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2727. · Pittsburg County Data Center · the summary of a news item

    Before
    A meeting was held in Pittsburg County to discuss a possible data center project with an unspecified timeline for beginning construction.
    After
    Pittsburg County leaders held a meeting to discuss a proposed data center, with community resistance evident in public comments.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2728. · a record · the summary of a news item

    Before
    Lancium CEO says Abilene AI data center is fully financed with 15 year Oracle and 20 year Microsoft commitments.
    After
    Lancium CEO states the Stargate AI data center in Abilene is fully financed with 15 year Oracle and 20 year Microsoft commitments, addressing power supply and noise concerns.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2729. · Meta El Paso data center · the summary of a news item

    Before
    Rowan Digital Infrastructure's three project, $4.2 billion Temple data center campus advances with five of six buildings approved or under construction. The sixth building enters final city approval processes.
    After
    Rowan Digital Infrastructure's three project Temple data center campus totaling at least $4.2 billion is advancing with five of six buildings approved or under construction, using air cooled closed loop systems and committing to water infrastructure investments.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2730. · a record · the summary of a news item

    Before
    Pennsylvania Republican Rep. Rob Bresnahan campaigns on data center limits while holding stock in data center operators and tech companies, raising concerns about conflicts of interest.
    After
    Pennsylvania Rep. Rob Bresnahan campaigns for municipal control over data centers while holding significant investments in companies that develop, operate and supply data center infrastructure.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2731. · a record · the summary of a news item

    Before
    Proposed data center would replace former Dauphin Highlands Golf Course in Swatara Township, Pennsylvania with two 30-35 foot buildings.
    After
    Proposed data center development in Swatara Township, Pennsylvania would place two one story buildings on former golf course site, subject to township zoning restrictions.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2732. · a record · the summary of a news item

    Before
    House Republicans blocked state and local governments' ability to protect residents from AI data centers through the One Big Beautiful Bill Act.
    After
    House Republicans blocked a state and local AI data center moratorium provision in the One Big Beautiful Bill Act, preventing local governments from restricting AI data centers.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2733. · a record · the summary of a news item

    Before
    Florida council to bring back data center moratorium vote.
    After
    A Florida coastal council announced plans to bring back a data center moratorium vote, indicating organized opposition to data center development in the Treasure Coast area.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2734. · a record · the summary of a news item

    Before
    Opinion argues Manitoba not positioned to cash in on data centre opportunities; cites Bell Canada investments in B.C. and Saskatchewan.
    After
    Opinion piece argues Manitoba is not positioned to attract large data center investment due to electrical capacity constraints, contrasting with recent announcements of Bell Canada facilities in British Columbia and Saskatchewan.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2735. · a record · the summary of a news item

    Before
    Atlanta now leads North America in data center construction with 2,882 MW under construction, the highest of any U.S. primary market, per CBRE report.
    After
    Atlanta leads North America in data center construction with 2,882 megawatts under construction, the highest capacity in any U.S. market, according to CBRE research.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2736. · a record · the summary of a news item

    Before
    Four New Mexico lawmakers plan to propose statewide data center moratorium, citing concerns about industry pace relative to water systems and communities.
    After
    Four New Mexico lawmakers plan to propose a statewide data center moratorium, citing concerns about the industry moving faster than laws and community systems can manage.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2737. · Meta Louisiana data center · the summary of a news item

    Before
    Gov. Landry and Richland Parish superintendent meet with Trump at White House, Trump announces ratepayer protection pledge signed by 220 partners, Landry says Louisiana deal will save ratepayers $2.6 billion.
    After
    Governor Landry and Richland Parish superintendent met with President Trump at the White House to discuss the ratepayer protection pledge and Meta's $50 billion investment in northeast Louisiana.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2738. · Yukon Data Center · the summary of a news item

    Before
    Oklahoma residents packed a council meeting to criticize leaders over a proposed data center development. The turnout demonstrates significant public concern about the project.
    After
    Yukon, Oklahoma residents packed a council meeting June 29 to oppose Beltline Energy's proposed data center development spanning Yukon, Luther, and Piedmont, with some calling for mayor and city manager removal.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2739. · a record · the summary of a news item

    Before
    Saskatchewan contractors have begun work on Bell Canada's Regina AI data centre. Construction has started on the project.
    After
    Bell Canada has hired Saskatchewan contractors to begin early phases of construction on its AI data centre south of Regina in RM of Sherwood.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2740. · a record · the summary of a news item

    Before
    Saskatchewan NDP demands government transparency regarding a Bell AI data centre. The headline indicates a political statement about a proposed data centre project.
    After
    Saskatchewan NDP continues to demand government transparency surrounding Bell AI data centre under construction in RM of Sherwood.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2741. · a record · the summary of a news item

    Before
    The Green Party called for a province wide halt on AI data centres until safeguards are in place. This represents a public advocacy position on data center policy in Ontario.
    After
    Ontario Green Party leader called for a province wide moratorium on AI data centres until environmental and health safeguards are established, after Mississauga paused new developments.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2742. · a record · the summary of a news item

    Before
    Ontario government rolls out proposed framework for AI data centres in communities. The provincial government announces regulatory framework for data centre development.
    After
    Ontario government unveiled a framework for AI data centre development that requires facilities to fund their own electricity but denies municipal councils veto power over projects.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2743. · a record · the summary of a news item

    Before
    Residents in a New Jersey city opposed a Big Tech data center proposal. The headline indicates local resistance to a data center project.
    After
    New Jersey residents cheered when a city removed data centres from its redevelopment plan, reflecting growing municipal opposition to AI data centre development.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2744. · a record · the summary of a news item

    Before
    A Stockton poll finds more than half of New Jersey residents support banning new AI data centers. The survey measures public sentiment on data center development.
    After
    A Stockton University poll found 56 percent of New Jersey voters support banning new AI data centres, and 74 percent believe AI will eliminate more jobs than it creates.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2745. · a record · the summary of a news item

    Before
    Telus outlined a $50 billion network infrastructure investment to support Canada's AI drive. The company is committing significant capital to network infrastructure supporting AI development.
    After
    Telus announced a five year CA$70 billion investment in network infrastructure to support sovereign AI data centres in British Columbia and Quebec and expand rural wireless coverage.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2746. · a record · the summary of a news item

    Before
    Alberta government held second town hall on AI data centres after community opposition at first event; residents voiced concerns about regulation and environmental impacts.
    After
    Alberta government held town halls on its AI data centre plan amid strong public opposition and concerns about water use, environmental impacts, and inadequate consultation with First Nations.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2747. · a record · the summary of a news item

    Before
    A First Nation defeated a legal challenge from Kevin O'Leary backed data centre developer. The court ruling advances the First Nation's position in ongoing disputes over the project.
    After
    Alberta court rejected a developer's bid to dismiss a First Nation's judicial review of water permits for an AI data centre near Grande Prairie, allowing the legal challenge to proceed.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2748. · Google Lincoln Data Center · the summary of a news item

    Before
    Construction began on a $10 million wastewater line to transport cooling water from the Lincoln data center to a recovery site. The project is underway.
    After
    Google is funding a $10 million wastewater project in Lincoln to transport non contact cooling water from its data center to the Northeast Water Resource Recovery Facility for treatment before discharge into Salt Creek.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2749. · a record · the summary of a news item

    Before
    The Nebraska governor announced plans to sign an executive order on data centers. The specific provisions cannot be determined from the headline alone.
    After
    Gov. Jim Pillen announced he would sign an executive order ending state tax incentives for large scale data centers and creating a task force to protect Nebraska's natural resources.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2750. · a record · the summary of a news item

    Before
    Governor Pillen ends tax incentives for data center developers building in Nebraska. The action removes a key state level incentive for future data center projects.
    After
    Gov. Jim Pillen signed an executive order ending state tax incentives for data center developers under Nebraska's ImagiNE Nebraska Act and establishing a task force to protect natural resources.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2751. · a record · the summary of a news item

    Before
    Article examines lessons from Maine's data center moratorium debate for the construction industry. It analyzes policy outcomes from the moratorium dispute.
    After
    Maine Governor Janet Mills vetoed a bill imposing a 16 month moratorium on data centers larger than 20 megawatts; the legislature failed to override the veto.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2752. · a record · the summary of a news item

    Before
    An executive order paved the way for Wyoming data centers while Colorado communities slowed development. Wyoming advanced policy while Colorado took a different approach.
    After
    Wyoming Governor Mark Gordon signed an executive order establishing data center development framework; Cheyenne rejected a moratorium while Denver and other communities imposed pauses on data center projects.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2753. · a record · the summary of a news item

    Before
    Wyoming Governor signed an executive order setting rules for data center development. The order establishes regulatory framework for the industry.
    After
    Wyoming Governor Mark Gordon signed an executive order establishing a statewide framework for data center development with requirements for water use, wildlife impacts, grid reliability, and workforce development.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2754. · Montgomery Meta Investment · the summary of a news item

    Before
    Wyoming officials stated Meta's 715,000 square foot data center caused water system contamination. The report links a specific data center project to environmental damage.
    After
    Wyoming officials say Meta's Cheyenne data center construction contaminated the city's recycled water system with a rare bacterium, prompting wastewater policy changes.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2755. · a record · the summary of a news item

    Before
    West Virginia's governor explained how his state learned from data center mistakes. This reflects state leadership commentary on data center policy experience.
    After
    West Virginia Governor Patrick Morrisey discusses his state's plan to attract data centers and lessons learned from past mistakes.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2756. · a record · the summary of a news item

    Before
    Fedorchak, likely a North Dakota official, comments on data centers. No details of the specific statement are available from the headline.
    After
    North Dakota Rep. Julie Fedorchak supports the federal Ratepayer Protection Act for data centers but argues local communities should make permitting decisions; she urges transparency on noise, roads, and energy impacts.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2757. · a record · the summary of a news item

    Before
    A data center is proposed near Mandan, North Dakota, raising concerns about its proximity to schools. The location and developer are not identified in the headline.
    After
    Stark Power is proposing a data center about 5 miles north of downtown Mandan, North Dakota; residents and the planning commission raised concerns about proximity to schools and the project entered the planning approval process.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2758. · a record · the summary of a news item

    Before
    Data center debate intensifies ahead of a special legislative session in North Dakota. The headline indicates policy activity regarding data center development.
    After
    North Dakota legislators debate two bills during a special session: one proposing a moratorium on AI data center construction and another banning non disclosure agreements for public officials; also proposed amendments to remove sales tax exemption on data center equipment.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2759. · a record · the summary of a news item

    Before
    A North Dakota legislative committee met to examine policy and community impacts of data center expansion. The hearing reflects state level deliberation on data center development.
    After
    The North Dakota Legislative Management Artificial Intelligence and Data Center Committee convened to review policy, electrical grid, and regulatory frameworks for data center development across the state.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2760. · a record · the summary of a news item

    Before
    Opposition to data centers is influencing midterm elections, with critics arguing data centers are not needed. The headline captures public resistance to data center development becoming a political issue.
    After
    A May 2026 Gallup poll found 71% of Americans oppose data center construction, while a July survey showed opposition rising sharply across both political parties, with governors in multiple states moving to restrict or regulate data center development.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2761. · a record · the summary of a news item

    Before
    Governor Kathy Hochul launched the first statewide moratorium on new hyperscale data centers in New York. The action halts new data center projects pending review.
    After
    New York Governor Kathy Hochul signed an executive order establishing the nation's first moratorium on new hyperscale data centers for up to one year while developing regulatory standards.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2762. · a record · the summary of a news item

    Before
    West Virginia Attorney General Morrisey announced state certifications for two Mason County data center projects. The certifications represent approval of the projects to proceed.
    After
    West Virginia Governor Patrick Morrisey announced state certifications for two high impact data center projects, advancing development amid community opposition over energy and water impacts.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2763. · Stratos Project · the summary of a news item

    Before
    Kevin O'Leary dismissed critics of the Stratos data center as professional protesters and suggested some opposition is being amplified by artificial intelligence. The article headline indicates his characterization of the opposition.
    After
    Kevin O'Leary dismissed opponents of his Utah data center as professional protesters amplified by artificial intelligence.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2764. · Stratos Project · the summary of a news item

    Before
    Kevin O'Leary told Utah Senate President J. Stuart Adams that he will trim acreage around Locomotive Springs and Interstate 80 from the Stratos project and said it will not be the largest data center in the world. The project has faced public opposition and political pressure.
    After
    Celebrity investor Kevin O'Leary said he will reduce acreage of his planned Box Elder County data center campus and it will not be the world's largest.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2765. · a record · the summary of a news item

    Before
    A judge is weighing whether to block Arkansas news outlets from publishing details of a data center pact. This represents a legal dispute over a data center agreement.
    After
    Federal judge considered blocking Arkansas news outlets from publishing details of a Google data center power agreement after Entergy claimed trade secret violations.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2766. · a record · the summary of a news item

    Before
    A study examines the economic impact of AI data centers in rural Arkansas. The report addresses effects on local economies.
    After
    A study weighs economic impacts of artificial intelligence data center growth across rural and urban U.S. communities.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2767. · SpaceXAI Memphis data centers · the summary of a news item

    Before
    A federal judge denied Entergy a temporary restraining order to block reporting on a West Memphis data center agreement. The ruling allows continued public disclosure of information about the project.
    After
    A federal judge denied Entergy's request to stop news organizations from reporting on a confidential data center agreement with Google near West Memphis; Google committed to covering $526 million in upfront costs plus operational funding over 20 years.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2768. · a record · the summary of a news item

    Before
    An article headline indicates that as cities around the country place moratoriums on data center building, Alaska sees the trend as an opportunity. The provided text does not contain substantive content beyond the headline.
    After
    As New York and Seattle implement data center moratoriums, Alaska is positioning itself as an attractive alternative for data center development.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2769. · a record · the summary of a news item

    Before
    A Missouri farmer invited data center developers to buy his land as a $6.3 billion project faces growing local opposition. The farmer supports the development despite community resistance.
    After
    A $6.3 billion data center project in Nodaway County faces opposition and has been stalled by commissioners' moratorium while they negotiate a development agreement with Scale Microgrids.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2770. · a record · the summary of a news item

    Before
    A new checklist was created to help Missouri communities ask data center developers important questions. The tool aims to improve community engagement with data center proposals.
    After
    Missouri House Future Caucus unveiled AI Infrastructure Community Evaluation Framework checklist to help local communities evaluate data center proposals transparently and protect community interests.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2771. · a record · the summary of a news item

    Before
    A judge halted construction of Pine Island's hyperscale data center project. The legal action brings the project to a stop.
    After
    A Minnesota judge granted a temporary restraining order halting construction of Project Skyway hyperscale data center near Rochester after environmental advocacy lawsuit challenged adequacy of environmental review.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2772. · a record · the summary of a news item

    Before
    A data center company acquired a former Minnesota Star Tribune printing site in downtown Minneapolis. The acquisition signals reuse of an existing structure for data center operations.
    After
    Legacy Investing agreed to acquire the former Minnesota Star Tribune printing facility in Minneapolis and convert it to a 20 megawatt data center with mixed use components.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2773. · a record · the summary of a news item

    Before
    Minneapolis City Council halts new data center developments until November. The moratorium is a jurisdiction wide action on data center projects.
    After
    Minneapolis City Council approved a five month pause on data center construction through November 2026, citing need to study environmental impacts and community concerns.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2774. · a record · the summary of a news item

    Before
    A data center lawsuit could cost Inver Grove Heights taxpayers millions and a path forward is being developed. The dispute involves financial liability related to a data center project.
    After
    Inver Grove Heights faces a potential $20 million lawsuit from data center company Q'Levr if city's one year moratorium applies; council voted to exclude the company but requires two more readings.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2775. · a record · the summary of a news item

    Before
    Minneapolis Mayor Jacob Frey says data centers should be regulated and not serve as sole use of a property. The statement reflects municipal policy concerns about data center development.
    After
    Minneapolis Mayor Jacob Frey said data centers must be regulated to ensure community benefit, banned as sole property use, and part of multiuse developments to drive tax revenue.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2776. · a record · the summary of a news item

    Before
    A judge ruled in favor of El Dorado citizens' petition to ban data centers. The decision upheld a community effort to restrict data center development.
    After
    An El Dorado, Kansas judge ruled that citizens' petition to ban data centers is a legislative matter, allowing voters to decide in a November ballot if a ban passes for 10 years.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2777. · a record · the summary of a news item

    Before
    Zach Lahn calls for state regulation of data centers. The statement represents a policy position on data center oversight.
    After
    Iowa GOP gubernatorial candidate Zach Lahn called for state level data center regulations, a temporary moratorium, no tax incentives, and requiring developers to pay electricity costs and address environmental concerns.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2778. · a record · the summary of a news item

    Before
    Zach Lahn proposed a change affecting data centers. The nature of the proposal cannot be determined from the headline alone.
    After
    Iowa Republican gubernatorial candidate Zach Lahn called for a temporary moratorium on data center projects, proposing state level regulations and requiring developers to benefit local communities.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2779. · a record · the summary of a news item

    Before
    An opinion or statement was made about how data centers can be built according to Iowa standards. The headline suggests advocacy for a particular approach to data center development.
    After
    Swati Dandekar, chairman of Bright Future Iowa, said data centers fit Iowa's innovation tradition and urged clear standards rather than moratoriums to manage responsible development.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2780. · a record · the summary of a news item

    Before
    Colorado Springs administratively approved a data center on Garden of the Gods Road. This represents a local jurisdictional approval action.
    After
    Colorado Springs administratively approved the Project Taurus AI data center at the former Intel chip manufacturing facility near Garden of the Gods Road.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2781. · a record · the summary of a news item

    Before
    Xcel Energy's data center plan faces opposition from Colorado residents and advocates. The project status and details are not specified in the headline.
    After
    Colorado residents and advocates pushed back on Xcel Energy's large load tariff pricing plan for data centers, demanding tighter environmental standards and cost protections.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2782. · a record · the summary of a news item

    Before
    Alabama Attorney General made a statement about advocating for consumers amid AI data center buildout in the state. The statement indicates concern about consumer protection as data centers expand.
    After
    Alabama Attorney General Steve Marshall said the state will continue advocating for consumers as AI data centers expand, addressing concerns about energy rate impacts.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2783. · a record · the summary of a news item

    Before
    Britt commented on data center controversy, stating 'We've got to win this race, but it has to be right for the people.' The statement reflects a political position on data center development.
    After
    U.S. Senator Katie Britt said Alabama must balance data center growth with community concerns about energy costs, environmental effects and economic impact.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2784. · a record · the summary of a news item

    Before
    A poll showed most New Mexico voters oppose large data centers. The finding reflects public sentiment on data center development in the state.
    After
    Poll shows 65 percent of New Mexico voters oppose large data centers and 75 percent support state moratorium pending regulatory standards.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2785. · a record · the summary of a news item

    Before
    Nevada is reviewing its data center tax breaks while counties are excluded from the review process. The review may lead to changes in state incentive policy.
    After
    Nevada state officials reviewing data center tax break program without consulting county governments that approve projects, raising concerns about program sustainability.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2786. · a record · the summary of a news item

    Before
    A federal board halted approval of a 167 megawatt data center in Nevada. The full text is unavailable but the headline indicates a jurisdiction action on a specific project affecting its status.
    After
    Interior Department appeals board halted federal approval of 167 MW Townsite data center on BLM land, finding the agency violated environmental law by reusing a solar project review.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2787. · a record · the summary of a news item

    Before
    Georgia congressional candidates discussed data centers as Trump pushes for more development. The candidates commented on data center policy during the 2026 election cycle.
    After
    Congressional candidates in Georgia's District 14 debate data center impact on energy rates and community input, recognizing economic importance but differing on regulation.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2788. · a record · the summary of a news item

    Before
    Georgia data centers are projected to demand more energy than the state can provide. The report raises questions about grid capacity to support industry growth.
    After
    A nonprofit study finds that Georgia data center energy demand will exceed the state's power supply capacity.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2789. · a record · the summary of a news item

    Before
    Georgia officials Warnock and Kemp clashed over the state's data center boom. The headline indicates disagreement between named figures about data center policy.
    After
    U.S. Senator Raphael Warnock calls for a moratorium on data center development in Georgia, citing concerns about electricity costs, water use, and pollution, while Governor Brian Kemp opposes a statewide pause.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2790. · a record · the summary of a news item

    Before
    Georgia leads the US in data center construction. The headline reports a comparative ranking of data center building activity by state.
    After
    Atlanta metro area leads the United States in data center capacity under construction as of first half 2026, surpassing Northern Virginia for the first time by power consumption projections.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2791. · Oakline at Mill Creek · the summary of a news item

    Before
    Oregon state agency agreed to sell 32 acres to Verrus for $6.7 million in May 2025 for data center at Mill Creek Corporate Center in Salem; Governor Kotek pulled property off table in July after learning of project.
    After
    Oregon state agency agreed to sell 32 acres to Verrus at Mill Creek Corporate Center in Salem for $6.7 million in May 2025 for a Google backed data center project, but the sale was cancelled in July 2026 after Governor Tina Kotek learned about the data center use.
    Why
    the record's rules: the sentence was the source's wording or carried a number not in the card's facts; written again from the article

  2792. · a record · the data year of a figure

    Before
    2026
    After
    2023
    Why
    The data year read 2026, the year of the PR Newswire release of September 9, 2026 that reported the figure. The release says the Lawrence Berkeley National Laboratory's report estimates that United States data centers directly consumed about 66 billion liters of water in 2023, so the figure is for 2023 (the release read on 2026-09-29; the editor's word of that day). The release's date stays the row's source date.

  2793. · a record · the duplicate mark of a figure

    Before
    After
    360e7fa3-52df-4d19-a184-6768f41e1997
    Why
    This row carried 17.4 billion gallons a year from the Lawrence Berkeley National Laboratory's 2024 report, which prints the figure as 66 billion liters consumed on site by US data centers in 2023. The record holds that figure as it is printed (figure 360e7fa3, read from the report's own page), and /numbers and the homepage show it in gallons as arithmetic: 66,000,000,000 liters divided by 3.785411784 liters a gallon is 17,435,355,456 gallons a year. This row repeated that conversion as a figure of its own, so it now defers to the report's row; it stays on file and is listed nowhere as a separate figure (the editor's word of 2026-09-29).

  2794. · St. Louis · the rating of a scorecard row

    Before
    open
    After
    no published rating
    Why
    The scorecard rubric of September 29, 2026 (/methodology#rubric), read against the row's own published events, does not give open: Board Bill 49 sets setbacks, noise rules and renewable power requirements. The Armory permit reads open, and the stronger word sets the row. Until the editor confirms a word the row reads no published rating; the rubric proposes restrictive.

  2795. · Manitoba · the rating of a scorecard row

    Before
    closed
    After
    no published rating
    Why
    The scorecard rubric of September 29, 2026 (/methodology#rubric), read against the row's own published events, does not give closed: The premier announced the project will not go ahead: a denial. The sentence does not say whether the project can come back; a denial it leaves open is decided one project at a time, which reads case by case, and with no path back it would read closed. Until the editor confirms a word the row reads no published rating; the rubric proposes case by case.

  2796. · Trenton · the rating of a scorecard row

    Before
    restrictive
    After
    no published rating
    Why
    The scorecard rubric of September 29, 2026 (/methodology#rubric), read against the row's own published events, does not give restrictive: The ban is on the ballot, not adopted: a measure before the voters. Until the editor confirms a word the row reads no published rating; the rubric proposes case by case.

  2797. · Ashville · the rating of a scorecard row

    Before
    restrictive
    After
    no published rating
    Why
    The scorecard rubric of September 29, 2026 (/methodology#rubric), read against the row's own published events, does not give restrictive: The council rejected the annexation tied to the data center (the sentence leaves a path back) and the project goes to the voters. Until the editor confirms a word the row reads no published rating; the rubric proposes case by case.

  2798. · Ohio · the rating of a scorecard row

    Before
    restrictive
    After
    no published rating
    Why
    The scorecard rubric of September 29, 2026 (/methodology#rubric), read against the row's own published events, does not give restrictive: Two events say the governor paused data centers (4296, through the end of the year; 2659, from October 1); twelve say his pause is on applications for the sales tax exemption. Read as a moratorium on data centers it is restrictive; the sources want a read before the word is confirmed. Until the editor confirms a word the row reads no published rating; the rubric proposes restrictive.

  2799. · California · the rating of a scorecard row

    Before
    case by case
    After
    no published rating
    Why
    The scorecard rubric of September 29, 2026 (/methodology#rubric), read against the row's own published events, does not give case by case: The governor signed seven bills requiring disclosure and rates for data centers. Until the editor confirms a word the row reads no published rating; the rubric proposes restrictive.

  2800. · Pulaski County · the rating of a scorecard row

    Before
    case by case
    After
    no published rating
    Why
    The scorecard rubric of September 29, 2026 (/methodology#rubric), read against the row's own published events, does not give case by case: The Quorum Court passed an ordinance regulating large data centers (noise, fire safety, utility studies); the county judge had seven days to veto it. Until the editor confirms a word the row reads no published rating; the rubric proposes restrictive.

  2801. · Kentucky · the rating of a scorecard row

    Before
    case by case
    After
    no published rating
    Why
    The scorecard rubric of September 29, 2026 (/methodology#rubric), read against the row's own published events, does not give case by case: The governor's order requires data centers to meet pollution requirements and pay going rates. Until the editor confirms a word the row reads no published rating; the rubric proposes restrictive.

  2802. · Saskatchewan · the rating of a scorecard row

    Before
    open
    After
    no published rating
    Why
    The scorecard rubric of September 29, 2026 (/methodology#rubric), read against the row's own published events, does not give open: The provincial framework requires new data centres to be Canadian owned and to supply their own electricity: rules adding conditions, which read restrictive. The approvals of Bell's expansion under it read open, and the stronger word sets the row. Until the editor confirms a word the row reads no published rating; the rubric proposes restrictive.

  2803. · RM of Sherwood · the rating of a scorecard row

    Before
    open
    After
    no published rating
    Why
    The scorecard rubric of September 29, 2026 (/methodology#rubric), read against the row's own published events, does not give open: A rally and the announcement at a summit; no act of the municipality. Until the editor confirms a word the row reads no published rating; the rubric proposes none.

  2804. · Wyoming County · the rating of a scorecard row

    Before
    case by case
    After
    no published rating
    Why
    The scorecard rubric of September 29, 2026 (/methodology#rubric), read against the row's own published events, does not give case by case: The SALDO amendment's noise cap and coordination requirements add conditions. Until the editor confirms a word the row reads no published rating; the rubric proposes restrictive.

  2805. · Armstrong County · the rating of a scorecard row

    Before
    case by case
    After
    no published rating
    Why
    The scorecard rubric of September 29, 2026 (/methodology#rubric), read against the row's own published events, does not give case by case: The one event is the developers' open house, not an act of the county. Until the editor confirms a word the row reads no published rating; the rubric proposes none.

  2806. · Texas · the rating of a scorecard row

    Before
    case by case
    After
    no published rating
    Why
    The scorecard rubric of September 29, 2026 (/methodology#rubric), read against the row's own published events, does not give case by case: The governor directed the environmental commission to halt data center permits until ERCOT completes its audit: a moratorium with an end. Until the editor confirms a word the row reads no published rating; the rubric proposes restrictive.

  2807. · Pennsylvania · the rating of a scorecard row

    Before
    case by case
    After
    no published rating
    Why
    The scorecard rubric of September 29, 2026 (/methodology#rubric), read against the row's own published events, does not give case by case: Executive Order 2026-05 sets requirements and removes data centers from the fast track program. Until the editor confirms a word the row reads no published rating; the rubric proposes restrictive.

  2808. · Washington County · the rating of a scorecard row

    Before
    restrictive
    After
    no published rating
    Why
    The scorecard rubric of September 29, 2026 (/methodology#rubric), read against the row's own published events, does not give restrictive: A commissioner's announced intention to propose a pause; no act of the county. Until the editor confirms a word the row reads no published rating; the rubric proposes none.

  2809. · Arkansas · the rating of a scorecard row

    Before
    open
    After
    no published rating
    Why
    The scorecard rubric of September 29, 2026 (/methodology#rubric), read against the row's own published events, does not give open: The legislature's joint energy committee held hearings on the Google project's power; the commission's approvals read open, and the stronger word sets the row. Until the editor confirms a word the row reads no published rating; the rubric proposes case by case.

  2810. · Quebec · the rating of a scorecard row

    Before
    case by case
    After
    no published rating
    Why
    The scorecard rubric of September 29, 2026 (/methodology#rubric), read against the row's own published events, does not give case by case: The one event is a municipal council's sale of land, filed on the province's row; no act of the province. Until the editor confirms a word the row reads no published rating; the rubric proposes none.

  2811. · Sturgeon County · the rating of a scorecard row

    Before
    restrictive
    After
    no published rating
    Why
    The scorecard rubric of September 29, 2026 (/methodology#rubric), read against the row's own published events, does not give restrictive: Public consultations on the Meta data centers were held in the county: a hearing. The council's resolution asks the Rural Municipalities of Alberta to review the province's rules, a call on another body, which earns nothing. Until the editor confirms a word the row reads no published rating; the rubric proposes case by case.

  2812. · South Dakota · the rating of a scorecard row

    Before
    case by case
    After
    no published rating
    Why
    The scorecard rubric of September 29, 2026 (/methodology#rubric), read against the row's own published events, does not give case by case: The legislature's law requires data centers to pay the costs of their electricity and water: a law adding conditions. Until the editor confirms a word the row reads no published rating; the rubric proposes restrictive.

  2813. · New Mexico · the rating of a scorecard row

    Before
    restrictive
    After
    no published rating
    Why
    The scorecard rubric of September 29, 2026 (/methodology#rubric), read against the row's own published events, does not give restrictive: The land commissioner blocked the Aetherion proposal and the land office denied pipeline rights of way: decided one at a time. The supreme court's pauses are rulings, which never move a rating. Until the editor confirms a word the row reads no published rating; the rubric proposes case by case.

  2814. · Edgerton · the rating of a scorecard row

    Before
    restrictive
    After
    no published rating
    Why
    The scorecard rubric of September 29, 2026 (/methodology#rubric), read against the row's own published events, does not give restrictive: Every event is the city's lawsuit against residents and its dismissal, and a suit never moves a rating. Until the editor confirms a word the row reads no published rating; the rubric proposes none.

  2815. · Kansas · the rating of a scorecard row

    Before
    restrictive
    After
    no published rating
    Why
    The scorecard rubric of September 29, 2026 (/methodology#rubric), read against the row's own published events, does not give restrictive: S.B. 98 gives data centers a 20 year sales tax exemption: an incentive. The lawsuits are cities'. Until the editor confirms a word the row reads no published rating; the rubric proposes open.

  2816. · Idaho · the rating of a scorecard row

    Before
    restrictive
    After
    no published rating
    Why
    The scorecard rubric of September 29, 2026 (/methodology#rubric), read against the row's own published events, does not give restrictive: The state's own act on the row is the 2020 sales tax exemption: an incentive. Until the editor confirms a word the row reads no published rating; the rubric proposes open.

  2817. · Hawaii County · the rating of a scorecard row

    Before
    restrictive
    After
    no published rating
    Why
    The scorecard rubric of September 29, 2026 (/methodology#rubric), read against the row's own published events, does not give restrictive: The planning commission deferred Bill 170: a vote to consider. Until the editor confirms a word the row reads no published rating; the rubric proposes case by case.

  2818. · Rhode Island · the rating of a scorecard row

    Before
    case by case
    After
    no published rating
    Why
    The scorecard rubric of September 29, 2026 (/methodology#rubric), read against the row's own published events, does not give case by case: The events are bills introduced and not passed; no act of the state earns a word. Until the editor confirms a word the row reads no published rating; the rubric proposes none.

  2819. · West Virginia · the rating of a scorecard row

    Before
    closed
    After
    no published rating
    Why
    The scorecard rubric of September 29, 2026 (/methodology#rubric), read against the row's own published events, does not give closed: The state's development framework requires data center projects to be self funded and to cut water use through closed loop cooling: conditions, which read restrictive. H.B. 2014, which lets data centers build their own power and takes zoning away from counties and towns, reads open, and the stronger word sets the row. Until the editor confirms a word the row reads no published rating; the rubric proposes restrictive.

  2820. · Missouri · the rating of a scorecard row

    Before
    case by case
    After
    no published rating
    Why
    The scorecard rubric of September 29, 2026 (/methodology#rubric), read against the row's own published events, does not give case by case: The 2025 law and the commission's large load protections add conditions. The rallies are residents'. Until the editor confirms a word the row reads no published rating; the rubric proposes restrictive.

  2821. · Pittsburg County · the rating of a scorecard row

    Before
    restrictive
    After
    no published rating
    Why
    The scorecard rubric of September 29, 2026 (/methodology#rubric), read against the row's own published events, does not give restrictive: The commissioners tabled the tax incentive districts for Project Emerald: a vote to consider. Until the editor confirms a word the row reads no published rating; the rubric proposes case by case.

  2822. · Louisiana · the rating of a scorecard row

    Before
    restrictive
    After
    no published rating
    Why
    The scorecard rubric of September 29, 2026 (/methodology#rubric), read against the row's own published events, does not give restrictive: The governor's order directs Louisiana Economic Development to develop protections: a study. The commission's approvals and the tax exemption read open. Three events on the row are other states' acts. Until the editor confirms a word the row reads no published rating; the rubric proposes case by case.

  2823. · Weld County · the rating of a scorecard row

    Before
    open
    After
    no published rating
    Why
    The scorecard rubric of September 29, 2026 (/methodology#rubric), read against the row's own published events, does not give open: The April framework requires water and power evidence, sets noise limits and bars data centers from agricultural zones: an ordinance adding conditions. The Global AI approvals read open, and the stronger word sets the row. Until the editor confirms a word the row reads no published rating; the rubric proposes restrictive.

  2824. · Kearney · the rating of a scorecard row

    Before
    case by case
    After
    no published rating
    Why
    The scorecard rubric of September 29, 2026 (/methodology#rubric), read against the row's own published events, does not give case by case: The revised regulations set setbacks, noise limits and closed loop cooling and require a conditional use permit: an ordinance adding conditions. The approvals read open, and the stronger word sets the row. Until the editor confirms a word the row reads no published rating; the rubric proposes restrictive.

  2825. · Salem · the rating of a scorecard row

    Before
    closed
    After
    no published rating
    Why
    The scorecard rubric of September 29, 2026 (/methodology#rubric), read against the row's own published events, does not give closed: A 120 day moratorium: a moratorium with an end date reads restrictive, not closed. Until the editor confirms a word the row reads no published rating; the rubric proposes restrictive.

  2826. · Nevada · the rating of a scorecard row

    Before
    case by case
    After
    no published rating
    Why
    The scorecard rubric of September 29, 2026 (/methodology#rubric), read against the row's own published events, does not give case by case: Executive Order 2026-005 adds conditions: the school support tax paid in full, project costs covered, water standards. Until the editor confirms a word the row reads no published rating; the rubric proposes restrictive.

  2827. · Arizona · the rating of a scorecard row

    Before
    restrictive
    After
    no published rating
    Why
    The scorecard rubric of September 29, 2026 (/methodology#rubric), read against the row's own published events, does not give restrictive: The Corporation Commission approved Project Blue's power supply agreement: an approval, which reads open. The state's three year moratorium is on tax breaks for data centers, not on building them, and a pause on an incentive is not a kind the rubric names; read as the rubric's moratorium it would be restrictive. Until the editor confirms a word the row reads no published rating; the rubric proposes open.

  2828. · Hopkinton · the rating of a scorecard row

    Before
    restrictive
    After
    no published rating
    Why
    The scorecard rubric of September 29, 2026 (/methodology#rubric), read against the row's own published events, does not give restrictive: The council directed the planning board to study a ban ordinance: a study. Until the editor confirms a word the row reads no published rating; the rubric proposes case by case.

  2829. · Colorado · the rating of a scorecard row

    Before
    case by case
    After
    no published rating
    Why
    The scorecard rubric of September 29, 2026 (/methodology#rubric), read against the row's own published events, does not give case by case: The row carries "Colorado declared a drought emergency and placed a moratorium on new data center development" (June 22, 2026), which gives no end date. No other Colorado event names a statewide moratorium, so the source wants a read before the word is confirmed. Until the editor confirms a word the row reads no published rating; the rubric proposes restrictive.

  2830. · Iowa · the rating of a scorecard row

    Before
    closed
    After
    no published rating
    Why
    The scorecard rubric of September 29, 2026 (/methodology#rubric), read against the row's own published events, does not give closed: The events are local moratoriums, petitions and residents' meetings; no act of the state earns a word. Until the editor confirms a word the row reads no published rating; the rubric proposes none.

  2831. · Imperial County · the rating of a scorecard row

    Before
    closed
    After
    no published rating
    Why
    The scorecard rubric of September 29, 2026 (/methodology#rubric), read against the row's own published events, does not give closed: The row's one event is a court ruling, and a suit or a ruling in one never moves a rating. Until the editor confirms a word the row reads no published rating; the rubric proposes none.

  2832. · Butte-Silver Bow County · the rating of a scorecard row

    Before
    restrictive
    After
    no published rating
    Why
    The scorecard rubric of September 29, 2026 (/methodology#rubric), read against the row's own published events, does not give restrictive: A commissioner asked for support to draft a moratorium, and the voter approval initiative is headed to the ballot: votes to consider. No moratorium is adopted. Until the editor confirms a word the row reads no published rating; the rubric proposes case by case.

  2833. · Harrington · the rating of a scorecard row

    Before
    restrictive
    After
    no published rating
    Why
    The scorecard rubric of September 29, 2026 (/methodology#rubric), read against the row's own published events, does not give restrictive: The council voted down an ordinance that would have allowed data centers as a conditional use. The rubric reads a denial closed only with no path back, which the sentence does not give, and names no other word for it. Until the editor confirms a word the row reads no published rating; the rubric proposes none.

  2834. · Baltimore County · the rating of a scorecard row

    Before
    case by case
    After
    no published rating
    Why
    The scorecard rubric of September 29, 2026 (/methodology#rubric), read against the row's own published events, does not give case by case: The council extended its moratorium through 2027. Until the editor confirms a word the row reads no published rating; the rubric proposes restrictive.

  2835. · Maine · the rating of a scorecard row

    Before
    open
    After
    no published rating
    Why
    The scorecard rubric of September 29, 2026 (/methodology#rubric), read against the row's own published events, does not give open: The governor vetoed the moratorium bill and created an advisory council, which has held hearings: a study. Nothing on the row reads open. Until the editor confirms a word the row reads no published rating; the rubric proposes case by case.

  2836. · Pima County · the rating of a scorecard row

    Before
    case by case
    After
    no published rating
    Why
    The scorecard rubric of September 29, 2026 (/methodology#rubric), read against the row's own published events, does not give case by case: A 120 day moratorium, approved September 22. Until the editor confirms a word the row reads no published rating; the rubric proposes restrictive.

  2837. · Piedmont · the rating of a scorecard row

    Before
    restrictive
    After
    no published rating
    Why
    The scorecard rubric of September 29, 2026 (/methodology#rubric), read against the row's own published events, does not give restrictive: The council postponed the rezoning request: a vote to consider. The petitions are residents'. Until the editor confirms a word the row reads no published rating; the rubric proposes case by case.

  2838. · Barber County · the rating of a scorecard row

    Before
    case by case
    After
    no published rating
    Why
    The scorecard rubric of September 29, 2026 (/methodology#rubric), read against the row's own published events, does not give case by case: The commissioners approved Google's data center: an approval. Until the editor confirms a word the row reads no published rating; the rubric proposes open.

  2839. · Vineland · the rating of a scorecard row

    Before
    closed
    After
    no published rating
    Why
    The scorecard rubric of September 29, 2026 (/methodology#rubric), read against the row's own published events, does not give closed: The Planning Board approved the project's second phase. The fines and the noise citation are the state's and the county's, and the suit is the residents'. Until the editor confirms a word the row reads no published rating; the rubric proposes open.

  2840. · Lacombe · the rating of a scorecard row

    Before
    restrictive
    After
    no published rating
    Why
    The scorecard rubric of September 29, 2026 (/methodology#rubric), read against the row's own published events, does not give restrictive: The row's events are residents' comments at a provincial town hall; no act of the town earns a word. Until the editor confirms a word the row reads no published rating; the rubric proposes none.

  2841. · Cass County · the rating of a scorecard row

    Before
    closed
    After
    no published rating
    Why
    The scorecard rubric of September 29, 2026 (/methodology#rubric), read against the row's own published events, does not give closed: A 12 month moratorium: a moratorium with an end date reads restrictive, not closed. Until the editor confirms a word the row reads no published rating; the rubric proposes restrictive.

  2842. · Clackamas County · the rating of a scorecard row

    Before
    restrictive
    After
    no published rating
    Why
    The scorecard rubric of September 29, 2026 (/methodology#rubric), read against the row's own published events, does not give restrictive: The board voted to start the process for a moratorium: a vote to consider. No moratorium adopted is on the row. Until the editor confirms a word the row reads no published rating; the rubric proposes case by case.

  2843. · Douglas County · the rating of a scorecard row

    Before
    open
    After
    no published rating
    Why
    The scorecard rubric of September 29, 2026 (/methodology#rubric), read against the row's own published events, does not give open: The commissioners took up a $19.3 million tax rebate for Flexential; no event says they approved it. Approved, the incentive would read open. Until the editor confirms a word the row reads no published rating; the rubric proposes case by case.

  2844. · Rochester · the rating of a scorecard row

    Before
    closed
    After
    no published rating
    Why
    The scorecard rubric of September 29, 2026 (/methodology#rubric), read against the row's own published events, does not give closed: The ordinance allows data centers only in the recycling industrial district, with a conditional use permit: it narrows where, which reads restrictive, not a ban. Until the editor confirms a word the row reads no published rating; the rubric proposes restrictive.

  2845. · Port Washington · the rating of a scorecard row

    Before
    case by case
    After
    no published rating
    Why
    The scorecard rubric of September 29, 2026 (/methodology#rubric), read against the row's own published events, does not give case by case: The rules limiting exterior construction to 6 a.m. to 8 p.m. add conditions on how the Vantage campus is built. Until the editor confirms a word the row reads no published rating; the rubric proposes restrictive.

  2846. · Gibraltar · the rating of a scorecard row

    Before
    closed
    After
    no published rating
    Why
    The scorecard rubric of September 29, 2026 (/methodology#rubric), read against the row's own published events, does not give closed: A one year moratorium: a moratorium with an end date reads restrictive, not closed. Until the editor confirms a word the row reads no published rating; the rubric proposes restrictive.

  2847. · Utah · the rating of a scorecard row

    Before
    case by case
    After
    no published rating
    Why
    The scorecard rubric of September 29, 2026 (/methodology#rubric), read against the row's own published events, does not give case by case: H.B. 76 requires water use reporting, and the governor's order sets guardrails: conditions. Until the editor confirms a word the row reads no published rating; the rubric proposes restrictive.

  2848. · Virginia · the rating of a scorecard row

    Before
    case by case
    After
    no published rating
    Why
    The scorecard rubric of September 29, 2026 (/methodology#rubric), read against the row's own published events, does not give case by case: Executive Order 22, the General Assembly's generator rules and energy tax, and the commission's rate class add conditions. Until the editor confirms a word the row reads no published rating; the rubric proposes restrictive.

  2849. · Eagle Mountain · the rating of a scorecard row

    Before
    restrictive
    After
    no published rating
    Why
    The scorecard rubric of September 29, 2026 (/methodology#rubric), read against the row's own published events, does not give restrictive: The row's one act is the incentives Meta and Google received, which reads open; the sentence does not say which body gave them, and nothing on the row restricts data centers. Until the editor confirms a word the row reads no published rating; the rubric proposes open.

  2850. · Alberta · the rating of a scorecard row

    Before
    open
    After
    no published rating
    Why
    The scorecard rubric of September 29, 2026 (/methodology#rubric), read against the row's own published events, does not give open: The system operator's interim limit of 1,200 megawatts on new large loads, and the grid cap that tells data centres to build their own power, add conditions; the Utilities Commission's hearings and denials read case by case. Until the editor confirms a word the row reads no published rating; the rubric proposes restrictive.

  2851. · Maricopa County · the rating of a scorecard row

    Before
    case by case
    After
    no published rating
    Why
    The scorecard rubric of September 29, 2026 (/methodology#rubric), read against the row's own published events, does not give case by case: The modernized ordinance restricts data centers to industrial areas: an ordinance adding conditions. Until the editor confirms a word the row reads no published rating; the rubric proposes restrictive.

  2852. · Alabama · the rating of a scorecard row

    Before
    open
    After
    no published rating
    Why
    The scorecard rubric of September 29, 2026 (/methodology#rubric), read against the row's own published events, does not give open: The Power to the People Act makes a large data center contract recover its full cost: a law adding conditions. The commission's solar approvals for Meta read open, and the stronger word sets the row. Until the editor confirms a word the row reads no published rating; the rubric proposes restrictive.

  2853. · Georgia · the rating of a scorecard row

    Before
    open
    After
    no published rating
    Why
    The scorecard rubric of September 29, 2026 (/methodology#rubric), read against the row's own published events, does not give open: The Public Service Commission's rules for customers of 100 megawatts or more add conditions; its approvals of Georgia Power's contract for OpenAI read open, and the stronger word sets the row. Until the editor confirms a word the row reads no published rating; the rubric proposes restrictive.

  2854. · Savannah · the rating of a scorecard row

    Before
    closed
    After
    no published rating
    Why
    The scorecard rubric of September 29, 2026 (/methodology#rubric), read against the row's own published events, does not give closed: A 155 day moratorium: a moratorium with an end date reads restrictive, not closed. Until the editor confirms a word the row reads no published rating; the rubric proposes restrictive.

  2855. · Wes Moore · the speaker's role of a statement

    Before
    Maryland
    After
    Governor, Maryland
    Why
    Speaker read again from the statement's source line, "Governor Wes Moore, Maryland": the title in front of the name (Governor) is the role, not part of the name.

  2856. · Wes Moore · the speaker of a statement

    Before
    Governor Wes Moore
    After
    Wes Moore
    Why
    Speaker read again from the statement's source line, "Governor Wes Moore, Maryland": the title in front of the name (Governor) is the role, not part of the name.

  2857. · Joey Andrews · the speaker's role of a statement

    Before
    D-St. Joseph
    After
    Representative, D-St. Joseph
    Why
    Speaker read again from the statement's source line, "Rep. Joey Andrews, D-St. Joseph": the title in front of the name (Representative) is the role, not part of the name.

  2858. · Joey Andrews · the speaker of a statement

    Before
    Rep. Joey Andrews
    After
    Joey Andrews
    Why
    Speaker read again from the statement's source line, "Rep. Joey Andrews, D-St. Joseph": the title in front of the name (Representative) is the role, not part of the name.

  2859. · Andres Cano · the speaker's role of a statement

    Before
    Pima County District 5
    After
    Supervisor, Pima County District 5
    Why
    Speaker read again from the statement's source line, "Supervisor Andres Cano, Pima County District 5": the title in front of the name (Supervisor) is the role, not part of the name.

  2860. · Andres Cano · the speaker of a statement

    Before
    Supervisor Andres Cano
    After
    Andres Cano
    Why
    Speaker read again from the statement's source line, "Supervisor Andres Cano, Pima County District 5": the title in front of the name (Supervisor) is the role, not part of the name.

  2861. · CyrusOne Aurora CHI1-CHI3 · the speaker's role of a statement

    Before
    After
    Governor
    Why
    Speaker read again from the statement's source line, "Governor JB Pritzker": the title in front of the name (Governor) is the role, not part of the name.

  2862. · CyrusOne Aurora CHI1-CHI3 · the speaker of a statement

    Before
    Governor JB Pritzker
    After
    JB Pritzker
    Why
    Speaker read again from the statement's source line, "Governor JB Pritzker": the title in front of the name (Governor) is the role, not part of the name.

  2863. · Abigail Spanberger · the speaker's role of a statement

    Before
    After
    Governor
    Why
    Speaker read again from the statement's source line, "Governor Abigail Spanberger": the title in front of the name (Governor) is the role, not part of the name.

  2864. · Abigail Spanberger · the speaker of a statement

    Before
    Governor Abigail Spanberger
    After
    Abigail Spanberger
    Why
    Speaker read again from the statement's source line, "Governor Abigail Spanberger": the title in front of the name (Governor) is the role, not part of the name.

  2865. · Andy Barr · the speaker's role of a statement

    Before
    Republican nominee for U.S. Senate from Kentucky
    After
    Representative, Republican nominee for U.S. Senate from Kentucky
    Why
    Speaker read again from the statement's source line, "Rep. Andy Barr, Republican nominee for U.S. Senate from Kentucky": the title in front of the name (Representative) is the role, not part of the name.

  2866. · Andy Barr · the speaker of a statement

    Before
    Rep. Andy Barr
    After
    Andy Barr
    Why
    Speaker read again from the statement's source line, "Rep. Andy Barr, Republican nominee for U.S. Senate from Kentucky": the title in front of the name (Representative) is the role, not part of the name.

  2867. · Andy Barr · the speaker's role of a statement

    Before
    Republican nominee for U.S. Senate from Kentucky
    After
    Representative, Republican nominee for U.S. Senate from Kentucky
    Why
    Speaker read again from the statement's source line, "Rep. Andy Barr, Republican nominee for U.S. Senate from Kentucky": the title in front of the name (Representative) is the role, not part of the name.

  2868. · Andy Barr · the speaker of a statement

    Before
    Rep. Andy Barr
    After
    Andy Barr
    Why
    Speaker read again from the statement's source line, "Rep. Andy Barr, Republican nominee for U.S. Senate from Kentucky": the title in front of the name (Representative) is the role, not part of the name.

  2869. · Ned Lamont · the speaker of a statement

    Before
    Gov. Ned Lamont
    After
    Ned Lamont
    Why
    Speaker read again from the statement's source line, "Gov. Ned Lamont, Connecticut governor": the title in front of the name (Governor) is the role, not part of the name.

  2870. · wilmington-data-center-oh · the speaker's role of a statement

    Before
    Ohio Supreme Court
    After
    Justice, Ohio Supreme Court
    Why
    Speaker read again from the statement's source line, "Justice Jennifer Brunner, Ohio Supreme Court": the title in front of the name (Justice) is the role, not part of the name.

  2871. · wilmington-data-center-oh · the speaker of a statement

    Before
    Justice Jennifer Brunner
    After
    Jennifer Brunner
    Why
    Speaker read again from the statement's source line, "Justice Jennifer Brunner, Ohio Supreme Court": the title in front of the name (Justice) is the role, not part of the name.

  2872. · wilmington-data-center-oh · the speaker's role of a statement

    Before
    Ohio Supreme Court
    After
    Justice, Ohio Supreme Court
    Why
    Speaker read again from the statement's source line, "Justice Patrick Fischer, Ohio Supreme Court": the title in front of the name (Justice) is the role, not part of the name.

  2873. · wilmington-data-center-oh · the speaker of a statement

    Before
    Justice Patrick Fischer
    After
    Patrick Fischer
    Why
    Speaker read again from the statement's source line, "Justice Patrick Fischer, Ohio Supreme Court": the title in front of the name (Justice) is the role, not part of the name.

  2874. · Kathy Castor · the speaker of a statement

    Before
    Rep. Kathy Castor
    After
    Kathy Castor
    Why
    Speaker read again from the statement's source line, "Rep. Kathy Castor, U.S. Representative (D-FL)": the title in front of the name (Representative) is the role, not part of the name.

  2875. · Gabe Evans · the speaker of a statement

    Before
    Rep. Gabe Evans
    After
    Gabe Evans
    Why
    Speaker read again from the statement's source line, "Rep. Gabe Evans, U.S. Representative (R-CO)": the title in front of the name (Representative) is the role, not part of the name.

  2876. · Tim Kaine · the speaker's role of a statement

    Before
    D-Virginia
    After
    U.S. Senator, D-Virginia
    Why
    Speaker read again from the statement's source line, "U.S. Senator Tim Kaine, D-Virginia": the title in front of the name (U.S. Senator) is the role, not part of the name.

  2877. · Tim Kaine · the speaker of a statement

    Before
    U.S. Senator Tim Kaine
    After
    Tim Kaine
    Why
    Speaker read again from the statement's source line, "U.S. Senator Tim Kaine, D-Virginia": the title in front of the name (U.S. Senator) is the role, not part of the name.

  2878. · Colin Wellenkamp · the speaker's role of a statement

    Before
    R-St. Charles
    After
    State Representative, R-St. Charles
    Why
    Speaker read again from the statement's source line, "State Rep. Colin Wellenkamp, R-St. Charles": the title in front of the name (State Representative) is the role, not part of the name.

  2879. · Colin Wellenkamp · the speaker of a statement

    Before
    State Rep. Colin Wellenkamp
    After
    Colin Wellenkamp
    Why
    Speaker read again from the statement's source line, "State Rep. Colin Wellenkamp, R-St. Charles": the title in front of the name (State Representative) is the role, not part of the name.

  2880. · Westover Proposed Data Center · the speaker's role of a statement

    Before
    Westover
    After
    Council member, Westover
    Why
    Speaker read again from the statement's source line, "Council member Michael Shirley, Westover": the title in front of the name (Council member) is the role, not part of the name.

  2881. · Westover Proposed Data Center · the speaker of a statement

    Before
    Council member Michael Shirley
    After
    Michael Shirley
    Why
    Speaker read again from the statement's source line, "Council member Michael Shirley, Westover": the title in front of the name (Council member) is the role, not part of the name.

  2882. · a statement · the speaker's role of a statement

    Before
    Florida Democrat
    After
    Representative, Florida Democrat
    Why
    Speaker read again from the statement's source line, "Rep. Kathy Castor, Florida Democrat": the title in front of the name (Representative) is the role, not part of the name.

  2883. · Kathy Castor · the speaker of a statement

    Before
    Rep. Kathy Castor
    After
    Kathy Castor
    Why
    Speaker read again from the statement's source line, "Rep. Kathy Castor, Florida Democrat": the title in front of the name (Representative) is the role, not part of the name.

  2884. · Gabe Evans · the speaker's role of a statement

    Before
    Colorado Republican
    After
    Representative, Colorado Republican
    Why
    Speaker read again from the statement's source line, "Rep. Gabe Evans, Colorado Republican": the title in front of the name (Representative) is the role, not part of the name.

  2885. · Gabe Evans · the speaker of a statement

    Before
    Rep. Gabe Evans
    After
    Gabe Evans
    Why
    Speaker read again from the statement's source line, "Rep. Gabe Evans, Colorado Republican": the title in front of the name (Representative) is the role, not part of the name.

  2886. · Lee P. Rudofsky · the speaker's role of a statement

    Before
    After
    Judge
    Why
    Speaker read again from the statement's source line, "Judge Lee P. Rudofsky": the title in front of the name (Judge) is the role, not part of the name.

  2887. · Lee P. Rudofsky · the speaker of a statement

    Before
    Judge Lee P. Rudofsky
    After
    Lee P. Rudofsky
    Why
    Speaker read again from the statement's source line, "Judge Lee P. Rudofsky": the title in front of the name (Judge) is the role, not part of the name.

  2888. · Mike Kehoe · the speaker's role of a statement

    Before
    After
    Governor
    Why
    Speaker read again from the statement's source line, "Gov. Mike Kehoe": the title in front of the name (Governor) is the role, not part of the name.

  2889. · Mike Kehoe · the speaker of a statement

    Before
    Gov. Mike Kehoe
    After
    Mike Kehoe
    Why
    Speaker read again from the statement's source line, "Gov. Mike Kehoe": the title in front of the name (Governor) is the role, not part of the name.

  2890. · U-M / Los Alamos Data Center (Van Buren Township) · the speaker's role of a statement

    Before
    After
    U.S. Representative
    Why
    Speaker read again from the statement's source line, "U.S. Rep. Debbie Dingell": the title in front of the name (U.S. Representative) is the role, not part of the name.

  2891. · U-M / Los Alamos Data Center (Van Buren Township) · the speaker of a statement

    Before
    U.S. Rep. Debbie Dingell
    After
    Debbie Dingell
    Why
    Speaker read again from the statement's source line, "U.S. Rep. Debbie Dingell": the title in front of the name (U.S. Representative) is the role, not part of the name.

  2892. · U-M / Los Alamos Data Center (Van Buren Township) · the speaker's role of a statement

    Before
    After
    U.S. Representative
    Why
    Speaker read again from the statement's source line, "U.S. Rep. Debbie Dingell": the title in front of the name (U.S. Representative) is the role, not part of the name.

  2893. · U-M / Los Alamos Data Center (Van Buren Township) · the speaker of a statement

    Before
    U.S. Rep. Debbie Dingell
    After
    Debbie Dingell
    Why
    Speaker read again from the statement's source line, "U.S. Rep. Debbie Dingell": the title in front of the name (U.S. Representative) is the role, not part of the name.

  2894. · U-M / Los Alamos Data Center (Van Buren Township) · the speaker's role of a statement

    Before
    After
    U.S. Representative
    Why
    Speaker read again from the statement's source line, "U.S. Rep. Debbie Dingell": the title in front of the name (U.S. Representative) is the role, not part of the name.

  2895. · U-M / Los Alamos Data Center (Van Buren Township) · the speaker of a statement

    Before
    U.S. Rep. Debbie Dingell
    After
    Debbie Dingell
    Why
    Speaker read again from the statement's source line, "U.S. Rep. Debbie Dingell": the title in front of the name (U.S. Representative) is the role, not part of the name.

  2896. · Suhas Subramanyam · the speaker of a statement

    Before
    Rep. Suhas Subramanyam
    After
    Suhas Subramanyam
    Why
    Speaker read again from the statement's source line, "Rep. Suhas Subramanyam, U.S. Representative": the title in front of the name (Representative) is the role, not part of the name.

  2897. · Natalie Murdock · the speaker's role of a statement

    Before
    Chatham counties)
    After
    State Senator (D-Durham, Chatham counties)
    Why
    Speaker read again from the statement's source line, "State Sen. Natalie Murdock (D-Durham, Chatham counties)": the title in front of the name (State Senator) is the role, not part of the name.

  2898. · Natalie Murdock · the speaker of a statement

    Before
    State Sen. Natalie Murdock (D-Durham
    After
    Natalie Murdock
    Why
    Speaker read again from the statement's source line, "State Sen. Natalie Murdock (D-Durham, Chatham counties)": the title in front of the name (State Senator) is the role, not part of the name.

  2899. · Anderson Clayton · the speaker's role of a statement

    Before
    After
    North Carolina Democratic Party Chair
    Why
    Speaker read again from the statement's source line, "North Carolina Democratic Party Chair Anderson Clayton": the title in front of the name (North Carolina Democratic Party Chair) is the role, not part of the name.

  2900. · Anderson Clayton · the speaker of a statement

    Before
    North Carolina Democratic Party Chair Anderson Clayton
    After
    Anderson Clayton
    Why
    Speaker read again from the statement's source line, "North Carolina Democratic Party Chair Anderson Clayton": the title in front of the name (North Carolina Democratic Party Chair) is the role, not part of the name.

  2901. · Anderson Clayton · the speaker's role of a statement

    Before
    After
    North Carolina Democratic Party Chair
    Why
    Speaker read again from the statement's source line, "North Carolina Democratic Party Chair Anderson Clayton": the title in front of the name (North Carolina Democratic Party Chair) is the role, not part of the name.

  2902. · Anderson Clayton · the speaker of a statement

    Before
    North Carolina Democratic Party Chair Anderson Clayton
    After
    Anderson Clayton
    Why
    Speaker read again from the statement's source line, "North Carolina Democratic Party Chair Anderson Clayton": the title in front of the name (North Carolina Democratic Party Chair) is the role, not part of the name.

  2903. · Bruce Westerman · the speaker's role of a statement

    Before
    R-Arkansas
    After
    U.S. Representative, R-Arkansas
    Why
    Speaker read again from the statement's source line, "U.S. Rep. Bruce Westerman, R-Arkansas": the title in front of the name (U.S. Representative) is the role, not part of the name.

  2904. · Bruce Westerman · the speaker of a statement

    Before
    U.S. Rep. Bruce Westerman
    After
    Bruce Westerman
    Why
    Speaker read again from the statement's source line, "U.S. Rep. Bruce Westerman, R-Arkansas": the title in front of the name (U.S. Representative) is the role, not part of the name.

  2905. · Jim Justice · the speaker's role of a statement

    Before
    R-W.Va.
    After
    Senator, R-W.Va.
    Why
    Speaker read again from the statement's source line, "Sen. Jim Justice, R-W.Va.": the title in front of the name (Senator) is the role, not part of the name.

  2906. · Jim Justice · the speaker of a statement

    Before
    Sen. Jim Justice
    After
    Jim Justice
    Why
    Speaker read again from the statement's source line, "Sen. Jim Justice, R-W.Va.": the title in front of the name (Senator) is the role, not part of the name.

  2907. · Eddie Treviño Jr. · the speaker's role of a statement

    Before
    Jr., Cameron County Judge
    After
    Cameron County Judge
    Why
    Speaker read again from the statement's source line, "Eddie Treviño, Jr., Cameron County Judge": the comma set off the name's own suffix, not the role.

  2908. · Eddie Treviño Jr. · the speaker of a statement

    Before
    Eddie Treviño
    After
    Eddie Treviño Jr.
    Why
    Speaker read again from the statement's source line, "Eddie Treviño, Jr., Cameron County Judge": the comma set off the name's own suffix, not the role.

  2909. · Jennifer Kuhn · the speaker's role of a statement

    Before
    After
    Jackson Mayor
    Why
    Speaker read again from the statement's source line, "Jackson Mayor Jennifer Kuhn": the title in front of the name (Jackson Mayor) is the role, not part of the name.

  2910. · Jennifer Kuhn · the speaker of a statement

    Before
    Jackson Mayor Jennifer Kuhn
    After
    Jennifer Kuhn
    Why
    Speaker read again from the statement's source line, "Jackson Mayor Jennifer Kuhn": the title in front of the name (Jackson Mayor) is the role, not part of the name.

  2911. · Greg Abbott · the speaker of a statement

    Before
    Gov. Greg Abbott
    After
    Greg Abbott
    Why
    Speaker read again from the statement's source line, "Gov. Greg Abbott, Texas Governor": the title in front of the name (Governor) is the role, not part of the name.

  2912. · Suhas Subramanyam · the speaker's role of a statement

    Before
    After
    U.S. Representative
    Why
    Speaker read again from the statement's source line, "U.S. Rep. Suhas Subramanyam": the title in front of the name (U.S. Representative) is the role, not part of the name.

  2913. · Suhas Subramanyam · the speaker of a statement

    Before
    U.S. Rep. Suhas Subramanyam
    After
    Suhas Subramanyam
    Why
    Speaker read again from the statement's source line, "U.S. Rep. Suhas Subramanyam": the title in front of the name (U.S. Representative) is the role, not part of the name.

  2914. · Patrick Morrisey · the speaker's role of a statement

    Before
    After
    Governor
    Why
    Speaker read again from the statement's source line, "Gov. Patrick Morrisey": the title in front of the name (Governor) is the role, not part of the name.

  2915. · Patrick Morrisey · the speaker of a statement

    Before
    Gov. Patrick Morrisey
    After
    Patrick Morrisey
    Why
    Speaker read again from the statement's source line, "Gov. Patrick Morrisey": the title in front of the name (Governor) is the role, not part of the name.

  2916. · Raphael Warnock · the speaker's role of a statement

    Before
    Georgia
    After
    Senator, Georgia
    Why
    Speaker read again from the statement's source line, "Senator Raphael Warnock, Georgia": the title in front of the name (Senator) is the role, not part of the name.

  2917. · Raphael Warnock · the speaker of a statement

    Before
    Senator Raphael Warnock
    After
    Raphael Warnock
    Why
    Speaker read again from the statement's source line, "Senator Raphael Warnock, Georgia": the title in front of the name (Senator) is the role, not part of the name.

  2918. · Kelly Ayotte · the speaker's role of a statement

    Before
    After
    Governor
    Why
    Speaker read again from the statement's source line, "Gov. Kelly Ayotte": the title in front of the name (Governor) is the role, not part of the name.

  2919. · Kelly Ayotte · the speaker of a statement

    Before
    Gov. Kelly Ayotte
    After
    Kelly Ayotte
    Why
    Speaker read again from the statement's source line, "Gov. Kelly Ayotte": the title in front of the name (Governor) is the role, not part of the name.

  2920. · Suhas Subramanyam · the speaker's role of a statement

    Before
    After
    Representative
    Why
    Speaker read again from the statement's source line, "Rep. Suhas Subramanyam": the title in front of the name (Representative) is the role, not part of the name.

  2921. · Suhas Subramanyam · the speaker of a statement

    Before
    Rep. Suhas Subramanyam
    After
    Suhas Subramanyam
    Why
    Speaker read again from the statement's source line, "Rep. Suhas Subramanyam": the title in front of the name (Representative) is the role, not part of the name.

  2922. · Suhas Subramanyam · the speaker's role of a statement

    Before
    After
    Representative
    Why
    Speaker read again from the statement's source line, "Rep. Suhas Subramanyam": the title in front of the name (Representative) is the role, not part of the name.

  2923. · Suhas Subramanyam · the speaker of a statement

    Before
    Rep. Suhas Subramanyam
    After
    Suhas Subramanyam
    Why
    Speaker read again from the statement's source line, "Rep. Suhas Subramanyam": the title in front of the name (Representative) is the role, not part of the name.

  2924. · Suhas Subramanyam · the speaker's role of a statement

    Before
    After
    Representative
    Why
    Speaker read again from the statement's source line, "Rep. Suhas Subramanyam": the title in front of the name (Representative) is the role, not part of the name.

  2925. · Suhas Subramanyam · the speaker of a statement

    Before
    Rep. Suhas Subramanyam
    After
    Suhas Subramanyam
    Why
    Speaker read again from the statement's source line, "Rep. Suhas Subramanyam": the title in front of the name (Representative) is the role, not part of the name.

  2926. · Tom Barrett · the speaker's role of a statement

    Before
    After
    Representative
    Why
    Speaker read again from the statement's source line, "Rep. Tom Barrett": the title in front of the name (Representative) is the role, not part of the name.

  2927. · Tom Barrett · the speaker of a statement

    Before
    Rep. Tom Barrett
    After
    Tom Barrett
    Why
    Speaker read again from the statement's source line, "Rep. Tom Barrett": the title in front of the name (Representative) is the role, not part of the name.

  2928. · Tom Barrett · the speaker's role of a statement

    Before
    After
    Representative
    Why
    Speaker read again from the statement's source line, "Rep. Tom Barrett": the title in front of the name (Representative) is the role, not part of the name.

  2929. · Tom Barrett · the speaker of a statement

    Before
    Rep. Tom Barrett
    After
    Tom Barrett
    Why
    Speaker read again from the statement's source line, "Rep. Tom Barrett": the title in front of the name (Representative) is the role, not part of the name.

  2930. · Josh Shapiro · the speaker's role of a statement

    Before
    After
    Governor
    Why
    Speaker read again from the statement's source line, "Governor Josh Shapiro": the title in front of the name (Governor) is the role, not part of the name.

  2931. · Josh Shapiro · the speaker of a statement

    Before
    Governor Josh Shapiro
    After
    Josh Shapiro
    Why
    Speaker read again from the statement's source line, "Governor Josh Shapiro": the title in front of the name (Governor) is the role, not part of the name.

  2932. · Bill Lee · the speaker of a statement

    Before
    Gov. Bill Lee
    After
    Bill Lee
    Why
    Speaker read again from the statement's source line, "Gov. Bill Lee, Tennessee Governor": the title in front of the name (Governor) is the role, not part of the name.

  2933. · ppl-archbald-data-center-power-plants-pa · the speaker's role of a statement

    Before
    Pennsylvania
    After
    Governor, Pennsylvania
    Why
    Speaker read again from the statement's source line, "Governor Josh Shapiro, Pennsylvania": the title in front of the name (Governor) is the role, not part of the name.

  2934. · ppl-archbald-data-center-power-plants-pa · the speaker of a statement

    Before
    Governor Josh Shapiro
    After
    Josh Shapiro
    Why
    Speaker read again from the statement's source line, "Governor Josh Shapiro, Pennsylvania": the title in front of the name (Governor) is the role, not part of the name.

  2935. · Mike Johnston · the speaker's role of a statement

    Before
    Denver
    After
    Mayor, Denver
    Why
    Speaker read again from the statement's source line, "Mayor Mike Johnston, Denver": the title in front of the name (Mayor) is the role, not part of the name.

  2936. · Mike Johnston · the speaker of a statement

    Before
    Mayor Mike Johnston
    After
    Mike Johnston
    Why
    Speaker read again from the statement's source line, "Mayor Mike Johnston, Denver": the title in front of the name (Mayor) is the role, not part of the name.

  2937. · Mike Thompson · the speaker's role of a statement

    Before
    After
    Representative
    Why
    Speaker read again from the statement's source line, "Rep. Mike Thompson": the title in front of the name (Representative) is the role, not part of the name.

  2938. · Mike Thompson · the speaker of a statement

    Before
    Rep. Mike Thompson
    After
    Mike Thompson
    Why
    Speaker read again from the statement's source line, "Rep. Mike Thompson": the title in front of the name (Representative) is the role, not part of the name.

  2939. · Mike Thompson · the speaker's role of a statement

    Before
    After
    Representative
    Why
    Speaker read again from the statement's source line, "Rep. Mike Thompson": the title in front of the name (Representative) is the role, not part of the name.

  2940. · Mike Thompson · the speaker of a statement

    Before
    Rep. Mike Thompson
    After
    Mike Thompson
    Why
    Speaker read again from the statement's source line, "Rep. Mike Thompson": the title in front of the name (Representative) is the role, not part of the name.

  2941. · Mike Thompson · the speaker's role of a statement

    Before
    After
    Representative
    Why
    Speaker read again from the statement's source line, "Rep. Mike Thompson": the title in front of the name (Representative) is the role, not part of the name.

  2942. · Mike Thompson · the speaker of a statement

    Before
    Rep. Mike Thompson
    After
    Mike Thompson
    Why
    Speaker read again from the statement's source line, "Rep. Mike Thompson": the title in front of the name (Representative) is the role, not part of the name.

  2943. · Mike Thompson · the speaker's role of a statement

    Before
    After
    Representative
    Why
    Speaker read again from the statement's source line, "Rep. Mike Thompson": the title in front of the name (Representative) is the role, not part of the name.

  2944. · Mike Thompson · the speaker of a statement

    Before
    Rep. Mike Thompson
    After
    Mike Thompson
    Why
    Speaker read again from the statement's source line, "Rep. Mike Thompson": the title in front of the name (Representative) is the role, not part of the name.

  2945. · Ned Lamont · the speaker's role of a statement

    Before
    After
    Governor
    Why
    Speaker read again from the statement's source line, "Governor Ned Lamont": the title in front of the name (Governor) is the role, not part of the name.

  2946. · Ned Lamont · the speaker of a statement

    Before
    Governor Ned Lamont
    After
    Ned Lamont
    Why
    Speaker read again from the statement's source line, "Governor Ned Lamont": the title in front of the name (Governor) is the role, not part of the name.

  2947. · Ned Lamont · the speaker's role of a statement

    Before
    After
    Governor
    Why
    Speaker read again from the statement's source line, "Governor Ned Lamont": the title in front of the name (Governor) is the role, not part of the name.

  2948. · Ned Lamont · the speaker of a statement

    Before
    Governor Ned Lamont
    After
    Ned Lamont
    Why
    Speaker read again from the statement's source line, "Governor Ned Lamont": the title in front of the name (Governor) is the role, not part of the name.

  2949. · Ned Lamont · the speaker's role of a statement

    Before
    After
    Governor
    Why
    Speaker read again from the statement's source line, "Governor Ned Lamont": the title in front of the name (Governor) is the role, not part of the name.

  2950. · Ned Lamont · the speaker of a statement

    Before
    Governor Ned Lamont
    After
    Ned Lamont
    Why
    Speaker read again from the statement's source line, "Governor Ned Lamont": the title in front of the name (Governor) is the role, not part of the name.

  2951. · Ned Lamont · the speaker's role of a statement

    Before
    After
    Governor
    Why
    Speaker read again from the statement's source line, "Governor Ned Lamont": the title in front of the name (Governor) is the role, not part of the name.

  2952. · Ned Lamont · the speaker of a statement

    Before
    Governor Ned Lamont
    After
    Ned Lamont
    Why
    Speaker read again from the statement's source line, "Governor Ned Lamont": the title in front of the name (Governor) is the role, not part of the name.

  2953. · Google Mesa data center · the speaker of a statement

    Before
    Governor Katie Hobbs
    After
    Katie Hobbs
    Why
    Speaker read again from the statement's source line, "Governor Katie Hobbs, Arizona Governor": the title in front of the name (Governor) is the role, not part of the name.

  2954. · EdgeCore Mesa North Campus · the speaker's role of a statement

    Before
    After
    Governor
    Why
    Speaker read again from the statement's source line, "Governor Katie Hobbs": the title in front of the name (Governor) is the role, not part of the name.

  2955. · EdgeCore Mesa North Campus · the speaker of a statement

    Before
    Governor Katie Hobbs
    After
    Katie Hobbs
    Why
    Speaker read again from the statement's source line, "Governor Katie Hobbs": the title in front of the name (Governor) is the role, not part of the name.

  2956. · Doug Fiefia · the speaker's role of a statement

    Before
    After
    Utah Representative
    Why
    Speaker read again from the statement's source line, "Utah Rep. Doug Fiefia": the title in front of the name (Utah Representative) is the role, not part of the name.

  2957. · Doug Fiefia · the speaker of a statement

    Before
    Utah Rep. Doug Fiefia
    After
    Doug Fiefia
    Why
    Speaker read again from the statement's source line, "Utah Rep. Doug Fiefia": the title in front of the name (Utah Representative) is the role, not part of the name.

  2958. · Donald Trump · the speaker's role of a statement

    Before
    After
    President
    Why
    Speaker read again from the statement's source line, "President Donald Trump": the title in front of the name (President) is the role, not part of the name.

  2959. · Donald Trump · the speaker of a statement

    Before
    President Donald Trump
    After
    Donald Trump
    Why
    Speaker read again from the statement's source line, "President Donald Trump": the title in front of the name (President) is the role, not part of the name.

  2960. · Greg Abbott · the speaker's role of a statement

    Before
    After
    Governor
    Why
    Speaker read again from the statement's source line, "Gov. Greg Abbott": the title in front of the name (Governor) is the role, not part of the name.

  2961. · Greg Abbott · the speaker of a statement

    Before
    Gov. Greg Abbott
    After
    Greg Abbott
    Why
    Speaker read again from the statement's source line, "Gov. Greg Abbott": the title in front of the name (Governor) is the role, not part of the name.

  2962. · Greg Abbott · the speaker's role of a statement

    Before
    After
    Governor
    Why
    Speaker read again from the statement's source line, "Gov. Greg Abbott": the title in front of the name (Governor) is the role, not part of the name.

  2963. · Greg Abbott · the speaker of a statement

    Before
    Gov. Greg Abbott
    After
    Greg Abbott
    Why
    Speaker read again from the statement's source line, "Gov. Greg Abbott": the title in front of the name (Governor) is the role, not part of the name.

  2964. · Donald Trump · the speaker's role of a statement

    Before
    After
    President
    Why
    Speaker read again from the statement's source line, "President Donald Trump": the title in front of the name (President) is the role, not part of the name.

  2965. · Donald Trump · the speaker of a statement

    Before
    President Donald Trump
    After
    Donald Trump
    Why
    Speaker read again from the statement's source line, "President Donald Trump": the title in front of the name (President) is the role, not part of the name.

  2966. · Austin Foss · the speaker's role of a statement

    Before
    D-Foss
    After
    Representative, D-Foss
    Why
    Speaker read again from the statement's source line, "Rep. Austin Foss, D-Foss": the title in front of the name (Representative) is the role, not part of the name.

  2967. · Austin Foss · the speaker of a statement

    Before
    Rep. Austin Foss
    After
    Austin Foss
    Why
    Speaker read again from the statement's source line, "Rep. Austin Foss, D-Foss": the title in front of the name (Representative) is the role, not part of the name.

  2968. · Todd Porter · the speaker's role of a statement

    Before
    R-Mandan
    After
    Representative, R-Mandan
    Why
    Speaker read again from the statement's source line, "Rep. Todd Porter, R-Mandan": the title in front of the name (Representative) is the role, not part of the name.

  2969. · Todd Porter · the speaker of a statement

    Before
    Rep. Todd Porter
    After
    Todd Porter
    Why
    Speaker read again from the statement's source line, "Rep. Todd Porter, R-Mandan": the title in front of the name (Representative) is the role, not part of the name.

  2970. · Jonathan Warrey · the speaker's role of a statement

    Before
    R-Casselton
    After
    Representative, R-Casselton
    Why
    Speaker read again from the statement's source line, "Rep. Jonathan Warrey, R-Casselton": the title in front of the name (Representative) is the role, not part of the name.

  2971. · Jonathan Warrey · the speaker of a statement

    Before
    Rep. Jonathan Warrey
    After
    Jonathan Warrey
    Why
    Speaker read again from the statement's source line, "Rep. Jonathan Warrey, R-Casselton": the title in front of the name (Representative) is the role, not part of the name.

  2972. · Mike Rounds · the speaker's role of a statement

    Before
    After
    U.S. Senator
    Why
    Speaker read again from the statement's source line, "U.S. Sen. Mike Rounds": the title in front of the name (U.S. Senator) is the role, not part of the name.

  2973. · Mike Rounds · the speaker of a statement

    Before
    U.S. Sen. Mike Rounds
    After
    Mike Rounds
    Why
    Speaker read again from the statement's source line, "U.S. Sen. Mike Rounds": the title in front of the name (U.S. Senator) is the role, not part of the name.

  2974. · Alberta government (reported by Jack Farrell, The Canadian Press) · the speaker's role of a statement

    Before
    The Canadian Press)
    After
    Why
    Speaker read again from the statement's source line, "Alberta government (reported by Jack Farrell, The Canadian Press)": the comma inside the parenthesis is part of it, not the break between name and role.

  2975. · Alberta government (reported by Jack Farrell, The Canadian Press) · the speaker of a statement

    Before
    Alberta government (reported by Jack Farrell
    After
    Alberta government (reported by Jack Farrell, The Canadian Press)
    Why
    Speaker read again from the statement's source line, "Alberta government (reported by Jack Farrell, The Canadian Press)": the comma inside the parenthesis is part of it, not the break between name and role.

  2976. · Jill Koford · the speaker's role of a statement

    Before
    Republican from Ogden
    After
    Representative, Republican from Ogden
    Why
    Speaker read again from the statement's source line, "Rep. Jill Koford, Republican from Ogden": the title in front of the name (Representative) is the role, not part of the name.

  2977. · Jill Koford · the speaker of a statement

    Before
    Rep. Jill Koford
    After
    Jill Koford
    Why
    Speaker read again from the statement's source line, "Rep. Jill Koford, Republican from Ogden": the title in front of the name (Representative) is the role, not part of the name.

  2978. · Stratos Project · the speaker of a statement

    Before
    Governor Spencer Cox
    After
    Spencer Cox
    Why
    Speaker read again from the statement's source line, "Governor Spencer Cox, Utah Governor": the title in front of the name (Governor) is the role, not part of the name.

  2979. · Stratos Project · the speaker of a statement

    Before
    Governor Spencer Cox
    After
    Spencer Cox
    Why
    Speaker read again from the statement's source line, "Governor Spencer Cox, Utah Governor": the title in front of the name (Governor) is the role, not part of the name.

  2980. · Jim Dunnigan · the speaker's role of a statement

    Before
    R-Taylorsville
    After
    Representative, R-Taylorsville
    Why
    Speaker read again from the statement's source line, "Rep. Jim Dunnigan, R-Taylorsville": the title in front of the name (Representative) is the role, not part of the name.

  2981. · Jim Dunnigan · the speaker of a statement

    Before
    Rep. Jim Dunnigan
    After
    Jim Dunnigan
    Why
    Speaker read again from the statement's source line, "Rep. Jim Dunnigan, R-Taylorsville": the title in front of the name (Representative) is the role, not part of the name.

  2982. · Doug Fiefia · the speaker's role of a statement

    Before
    R-Herriman
    After
    Representative, R-Herriman
    Why
    Speaker read again from the statement's source line, "Rep. Doug Fiefia, R-Herriman": the title in front of the name (Representative) is the role, not part of the name.

  2983. · Doug Fiefia · the speaker of a statement

    Before
    Rep. Doug Fiefia
    After
    Doug Fiefia
    Why
    Speaker read again from the statement's source line, "Rep. Doug Fiefia, R-Herriman": the title in front of the name (Representative) is the role, not part of the name.

  2984. · Jon Hawkins · the speaker's role of a statement

    Before
    R-Pleasant Grove, chair of Economic Development and Workforce Services Interim Committee
    After
    Representative, R-Pleasant Grove, chair of Economic Development and Workforce Services Interim Committee
    Why
    Speaker read again from the statement's source line, "Rep. Jon Hawkins, R-Pleasant Grove, chair of Economic Development and Workforce Services Interim Committee": the title in front of the name (Representative) is the role, not part of the name.

  2985. · Jon Hawkins · the speaker of a statement

    Before
    Rep. Jon Hawkins
    After
    Jon Hawkins
    Why
    Speaker read again from the statement's source line, "Rep. Jon Hawkins, R-Pleasant Grove, chair of Economic Development and Workforce Services Interim Committee": the title in front of the name (Representative) is the role, not part of the name.

  2986. · Stratos Project · the speaker's role of a statement

    Before
    After
    House Speaker
    Why
    Speaker read again from the statement's source line, "House Speaker Mike Schultz": the title in front of the name (House Speaker) is the role, not part of the name.

  2987. · Stratos Project · the speaker of a statement

    Before
    House Speaker Mike Schultz
    After
    Mike Schultz
    Why
    Speaker read again from the statement's source line, "House Speaker Mike Schultz": the title in front of the name (House Speaker) is the role, not part of the name.

  2988. · Stratos Project · the speaker's role of a statement

    Before
    After
    Governor
    Why
    Speaker read again from the statement's source line, "Governor Spencer Cox": the title in front of the name (Governor) is the role, not part of the name.

  2989. · Stratos Project · the speaker of a statement

    Before
    Governor Spencer Cox
    After
    Spencer Cox
    Why
    Speaker read again from the statement's source line, "Governor Spencer Cox": the title in front of the name (Governor) is the role, not part of the name.

  2990. · Stratos Project · the speaker's role of a statement

    Before
    After
    Governor
    Why
    Speaker read again from the statement's source line, "Governor Spencer Cox": the title in front of the name (Governor) is the role, not part of the name.

  2991. · Stratos Project · the speaker of a statement

    Before
    Governor Spencer Cox
    After
    Spencer Cox
    Why
    Speaker read again from the statement's source line, "Governor Spencer Cox": the title in front of the name (Governor) is the role, not part of the name.

  2992. · Jill Koford · the speaker's role of a statement

    Before
    Utah House
    After
    State Representative, Utah House
    Why
    Speaker read again from the statement's source line, "State Rep. Jill Koford, Utah House": the title in front of the name (State Representative) is the role, not part of the name.

  2993. · Jill Koford · the speaker of a statement

    Before
    State Rep. Jill Koford
    After
    Jill Koford
    Why
    Speaker read again from the statement's source line, "State Rep. Jill Koford, Utah House": the title in front of the name (State Representative) is the role, not part of the name.

  2994. · Tina Kotek · the speaker's role of a statement

    Before
    After
    Governor
    Why
    Speaker read again from the statement's source line, "Gov. Tina Kotek": the title in front of the name (Governor) is the role, not part of the name.

  2995. · Tina Kotek · the speaker of a statement

    Before
    Gov. Tina Kotek
    After
    Tina Kotek
    Why
    Speaker read again from the statement's source line, "Gov. Tina Kotek": the title in front of the name (Governor) is the role, not part of the name.

  2996. · Tina Kotek · the speaker's role of a statement

    Before
    After
    Governor
    Why
    Speaker read again from the statement's source line, "Gov. Tina Kotek": the title in front of the name (Governor) is the role, not part of the name.

  2997. · Tina Kotek · the speaker of a statement

    Before
    Gov. Tina Kotek
    After
    Tina Kotek
    Why
    Speaker read again from the statement's source line, "Gov. Tina Kotek": the title in front of the name (Governor) is the role, not part of the name.

  2998. · Tina Kotek · the speaker's role of a statement

    Before
    After
    Governor
    Why
    Speaker read again from the statement's source line, "Gov. Tina Kotek": the title in front of the name (Governor) is the role, not part of the name.

  2999. · Tina Kotek · the speaker of a statement

    Before
    Gov. Tina Kotek
    After
    Tina Kotek
    Why
    Speaker read again from the statement's source line, "Gov. Tina Kotek": the title in front of the name (Governor) is the role, not part of the name.

  3000. · Meta Louisiana data center · the speaker's role of a statement

    Before
    After
    Governor
    Why
    Speaker read again from the statement's source line, "Gov. Jeff Landry": the title in front of the name (Governor) is the role, not part of the name.

  3001. · Meta Louisiana data center · the speaker of a statement

    Before
    Gov. Jeff Landry
    After
    Jeff Landry
    Why
    Speaker read again from the statement's source line, "Gov. Jeff Landry": the title in front of the name (Governor) is the role, not part of the name.

  3002. · Meta Louisiana data center · the speaker's role of a statement

    Before
    After
    Governor
    Why
    Speaker read again from the statement's source line, "Gov. Jeff Landry": the title in front of the name (Governor) is the role, not part of the name.

  3003. · Meta Louisiana data center · the speaker of a statement

    Before
    Gov. Jeff Landry
    After
    Jeff Landry
    Why
    Speaker read again from the statement's source line, "Gov. Jeff Landry": the title in front of the name (Governor) is the role, not part of the name.

  3004. · Google West Memphis Data Center · the speaker's role of a statement

    Before
    After
    Judge
    Why
    Speaker read again from the statement's source line, "Judge Lee Rudofsky": the title in front of the name (Judge) is the role, not part of the name.

  3005. · Google West Memphis Data Center · the speaker of a statement

    Before
    Judge Lee Rudofsky
    After
    Lee Rudofsky
    Why
    Speaker read again from the statement's source line, "Judge Lee Rudofsky": the title in front of the name (Judge) is the role, not part of the name.

  3006. · Google Salix Data Center · the speaker's role of a statement

    Before
    Salix
    After
    Mayor, Salix
    Why
    Speaker read again from the statement's source line, "Mayor Kevin Nelson, Salix": the title in front of the name (Mayor) is the role, not part of the name.

  3007. · Google Salix Data Center · the speaker of a statement

    Before
    Mayor Kevin Nelson
    After
    Kevin Nelson
    Why
    Speaker read again from the statement's source line, "Mayor Kevin Nelson, Salix": the title in front of the name (Mayor) is the role, not part of the name.

  3008. · Google West Memphis Data Center · the speaker's role of a statement

    Before
    news anchor)
    After
    Why
    Speaker read again from the statement's source line, "Entergy (via Beth Hunt, news anchor)": the comma inside the parenthesis is part of it, not the break between name and role.

  3009. · Google West Memphis Data Center · the speaker of a statement

    Before
    Entergy (via Beth Hunt
    After
    Entergy (via Beth Hunt, news anchor)
    Why
    Speaker read again from the statement's source line, "Entergy (via Beth Hunt, news anchor)": the comma inside the parenthesis is part of it, not the break between name and role.

  3010. · Google West Memphis Data Center · the speaker of a statement

    Before
    Mayor Marco McClendon
    After
    Marco McClendon
    Why
    Speaker read again from the statement's source line, "Mayor Marco McClendon, Mayor of West Memphis": the title in front of the name (Mayor) is the role, not part of the name.

  3011. · Google West Memphis Data Center · the speaker of a statement

    Before
    Governor Sarah Sanders
    After
    Sarah Sanders
    Why
    Speaker read again from the statement's source line, "Governor Sarah Sanders, Governor of Arkansas": the title in front of the name (Governor) is the role, not part of the name.

  3012. · Google West Memphis Data Center · the speaker of a statement

    Before
    Gov. Sarah Huckabee Sanders
    After
    Sarah Huckabee Sanders
    Why
    Speaker read again from the statement's source line, "Gov. Sarah Huckabee Sanders, Governor of Arkansas": the title in front of the name (Governor) is the role, not part of the name.

  3013. · Vantage Port Washington Data Center · the speaker's role of a statement

    Before
    Responsible Energy Alliance
    After
    Pastor, Responsible Energy Alliance
    Why
    Speaker read again from the statement's source line, "Pastor Patti Plough, Responsible Energy Alliance": the title in front of the name (Pastor) is the role, not part of the name.

  3014. · Vantage Port Washington Data Center · the speaker of a statement

    Before
    Pastor Patti Plough
    After
    Patti Plough
    Why
    Speaker read again from the statement's source line, "Pastor Patti Plough, Responsible Energy Alliance": the title in front of the name (Pastor) is the role, not part of the name.

  3015. · Vantage Port Washington Data Center · the speaker's role of a statement

    Before
    After
    Mayor
    Why
    Speaker read again from the statement's source line, "Mayor Ted Neitzke": the title in front of the name (Mayor) is the role, not part of the name.

  3016. · Vantage Port Washington Data Center · the speaker of a statement

    Before
    Mayor Ted Neitzke
    After
    Ted Neitzke
    Why
    Speaker read again from the statement's source line, "Mayor Ted Neitzke": the title in front of the name (Mayor) is the role, not part of the name.

  3017. · Vantage Port Washington Data Center · the speaker's role of a statement

    Before
    After
    Sheriff
    Why
    Speaker read again from the statement's source line, "Sheriff Christy Knowles": the title in front of the name (Sheriff) is the role, not part of the name.

  3018. · Vantage Port Washington Data Center · the speaker of a statement

    Before
    Sheriff Christy Knowles
    After
    Christy Knowles
    Why
    Speaker read again from the statement's source line, "Sheriff Christy Knowles": the title in front of the name (Sheriff) is the role, not part of the name.

  3019. · Vantage Port Washington Data Center · the speaker's role of a statement

    Before
    After
    Sheriff
    Why
    Speaker read again from the statement's source line, "Sheriff Christy Knowles": the title in front of the name (Sheriff) is the role, not part of the name.

  3020. · Vantage Port Washington Data Center · the speaker of a statement

    Before
    Sheriff Christy Knowles
    After
    Christy Knowles
    Why
    Speaker read again from the statement's source line, "Sheriff Christy Knowles": the title in front of the name (Sheriff) is the role, not part of the name.

  3021. · Byron Donalds · the speaker's role of a statement

    Before
    After
    U.S. Representative
    Why
    Speaker read again from the statement's source line, "U.S. Rep. Byron Donalds": the title in front of the name (U.S. Representative) is the role, not part of the name.

  3022. · Byron Donalds · the speaker of a statement

    Before
    U.S. Rep. Byron Donalds
    After
    Byron Donalds
    Why
    Speaker read again from the statement's source line, "U.S. Rep. Byron Donalds": the title in front of the name (U.S. Representative) is the role, not part of the name.

  3023. · Mikie Sherrill · the speaker's role of a statement

    Before
    After
    Governor
    Why
    Speaker read again from the statement's source line, "Governor Mikie Sherrill": the title in front of the name (Governor) is the role, not part of the name.

  3024. · Mikie Sherrill · the speaker of a statement

    Before
    Governor Mikie Sherrill
    After
    Mikie Sherrill
    Why
    Speaker read again from the statement's source line, "Governor Mikie Sherrill": the title in front of the name (Governor) is the role, not part of the name.

  3025. · Apple Prineville Campus · the speaker's role of a statement

    Before
    After
    Mayor
    Why
    Speaker read again from the statement's source line, "Mayor Jason Beebe": the title in front of the name (Mayor) is the role, not part of the name.

  3026. · Apple Prineville Campus · the speaker of a statement

    Before
    Mayor Jason Beebe
    After
    Jason Beebe
    Why
    Speaker read again from the statement's source line, "Mayor Jason Beebe": the title in front of the name (Mayor) is the role, not part of the name.

  3027. · Apple Prineville Campus · the speaker's role of a statement

    Before
    After
    Mayor
    Why
    Speaker read again from the statement's source line, "Mayor Jason Beebe": the title in front of the name (Mayor) is the role, not part of the name.

  3028. · Apple Prineville Campus · the speaker of a statement

    Before
    Mayor Jason Beebe
    After
    Jason Beebe
    Why
    Speaker read again from the statement's source line, "Mayor Jason Beebe": the title in front of the name (Mayor) is the role, not part of the name.

  3029. · Doug Ford · the speaker's role of a statement

    Before
    Ontario
    After
    Premier, Ontario
    Why
    Speaker read again from the statement's source line, "Premier Doug Ford, Ontario": the title in front of the name (Premier) is the role, not part of the name.

  3030. · Doug Ford · the speaker of a statement

    Before
    Premier Doug Ford
    After
    Doug Ford
    Why
    Speaker read again from the statement's source line, "Premier Doug Ford, Ontario": the title in front of the name (Premier) is the role, not part of the name.

  3031. · Doug Ford · the speaker's role of a statement

    Before
    Ontario
    After
    Premier, Ontario
    Why
    Speaker read again from the statement's source line, "Premier Doug Ford, Ontario": the title in front of the name (Premier) is the role, not part of the name.

  3032. · Doug Ford · the speaker of a statement

    Before
    Premier Doug Ford
    After
    Doug Ford
    Why
    Speaker read again from the statement's source line, "Premier Doug Ford, Ontario": the title in front of the name (Premier) is the role, not part of the name.

  3033. · Doug Ford · the speaker's role of a statement

    Before
    Ontario
    After
    Premier, Ontario
    Why
    Speaker read again from the statement's source line, "Premier Doug Ford, Ontario": the title in front of the name (Premier) is the role, not part of the name.

  3034. · Doug Ford · the speaker of a statement

    Before
    Premier Doug Ford
    After
    Doug Ford
    Why
    Speaker read again from the statement's source line, "Premier Doug Ford, Ontario": the title in front of the name (Premier) is the role, not part of the name.

  3035. · Kelly Ayotte · the speaker of a statement

    Before
    Gov. Kelly Ayotte
    After
    Kelly Ayotte
    Why
    Speaker read again from the statement's source line, "Gov. Kelly Ayotte, New Hampshire governor": the title in front of the name (Governor) is the role, not part of the name.

  3036. · Kelly Ayotte · the speaker of a statement

    Before
    Gov. Kelly Ayotte
    After
    Kelly Ayotte
    Why
    Speaker read again from the statement's source line, "Gov. Kelly Ayotte, New Hampshire governor": the title in front of the name (Governor) is the role, not part of the name.

  3037. · Kelly Ayotte · the speaker's role of a statement

    Before
    After
    Governor
    Why
    Speaker read again from the statement's source line, "Governor Kelly Ayotte": the title in front of the name (Governor) is the role, not part of the name.

  3038. · Kelly Ayotte · the speaker of a statement

    Before
    Governor Kelly Ayotte
    After
    Kelly Ayotte
    Why
    Speaker read again from the statement's source line, "Governor Kelly Ayotte": the title in front of the name (Governor) is the role, not part of the name.

  3039. · Kelly Ayotte · the speaker's role of a statement

    Before
    After
    Governor
    Why
    Speaker read again from the statement's source line, "Governor Kelly Ayotte": the title in front of the name (Governor) is the role, not part of the name.

  3040. · Kelly Ayotte · the speaker of a statement

    Before
    Governor Kelly Ayotte
    After
    Kelly Ayotte
    Why
    Speaker read again from the statement's source line, "Governor Kelly Ayotte": the title in front of the name (Governor) is the role, not part of the name.

  3041. · Kelly Ayotte · the speaker's role of a statement

    Before
    After
    Governor
    Why
    Speaker read again from the statement's source line, "Governor Kelly Ayotte": the title in front of the name (Governor) is the role, not part of the name.

  3042. · Kelly Ayotte · the speaker of a statement

    Before
    Governor Kelly Ayotte
    After
    Kelly Ayotte
    Why
    Speaker read again from the statement's source line, "Governor Kelly Ayotte": the title in front of the name (Governor) is the role, not part of the name.

  3043. · Kelly Ayotte · the speaker's role of a statement

    Before
    After
    Governor
    Why
    Speaker read again from the statement's source line, "Governor Kelly Ayotte": the title in front of the name (Governor) is the role, not part of the name.

  3044. · Kelly Ayotte · the speaker of a statement

    Before
    Governor Kelly Ayotte
    After
    Kelly Ayotte
    Why
    Speaker read again from the statement's source line, "Governor Kelly Ayotte": the title in front of the name (Governor) is the role, not part of the name.

  3045. · Kelly Ayotte · the speaker's role of a statement

    Before
    After
    Governor
    Why
    Speaker read again from the statement's source line, "Governor Kelly Ayotte": the title in front of the name (Governor) is the role, not part of the name.

  3046. · Kelly Ayotte · the speaker of a statement

    Before
    Governor Kelly Ayotte
    After
    Kelly Ayotte
    Why
    Speaker read again from the statement's source line, "Governor Kelly Ayotte": the title in front of the name (Governor) is the role, not part of the name.

  3047. · Kelly Ayotte · the speaker's role of a statement

    Before
    After
    Governor
    Why
    Speaker read again from the statement's source line, "Governor Kelly Ayotte": the title in front of the name (Governor) is the role, not part of the name.

  3048. · Kelly Ayotte · the speaker of a statement

    Before
    Governor Kelly Ayotte
    After
    Kelly Ayotte
    Why
    Speaker read again from the statement's source line, "Governor Kelly Ayotte": the title in front of the name (Governor) is the role, not part of the name.

  3049. · Kelly Ayotte · the speaker's role of a statement

    Before
    After
    Governor
    Why
    Speaker read again from the statement's source line, "Governor Kelly Ayotte": the title in front of the name (Governor) is the role, not part of the name.

  3050. · Kelly Ayotte · the speaker of a statement

    Before
    Governor Kelly Ayotte
    After
    Kelly Ayotte
    Why
    Speaker read again from the statement's source line, "Governor Kelly Ayotte": the title in front of the name (Governor) is the role, not part of the name.

  3051. · Bow Data Center (350 MW) · the speaker's role of a statement

    Before
    After
    Governor
    Why
    Speaker read again from the statement's source line, "Governor Kelly Ayotte": the title in front of the name (Governor) is the role, not part of the name.

  3052. · Bow Data Center (350 MW) · the speaker of a statement

    Before
    Governor Kelly Ayotte
    After
    Kelly Ayotte
    Why
    Speaker read again from the statement's source line, "Governor Kelly Ayotte": the title in front of the name (Governor) is the role, not part of the name.

  3053. · Jim Pillen · the speaker's role of a statement

    Before
    After
    Governor
    Why
    Speaker read again from the statement's source line, "Governor Jim Pillen": the title in front of the name (Governor) is the role, not part of the name.

  3054. · Jim Pillen · the speaker of a statement

    Before
    Governor Jim Pillen
    After
    Jim Pillen
    Why
    Speaker read again from the statement's source line, "Governor Jim Pillen": the title in front of the name (Governor) is the role, not part of the name.

  3055. · Hyperscale Data Dowagiac AI Data Center · the speaker's role of a statement

    Before
    After
    President
    Why
    Speaker read again from the statement's source line, "President Donald Trump": the title in front of the name (President) is the role, not part of the name.

  3056. · Hyperscale Data Dowagiac AI Data Center · the speaker of a statement

    Before
    President Donald Trump
    After
    Donald Trump
    Why
    Speaker read again from the statement's source line, "President Donald Trump": the title in front of the name (President) is the role, not part of the name.

  3057. · Hyperscale Data Dowagiac AI Data Center · the speaker of a statement

    Before
    Rep. Steve Carra
    After
    Steve Carra
    Why
    Speaker read again from the statement's source line, "Rep. Steve Carra, Michigan House of Representatives": the title in front of the name (Representative) is the role, not part of the name.

  3058. · Donald Trump · the speaker's role of a statement

    Before
    After
    President
    Why
    Speaker read again from the statement's source line, "President Donald Trump": the title in front of the name (President) is the role, not part of the name.

  3059. · Donald Trump · the speaker of a statement

    Before
    President Donald Trump
    After
    Donald Trump
    Why
    Speaker read again from the statement's source line, "President Donald Trump": the title in front of the name (President) is the role, not part of the name.

  3060. · Johnny Ray Salling · the speaker of a statement

    Before
    Sen. Johnny Ray Salling
    After
    Johnny Ray Salling
    Why
    Speaker read again from the statement's source line, "Sen. Johnny Ray Salling, Maryland State Senator, Baltimore County": the title in front of the name (Senator) is the role, not part of the name.

  3061. · Johnny Ray Salling · the speaker of a statement

    Before
    Sen. Johnny Ray Salling
    After
    Johnny Ray Salling
    Why
    Speaker read again from the statement's source line, "Sen. Johnny Ray Salling, Maryland State Senator, Baltimore County": the title in front of the name (Senator) is the role, not part of the name.

  3062. · Johnny Ray Salling · the speaker of a statement

    Before
    Sen. Johnny Ray Salling
    After
    Johnny Ray Salling
    Why
    Speaker read again from the statement's source line, "Sen. Johnny Ray Salling, Maryland State Senator, Baltimore County": the title in front of the name (Senator) is the role, not part of the name.

  3063. · Johnny Ray Salling · the speaker of a statement

    Before
    Sen. Johnny Ray Salling
    After
    Johnny Ray Salling
    Why
    Speaker read again from the statement's source line, "Sen. Johnny Ray Salling, Maryland State Senator, Baltimore County": the title in front of the name (Senator) is the role, not part of the name.

  3064. · Jeff Landry · the speaker of a statement

    Before
    Gov. Jeff Landry
    After
    Jeff Landry
    Why
    Speaker read again from the statement's source line, "Gov. Jeff Landry, Louisiana Governor": the title in front of the name (Governor) is the role, not part of the name.

  3065. · Meta Louisiana data center · the speaker's role of a statement

    Before
    Louisiana Legislative Black Caucus chairman
    After
    Representative, Louisiana Legislative Black Caucus chairman
    Why
    Speaker read again from the statement's source line, "Rep. Edmond Jordan, Louisiana Legislative Black Caucus chairman": the title in front of the name (Representative) is the role, not part of the name.

  3066. · Meta Louisiana data center · the speaker of a statement

    Before
    Rep. Edmond Jordan
    After
    Edmond Jordan
    Why
    Speaker read again from the statement's source line, "Rep. Edmond Jordan, Louisiana Legislative Black Caucus chairman": the title in front of the name (Representative) is the role, not part of the name.

  3067. · Meta Louisiana data center · the speaker's role of a statement

    Before
    Louisiana House
    After
    Representative, Louisiana House
    Why
    Speaker read again from the statement's source line, "Rep. Denise Marcelle, Louisiana House": the title in front of the name (Representative) is the role, not part of the name.

  3068. · Meta Louisiana data center · the speaker of a statement

    Before
    Rep. Denise Marcelle
    After
    Denise Marcelle
    Why
    Speaker read again from the statement's source line, "Rep. Denise Marcelle, Louisiana House": the title in front of the name (Representative) is the role, not part of the name.

  3069. · Meta Louisiana data center · the speaker's role of a statement

    Before
    House Democratic Caucus chairman
    After
    Representative, House Democratic Caucus chairman
    Why
    Speaker read again from the statement's source line, "Rep. Kyle Green, House Democratic Caucus chairman": the title in front of the name (Representative) is the role, not part of the name.

  3070. · Meta Louisiana data center · the speaker of a statement

    Before
    Rep. Kyle Green
    After
    Kyle Green
    Why
    Speaker read again from the statement's source line, "Rep. Kyle Green, House Democratic Caucus chairman": the title in front of the name (Representative) is the role, not part of the name.

  3071. · Meta Louisiana data center · the speaker's role of a statement

    Before
    House Democratic Caucus chairman
    After
    Representative, House Democratic Caucus chairman
    Why
    Speaker read again from the statement's source line, "Rep. Kyle Green, House Democratic Caucus chairman": the title in front of the name (Representative) is the role, not part of the name.

  3072. · Meta Louisiana data center · the speaker of a statement

    Before
    Rep. Kyle Green
    After
    Kyle Green
    Why
    Speaker read again from the statement's source line, "Rep. Kyle Green, House Democratic Caucus chairman": the title in front of the name (Representative) is the role, not part of the name.

  3073. · Stacy Garrity · the speaker's role of a statement

    Before
    After
    State Treasurer
    Why
    Speaker read again from the statement's source line, "State Treasurer Stacy Garrity": the title in front of the name (State Treasurer) is the role, not part of the name.

  3074. · Stacy Garrity · the speaker of a statement

    Before
    State Treasurer Stacy Garrity
    After
    Stacy Garrity
    Why
    Speaker read again from the statement's source line, "State Treasurer Stacy Garrity": the title in front of the name (State Treasurer) is the role, not part of the name.

  3075. · Dave McCormick · the speaker's role of a statement

    Before
    R-Pa.
    After
    U.S. Senator, R-Pa.
    Why
    Speaker read again from the statement's source line, "U.S. Sen. Dave McCormick, R-Pa.": the title in front of the name (U.S. Senator) is the role, not part of the name.

  3076. · Dave McCormick · the speaker of a statement

    Before
    U.S. Sen. Dave McCormick
    After
    Dave McCormick
    Why
    Speaker read again from the statement's source line, "U.S. Sen. Dave McCormick, R-Pa.": the title in front of the name (U.S. Senator) is the role, not part of the name.

  3077. · Dave McCormick · the speaker's role of a statement

    Before
    R-Pa.
    After
    U.S. Senator, R-Pa.
    Why
    Speaker read again from the statement's source line, "U.S. Sen. Dave McCormick, R-Pa.": the title in front of the name (U.S. Senator) is the role, not part of the name.

  3078. · Dave McCormick · the speaker of a statement

    Before
    U.S. Sen. Dave McCormick
    After
    Dave McCormick
    Why
    Speaker read again from the statement's source line, "U.S. Sen. Dave McCormick, R-Pa.": the title in front of the name (U.S. Senator) is the role, not part of the name.

  3079. · John Fetterman · the speaker's role of a statement

    Before
    D-Pa.
    After
    U.S. Senator, D-Pa.
    Why
    Speaker read again from the statement's source line, "U.S. Sen. John Fetterman, D-Pa.": the title in front of the name (U.S. Senator) is the role, not part of the name.

  3080. · John Fetterman · the speaker of a statement

    Before
    U.S. Sen. John Fetterman
    After
    John Fetterman
    Why
    Speaker read again from the statement's source line, "U.S. Sen. John Fetterman, D-Pa.": the title in front of the name (U.S. Senator) is the role, not part of the name.

  3081. · John Fetterman · the speaker's role of a statement

    Before
    D-Pa.
    After
    U.S. Senator, D-Pa.
    Why
    Speaker read again from the statement's source line, "U.S. Sen. John Fetterman, D-Pa.": the title in front of the name (U.S. Senator) is the role, not part of the name.

  3082. · John Fetterman · the speaker of a statement

    Before
    U.S. Sen. John Fetterman
    After
    John Fetterman
    Why
    Speaker read again from the statement's source line, "U.S. Sen. John Fetterman, D-Pa.": the title in front of the name (U.S. Senator) is the role, not part of the name.

  3083. · John Fetterman · the speaker's role of a statement

    Before
    D-Pa.
    After
    U.S. Senator, D-Pa.
    Why
    Speaker read again from the statement's source line, "U.S. Sen. John Fetterman, D-Pa.": the title in front of the name (U.S. Senator) is the role, not part of the name.

  3084. · John Fetterman · the speaker of a statement

    Before
    U.S. Sen. John Fetterman
    After
    John Fetterman
    Why
    Speaker read again from the statement's source line, "U.S. Sen. John Fetterman, D-Pa.": the title in front of the name (U.S. Senator) is the role, not part of the name.

  3085. · Donald Trump · the speaker's role of a statement

    Before
    After
    President
    Why
    Speaker read again from the statement's source line, "President Donald Trump": the title in front of the name (President) is the role, not part of the name.

  3086. · Donald Trump · the speaker of a statement

    Before
    President Donald Trump
    After
    Donald Trump
    Why
    Speaker read again from the statement's source line, "President Donald Trump": the title in front of the name (President) is the role, not part of the name.

  3087. · Donald Trump · the speaker's role of a statement

    Before
    After
    President
    Why
    Speaker read again from the statement's source line, "President Donald Trump": the title in front of the name (President) is the role, not part of the name.

  3088. · Donald Trump · the speaker of a statement

    Before
    President Donald Trump
    After
    Donald Trump
    Why
    Speaker read again from the statement's source line, "President Donald Trump": the title in front of the name (President) is the role, not part of the name.

  3089. · Stratos Project · the speaker's role of a statement

    Before
    After
    Governor
    Why
    Speaker read again from the statement's source line, "Gov. Spencer Cox": the title in front of the name (Governor) is the role, not part of the name.

  3090. · Stratos Project · the speaker of a statement

    Before
    Gov. Spencer Cox
    After
    Spencer Cox
    Why
    Speaker read again from the statement's source line, "Gov. Spencer Cox": the title in front of the name (Governor) is the role, not part of the name.

  3091. · Stratos Project · the speaker's role of a statement

    Before
    After
    Governor
    Why
    Speaker read again from the statement's source line, "Gov. Spencer Cox": the title in front of the name (Governor) is the role, not part of the name.

  3092. · Stratos Project · the speaker of a statement

    Before
    Gov. Spencer Cox
    After
    Spencer Cox
    Why
    Speaker read again from the statement's source line, "Gov. Spencer Cox": the title in front of the name (Governor) is the role, not part of the name.

  3093. · Volition Industries Spanish Fork · the speaker's role of a statement

    Before
    After
    Mayor
    Why
    Speaker read again from the statement's source line, "Mayor Mike Mendenhall": the title in front of the name (Mayor) is the role, not part of the name.

  3094. · Volition Industries Spanish Fork · the speaker of a statement

    Before
    Mayor Mike Mendenhall
    After
    Mike Mendenhall
    Why
    Speaker read again from the statement's source line, "Mayor Mike Mendenhall": the title in front of the name (Mayor) is the role, not part of the name.

  3095. · Donald Trump · the speaker's role of a statement

    Before
    After
    President
    Why
    Speaker read again from the statement's source line, "President Donald Trump": the title in front of the name (President) is the role, not part of the name.

  3096. · Donald Trump · the speaker of a statement

    Before
    President Donald Trump
    After
    Donald Trump
    Why
    Speaker read again from the statement's source line, "President Donald Trump": the title in front of the name (President) is the role, not part of the name.

  3097. · PORTS-Pike Technology Campus · the speaker's role of a statement

    Before
    After
    Energy Secretary
    Why
    Speaker read again from the statement's source line, "Energy Secretary Chris Wright": the title in front of the name (Energy Secretary) is the role, not part of the name.

  3098. · PORTS-Pike Technology Campus · the speaker of a statement

    Before
    Energy Secretary Chris Wright
    After
    Chris Wright
    Why
    Speaker read again from the statement's source line, "Energy Secretary Chris Wright": the title in front of the name (Energy Secretary) is the role, not part of the name.

  3099. · Greg Abbott · the speaker's role of a statement

    Before
    After
    Governor
    Why
    Speaker read again from the statement's source line, "Gov. Greg Abbott": the title in front of the name (Governor) is the role, not part of the name.

  3100. · Greg Abbott · the speaker of a statement

    Before
    Gov. Greg Abbott
    After
    Greg Abbott
    Why
    Speaker read again from the statement's source line, "Gov. Greg Abbott": the title in front of the name (Governor) is the role, not part of the name.

  3101. · Greg Abbott · the speaker's role of a statement

    Before
    After
    Governor
    Why
    Speaker read again from the statement's source line, "Gov. Greg Abbott": the title in front of the name (Governor) is the role, not part of the name.

  3102. · Greg Abbott · the speaker of a statement

    Before
    Gov. Greg Abbott
    After
    Greg Abbott
    Why
    Speaker read again from the statement's source line, "Gov. Greg Abbott": the title in front of the name (Governor) is the role, not part of the name.

  3103. · Greg Abbott · the speaker's role of a statement

    Before
    After
    Governor
    Why
    Speaker read again from the statement's source line, "Gov. Greg Abbott": the title in front of the name (Governor) is the role, not part of the name.

  3104. · Greg Abbott · the speaker of a statement

    Before
    Gov. Greg Abbott
    After
    Greg Abbott
    Why
    Speaker read again from the statement's source line, "Gov. Greg Abbott": the title in front of the name (Governor) is the role, not part of the name.

  3105. · Andrea Salinas · the speaker of a statement

    Before
    Rep. Andrea Salinas
    After
    Andrea Salinas
    Why
    Speaker read again from the statement's source line, "Rep. Andrea Salinas, U.S. House of Representatives": the title in front of the name (Representative) is the role, not part of the name.

  3106. · Nicholeen Peck · the speaker's role of a statement

    Before
    After
    Representative
    Why
    Speaker read again from the statement's source line, "Rep. Nicholeen Peck": the title in front of the name (Representative) is the role, not part of the name.

  3107. · Nicholeen Peck · the speaker of a statement

    Before
    Rep. Nicholeen Peck
    After
    Nicholeen Peck
    Why
    Speaker read again from the statement's source line, "Rep. Nicholeen Peck": the title in front of the name (Representative) is the role, not part of the name.

  3108. · Nicholeen Peck · the speaker's role of a statement

    Before
    After
    Representative
    Why
    Speaker read again from the statement's source line, "Rep. Nicholeen Peck": the title in front of the name (Representative) is the role, not part of the name.

  3109. · Nicholeen Peck · the speaker of a statement

    Before
    Rep. Nicholeen Peck
    After
    Nicholeen Peck
    Why
    Speaker read again from the statement's source line, "Rep. Nicholeen Peck": the title in front of the name (Representative) is the role, not part of the name.

  3110. · Jim Dunnigan · the speaker's role of a statement

    Before
    After
    Representative
    Why
    Speaker read again from the statement's source line, "Rep. Jim Dunnigan": the title in front of the name (Representative) is the role, not part of the name.

  3111. · Jim Dunnigan · the speaker of a statement

    Before
    Rep. Jim Dunnigan
    After
    Jim Dunnigan
    Why
    Speaker read again from the statement's source line, "Rep. Jim Dunnigan": the title in front of the name (Representative) is the role, not part of the name.

  3112. · Stratos Project · the speaker of a statement

    Before
    Governor Spencer Cox
    After
    Spencer Cox
    Why
    Speaker read again from the statement's source line, "Governor Spencer Cox, Utah Governor": the title in front of the name (Governor) is the role, not part of the name.

  3113. · Stratos Project · the speaker of a statement

    Before
    Governor Spencer Cox
    After
    Spencer Cox
    Why
    Speaker read again from the statement's source line, "Governor Spencer Cox, Utah Governor": the title in front of the name (Governor) is the role, not part of the name.

  3114. · Stratos Project · the speaker of a statement

    Before
    Governor Spencer Cox
    After
    Spencer Cox
    Why
    Speaker read again from the statement's source line, "Governor Spencer Cox, Utah Governor": the title in front of the name (Governor) is the role, not part of the name.

  3115. · Stratos Project · the speaker of a statement

    Before
    Governor Spencer Cox
    After
    Spencer Cox
    Why
    Speaker read again from the statement's source line, "Governor Spencer Cox, Utah Governor": the title in front of the name (Governor) is the role, not part of the name.

  3116. · Stratos Project · the speaker of a statement

    Before
    Gov. Spencer Cox
    After
    Spencer Cox
    Why
    Speaker read again from the statement's source line, "Gov. Spencer Cox, Governor of Utah": the title in front of the name (Governor) is the role, not part of the name.

  3117. · Stratos Project · the speaker of a statement

    Before
    Gov. Spencer Cox
    After
    Spencer Cox
    Why
    Speaker read again from the statement's source line, "Gov. Spencer Cox, Governor of Utah": the title in front of the name (Governor) is the role, not part of the name.

  3118. · Stratos Project · the speaker of a statement

    Before
    Gov. Spencer Cox
    After
    Spencer Cox
    Why
    Speaker read again from the statement's source line, "Gov. Spencer Cox, Governor of Utah": the title in front of the name (Governor) is the role, not part of the name.

  3119. · Donald Trump · the speaker's role of a statement

    Before
    After
    President
    Why
    Speaker read again from the statement's source line, "President Donald Trump": the title in front of the name (President) is the role, not part of the name.

  3120. · Donald Trump · the speaker of a statement

    Before
    President Donald Trump
    After
    Donald Trump
    Why
    Speaker read again from the statement's source line, "President Donald Trump": the title in front of the name (President) is the role, not part of the name.

  3121. · Stratos Project · the speaker of a statement

    Before
    Rep. Jim Dunnigan
    After
    Jim Dunnigan
    Why
    Speaker read again from the statement's source line, "Rep. Jim Dunnigan, R-Taylorsville, Utah Representative": the title in front of the name (Representative) is the role, not part of the name.

  3122. · Stratos Project · the speaker of a statement

    Before
    Rep. Doug Fiefia
    After
    Doug Fiefia
    Why
    Speaker read again from the statement's source line, "Rep. Doug Fiefia, R-Herriman, Utah Representative": the title in front of the name (Representative) is the role, not part of the name.

  3123. · Stratos Project · the speaker's role of a statement

    Before
    R-Pleasant Grove, chair, Economic Development and Workforce Services Interim Committee
    After
    Representative, R-Pleasant Grove, chair, Economic Development and Workforce Services Interim Committee
    Why
    Speaker read again from the statement's source line, "Rep. Jon Hawkins, R-Pleasant Grove, chair, Economic Development and Workforce Services Interim Committee": the title in front of the name (Representative) is the role, not part of the name.

  3124. · Stratos Project · the speaker of a statement

    Before
    Rep. Jon Hawkins
    After
    Jon Hawkins
    Why
    Speaker read again from the statement's source line, "Rep. Jon Hawkins, R-Pleasant Grove, chair, Economic Development and Workforce Services Interim Committee": the title in front of the name (Representative) is the role, not part of the name.

  3125. · Paul Cutler · the speaker of a statement

    Before
    Rep. Paul Cutler
    After
    Paul Cutler
    Why
    Speaker read again from the statement's source line, "Rep. Paul Cutler, Utah representative": the title in front of the name (Representative) is the role, not part of the name.

  3126. · Jill Koford · the speaker of a statement

    Before
    Rep. Jill Koford
    After
    Jill Koford
    Why
    Speaker read again from the statement's source line, "Rep. Jill Koford, R-Ogden, Utah Representative": the title in front of the name (Representative) is the role, not part of the name.

  3127. · Donald Trump · the speaker's role of a statement

    Before
    After
    President
    Why
    Speaker read again from the statement's source line, "President Donald Trump": the title in front of the name (President) is the role, not part of the name.

  3128. · Donald Trump · the speaker of a statement

    Before
    President Donald Trump
    After
    Donald Trump
    Why
    Speaker read again from the statement's source line, "President Donald Trump": the title in front of the name (President) is the role, not part of the name.

  3129. · a statement · the speaker's role of a statement

    Before
    After
    President
    Why
    Speaker read again from the statement's source line, "President Donald Trump": the title in front of the name (President) is the role, not part of the name.

  3130. · Donald Trump · the speaker of a statement

    Before
    President Donald Trump
    After
    Donald Trump
    Why
    Speaker read again from the statement's source line, "President Donald Trump": the title in front of the name (President) is the role, not part of the name.

  3131. · Kentucky · the date of a scorecard event

    Before
    2026-09-11
    After
    2026-08-06
    Why
    The event's own sentence names the day of the act (Aug. 6), August 6, 2026; the row carried the date of the report that carried it, September 11, 2026. Read again from the card line that wrote it.

  3132. · Box Elder County · the date of a scorecard event

    Before
    2026-09-24
    After
    2026-07-15
    Why
    The event's own sentence names the day of the act (July 15), July 15, 2026; the row carried the date of the report that carried it, September 24, 2026. Read again from the card line that wrote it.

  3133. · Texas · the date of a scorecard event

    Before
    2026-09-24
    After
    2026-09-21
    Why
    The event's own sentence names the day of the act (September 21), September 21, 2026; the row carried the date of the report that carried it, September 24, 2026. Read again from the card line that wrote it.

  3134. · Taylor · the date of a scorecard event

    Before
    2026-09-24
    After
    2026-07-09
    Why
    The event's own sentence names the day of the act (July 9), July 9, 2026; the row carried the date of the report that carried it, September 24, 2026. Read again from the card line that wrote it.

  3135. · New Mexico · the date of a scorecard event

    Before
    2026-09-23
    After
    2026-09-17
    Why
    The event's own sentence names the day of the act (September 17), September 17, 2026; the row carried the date of the report that carried it, September 23, 2026. Read again from the card line that wrote it.

  3136. · Butte-Silver Bow County · the date of a scorecard event

    Before
    2026-09-24
    After
    2026-09-22
    Why
    The event's own sentence names the day of the act (September 22), September 22, 2026; the row carried the date of the report that carried it, September 24, 2026. Read again from the card line that wrote it.

  3137. · United States (federal) · the date of a scorecard event

    Before
    2026-09-23
    After
    2026-09-17
    Why
    The event's own sentence names the day of the act (September 17, 2026), September 17, 2026; the row carried the date of the report that carried it, September 23, 2026. Read again from the card line that wrote it.

  3138. · United States (federal) · the date of a scorecard event

    Before
    2026-09-23
    After
    2026-09-16
    Why
    The event's own sentence names the day of the act (September 16, 2026), September 16, 2026; the row carried the date of the report that carried it, September 23, 2026. Read again from the card line that wrote it.

  3139. · Prince William County · the date of a scorecard event

    Before
    2026-09-23
    After
    2026-09-22
    Why
    The event's own sentence names the day of the act (Tuesday), September 22, 2026; the row carried the date of the report that carried it, September 23, 2026. Read again from the card line that wrote it.

  3140. · California · the date of a scorecard event

    Before
    2026-09-23
    After
    2026-09-21
    Why
    The event's own sentence names the day of the act (Monday), September 21, 2026; the row carried the date of the report that carried it, September 23, 2026. Read again from the card line that wrote it.

  3141. · Pulaski County · the date of a scorecard event

    Before
    2026-09-23
    After
    2026-09-22
    Why
    The event's own sentence names the day of the act (Tuesday night), September 22, 2026; the row carried the date of the report that carried it, September 23, 2026. Read again from the card line that wrote it.

  3142. · Butte-Silver Bow · the date of a scorecard event

    Before
    2026-09-23
    After
    2026-08-12
    Why
    The event's own sentence names the day of the act (August 12, 2026), August 12, 2026; the row carried the date of the report that carried it, September 23, 2026. Read again from the card line that wrote it.

  3143. · Butte-Silver Bow · the date of a scorecard event

    Before
    2026-09-22
    After
    2026-04-29
    Why
    The event's own sentence names the day of the act (April 29, 2026), April 29, 2026; the row carried the date of the report that carried it, September 22, 2026. Read again from the card line that wrote it.

  3144. · North Carolina · the date of a scorecard event

    Before
    2026-09-23
    After
    2026-09-18
    Why
    The event's own sentence names the day of the act (September 18), September 18, 2026; the row carried the date of the report that carried it, September 23, 2026. Read again from the card line that wrote it.

  3145. · Pima County · the date of a scorecard event

    Before
    2026-09-23
    After
    2026-09-22
    Why
    The event's own sentence names the day of the act (Tuesday), September 22, 2026; the row carried the date of the report that carried it, September 23, 2026. Read again from the card line that wrote it.

  3146. · Texas · the date of a scorecard event

    Before
    2026-09-23
    After
    2026-09-22
    Why
    The event's own sentence names the day of the act (September 22, 2026), September 22, 2026; the row carried the date of the report that carried it, September 23, 2026. Read again from the card line that wrote it.

  3147. · Texas · the date of a scorecard event

    Before
    2026-09-23
    After
    2026-08-03
    Why
    The event's own sentence names the day of the act (August 3, 2026), August 3, 2026; the row carried the date of the report that carried it, September 23, 2026. Read again from the card line that wrote it.

  3148. · Virginia · the date of a scorecard event

    Before
    2026-09-23
    After
    2026-09-18
    Why
    The event's own sentence names the day of the act (September 18, 2026), September 18, 2026; the row carried the date of the report that carried it, September 23, 2026. Read again from the card line that wrote it.

  3149. · Virginia · the date of a scorecard event

    Before
    2026-09-23
    After
    2026-09-18
    Why
    The event's own sentence names the day of the act (September 18, 2026), September 18, 2026; the row carried the date of the report that carried it, September 23, 2026. Read again from the card line that wrote it.

  3150. · Virginia · the date of a scorecard event

    Before
    2026-09-22
    After
    2026-09-18
    Why
    The event's own sentence names the day of the act (September 18, 2026), September 18, 2026; the row carried the date of the report that carried it, September 22, 2026. Read again from the card line that wrote it.

  3151. · Kershaw County · the date of a scorecard event

    Before
    2026-09-23
    After
    2026-09-22
    Why
    The event's own sentence names the day of the act (Tuesday night), September 22, 2026; the row carried the date of the report that carried it, September 23, 2026. Read again from the card line that wrote it.

  3152. · Sioux County · the date of a scorecard event

    Before
    2026-09-23
    After
    2026-09-10
    Why
    The event's own sentence names the day of the act (September 10, 2026), September 10, 2026; the row carried the date of the report that carried it, September 23, 2026. Read again from the card line that wrote it.

  3153. · Sioux County · the date of a scorecard event

    Before
    2026-09-23
    After
    2026-06-16
    Why
    The event's own sentence names the day of the act (June 16, 2026), June 16, 2026; the row carried the date of the report that carried it, September 23, 2026. Read again from the card line that wrote it.

  3154. · Calvert County · the date of a scorecard event

    Before
    2026-09-23
    After
    2026-08-04
    Why
    The event's own sentence names the day of the act (August 4, 2026), August 4, 2026; the row carried the date of the report that carried it, September 23, 2026. Read again from the card line that wrote it.

  3155. · Maryland · the date of a scorecard event

    Before
    2026-09-20
    After
    2026-05-07
    Why
    The event's own sentence names the day of the act (May 7, 2026), May 7, 2026; the row carried the date of the report that carried it, September 20, 2026. Read again from the card line that wrote it.

  3156. · Bridgewater Township · the date of a scorecard event

    Before
    2026-09-23
    After
    2026-09-08
    Why
    The event's own sentence names the day of the act (September 8), September 8, 2026; the row carried the date of the report that carried it, September 23, 2026. Read again from the card line that wrote it.

  3157. · New York · the date of a scorecard event

    Before
    2026-09-23
    After
    2026-07-15
    Why
    The event's own sentence names the day of the act (July 15, 2026), July 15, 2026; the row carried the date of the report that carried it, September 23, 2026. Read again from the card line that wrote it.

  3158. · Sangamon County · the date of a scorecard event

    Before
    2026-09-23
    After
    2026-09-11
    Why
    The event's own sentence names the day of the act (October 9), September 11, 2026; the row carried the date of the report that carried it, September 23, 2026. Read again from the card line that wrote it.

  3159. · Sangamon County · the date of a scorecard event

    Before
    2026-09-23
    After
    2026-04-07
    Why
    The event's own sentence names the day of the act (April 7, 2026), April 7, 2026; the row carried the date of the report that carried it, September 23, 2026. Read again from the card line that wrote it.

  3160. · Texas · the date of a scorecard event

    Before
    2026-09-23
    After
    2026-09-14
    Why
    The event's own sentence names the day of the act (September 14), September 14, 2026; the row carried the date of the report that carried it, September 23, 2026. Read again from the card line that wrote it.

  3161. · Prince William County · the date of a scorecard event

    Before
    2026-09-23
    After
    2026-09-22
    Why
    The event's own sentence names the day of the act (September 22, 2026), September 22, 2026; the row carried the date of the report that carried it, September 23, 2026. Read again from the card line that wrote it.

  3162. · Pulaski County · the date of a scorecard event

    Before
    2026-09-23
    After
    2026-09-22
    Why
    The event's own sentence names the day of the act (September 22, 2026), September 22, 2026; the row carried the date of the report that carried it, September 23, 2026. Read again from the card line that wrote it.

  3163. · Pulaski County · the date of a scorecard event

    Before
    2026-09-23
    After
    2026-09-22
    Why
    The event's own sentence names the day of the act (Tuesday), September 22, 2026; the row carried the date of the report that carried it, September 23, 2026. Read again from the card line that wrote it.

  3164. · Michigan · the date of a scorecard event

    Before
    2026-09-23
    After
    2026-09-22
    Why
    The event's own sentence names the day of the act (Tuesday), September 22, 2026; the row carried the date of the report that carried it, September 23, 2026. Read again from the card line that wrote it.

  3165. · New Jersey · the date of a scorecard event

    Before
    2026-09-23
    After
    2026-08-27
    Why
    The event's own sentence names the day of the act (August 27), August 27, 2026; the row carried the date of the report that carried it, September 23, 2026. Read again from the card line that wrote it.

  3166. · Texas · the date of a scorecard event

    Before
    2026-09-22
    After
    2026-09-21
    Why
    The event's own sentence names the day of the act (September 21, 2026), September 21, 2026; the row carried the date of the report that carried it, September 22, 2026. Read again from the card line that wrote it.

  3167. · Texas · the date of a scorecard event

    Before
    2026-09-22
    After
    2026-09-21
    Why
    The event's own sentence names the day of the act (Monday), September 21, 2026; the row carried the date of the report that carried it, September 22, 2026. Read again from the card line that wrote it.

  3168. · Ohio · the date of a scorecard event

    Before
    2026-09-22
    After
    2026-09-18
    Why
    The event's own sentence names the day of the act (September 18), September 18, 2026; the row carried the date of the report that carried it, September 22, 2026. Read again from the card line that wrote it.

  3169. · Texas · the date of a scorecard event

    Before
    2026-09-22
    After
    2026-09-21
    Why
    The event's own sentence names the day of the act (Monday), September 21, 2026; the row carried the date of the report that carried it, September 22, 2026. Read again from the card line that wrote it.

  3170. · Texas · the date of a scorecard event

    Before
    2026-09-22
    After
    2026-09-21
    Why
    The event's own sentence names the day of the act (September 21, 2026), September 21, 2026; the row carried the date of the report that carried it, September 22, 2026. Read again from the card line that wrote it.

  3171. · United States (federal) · the date of a scorecard event

    Before
    2026-09-22
    After
    2026-09-16
    Why
    The event's own sentence names the day of the act (September 16), September 16, 2026; the row carried the date of the report that carried it, September 22, 2026. Read again from the card line that wrote it.

  3172. · California · the date of a scorecard event

    Before
    2026-09-22
    After
    2026-09-21
    Why
    The event's own sentence names the day of the act (Monday), September 21, 2026; the row carried the date of the report that carried it, September 22, 2026. Read again from the card line that wrote it.

  3173. · Springfield Township · the date of a scorecard event

    Before
    2026-09-22
    After
    2026-09-08
    Why
    The event's own sentence names the day of the act (September 8, 2026), September 8, 2026; the row carried the date of the report that carried it, September 22, 2026. Read again from the card line that wrote it.

  3174. · Wilmington · the date of a scorecard event

    Before
    2026-09-22
    After
    2026-09-18
    Why
    The event's own sentence names the day of the act (Friday), September 18, 2026; the row carried the date of the report that carried it, September 22, 2026. Read again from the card line that wrote it.

  3175. · Texas · the date of a scorecard event

    Before
    2026-09-21
    After
    2026-09-14
    Why
    The event's own sentence names the day of the act (Sept. 14), September 14, 2026; the row carried the date of the report that carried it, September 21, 2026. Read again from the card line that wrote it.

  3176. · Texas · the date of a scorecard event

    Before
    2026-09-21
    After
    2026-09-14
    Why
    The event's own sentence names the day of the act (September 14), September 14, 2026; the row carried the date of the report that carried it, September 21, 2026. Read again from the card line that wrote it.

  3177. · Texas · the date of a scorecard event

    Before
    2026-09-21
    After
    2026-09-17
    Why
    The event's own sentence names the day of the act (Thursday), September 17, 2026; the row carried the date of the report that carried it, September 21, 2026. Read again from the card line that wrote it.

  3178. · Nevada · the date of a scorecard event

    Before
    2026-09-21
    After
    2026-09-17
    Why
    The event's own sentence names the day of the act (September 17, 2026), September 17, 2026; the row carried the date of the report that carried it, September 21, 2026. Read again from the card line that wrote it.

  3179. · Colleton County · the date of a scorecard event

    Before
    2026-09-17
    After
    2026-09-14
    Why
    The event's own sentence names the day of the act (September 14, 2026), September 14, 2026; the row carried the date of the report that carried it, September 17, 2026. Read again from the card line that wrote it.

  3180. · Rose Hill · the date of a scorecard event

    Before
    2026-09-22
    After
    2026-09-21
    Why
    The event's own sentence names the day of the act (October 5), September 21, 2026; the row carried the date of the report that carried it, September 22, 2026. Read again from the card line that wrote it.

  3181. · Texas · the date of a scorecard event

    Before
    2026-09-21
    After
    2026-09-14
    Why
    The event's own sentence names the day of the act (September 14), September 14, 2026; the row carried the date of the report that carried it, September 21, 2026. Read again from the card line that wrote it.

  3182. · Texas · the date of a scorecard event

    Before
    2026-09-21
    After
    2026-09-14
    Why
    The event's own sentence names the day of the act (September 14), September 14, 2026; the row carried the date of the report that carried it, September 21, 2026. Read again from the card line that wrote it.

  3183. · Virginia · the date of a scorecard event

    Before
    2026-09-21
    After
    2026-07-01
    Why
    The event's own sentence names the day of the act (July 1), July 1, 2026; the row carried the date of the report that carried it, September 21, 2026. Read again from the card line that wrote it.

  3184. · Biddeford · the date of a scorecard event

    Before
    2026-09-03
    After
    2026-09-02
    Why
    The event's own sentence names the day of the act (Wednesday night), September 2, 2026; the row carried the date of the report that carried it, September 3, 2026. Read again from the card line that wrote it.

  3185. · Baltimore County · the date of a scorecard event

    Before
    2026-09-21
    After
    2026-09-17
    Why
    The event's own sentence names the day of the act (September 17, 2026), September 17, 2026; the row carried the date of the report that carried it, September 21, 2026. Read again from the card line that wrote it.

  3186. · Mississippi · the date of a scorecard event

    Before
    2026-09-21
    After
    2026-09-15
    Why
    The event's own sentence names the day of the act (September 15), September 15, 2026; the row carried the date of the report that carried it, September 21, 2026. Read again from the card line that wrote it.

  3187. · Yellowstone County · the date of a scorecard event

    Before
    2026-09-21
    After
    2026-08-11
    Why
    The event's own sentence names the day of the act (August 11, 2026), August 11, 2026; the row carried the date of the report that carried it, September 21, 2026. Read again from the card line that wrote it.

  3188. · Statesboro · the date of a scorecard event

    Before
    2026-09-21
    After
    2026-06-02
    Why
    The event's own sentence names the day of the act (June 2, 2026), June 2, 2026; the row carried the date of the report that carried it, September 21, 2026. Read again from the card line that wrote it.

  3189. · Ohio · the date of a scorecard event

    Before
    2026-09-21
    After
    2026-08-12
    Why
    The event's own sentence names the day of the act (August 12, 2026), August 12, 2026; the row carried the date of the report that carried it, September 21, 2026. Read again from the card line that wrote it.

  3190. · Virginia · the date of a scorecard event

    Before
    2026-09-21
    After
    2026-09-18
    Why
    The event's own sentence names the day of the act (Friday), September 18, 2026; the row carried the date of the report that carried it, September 21, 2026. Read again from the card line that wrote it.

  3191. · Virginia · the date of a scorecard event

    Before
    2026-09-19
    After
    2026-09-18
    Why
    The event's own sentence names the day of the act (Friday), September 18, 2026; the row carried the date of the report that carried it, September 19, 2026. Read again from the card line that wrote it.

  3192. · Marathon County · the date of a scorecard event

    Before
    2026-09-21
    After
    2026-08-25
    Why
    The event's own sentence names the day of the act (Aug. 25), August 25, 2026; the row carried the date of the report that carried it, September 21, 2026. Read again from the card line that wrote it.

  3193. · Wilson County · the date of a scorecard event

    Before
    2026-09-21
    After
    2026-09-15
    Why
    The event's own sentence names the day of the act (September 15, 2026), September 15, 2026; the row carried the date of the report that carried it, September 21, 2026. Read again from the card line that wrote it.

  3194. · Colorado Springs · the date of a scorecard event

    Before
    2026-09-21
    After
    2026-09-17
    Why
    The event's own sentence names the day of the act (Thursday), September 17, 2026; the row carried the date of the report that carried it, September 21, 2026. Read again from the card line that wrote it.

  3195. · Nevada · the date of a scorecard event

    Before
    2026-09-21
    After
    2026-09-18
    Why
    The event's own sentence names the day of the act (September 18, 2026), September 18, 2026; the row carried the date of the report that carried it, September 21, 2026. Read again from the card line that wrote it.

  3196. · Texas · the date of a scorecard event

    Before
    2026-09-21
    After
    2026-09-18
    Why
    The event's own sentence names the day of the act (Friday), September 18, 2026; the row carried the date of the report that carried it, September 21, 2026. Read again from the card line that wrote it.

  3197. · Wyoming · the date of a scorecard event

    Before
    2026-09-20
    After
    2026-06-03
    Why
    The event's own sentence names the day of the act (June 3, 2026), June 3, 2026; the row carried the date of the report that carried it, September 20, 2026. Read again from the card line that wrote it.

  3198. · Nevada · the date of a scorecard event

    Before
    2026-09-20
    After
    2026-09-18
    Why
    The event's own sentence names the day of the act (Friday), September 18, 2026; the row carried the date of the report that carried it, September 20, 2026. Read again from the card line that wrote it.

  3199. · Morton County · the date of a scorecard event

    Before
    2026-09-19
    After
    2026-09-10
    Why
    The event's own sentence names the day of the act (September 10, 2026), September 10, 2026; the row carried the date of the report that carried it, September 19, 2026. Read again from the card line that wrote it.

  3200. · South Bend · the date of a scorecard event

    Before
    2026-09-20
    After
    2026-09-16
    Why
    The event's own sentence names the day of the act (September 16, 2026), September 16, 2026; the row carried the date of the report that carried it, September 20, 2026. Read again from the card line that wrote it.

  3201. · Kokomo · the date of a scorecard event

    Before
    2026-08-30
    After
    2026-08-24
    Why
    The event's own sentence names the day of the act (Aug. 24), August 24, 2026; the row carried the date of the report that carried it, August 30, 2026. Read again from the card line that wrote it.

  3202. · Wilmington · the date of a scorecard event

    Before
    2026-09-20
    After
    2026-09-19
    Why
    The event's own sentence names the day of the act (September 19, 2026), September 19, 2026; the row carried the date of the report that carried it, September 20, 2026. Read again from the card line that wrote it.

  3203. · Pennsylvania · the date of a scorecard event

    Before
    2026-08-24
    After
    2026-08-18
    Why
    The event's own sentence names the day of the act (August 18, 2026), August 18, 2026; the row carried the date of the report that carried it, August 24, 2026. Read again from the card line that wrote it.

  3204. · Carroll County · the date of a scorecard event

    Before
    2026-09-19
    After
    2026-09-14
    Why
    The event's own sentence names the day of the act (September 14), September 14, 2026; the row carried the date of the report that carried it, September 19, 2026. Read again from the card line that wrote it.

  3205. · Clovis · the date of a scorecard event

    Before
    2026-09-19
    After
    2026-09-17
    Why
    The event's own sentence names the day of the act (Thursday), September 17, 2026; the row carried the date of the report that carried it, September 19, 2026. Read again from the card line that wrote it.

  3206. · Wilmington · the date of a scorecard event

    Before
    2026-09-19
    After
    2026-09-03
    Why
    The event's own sentence names the day of the act (September 3, 2026), September 3, 2026; the row carried the date of the report that carried it, September 19, 2026. Read again from the card line that wrote it.

  3207. · Wyoming · the date of a scorecard event

    Before
    2026-09-18
    After
    2026-06-03
    Why
    The event's own sentence names the day of the act (June 3, 2026), June 3, 2026; the row carried the date of the report that carried it, September 18, 2026. Read again from the card line that wrote it.

  3208. · Ohio · the date of a scorecard event

    Before
    2026-09-19
    After
    2026-09-18
    Why
    The event's own sentence names the day of the act (September 18, 2026), September 18, 2026; the row carried the date of the report that carried it, September 19, 2026. Read again from the card line that wrote it.

  3209. · New Mexico · the date of a scorecard event

    Before
    2026-09-18
    After
    2026-09-17
    Why
    The event's own sentence names the day of the act (September 17), September 17, 2026; the row carried the date of the report that carried it, September 18, 2026. Read again from the card line that wrote it.

  3210. · Montgomery County · the date of a scorecard event

    Before
    2026-09-18
    After
    2026-09-15
    Why
    The event's own sentence names the day of the act (September 15, 2026), September 15, 2026; the row carried the date of the report that carried it, September 18, 2026. Read again from the card line that wrote it.

  3211. · Winchester · the date of a scorecard event

    Before
    2026-09-17
    After
    2026-09-16
    Why
    The event's own sentence names the day of the act (Wednesday night), September 16, 2026; the row carried the date of the report that carried it, September 17, 2026. Read again from the card line that wrote it.

  3212. · United States (federal) · the date of a scorecard event

    Before
    2026-09-19
    After
    2026-09-16
    Why
    The event's own sentence names the day of the act (September 16), September 16, 2026; the row carried the date of the report that carried it, September 19, 2026. Read again from the card line that wrote it.

  3213. · New York · the date of a scorecard event

    Before
    2026-09-19
    After
    2026-07-14
    Why
    The event's own sentence names the day of the act (July 14, 2026), July 14, 2026; the row carried the date of the report that carried it, September 19, 2026. Read again from the card line that wrote it.

  3214. · West Virginia · the date of a scorecard event

    Before
    2026-09-19
    After
    2026-09-14
    Why
    The event's own sentence names the day of the act (Sept. 14, 2026), September 14, 2026; the row carried the date of the report that carried it, September 19, 2026. Read again from the card line that wrote it.

  3215. · West Virginia · the date of a scorecard event

    Before
    2026-09-19
    After
    2026-09-03
    Why
    The event's own sentence names the day of the act (Sept. 3), September 3, 2026; the row carried the date of the report that carried it, September 19, 2026. Read again from the card line that wrote it.

  3216. · United States (federal) · the date of a scorecard event

    Before
    2026-09-18
    After
    2026-09-16
    Why
    The event's own sentence names the day of the act (Wednesday), September 16, 2026; the row carried the date of the report that carried it, September 18, 2026. Read again from the card line that wrote it.

  3217. · Colorado Springs · the date of a scorecard event

    Before
    2026-09-18
    After
    2026-09-17
    Why
    The event's own sentence names the day of the act (September 17, 2026), September 17, 2026; the row carried the date of the report that carried it, September 18, 2026. Read again from the card line that wrote it.

  3218. · Colorado Springs · the date of a scorecard event

    Before
    2026-09-18
    After
    2026-09-17
    Why
    The event's own sentence names the day of the act (September 17, 2026), September 17, 2026; the row carried the date of the report that carried it, September 18, 2026. Read again from the card line that wrote it.

  3219. · Massachusetts · the date of a scorecard event

    Before
    2026-09-18
    After
    2026-09-08
    Why
    The event's own sentence names the day of the act (September 8, 2026), September 8, 2026; the row carried the date of the report that carried it, September 18, 2026. Read again from the card line that wrote it.

  3220. · New York · the date of a scorecard event

    Before
    2026-09-18
    After
    2026-07-14
    Why
    The event's own sentence names the day of the act (July 14, 2026), July 14, 2026; the row carried the date of the report that carried it, September 18, 2026. Read again from the card line that wrote it.

  3221. · United States (federal) · the date of a scorecard event

    Before
    2026-09-18
    After
    2026-09-16
    Why
    The event's own sentence names the day of the act (September 16, 2026), September 16, 2026; the row carried the date of the report that carried it, September 18, 2026. Read again from the card line that wrote it.

  3222. · United States (federal) · the date of a scorecard event

    Before
    2026-09-18
    After
    2026-09-17
    Why
    The event's own sentence names the day of the act (September 17, 2026), September 17, 2026; the row carried the date of the report that carried it, September 18, 2026. Read again from the card line that wrote it.

  3223. · Greenwood County · the date of a scorecard event

    Before
    2026-09-18
    After
    2026-09-16
    Why
    The event's own sentence names the day of the act (September 16, 2026), September 16, 2026; the row carried the date of the report that carried it, September 18, 2026. Read again from the card line that wrote it.

  3224. · Colorado Springs · the date of a scorecard event

    Before
    2026-09-18
    After
    2026-09-17
    Why
    The event's own sentence names the day of the act (September 17, 2026), September 17, 2026; the row carried the date of the report that carried it, September 18, 2026. Read again from the card line that wrote it.

  3225. · New Mexico · the date of a scorecard event

    Before
    2026-09-18
    After
    2026-09-17
    Why
    The event's own sentence names the day of the act (Thursday), September 17, 2026; the row carried the date of the report that carried it, September 18, 2026. Read again from the card line that wrote it.

  3226. · Fort Pierce · the date of a scorecard event

    Before
    2026-09-18
    After
    2026-09-17
    Why
    The event's own sentence names the day of the act (September 17, 2026), September 17, 2026; the row carried the date of the report that carried it, September 18, 2026. Read again from the card line that wrote it.

  3227. · Alberta · the date of a scorecard event

    Before
    2026-08-28
    After
    2026-08-17
    Why
    The event's own sentence names the day of the act (August 17, 2026), August 17, 2026; the row carried the date of the report that carried it, August 28, 2026. Read again from the card line that wrote it.

  3228. · Virginia · the date of a scorecard event

    Before
    2026-09-18
    After
    2026-08-28
    Why
    The event's own sentence names the day of the act (August 28, 2026), August 28, 2026; the row carried the date of the report that carried it, September 18, 2026. Read again from the card line that wrote it.

  3229. · Troy · the date of a scorecard event

    Before
    2026-09-18
    After
    2026-09-10
    Why
    The event's own sentence names the day of the act (September 10), September 10, 2026; the row carried the date of the report that carried it, September 18, 2026. Read again from the card line that wrote it.

  3230. · United States (federal) · the date of a scorecard event

    Before
    2026-09-18
    After
    2026-09-17
    Why
    The event's own sentence names the day of the act (September 17, 2026), September 17, 2026; the row carried the date of the report that carried it, September 18, 2026. Read again from the card line that wrote it.

  3231. · United States (federal) · the date of a scorecard event

    Before
    2026-09-17
    After
    2026-09-16
    Why
    The event's own sentence names the day of the act (Wednesday), September 16, 2026; the row carried the date of the report that carried it, September 17, 2026. Read again from the card line that wrote it.

  3232. · Texas · the date of a scorecard event

    Before
    2026-09-17
    After
    2026-06-10
    Why
    The event's own sentence names the day of the act (June 10, 2026), June 10, 2026; the row carried the date of the report that carried it, September 17, 2026. Read again from the card line that wrote it.

  3233. · Wisconsin · the date of a scorecard event

    Before
    2026-09-17
    After
    2026-09-04
    Why
    The event's own sentence names the day of the act (September 4, 2026), September 4, 2026; the row carried the date of the report that carried it, September 17, 2026. Read again from the card line that wrote it.

  3234. · United States (federal) · the date of a scorecard event

    Before
    2026-09-17
    After
    2026-09-16
    Why
    The event's own sentence names the day of the act (September 16, 2026), September 16, 2026; the row carried the date of the report that carried it, September 17, 2026. Read again from the card line that wrote it.

  3235. · United States (federal) · the date of a scorecard event

    Before
    2026-09-17
    After
    2026-09-16
    Why
    The event's own sentence names the day of the act (Sept. 16), September 16, 2026; the row carried the date of the report that carried it, September 17, 2026. Read again from the card line that wrote it.

  3236. · Ypsilanti · the date of a scorecard event

    Before
    2026-09-17
    After
    2026-09-15
    Why
    The event's own sentence names the day of the act (Sept. 15), September 15, 2026; the row carried the date of the report that carried it, September 17, 2026. Read again from the card line that wrote it.

  3237. · Newark · the date of a scorecard event

    Before
    2026-09-17
    After
    2026-09-09
    Why
    The event's own sentence names the day of the act (September 9 2026), September 9, 2026; the row carried the date of the report that carried it, September 17, 2026. Read again from the card line that wrote it.

  3238. · South Dakota · the date of a scorecard event

    Before
    2026-08-26
    After
    2026-08-25
    Why
    The event's own sentence names the day of the act (August 25, 2026), August 25, 2026; the row carried the date of the report that carried it, August 26, 2026. Read again from the card line that wrote it.

  3239. · Cheyenne · the date of a scorecard event

    Before
    2026-09-16
    After
    2026-09-14
    Why
    The event's own sentence names the day of the act (Sept. 14), September 14, 2026; the row carried the date of the report that carried it, September 16, 2026. Read again from the card line that wrote it.

  3240. · New Hampshire · the date of a scorecard event

    Before
    2026-06-03
    After
    2026-05-05
    Why
    The event's own sentence names the day of the act (May 5), May 5, 2026; the row carried the date of the report that carried it, June 3, 2026. Read again from the card line that wrote it.

  3241. · Texas · the date of a scorecard event

    Before
    2026-09-17
    After
    2026-09-14
    Why
    The event's own sentence names the day of the act (September 14, 2026), September 14, 2026; the row carried the date of the report that carried it, September 17, 2026. Read again from the card line that wrote it.

  3242. · Missouri · the date of a scorecard event

    Before
    2026-09-17
    After
    2026-09-16
    Why
    The event's own sentence names the day of the act (Wednesday), September 16, 2026; the row carried the date of the report that carried it, September 17, 2026. Read again from the card line that wrote it.

  3243. · Van Buren Township · the date of a scorecard event

    Before
    2026-02-12
    After
    2026-02-11
    Why
    The event's own sentence names the day of the act (Wednesday night), February 11, 2026; the row carried the date of the report that carried it, February 12, 2026. Read again from the card line that wrote it.

  3244. · Massachusetts · the date of a scorecard event

    Before
    2026-09-16
    After
    2026-09-08
    Why
    The event's own sentence names the day of the act (September 8, 2026), September 8, 2026; the row carried the date of the report that carried it, September 16, 2026. Read again from the card line that wrote it.

  3245. · Linden · the date of a scorecard event

    Before
    2026-09-17
    After
    2026-09-14
    Why
    The event's own sentence names the day of the act (Monday night), September 14, 2026; the row carried the date of the report that carried it, September 17, 2026. Read again from the card line that wrote it.

  3246. · Sarasota County · the date of a scorecard event

    Before
    2026-07-09
    After
    2026-07-08
    Why
    The event's own sentence names the day of the act (July 8), July 8, 2026; the row carried the date of the report that carried it, July 9, 2026. Read again from the card line that wrote it.

  3247. · Rapid City · the date of a scorecard event

    Before
    2026-09-17
    After
    2026-09-10
    Why
    The event's own sentence names the day of the act (September 10), September 10, 2026; the row carried the date of the report that carried it, September 17, 2026. Read again from the card line that wrote it.

  3248. · Chelsea · the date of a scorecard event

    Before
    2026-08-17
    After
    2026-07-21
    Why
    The event's own sentence names the day of the act (July 21, 2026), July 21, 2026; the row carried the date of the report that carried it, August 17, 2026. Read again from the card line that wrote it.

  3249. · Westover · the date of a scorecard event

    Before
    2026-08-17
    After
    2026-08-06
    Why
    The event's own sentence names the day of the act (August 6, 2026), August 6, 2026; the row carried the date of the report that carried it, August 17, 2026. Read again from the card line that wrote it.

  3250. · Spartanburg County · the date of a scorecard event

    Before
    2026-07-21
    After
    2026-07-20
    Why
    The event's own sentence names the day of the act (July 20, 2026), July 20, 2026; the row carried the date of the report that carried it, July 21, 2026. Read again from the card line that wrote it.

  3251. · United States (federal) · the date of a scorecard event

    Before
    2026-09-17
    After
    2026-09-16
    Why
    The event's own sentence names the day of the act (September 16, 2026), September 16, 2026; the row carried the date of the report that carried it, September 17, 2026. Read again from the card line that wrote it.

  3252. · El Paso · the date of a scorecard event

    Before
    2026-09-15
    After
    2026-08-18
    Why
    The event's own sentence names the day of the act (August 18), August 18, 2026; the row carried the date of the report that carried it, September 15, 2026. Read again from the card line that wrote it.

  3253. · Wisconsin Rapids · the date of a scorecard event

    Before
    2026-09-17
    After
    2026-09-16
    Why
    The event's own sentence names the day of the act (September 16), September 16, 2026; the row carried the date of the report that carried it, September 17, 2026. Read again from the card line that wrote it.

  3254. · Missouri · the date of a scorecard event

    Before
    2026-09-17
    After
    2026-09-16
    Why
    The event's own sentence names the day of the act (Wednesday), September 16, 2026; the row carried the date of the report that carried it, September 17, 2026. Read again from the card line that wrote it.

  3255. · Killeen · the date of a scorecard event

    Before
    2026-09-16
    After
    2026-09-15
    Why
    The event's own sentence names the day of the act (Tuesday), September 15, 2026; the row carried the date of the report that carried it, September 16, 2026. Read again from the card line that wrote it.

  3256. · Salem · the date of a scorecard event

    Before
    2026-09-16
    After
    2026-09-15
    Why
    The event's own sentence names the day of the act (September 15, 2026), September 15, 2026; the row carried the date of the report that carried it, September 16, 2026. Read again from the card line that wrote it.

  3257. · Missouri · the date of a scorecard event

    Before
    2026-09-16
    After
    2026-09-14
    Why
    The event's own sentence names the day of the act (Sept. 14), September 14, 2026; the row carried the date of the report that carried it, September 16, 2026. Read again from the card line that wrote it.

  3258. · Arkansas · the date of a scorecard event

    Before
    2026-09-16
    After
    2026-09-15
    Why
    The event's own sentence names the day of the act (Tuesday), September 15, 2026; the row carried the date of the report that carried it, September 16, 2026. Read again from the card line that wrote it.

  3259. · Champaign County · the date of a scorecard event

    Before
    2026-09-01
    After
    2026-08-31
    Why
    The event's own sentence names the day of the act (August 31, 2026), August 31, 2026; the row carried the date of the report that carried it, September 1, 2026. Read again from the card line that wrote it.

  3260. · Bee County · the date of a scorecard event

    Before
    2026-09-16
    After
    2026-09-14
    Why
    The event's own sentence names the day of the act (September 14), September 14, 2026; the row carried the date of the report that carried it, September 16, 2026. Read again from the card line that wrote it.

  3261. · Otter Tail County · the date of a scorecard event

    Before
    2026-09-16
    After
    2026-09-08
    Why
    The event's own sentence names the day of the act (September 8), September 8, 2026; the row carried the date of the report that carried it, September 16, 2026. Read again from the card line that wrote it.

  3262. · Gallatin · the date of a scorecard event

    Before
    2026-09-16
    After
    2026-09-15
    Why
    The event's own sentence names the day of the act (September 15), September 15, 2026; the row carried the date of the report that carried it, September 16, 2026. Read again from the card line that wrote it.

  3263. · Sioux County · the date of a scorecard event

    Before
    2026-09-16
    After
    2026-06-16
    Why
    The event's own sentence names the day of the act (June 16), June 16, 2026; the row carried the date of the report that carried it, September 16, 2026. Read again from the card line that wrote it.

  3264. · Arkansas · the date of a scorecard event

    Before
    2026-09-16
    After
    2026-09-15
    Why
    The event's own sentence names the day of the act (September 15, 2026), September 15, 2026; the row carried the date of the report that carried it, September 16, 2026. Read again from the card line that wrote it.

  3265. · Bridgewater Township · the date of a scorecard event

    Before
    2026-09-16
    After
    2026-09-03
    Why
    The event's own sentence names the day of the act (September 3), September 3, 2026; the row carried the date of the report that carried it, September 16, 2026. Read again from the card line that wrote it.

  3266. · Juab County · the date of a scorecard event

    Before
    2026-09-16
    After
    2026-09-15
    Why
    The event's own sentence names the day of the act (Tuesday), September 15, 2026; the row carried the date of the report that carried it, September 16, 2026. Read again from the card line that wrote it.

  3267. · Pima County · the date of a scorecard event

    Before
    2026-09-04
    After
    2026-08-12
    Why
    The event's own sentence names the day of the act (August 12), August 12, 2026; the row carried the date of the report that carried it, September 4, 2026. Read again from the card line that wrote it.

  3268. · Byron · the date of a scorecard event

    Before
    2026-09-15
    After
    2026-09-14
    Why
    The event's own sentence names the day of the act (Monday), September 14, 2026; the row carried the date of the report that carried it, September 15, 2026. Read again from the card line that wrote it.

  3269. · Martin County · the date of a scorecard event

    Before
    2026-09-16
    After
    2026-09-15
    Why
    The event's own sentence names the day of the act (September 15, 2026), September 15, 2026; the row carried the date of the report that carried it, September 16, 2026. Read again from the card line that wrote it.

  3270. · Scott County · the date of a scorecard event

    Before
    2026-09-15
    After
    2026-09-14
    Why
    The event's own sentence names the day of the act (September 14, 2026), September 14, 2026; the row carried the date of the report that carried it, September 15, 2026. Read again from the card line that wrote it.

  3271. · Wilmington · the date of a scorecard event

    Before
    2026-09-15
    After
    2026-09-03
    Why
    The event's own sentence names the day of the act (September 3), September 3, 2026; the row carried the date of the report that carried it, September 15, 2026. Read again from the card line that wrote it.

  3272. · Kansas · the date of a scorecard event

    Before
    2026-08-30
    After
    2026-08-20
    Why
    The event's own sentence names the day of the act (August 20), August 20, 2026; the row carried the date of the report that carried it, August 30, 2026. Read again from the card line that wrote it.

  3273. · Uinta County · the date of a scorecard event

    Before
    2026-08-25
    After
    2026-08-17
    Why
    The event's own sentence names the day of the act (August 17), August 17, 2026; the row carried the date of the report that carried it, August 25, 2026. Read again from the card line that wrote it.

  3274. · Uinta County · the date of a scorecard event

    Before
    2026-08-25
    After
    2026-07-16
    Why
    The event's own sentence names the day of the act (July 16), July 16, 2026; the row carried the date of the report that carried it, August 25, 2026. Read again from the card line that wrote it.

  3275. · Uinta County · the date of a scorecard event

    Before
    2026-08-31
    After
    2026-08-17
    Why
    The event's own sentence names the day of the act (August 17, 2026), August 17, 2026; the row carried the date of the report that carried it, August 31, 2026. Read again from the card line that wrote it.

  3276. · Michigan · the date of a scorecard event

    Before
    2026-09-14
    After
    2026-09-09
    Why
    The event's own sentence names the day of the act (September 9), September 9, 2026; the row carried the date of the report that carried it, September 14, 2026. Read again from the card line that wrote it.

  3277. · Stokes County · the date of a scorecard event

    Before
    2026-09-15
    After
    2026-09-14
    Why
    The event's own sentence names the day of the act (September 14), September 14, 2026; the row carried the date of the report that carried it, September 15, 2026. Read again from the card line that wrote it.

  3278. · Texas · the date of a scorecard event

    Before
    2026-09-14
    After
    2026-08-03
    Why
    The event's own sentence names the day of the act (August 3), August 3, 2026; the row carried the date of the report that carried it, September 14, 2026. Read again from the card line that wrote it.

  3279. · El Paso · the date of a scorecard event

    Before
    2026-09-15
    After
    2026-06-23
    Why
    The event's own sentence names the day of the act (June 23), June 23, 2026; the row carried the date of the report that carried it, September 15, 2026. Read again from the card line that wrote it.

  3280. · Chesapeake · the date of a scorecard event

    Before
    2026-08-25
    After
    2026-08-18
    Why
    The event's own sentence names the day of the act (August 18), August 18, 2026; the row carried the date of the report that carried it, August 25, 2026. Read again from the card line that wrote it.

  3281. · Ypsilanti Township · the date of a scorecard event

    Before
    2026-09-14
    After
    2026-08-18
    Why
    The event's own sentence names the day of the act (August 18), August 18, 2026; the row carried the date of the report that carried it, September 14, 2026. Read again from the card line that wrote it.

  3282. · Ypsilanti Township · the date of a scorecard event

    Before
    2026-09-14
    After
    2026-08-08
    Why
    The event's own sentence names the day of the act (August 8), August 8, 2026; the row carried the date of the report that carried it, September 14, 2026. Read again from the card line that wrote it.

  3283. · Oregon · the date of a scorecard event

    Before
    2026-09-14
    After
    2026-09-10
    Why
    The event's own sentence names the day of the act (September 10, 2026), September 10, 2026; the row carried the date of the report that carried it, September 14, 2026. Read again from the card line that wrote it.

  3284. · Ohio · the date of a scorecard event

    Before
    2026-09-14
    After
    2026-09-04
    Why
    The event's own sentence names the day of the act (September 4), September 4, 2026; the row carried the date of the report that carried it, September 14, 2026. Read again from the card line that wrote it.

  3285. · St. Louis · the date of a scorecard event

    Before
    2026-09-14
    After
    2026-09-11
    Why
    The event's own sentence names the day of the act (Friday), September 11, 2026; the row carried the date of the report that carried it, September 14, 2026. Read again from the card line that wrote it.

  3286. · Florida · the date of a scorecard event

    Before
    2026-09-14
    After
    2026-05-08
    Why
    The event's own sentence names the day of the act (May 8), May 8, 2026; the row carried the date of the report that carried it, September 14, 2026. Read again from the card line that wrote it.

  3287. · Palmetto · the date of a scorecard event

    Before
    2026-09-14
    After
    2026-08-03
    Why
    The event's own sentence names the day of the act (Aug. 3), August 3, 2026; the row carried the date of the report that carried it, September 14, 2026. Read again from the card line that wrote it.

  3288. · Kentucky · the date of a scorecard event

    Before
    2026-09-11
    After
    2026-08-06
    Why
    The event's own sentence names the day of the act (August 6), August 6, 2026; the row carried the date of the report that carried it, September 11, 2026. Read again from the card line that wrote it.

  3289. · Maine · the date of a scorecard event

    Before
    2026-09-14
    After
    2026-08-27
    Why
    The event's own sentence names the day of the act (August 27, 2026), August 27, 2026; the row carried the date of the report that carried it, September 14, 2026. Read again from the card line that wrote it.

  3290. · Pennsylvania · the date of a scorecard event

    Before
    2026-09-13
    After
    2026-09-09
    Why
    The event's own sentence names the day of the act (Wednesday), September 9, 2026; the row carried the date of the report that carried it, September 13, 2026. Read again from the card line that wrote it.

  3291. · Anniston · the date of a scorecard event

    Before
    2026-08-26
    After
    2026-08-18
    Why
    The event's own sentence names the day of the act (August 18, 2026), August 18, 2026; the row carried the date of the report that carried it, August 26, 2026. Read again from the card line that wrote it.

  3292. · Pinal County · the date of a scorecard event

    Before
    2026-08-27
    After
    2026-08-26
    Why
    The event's own sentence names the day of the act (August 26, 2026), August 26, 2026; the row carried the date of the report that carried it, August 27, 2026. Read again from the card line that wrote it.

  3293. · Desloge · the date of a scorecard event

    Before
    2026-09-10
    After
    2026-09-09
    Why
    The event's own sentence names the day of the act (September 9, 2026), September 9, 2026; the row carried the date of the report that carried it, September 10, 2026. Read again from the card line that wrote it.

  3294. · Sturgeon County · the date of a scorecard event

    Before
    2026-09-12
    After
    2026-09-08
    Why
    The event's own sentence names the day of the act (September 8), September 8, 2026; the row carried the date of the report that carried it, September 12, 2026. Read again from the card line that wrote it.

  3295. · Quebec · the date of a scorecard event

    Before
    2026-09-02
    After
    2026-07-07
    Why
    The event's own sentence names the day of the act (July 7), July 7, 2026; the row carried the date of the report that carried it, September 2, 2026. Read again from the card line that wrote it.

  3296. · St. Louis · the date of a scorecard event

    Before
    2026-09-12
    After
    2026-09-11
    Why
    The event's own sentence names the day of the act (September 11, 2026), September 11, 2026; the row carried the date of the report that carried it, September 12, 2026. Read again from the card line that wrote it.

  3297. · Rhode Island · the date of a scorecard event

    Before
    2026-09-12
    After
    2026-03-04
    Why
    The event's own sentence names the day of the act (March 4), March 4, 2026; the row carried the date of the report that carried it, September 12, 2026. Read again from the card line that wrote it.

  3298. · Nevada · the date of a scorecard event

    Before
    2026-09-03
    After
    2026-09-01
    Why
    The event's own sentence names the day of the act (September 1, 2026), September 1, 2026; the row carried the date of the report that carried it, September 3, 2026. Read again from the card line that wrote it.

  3299. · Alberta · the date of a scorecard event

    Before
    2026-09-11
    After
    2026-09-10
    Why
    The event's own sentence names the day of the act (September 10), September 10, 2026; the row carried the date of the report that carried it, September 11, 2026. Read again from the card line that wrote it.

  3300. · New Mexico · the date of a scorecard event

    Before
    2026-09-11
    After
    2026-08-23
    Why
    The event's own sentence names the day of the act (August 23), August 23, 2026; the row carried the date of the report that carried it, September 11, 2026. Read again from the card line that wrote it.

  3301. · Weld County · the date of a scorecard event

    Before
    2026-09-11
    After
    2026-09-09
    Why
    The event's own sentence names the day of the act (Sept. 9), September 9, 2026; the row carried the date of the report that carried it, September 11, 2026. Read again from the card line that wrote it.

  3302. · Weld County · the date of a scorecard event

    Before
    2026-09-11
    After
    2026-09-09
    Why
    The event's own sentence names the day of the act (September 9), September 9, 2026; the row carried the date of the report that carried it, September 11, 2026. Read again from the card line that wrote it.

  3303. · Edgerton · the date of a scorecard event

    Before
    2026-09-10
    After
    2026-07-23
    Why
    The event's own sentence names the day of the act (July 23), July 23, 2026; the row carried the date of the report that carried it, September 10, 2026. Read again from the card line that wrote it.

  3304. · Edgerton · the date of a scorecard event

    Before
    2026-09-10
    After
    2026-09-03
    Why
    The event's own sentence names the day of the act (Sept. 3), September 3, 2026; the row carried the date of the report that carried it, September 10, 2026. Read again from the card line that wrote it.

  3305. · Ypsilanti Township · the date of a scorecard event

    Before
    2026-09-11
    After
    2026-01-29
    Why
    The event's own sentence names the day of the act (January 29), January 29, 2026; the row carried the date of the report that carried it, September 11, 2026. Read again from the card line that wrote it.

  3306. · Ypsilanti Township · the date of a scorecard event

    Before
    2026-09-11
    After
    2026-09-09
    Why
    The event's own sentence names the day of the act (Wednesday), September 9, 2026; the row carried the date of the report that carried it, September 11, 2026. Read again from the card line that wrote it.

  3307. · Colorado · the date of a scorecard event

    Before
    2026-08-24
    After
    2026-08-06
    Why
    The event's own sentence names the day of the act (August 6, 2026), August 6, 2026; the row carried the date of the report that carried it, August 24, 2026. Read again from the card line that wrote it.

  3308. · Edgerton · the date of a scorecard event

    Before
    2026-09-10
    After
    2026-07-23
    Why
    The event's own sentence names the day of the act (July 23), July 23, 2026; the row carried the date of the report that carried it, September 10, 2026. Read again from the card line that wrote it.

  3309. · Edgerton · the date of a scorecard event

    Before
    2026-09-10
    After
    2026-08-04
    Why
    The event's own sentence names the day of the act (Aug. 4), August 4, 2026; the row carried the date of the report that carried it, September 10, 2026. Read again from the card line that wrote it.

  3310. · Kansas · the date of a scorecard event

    Before
    2026-09-10
    After
    2026-09-03
    Why
    The event's own sentence names the day of the act (Sept. 3), September 3, 2026; the row carried the date of the report that carried it, September 10, 2026. Read again from the card line that wrote it.

  3311. · Ypsilanti Township · the date of a scorecard event

    Before
    2026-09-10
    After
    2026-09-09
    Why
    The event's own sentence names the day of the act (September 9, 2026), September 9, 2026; the row carried the date of the report that carried it, September 10, 2026. Read again from the card line that wrote it.

  3312. · Ypsilanti Township · the date of a scorecard event

    Before
    2026-09-10
    After
    2026-09-09
    Why
    The event's own sentence names the day of the act (September 9, 2026), September 9, 2026; the row carried the date of the report that carried it, September 10, 2026. Read again from the card line that wrote it.

  3313. · Pennsylvania · the date of a scorecard event

    Before
    2026-09-03
    After
    2026-08-18
    Why
    The event's own sentence names the day of the act (August 18, 2026), August 18, 2026; the row carried the date of the report that carried it, September 3, 2026. Read again from the card line that wrote it.

  3314. · Saskatchewan · the date of a scorecard event

    Before
    2026-09-10
    After
    2026-09-09
    Why
    The event's own sentence names the day of the act (Wednesday night), September 9, 2026; the row carried the date of the report that carried it, September 10, 2026. Read again from the card line that wrote it.

  3315. · Tarrant County · the date of a scorecard event

    Before
    2026-09-10
    After
    2026-09-08
    Why
    The event's own sentence names the day of the act (Tuesday), September 8, 2026; the row carried the date of the report that carried it, September 10, 2026. Read again from the card line that wrote it.

  3316. · Spartanburg County · the date of a scorecard event

    Before
    2026-09-10
    After
    2026-07-06
    Why
    The event's own sentence names the day of the act (July 6, 2026), July 6, 2026; the row carried the date of the report that carried it, September 10, 2026. Read again from the card line that wrote it.

  3317. · Massachusetts · the date of a scorecard event

    Before
    2026-09-10
    After
    2026-09-08
    Why
    The event's own sentence names the day of the act (September 8 2026), September 8, 2026; the row carried the date of the report that carried it, September 10, 2026. Read again from the card line that wrote it.

  3318. · Kearney · the date of a scorecard event

    Before
    2026-09-09
    After
    2026-09-08
    Why
    The event's own sentence names the day of the act (September 8, 2026), September 8, 2026; the row carried the date of the report that carried it, September 9, 2026. Read again from the card line that wrote it.

  3319. · North Dakota · the date of a scorecard event

    Before
    2026-09-08
    After
    2026-08-31
    Why
    The event's own sentence names the day of the act (August 31), August 31, 2026; the row carried the date of the report that carried it, September 8, 2026. Read again from the card line that wrote it.

  3320. · Hopkinton · the date of a scorecard event

    Before
    2026-08-17
    After
    2026-07-06
    Why
    The event's own sentence names the day of the act (July 6), July 6, 2026; the row carried the date of the report that carried it, August 17, 2026. Read again from the card line that wrote it.

  3321. · Smithfield · the date of a scorecard event

    Before
    2026-08-17
    After
    2026-05-05
    Why
    The event's own sentence names the day of the act (May 5), May 5, 2026; the row carried the date of the report that carried it, August 17, 2026. Read again from the card line that wrote it.

  3322. · Grayslake · the date of a scorecard event

    Before
    2026-08-30
    After
    2026-08-19
    Why
    The event's own sentence names the day of the act (August 19), August 19, 2026; the row carried the date of the report that carried it, August 30, 2026. Read again from the card line that wrote it.

  3323. · Lubbock · the date of a scorecard event

    Before
    2026-09-09
    After
    2026-09-08
    Why
    The event's own sentence names the day of the act (Tuesday), September 8, 2026; the row carried the date of the report that carried it, September 9, 2026. Read again from the card line that wrote it.

  3324. · Desloge · the date of a scorecard event

    Before
    2026-08-27
    After
    2026-08-10
    Why
    The event's own sentence names the day of the act (August 10), August 10, 2026; the row carried the date of the report that carried it, August 27, 2026. Read again from the card line that wrote it.

  3325. · Massachusetts · the date of a scorecard event

    Before
    2026-09-09
    After
    2026-06-25
    Why
    The event's own sentence names the day of the act (June 25), June 25, 2026; the row carried the date of the report that carried it, September 9, 2026. Read again from the card line that wrote it.

  3326. · Massachusetts · the date of a scorecard event

    Before
    2026-09-10
    After
    2026-06-25
    Why
    The event's own sentence names the day of the act (June 25), June 25, 2026; the row carried the date of the report that carried it, September 10, 2026. Read again from the card line that wrote it.

  3327. · Massachusetts · the date of a scorecard event

    Before
    2026-09-09
    After
    2026-09-08
    Why
    The event's own sentence names the day of the act (September 8), September 8, 2026; the row carried the date of the report that carried it, September 9, 2026. Read again from the card line that wrote it.

  3328. · Lake County · the date of a scorecard event

    Before
    2026-08-25
    After
    2026-06-09
    Why
    The event's own sentence names the day of the act (June 9, 2026), June 9, 2026; the row carried the date of the report that carried it, August 25, 2026. Read again from the card line that wrote it.

  3329. · Lake County · the date of a scorecard event

    Before
    2026-08-25
    After
    2026-08-18
    Why
    The event's own sentence names the day of the act (August 18, 2026), August 18, 2026; the row carried the date of the report that carried it, August 25, 2026. Read again from the card line that wrote it.

  3330. · Wisconsin Rapids · the date of a scorecard event

    Before
    2026-09-09
    After
    2026-08-10
    Why
    The event's own sentence names the day of the act (August 10, 2026), August 10, 2026; the row carried the date of the report that carried it, September 9, 2026. Read again from the card line that wrote it.

  3331. · United States (federal) · the date of a scorecard event

    Before
    2026-09-09
    After
    2026-09-01
    Why
    The event's own sentence names the day of the act (September 1, 2026), September 1, 2026; the row carried the date of the report that carried it, September 9, 2026. Read again from the card line that wrote it.

  3332. · Baltimore County · the date of a scorecard event

    Before
    2026-09-04
    After
    2026-09-03
    Why
    The event's own sentence names the day of the act (September 3, 2026), September 3, 2026; the row carried the date of the report that carried it, September 4, 2026. Read again from the card line that wrote it.

  3333. · North Dakota · the date of a scorecard event

    Before
    2026-09-09
    After
    2026-08-31
    Why
    The event's own sentence names the day of the act (August 31 2026), August 31, 2026; the row carried the date of the report that carried it, September 9, 2026. Read again from the card line that wrote it.

  3334. · Kentucky · the date of a scorecard event

    Before
    2026-09-09
    After
    2026-08-06
    Why
    The event's own sentence names the day of the act (Aug. 6), August 6, 2026; the row carried the date of the report that carried it, September 9, 2026. Read again from the card line that wrote it.

  3335. · Manchester · the date of a scorecard event

    Before
    2026-09-09
    After
    2026-08-24
    Why
    The event's own sentence names the day of the act (August 24, 2026), August 24, 2026; the row carried the date of the report that carried it, September 9, 2026. Read again from the card line that wrote it.

  3336. · North Dakota · the date of a scorecard event

    Before
    2026-09-01
    After
    2026-08-31
    Why
    The event's own sentence names the day of the act (Monday), August 31, 2026; the row carried the date of the report that carried it, September 1, 2026. Read again from the card line that wrote it.

  3337. · Lincoln County · the date of a scorecard event

    Before
    2026-08-26
    After
    2026-08-25
    Why
    The event's own sentence names the day of the act (August 25, 2026), August 25, 2026; the row carried the date of the report that carried it, August 26, 2026. Read again from the card line that wrote it.

  3338. · Natrona County · the date of a scorecard event

    Before
    2026-09-02
    After
    2026-09-01
    Why
    The event's own sentence names the day of the act (Tuesday), September 1, 2026; the row carried the date of the report that carried it, September 2, 2026. Read again from the card line that wrote it.

  3339. · Keller · the date of a scorecard event

    Before
    2026-08-27
    After
    2026-08-12
    Why
    The event's own sentence names the day of the act (August 12), August 12, 2026; the row carried the date of the report that carried it, August 27, 2026. Read again from the card line that wrote it.

  3340. · Westlake · the date of a scorecard event

    Before
    2026-08-27
    After
    2026-08-19
    Why
    The event's own sentence names the day of the act (August 19), August 19, 2026; the row carried the date of the report that carried it, August 27, 2026. Read again from the card line that wrote it.

  3341. · Cheyenne · the date of a scorecard event

    Before
    2026-09-09
    After
    2026-09-08
    Why
    The event's own sentence names the day of the act (Tuesday), September 8, 2026; the row carried the date of the report that carried it, September 9, 2026. Read again from the card line that wrote it.

  3342. · Richmond · the date of a scorecard event

    Before
    2026-08-19
    After
    2026-08-18
    Why
    The event's own sentence names the day of the act (August 18, 2026), August 18, 2026; the row carried the date of the report that carried it, August 19, 2026. Read again from the card line that wrote it.

  3343. · Fayetteville · the date of a scorecard event

    Before
    2026-08-19
    After
    2026-06-16
    Why
    The event's own sentence names the day of the act (June 16), June 16, 2026; the row carried the date of the report that carried it, August 19, 2026. Read again from the card line that wrote it.

  3344. · Salem · the date of a scorecard event

    Before
    2026-09-08
    After
    2026-07-27
    Why
    The event's own sentence names the day of the act (July 27, 2026), July 27, 2026; the row carried the date of the report that carried it, September 8, 2026. Read again from the card line that wrote it.

  3345. · Bridgewater Township · the date of a scorecard event

    Before
    2026-09-08
    After
    2026-09-02
    Why
    The event's own sentence names the day of the act (September 2, 2026), September 2, 2026; the row carried the date of the report that carried it, September 8, 2026. Read again from the card line that wrote it.

  3346. · New Mexico · the date of a scorecard event

    Before
    2026-08-23
    After
    2026-08-18
    Why
    The event's own sentence names the day of the act (August 18, 2026), August 18, 2026; the row carried the date of the report that carried it, August 23, 2026. Read again from the card line that wrote it.

  3347. · Montville · the date of a scorecard event

    Before
    2026-09-08
    After
    2026-08-27
    Why
    The event's own sentence names the day of the act (August 27), August 27, 2026; the row carried the date of the report that carried it, September 8, 2026. Read again from the card line that wrote it.

  3348. · Pataskala · the date of a scorecard event

    Before
    2026-08-23
    After
    2026-06-03
    Why
    The event's own sentence names the day of the act (June 3), June 3, 2026; the row carried the date of the report that carried it, August 23, 2026. Read again from the card line that wrote it.

  3349. · Floyd County · the date of a scorecard event

    Before
    2026-09-07
    After
    2026-06-09
    Why
    The event's own sentence names the day of the act (June 9, 2026), June 9, 2026; the row carried the date of the report that carried it, September 7, 2026. Read again from the card line that wrote it.

  3350. · Floyd County · the date of a scorecard event

    Before
    2026-09-07
    After
    2026-08-25
    Why
    The event's own sentence names the day of the act (August 25, 2026), August 25, 2026; the row carried the date of the report that carried it, September 7, 2026. Read again from the card line that wrote it.

  3351. · Anniston · the date of a scorecard event

    Before
    2026-09-07
    After
    2026-08-18
    Why
    The event's own sentence names the day of the act (August 18, 2026), August 18, 2026; the row carried the date of the report that carried it, September 7, 2026. Read again from the card line that wrote it.

  3352. · Gibraltar · the date of a scorecard event

    Before
    2026-08-20
    After
    2026-08-17
    Why
    The event's own sentence names the day of the act (August 17, 2026), August 17, 2026; the row carried the date of the report that carried it, August 20, 2026. Read again from the card line that wrote it.

  3353. · Hillsboro · the date of a scorecard event

    Before
    2026-08-19
    After
    2026-07-27
    Why
    The event's own sentence names the day of the act (July 27), July 27, 2026; the row carried the date of the report that carried it, August 19, 2026. Read again from the card line that wrote it.

  3354. · Trenton · the date of a scorecard event

    Before
    2026-09-07
    After
    2026-09-01
    Why
    The event's own sentence names the day of the act (Sept. 1), September 1, 2026; the row carried the date of the report that carried it, September 7, 2026. Read again from the card line that wrote it.

  3355. · Pennsylvania · the date of a scorecard event

    Before
    2026-08-19
    After
    2026-08-18
    Why
    The event's own sentence names the day of the act (Tuesday), August 18, 2026; the row carried the date of the report that carried it, August 19, 2026. Read again from the card line that wrote it.

  3356. · Louisiana · the date of a scorecard event

    Before
    2026-08-10
    After
    2026-08-04
    Why
    The event's own sentence names the day of the act (August 4, 2026), August 4, 2026; the row carried the date of the report that carried it, August 10, 2026. Read again from the card line that wrote it.

  3357. · Gibraltar · the date of a scorecard event

    Before
    2026-08-21
    After
    2026-03-09
    Why
    The event's own sentence names the day of the act (March 9, 2026), March 9, 2026; the row carried the date of the report that carried it, August 21, 2026. Read again from the card line that wrote it.

  3358. · North Dakota · the date of a scorecard event

    Before
    2026-09-01
    After
    2026-08-31
    Why
    The event's own sentence names the day of the act (Monday), August 31, 2026; the row carried the date of the report that carried it, September 1, 2026. Read again from the card line that wrote it.

  3359. · RM of Sherwood · the date of a scorecard event

    Before
    2026-08-21
    After
    2026-04-20
    Why
    The event's own sentence names the day of the act (April 20, 2026), April 20, 2026; the row carried the date of the report that carried it, August 21, 2026. Read again from the card line that wrote it.

  3360. · Pima County · the date of a scorecard event

    Before
    2026-09-07
    After
    2026-08-26
    Why
    The event's own sentence names the day of the act (Aug. 26), August 26, 2026; the row carried the date of the report that carried it, September 7, 2026. Read again from the card line that wrote it.

  3361. · Pima County · the date of a scorecard event

    Before
    2026-09-07
    After
    2026-08-11
    Why
    The event's own sentence names the day of the act (Aug. 11), August 11, 2026; the row carried the date of the report that carried it, September 7, 2026. Read again from the card line that wrote it.

  3362. · Mesa · the date of a scorecard event

    Before
    2025-07-16
    After
    2025-07-08
    Why
    The event's own sentence names the day of the act (July 8, 2025), July 8, 2025; the row carried the date of the report that carried it, July 16, 2025. Read again from the card line that wrote it.

  3363. · Marshall · the date of a scorecard event

    Before
    2026-08-13
    After
    2026-08-03
    Why
    The event's own sentence names the day of the act (August 3), August 3, 2026; the row carried the date of the report that carried it, August 13, 2026. Read again from the card line that wrote it.

  3364. · Marshall · the date of a scorecard event

    Before
    2026-08-13
    After
    2026-08-12
    Why
    The event's own sentence names the day of the act (Wednesday), August 12, 2026; the row carried the date of the report that carried it, August 13, 2026. Read again from the card line that wrote it.

  3365. · New Jersey · the date of a scorecard event

    Before
    2026-08-28
    After
    2026-06-30
    Why
    The event's own sentence names the day of the act (June 30, 2026), June 30, 2026; the row carried the date of the report that carried it, August 28, 2026. Read again from the card line that wrote it.

  3366. · New Jersey · the date of a scorecard event

    Before
    2026-08-28
    After
    2026-08-27
    Why
    The event's own sentence names the day of the act (August 27, 2026), August 27, 2026; the row carried the date of the report that carried it, August 28, 2026. Read again from the card line that wrote it.

  3367. · Bridgewater Township · the date of a scorecard event

    Before
    2026-08-25
    After
    2026-08-20
    Why
    The event's own sentence names the day of the act (August 20, 2026), August 20, 2026; the row carried the date of the report that carried it, August 25, 2026. Read again from the card line that wrote it.

  3368. · Williston · the date of a scorecard event

    Before
    2026-09-02
    After
    2025-03-25
    Why
    The event's own sentence names the day of the act (March 25, 2025), March 25, 2025; the row carried the date of the report that carried it, September 2, 2026. Read again from the card line that wrote it.

  3369. · Alberta · the date of a scorecard event

    Before
    2026-09-02
    After
    2026-08-27
    Why
    The event's own sentence names the day of the act (August 27), August 27, 2026; the row carried the date of the report that carried it, September 2, 2026. Read again from the card line that wrote it.

  3370. · Salem · the date of a scorecard event

    Before
    2026-08-21
    After
    2026-07-30
    Why
    The event's own sentence names the day of the act (July 30), July 30, 2026; the row carried the date of the report that carried it, August 21, 2026. Read again from the card line that wrote it.

  3371. · Austin · the date of a scorecard event

    Before
    2026-09-07
    After
    2026-09-02
    Why
    The event's own sentence names the day of the act (September 2, 2026), September 2, 2026; the row carried the date of the report that carried it, September 7, 2026. Read again from the card line that wrote it.

  3372. · Louisiana · the date of a scorecard event

    Before
    2026-08-11
    After
    2025-08-20
    Why
    The event's own sentence names the day of the act (August 20, 2025), August 20, 2025; the row carried the date of the report that carried it, August 11, 2026. Read again from the card line that wrote it.

  3373. · Arkansas · the date of a scorecard event

    Before
    2026-09-03
    After
    2026-09-02
    Why
    The event's own sentence names the day of the act (Wednesday), September 2, 2026; the row carried the date of the report that carried it, September 3, 2026. Read again from the card line that wrote it.

  3374. · Port Washington · the date of a scorecard event

    Before
    2026-03-20
    After
    2026-03-19
    Why
    The event's own sentence names the day of the act (Thursday), March 19, 2026; the row carried the date of the report that carried it, March 20, 2026. Read again from the card line that wrote it.

  3375. · Wisconsin · the date of a scorecard event

    Before
    2026-08-07
    After
    2026-08-06
    Why
    The event's own sentence names the day of the act (Thursday), August 6, 2026; the row carried the date of the report that carried it, August 7, 2026. Read again from the card line that wrote it.

  3376. · Effingham County · the date of a scorecard event

    Before
    2026-09-03
    After
    2026-09-02
    Why
    The event's own sentence names the day of the act (September 2), September 2, 2026; the row carried the date of the report that carried it, September 3, 2026. Read again from the card line that wrote it.

  3377. · Gibraltar · the date of a scorecard event

    Before
    2026-08-24
    After
    2026-03-09
    Why
    The event's own sentence names the day of the act (March 9, 2026), March 9, 2026; the row carried the date of the report that carried it, August 24, 2026. Read again from the card line that wrote it.

  3378. · Marshall · the date of a scorecard event

    Before
    2026-08-31
    After
    2026-08-03
    Why
    The event's own sentence names the day of the act (Aug. 3), August 3, 2026; the row carried the date of the report that carried it, August 31, 2026. Read again from the card line that wrote it.

  3379. · Richland Parish · the date of a scorecard event

    Before
    2026-08-10
    After
    2026-08-04
    Why
    The event's own sentence names the day of the act (August 4, 2026), August 4, 2026; the row carried the date of the report that carried it, August 10, 2026. Read again from the card line that wrote it.

  3380. · United States (federal) · the date of a scorecard event

    Before
    2026-08-17
    After
    2026-08-13
    Why
    The event's own sentence names the day of the act (August 13, 2026), August 13, 2026; the row carried the date of the report that carried it, August 17, 2026. Read again from the card line that wrote it.

  3381. · United States (federal) · the date of a scorecard event

    Before
    2026-08-26
    After
    2026-07-31
    Why
    The event's own sentence names the day of the act (July 31), July 31, 2026; the row carried the date of the report that carried it, August 26, 2026. Read again from the card line that wrote it.

  3382. · United States (federal) · the date of a scorecard event

    Before
    2026-08-28
    After
    2026-08-26
    Why
    The event's own sentence names the day of the act (August 26, 2026), August 26, 2026; the row carried the date of the report that carried it, August 28, 2026. Read again from the card line that wrote it.

  3383. · the date of 64 timeline entries and scorecard events

    Before
    The first of the month, printed as though it were the day: February 1, 2026.
    After
    The month alone: February 2026. The stored date is still the first of the month.
    Why
    64 timeline entries and scorecard events are dated the first of a month because their own sentence names the month and not the day, such as "in February 2026", which is the record's rule for a source that gives only the month. Every page and export printed that first as though it were the day. They now print the month alone, because the sentence names no day. No date and no word of any row changed. 11 of the 64 are published and 53 are drafts, which print the same way once published.

  3384. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    S&P Global Market Intelligence's 451 Research article of March 2026 could not be read by the record: spglobal.com answered the reader with HTTP 403 from a runner and the Internet Archive holds no capture, so the figure was never read from its source (card 15511, the homepage power and water batch of 2026-09-22), and the bulk approve of 2026-09-25 published it. A reference figure needs a source the record read: returned to draft, off every page, until a readable source that quotes it is cited (docs/batch-unread-figures-0929.md).

  3385. · Yellowstone County data center (eyeing) · the publication of a figure

    Before
    published
    After
    draft
    Why
    The record could not read this figure's source: the page answered with no article text, so none reached the classifier, which scored card 12506 from the headline alone, and the number came from the headline; published by the bulk approve of 2026-09-25. A reference figure needs a source the record read: returned to draft, off every page, until a readable source that states it is cited (docs/batch-unread-figures-0929.md).

  3386. · pennsylvania-energy-and-data-innovation-campus-pa · the publication of a figure

    Before
    published
    After
    draft
    Why
    The record could not read this figure's source: the page answered HTTP 403, so no text of it reached the classifier, which scored card 12013 from the headline alone, and the number came from the headline; published by the bulk approve of 2026-09-25. A reference figure needs a source the record read: returned to draft, off every page, until a readable source that states it is cited (docs/batch-unread-figures-0929.md).

  3387. · google-michigan-data-center-mi · the publication of a figure

    Before
    published
    After
    draft
    Why
    The record could not read this figure's source: the page answered HTTP 429, so no text of it reached the classifier, which scored card 12495 from the headline alone, and the number came from the headline; published by the bulk approve of 2026-09-25. A reference figure needs a source the record read: returned to draft, off every page, until a readable source that states it is cited (docs/batch-unread-figures-0929.md).

  3388. · St. Louis Midtown Data Center · the publication of a figure

    Before
    published
    After
    draft
    Why
    The record could not read this figure's source: the page answered HTTP 403, so no text of it reached the classifier, which scored card 12140 from the headline alone, and the number came from the headline; published by the bulk approve of 2026-09-25. A reference figure needs a source the record read: returned to draft, off every page, until a readable source that states it is cited (docs/batch-unread-figures-0929.md).

  3389. · amazon-data-center-nc-nc · the publication of a figure

    Before
    published
    After
    draft
    Why
    The record could not read this figure's source: the page answered HTTP 403, so no text of it reached the classifier, which scored card 12082 from the headline alone, and the number came from the headline; published by the bulk approve of 2026-09-25. A reference figure needs a source the record read: returned to draft, off every page, until a readable source that states it is cited (docs/batch-unread-figures-0929.md).

  3390. · bitdeer-milam-county-ai-and-hpc-data-center-tx · the publication of a figure

    Before
    published
    After
    draft
    Why
    The record could not read this figure's source: the page answered HTTP 403, so no text of it reached the classifier, which scored card 11759 from the headline alone, and the number came from the headline; published by the bulk approve of 2026-09-25. A reference figure needs a source the record read: returned to draft, off every page, until a readable source that states it is cited (docs/batch-unread-figures-0929.md).

  3391. · Google Mesa data center · the publication of a figure

    Before
    published
    After
    draft
    Why
    The record could not read this figure's source: no text of the page reached the classifier, which scored card 5250 from the headline alone, and the number came from the headline; approved on the editor's word of 2026-09-08. A reference figure needs a source the record read: returned to draft, off every page, until a readable source that states it is cited (docs/batch-unread-figures-0929.md).

  3392. · Google Mesa data center · the publication of a figure

    Before
    published
    After
    draft
    Why
    The record could not read this figure's source: no text of the page reached the classifier, which scored card 5228 from the headline alone, and the number came from the headline; approved on the editor's word of 2026-09-08. A reference figure needs a source the record read: returned to draft, off every page, until a readable source that states it is cited (docs/batch-unread-figures-0929.md).

  3393. · Google Mesa data center · the publication of a figure

    Before
    published
    After
    draft
    Why
    The record could not read this figure's source: no text of the page reached the classifier, which scored card 5232 from the headline alone, and the number came from the headline; approved on the editor's word of 2026-09-08. A reference figure needs a source the record read: returned to draft, off every page, until a readable source that states it is cited (docs/batch-unread-figures-0929.md).

  3394. · Google Mesa data center · the publication of a figure

    Before
    published
    After
    draft
    Why
    The record could not read this figure's source: no text of the page reached the classifier, which scored card 5237 from the headline alone, and the number came from the headline; approved on the editor's word of 2026-09-08. A reference figure needs a source the record read: returned to draft, off every page, until a readable source that states it is cited (docs/batch-unread-figures-0929.md).

  3395. · Meta Louisiana data center · the publication of a figure

    Before
    published
    After
    draft
    Why
    The record could not read this figure's source: no text of the page reached the classifier, which scored card 4504 from the headline alone, and the number came from the headline; published by the bulk approve of 2026-09-25. A reference figure needs a source the record read: returned to draft, off every page, until a readable source that states it is cited (docs/batch-unread-figures-0929.md).

  3396. · Google West Memphis Data Center · the publication of a figure

    Before
    published
    After
    draft
    Why
    The record could not read this figure's source: no text of the page reached the classifier, which scored card 4454 from the headline alone, and the number came from the headline; published by the bulk approve of 2026-09-25. A reference figure needs a source the record read: returned to draft, off every page, until a readable source that states it is cited (docs/batch-unread-figures-0929.md).

  3397. · Google West Memphis Data Center · the publication of a figure

    Before
    published
    After
    draft
    Why
    The record could not read this figure's source: no text of the page reached the classifier, which scored card 4449 from the headline alone, and the number came from the headline; published by the bulk approve of 2026-09-25. A reference figure needs a source the record read: returned to draft, off every page, until a readable source that states it is cited (docs/batch-unread-figures-0929.md).

  3398. · Google West Memphis Data Center · the publication of a figure

    Before
    published
    After
    draft
    Why
    The record could not read this figure's source: no text of the page reached the classifier, which scored card 4445 from the headline alone, and the number came from the headline; published by the bulk approve of 2026-09-25. A reference figure needs a source the record read: returned to draft, off every page, until a readable source that states it is cited (docs/batch-unread-figures-0929.md).

  3399. · Meta Louisiana data center · the publication of a figure

    Before
    published
    After
    draft
    Why
    The record could not read this figure's source: no text of the page reached the classifier, which scored card 4513 from the headline alone, and the number came from the headline; published by the bulk approve of 2026-09-25. A reference figure needs a source the record read: returned to draft, off every page, until a readable source that states it is cited (docs/batch-unread-figures-0929.md).

  3400. · Meta Louisiana data center · the publication of a figure

    Before
    published
    After
    draft
    Why
    The record could not read this figure's source: no text of the page reached the classifier, which scored card 4513 from the headline alone, and the number came from the headline; published by the bulk approve of 2026-09-25. A reference figure needs a source the record read: returned to draft, off every page, until a readable source that states it is cited (docs/batch-unread-figures-0929.md).

  3401. · Google West Memphis Data Center · the publication of a figure

    Before
    published
    After
    draft
    Why
    The record could not read this figure's source: no text of the page reached the classifier, which scored card 4438 from the headline alone, and the number came from the headline; published by the bulk approve of 2026-09-25. A reference figure needs a source the record read: returned to draft, off every page, until a readable source that states it is cited (docs/batch-unread-figures-0929.md).

  3402. · Vantage Port Washington Data Center · the publication of a figure

    Before
    published
    After
    draft
    Why
    The record could not read this figure's source: no text of the page reached the classifier, which scored card 4304 from the headline alone, and the number came from the headline; published by the bulk approve of 2026-09-25. A reference figure needs a source the record read: returned to draft, off every page, until a readable source that states it is cited (docs/batch-unread-figures-0929.md).

  3403. · Vantage Port Washington Data Center · the publication of a figure

    Before
    published
    After
    draft
    Why
    The record could not read this figure's source: no text of the page reached the classifier, which scored card 4287 from the headline alone, and the number came from the headline; published by the bulk approve of 2026-09-25. A reference figure needs a source the record read: returned to draft, off every page, until a readable source that states it is cited (docs/batch-unread-figures-0929.md).

  3404. · Google West Memphis Data Center · the publication of a figure

    Before
    published
    After
    draft
    Why
    The record could not read this figure's source: no text of the page reached the classifier, which scored card 4466 from the headline alone, and the number came from the headline; published by the bulk approve of 2026-09-25. A reference figure needs a source the record read: returned to draft, off every page, until a readable source that states it is cited (docs/batch-unread-figures-0929.md).

  3405. · hassayampa-ranch-data-center-hub-az · the publication of a figure

    Before
    published
    After
    draft
    Why
    The record could not read this figure's source: no text of the page reached the classifier, which scored card 5210 from the headline alone, and the number came from the headline; approved on the editor's word of 2026-09-08. A reference figure needs a source the record read: returned to draft, off every page, until a readable source that states it is cited (docs/batch-unread-figures-0929.md).

  3406. · Apple Prineville Campus · the publication of a figure

    Before
    published
    After
    draft
    Why
    The record could not read this figure's source: no text of the page reached the classifier, which scored card 4063 from the headline alone, and the number came from the headline; published by the bulk approve of 2026-09-25. A reference figure needs a source the record read: returned to draft, off every page, until a readable source that states it is cited (docs/batch-unread-figures-0929.md).

  3407. · Apple Prineville Campus · the publication of a figure

    Before
    published
    After
    draft
    Why
    The record could not read this figure's source: no text of the page reached the classifier, which scored card 4062 from the headline alone, and the number came from the headline; published by the bulk approve of 2026-09-25. A reference figure needs a source the record read: returned to draft, off every page, until a readable source that states it is cited (docs/batch-unread-figures-0929.md).

  3408. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    S&P Global Market Intelligence's 451 Research article of March 2026 could not be read by the record: spglobal.com answered the reader with HTTP 403 from a runner and the Internet Archive holds no capture, so the figure was never read from its source (card 15511, the homepage power and water batch of 2026-09-22), and the bulk approve of 2026-09-25 published it. A reference figure needs a source the record read: returned to draft, off every page, until a readable source that quotes it is cited (docs/batch-unread-figures-0929.md).

  3409. · NTT Mesa data center campus · the publication of a figure

    Before
    published
    After
    draft
    Why
    The record could not read this figure's source: no text of the page reached the classifier, which scored card 5194 from the headline alone, and the number came from the headline; approved on the editor's word of 2026-09-08. A reference figure needs a source the record read: returned to draft, off every page, until a readable source that states it is cited (docs/batch-unread-figures-0929.md).

  3410. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    The record could not read this figure's source: no text of the page reached the classifier, which scored card 5246 from the headline alone, and the number came from the headline; approved on the editor's word of 2026-09-08. A reference figure needs a source the record read: returned to draft, off every page, until a readable source that states it is cited (docs/batch-unread-figures-0929.md).

  3411. · Google Mesa data center · the publication of a figure

    Before
    published
    After
    draft
    Why
    The record could not read this figure's source: no text of the page reached the classifier, which scored card 5245 from the headline alone, and the number came from the headline; approved on the editor's word of 2026-09-08. A reference figure needs a source the record read: returned to draft, off every page, until a readable source that states it is cited (docs/batch-unread-figures-0929.md).

  3412. · Google Mesa data center · the publication of a figure

    Before
    published
    After
    draft
    Why
    The record could not read this figure's source: no text of the page reached the classifier, which scored card 5236 from the headline alone, and the number came from the headline; approved on the editor's word of 2026-09-08. A reference figure needs a source the record read: returned to draft, off every page, until a readable source that states it is cited (docs/batch-unread-figures-0929.md).

  3413. · east-houston-data-center-chron-tx · the publication of a figure

    Before
    published
    After
    draft
    Why
    The record could not read this figure's source: the page answered HTTP 403, so no text of it reached the classifier, which scored card 11769 from the headline alone, and the number came from the headline; published by the bulk approve of 2026-09-25. A reference figure needs a source the record read: returned to draft, off every page, until a readable source that states it is cited (docs/batch-unread-figures-0929.md).

  3414. · Google Mesa data center · the publication of a figure

    Before
    published
    After
    draft
    Why
    The record could not read this figure's source: no text of the page reached the classifier, which scored card 5241 from the headline alone, and the number came from the headline; approved on the editor's word of 2026-09-08. A reference figure needs a source the record read: returned to draft, off every page, until a readable source that states it is cited (docs/batch-unread-figures-0929.md).

  3415. · Salem Township · the county of a scorecard row

    Before
    Salem Township
    After
    Luzerne
    Why
    Salem Township is in Luzerne County; its page moves from /states/pa/salem-township-county to /states/pa/luzerne-county/salem-township, and the old address redirects there. On the editor's word of 2026-09-28.

  3416. · Salem Township · the level of a scorecard row

    Before
    county
    After
    municipality
    Why
    Salem Township is a township, a municipality, in Luzerne County; the row had been filed at the county level under its own name. On the editor's word of 2026-09-28.

  3417. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    The 161 MW is the capacity of the Babbitt Ranch wind project, whose output Google buys (SRP newsroom), the same plant and figure Latitude Media gave on the Google Mesa record. A figure whose sentence names a solar, wind, battery or generation project is not a data center's capacity; returned to draft, so it no longer reads among Arizona's third party power figures (docs/batch-reader-audit-0929.md).

  3418. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    The 260 MW is the capacity of the Sonoran Solar Energy Center, a solar and battery project whose output Google buys (SRP newsroom), the plant Latitude Media gave as 250 MW on the Google Mesa record. A figure whose sentence names a solar, wind, battery or generation project is not a data center's capacity; returned to draft, so it no longer reads among Arizona's third party power figures (docs/batch-reader-audit-0929.md).

  3419. · a record · the reason of a corrections entry

    Before
    A person's name in the reason of 3,066 earlier corrections: on the source tier relabels of 2026-09-23 and on the corrections made on the editor's word.
    After
    The record's rules of 2026-09-23 on the source tier relabels, and the editor's word, brief or rule in the same place on the rest. Nothing else in any reason changed.
    Why
    A public correction line names no person: the record's rules and the editor's decisions are the record's own, and the log says what changed and why without a name. Changed once, on every earlier row, in the reader audit of 2026-09-29 (docs/batch-reader-audit-0929.md).

  3420. · Google Mesa data center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    A caption from an azcentral photo gallery of Mesa data centers, "NTT data center operates in Mesa, Arizona, photographed January 6, 2026": it is about NTT's facility, not Google's, and says nothing about this record. Superseded on this record, returned to draft the way a published history entry leaves a record; Google's own caption from the same gallery (entry 539) stays (docs/batch-reader-audit-0929.md).

  3421. · Google Mesa data center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    A caption from an azcentral photo gallery of Mesa data centers, "Meta data center operates in Mesa, Arizona, photographed January 6, 2026": it is about Meta's facility, not Google's, and says nothing about this record. Superseded on this record, returned to draft the way a published history entry leaves a record; Google's own caption from the same gallery (entry 539) stays (docs/batch-reader-audit-0929.md).

  3422. · Google Mesa data center · the publication of a figure

    Before
    published
    After
    draft
    Why
    The 161 MW is the capacity of the Babbitt Ranch wind project, whose output Google buys under a power purchase agreement (Latitude Media), not the power of the Google Mesa data center. A figure whose sentence names a solar, wind, battery or generation project is not a data center's capacity; returned to draft, so it no longer reads as power reported by others on this record or in Arizona's third party figures (docs/batch-reader-audit-0929.md).

  3423. · Google Mesa data center · the publication of a figure

    Before
    published
    After
    draft
    Why
    The 250 MW is the capacity of the Sonoran Solar Energy Center, a solar and battery project whose output Google buys under a power purchase agreement (Latitude Media), not the power of the Google Mesa data center. A figure whose sentence names a solar, wind, battery or generation project is not a data center's capacity; returned to draft, so it no longer reads as power reported by others on this record or in Arizona's third party figures (docs/batch-reader-audit-0929.md).

  3424. · Josh Shapiro · the state of a statement

    Before
    AZ
    After
    PA
    Why
    Josh Shapiro is the governor of Pennsylvania; the statement, from a WCTI story on Democrats and data center rules, sat on Arizona's row. A statement's home is the row of the body its speaker speaks for (DECISIONS section 24), so it goes on Pennsylvania's own row (docs/batch-reader-audit-0929.md).

  3425. · Wes Moore · the state of a statement

    Before
    AZ
    After
    MD
    Why
    Wes Moore is the governor of Maryland; the statement, from a WCTI story on Democrats and data center rules, sat on Arizona's row. A statement's home is the row of the body its speaker speaks for (DECISIONS section 24), so it goes on Maryland's own row (docs/batch-reader-audit-0929.md).

  3426. · Josh Shapiro · the scorecard row of a statement

    Before
    null
    After
    pa/pennsylvania
    Why
    Josh Shapiro is the governor of Pennsylvania; the statement, from a WCTI story on Democrats and data center rules, sat on Arizona's row. A statement's home is the row of the body its speaker speaks for (DECISIONS section 24), so it goes on Pennsylvania's own row (docs/batch-reader-audit-0929.md).

  3427. · Wes Moore · the scorecard row of a statement

    Before
    null
    After
    md/maryland
    Why
    Wes Moore is the governor of Maryland; the statement, from a WCTI story on Democrats and data center rules, sat on Arizona's row. A statement's home is the row of the body its speaker speaks for (DECISIONS section 24), so it goes on Maryland's own row (docs/batch-reader-audit-0929.md).

  3428. · a record · the publication of a bill

    Before
    published
    After
    draft
    Why
    S.B. 1283 of 2015 is about outpatient treatment centers and respite care. The bill watch matched its title on the word colocation alone, an indirect term, and the bulk approve of 2026-09-25 published it with the cards the gate passed cleanly, so the Arizona page listed it as a signed data center law. It is not a data center measure: dismissed from the record and returned to draft in the reader audit of 2026-09-29. An indirect term alone no longer publishes a bill without a person's word (docs/batch-reader-audit-0929.md).

  3429. · a record · the decision of a bill

    Before
    on_record
    After
    not_on_record
    Why
    S.B. 1283 of 2015 is about outpatient treatment centers and respite care. The bill watch matched its title on the word colocation alone, an indirect term, and the bulk approve of 2026-09-25 published it with the cards the gate passed cleanly, so the Arizona page listed it as a signed data center law. It is not a data center measure: dismissed from the record and returned to draft in the reader audit of 2026-09-29. An indirect term alone no longer publishes a bill without a person's word (docs/batch-reader-audit-0929.md).

  3430. · Scarborough · the rating of a scorecard event

    Before
    open
    After
    no published rating
    Why
    The event carried ME/maine's own rating, which the approve writes on an event whose proposed rating nobody accepted; on ME/scarborough, which carries no rating, it carries none. No row's rating changed (docs/batch-maine-rows-0930.md).

  3431. · Westbrook · the rating of a scorecard event

    Before
    open
    After
    no published rating
    Why
    The event carried ME/maine's own rating, which the approve writes on an event whose proposed rating nobody accepted; on ME/westbrook, which carries no rating, it carries none. No row's rating changed (docs/batch-maine-rows-0930.md).

  3432. · Westbrook · the scorecard row of a scorecard event

    Before
    ME/maine
    After
    ME/westbrook
    Why
    Westbrook's 180 day moratorium, an act of the city (Press Herald); the row was Maine's own. Moved to the Westbrook row, Cumberland County, on the editor's word (docs/batch-maine-rows-0930.md).

  3433. · Scarborough · the scorecard row of a scorecard event

    Before
    ME/maine
    After
    ME/scarborough
    Why
    Scarborough's 180 day moratorium, an act of the town (Press Herald); the row was Maine's own. Moved to the Scarborough row, Cumberland County, on the editor's word (docs/batch-maine-rows-0930.md).

  3434. · Georgia · the moratorium step of a scorecard event

    Before
    ended
    After
    none
    Why
    The sentence counts other bodies' moratoriums without naming one; on a state's own row such a sentence carries no step (the other bodies rule of 2026-09-29), on the editor's word (docs/batch-misfiled-apply-0930.md).

  3435. · South Carolina · the moratorium step of a scorecard event

    Before
    adopted
    After
    none
    Why
    The sentence counts other bodies' moratoriums without naming one; on a state's own row such a sentence carries no step (the other bodies rule of 2026-09-29), on the editor's word (docs/batch-misfiled-apply-0930.md).

  3436. · Iowa · the moratorium step of a scorecard event

    Before
    adopted
    After
    none
    Why
    The sentence counts other bodies' moratoriums without naming one; on a state's own row such a sentence carries no step (the other bodies rule of 2026-09-29), on the editor's word (docs/batch-misfiled-apply-0930.md).

  3437. · Colorado · the moratorium step of a scorecard event

    Before
    adopted
    After
    none
    Why
    The sentence counts other bodies' moratoriums without naming one; on a state's own row such a sentence carries no step (the other bodies rule of 2026-09-29), on the editor's word (docs/batch-misfiled-apply-0930.md).

  3438. · North Carolina · the moratorium step of a scorecard event

    Before
    adopted
    After
    none
    Why
    The sentence counts other bodies' moratoriums without naming one; on a state's own row such a sentence carries no step (the other bodies rule of 2026-09-29), on the editor's word (docs/batch-misfiled-apply-0930.md).

  3439. · Florida · the moratorium step of a scorecard event

    Before
    adopted
    After
    none
    Why
    The sentence counts other bodies' moratoriums without naming one; on a state's own row such a sentence carries no step (the other bodies rule of 2026-09-29), on the editor's word (docs/batch-misfiled-apply-0930.md).

  3440. · North Carolina · the moratorium step of a scorecard event

    Before
    adopted
    After
    none
    Why
    The sentence counts other bodies' moratoriums without naming one; on a state's own row such a sentence carries no step (the other bodies rule of 2026-09-29), on the editor's word (docs/batch-misfiled-apply-0930.md).

  3441. · Tennessee · the moratorium step of a scorecard event

    Before
    adopted
    After
    none
    Why
    The sentence counts other bodies' moratoriums without naming one; on a state's own row such a sentence carries no step (the other bodies rule of 2026-09-29), on the editor's word (docs/batch-misfiled-apply-0930.md).

  3442. · Nebraska · the moratorium step of a scorecard event

    Before
    adopted
    After
    none
    Why
    The sentence counts other bodies' moratoriums without naming one; on a state's own row such a sentence carries no step (the other bodies rule of 2026-09-29), on the editor's word (docs/batch-misfiled-apply-0930.md).

  3443. · Maryland · the moratorium step of a scorecard event

    Before
    adopted
    After
    none
    Why
    The sentence counts other bodies' moratoriums without naming one; on a state's own row such a sentence carries no step (the other bodies rule of 2026-09-29), on the editor's word (docs/batch-misfiled-apply-0930.md).

  3444. · Michigan · the moratorium step of a scorecard event

    Before
    adopted
    After
    none
    Why
    The sentence counts other bodies' moratoriums without naming one; on a state's own row such a sentence carries no step (the other bodies rule of 2026-09-29), on the editor's word (docs/batch-misfiled-apply-0930.md).

  3445. · Michigan · the moratorium step of a scorecard event

    Before
    adopted
    After
    none
    Why
    The sentence counts other bodies' moratoriums without naming one; on a state's own row such a sentence carries no step (the other bodies rule of 2026-09-29), on the editor's word (docs/batch-misfiled-apply-0930.md).

  3446. · Florida · the moratorium step of a scorecard event

    Before
    adopted
    After
    none
    Why
    The sentence counts other bodies' moratoriums, each place's own act on its own row where the record has one; on a state's own row such a sentence carries no step (the other bodies rule of 2026-09-29), on the editor's word (docs/batch-misfiled-apply-0930.md).

  3447. · Massachusetts · the moratorium step of a scorecard event

    Before
    adopted
    After
    none
    Why
    The sentence counts other bodies' moratoriums, each place's own act on its own row where the record has one; on a state's own row such a sentence carries no step (the other bodies rule of 2026-09-29), on the editor's word (docs/batch-misfiled-apply-0930.md).

  3448. · Massachusetts · the moratorium step of a scorecard event

    Before
    adopted
    After
    none
    Why
    The sentence counts other bodies' moratoriums, each place's own act on its own row where the record has one; on a state's own row such a sentence carries no step (the other bodies rule of 2026-09-29), on the editor's word (docs/batch-misfiled-apply-0930.md).

  3449. · New Mexico · the moratorium step of a scorecard event

    Before
    adopted
    After
    none
    Why
    The sentence counts other bodies' moratoriums, each place's own act on its own row where the record has one; on a state's own row such a sentence carries no step (the other bodies rule of 2026-09-29), on the editor's word (docs/batch-misfiled-apply-0930.md).

  3450. · New Mexico · the moratorium step of a scorecard event

    Before
    adopted
    After
    none
    Why
    A candidate's promise that she would issue an order; a plan takes no step, on the editor's word (docs/batch-misfiled-apply-0930.md).

  3451. · Maine · the moratorium step of a scorecard event

    Before
    adopted
    After
    rejected
    Why
    The governor vetoed the bill that would have enacted the moratorium; a veto is the moratorium rejected (the editor's word of 2026-09-29 on event 2261), so the step reads rejected, on the editor's word (docs/batch-misfiled-apply-0930.md).

  3452. · Maine · the moratorium step of a scorecard event

    Before
    adopted
    After
    rejected
    Why
    The governor vetoed the bill that would have enacted the moratorium; a veto is the moratorium rejected (the editor's word of 2026-09-29 on event 2261), so the step reads rejected, on the editor's word (docs/batch-misfiled-apply-0930.md).

  3453. · Cayuga County · the moratorium step of a scorecard event

    Before
    adopted
    After
    none
    Why
    The county passed a resolution urging the state to sign a bill that would impose a moratorium; no moratorium was adopted, so the event carries no step, on the editor's word (docs/batch-misfiled-apply-0930.md).

  3454. · Hays County · the moratorium step of a scorecard event

    Before
    adopted
    After
    rejected
    Why
    The sentence says the countywide moratorium was not passed; the step reads rejected, not adopted, on the editor's word (docs/batch-misfiled-apply-0930.md).

  3455. · Monterey Park · the duplicate mark of a scorecard event

    Before
    none
    After
    4652
    Why
    The same act as event 4652 on the Monterey Park row, the city's voter approved ban of June 2026. Superseded by 4652 so the act shows once, on the editor's word (docs/batch-misfiled-apply-0930.md).

  3456. · Eastport · the duplicate mark of a scorecard event

    Before
    none
    After
    2157
    Why
    The same act as event 2157 on the Eastport row, the City Council's 180 day ban, from the same Maine Monitor story (2310 is Yahoo's copy). Superseded by 2157 so the act shows once, on the editor's word (docs/batch-misfiled-apply-0930.md).

  3457. · Cayuga County · the rating of a scorecard event

    Before
    restrictive
    After
    no published rating
    Why
    The event carried NY/new-york's own rating, which the approve writes on an event whose proposed rating nobody accepted; on NY/cayuga-county, which carries no rating, it carries none. No row's rating changed (docs/batch-misfiled-apply-0930.md).

  3458. · Harpersville · the rating of a scorecard event

    Before
    open
    After
    no published rating
    Why
    The event carried AL/alabama's own rating, which the approve writes on an event whose proposed rating nobody accepted; on AL/harpersville, which carries no rating, it carries none. No row's rating changed (docs/batch-misfiled-apply-0930.md).

  3459. · Linn County · the rating of a scorecard event

    Before
    closed
    After
    no published rating
    Why
    The event carried IA/iowa's own rating, which the approve writes on an event whose proposed rating nobody accepted; on IA/linn-county, which carries no rating, it carries none. No row's rating changed (docs/batch-misfiled-apply-0930.md).

  3460. · Massillon · the rating of a scorecard event

    Before
    restrictive
    After
    no published rating
    Why
    The event carried OH/ohio's own rating, which the approve writes on an event whose proposed rating nobody accepted; on OH/massillon, which carries no rating, it carries none. No row's rating changed (docs/batch-misfiled-apply-0930.md).

  3461. · Ontario · the rating of a scorecard event

    Before
    restrictive
    After
    no published rating
    Why
    The event carried OH/ohio's own rating, which the approve writes on an event whose proposed rating nobody accepted; on OH/ontario, which carries no rating, it carries none. No row's rating changed (docs/batch-misfiled-apply-0930.md).

  3462. · Reno · the rating of a scorecard event

    Before
    case by case
    After
    no published rating
    Why
    The event carried NV/nevada's own rating, which the approve writes on an event whose proposed rating nobody accepted; on NV/reno, which carries no rating, it carries none. No row's rating changed (docs/batch-misfiled-apply-0930.md).

  3463. · Reno · the rating of a scorecard event

    Before
    case by case
    After
    no published rating
    Why
    The event carried NV/nevada's own rating, which the approve writes on an event whose proposed rating nobody accepted; on NV/reno, which carries no rating, it carries none. No row's rating changed (docs/batch-misfiled-apply-0930.md).

  3464. · Cayuga County · the scorecard row of a scorecard event

    Before
    NY/new-york
    After
    NY/cayuga-county
    Why
    The Cayuga County Legislature's resolution, an act of the county (auburnpub.com); the row was New York's own. Moved to the Cayuga County row on the editor's word (docs/batch-misfiled-apply-0930.md).

  3465. · Hays County · the scorecard row of a scorecard event

    Before
    TX/texas
    After
    TX/hays-county
    Why
    The Hays County commissioners' countywide moratorium question, an act of the county (Texas Standard); the row was Texas's own. Moved to the Hays County row on the editor's word (docs/batch-misfiled-apply-0930.md).

  3466. · Harpersville · the scorecard row of a scorecard event

    Before
    AL/alabama
    After
    AL/harpersville
    Why
    Harpersville's six month moratorium, an act of the city (abc3340.com); the row was Alabama's own. Moved to the Harpersville row, Shelby County, on the editor's word (docs/batch-misfiled-apply-0930.md).

  3467. · Linn County · the scorecard row of a scorecard event

    Before
    IA/iowa
    After
    IA/linn-county
    Why
    Linn County's moratorium, an act of the county (The Gazette); the row was Iowa's own. Moved to the Linn County row on the editor's word (docs/batch-misfiled-apply-0930.md).

  3468. · Massillon · the scorecard row of a scorecard event

    Before
    OH/ohio
    After
    OH/massillon
    Why
    Massillon lifted its own moratorium; Massillon is a city in Stark County (Ohio Capital Journal; U.S. Census Bureau, 2020 places by county), and the row was Ohio's own. Moved to the Massillon row on the editor's word (docs/batch-misfiled-apply-0930.md).

  3469. · Ontario · the scorecard row of a scorecard event

    Before
    OH/ohio
    After
    OH/ontario
    Why
    The Ontario City Council's six month moratorium; Ontario is a city in Richland County (Richland Source; U.S. Census Bureau, 2020 places by county), and the row was Ohio's own. Moved to the Ontario row on the editor's word (docs/batch-misfiled-apply-0930.md).

  3470. · Reno · the scorecard row of a scorecard event

    Before
    NV/nevada
    After
    NV/reno
    Why
    Reno's extension of its moratorium through August 2027, an act of the city (nnbw.com); the row was Nevada's own. Moved to the Reno row, Washoe County, on the editor's word (docs/batch-misfiled-apply-0930.md).

  3471. · Reno · the scorecard row of a scorecard event

    Before
    NV/nevada
    After
    NV/reno
    Why
    The Reno City Council's 30 day moratorium, an act of the city (nnbw.com); the row was Nevada's own. Moved to the Reno row, Washoe County, on the editor's word (docs/batch-misfiled-apply-0930.md).

  3472. · Monterey Park · the rating of a scorecard event

    Before
    case by case
    After
    no published rating
    Why
    The event carried CA/california's own rating, which the approve writes on an event whose proposed rating nobody accepted; on CA/monterey-park it carries that row's own rating, none. No row's rating changed.

  3473. · Eastport · the rating of a scorecard event

    Before
    open
    After
    restrictive
    Why
    The event carried ME/maine's own rating, which the approve writes on an event whose proposed rating nobody accepted; on ME/eastport it carries that row's own rating, restrictive. No row's rating changed.

  3474. · Monterey Park · the scorecard row of a scorecard event

    Before
    CA/california
    After
    CA/monterey-park
    Why
    The ban is Monterey Park's, approved by the city's voters (Maine Morning Star); the row was California's own. Moved to the Monterey Park row, Los Angeles County, on the editor's word (docs/batch-row-refile-0930.md).

  3475. · Eastport · the scorecard row of a scorecard event

    Before
    ME/maine
    After
    ME/eastport
    Why
    The ban is the Eastport City Council's, an act of the city (the Maine Monitor's story as Yahoo carried it); the row was Maine's own. Moved to the Eastport row on the editor's word (docs/batch-row-refile-0930.md).

  3476. · Karen Raye · the state of a statement

    Before
    US
    After
    ME
    Why
    Karen Raye is an Eastport city councilor; the statement goes on the Eastport row (DECISIONS section 24; docs/review/statements-reattach-0929.md, the editor's word of 2026-09-29).

  3477. · Vicki Fisher · the state of a statement

    Before
    US
    After
    SD
    Why
    Vicki Fisher is Rapid City's Community Development Director; the statement goes on the Rapid City row (DECISIONS section 24; docs/review/statements-reattach-0929.md, the editor's word of 2026-09-29).

  3478. · Stephen Tamang · the state of a statement

    Before
    US
    After
    SD
    Why
    Stephen Tamang is the Rapid City Council President; the statement goes on the Rapid City row (DECISIONS section 24; docs/review/statements-reattach-0929.md, the editor's word of 2026-09-29).

  3479. · Office of People's Counsel · the state of a statement

    Before
    US
    After
    MD
    Why
    The Office of People's Counsel is a Maryland state office; the statement goes on Maryland's own row (DECISIONS section 24; docs/review/statements-reattach-0929.md, the editor's word of 2026-09-29).

  3480. · JB Pritzker · the state of a statement

    Before
    US
    After
    IL
    Why
    JB Pritzker is the governor of Illinois; the statement goes on Illinois's own row (DECISIONS section 24; docs/review/statements-reattach-0929.md, the editor's word of 2026-09-29).

  3481. · Bryce Bird · the state of a statement

    Before
    US
    After
    UT
    Why
    Bryce Bird heads a Utah state agency; the statement goes on Utah's own row (DECISIONS section 24; docs/review/statements-reattach-0929.md, the editor's word of 2026-09-29).

  3482. · Bryce Bird · the state of a statement

    Before
    US
    After
    UT
    Why
    Bryce Bird heads a Utah state agency; the statement goes on Utah's own row (DECISIONS section 24; docs/review/statements-reattach-0929.md, the editor's word of 2026-09-29).

  3483. · Bryce Bird · the state of a statement

    Before
    US
    After
    UT
    Why
    Bryce Bird heads a Utah state agency; the statement goes on Utah's own row (DECISIONS section 24; docs/review/statements-reattach-0929.md, the editor's word of 2026-09-29).

  3484. · Bryce Bird · the state of a statement

    Before
    US
    After
    UT
    Why
    Bryce Bird heads a Utah state agency; the statement goes on Utah's own row (DECISIONS section 24; docs/review/statements-reattach-0929.md, the editor's word of 2026-09-29).

  3485. · Karen Raye · the scorecard row of a statement

    Before
    null
    After
    me/eastport
    Why
    Karen Raye is an Eastport city councilor; the statement goes on the Eastport row (DECISIONS section 24; docs/review/statements-reattach-0929.md, the editor's word of 2026-09-29).

  3486. · Vicki Fisher · the scorecard row of a statement

    Before
    null
    After
    sd/rapid-city
    Why
    Vicki Fisher is Rapid City's Community Development Director; the statement goes on the Rapid City row (DECISIONS section 24; docs/review/statements-reattach-0929.md, the editor's word of 2026-09-29).

  3487. · Stephen Tamang · the scorecard row of a statement

    Before
    null
    After
    sd/rapid-city
    Why
    Stephen Tamang is the Rapid City Council President; the statement goes on the Rapid City row (DECISIONS section 24; docs/review/statements-reattach-0929.md, the editor's word of 2026-09-29).

  3488. · Office of People's Counsel · the scorecard row of a statement

    Before
    null
    After
    md/maryland
    Why
    The Office of People's Counsel is a Maryland state office; the statement goes on Maryland's own row (DECISIONS section 24; docs/review/statements-reattach-0929.md, the editor's word of 2026-09-29).

  3489. · JB Pritzker · the scorecard row of a statement

    Before
    null
    After
    il/illinois
    Why
    JB Pritzker is the governor of Illinois; the statement goes on Illinois's own row (DECISIONS section 24; docs/review/statements-reattach-0929.md, the editor's word of 2026-09-29).

  3490. · Bryce Bird · the scorecard row of a statement

    Before
    null
    After
    ut/utah
    Why
    Bryce Bird heads a Utah state agency; the statement goes on Utah's own row (DECISIONS section 24; docs/review/statements-reattach-0929.md, the editor's word of 2026-09-29).

  3491. · Bryce Bird · the scorecard row of a statement

    Before
    null
    After
    ut/utah
    Why
    Bryce Bird heads a Utah state agency; the statement goes on Utah's own row (DECISIONS section 24; docs/review/statements-reattach-0929.md, the editor's word of 2026-09-29).

  3492. · Bryce Bird · the scorecard row of a statement

    Before
    null
    After
    ut/utah
    Why
    Bryce Bird heads a Utah state agency; the statement goes on Utah's own row (DECISIONS section 24; docs/review/statements-reattach-0929.md, the editor's word of 2026-09-29).

  3493. · Bryce Bird · the scorecard row of a statement

    Before
    null
    After
    ut/utah
    Why
    Bryce Bird heads a Utah state agency; the statement goes on Utah's own row (DECISIONS section 24; docs/review/statements-reattach-0929.md, the editor's word of 2026-09-29).

  3494. · a record · the value of a figure

    Before
    2,026 ballot measures
    After
    20 ballot measures
    Why
    The value read 2,026 ballot measures, the year of the election. The sentence gives twenty referenda, in words.

  3495. · a record · the value of a figure

    Before
    9 gallons
    After
    1 million gallons
    Why
    The value read 9 gallons, the day of the month the sentence names. The sentence gives nearly a million gallons, in words.

  3496. · a record · the value of a figure

    Before
    2,030 percent of total electricity demand
    After
    not disclosed (percent of total electricity demand)
    Why
    The value read 2,030 percent, the year the sentence names. The sentence gives roughly one third, in words; the value is cleared for a person to enter.

  3497. · a record · the value of a figure

    Before
    2,020 multiple
    After
    4 multiple
    Why
    The value read 2,020, the year the sentence names. The sentence gives nearly quadrupled, in words.

  3498. · a record · the value of a figure

    Before
    2,025 terawatt-hours
    After
    32,202 terawatt hours
    Why
    The value read 2,025, the year the sentence names. The sentence gives worldwide production of 32,202 terawatt hours, with the United States and China as parts of it.

  3499. · a record · the value of a figure

    Before
    27 percent
    After
    75 percent
    Why
    The value read 27 percent, the day the poll began. The sentence gives nearly three quarters, in words.

  3500. · a record · the value of a figure

    Before
    4 tons
    After
    11.599 tons
    Why
    The value read 4 tons, the day of the month the period begins. The sentence gives VOC emissions of approximately 11.599 tons against a permit limit of 6.86 tons; the row carries the emissions.

  3501. · a record · the value of a figure

    Before
    4 tons
    After
    5.158 tons
    Why
    The value read 4 tons, the day of the month the period begins. The sentence gives PM emissions of approximately 5.158 tons against a permit limit of 3.34 tons; the row carries the emissions.

  3502. · a record · the value of a figure

    Before
    4 tons
    After
    102 tons
    Why
    The value read 4 tons, the day of the month the period begins. The sentence gives NOx emissions of approximately 102 tons against a permit limit of 94.67 tons; the row carries the emissions.

  3503. · a record · the value of a figure

    Before
    2,025 %
    After
    not disclosed (%)
    Why
    The value read 2,025 percent, the year the sentence names. The sentence gives about two thirds now and about half in 2025, in words; the value is cleared for a person to enter the one the row carries.

  3504. · a record · the value of a figure

    Before
    2,025 percent
    After
    50 percent
    Why
    The value read 2,025 percent, the year the sentence names. The sentence gives half, in words.

  3505. · a record · the value of a figure

    Before
    2,040 percent increase
    After
    100 percent increase
    Why
    The value read 2,040 percent, the year the sentence names. The sentence says demand will nearly double, which is an increase of nearly 100 percent.

  3506. · a record · the value of a figure

    Before
    2,030 loss-of-load events
    After
    6 loss of load events every 10 years
    Why
    The value read 2,030, the year the sentence names. The sentence gives six times every 10 years, in words.

  3507. · a record · the value of a figure

    Before
    2,030 ratio
    After
    6 ratio
    Why
    The value read 2,030, the year the sentence names. The sentence gives nearly six times the planning standard, in words.

  3508. · a record · the value of a figure

    Before
    2,030 times standard
    After
    6 times standard
    Why
    The value read 2,030, the year the sentence names. The sentence gives nearly six times the standard, in words.

  3509. · a record · the value of a figure

    Before
    2,025 counties
    After
    6 counties
    Why
    The value read 2,025 counties, the year the sentence names. The sentence gives six of the ten counties, in words.

  3510. · a record · the value of a figure

    Before
    2 jobs
    After
    not disclosed (jobs)
    Why
    The value read 2 jobs, the digit in the project's name (Path2Zero). The sentence gives thousands of construction jobs and hundreds of permanent positions, with no number, so the value is cleared.

  3511. · a record · the value of a figure

    Before
    2,024 count
    After
    not disclosed (count)
    Why
    The value read 2,024, a year the sentence names. The sentence gives three counts at three times (six in 2024, 59 in 2025, 294 last month); the value is cleared for a person to pick the one the row carries.

  3512. · a record · the value of a figure

    Before
    2,026 asthma cases and premature deaths
    After
    600,000 asthma cases
    Why
    The value read 2,026, the year of the study. The sentence gives roughly 600,000 asthma cases and 1,300 premature deaths; the row carries the first, and the deaths are a figure of their own for a person to add.

  3513. · a record · the value of a figure

    Before
    2,025 price increase factor
    After
    10 price increase factor
    Why
    The value read 2,025, the year the sentence names. The sentence gives the increase as more than tenfold, in words.

  3514. · a record · the value of a figure

    Before
    2,033 gallons per year
    After
    3 billion gallons per year
    Why
    The value read 2,033 gallons a year, the year the sentence names. The sentence gives more than three billion gallons of water a year, in words.

  3515. · a record · the value of a figure

    Before
    2,026 projects
    After
    26 projects
    Why
    The value read 2,026 projects, the year the sentence names. The line counts projects, and the sentence gives 26 planned projects (and 40 operating data centers, a different count).

  3516. · a record · the value of a figure

    Before
    2,024 dollars
    After
    not disclosed (dollars)
    Why
    The value read 2,024 dollars, the year the sentence names. The sentence gives the figure only as hundreds of millions of dollars, with no number, so the value is cleared.

  3517. · a record · the value of a figure

    Before
    797.5 USD
    After
    797.5 million dollars
    Why
    The sentence gives 797.5 million dollars; the admin's reader dropped the scale word and stored 797.5 USD. Corrected.

  3518. · a record · the value of a figure

    Before
    136.7 USD
    After
    136.7 million dollars
    Why
    The sentence gives 136.7 million dollars; the admin's reader dropped the scale word and stored 136.7 USD. Corrected.

  3519. · a record · the unit of a figure

    Before
    2 million gallons
    After
    2 million gallons a year
    Why
    The unit read gallons with no period; the sentence gives the figure a year. The admin's reader kept the number and dropped the period, so the figure did not count as water a year. Corrected to the unit the sentence gives.

  3520. · a record · the value of a figure

    Before
    1.4 dollars
    After
    1.4 trillion dollars
    Why
    The sentence gives 1.4 trillion dollars; the admin's reader dropped the scale word and stored 1.4 dollars. Corrected.

  3521. · a record · the value of a figure

    Before
    2,017 dollars
    After
    16 billion dollars
    Why
    The value read 2,017 dollars, a year the sentence names; the figure the line is about is 16 billion dollars. Corrected.

  3522. · a record · the value of a figure

    Before
    10 percent
    After
    253 data centers
    Why
    The value read 10 percent, another figure in the same sentence; the line is in data centers, and the sentence gives 253 data centers. Corrected.

  3523. · a record · the value of a figure

    Before
    0 signatures
    After
    3,850 signatures
    Why
    The value read 0 signatures, a number the sentence gives for something else; the figure the line is about is 3,850 signatures. Corrected.

  3524. · a record · the value of a figure

    Before
    1 million USD
    After
    1,982 kW
    Why
    The value read 1 million USD, another figure in the same sentence; the line is in MW, and the sentence gives 1,982 kW. Corrected.

  3525. · a record · the value of a figure

    Before
    45 dollars
    After
    68 billion dollars
    Why
    The value read 45 dollars, a number the sentence gives for something else; the figure the line is about is 68 billion dollars. Corrected.

  3526. · a record · the value of a figure

    Before
    75 percent
    After
    18 jobs
    Why
    The value read 75 percent, another figure in the same sentence; the line is in jobs, and the sentence gives 18 jobs. Corrected.

  3527. · a record · the value of a figure

    Before
    15 dollars
    After
    43.5 million dollars
    Why
    The value read 15 dollars, a number the sentence gives for something else; the figure the line is about is 43.5 million dollars. Corrected.

  3528. · a record · the value of a figure

    Before
    50.62 percent
    After
    520 count
    Why
    The value read 50.62 percent, another figure in the same sentence; the line is in count, and the sentence gives 520 count. Corrected.

  3529. · a record · the value of a figure

    Before
    44.83 percent
    After
    600 count
    Why
    The value read 44.83 percent, another figure in the same sentence; the line is in count, and the sentence gives 600 count. Corrected.

  3530. · a record · the value of a figure

    Before
    4.349 kilowatt-hours
    After
    4.349 trillion kilowatt hours
    Why
    The sentence gives 4.349 trillion kilowatt hours; the admin's reader dropped the scale word and stored 4.349 kilowatt-hours. Corrected.

  3531. · a record · the value of a figure

    Before
    4.27 kilowatt-hours
    After
    4.27 trillion kilowatt hours
    Why
    The sentence gives 4.27 trillion kilowatt hours; the admin's reader dropped the scale word and stored 4.27 kilowatt-hours. Corrected.

  3532. · a record · the value of a figure

    Before
    17 percent
    After
    380 to 790 terawatt hours
    Why
    The value read 17 percent, another figure in the same sentence; the line is in terawatt hours, and the sentence gives 380 to 790 terawatt hours. Corrected.

  3533. · a record · the value of a figure

    Before
    5 percent
    After
    177 to 192 terawatt hours
    Why
    The value read 5 percent, another figure in the same sentence; the line is in terawatt hours, and the sentence gives 177 to 192 terawatt hours. Corrected.

  3534. · a record · the value of a figure

    Before
    30 MW
    After
    20 to 30 MW
    Why
    The sentence gives a range, 20 to 30 MW; the admin's reader kept one end, 30 MW. Corrected to the range.

  3535. · a record · the value of a figure

    Before
    30 MW
    After
    20 to 30 MW
    Why
    The sentence gives a range, 20 to 30 MW; the admin's reader kept one end, 30 MW. Corrected to the range.

  3536. · a record · the value of a figure

    Before
    30 MW
    After
    20 to 30 MW
    Why
    The sentence gives a range, 20 to 30 MW; the admin's reader kept one end, 30 MW. Corrected to the range.

  3537. · a record · the value of a figure

    Before
    1.18 dollars
    After
    1.18 trillion dollars
    Why
    The sentence gives 1.18 trillion dollars; the admin's reader dropped the scale word and stored 1.18 dollars. Corrected.

  3538. · a record · the value of a figure

    Before
    15 dollars
    After
    444 million to 1.5 billion dollars
    Why
    The value read 15 dollars, a number the sentence gives for something else; the figure the line is about is 444 million to 1.5 billion dollars. Corrected.

  3539. · a record · the value of a figure

    Before
    1,600 homes
    After
    1,982 kilowatts per engine
    Why
    The value read 1,600 homes, another figure in the same sentence; the line is in kilowatts per engine, and the sentence gives 1,982 kilowatts per engine. Corrected.

  3540. · a record · the value of a figure

    Before
    45 dollars
    After
    68 billion dollars
    Why
    The value read 45 dollars, a number the sentence gives for something else; the figure the line is about is 68 billion dollars. Corrected.

  3541. · a record · the value of a figure

    Before
    62 kilowatts
    After
    1,982 kilowatts
    Why
    The value read 62 kilowatts, a number the sentence gives for something else; the figure the line is about is 1,982 kilowatts. Corrected.

  3542. · a record · the value of a figure

    Before
    45 dollars
    After
    68 billion dollars
    Why
    The value read 45 dollars, a number the sentence gives for something else; the figure the line is about is 68 billion dollars. Corrected.

  3543. · a record · the value of a figure

    Before
    2,028 dollars a year
    After
    25 million dollars a year
    Why
    The value read 2,028 dollars a year, a year the sentence names; the figure the line is about is 25 million dollars a year. Corrected.

  3544. · a record · the value of a figure

    Before
    2,025 dollars
    After
    3.5 million dollars
    Why
    The value read 2,025 dollars, a year the sentence names; the figure the line is about is 3.5 million dollars. Corrected.

  3545. · a record · the value of a figure

    Before
    134 million USD
    After
    134 million to 389 million dollars
    Why
    The sentence gives a range, 134 million to 389 million dollars; the admin's reader kept one end, 134 million USD. Corrected to the range.

  3546. · a record · the value of a figure

    Before
    150 million USD
    After
    100 jobs
    Why
    The value read 150 million USD, another figure in the same sentence; the line is in jobs, and the sentence gives 100 jobs. Corrected.

  3547. · a record · the value of a figure

    Before
    544 million USD
    After
    544 million to 1.5 billion dollars
    Why
    The sentence gives a range, 544 million to 1.5 billion dollars; the admin's reader kept one end, 544 million USD. Corrected to the range.

  3548. · a record · the value of a figure

    Before
    20 percent
    After
    253 GW
    Why
    The value read 20 percent, another figure in the same sentence; the line is in GW, and the sentence gives 253 GW. Corrected.

  3549. · a record · the value of a figure

    Before
    2 million square feet
    After
    500,000 to 2 million square feet
    Why
    The sentence gives a range, 500,000 to 2 million square feet; the admin's reader kept one end, 2 million square feet. Corrected to the range.

  3550. · a record · the value of a figure

    Before
    10,000 square feet
    After
    1,000 to 10,000 square feet
    Why
    The sentence gives a range, 1,000 to 10,000 square feet; the admin's reader kept one end, 10,000 square feet. Corrected to the range.

  3551. · a record · the value of a figure

    Before
    1 million homes
    After
    1 GW
    Why
    The value read 1 million homes, another figure in the same sentence; the line is in GW, and the sentence gives 1 GW. Corrected.

  3552. · a record · the unit of a figure

    Before
    10.5 billion gallons
    After
    10.5 billion gallons a year
    Why
    The unit read gallons with no period; the sentence gives the figure a year. The admin's reader kept the number and dropped the period, so the figure did not count as water a year. Corrected to the unit the sentence gives.

  3553. · a record · the value of a figure

    Before
    2.2 million USD
    After
    189 million gallons a year
    Why
    The value read 2.2 million USD, another figure in the same sentence; the line is in gallons a year, and the sentence gives 189 million gallons a year. Corrected.

  3554. · a record · the unit of a figure

    Before
    2.5 billion gallons
    After
    2.5 billion gallons a year
    Why
    The unit read gallons with no period; the sentence gives the figure a year. The admin's reader kept the number and dropped the period, so the figure did not count as water a year. Corrected to the unit the sentence gives.

  3555. · a record · the value of a figure

    Before
    123 facilities
    After
    123 to 144 facilities
    Why
    The sentence gives a range, 123 to 144 facilities; the admin's reader kept one end, 123 facilities. Corrected to the range.

  3556. · a record · the value of a figure

    Before
    90 percent
    After
    700 written comments
    Why
    The value read 90 percent, another figure in the same sentence; the line is in written comments, and the sentence gives 700 written comments. Corrected.

  3557. · a record · the value of a figure

    Before
    8,000 workers
    After
    2,500 to 8,000 workers
    Why
    The sentence gives a range, 2,500 to 8,000 workers; the admin's reader kept one end, 8,000 workers. Corrected to the range.

  3558. · a record · the value of a figure

    Before
    4 billion USD
    After
    600 MW
    Why
    The value read 4 billion USD, another figure in the same sentence; the line is in MW, and the sentence gives 600 MW. Corrected.

  3559. · a record · the value of a figure

    Before
    24 billion USD
    After
    19 gigawatts
    Why
    The value read 24 billion USD, another figure in the same sentence; the line is in gigawatts, and the sentence gives 19 gigawatts. Corrected.

  3560. · a record · the value of a figure

    Before
    35.88 tons per year
    After
    157 tons per year
    Why
    The value read 35.88 tons per year, a number the sentence gives for something else; the figure the line is about is 157 tons per year. Corrected.

  3561. · a record · the value of a figure

    Before
    1,100 MW
    After
    300 to 1,100 MW
    Why
    The sentence gives a range, 300 to 1,100 MW; the admin's reader kept one end, 1,100 MW. Corrected to the range.

  3562. · a record · the value of a figure

    Before
    600 MW
    After
    500 to 600 MW
    Why
    The sentence gives a range, 500 to 600 MW; the admin's reader kept one end, 600 MW. Corrected to the range.

  3563. · a record · the value of a figure

    Before
    1.3 USD
    After
    1.3 trillion USD
    Why
    The sentence gives 1.3 trillion USD; the admin's reader dropped the scale word and stored 1.3 USD. Corrected.

  3564. · a record · the value of a figure

    Before
    32 percent
    After
    31 to 32 percent
    Why
    The sentence gives a range, 31 to 32 percent; the admin's reader kept one end, 32 percent. Corrected to the range.

  3565. · a record · the value of a figure

    Before
    26.49 acres
    After
    99 MW
    Why
    The value read 26.49 acres, another figure in the same sentence; the line is in MW, and the sentence gives 99 MW. Corrected.

  3566. · a record · the value of a figure

    Before
    54 percent
    After
    3.1 TWh a year
    Why
    The value read 54 percent, another figure in the same sentence; the line is in TWh a year, and the sentence gives 3.1 TWh a year. Corrected.

  3567. · a record · the unit of a figure

    Before
    14.8 million gallons
    After
    14.8 million gallons a day
    Why
    The unit read gallons with no period; the sentence gives the figure a day. The admin's reader kept the number and dropped the period, so the figure did not count as water a day. Corrected to the unit the sentence gives.

  3568. · a record · the unit of a figure

    Before
    284 million gallons
    After
    284 million gallons a year
    Why
    The unit read gallons with no period; the sentence gives the figure a year. The admin's reader kept the number and dropped the period, so the figure did not count as water a year. Corrected to the unit the sentence gives.

  3569. · a record · the unit of a figure

    Before
    957 million gallons
    After
    957 million gallons a year
    Why
    The unit read gallons with no period; the sentence gives the figure a year. The admin's reader kept the number and dropped the period, so the figure did not count as water a year. Corrected to the unit the sentence gives.

  3570. · a record · the unit of a figure

    Before
    242 million gallons
    After
    242 million gallons a year
    Why
    The unit read gallons with no period; the sentence gives the figure a year. The admin's reader kept the number and dropped the period, so the figure did not count as water a year. Corrected to the unit the sentence gives.

  3571. · a record · the unit of a figure

    Before
    25,000 gallons
    After
    25,000 gallons a day
    Why
    The unit read gallons with no period; the sentence gives the figure a day. The admin's reader kept the number and dropped the period, so the figure did not count as water a day. Corrected to the unit the sentence gives.

  3572. · a record · the unit of a figure

    Before
    4,000 acres
    After
    4,000 acre feet a year
    Why
    The value read 4,000 acres, another figure in the same sentence; the line is in acre feet a year, and the sentence gives 4,000 acre feet a year. Corrected.

  3573. · a record · the unit of a figure

    Before
    17 million acres
    After
    17 million acre feet a year
    Why
    The value read 17 million acres, another figure in the same sentence; the line is in acre feet a year, and the sentence gives 17 million acre feet a year. Corrected.

  3574. · a record · the value of a figure

    Before
    400 MW
    After
    150 data centers
    Why
    The value read 400 MW, another figure in the same sentence; the line is in data centers, and the sentence gives 150 data centers. Corrected.

  3575. · a record · the value of a figure

    Before
    5,000 MW
    After
    1,000 to 5,000 megawatts
    Why
    The sentence gives a range, 1,000 to 5,000 megawatts; the admin's reader kept one end, 5,000 MW. Corrected to the range.

  3576. · a record · the value of a figure

    Before
    2 million homes
    After
    100,000 to 2 million homes equivalent
    Why
    The sentence gives a range, 100,000 to 2 million homes equivalent; the admin's reader kept one end, 2 million homes. Corrected to the range.

  3577. · a record · the unit of a figure

    Before
    300 million gallons
    After
    300 million gallons a year
    Why
    The unit read gallons with no period; the sentence gives the figure a year. The admin's reader kept the number and dropped the period, so the figure did not count as water a year. Corrected to the unit the sentence gives.

  3578. · a record · the value of a figure

    Before
    2,028 dollars a year
    After
    10 billion dollars a year
    Why
    The value read 2,028 dollars a year, a year the sentence names; the figure the line is about is 10 billion dollars a year. Corrected.

  3579. · a record · the unit of a figure

    Before
    3.3 billion gallons
    After
    3.3 billion gallons per year
    Why
    The unit read gallons with no period; the sentence gives the figure a year. The admin's reader kept the number and dropped the period, so the figure did not count as water a year. Corrected to the unit the sentence gives.

  3580. · a record · the unit of a figure

    Before
    385 million gallons
    After
    385 million gallons per year
    Why
    The unit read gallons with no period; the sentence gives the figure a year. The admin's reader kept the number and dropped the period, so the figure did not count as water a year. Corrected to the unit the sentence gives.

  3581. · a record · the unit of a figure

    Before
    1,841 acres
    After
    1,841 acre feet
    Why
    The value read 1,841 acres, another figure in the same sentence; the line is in acre feet, and the sentence gives 1,841 acre feet. Corrected.

  3582. · a record · the value of a figure

    Before
    27 percent
    After
    27 to 30 percent
    Why
    The sentence gives a range, 27 to 30 percent; the admin's reader kept one end, 27 percent. Corrected to the range.

  3583. · a record · the value of a figure

    Before
    32 percent
    After
    25 terawatt hours
    Why
    The value read 32 percent, another figure in the same sentence; the line is in terawatt hours, and the sentence gives 25 terawatt hours. Corrected.

  3584. · a record · the value of a figure

    Before
    844 billion gallons
    After
    469 billion to 844 billion gallons a year
    Why
    The sentence gives a range, 469 billion to 844 billion gallons a year; the admin's reader kept one end, 844 billion gallons. Corrected to the range.

  3585. · a record · the value of a figure

    Before
    2,010 dollars
    After
    1.6 billion dollars
    Why
    The value read 2,010 dollars, a year the sentence names; the figure the line is about is 1.6 billion dollars. Corrected.

  3586. · a record · the value of a figure

    Before
    89 cents on dollar
    After
    89 to 91 cents on dollar
    Why
    The sentence gives a range, 89 to 91 cents on dollar; the admin's reader kept one end, 89 cents on dollar. Corrected to the range.

  3587. · a record · the value of a figure

    Before
    20 dollars
    After
    942 million dollars
    Why
    The value read 20 dollars, a number the sentence gives for something else; the figure the line is about is 942 million dollars. Corrected.

  3588. · a record · the value of a figure

    Before
    74 percent
    After
    752 count
    Why
    The value read 74 percent, another figure in the same sentence; the line is in count, and the sentence gives 752 count. Corrected.

  3589. · a record · the value of a figure

    Before
    99 MW
    After
    49 to 99 MW
    Why
    The sentence gives a range, 49 to 99 MW; the admin's reader kept one end, 99 MW. Corrected to the range.

  3590. · a record · the value of a figure

    Before
    1 million USD
    After
    1 million to 5 million dollars
    Why
    The sentence gives a range, 1 million to 5 million dollars; the admin's reader kept one end, 1 million USD. Corrected to the range.

  3591. · a record · the value of a figure

    Before
    1 million USD
    After
    1 million to 5 million dollars
    Why
    The sentence gives a range, 1 million to 5 million dollars; the admin's reader kept one end, 1 million USD. Corrected to the range.

  3592. · a record · the value of a figure

    Before
    2.48 billion USD
    After
    2.48 billion to 2.72 billion dollars
    Why
    The sentence gives a range, 2.48 billion to 2.72 billion dollars; the admin's reader kept one end, 2.48 billion USD. Corrected to the range.

  3593. · a record · the value of a figure

    Before
    7.1 percent
    After
    7.1 to 8.375 percent
    Why
    The sentence gives a range, 7.1 to 8.375 percent; the admin's reader kept one end, 7.1 percent. Corrected to the range.

  3594. · a record · the unit of a figure

    Before
    650,000 gallons
    After
    650,000 gallons a year
    Why
    The unit read gallons with no period; the sentence gives the figure a year. The admin's reader kept the number and dropped the period, so the figure did not count as water a year. Corrected to the unit the sentence gives.

  3595. · a record · the unit of a figure

    Before
    1.5 million gallons
    After
    1.5 million gallons a year
    Why
    The unit read gallons with no period; the sentence gives the figure a year. The admin's reader kept the number and dropped the period, so the figure did not count as water a year. Corrected to the unit the sentence gives.

  3596. · a record · the value of a figure

    Before
    12 percent
    After
    6.7 to 12 percent
    Why
    The sentence gives a range, 6.7 to 12 percent; the admin's reader kept one end, 12 percent. Corrected to the range.

  3597. · a record · the value of a figure

    Before
    29 million dollars
    After
    29 million to 214 million dollars
    Why
    The sentence gives a range, 29 million to 214 million dollars; the admin's reader kept one end, 29 million dollars. Corrected to the range.

  3598. · a record · the value of a figure

    Before
    2,026 kW
    After
    26 kW
    Why
    The value read 2,026 kW, a year the sentence names; the figure the line is about is 26 kW. Corrected.

  3599. · a record · the value of a figure

    Before
    2,024 kW
    After
    12 kW
    Why
    The value read 2,024 kW, a year the sentence names; the figure the line is about is 12 kW. Corrected.

  3600. · a record · the value of a figure

    Before
    2,016 kW
    After
    6.1 kW
    Why
    The value read 2,016 kW, a year the sentence names; the figure the line is about is 6.1 kW. Corrected.

  3601. · a record · the unit of a figure

    Before
    104 million gallons
    After
    104 million gallons a year
    Why
    The unit read gallons with no period; the sentence gives the figure a year. The admin's reader kept the number and dropped the period, so the figure did not count as water a year. Corrected to the unit the sentence gives.

  3602. · a record · the unit of a figure

    Before
    161 billion gallons
    After
    161 billion gallons a year
    Why
    The unit read gallons with no period; the sentence gives the figure a year. The admin's reader kept the number and dropped the period, so the figure did not count as water a year. Corrected to the unit the sentence gives.

  3603. · a record · the value of a figure

    Before
    201 USD
    After
    307,954 shares
    Why
    The value read 201 USD, another figure in the same sentence; the line is in shares, and the sentence gives 307,954 shares. Corrected.

  3604. · a record · the value of a figure

    Before
    100 million dollars
    After
    100 million to 150 million dollars
    Why
    The sentence gives a range, 100 million to 150 million dollars; the admin's reader kept one end, 100 million dollars. Corrected to the range.

  3605. · a record · the value of a figure

    Before
    9,647 acres
    After
    3.14 billion gallons per year
    Why
    The value read 9,647 acres, another figure in the same sentence; the line is in billion gallons a year, and the sentence gives 3.14 billion gallons per year. Corrected.

  3606. · a record · the value of a figure

    Before
    92 percent
    After
    2,971 counties
    Why
    The value read 92 percent, another figure in the same sentence; the line is in counties, and the sentence gives 2,971 counties. Corrected.

  3607. · a record · the value of a figure

    Before
    2,030 terawatt-hours
    After
    950 to 980 terawatt hours
    Why
    The value read 2,030 terawatt-hours, a year the sentence names; the figure the line is about is 950 to 980 terawatt hours. Corrected.

  3608. · a record · the unit of a figure

    Before
    124,000 gallons
    After
    124,000 gallons a year
    Why
    The unit read gallons with no period; the sentence gives the figure a year. The admin's reader kept the number and dropped the period, so the figure did not count as water a year. Corrected to the unit the sentence gives.

  3609. · a record · the value of a figure

    Before
    350 jobs
    After
    350 to 500 jobs
    Why
    The sentence gives a range, 350 to 500 jobs; the admin's reader kept one end, 350 jobs. Corrected to the range.

  3610. · a record · the unit of a figure

    Before
    260 million gallons
    After
    260 million gallons a year
    Why
    The unit read gallons with no period; the sentence gives the figure a year. The admin's reader kept the number and dropped the period, so the figure did not count as water a year. Corrected to the unit the sentence gives.

  3611. · a record · the value of a figure

    Before
    300 dollars
    After
    300 million to 700 million dollars
    Why
    The sentence gives 300 million to 700 million dollars; the admin's reader dropped the scale word and stored 300 dollars. Corrected.

  3612. · a record · the value of a figure

    Before
    97,493 USD
    After
    314 jobs
    Why
    The value read 97,493 USD, another figure in the same sentence; the line is in jobs, and the sentence gives 314 jobs. Corrected.

  3613. · a record · the unit of a figure

    Before
    5 million gallons
    After
    5 million gallons a day
    Why
    The unit read gallons with no period; the sentence gives the figure a day. The admin's reader kept the number and dropped the period, so the figure did not count as water a day. Corrected to the unit the sentence gives.

  3614. · a record · the value of a figure

    Before
    10 billion USD
    After
    2,986 jobs
    Why
    The value read 10 billion USD, another figure in the same sentence; the line is in jobs, and the sentence gives 2,986 jobs. Corrected.

  3615. · a record · the unit of a figure

    Before
    531 billion gallons
    After
    531 billion gallons a year
    Why
    The unit read gallons with no period; the sentence gives the figure a year. The admin's reader kept the number and dropped the period, so the figure did not count as water a year. Corrected to the unit the sentence gives.

  3616. · a record · the unit of a figure

    Before
    228 billion gallons
    After
    228 billion gallons a year
    Why
    The unit read gallons with no period; the sentence gives the figure a year. The admin's reader kept the number and dropped the period, so the figure did not count as water a year. Corrected to the unit the sentence gives.

  3617. · a record · the value of a figure

    Before
    161 billion gallons
    After
    29 billion to 161 billion gallons a year
    Why
    The sentence gives a range, 29 billion to 161 billion gallons a year; the admin's reader kept one end, 161 billion gallons. Corrected to the range.

  3618. · a record · the value of a figure

    Before
    57,000 homes
    After
    286 MW
    Why
    The value read 57,000 homes, another figure in the same sentence; the line is in MW, and the sentence gives 286 MW. Corrected.

  3619. · a record · the unit of a figure

    Before
    177 million gallons
    After
    177 million gallons a day
    Why
    The unit read gallons with no period; the sentence gives the figure a day. The admin's reader kept the number and dropped the period, so the figure did not count as water a day. Corrected to the unit the sentence gives.

  3620. · a record · the value of a figure

    Before
    134 facilities
    After
    134 to 196 facilities
    Why
    The sentence gives a range, 134 to 196 facilities; the admin's reader kept one end, 134 facilities. Corrected to the range.

  3621. · a record · the value of a figure

    Before
    42 percent
    After
    60.4 billion dollars
    Why
    The value read 42 percent, another figure in the same sentence; the line is in dollars, and the sentence gives 60.4 billion dollars. Corrected.

  3622. · a record · the value of a figure

    Before
    20 jobs
    After
    20 to 50 jobs
    Why
    The sentence gives a range, 20 to 50 jobs; the admin's reader kept one end, 20 jobs. Corrected to the range.

  3623. · a record · the value of a figure

    Before
    40 MW
    After
    30 to 40 MW
    Why
    The sentence gives a range, 30 to 40 MW; the admin's reader kept one end, 40 MW. Corrected to the range.

  3624. · a record · the value of a figure

    Before
    5 MW
    After
    3 to 5 MW
    Why
    The sentence gives a range, 3 to 5 MW; the admin's reader kept one end, 5 MW. Corrected to the range.

  3625. · a record · the value of a figure

    Before
    496,000 square feet
    After
    20 acres
    Why
    The value read 496,000 square feet, another figure in the same sentence; the line is in acres, and the sentence gives 20 acres. Corrected.

  3626. · a record · the value of a figure

    Before
    1 dollars per kilowatt
    After
    7,000 dollars per kilowatt
    Why
    The value read 1 dollars per kilowatt, a number the sentence gives for something else; the figure the line is about is 7,000 dollars per kilowatt. Corrected.

  3627. · a record · the value of a figure

    Before
    30 percent
    After
    20 trillion to 30 trillion dollars a year
    Why
    The value read 30 percent, another figure in the same sentence; the line is in dollars a year, and the sentence gives 20 trillion to 30 trillion dollars a year. Corrected.

  3628. · a record · the value of a figure

    Before
    2.5 GW
    After
    10 million gallons a day
    Why
    The value read 2.5 GW, another figure in the same sentence; the line is in gallons a day, and the sentence gives 10 million gallons a day. Corrected.

  3629. · a record · the value of a figure

    Before
    8,000 USD
    After
    8,000 to 10,000 dollars
    Why
    The sentence gives a range, 8,000 to 10,000 dollars; the admin's reader kept one end, 8,000 USD. Corrected to the range.

  3630. · a record · the value of a figure

    Before
    123 facilities
    After
    123 to 144 facilities
    Why
    The sentence gives a range, 123 to 144 facilities; the admin's reader kept one end, 123 facilities. Corrected to the range.

  3631. · a record · the value of a figure

    Before
    1.5 million gallons
    After
    1 million to 1.5 million gallons per acre
    Why
    The sentence gives a range, 1 million to 1.5 million gallons per acre; the admin's reader kept one end, 1.5 million gallons. Corrected to the range.

  3632. · a record · the value of a figure

    Before
    9.5 percent
    After
    17.45 cents per kilowatt hour
    Why
    The value read 9.5 percent, another figure in the same sentence; the line is in cents per kilowatt hour, and the sentence gives 17.45 cents per kilowatt hour. Corrected.

  3633. · a record · the unit of a figure

    Before
    245 million gallons
    After
    245 million gallons a day
    Why
    The unit read gallons with no period; the sentence gives the figure a day. The admin's reader kept the number and dropped the period, so the figure did not count as water a day. Corrected to the unit the sentence gives.

  3634. · a record · the unit of a figure

    Before
    156 million gallons
    After
    156 million gallons a day
    Why
    The unit read gallons with no period; the sentence gives the figure a day. The admin's reader kept the number and dropped the period, so the figure did not count as water a day. Corrected to the unit the sentence gives.

  3635. · a record · the unit of a figure

    Before
    448 million gallons
    After
    448 million gallons a year
    Why
    The unit read gallons with no period; the sentence gives the figure a year. The admin's reader kept the number and dropped the period, so the figure did not count as water a year. Corrected to the unit the sentence gives.

  3636. · a record · the unit of a figure

    Before
    1 billion gallons
    After
    1 billion gallons a year
    Why
    The unit read gallons with no period; the sentence gives the figure a year. The admin's reader kept the number and dropped the period, so the figure did not count as water a year. Corrected to the unit the sentence gives.

  3637. · a record · the value of a figure

    Before
    2,026 sites
    After
    16 sites
    Why
    The value read 2,026 sites, a year the sentence names; the figure the line is about is 16 sites. Corrected.

  3638. · a record · the unit of a figure

    Before
    100 million gallons
    After
    100 million gallons per year
    Why
    The unit read gallons with no period; the sentence gives the figure a year. The admin's reader kept the number and dropped the period, so the figure did not count as water a year. Corrected to the unit the sentence gives.

  3639. · a record · the value of a figure

    Before
    117 acres
    After
    2.3 million square feet
    Why
    The value read 117 acres, another figure in the same sentence; the line is in square feet, and the sentence gives 2.3 million square feet. Corrected.

  3640. · a record · the unit of a figure

    Before
    300,000 gallons
    After
    300,000 gallons a day
    Why
    The unit read gallons with no period; the sentence gives the figure a day. The admin's reader kept the number and dropped the period, so the figure did not count as water a day. Corrected to the unit the sentence gives.

  3641. · a record · the value of a figure

    Before
    50 MW
    After
    5 million gallons a day
    Why
    The value read 50 MW, another figure in the same sentence; the line is in gallons a day, and the sentence gives 5 million gallons a day. Corrected.

  3642. · a record · the value of a figure

    Before
    3.4 percent
    After
    300,790 jobs
    Why
    The value read 3.4 percent, another figure in the same sentence; the line is in jobs, and the sentence gives 300,790 jobs. Corrected.

  3643. · a record · the value of a figure

    Before
    1.3 USD
    After
    1.3 trillion dollars
    Why
    The sentence gives 1.3 trillion dollars; the admin's reader dropped the scale word and stored 1.3 USD. Corrected.

  3644. · a record · the value of a figure

    Before
    2,000 acres
    After
    1,500 to 2,000 acres
    Why
    The sentence gives a range, 1,500 to 2,000 acres; the admin's reader kept one end, 2,000 acres. Corrected to the range.

  3645. · a record · the value of a figure

    Before
    161 billion gallons
    After
    29 billion to 161 billion gallons per year
    Why
    The sentence gives a range, 29 billion to 161 billion gallons per year; the admin's reader kept one end, 161 billion gallons. Corrected to the range.

  3646. · a record · the value of a figure

    Before
    3 percent
    After
    3 to 9 percent
    Why
    The sentence gives a range, 3 to 9 percent; the admin's reader kept one end, 3 percent. Corrected to the range.

  3647. · a record · the value of a figure

    Before
    415,000 USD
    After
    100,000 gallons per day
    Why
    The value read 415,000 USD, another figure in the same sentence; the line is in gallons per day, and the sentence gives 100,000 gallons per day. Corrected.

  3648. · a record · the value of a figure

    Before
    100 MW
    After
    530,000 gallons per day
    Why
    The value read 100 MW, another figure in the same sentence; the line is in gallons per day, and the sentence gives 530,000 gallons per day. Corrected.

  3649. · a record · the value of a figure

    Before
    10.86 percent
    After
    158.2 billion USD
    Why
    The value read 10.86 percent, another figure in the same sentence; the line is in USD billion, and the sentence gives 158.2 billion USD. Corrected.

  3650. · a record · the unit of a figure

    Before
    100 million gallons
    After
    100 million gallons a year
    Why
    The unit read gallons with no period; the sentence gives the figure a year. The admin's reader kept the number and dropped the period, so the figure did not count as water a year. Corrected to the unit the sentence gives.

  3651. · a record · the value of a figure

    Before
    80 billion USD
    After
    80 billion to 115 billion dollars
    Why
    The sentence gives a range, 80 billion to 115 billion dollars; the admin's reader kept one end, 80 billion USD. Corrected to the range.

  3652. · a record · the value of a figure

    Before
    25 billion USD
    After
    25 billion to 30 billion dollars a year
    Why
    The sentence gives a range, 25 billion to 30 billion dollars a year; the admin's reader kept one end, 25 billion USD. Corrected to the range.

  3653. · a record · the value of a figure

    Before
    3 dollars
    After
    3 trillion dollars
    Why
    The sentence gives 3 trillion dollars; the admin's reader dropped the scale word and stored 3 dollars. Corrected.

  3654. · a record · the value of a figure

    Before
    2,030 dollars
    After
    7 trillion dollars
    Why
    The value read 2,030 dollars, a year the sentence names; the figure the line is about is 7 trillion dollars. Corrected.

  3655. · a record · the value of a figure

    Before
    9 percent
    After
    4,500 megawatts
    Why
    The value read 9 percent, another figure in the same sentence; the line is in megawatts, and the sentence gives 4,500 megawatts. Corrected.

  3656. · a record · the value of a figure

    Before
    2,026 dollars
    After
    130 billion dollars
    Why
    The value read 2,026 dollars, a year the sentence names; the figure the line is about is 130 billion dollars. Corrected.

  3657. · a record · the value of a figure

    Before
    27 dollars
    After
    1 billion dollars
    Why
    The value read 27 dollars, a number the sentence gives for something else; the figure the line is about is 1 billion dollars. Corrected.

  3658. · a record · the unit of a figure

    Before
    30 million gallons
    After
    30 million gallons per day
    Why
    The unit read gallons with no period; the sentence gives the figure a day. The admin's reader kept the number and dropped the period, so the figure did not count as water a day. Corrected to the unit the sentence gives.

  3659. · a record · the value of a figure

    Before
    2,010 watt-hours
    After
    0.04 watt hours
    Why
    The value read 2,010 watt-hours, a year the sentence names; the figure the line is about is 0.04 watt hours. Corrected.

  3660. · a record · the unit of a figure

    Before
    300 million gallons
    After
    300 million gallons per year
    Why
    The unit read gallons with no period; the sentence gives the figure a year. The admin's reader kept the number and dropped the period, so the figure did not count as water a year. Corrected to the unit the sentence gives.

  3661. · a record · the unit of a figure

    Before
    161 billion gallons
    After
    161 billion gallons per year
    Why
    The unit read gallons with no period; the sentence gives the figure a year. The admin's reader kept the number and dropped the period, so the figure did not count as water a year. Corrected to the unit the sentence gives.

  3662. · a record · the unit of a figure

    Before
    1.54 million gallons
    After
    1.54 million gallons per day
    Why
    The unit read gallons with no period; the sentence gives the figure a day. The admin's reader kept the number and dropped the period, so the figure did not count as water a day. Corrected to the unit the sentence gives.

  3663. · a record · the unit of a figure

    Before
    138 million gallons
    After
    138 million gallons a year
    Why
    The unit read gallons with no period; the sentence gives the figure a year. The admin's reader kept the number and dropped the period, so the figure did not count as water a year. Corrected to the unit the sentence gives.

  3664. · a record · the value of a figure

    Before
    2.56 percent
    After
    54,020 jobs
    Why
    The value read 2.56 percent, another figure in the same sentence; the line is in jobs, and the sentence gives 54,020 jobs. Corrected.

  3665. · a record · the value of a figure

    Before
    1 milliliters
    After
    0.6 to 17 milliliters
    Why
    The value read 1 milliliters, a number the sentence gives for something else; the figure the line is about is 0.6 to 17 milliliters. Corrected.

  3666. · a record · the value of a figure

    Before
    30 gallons
    After
    30 trillion gallons
    Why
    The sentence gives 30 trillion gallons; the admin's reader dropped the scale word and stored 30 gallons. Corrected.

  3667. · a record · the unit of a figure

    Before
    100 million gallons
    After
    100 million gallons a year
    Why
    The unit read gallons with no period; the sentence gives the figure a year. The admin's reader kept the number and dropped the period, so the figure did not count as water a year. Corrected to the unit the sentence gives.

  3668. · a record · the value of a figure

    Before
    10 USD
    After
    10 billion to 12 billion dollars
    Why
    The sentence gives 10 billion to 12 billion dollars; the admin's reader dropped the scale word and stored 10 USD. Corrected.

  3669. · a record · the value of a figure

    Before
    200 dollars a year
    After
    105,000 dollars a year
    Why
    The value read 200 dollars a year, a number the sentence gives for something else; the figure the line is about is 105,000 dollars a year. Corrected.

  3670. · a record · the value of a figure

    Before
    12 dollars
    After
    435 million dollars
    Why
    The value read 12 dollars, a number the sentence gives for something else; the figure the line is about is 435 million dollars. Corrected.

  3671. · a record · the value of a figure

    Before
    12 dollars
    After
    227 million to 232 million dollars
    Why
    The value read 12 dollars, a number the sentence gives for something else; the figure the line is about is 227 million to 232 million dollars. Corrected.

  3672. · a record · the value of a figure

    Before
    11 responses
    After
    103 responses
    Why
    The value read 11 responses, a number the sentence gives for something else; the figure the line is about is 103 responses. Corrected.

  3673. · a record · the value of a figure

    Before
    2,027 dollars
    After
    175 billion dollars
    Why
    The value read 2,027 dollars, a year the sentence names; the figure the line is about is 175 billion dollars. Corrected.

  3674. · a record · the value of a figure

    Before
    2,026 dollars
    After
    145.3 billion dollars
    Why
    The value read 2,026 dollars, a year the sentence names; the figure the line is about is 145.3 billion dollars. Corrected.

  3675. · a record · the value of a figure

    Before
    2,025 dollars
    After
    115.9 billion dollars
    Why
    The value read 2,025 dollars, a year the sentence names; the figure the line is about is 115.9 billion dollars. Corrected.

  3676. · a record · the value of a figure

    Before
    2,024 dollars
    After
    55.7 billion dollars
    Why
    The value read 2,024 dollars, a year the sentence names; the figure the line is about is 55.7 billion dollars. Corrected.

  3677. · a record · the value of a figure

    Before
    2,025 dollars
    After
    60 billion dollars
    Why
    The value read 2,025 dollars, a year the sentence names; the figure the line is about is 60 billion dollars. Corrected.

  3678. · a record · the value of a figure

    Before
    200 MW
    After
    0.059 dollars per kilowatt hour
    Why
    The value read 200 MW, another figure in the same sentence; the line is in dollars per kilowatt hour, and the sentence gives 0.059 dollars per kilowatt hour. Corrected.

  3679. · a record · the value of a figure

    Before
    39 percent
    After
    1.2 billion dollars
    Why
    The value read 39 percent, another figure in the same sentence; the line is in dollars, and the sentence gives 1.2 billion dollars. Corrected.

  3680. · a record · the unit of a figure

    Before
    30 million MW
    After
    30 million megawatt hours
    Why
    The value read 30 million MW, another figure in the same sentence; the line is in megawatt hours, and the sentence gives 30 million megawatt hours. Corrected.

  3681. · a record · the value of a figure

    Before
    75 dollars
    After
    130 billion dollars
    Why
    The value read 75 dollars, a number the sentence gives for something else; the figure the line is about is 130 billion dollars. Corrected.

  3682. · a record · the value of a figure

    Before
    750 million USD
    After
    750 million to 1.25 billion dollars
    Why
    The sentence gives a range, 750 million to 1.25 billion dollars; the admin's reader kept one end, 750 million USD. Corrected to the range.

  3683. · a record · the value of a figure

    Before
    750 million USD
    After
    750 million to 1.25 billion dollars
    Why
    The sentence gives a range, 750 million to 1.25 billion dollars; the admin's reader kept one end, 750 million USD. Corrected to the range.

  3684. · a record · the value of a figure

    Before
    52 MW
    After
    3 billion dollars
    Why
    The value read 52 MW, another figure in the same sentence; the line is in dollars, and the sentence gives 3 billion dollars. Corrected.

  3685. · a record · the value of a figure

    Before
    10 dollars
    After
    1.2 billion dollars
    Why
    The value read 10 dollars, a number the sentence gives for something else; the figure the line is about is 1.2 billion dollars. Corrected.

  3686. · a record · the value of a figure

    Before
    750 million dollars
    After
    750 million to 1.25 billion dollars
    Why
    The sentence gives a range, 750 million to 1.25 billion dollars; the admin's reader kept one end, 750 million dollars. Corrected to the range.

  3687. · a record · the value of a figure

    Before
    52 MW
    After
    3 billion dollars
    Why
    The value read 52 MW, another figure in the same sentence; the line is in dollars, and the sentence gives 3 billion dollars. Corrected.

  3688. · a record · the value of a figure

    Before
    20 MW
    After
    1.2 billion dollars
    Why
    The value read 20 MW, another figure in the same sentence; the line is in dollars, and the sentence gives 1.2 billion dollars. Corrected.

  3689. · a record · the value of a figure

    Before
    32 MW
    After
    3 billion dollars
    Why
    The value read 32 MW, another figure in the same sentence; the line is in dollars, and the sentence gives 3 billion dollars. Corrected.

  3690. · a record · the value of a figure

    Before
    20 MW
    After
    1.2 billion dollars
    Why
    The value read 20 MW, another figure in the same sentence; the line is in dollars, and the sentence gives 1.2 billion dollars. Corrected.

  3691. · a record · the value of a figure

    Before
    750 million dollars
    After
    750 million to 1.25 billion dollars
    Why
    The sentence gives a range, 750 million to 1.25 billion dollars; the admin's reader kept one end, 750 million dollars. Corrected to the range.

  3692. · a record · the unit of a figure

    Before
    100 million gallons
    After
    100 million gallons per year
    Why
    The unit read gallons with no period; the sentence gives the figure a year. The admin's reader kept the number and dropped the period, so the figure did not count as water a year. Corrected to the unit the sentence gives.

  3693. · a record · the value of a figure

    Before
    4.5 liters
    After
    4.5 trillion liters
    Why
    The sentence gives 4.5 trillion liters; the admin's reader dropped the scale word and stored 4.5 liters. Corrected.

  3694. · a record · the value of a figure

    Before
    6.7 percent
    After
    6.7 to 12 percent of national electricity
    Why
    The sentence gives a range, 6.7 to 12 percent of national electricity; the admin's reader kept one end, 6.7 percent. Corrected to the range.

  3695. · a record · the value of a figure

    Before
    11.7 billion USD
    After
    11.7 billion to 20.9 billion dollars
    Why
    The sentence gives a range, 11.7 billion to 20.9 billion dollars; the admin's reader kept one end, 11.7 billion USD. Corrected to the range.

  3696. · a record · the value of a figure

    Before
    1 USD
    After
    1 trillion CAD
    Why
    The value read 1 USD, another figure in the same sentence; the line is in dollars, and the sentence gives 1 trillion CAD. Corrected.

  3697. · a record · the unit of a figure

    Before
    14.5 billion USD
    After
    14.5 billion CAD
    Why
    The value read 14.5 billion USD, another figure in the same sentence; the line is in dollars, and the sentence gives 14.5 billion CAD. Corrected.

  3698. · a record · the value of a figure

    Before
    4 GW
    After
    3.5 to 4 GW
    Why
    The sentence gives a range, 3.5 to 4 GW; the admin's reader kept one end, 4 GW. Corrected to the range.

  3699. · a record · the value of a figure

    Before
    4.5 million USD
    After
    4.5 million to 12.5 million dollars a year
    Why
    The sentence gives a range, 4.5 million to 12.5 million dollars a year; the admin's reader kept one end, 4.5 million USD. Corrected to the range.

  3700. · a record · the value of a figure

    Before
    60 million USD
    After
    60 million to 85 million dollars a year
    Why
    The sentence gives a range, 60 million to 85 million dollars a year; the admin's reader kept one end, 60 million USD. Corrected to the range.

  3701. · a record · the value of a figure

    Before
    100 MW
    After
    0.1 to 1 GW
    Why
    The sentence gives a range, 0.1 to 1 GW; the admin's reader kept one end, 100 MW. Corrected to the range.

  3702. · a record · the value of a figure

    Before
    24 million metric tons of CO2
    After
    24 million to 44 million metric tons of CO2
    Why
    The sentence gives 24 million to 44 million metric tons of CO2; the admin's reader dropped the scale word and stored 24 million metric tons of CO2. Corrected.

  3703. · a record · the value of a figure

    Before
    2 MW
    After
    280 MW
    Why
    The value read 2 MW, a number the sentence gives for something else; the figure the line is about is 280 MW. Corrected.

  3704. · a record · the unit of a figure

    Before
    650,000 acres
    After
    650,000 acre feet
    Why
    The value read 650,000 acres, another figure in the same sentence; the line is in acre feet, and the sentence gives 650,000 acre feet. Corrected.

  3705. · a record · the value of a figure

    Before
    1.4 gallons
    After
    1.4 trillion gallons
    Why
    The sentence gives 1.4 trillion gallons; the admin's reader dropped the scale word and stored 1.4 gallons. Corrected.

  3706. · a record · the value of a figure

    Before
    3.4 gallons
    After
    3.4 trillion gallons
    Why
    The sentence gives 3.4 trillion gallons; the admin's reader dropped the scale word and stored 3.4 gallons. Corrected.

  3707. · a record · the value of a figure

    Before
    350 count
    After
    350 to 690 count
    Why
    The sentence gives a range, 350 to 690 count; the admin's reader kept one end, 350 count. Corrected to the range.

  3708. · a record · the value of a figure

    Before
    500,000 gallons
    After
    300,000 to 500,000 gallons per day
    Why
    The sentence gives a range, 300,000 to 500,000 gallons per day; the admin's reader kept one end, 500,000 gallons. Corrected to the range.

  3709. · a record · the value of a figure

    Before
    50 MW
    After
    40 to 50 MW
    Why
    The sentence gives a range, 40 to 50 MW; the admin's reader kept one end, 50 MW. Corrected to the range.

  3710. · a record · the value of a figure

    Before
    645 MW
    After
    17 percent
    Why
    The value read 645 MW, another figure in the same sentence; the line is in percent, and the sentence gives 17 percent. Corrected.

  3711. · a record · the unit of a figure

    Before
    5 million gallons
    After
    5 million gallons per day
    Why
    The unit read gallons with no period; the sentence gives the figure a day. The admin's reader kept the number and dropped the period, so the figure did not count as water a day. Corrected to the unit the sentence gives.

  3712. · a record · the value of a figure

    Before
    11.6 billion dollars
    After
    11.6 billion to 20.8 billion dollars
    Why
    The sentence gives a range, 11.6 billion to 20.8 billion dollars; the admin's reader kept one end, 11.6 billion dollars. Corrected to the range.

  3713. · a record · the value of a figure

    Before
    2,025 dollars
    After
    1.6 billion dollars
    Why
    The value read 2,025 dollars, a year the sentence names; the figure the line is about is 1.6 billion dollars. Corrected.

  3714. · a record · the value of a figure

    Before
    213 percent
    After
    11.7 billion to 20.9 billion dollars
    Why
    The value read 213 percent, another figure in the same sentence; the line is in dollars, and the sentence gives 11.7 billion to 20.9 billion dollars. Corrected.

  3715. · a record · the value of a figure

    Before
    11.7 billion dollars
    After
    11.7 billion to 20.9 billion dollars
    Why
    The sentence gives a range, 11.7 billion to 20.9 billion dollars; the admin's reader kept one end, 11.7 billion dollars. Corrected to the range.

  3716. · a record · the value of a figure

    Before
    75 MW
    After
    214 count
    Why
    The value read 75 MW, another figure in the same sentence; the line is in count, and the sentence gives 214 count. Corrected.

  3717. · a record · the value of a figure

    Before
    75 MW
    After
    247 count
    Why
    The value read 75 MW, another figure in the same sentence; the line is in count, and the sentence gives 247 count. Corrected.

  3718. · a record · the value of a figure

    Before
    4 billion dollars
    After
    4 billion to 4.5 billion dollars
    Why
    The sentence gives a range, 4 billion to 4.5 billion dollars; the admin's reader kept one end, 4 billion dollars. Corrected to the range.

  3719. · a record · the value of a figure

    Before
    16 dollars
    After
    350 million dollars
    Why
    The value read 16 dollars, a number the sentence gives for something else; the figure the line is about is 350 million dollars. Corrected.

  3720. · a record · the unit of a figure

    Before
    300,000 gallons
    After
    300,000 gallons a day
    Why
    The unit read gallons with no period; the sentence gives the figure a day. The admin's reader kept the number and dropped the period, so the figure did not count as water a day. Corrected to the unit the sentence gives.

  3721. · a record · the value of a figure

    Before
    3 billion USD
    After
    120 MW
    Why
    The value read 3 billion USD, another figure in the same sentence; the line is in MW, and the sentence gives 120 MW. Corrected.

  3722. · a record · the value of a figure

    Before
    50 percent
    After
    30 to 50 percent
    Why
    The sentence gives a range, 30 to 50 percent; the admin's reader kept one end, 50 percent. Corrected to the range.

  3723. · a record · the unit of a figure

    Before
    30,000 gallons
    After
    30,000 gallons per day
    Why
    The unit read gallons with no period; the sentence gives the figure a day. The admin's reader kept the number and dropped the period, so the figure did not count as water a day. Corrected to the unit the sentence gives.

  3724. · a record · the value of a figure

    Before
    4,500 USD
    After
    4,500 to 8,900 dollars per household per year
    Why
    The sentence gives a range, 4,500 to 8,900 dollars per household per year; the admin's reader kept one end, 4,500 USD. Corrected to the range.

  3725. · a record · the unit of a figure

    Before
    50,000 gallons
    After
    50,000 gallons a day
    Why
    The unit read gallons with no period; the sentence gives the figure a day. The admin's reader kept the number and dropped the period, so the figure did not count as water a day. Corrected to the unit the sentence gives.

  3726. · a record · the value of a figure

    Before
    30 million gallons
    After
    20 million to 30 million gallons a year
    Why
    The sentence gives a range, 20 million to 30 million gallons a year; the admin's reader kept one end, 30 million gallons. Corrected to the range.

  3727. · a record · the value of a figure

    Before
    11.7 billion dollars per year
    After
    11.7 billion to 20.9 billion dollars per year
    Why
    The sentence gives a range, 11.7 billion to 20.9 billion dollars per year; the admin's reader kept one end, 11.7 billion dollars per year. Corrected to the range.

  3728. · a record · the value of a figure

    Before
    2,000 jobs
    After
    1,500 to 2,000 jobs
    Why
    The sentence gives a range, 1,500 to 2,000 jobs; the admin's reader kept one end, 2,000 jobs. Corrected to the range.

  3729. · a record · the value of a figure

    Before
    2,027 dollars
    After
    310 million dollars
    Why
    The value read 2,027 dollars, a year the sentence names; the figure the line is about is 310 million dollars. Corrected.

  3730. · a record · the unit of a figure

    Before
    5 million gallons
    After
    5 million gallons a day
    Why
    The unit read gallons with no period; the sentence gives the figure a day. The admin's reader kept the number and dropped the period, so the figure did not count as water a day. Corrected to the unit the sentence gives.

  3731. · a record · the unit of a figure

    Before
    11.7 million acres
    After
    11.7 million acre feet
    Why
    The value read 11.7 million acres, another figure in the same sentence; the line is in acre feet, and the sentence gives 11.7 million acre feet. Corrected.

  3732. · a record · the unit of a figure

    Before
    4,000 acres
    After
    4,000 acre feet per year
    Why
    The value read 4,000 acres, another figure in the same sentence; the line is in acre feet per year, and the sentence gives 4,000 acre feet per year. Corrected.

  3733. · a record · the unit of a figure

    Before
    25 million gallons
    After
    25 million gallons per day
    Why
    The unit read gallons with no period; the sentence gives the figure a day. The admin's reader kept the number and dropped the period, so the figure did not count as water a day. Corrected to the unit the sentence gives.

  3734. · a record · the value of a figure

    Before
    24 kW
    After
    2,000 kW
    Why
    The value read 24 kW, a number the sentence gives for something else; the figure the line is about is 2,000 kW. Corrected.

  3735. · a record · the value of a figure

    Before
    60 percent
    After
    55 to 60 percent of property tax revenue
    Why
    The sentence gives a range, 55 to 60 percent of property tax revenue; the admin's reader kept one end, 60 percent. Corrected to the range.

  3736. · a record · the unit of a figure

    Before
    4,000 acres
    After
    4,000 acre feet a year
    Why
    The value read 4,000 acres, another figure in the same sentence; the line is in acre feet a year, and the sentence gives 4,000 acre feet a year. Corrected.

  3737. · a record · the value of a figure

    Before
    10 data centers
    After
    300 data centers
    Why
    The value read 10 data centers, a number the sentence gives for something else; the figure the line is about is 300 data centers. Corrected.

  3738. · a record · the value of a figure

    Before
    35 percent
    After
    2.8 billion dollars
    Why
    The value read 35 percent, another figure in the same sentence; the line is in dollars, and the sentence gives 2.8 billion dollars. Corrected.

  3739. · a record · the value of a figure

    Before
    1,200 MW
    After
    1,100 to 1,200 MW
    Why
    The sentence gives a range, 1,100 to 1,200 MW; the admin's reader kept one end, 1,200 MW. Corrected to the range.

  3740. · a record · the unit of a figure

    Before
    4,000 acres
    After
    4,000 acre feet per year
    Why
    The value read 4,000 acres, another figure in the same sentence; the line is in acre feet per year, and the sentence gives 4,000 acre feet per year. Corrected.

  3741. · a record · the unit of a figure

    Before
    200 acres
    After
    200 acre feet per year
    Why
    The value read 200 acres, another figure in the same sentence; the line is in acre feet per year, and the sentence gives 200 acre feet per year. Corrected.

  3742. · a record · the value of a figure

    Before
    75 MW
    After
    150 projects
    Why
    The value read 75 MW, another figure in the same sentence; the line is in projects, and the sentence gives 150 projects. Corrected.

  3743. · a record · the value of a figure

    Before
    75 MW
    After
    300 projects
    Why
    The value read 75 MW, another figure in the same sentence; the line is in projects, and the sentence gives 300 projects. Corrected.

  3744. · a record · the unit of a figure

    Before
    6,500 acres
    After
    6,500 acre feet per year
    Why
    The value read 6,500 acres, another figure in the same sentence; the line is in acre feet per year, and the sentence gives 6,500 acre feet per year. Corrected.

  3745. · a record · the value of a figure

    Before
    900 homes
    After
    2.3 million cubic feet per hour
    Why
    The value read 900 homes, a number the sentence gives for something else; the figure the line is about is 2.3 million cubic feet per hour. Corrected.

  3746. · a record · the value of a figure

    Before
    150 dollars
    After
    150 million to 225 million dollars
    Why
    The sentence gives 150 million to 225 million dollars; the admin's reader dropped the scale word and stored 150 dollars. Corrected.

  3747. · a record · the value of a figure

    Before
    100 dollars
    After
    100 million to 150 million dollars
    Why
    The sentence gives 100 million to 150 million dollars; the admin's reader dropped the scale word and stored 100 dollars. Corrected.

  3748. · a record · the value of a figure

    Before
    2 dollars a year
    After
    53 million to 99 million dollars a year
    Why
    The value read 2 dollars a year, a number the sentence gives for something else; the figure the line is about is 53 million to 99 million dollars a year. Corrected.

  3749. · a record · the value of a figure

    Before
    19.7 billion USD
    After
    6,400 jobs
    Why
    The value read 19.7 billion USD, another figure in the same sentence; the line is in jobs, and the sentence gives 6,400 jobs. Corrected.

  3750. · a record · the value of a figure

    Before
    10 dollars
    After
    89,000 dollars
    Why
    The value read 10 dollars, a number the sentence gives for something else; the figure the line is about is 89,000 dollars. Corrected.

  3751. · a record · the unit of a figure

    Before
    2,240,073 gallons
    After
    2,240,073 gallons per year
    Why
    The unit read gallons with no period; the sentence gives the figure a year. The admin's reader kept the number and dropped the period, so the figure did not count as water a year. Corrected to the unit the sentence gives.

  3752. · a record · the unit of a figure

    Before
    911,200 gallons
    After
    911,200 gallons per year
    Why
    The unit read gallons with no period; the sentence gives the figure a year. The admin's reader kept the number and dropped the period, so the figure did not count as water a year. Corrected to the unit the sentence gives.

  3753. · a record · the unit of a figure

    Before
    455,600 gallons
    After
    455,600 gallons per year
    Why
    The unit read gallons with no period; the sentence gives the figure a year. The admin's reader kept the number and dropped the period, so the figure did not count as water a year. Corrected to the unit the sentence gives.

  3754. · a record · the value of a figure

    Before
    80 million dollars
    After
    80 million to 115 million dollars
    Why
    The sentence gives a range, 80 million to 115 million dollars; the admin's reader kept one end, 80 million dollars. Corrected to the range.

  3755. · a record · the unit of a figure

    Before
    4,000 acres
    After
    4,000 acre feet per year
    Why
    The value read 4,000 acres, another figure in the same sentence; the line is in acre feet per year, and the sentence gives 4,000 acre feet per year. Corrected.

  3756. · a record · the unit of a figure

    Before
    300 million gallons
    After
    300 million gallons per year
    Why
    The unit read gallons with no period; the sentence gives the figure a year. The admin's reader kept the number and dropped the period, so the figure did not count as water a year. Corrected to the unit the sentence gives.

  3757. · a record · the value of a figure

    Before
    2,025 ratio
    After
    2.5 ratio
    Why
    The value read 2,025 ratio, a year the sentence names; the figure the line is about is 2.5 ratio. Corrected.

  3758. · a record · the value of a figure

    Before
    20 MW
    After
    1 to 20 MW
    Why
    The sentence gives a range, 1 to 20 MW; the admin's reader kept one end, 20 MW. Corrected to the range.

  3759. · a record · the value of a figure

    Before
    1 facilities
    After
    233 facilities
    Why
    The value read 1 facilities, a number the sentence gives for something else; the figure the line is about is 233 facilities. Corrected.

  3760. · a record · the value of a figure

    Before
    5 million gallons
    After
    2 million to 5 million gallons a year
    Why
    The sentence gives a range, 2 million to 5 million gallons a year; the admin's reader kept one end, 5 million gallons. Corrected to the range.

  3761. · a record · the value of a figure

    Before
    19.7 percent
    After
    410.8 TWh
    Why
    The value read 19.7 percent, another figure in the same sentence; the line is in TWh, and the sentence gives 410.8 TWh. Corrected.

  3762. · a record · the value of a figure

    Before
    39.7 percent
    After
    787.8 TWh
    Why
    The value read 39.7 percent, another figure in the same sentence; the line is in TWh, and the sentence gives 787.8 TWh. Corrected.

  3763. · a record · the value of a figure

    Before
    3.2 percent
    After
    4,772 TWh
    Why
    The value read 3.2 percent, another figure in the same sentence; the line is in TWh, and the sentence gives 4,772 TWh. Corrected.

  3764. · a record · the value of a figure

    Before
    25.5 percent
    After
    312.6 TWh
    Why
    The value read 25.5 percent, another figure in the same sentence; the line is in TWh, and the sentence gives 312.6 TWh. Corrected.

  3765. · a record · the value of a figure

    Before
    2,025 dollars
    After
    3.56 billion dollars
    Why
    The value read 2,025 dollars, a year the sentence names; the figure the line is about is 3.56 billion dollars. Corrected.

  3766. · a record · the value of a figure

    Before
    18 months
    After
    18 to 26 months
    Why
    The sentence gives a range, 18 to 26 months; the admin's reader kept one end, 18 months. Corrected to the range.

  3767. · a record · the value of a figure

    Before
    12 months
    After
    12 to 19 months
    Why
    The sentence gives a range, 12 to 19 months; the admin's reader kept one end, 12 months. Corrected to the range.

  3768. · a record · the value of a figure

    Before
    7 dollars
    After
    7 trillion dollars
    Why
    The sentence gives 7 trillion dollars; the admin's reader dropped the scale word and stored 7 dollars. Corrected.

  3769. · a record · the unit of a figure

    Before
    6,500 acres
    After
    6,500 acre feet per year
    Why
    The value read 6,500 acres, another figure in the same sentence; the line is in acre feet per year, and the sentence gives 6,500 acre feet per year. Corrected.

  3770. · a record · the value of a figure

    Before
    2,027 dollars
    After
    13 billion dollars
    Why
    The value read 2,027 dollars, a year the sentence names; the figure the line is about is 13 billion dollars. Corrected.

  3771. · a record · the value of a figure

    Before
    32 GW
    After
    11 to 32 gigawatts
    Why
    The sentence gives a range, 11 to 32 gigawatts; the admin's reader kept one end, 32 GW. Corrected to the range.

  3772. · a record · the value of a figure

    Before
    750 homes per megawatt
    After
    750 to 1,000 homes per megawatt
    Why
    The sentence gives a range, 750 to 1,000 homes per megawatt; the admin's reader kept one end, 750 homes per megawatt. Corrected to the range.

  3773. · a record · the value of a figure

    Before
    100,000 square feet
    After
    106 jobs per 100,000 square feet
    Why
    The value read 100,000 square feet, another figure in the same sentence; the line is in jobs per 100,000 square feet, and the sentence gives 106 jobs per 100,000 square feet. Corrected.

  3774. · a record · the value of a figure

    Before
    100,000 square feet
    After
    12 jobs per 100,000 square feet
    Why
    The value read 100,000 square feet, another figure in the same sentence; the line is in jobs per 100,000 square feet, and the sentence gives 12 jobs per 100,000 square feet. Corrected.

  3775. · a record · the unit of a figure

    Before
    90,000 acres
    After
    90,000 acre feet per year
    Why
    The value read 90,000 acres, another figure in the same sentence; the line is in acre feet per year, and the sentence gives 90,000 acre feet per year. Corrected.

  3776. · a record · the value of a figure

    Before
    22 acres
    After
    20 to 22 acre feet per year
    Why
    The value read 22 acres, another figure in the same sentence; the line is in acre feet per year, and the sentence gives 20 to 22 acre feet per year. Corrected.

  3777. · a record · the value of a figure

    Before
    2,023 dollars
    After
    233 million dollars
    Why
    The value read 2,023 dollars, a year the sentence names; the figure the line is about is 233 million dollars. Corrected.

  3778. · a record · the value of a figure

    Before
    7 dollars
    After
    7 trillion dollars
    Why
    The sentence gives 7 trillion dollars; the admin's reader dropped the scale word and stored 7 dollars. Corrected.

  3779. · a record · the unit of a figure

    Before
    551,000 gallons
    After
    551,000 gallons per year
    Why
    The unit read gallons with no period; the sentence gives the figure a year. The admin's reader kept the number and dropped the period, so the figure did not count as water a year. Corrected to the unit the sentence gives.

  3780. · a record · the unit of a figure

    Before
    339 million gallons
    After
    339 million gallons per year
    Why
    The unit read gallons with no period; the sentence gives the figure a year. The admin's reader kept the number and dropped the period, so the figure did not count as water a year. Corrected to the unit the sentence gives.

  3781. · a record · the unit of a figure

    Before
    404 million gallons
    After
    404 million gallons per year
    Why
    The unit read gallons with no period; the sentence gives the figure a year. The admin's reader kept the number and dropped the period, so the figure did not count as water a year. Corrected to the unit the sentence gives.

  3782. · a record · the unit of a figure

    Before
    10.4 million acres
    After
    10.4 million acre feet a year
    Why
    The value read 10.4 million acres, another figure in the same sentence; the line is in acre feet a year, and the sentence gives 10.4 million acre feet a year. Corrected.

  3783. · a record · the value of a figure

    Before
    3.4 gallons a year
    After
    3.4 trillion gallons a year
    Why
    The sentence gives 3.4 trillion gallons a year; the admin's reader dropped the scale word and stored 3.4 gallons a year. Corrected.

  3784. · a record · the value of a figure

    Before
    10 million square feet
    After
    4,000 acres
    Why
    The value read 10 million square feet, another figure in the same sentence; the line is in acres, and the sentence gives 4,000 acres. Corrected.

  3785. · a record · the value of a figure

    Before
    59 billion gallons
    After
    222 billion liters
    Why
    The value read 59 billion gallons, another figure in the same sentence; the line is in liters, and the sentence gives 222 billion liters. Corrected.

  3786. · a record · the value of a figure

    Before
    3 million USD
    After
    3 million to 124 million dollars
    Why
    The sentence gives a range, 3 million to 124 million dollars; the admin's reader kept one end, 3 million USD. Corrected to the range.

  3787. · a record · the value of a figure

    Before
    15 generators
    After
    588 generators
    Why
    The value read 15 generators, a number the sentence gives for something else; the figure the line is about is 588 generators. Corrected.

  3788. · a record · the unit of a figure

    Before
    1.25 million gallons
    After
    1.25 million gallons per day
    Why
    The unit read gallons with no period; the sentence gives the figure a day. The admin's reader kept the number and dropped the period, so the figure did not count as water a day. Corrected to the unit the sentence gives.

  3789. · a record · the unit of a figure

    Before
    1 million gallons
    After
    1 million gallons a day
    Why
    The unit read gallons with no period; the sentence gives the figure a day. The admin's reader kept the number and dropped the period, so the figure did not count as water a day. Corrected to the unit the sentence gives.

  3790. · a record · the value of a figure

    Before
    15 million square feet
    After
    1,500 acres
    Why
    The value read 15 million square feet, another figure in the same sentence; the line is in acres, and the sentence gives 1,500 acres. Corrected.

  3791. · a record · the value of a figure

    Before
    15 million square feet
    After
    1,500 acres
    Why
    The value read 15 million square feet, another figure in the same sentence; the line is in acres, and the sentence gives 1,500 acres. Corrected.

  3792. · a record · the value of a figure

    Before
    1 million gallons
    After
    100,000 to 1 million gallons a day
    Why
    The sentence gives a range, 100,000 to 1 million gallons a day; the admin's reader kept one end, 1 million gallons. Corrected to the range.

  3793. · a record · the value of a figure

    Before
    33 billion gallons
    After
    16 billion to 33 billion gallons per year
    Why
    The sentence gives a range, 16 billion to 33 billion gallons per year; the admin's reader kept one end, 33 billion gallons. Corrected to the range.

  3794. · a record · the value of a figure

    Before
    80 million dollars
    After
    80 million to 115 million dollars
    Why
    The sentence gives a range, 80 million to 115 million dollars; the admin's reader kept one end, 80 million dollars. Corrected to the range.

  3795. · a record · the value of a figure

    Before
    100 million dollars
    After
    100 million to 150 million dollars
    Why
    The sentence gives a range, 100 million to 150 million dollars; the admin's reader kept one end, 100 million dollars. Corrected to the range.

  3796. · a record · the value of a figure

    Before
    60 percent
    After
    7,500 GWH/year
    Why
    The value read 60 percent, another figure in the same sentence; the line is in GWH/year, and the sentence gives 7,500 GWH/year. Corrected.

  3797. · a record · the value of a figure

    Before
    4,500 gallons
    After
    81.21 dollars
    Why
    The value read 4,500 gallons, another figure in the same sentence; the line is in dollars, and the sentence gives 81.21 dollars. Corrected.

  3798. · a record · the value of a figure

    Before
    45 GW
    After
    2 billion dollars
    Why
    The value read 45 GW, another figure in the same sentence; the line is in dollars, and the sentence gives 2 billion dollars. Corrected.

  3799. · a record · the value of a figure

    Before
    500,000 USD
    After
    500,000 to 700,000 dollars a year
    Why
    The sentence gives a range, 500,000 to 700,000 dollars a year; the admin's reader kept one end, 500,000 USD. Corrected to the range.

  3800. · a record · the value of a figure

    Before
    85 million USD
    After
    165 jobs
    Why
    The value read 85 million USD, another figure in the same sentence; the line is in jobs, and the sentence gives 165 jobs. Corrected.

  3801. · a record · the value of a figure

    Before
    500 MW
    After
    35 to 40 jobs
    Why
    The value read 500 MW, another figure in the same sentence; the line is in jobs, and the sentence gives 35 to 40 jobs. Corrected.

  3802. · a record · the value of a figure

    Before
    1.6 USD
    After
    1.6 trillion dollars
    Why
    The sentence gives 1.6 trillion dollars; the admin's reader dropped the scale word and stored 1.6 USD. Corrected.

  3803. · a record · the value of a figure

    Before
    16.5 percent
    After
    2,420.2 MW
    Why
    The value read 16.5 percent, another figure in the same sentence; the line is in MW, and the sentence gives 2,420.2 MW. Corrected.

  3804. · a record · the value of a figure

    Before
    52.3 percent
    After
    2,882 MW
    Why
    The value read 52.3 percent, another figure in the same sentence; the line is in MW, and the sentence gives 2,882 MW. Corrected.

  3805. · a record · the value of a figure

    Before
    11.7 percent
    After
    1,456.2 MW
    Why
    The value read 11.7 percent, another figure in the same sentence; the line is in MW, and the sentence gives 1,456.2 MW. Corrected.

  3806. · a record · the value of a figure

    Before
    33.7 percent
    After
    10,903 MW
    Why
    The value read 33.7 percent, another figure in the same sentence; the line is in MW, and the sentence gives 10,903 MW. Corrected.

  3807. · a record · the value of a figure

    Before
    830,000 USD
    After
    830,000 to 1.9 billion dollars
    Why
    The sentence gives a range, 830,000 to 1.9 billion dollars; the admin's reader kept one end, 830,000 USD. Corrected to the range.

  3808. · a record · the value of a figure

    Before
    32 acres
    After
    6.7 million dollars
    Why
    The value read 32 acres, another figure in the same sentence; the line is in dollars, and the sentence gives 6.7 million dollars. Corrected.

  3809. · a record · the value of a figure

    Before
    2.8 billion USD
    After
    450 MW
    Why
    The value read 2.8 billion USD, another figure in the same sentence; the line is in MW, and the sentence gives 450 MW. Corrected.

  3810. · a record · the value of a figure

    Before
    18 USD
    After
    18 to 26 dollars per hour
    Why
    The sentence gives a range, 18 to 26 dollars per hour; the admin's reader kept one end, 18 USD. Corrected to the range.

  3811. · a record · the value of a figure

    Before
    50 percent
    After
    8,000 jobs
    Why
    The value read 50 percent, another figure in the same sentence; the line is in jobs, and the sentence gives 8,000 jobs. Corrected.

  3812. · a record · the value of a figure

    Before
    4 billion USD
    After
    1,100 acres
    Why
    The value read 4 billion USD, another figure in the same sentence; the line is in acres, and the sentence gives 1,100 acres. Corrected.

  3813. · a record · the value of a figure

    Before
    15 billion USD
    After
    670 acres
    Why
    The value read 15 billion USD, another figure in the same sentence; the line is in acres, and the sentence gives 670 acres. Corrected.

  3814. · a record · the unit of a figure

    Before
    11,000 gallons
    After
    11,000 gallons per day
    Why
    The unit read gallons with no period; the sentence gives the figure a day. The admin's reader kept the number and dropped the period, so the figure did not count as water a day. Corrected to the unit the sentence gives.

  3815. · a record · the unit of a figure

    Before
    10,000 gallons
    After
    10,000 gallons per day
    Why
    The unit read gallons with no period; the sentence gives the figure a day. The admin's reader kept the number and dropped the period, so the figure did not count as water a day. Corrected to the unit the sentence gives.

  3816. · a record · the value of a figure

    Before
    1.3 billion USD
    After
    1.3 billion to 1.7 billion dollars
    Why
    The sentence gives a range, 1.3 billion to 1.7 billion dollars; the admin's reader kept one end, 1.3 billion USD. Corrected to the range.

  3817. · a record · the unit of a figure

    Before
    22,000 gallons
    After
    22,000 gallons daily
    Why
    The unit read gallons with no period; the sentence gives the figure a year. The admin's reader kept the number and dropped the period, so the figure did not count as water a year. Corrected to the unit the sentence gives.

  3818. · a record · the unit of a figure

    Before
    324,000 gallons
    After
    324,000 gallons annually
    Why
    The unit read gallons with no period; the sentence gives the figure a year. The admin's reader kept the number and dropped the period, so the figure did not count as water a year. Corrected to the unit the sentence gives.

  3819. · a record · the value of a figure

    Before
    960,000 USD
    After
    960,000 to 1.29 million dollars annually
    Why
    The sentence gives a range, 960,000 to 1.29 million dollars annually; the admin's reader kept one end, 960,000 USD. Corrected to the range.

  3820. · a record · the unit of a figure

    Before
    22,000 gallons
    After
    22,000 gallons a day
    Why
    The unit read gallons with no period; the sentence gives the figure a day. The admin's reader kept the number and dropped the period, so the figure did not count as water a day. Corrected to the unit the sentence gives.

  3821. · a record · the value of a figure

    Before
    2 breakers
    After
    32 breakers
    Why
    The value read 2 breakers, a number the sentence gives for something else; the figure the line is about is 32 breakers. Corrected.

  3822. · a record · the value of a figure

    Before
    80 million USD
    After
    400 jobs
    Why
    The value read 80 million USD, another figure in the same sentence; the line is in jobs, and the sentence gives 400 jobs. Corrected.

  3823. · a record · the unit of a figure

    Before
    30,000 gallons
    After
    30,000 gallons per day
    Why
    The unit read gallons with no period; the sentence gives the figure a day. The admin's reader kept the number and dropped the period, so the figure did not count as water a day. Corrected to the unit the sentence gives.

  3824. · a record · the unit of a figure

    Before
    57 million gallons
    After
    57 million gallons a day
    Why
    The unit read gallons with no period; the sentence gives the figure a day. The admin's reader kept the number and dropped the period, so the figure did not count as water a day. Corrected to the unit the sentence gives.

  3825. · a record · the value of a figure

    Before
    74 million tons per year
    After
    662 million tons per year
    Why
    The value read 74 million tons per year, a number the sentence gives for something else; the figure the line is about is 662 million tons per year. Corrected.

  3826. · a record · the value of a figure

    Before
    350 MW
    After
    200 to 350 MW
    Why
    The sentence gives a range, 200 to 350 MW; the admin's reader kept one end, 350 MW. Corrected to the range.

  3827. · a record · the unit of a figure

    Before
    20,000 gallons
    After
    20,000 gallons per day
    Why
    The unit read gallons with no period; the sentence gives the figure a day. The admin's reader kept the number and dropped the period, so the figure did not count as water a day. Corrected to the unit the sentence gives.

  3828. · a record · the unit of a figure

    Before
    20,000 gallons
    After
    20,000 gallons a day
    Why
    The unit read gallons with no period; the sentence gives the figure a day. The admin's reader kept the number and dropped the period, so the figure did not count as water a day. Corrected to the unit the sentence gives.

  3829. · a record · the value of a figure

    Before
    1.6 million dollars
    After
    16 billion dollars
    Why
    The value read 1.6 million dollars, a number the sentence gives for something else; the figure the line is about is 16 billion dollars. Corrected.

  3830. · a record · the value of a figure

    Before
    100,001 dollars
    After
    100,001 to 250,000 dollars
    Why
    The sentence gives a range, 100,001 to 250,000 dollars; the admin's reader kept one end, 100,001 dollars. Corrected to the range.

  3831. · a record · the value of a figure

    Before
    1.7 million dollars
    After
    1.7 million to 2.6 million dollars
    Why
    The sentence gives a range, 1.7 million to 2.6 million dollars; the admin's reader kept one end, 1.7 million dollars. Corrected to the range.

  3832. · a record · the value of a figure

    Before
    5 USD
    After
    5 million to 10 million dollars per year
    Why
    The sentence gives 5 million to 10 million dollars per year; the admin's reader dropped the scale word and stored 5 USD. Corrected.

  3833. · a record · the value of a figure

    Before
    100 MW
    After
    900 million kWh per year
    Why
    The value read 100 MW, another figure in the same sentence; the line is in kWh per year, and the sentence gives 900 million kWh per year. Corrected.

  3834. · a record · the value of a figure

    Before
    2.5 billion USD
    After
    2.5 billion to 4 billion dollars
    Why
    The sentence gives a range, 2.5 billion to 4 billion dollars; the admin's reader kept one end, 2.5 billion USD. Corrected to the range.

  3835. · a record · the value of a figure

    Before
    8 USD
    After
    8 to 13 dollars per month
    Why
    The sentence gives a range, 8 to 13 dollars per month; the admin's reader kept one end, 8 USD. Corrected to the range.

  3836. · a record · the value of a figure

    Before
    18 USD
    After
    18 to 24 USD
    Why
    The sentence gives a range, 18 to 24 USD; the admin's reader kept one end, 18 USD. Corrected to the range.

  3837. · a record · the value of a figure

    Before
    104,000 USD
    After
    104,000 to 124,000 USD
    Why
    The sentence gives a range, 104,000 to 124,000 USD; the admin's reader kept one end, 104,000 USD. Corrected to the range.

  3838. · a record · the value of a figure

    Before
    400 MW
    After
    250 to 400 MW
    Why
    The sentence gives a range, 250 to 400 MW; the admin's reader kept one end, 400 MW. Corrected to the range.

  3839. · a record · the value of a figure

    Before
    15 USD
    After
    15 trillion USD
    Why
    The sentence gives 15 trillion USD; the admin's reader dropped the scale word and stored 15 USD. Corrected.

  3840. · a record · the value of a figure

    Before
    50 USD
    After
    50 trillion USD
    Why
    The sentence gives 50 trillion USD; the admin's reader dropped the scale word and stored 50 USD. Corrected.

  3841. · a record · the value of a figure

    Before
    31.6 USD
    After
    31.6 trillion USD
    Why
    The sentence gives 31.6 trillion USD; the admin's reader dropped the scale word and stored 31.6 USD. Corrected.

  3842. · a record · the value of a figure

    Before
    22 USD
    After
    22 trillion to 50 trillion USD
    Why
    The sentence gives 22 trillion to 50 trillion USD; the admin's reader dropped the scale word and stored 22 USD. Corrected.

  3843. · a record · the value of a figure

    Before
    31.6 USD
    After
    31.6 trillion USD
    Why
    The sentence gives 31.6 trillion USD; the admin's reader dropped the scale word and stored 31.6 USD. Corrected.

  3844. · a record · the value of a figure

    Before
    4 percent
    After
    3 to 4 percent
    Why
    The sentence gives a range, 3 to 4 percent; the admin's reader kept one end, 4 percent. Corrected to the range.

  3845. · a record · the value of a figure

    Before
    5 percent
    After
    4 to 5 percent
    Why
    The sentence gives a range, 4 to 5 percent; the admin's reader kept one end, 5 percent. Corrected to the range.

  3846. · a record · the value of a figure

    Before
    53 million USD
    After
    53 million to 99 million USD
    Why
    The sentence gives a range, 53 million to 99 million USD; the admin's reader kept one end, 53 million USD. Corrected to the range.

  3847. · a record · the value of a figure

    Before
    400 MW
    After
    250 to 400 MW
    Why
    The sentence gives a range, 250 to 400 MW; the admin's reader kept one end, 400 MW. Corrected to the range.

  3848. · a record · the value of a figure

    Before
    400 MW
    After
    250 to 400 MW
    Why
    The sentence gives a range, 250 to 400 MW; the admin's reader kept one end, 400 MW. Corrected to the range.

  3849. · Nebius AI Data Center (Vineland) · the site acres of a record

    Before
    2.6 acres
    After
    107 acres
    Why
    The site read 2.6 acres. Two approvals wrote square feet as acres over the 107 acres an Asbury Park Press article of September 22, 2026 gave (2.6 million square feet and 2,600,000 square feet are a floor area). Restored to 107 acres from that article.

  3850. · ValorC3 Boise Data Center · the site acres of a record

    Before
    924 acres
    After
    92 acres
    Why
    The site read 924 acres. The source said approximately 92 acres (4 million square feet), and the approval ran the two numbers together. Corrected to the 92 acres the source gives.

  3851. · Prometheus Hyperscale Natrona County Data Center · the site acres of a record

    Before
    640300 acres
    After
    not disclosed
    Why
    The site read 640,300 acres. The source gave 640 acres for the data center and 300 acres for the power station, and the approval ran the two numbers together. Returned to not disclosed, as it was before; which figure the record carries is a person's decision.

  3852. · mona-data-center-ut · the site acres of a record

    Before
    20 acres
    After
    not disclosed
    Why
    The site read 20 acres. The source described the building as about 20 Costco warehouses, which is not an area in acres, and the approval wrote the number as acres. Returned to not disclosed, as it was before.

  3853. · MLP Ventures King of Prussia Data Center Campus · the site acres of a record

    Before
    4 acres
    After
    not disclosed
    Why
    The site read 4 acres. The source's figure was 4 million square feet, a floor area, and the approval wrote the number as acres. Returned to not disclosed, as it was before.

  3854. · Inver Grove Heights Data Center · the site acres of a record

    Before
    55000 acres
    After
    not disclosed
    Why
    The site read 55,000 acres. The source's figure was 55,000 square feet, a floor area, and the approval wrote it as acres. Returned to not disclosed, as it was before.

  3855. · Amazon Montgomery County data center · the site acres of a record

    Before
    800000 acres
    After
    not disclosed
    Why
    The site read 800,000 acres. The source's figure was 800,000 square feet, a floor area, and the approval wrote it as acres. Returned to not disclosed, as it was before.

  3856. · Meta Henrico Data Center · the site acres of a record

    Before
    970000 acres
    After
    not disclosed
    Why
    The site read 970,000 acres. The source's figure was 970,000 square feet, a floor area, and the approval wrote it as acres. Returned to not disclosed, as it was before.

  3857. · Meta Huntsville Data Center · the capacity mw of a record

    Before
    3.5 MW
    After
    not disclosed
    Why
    The capacity read 3.5 MW. The source's figure was 3.5 million square feet, a floor area, not a capacity, and the approval of 2026-09-25 wrote the number as megawatts. Returned to not disclosed, as it was before.

  3858. · Google West Memphis Data Center · the capacity mw of a record

    Before
    4 MW
    After
    not disclosed
    Why
    The capacity read 4 MW. The source's figure was $4 billion, an investment, not a capacity, and the approval of 2026-09-25 wrote the number as megawatts. Returned to not disclosed, as it was before.

  3859. · Vantage Port Washington Data Center · the capacity mw of a record

    Before
    130013500 MW
    After
    not disclosed
    Why
    The capacity read 130,013,500 MW. The source, a WPR article on the transmission line, said the data center is expected to need 1,300 megawatts in its first phase and up to 3,500 megawatts later, and the approval of 2026-09-25 ran the two numbers together. Returned to not disclosed, as it was before; which of the two figures the record carries is a person's decision.

  3860. · Project Jupiter · the capacity mw of a record

    Before
    2.45 MW
    After
    2450 MW
    Why
    The capacity read 2.45 MW. The source gave 2.45 gigawatts, and the approval of 2026-09-25 wrote the number without its unit. Corrected to 2,450 MW from the same source.

  3861. · Meta Louisiana data center · the capacity mw of a record

    Before
    5 MW
    After
    5000 MW
    Why
    The capacity read 5 MW. The source gave 5 gigawatts, and the approval of 2026-09-25 wrote the number without its unit. Corrected to 5,000 MW from the same source.

  3862. · Stratos Project · the capacity mw of a record

    Before
    9.5 MW
    After
    9000 MW
    Why
    The capacity read 9.5 MW. A KSL article of September 2026 gave 9.5 gigawatts, and the approval of 2026-09-25 wrote the number without its unit over the 9,000 MW the record carried from the Military Installation Development Authority's own page, which is the figure the record uses where two sources differ (the rule of 2026-09-14). Restored to 9,000 MW from that page; the 9.5 GW figure stays listed beside it as reported by others.

  3863. · a record · the publication of a scorecard row

    Before
    published
    After
    draft
    Why
    Published on the morning of 2026-09-25 (publish_rows_with_events_0925.sql) only for events 4429, which were a vote of the Wasco County commissioners; the row carries no published event of its own. Returned to draft 2026-09-25.

  3864. · a record · the publication of a scorecard row

    Before
    published
    After
    draft
    Why
    Published on the morning of 2026-09-25 (publish_rows_with_events_0925.sql) only for events 2740, 2741, 3022 and 3023, which were a state agency's proposal and its comment deadline; the row carries no published event of its own. Returned to draft 2026-09-25.

  3865. · a record · the publication of a scorecard event

    Before
    published
    After
    draft
    Why
    A background sentence about Ottawa in a roundup of Ontario towns; not an act of Toronto. Returned to draft 2026-09-25.

  3866. · a record · the publication of a scorecard event

    Before
    published
    After
    draft
    Why
    A background sentence about Greater Napanee in a roundup of Ontario towns; not an act of Orangeville. Returned to draft 2026-09-25.

  3867. · a record · the publication of a scorecard event

    Before
    published
    After
    draft
    Why
    A background sentence about a wastewater incident in Cheyenne, Wyoming; not an act of Colorado Springs. Returned to draft 2026-09-25.

  3868. · a record · the publication of a scorecard event

    Before
    published
    After
    draft
    Why
    The comment deadline on a state agency's proposal, not an act of the borough. Returned to draft 2026-09-25.

  3869. · a record · the publication of a scorecard event

    Before
    published
    After
    draft
    Why
    The comment deadline on a state agency's proposal, not an act of the borough. Returned to draft 2026-09-25.

  3870. · a record · the publication of a scorecard event

    Before
    published
    After
    draft
    Why
    A meeting notice of the Pennsylvania Department of Environmental Protection, not an act of Indiana County. Returned to draft 2026-09-25.

  3871. · a record · the publication of a scorecard event

    Before
    published
    After
    draft
    Why
    A meeting notice of the Fairfax County Planning Commission, not an act of Loudoun County. Returned to draft 2026-09-25.

  3872. · New Jersey · the rating of a scorecard event

    Before
    closed
    After
    restrictive
    Why
    The event carried NJ/vineland's own rating, which the approve writes on an event whose proposed rating nobody accepted; on NJ/new-jersey it carries that row's rating, restrictive, so the row's rating does not move. 2026-09-25.

  3873. · Prince George's County · the rating of a scorecard event

    Before
    closed
    After
    no published rating
    Why
    The event carried MD/montgomery-county's own rating, which the approve writes on an event whose proposed rating nobody accepted; on MD/prince-georges-county it carries that row's rating, which is none, so the row's rating does not move. 2026-09-25.

  3874. · Gage County · the rating of a scorecard event

    Before
    closed
    After
    no published rating
    Why
    The event carried NE/cass-county's own rating, which the approve writes on an event whose proposed rating nobody accepted; on NE/gage-county it carries that row's rating, which is none, so the row's rating does not move. 2026-09-25.

  3875. · Gage County · the rating of a scorecard event

    Before
    closed
    After
    no published rating
    Why
    The event carried NE/cass-county's own rating, which the approve writes on an event whose proposed rating nobody accepted; on NE/gage-county it carries that row's rating, which is none, so the row's rating does not move. 2026-09-25.

  3876. · Gage County · the rating of a scorecard event

    Before
    closed
    After
    no published rating
    Why
    The event carried NE/cass-county's own rating, which the approve writes on an event whose proposed rating nobody accepted; on NE/gage-county it carries that row's rating, which is none, so the row's rating does not move. 2026-09-25.

  3877. · Hillsboro · the scorecard row of a scorecard event

    Before
    OR/washington-county
    After
    OR/hillsboro
    Why
    A legal challenge to the City of Hillsboro's data center deals; the row was Washington County. Moved to the Hillsboro row 2026-09-25.

  3878. · Wasco County · the scorecard row of a scorecard event

    Before
    OR/umatilla-county
    After
    OR/wasco-county
    Why
    The Wasco County commissioners' vote; the row was Umatilla County. Moved to the Wasco County row 2026-09-25.

  3879. · United States (federal) · the scorecard row of a scorecard event

    Before
    NV/boulder-city
    After
    US/united-states
    Why
    A stay issued by the Interior Board of Land Appeals, a federal body; the row was Boulder City. Moved to the United States row 2026-09-25.

  3880. · United States (federal) · the scorecard row of a scorecard event

    Before
    NV/boulder-city
    After
    US/united-states
    Why
    An approval by the Bureau of Land Management, a federal agency; the row was Boulder City. Moved to the United States row 2026-09-25.

  3881. · New Jersey · the scorecard row of a scorecard event

    Before
    NJ/vineland
    After
    NJ/new-jersey
    Why
    A penalty imposed by the New Jersey Department of Environmental Protection, a state agency; the row was Vineland. Moved to the New Jersey row 2026-09-25.

  3882. · Kenilworth · the scorecard row of a scorecard event

    Before
    NJ/montville
    After
    NJ/kenilworth
    Why
    The Kenilworth planning board's approval; Kenilworth is a borough in Union County, and the row was Montville. Moved to the Kenilworth row 2026-09-25.

  3883. · Gage County · the scorecard row of a scorecard event

    Before
    NE/cass-county
    After
    NE/gage-county
    Why
    Gage County's public hearing on its proposed moratorium; the row was Cass County. Moved to the Gage County row 2026-09-25.

  3884. · Gage County · the scorecard row of a scorecard event

    Before
    NE/cass-county
    After
    NE/gage-county
    Why
    The Gage County Board of Supervisors' moratorium; the row was Cass County. Moved to the Gage County row 2026-09-25.

  3885. · Gage County · the scorecard row of a scorecard event

    Before
    NE/cass-county
    After
    NE/gage-county
    Why
    The recommendation of Gage County's planning and zoning commission, from the same article; the row was Cass County. Moved to the Gage County row 2026-09-25.

  3886. · Prince George's County · the scorecard row of a scorecard event

    Before
    MD/montgomery-county
    After
    MD/prince-georges-county
    Why
    Prince George's County's moratorium; the row was Montgomery County. Moved to the Prince George's County row 2026-09-25.

  3887. · Burgin · the scorecard row of a scorecard event

    Before
    KY/mercer-county
    After
    KY/burgin
    Why
    The Burgin City Council's vote; an act of the city, and the row was Mercer County. Moved to the Burgin row 2026-09-25.

  3888. · Burgin · the scorecard row of a scorecard event

    Before
    KY/mercer-county
    After
    KY/burgin
    Why
    The Burgin mayor's deciding vote; the row was Mercer County. Moved to the Burgin row 2026-09-25.

  3889. · Burgin · the scorecard row of a scorecard event

    Before
    KY/mercer-county
    After
    KY/burgin
    Why
    The Burgin City Council's annexation vote, postponed; the row was Mercer County. Moved to the Burgin row 2026-09-25.

  3890. · Woodford County · the scorecard row of a scorecard event

    Before
    IL/sangamon-county
    After
    IL/woodford-county
    Why
    The Woodford County Board's moratorium; the row was Sangamon County. Moved to the Woodford County row 2026-09-25.

  3891. · Stickney · the scorecard row of a scorecard event

    Before
    IL/cook-county
    After
    IL/stickney
    Why
    The Stickney board of trustees' moratorium; an act of the village, and the row was Cook County. Moved to the Stickney row 2026-09-25.

  3892. · Cicero · the scorecard row of a scorecard event

    Before
    IL/cook-county
    After
    IL/cicero
    Why
    The Cicero trustees' resolution; an act of the town, and the row was Cook County. Moved to the Cicero row 2026-09-25.

  3893. · Cicero · the scorecard row of a scorecard event

    Before
    IL/cook-county
    After
    IL/cicero
    Why
    Cicero's legal challenge to the Hawthorne development; an act of the town, and the row was Cook County. Moved to the Cicero row 2026-09-25.

  3894. · Tazewell County · the scorecard row of a scorecard event

    Before
    IL/champaign-county
    After
    IL/tazewell-county
    Why
    The Tazewell County Board's zoning amendment; the row was Champaign County. Moved to the Tazewell County row 2026-09-25.

  3895. · Columbia County · the scorecard row of a scorecard event

    Before
    GA/chatham-county
    After
    GA/columbia-county
    Why
    The Economic Development Authority of Columbia County's work with Google; the row was Chatham County. Moved to the Columbia County row 2026-09-25.

  3896. · San Francisco · the scorecard row of a scorecard event

    Before
    CA/san-jose
    After
    CA/san-francisco
    Why
    The San Francisco Board of Supervisors' proposed pause; the row was San Jose. Moved to the San Francisco row 2026-09-25.

  3897. · San Francisco · the scorecard row of a scorecard event

    Before
    CA/san-jose
    After
    CA/san-francisco
    Why
    The terms of San Francisco's proposed pause, from the same article; the row was San Jose. Moved to the San Francisco row 2026-09-25.

  3898. · Alaska · the scorecard row of a scorecard event

    Before
    AK/matanuska-susitna-borough
    After
    AK/alaska
    Why
    A proposal of the Alaska Department of Natural Resources, a state agency; the row was the Matanuska-Susitna Borough. Moved to the Alaska row 2026-09-25.

  3899. · Alaska · the scorecard row of a scorecard event

    Before
    AK/matanuska-susitna-borough
    After
    AK/alaska
    Why
    A proposal of the Alaska Department of Natural Resources, a state agency; the row was the Matanuska-Susitna Borough. Moved to the Alaska row 2026-09-25.

  3900. · a record · the publication of a scorecard row

    Before
    published
    After
    draft
    Why
    Published on the morning of 2026-09-25 only for event 4426 to 4428, which was about Montgomery County and moved to its own row; the row carries no published event of its own. Returned to draft 2026-09-25.

  3901. · Lincoln County · the publication of a scorecard row

    Before
    published
    After
    draft
    Why
    Published on the morning of 2026-09-25 only for event 2731, which was about the City of Lincoln and moved to its own row; the row carries no published event of its own. Returned to draft 2026-09-25.

  3902. · a record · the publication of a scorecard event

    Before
    published
    After
    draft
    Why
    A background sentence about the towns of Leland and Shallotte in a Southport story; not an act of Brunswick County. Returned to draft 2026-09-25 before the row published.

  3903. · a record · the publication of a scorecard event

    Before
    published
    After
    draft
    Why
    A background sentence about Howard, Prince George's, Baltimore and Calvert counties; not an act of Anne Arundel County. Returned to draft 2026-09-25 before the row published.

  3904. · a record · the publication of a scorecard event

    Before
    published
    After
    draft
    Why
    A background sentence about Seattle and Tacoma (Tacoma is in Pierce County) in a Portland story; not an act of King County. Returned to draft 2026-09-25 before the row published.

  3905. · Ypsilanti · the rating of a scorecard event

    Before
    restrictive
    After
    no published rating
    Why
    The event carried MI/ypsilanti-township's own rating, which the approve writes on an event whose proposed rating nobody accepted; on MI/ypsilanti, which carries no rating, it carries none. 2026-09-25.

  3906. · Ypsilanti · the rating of a scorecard event

    Before
    restrictive
    After
    no published rating
    Why
    The event carried MI/ypsilanti-township's own rating, which the approve writes on an event whose proposed rating nobody accepted; on MI/ypsilanti, which carries no rating, it carries none. 2026-09-25.

  3907. · Ferguson · the rating of a scorecard event

    Before
    open
    After
    no published rating
    Why
    The event carried MO/st-louis's own rating, which the approve writes on an event whose proposed rating nobody accepted; on MO/ferguson, which carries no rating, it carries none. 2026-09-25.

  3908. · Ferguson · the rating of a scorecard event

    Before
    open
    After
    no published rating
    Why
    The event carried MO/st-louis's own rating, which the approve writes on an event whose proposed rating nobody accepted; on MO/ferguson, which carries no rating, it carries none. 2026-09-25.

  3909. · Ferguson · the rating of a scorecard event

    Before
    open
    After
    no published rating
    Why
    The event carried MO/st-louis's own rating, which the approve writes on an event whose proposed rating nobody accepted; on MO/ferguson, which carries no rating, it carries none. 2026-09-25.

  3910. · Ferguson · the rating of a scorecard event

    Before
    open
    After
    no published rating
    Why
    The event carried MO/st-louis's own rating, which the approve writes on an event whose proposed rating nobody accepted; on MO/ferguson, which carries no rating, it carries none. 2026-09-25.

  3911. · Ferguson · the rating of a scorecard event

    Before
    open
    After
    no published rating
    Why
    The event carried MO/st-louis's own rating, which the approve writes on an event whose proposed rating nobody accepted; on MO/ferguson, which carries no rating, it carries none. 2026-09-25.

  3912. · Wisconsin Rapids · the scorecard row of a scorecard event

    Before
    WI/wood-county
    After
    WI/wisconsin-rapids
    Why
    The Wisconsin Rapids Planning Commission's vote; the row was Wood County. Moved to the Wisconsin Rapids row 2026-09-25.

  3913. · Montgomery County · the scorecard row of a scorecard event

    Before
    TN/white-county
    After
    TN/montgomery-county
    Why
    The Montgomery County Regional Planning Commission's zoning update (Clarksville Now); the row was White County. Moved to the Montgomery County row 2026-09-25.

  3914. · Montgomery County · the scorecard row of a scorecard event

    Before
    TN/white-county
    After
    TN/montgomery-county
    Why
    A term of Montgomery County's zoning update (Clarksville Now); the row was White County. Moved to the Montgomery County row 2026-09-25.

  3915. · Montgomery County · the scorecard row of a scorecard event

    Before
    TN/white-county
    After
    TN/montgomery-county
    Why
    A term of Montgomery County's zoning update (Clarksville Now); the row was White County. Moved to the Montgomery County row 2026-09-25.

  3916. · Cleveland · the scorecard row of a scorecard event

    Before
    TN/bradley-county
    After
    TN/cleveland
    Why
    The City of Cleveland's ordinance for Project River (Cleveland Daily Banner); an act of the city, and the row was Bradley County. Moved to the Cleveland row 2026-09-25.

  3917. · Cleveland · the scorecard row of a scorecard event

    Before
    TN/bradley-county
    After
    TN/cleveland
    Why
    The developer accepted the City of Cleveland's ordinance (Cleveland Daily Banner); the row was Bradley County. Moved to the Cleveland row 2026-09-25.

  3918. · Cleveland · the scorecard row of a scorecard event

    Before
    TN/bradley-county
    After
    TN/cleveland
    Why
    The City of Cleveland's required studies (Cleveland Daily Banner); the row was Bradley County. Moved to the Cleveland row 2026-09-25.

  3919. · Prineville · the scorecard row of a scorecard event

    Before
    OR/wasco-county
    After
    OR/prineville
    Why
    Prineville officials' talks with two companies; Prineville is in Crook County, and the row was Wasco County. Moved to the Prineville row 2026-09-25.

  3920. · Wilmington · the scorecard row of a scorecard event

    Before
    OH/clinton-county
    After
    OH/wilmington
    Why
    A federal ruling on the City of Wilmington's three ordinances; the row was Clinton County. Moved to the Wilmington row 2026-09-25.

  3921. · Lincoln · the scorecard row of a scorecard event

    Before
    NE/lincoln-county
    After
    NE/lincoln
    Why
    The City of Lincoln's announcement about Google's site at North 35th Street and Interstate 80 (Lincoln Journal Star); Lincoln is in Lancaster County, and the row was Lincoln County. Moved to the Lincoln row 2026-09-25.

  3922. · Desloge · the scorecard row of a scorecard event

    Before
    MO/st-louis-county
    After
    MO/desloge
    Why
    The City of Desloge's town hall (Daily Journal); Desloge is in St. Francois County, and the row was St. Louis County. Moved to the Desloge row 2026-09-25.

  3923. · Desloge · the scorecard row of a scorecard event

    Before
    MO/st-louis-county
    After
    MO/desloge
    Why
    Attendance at the Desloge town hall (Daily Journal); the row was St. Louis County. Moved to the Desloge row 2026-09-25.

  3924. · Desloge · the scorecard row of a scorecard event

    Before
    MO/st-louis-county
    After
    MO/desloge
    Why
    Public comment at the Desloge town hall (Daily Journal); the row was St. Louis County. Moved to the Desloge row 2026-09-25.

  3925. · Ferguson · the scorecard row of a scorecard event

    Before
    MO/st-louis
    After
    MO/ferguson
    Why
    The Ferguson City Council's vote on the Emerson campus tax break (St. Louis Public Radio); Ferguson is a city in St. Louis County, and the row was the City of St. Louis. Moved to the Ferguson row 2026-09-25.

  3926. · Ferguson · the scorecard row of a scorecard event

    Before
    MO/st-louis
    After
    MO/ferguson
    Why
    Ferguson council members reintroduced the Emerson campus incentives (St. Louis Public Radio); the row was the City of St. Louis. Moved to the Ferguson row 2026-09-25.

  3927. · Ferguson · the scorecard row of a scorecard event

    Before
    MO/st-louis
    After
    MO/ferguson
    Why
    A term of Ferguson's Emerson campus proposal (St. Louis Public Radio); the row was the City of St. Louis. Moved to the Ferguson row 2026-09-25.

  3928. · Ferguson · the scorecard row of a scorecard event

    Before
    MO/st-louis
    After
    MO/ferguson
    Why
    The City Council vote on the Emerson campus incentives is Ferguson's (the Emerson campus is in Ferguson; St. Louis legislates through its Board of Aldermen); the row was the City of St. Louis. Moved to the Ferguson row 2026-09-25.

  3929. · Ferguson · the scorecard row of a scorecard event

    Before
    MO/st-louis
    After
    MO/ferguson
    Why
    A term of Ferguson's Emerson campus incentives, paid to the Ferguson Neighborhood Improvement Program; the row was the City of St. Louis. Moved to the Ferguson row 2026-09-25.

  3930. · Ypsilanti · the scorecard row of a scorecard event

    Before
    MI/ypsilanti-township
    After
    MI/ypsilanti
    Why
    The Ypsilanti City Council's moratorium vote; the City of Ypsilanti and Ypsilanti Township are separate governments, and the row was the township. Moved to the Ypsilanti row 2026-09-25.

  3931. · Ypsilanti · the scorecard row of a scorecard event

    Before
    MI/ypsilanti-township
    After
    MI/ypsilanti
    Why
    The Ypsilanti City Council's review of proposed regulations; the row was the township. Moved to the Ypsilanti row 2026-09-25.

  3932. · Bloomington · the scorecard row of a scorecard event

    Before
    IL/chicago
    After
    IL/bloomington
    Why
    Bloomington's public forum (WGLT, Bloomington and Normal); Bloomington is in McLean County, and the row was Chicago. Moved to the Bloomington row 2026-09-25.

  3933. · Bloomington · the scorecard row of a scorecard event

    Before
    IL/chicago
    After
    IL/bloomington
    Why
    The Bloomington Planning Commission's hearings (WGLT); Bloomington is in McLean County, and the row was Chicago. Moved to the Bloomington row 2026-09-25.

  3934. · Normal · the scorecard row of a scorecard event

    Before
    IL/chicago
    After
    IL/normal
    Why
    The Town of Normal's planning (WGLT); Normal is in McLean County, and the row was Chicago. Moved to the Normal row 2026-09-25.

  3935. · Elgin · the scorecard row of a scorecard event

    Before
    IL/chicago
    After
    IL/elgin
    Why
    The Elgin City Council's moratorium vote (Chicago Tribune); the row was Chicago. Moved to the Elgin row 2026-09-25.

  3936. · Elgin · the scorecard row of a scorecard event

    Before
    IL/chicago
    After
    IL/elgin
    Why
    The Elgin City Council's final vote to come (Chicago Tribune); the row was Chicago. Moved to the Elgin row 2026-09-25.

  3937. · Aurora · the scorecard row of a scorecard event

    Before
    IL/chicago
    After
    IL/aurora
    Why
    Aurora's moratorium and ordinance (Chicago Tribune); the row was Chicago. Moved to the Aurora row 2026-09-25.

  3938. · Aurora · the scorecard row of a scorecard event

    Before
    IL/chicago
    After
    IL/aurora
    Why
    Aurora's ordinance (Chicago Tribune); the row was Chicago. Moved to the Aurora row 2026-09-25.

  3939. · South Elgin · the scorecard row of a scorecard event

    Before
    IL/chicago
    After
    IL/south-elgin
    Why
    The South Elgin village board's denial (Chicago Tribune); the row was Chicago. Moved to the South Elgin row 2026-09-25.

  3940. · Fort Pierce · the scorecard row of a scorecard event

    Before
    FL/st-lucie-county
    After
    FL/fort-pierce
    Why
    The Fort Pierce planning board's request; the row was St. Lucie County. Moved to the Fort Pierce row 2026-09-25.

  3941. · Philip D. Murphy · the date of a statement

    Before
    2026-09-24
    After
    2025-10-20
    Why
    The statement was dated 2026-09-24, the day its card was queued, because LegiScan lists the letter with no date and the letter prints none. The letter is Governor Murphy's conditional veto of S. 4293, which the Legislature records as received in the Senate on 2025-10-20; the statement now carries that date.

  3942. · Philip D. Murphy · the date of a statement

    Before
    2026-09-24
    After
    2025-10-20
    Why
    The statement was dated 2026-09-24, the day its card was queued, because LegiScan lists the letter with no date and the letter prints none. The letter is Governor Murphy's conditional veto of S. 4293, which the Legislature records as received in the Senate on 2025-10-20; the statement now carries that date.

  3943. · a record · the summary of a law

    Before
    H.B. 4983 of the 2026 Regular Session was signed on 2026-03-30. The legislature titles it: Authorizing the Department of Commerce to promulgate a legislative rule relating to certification of a microgrid district or certification as a high impact data center. What the act requires is not yet on the record; its text has not been read.
    After
    H.B. 4983 of the 2026 Regular Session was signed on 2026-03-30. The legislature titles it: Authorizing the Department of Commerce to promulgate a legislative rule relating to certification of a microgrid district or certification as a high impact data center.
    Why
    The summary said what the act requires was not yet on the record and that its text had not been read, the sentence written while the row was empty. The requires beneath it has since been drafted from the act's own text, so the sentence was no longer true. It is removed and nothing else in the summary changes.

  3944. · a record · the summary of a law

    Before
    S.B. 6231 of the 2025-2026 Regular Session was signed on 2026-04-01. The legislature titles it: Revised for engrossed: Removing a tax exemption for the replacement of equipment for data centers. What the act requires is not yet on the record; its text has not been read.
    After
    S.B. 6231 of the 2025-2026 Regular Session was signed on 2026-04-01. The legislature titles it: Revised for engrossed: Removing a tax exemption for the replacement of equipment for data centers.
    Why
    The summary said what the act requires was not yet on the record and that its text had not been read, the sentence written while the row was empty. The requires beneath it has since been drafted from the act's own text, so the sentence was no longer true. It is removed and nothing else in the summary changes.

  3945. · a record · the summary of a law

    Before
    H.B. 1038 of the 2026 Regular Session was signed on 2026-03-30. The legislature titles it: Allow the Public Utilities Commission to assess actual costs to data centers that are customers of public utilities. What the act requires is not yet on the record; its text has not been read.
    After
    H.B. 1038 of the 2026 Regular Session was signed on 2026-03-30. The legislature titles it: Allow the Public Utilities Commission to assess actual costs to data centers that are customers of public utilities.
    Why
    The summary said what the act requires was not yet on the record and that its text had not been read, the sentence written while the row was empty. The requires beneath it has since been drafted from the act's own text, so the sentence was no longer true. It is removed and nothing else in the summary changes.

  3946. · a record · the summary of a law

    Before
    S.B. 135 of the 2026 Regular Session was signed on 2026-03-30. The legislature titles it: Protect residents from increased utility costs and utility shortages caused by data centers and clarify authority to regulate data centers. What the act requires is not yet on the record; its text has not been read.
    After
    S.B. 135 of the 2026 Regular Session was signed on 2026-03-30. The legislature titles it: Protect residents from increased utility costs and utility shortages caused by data centers and clarify authority to regulate data centers.
    Why
    The summary said what the act requires was not yet on the record and that its text had not been read, the sentence written while the row was empty. The requires beneath it has since been drafted from the act's own text, so the sentence was no longer true. It is removed and nothing else in the summary changes.

  3947. · a record · the summary of a law

    Before
    H.B. 2992 of the 2026 Regular Session was signed on 2026-05-11. The legislature titles it: Corporation Commission; creating the Data Center Customer Ratepayer Protection Act of 2026; effective date; emergency. What the act requires is not yet on the record; its text has not been read.
    After
    H.B. 2992 of the 2026 Regular Session was signed on 2026-05-11. The legislature titles it: Corporation Commission; creating the Data Center Customer Ratepayer Protection Act of 2026; effective date; emergency.
    Why
    The summary said what the act requires was not yet on the record and that its text had not been read, the sentence written while the row was empty. The requires beneath it has since been drafted from the act's own text, so the sentence was no longer true. It is removed and nothing else in the summary changes.

  3948. · a record · the summary of a law

    Before
    H.B. 424 of the 2025 Regular Session was signed on 2025-05-13. The legislature titles it: Revise taxes for class 17 data center property. What the act requires is not yet on the record; its text has not been read.
    After
    H.B. 424 of the 2025 Regular Session was signed on 2025-05-13. The legislature titles it: Revise taxes for class 17 data center property.
    Why
    The summary said what the act requires was not yet on the record and that its text had not been read, the sentence written while the row was empty. The requires beneath it has since been drafted from the act's own text, so the sentence was no longer true. It is removed and nothing else in the summary changes.

  3949. · a record · the summary of a law

    Before
    S.B. 3410 of the 2026 Regular Session was signed on 2026-04-08. The legislature titles it: City of Brandon and West Rankin Utility Authority; authorize to enter agreements w/data center for water & wastewater infrastructure. What the act requires is not yet on the record; its text has not been read.
    After
    S.B. 3410 of the 2026 Regular Session was signed on 2026-04-08. The legislature titles it: City of Brandon and West Rankin Utility Authority; authorize to enter agreements w/data center for water & wastewater infrastructure.
    Why
    The summary said what the act requires was not yet on the record and that its text had not been read, the sentence written while the row was empty. The requires beneath it has since been drafted from the act's own text, so the sentence was no longer true. It is removed and nothing else in the summary changes.

  3950. · a record · the summary of a law

    Before
    L.D. 912 of the 132nd Legislature was signed on 2025-05-21. The legislature titles it: An Act to Limit the Amount of Electricity That May Be Provided to Data Centers on a Certain Commercial or Industrial Site. What the act requires is not yet on the record; its text has not been read.
    After
    L.D. 912 of the 132nd Legislature was signed on 2025-05-21. The legislature titles it: An Act to Limit the Amount of Electricity That May Be Provided to Data Centers on a Certain Commercial or Industrial Site.
    Why
    The summary said what the act requires was not yet on the record and that its text had not been read, the sentence written while the row was empty. The requires beneath it has since been drafted from the act's own text, so the sentence was no longer true. It is removed and nothing else in the summary changes.

  3951. · a record · the summary of a law

    Before
    L.D. 713 of the 132nd Legislature was signed on 2026-04-14. The legislature titles it: An Act to Exclude Data Centers from the Business Equipment Tax Exemption and the Dirigo Business Incentives Program and to Require the Department of Economic and Community Development to Study Financial Incentives for Data Centers. What the act requires is not yet on the record; its text has not been read.
    After
    L.D. 713 of the 132nd Legislature was signed on 2026-04-14. The legislature titles it: An Act to Exclude Data Centers from the Business Equipment Tax Exemption and the Dirigo Business Incentives Program and to Require the Department of Economic and Community Development to Study Financial Incentives for Data Centers.
    Why
    The summary said what the act requires was not yet on the record and that its text had not been read, the sentence written while the row was empty. The requires beneath it has since been drafted from the act's own text, so the sentence was no longer true. It is removed and nothing else in the summary changes.

  3952. · a record · the summary of a law

    Before
    S.B. 431 of the 2025 Regular Session was signed on 2025-04-10. The legislature titles it: Construction of data center by foreign adversary. What the act requires is not yet on the record; its text has not been read.
    After
    S.B. 431 of the 2025 Regular Session was signed on 2025-04-10. The legislature titles it: Construction of data center by foreign adversary.
    Why
    The summary said what the act requires was not yet on the record and that its text had not been read, the sentence written while the row was empty. The requires beneath it has since been drafted from the act's own text, so the sentence was no longer true. It is removed and nothing else in the summary changes.

  3953. · a record · the summary of a law

    Before
    H. 911 of the 2026 Regular Session was signed on 2026-04-02. The legislature titles it: Adds to existing law to provide for new large loads. What the act requires is not yet on the record; its text has not been read.
    After
    H. 911 of the 2026 Regular Session was signed on 2026-04-02. The legislature titles it: Adds to existing law to provide for new large loads.
    Why
    The summary said what the act requires was not yet on the record and that its text had not been read, the sentence written while the row was empty. The requires beneath it has since been drafted from the act's own text, so the sentence was no longer true. It is removed and nothing else in the summary changes.

  3954. · a record · the summary of a law

    Before
    S.B. 312 of the 153rd General Assembly was signed on 2026-08-26. The legislature titles it: An Act To Amend Title 9, Title 22, And Title 29 Of The Delaware Code Relating To Data Centers. What the act requires is not yet on the record; its text has not been read.
    After
    S.B. 312 of the 153rd General Assembly was signed on 2026-08-26. The legislature titles it: An Act To Amend Title 9, Title 22, And Title 29 Of The Delaware Code Relating To Data Centers.
    Why
    The summary said what the act requires was not yet on the record and that its text had not been read, the sentence written while the row was empty. The requires beneath it was drafted on 2026-09-20 from the bill's text as Delaware serves it; the enacted chapter, Laws of Delaware 85:447, is not yet published, and a correction card waits on it. The sentence is removed and nothing else in the summary changes.

  3955. · a record · the summary of a law

    Before
    S.B. 57 of the 2025-2026 Regular Session was signed on 2025-10-11. The legislature titles it: Electrical corporations: data centers: report. What the act requires is not yet on the record; its text has not been read.
    After
    S.B. 57 of the 2025-2026 Regular Session was signed on 2025-10-11. The legislature titles it: Electrical corporations: data centers: report.
    Why
    The summary said what the act requires was not yet on the record and that its text had not been read, the sentence written while the row was empty. The requires beneath it has since been drafted from the act's own text, so the sentence was no longer true. It is removed and nothing else in the summary changes.

  3956. · a record · the summary of a law

    Before
    S.B. 270 of the 2026 Regular Session was signed on 2026-04-17. The legislature titles it: Electric Utilities; review by Public Service Commission of certain contracts with large load data centers further provided for. What the act requires is not yet on the record; its text has not been read.
    After
    S.B. 270 of the 2026 Regular Session was signed on 2026-04-17. The legislature titles it: Electric Utilities; review by Public Service Commission of certain contracts with large load data centers further provided for.
    Why
    The summary said what the act requires was not yet on the record and that its text had not been read, the sentence written while the row was empty. The requires beneath it has since been drafted from the act's own text, so the sentence was no longer true. It is removed and nothing else in the summary changes.

  3957. · Vantage Fredericksburg · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    The entry is a sentence about Governor Spanberger's Executive Order 22, approved onto this record from a card the framework story was hinted to by its Fredericksburg dateline; it says nothing about Vantage Fredericksburg, whose operational status rests on the operator's own site list read 2026-09-14. Returned to draft on the editor's word, 2026-09-24. The article stays in the record's source list.

  3958. · a record · the law id of a bill

    Before
    no laws row joined
    After
    laws row 45, 2022 Va. Acts ch. 671 (H.B. 791), amending Va. Code 58.1-3500 and adding Va. Code 58.1-3295.3, at /laws/va#hb-791
    Why
    The laws row for this act was published on 2026-09-22 from card 14883 without its join to this bill, so the Virginia page listed the act twice, as a signed bill and again as a law with no bill behind it, and read 23 state laws where the record holds 17 enacted acts. Joined on 2026-09-24 on the editor's word; the law's status now derives from this bill, as it does for every other act on the record.

  3959. · a record · the law id of a bill

    Before
    no laws row joined
    After
    laws row 44, 2016 Va. Acts ch. 712 (S.B. 64), amending Va. Code 58.1-609.3, at /laws/va#sb-64
    Why
    The laws row for this act was published on 2026-09-22 from card 14874 without its join to this bill, so the Virginia page listed the act twice, as a signed bill and again as a law with no bill behind it, and read 23 state laws where the record holds 17 enacted acts. Joined on 2026-09-24 on the editor's word; the law's status now derives from this bill, as it does for every other act on the record.

  3960. · a record · the law id of a bill

    Before
    no laws row joined
    After
    laws row 43, 2022 Va. Acts ch. 672 (S.B. 513), amending Va. Code 58.1-3500 and adding Va. Code 58.1-3295.3, at /laws/va#sb-513
    Why
    The laws row for this act was published on 2026-09-22 from card 14873 without its join to this bill, so the Virginia page listed the act twice, as a signed bill and again as a law with no bill behind it, and read 23 state laws where the record holds 17 enacted acts. Joined on 2026-09-24 on the editor's word; the law's status now derives from this bill, as it does for every other act on the record.

  3961. · a record · the law id of a bill

    Before
    no laws row joined
    After
    laws row 42, 2018 Va. Acts ch. 292 (S.B. 268), amending Va. Code 58.1-3503 and 58.1-3506, at /laws/va#sb-268
    Why
    The laws row for this act was published on 2026-09-22 from card 14872 without its join to this bill, so the Virginia page listed the act twice, as a signed bill and again as a law with no bill behind it, and read 23 state laws where the record holds 17 enacted acts. Joined on 2026-09-24 on the editor's word; the law's status now derives from this bill, as it does for every other act on the record.

  3962. · a record · the law id of a bill

    Before
    no laws row joined
    After
    laws row 41, 2021 Va. Acts Spec. Sess. I ch. 368 (S.B. 1423), amending Va. Code 58.1-609.3, at /laws/va#sb-1423
    Why
    The laws row for this act was published on 2026-09-22 from card 14871 without its join to this bill, so the Virginia page listed the act twice, as a signed bill and again as a law with no bill behind it, and read 23 state laws where the record holds 17 enacted acts. Joined on 2026-09-24 on the editor's word; the law's status now derives from this bill, as it does for every other act on the record.

  3963. · a record · the law id of a bill

    Before
    no laws row joined
    After
    laws row 40, 2015 Va. Acts ch. 92 (S.B. 1142), amending Va. Code 58.1-408 and adding Va. Code 58.1-422.2, at /laws/va#sb-1142
    Why
    The laws row for this act was published on 2026-09-22 from card 14870 without its join to this bill, so the Virginia page listed the act twice, as a signed bill and again as a law with no bill behind it, and read 23 state laws where the record holds 17 enacted acts. Joined on 2026-09-24 on the editor's word; the law's status now derives from this bill, as it does for every other act on the record.

  3964. · a record · the law id of a bill

    Before
    no laws row joined
    After
    laws row 39, 2013 Va. Acts ch. 393 (S.B. 1133), amending Va. Code 58.1-3506, at /laws/va#sb-1133
    Why
    The laws row for this act was published on 2026-09-22 from card 14869 without its join to this bill, so the Virginia page listed the act twice, as a signed bill and again as a law with no bill behind it, and read 23 state laws where the record holds 17 enacted acts. Joined on 2026-09-24 on the editor's word; the law's status now derives from this bill, as it does for every other act on the record.

  3965. · a record · the law id of a bill

    Before
    no laws row joined
    After
    laws row 38, 2016 Va. Acts ch. 343 (H.B. 872), amending Va. Code 58.1-609.3, at /laws/va#hb-872
    Why
    The laws row for this act was published on 2026-09-22 from card 14868 without its join to this bill, so the Virginia page listed the act twice, as a signed bill and again as a law with no bill behind it, and read 23 state laws where the record holds 17 enacted acts. Joined on 2026-09-24 on the editor's word; the law's status now derives from this bill, as it does for every other act on the record.

  3966. · a record · the law id of a bill

    Before
    no laws row joined
    After
    laws row 37, 2018 Va. Acts ch. 28 (H.B. 828), amending Va. Code 58.1-3503 and 58.1-3506, at /laws/va#hb-828
    Why
    The laws row for this act was published on 2026-09-22 from card 14867 without its join to this bill, so the Virginia page listed the act twice, as a signed bill and again as a law with no bill behind it, and read 23 state laws where the record holds 17 enacted acts. Joined on 2026-09-24 on the editor's word; the law's status now derives from this bill, as it does for every other act on the record.

  3967. · a record · the law id of a bill

    Before
    no laws row joined
    After
    laws row 36, 2021 Va. Acts Spec. Sess. I ch. 367 (H.B. 2273), amending Va. Code 58.1-609.3, at /laws/va#hb-2273
    Why
    The laws row for this act was published on 2026-09-22 from card 14866 without its join to this bill, so the Virginia page listed the act twice, as a signed bill and again as a law with no bill behind it, and read 23 state laws where the record holds 17 enacted acts. Joined on 2026-09-24 on the editor's word; the law's status now derives from this bill, as it does for every other act on the record.

  3968. · a record · the law id of a bill

    Before
    no laws row joined
    After
    laws row 35, 2015 Va. Acts ch. 237 (H.B. 2162), amending Va. Code 58.1-408 and adding Va. Code 58.1-422.2, at /laws/va#hb-2162
    Why
    The laws row for this act was published on 2026-09-22 from card 14865 without its join to this bill, so the Virginia page listed the act twice, as a signed bill and again as a law with no bill behind it, and read 23 state laws where the record holds 17 enacted acts. Joined on 2026-09-24 on the editor's word; the law's status now derives from this bill, as it does for every other act on the record.

  3969. · a record · the law id of a bill

    Before
    no laws row joined
    After
    laws row 34, 2013 Va. Acts ch. 271 (H.B. 1699), amending Va. Code 58.1-3506, at /laws/va#hb-1699
    Why
    The laws row for this act was published on 2026-09-22 from card 14864 without its join to this bill, so the Virginia page listed the act twice, as a signed bill and again as a law with no bill behind it, and read 23 state laws where the record holds 17 enacted acts. Joined on 2026-09-24 on the editor's word; the law's status now derives from this bill, as it does for every other act on the record.

  3970. · a record · the requires of a law

    Before
    The act narrows two retail sales tax exemptions for data center equipment by striking replacement server equipment from what counts as eligible server equipment. It places no new duty on a data center, an operator, a utility or a local government: what it changes is what a buyer may claim.
    After
    Under both retail sales tax exemptions for data center equipment, RCW 82.08.986 and RCW 82.08.9861, eligible server equipment is the original server equipment installed in an eligible computer data center, or in the space a qualifying tenant leases there, within the dates each subsection sets. Replacement server equipment remains eligible only for the data centers RCW 82.08.986 qualifies under (f)(i)(C)(I) and (II), and only where it was installed and put into regular use before April 1, 2018 and April 1, 2024 respectively. The act places no new duty on a data center, an operator, a utility or a local government: what it changes is what a buyer may claim.
    Why
    The sentence said the act strikes replacement server equipment, which is read off the language the session law marks deleted. Chapter 266, Laws of 2026 strikes those words from four subsections and keeps them in two; the requires now states what the enacted text makes eligible, read 2026-09-24 from the session law on leg.wa.gov.

  3971. · Virginia · the duplicate mark of a scorecard event

    Before
    null
    After
    1929
    Why
    A background sentence from the News & Advance story of September 19, 2026 on the Data Center Accountability Framework (the governor had earlier proposed and signed an energy consumption tax and pushed a transmission line cost requirement), dated on the article and not an event of that day. The framework is event 1929 (Executive Order 22, September 18), which already cites the story; 2063 follows 2054, the same story's framework line, to it. The editor's word, 2026-09-24.

  3972. · Mark Warner · the topic of a statement

    Before
    data centers
    After
    artificial intelligence
    Why
    The sentence is Senator Warner's concern about AI agents and government safety testing of AI, from a WVVA story whose other lines were about data centers; the admin wrote the card's default tag on it. Retagged so it stays on the record and off the front page's data center pull quotes. The editor's brief of 2026-09-24.

  3973. · Lowell · the duplicate mark of a scorecard event

    Before
    null
    After
    1271
    Why
    The same Lowell City Council action as event 1271 (the 360 day moratorium passed in March 2026), from the GBH story of August 12, 2026, dated on that article. Superseded by 1271, which now carries the March date; the GBH story is cited on 1271. The editor's brief of 2026-09-24.

  3974. · Lowell · the date of a scorecard event

    Before
    2026-09-13
    After
    2026-03-01
    Why
    The cited Boston Herald article of September 13, 2026 says the City Council imposed the moratorium in March; the row read the article's own date as the event's. A month only date is the first of the month (/methodology#dates), so the event is dated March 1, 2026 on the content, with the article's date as the source date. The editor's brief of 2026-09-24.

  3975. · a record · the source url of a law

    Before
    https://legislature.idaho.gov/sessioninfo/2026/legislation/H0911/
    After
    https://legislature.idaho.gov/wp-content/uploads/sessionlaws/sessionlaws_vol2_2026.pdf#page=527
    Why
    The requires on this row was drafted from the introduced bill, H0911.pdf. The enacted text is 2026 Idaho Session Laws, chapter 335, pages 1315 and 1316, approved April 10, 2026, read 2026-09-24; its words match the bill's exactly, so the requires stands and the source now names the enacted text.

  3976. · Google New Florence data center · the merged into of a record

    Before
    google-missouri-ai-hyperscale-campus-mo
    After
    google-new-florence-data-center-mo
    Why
    The same project on two records: the $15 billion Google data center at New Florence, Montgomery County, Missouri (history entry 583 of the retired record says so). Merged into the New Florence record on the editor's word, 2026-09-23; its sources and history moved with it, its name is kept as an alias, and its address redirects. merged google-missouri-ai-hyperscale-campus-mo into google-new-florence-data-center-mo: 3 sources moved, 0 duplicate sources dropped, "Google Missouri AI Hyperscale Campus" kept as an alias

  3977. · Delta Forge 1 · the status of a record

    Before
    under_construction
    After
    rumored
    Why
    The stage was set by timeline entries that were returned to draft on 2026-09-17 (they had been published onto the record while it was still a draft skeleton). With no published entry behind it the record reads rumored until one is approved.

  3978. · Oracle and OpenAI Saline Township Data Center · the status of a record

    Before
    under_construction
    After
    rumored
    Why
    The stage was set by timeline entries that were returned to draft on 2026-09-17 (they had been published onto the record while it was still a draft skeleton). With no published entry behind it the record reads rumored until one is approved.

  3979. · Proposed data center near Mandan · the status of a record

    Before
    under_construction
    After
    rumored
    Why
    The stage was set by timeline entries that were returned to draft on 2026-09-17 (they had been published onto the record while it was still a draft skeleton). With no published entry behind it the record reads rumored until one is approved.

  3980. · Project Jupiter · the status of a record

    Before
    under_construction
    After
    rumored
    Why
    The stage was set by timeline entries that were returned to draft on 2026-09-17 (they had been published onto the record while it was still a draft skeleton). With no published entry behind it the record reads rumored until one is approved.

  3981. · Amazon Web Services Louisiana data centers · the status of a record

    Before
    under_construction
    After
    rumored
    Why
    The stage was set by timeline entries that were returned to draft on 2026-09-17 (they had been published onto the record while it was still a draft skeleton). With no published entry behind it the record reads rumored until one is approved.

  3982. · SpaceX Starbase Louisiana / orbital data center · the status of a record

    Before
    proposed
    After
    rumored
    Why
    The stage was set by timeline entries that were returned to draft on 2026-09-17 (they had been published onto the record while it was still a draft skeleton). With no published entry behind it the record reads rumored until one is approved.

  3983. · Data Center Edgerton · the status of a record

    Before
    proposed
    After
    rumored
    Why
    The stage was set by timeline entries that were returned to draft on 2026-09-17 (they had been published onto the record while it was still a draft skeleton). With no published entry behind it the record reads rumored until one is approved.

  3984. · Grant County Data Center · the status of a record

    Before
    proposed
    After
    rumored
    Why
    The stage was set by timeline entries that were returned to draft on 2026-09-17 (they had been published onto the record while it was still a draft skeleton). With no published entry behind it the record reads rumored until one is approved.

  3985. · DeepGreen Western Passage Underwater AI Data Center · the status of a record

    Before
    permitting
    After
    rumored
    Why
    The stage was set by timeline entries that were returned to draft on 2026-09-17 (they had been published onto the record while it was still a draft skeleton). With no published entry behind it the record reads rumored until one is approved.

  3986. · Frederick County Data Center Expansion · the status of a record

    Before
    permitting
    After
    rumored
    Why
    The stage was set by timeline entries that were returned to draft on 2026-09-17 (they had been published onto the record while it was still a draft skeleton). With no published entry behind it the record reads rumored until one is approved.

  3987. · energiacres-franklin-township-data-center-oh · the status of a record

    Before
    proposed
    After
    rumored
    Why
    The stage was set by timeline entries that were returned to draft on 2026-09-17 (they had been published onto the record while it was still a draft skeleton). With no published entry behind it the record reads rumored until one is approved.

  3988. · Starwood Digital Ventures Mason County Data Center · the status of a record

    Before
    approved
    After
    rumored
    Why
    The stage was set by timeline entries that were returned to draft on 2026-09-17 (they had been published onto the record while it was still a draft skeleton). With no published entry behind it the record reads rumored until one is approved.

  3989. · DC Blox Montgomery data center · the status of a record

    Before
    proposed
    After
    rumored
    Why
    The stage was set by timeline entries that were returned to draft on 2026-09-17 (they had been published onto the record while it was still a draft skeleton). With no published entry behind it the record reads rumored until one is approved.

  3990. · NScale Mason County Data Center · the status of a record

    Before
    approved
    After
    rumored
    Why
    The stage was set by timeline entries that were returned to draft on 2026-09-17 (they had been published onto the record while it was still a draft skeleton). With no published entry behind it the record reads rumored until one is approved.

  3991. · prosper-data-center-500m-tx · the status of a record

    Before
    cancelled
    After
    rumored
    Why
    The stage was set by timeline entries that were returned to draft on 2026-09-17 (they had been published onto the record while it was still a draft skeleton). With no published entry behind it the record reads rumored until one is approved.

  3992. · Amazon / AWS Data Center Campus at Calvert Cliffs · the status of a record

    Before
    cancelled
    After
    rumored
    Why
    The stage was set by timeline entries that were returned to draft on 2026-09-17 (they had been published onto the record while it was still a draft skeleton). With no published entry behind it the record reads rumored until one is approved.

  3993. · St. Louis Armory Data Center · the status of a record

    Before
    under_construction
    After
    rumored
    Why
    The stage was set by timeline entries that were returned to draft on 2026-09-17 (they had been published onto the record while it was still a draft skeleton). With no published entry behind it the record reads rumored until one is approved.

  3994. · Claremore Data Center · the status of a record

    Before
    approved
    After
    rumored
    Why
    The stage was set by timeline entries that were returned to draft on 2026-09-17 (they had been published onto the record while it was still a draft skeleton). With no published entry behind it the record reads rumored until one is approved.

  3995. · Beacon Falls Data Center · the status of a record

    Before
    proposed
    After
    rumored
    Why
    The stage was set by timeline entries that were returned to draft on 2026-09-17 (they had been published onto the record while it was still a draft skeleton). With no published entry behind it the record reads rumored until one is approved.

  3996. · U-M / Los Alamos Data Center (Van Buren Township) · the status of a record

    Before
    proposed
    After
    rumored
    Why
    The stage was set by timeline entries that were returned to draft on 2026-09-17 (they had been published onto the record while it was still a draft skeleton). With no published entry behind it the record reads rumored until one is approved.

  3997. · Eaton Corp. North Little Rock Manufacturing Site · the status of a record

    Before
    proposed
    After
    rumored
    Why
    The stage was set by timeline entries that were returned to draft on 2026-09-17 (they had been published onto the record while it was still a draft skeleton). With no published entry behind it the record reads rumored until one is approved.

  3998. · SpaceXAI Southaven Data Center (Fifth Location) · the status of a record

    Before
    approved
    After
    rumored
    Why
    The stage was set by timeline entries that were returned to draft on 2026-09-17 (they had been published onto the record while it was still a draft skeleton). With no published entry behind it the record reads rumored until one is approved.

  3999. · Parker Data Center · the status of a record

    Before
    under_construction
    After
    rumored
    Why
    The stage was set by timeline entries that were returned to draft on 2026-09-17 (they had been published onto the record while it was still a draft skeleton). With no published entry behind it the record reads rumored until one is approved.

  4000. · Boulder City BLM Land Data Center · the status of a record

    Before
    stalled
    After
    rumored
    Why
    The stage was set by timeline entries that were returned to draft on 2026-09-17 (they had been published onto the record while it was still a draft skeleton). With no published entry behind it the record reads rumored until one is approved.

  4001. · Global AI data center (Weld County) · the status of a record

    Before
    approved
    After
    rumored
    Why
    The stage was set by timeline entries that were returned to draft on 2026-09-17 (they had been published onto the record while it was still a draft skeleton). With no published entry behind it the record reads rumored until one is approved.

  4002. · Homer City Energy Campus Redevelopment · the status of a record

    Before
    under_construction
    After
    rumored
    Why
    The stage was set by timeline entries that were returned to draft on 2026-09-17 (they had been published onto the record while it was still a draft skeleton). With no published entry behind it the record reads rumored until one is approved.

  4003. · Applied Digital Polaris Forge 3 (Oliver County) · the status of a record

    Before
    under_construction
    After
    rumored
    Why
    The stage was set by timeline entries that were returned to draft on 2026-09-17 (they had been published onto the record while it was still a draft skeleton). With no published entry behind it the record reads rumored until one is approved.

  4004. · Leola Data Center · the status of a record

    Before
    permitting
    After
    rumored
    Why
    The stage was set by timeline entries that were returned to draft on 2026-09-17 (they had been published onto the record while it was still a draft skeleton). With no published entry behind it the record reads rumored until one is approved.

  4005. · SENS Longmont Facility · the status of a record

    Before
    operational
    After
    rumored
    Why
    The stage was set by timeline entries that were returned to draft on 2026-09-17 (they had been published onto the record while it was still a draft skeleton). With no published entry behind it the record reads rumored until one is approved.

  4006. · Hillsboro data center projects (7 in permitting) · the status of a record

    Before
    permitting
    After
    rumored
    Why
    The stage was set by timeline entries that were returned to draft on 2026-09-17 (they had been published onto the record while it was still a draft skeleton). With no published entry behind it the record reads rumored until one is approved.

  4007. · Former Star Tribune Printing Plant Data Center · the status of a record

    Before
    cancelled
    After
    rumored
    Why
    The stage was set by timeline entries that were returned to draft on 2026-09-17 (they had been published onto the record while it was still a draft skeleton). With no published entry behind it the record reads rumored until one is approved.

  4008. · Google Barber County Data Center · the status of a record

    Before
    approved
    After
    rumored
    Why
    The stage was set by timeline entries that were returned to draft on 2026-09-17 (they had been published onto the record while it was still a draft skeleton). With no published entry behind it the record reads rumored until one is approved.

  4009. · New York · the rating of a scorecard event

    Before
    case by case
    After
    restrictive
    Why
    The framework is issued under Executive Order No. 62, whose pause of up to a year on permits for new data centers of 50 megawatts or more is still in force (WHEC, 2026-09-15: "amid year long moratorium"). Releasing it does not lift the pause; rated restrictive on the editor's word, 2026-09-23.

  4010. · a record · the publication of a scorecard event

    Before
    published
    After
    draft
    Why
    The exemption survived a debate: nothing changed. Returned to draft 2026-09-23 before the row published.

  4011. · a record · the publication of a scorecard event

    Before
    published
    After
    draft
    Why
    An act of a regional authority, which has no scorecard row; not an act of the state. Returned to draft 2026-09-23 before the row published.

  4012. · a record · the publication of a scorecard event

    Before
    published
    After
    draft
    Why
    A board meeting was held; no act is named. Returned to draft 2026-09-23 before the row published.

  4013. · a record · the publication of a scorecard event

    Before
    published
    After
    draft
    Why
    A market ranking, not an act of the state. Returned to draft 2026-09-23 before the row published.

  4014. · a record · the publication of a scorecard event

    Before
    published
    After
    draft
    Why
    A grid event, not an act of the state. Returned to draft 2026-09-23 before the row published.

  4015. · a record · the publication of a scorecard event

    Before
    published
    After
    draft
    Why
    Residents voting officials out in two states, not an act of the state. Returned to draft 2026-09-23 before the row published.

  4016. · a record · the publication of a scorecard event

    Before
    published
    After
    draft
    Why
    A figure (the exemption's cost), not an act; it belongs with figures. Returned to draft 2026-09-23 before the row published.

  4017. · a record · the publication of a scorecard event

    Before
    published
    After
    draft
    Why
    A statement about tax revenue, not an act. Returned to draft 2026-09-23 before the row published.

  4018. · a record · the publication of a scorecard event

    Before
    published
    After
    draft
    Why
    Residents calling for a change; not an act of the county. Returned to draft 2026-09-23 before the row published.

  4019. · a record · the publication of a scorecard event

    Before
    published
    After
    draft
    Why
    The county is considering a change; not an act. Returned to draft 2026-09-23 before the row published.

  4020. · a record · the publication of a scorecard event

    Before
    published
    After
    draft
    Why
    A proposal by supervisors, not an act of the board; the board's vote is on the row as its own event. Returned to draft 2026-09-23 before the row published.

  4021. · a record · the publication of a scorecard event

    Before
    published
    After
    draft
    Why
    A characterization of federal policy from an article, not a dated act. Returned to draft 2026-09-23 before the row published.

  4022. · a record · the publication of a scorecard event

    Before
    published
    After
    draft
    Why
    A public comment deadline, not an act. Returned to draft 2026-09-23 before the row published.

  4023. · a record · the publication of a scorecard event

    Before
    published
    After
    draft
    Why
    A meeting notice of the Northwest Power and Conservation Council, not an act. Returned to draft 2026-09-23 before the row published.

  4024. · a record · the publication of a scorecard event

    Before
    published
    After
    draft
    Why
    A member of Congress's view, not an act of the federal government; it belongs with statements. Returned to draft 2026-09-23 before the row published.

  4025. · a record · the publication of a scorecard event

    Before
    published
    After
    draft
    Why
    An aside with no date of its own ("previously blocked"); the act it names needs its own dated source. Returned to draft 2026-09-23 before the row published.

  4026. · a record · the publication of a scorecard event

    Before
    published
    After
    draft
    Why
    A plan to introduce legislation in 2027, not an act. Returned to draft 2026-09-23 before the row published.

  4027. · a record · the publication of a scorecard event

    Before
    published
    After
    draft
    Why
    Names Petersburg, which has no scorecard row, and an approval two years before the article with no date of its own. Returned to draft 2026-09-23 before the row published.

  4028. · Prince William County · the scorecard row of a scorecard event

    Before
    VA/virginia
    After
    VA/prince-william-county
    Why
    An act of Prince William County; the row was the state. Moved to the Prince William County row 2026-09-23.

  4029. · United States (federal) · the scorecard row of a scorecard event

    Before
    VA/virginia
    After
    US/united-states
    Why
    A member of Congress's package of federal bills; the row was the state. Moved to the United States row 2026-09-23.

  4030. · Virginia · the scorecard row of a scorecard event

    Before
    VA/loudoun-county
    After
    VA/virginia
    Why
    A penalty secured by the Virginia Department of Environmental Quality, a state agency; the row was Loudoun County. Moved to the Virginia row 2026-09-23.

  4031. · Virginia · the scorecard row of a scorecard event

    Before
    VA/loudoun-county
    After
    VA/virginia
    Why
    A penalty secured by the Virginia Department of Environmental Quality, a state agency; the row was Loudoun County. Moved to the Virginia row 2026-09-23.

  4032. · Virginia · the scorecard row of a scorecard event

    Before
    VA/loudoun-county
    After
    VA/virginia
    Why
    A penalty secured by the Virginia Department of Environmental Quality, a state agency; the row was Loudoun County. Moved to the Virginia row 2026-09-23.

  4033. · Lowell · the scorecard row of a scorecard event

    Before
    MA/massachusetts
    After
    MA/lowell
    Why
    A suit by Lowell residents over the Markley data center in Lowell; the row was the state. Moved to the Lowell row 2026-09-23.

  4034. · Lowell · the scorecard row of a scorecard event

    Before
    MA/massachusetts
    After
    MA/lowell
    Why
    A suit by Lowell residents over the Markley data center in Lowell; the row was the state. Moved to the Lowell row 2026-09-23.

  4035. · Holyoke · the scorecard row of a scorecard event

    Before
    MA/massachusetts
    After
    MA/holyoke
    Why
    The Holyoke City Council's vote; the row was the state. Moved to the Holyoke row 2026-09-23.

  4036. · Lowell · the scorecard row of a scorecard event

    Before
    MA/massachusetts
    After
    MA/lowell
    Why
    A court order on the generators at the Lowell data center; the row was the state. Moved to the Lowell row 2026-09-23.

  4037. · Lowell · the date of a scorecard event

    Before
    2026-09-08
    After
    2026-04-01
    Why
    The sentence dates the act: Lowell residents sued in April, in an article of September 2026. Dated the first of that month; it had carried the article's date.

  4038. · Virginia · the date of a scorecard event

    Before
    2026-09-16
    After
    2026-01-01
    Why
    The sentence dates the act: the General Assembly passed the legislation this year, in an article of September 2026. Dated January 1, 2026; it had carried the article's date.

  4039. · New York · the date of a scorecard event

    Before
    2026-08-19
    After
    2026-07-01
    Why
    The sentence dates the act: Hochul issued the order in July 2026. Dated the first of that month; it had carried the article's date.

  4040. · United States (federal) · the date of a scorecard event

    Before
    2026-09-17
    After
    2026-09-16
    Why
    The sentence dates the act: the House passed the bill on Wednesday, September 16, 2026; it had carried the next day's article date.

  4041. · United States (federal) · the date of a scorecard event

    Before
    2026-09-14
    After
    2026-06-01
    Why
    The sentence dates the act: the order was revoked and replaced in June 2026. Dated the first of that month; it had carried the article's date.

  4042. · Pennsylvania · the date of a scorecard event

    Before
    2026-09-14
    After
    2026-05-01
    Why
    The sentence dates the act: the PUC established the model tariff in May 2026. Dated the first of that month; it had carried the article's date.

  4043. · Pennsylvania · the date of a scorecard event

    Before
    2026-08-11
    After
    2021-01-01
    Why
    The sentence dates the act: the General Assembly first approved the exemption in 2021. Dated January 1 of that year; it had carried the article's date.

  4044. · Massachusetts · the date of a scorecard event

    Before
    2026-09-08
    After
    2026-06-01
    Why
    The sentence dates the act: Healey paused new applications in June 2026. Dated the first of that month; it had carried the article's date.

  4045. · Massachusetts · the date of a scorecard event

    Before
    2026-09-08
    After
    2024-01-01
    Why
    The sentence dates the act: the Legislature approved the tax incentive two years before the article of September 8, 2026. Dated January 1, 2024; it had carried the article's date.

  4046. · Oregon · the date of a scorecard event

    Before
    2026-09-09
    After
    2026-09-08
    Why
    The sentence dates the act: the executive order was issued on September 8, 2026; it had carried the next day's article date.

  4047. · Oregon · the date of a scorecard event

    Before
    2026-09-08
    After
    2025-01-01
    Why
    The sentence dates the act: Kotek signed the POWER Act in 2025. Dated January 1 of the year the text gives; it had carried the article's date.

  4048. · Oregon · the date of a scorecard event

    Before
    2026-09-08
    After
    2026-01-01
    Why
    The sentence dates the act: Kotek convened the advisory committee in January, in an article of September 2026. Dated the first of that month; it had carried the article's date.

  4049. · Oregon · the date of a scorecard event

    Before
    2026-09-09
    After
    2025-06-01
    Why
    The sentence dates the act: the Oregon House passed the bill in June 2025. Dated the first of that month (methodology#dates); it had carried the article's date.

  4050. · Pennsylvania · the summary of a scorecard event

    Before
    PUC established model large-load tariff in May 2026 to ensure customers requiring 50 megawatts or more bear the costs they add to electric system
    After
    PUC established model large load tariff in May 2026 to ensure customers requiring 50 megawatts or more bear the costs they add to electric system
    Why
    A hyphenated compound in the record's own sentence, which the writing rule does not allow, split into words before the row is published; nothing else changed.

  4051. · Spanish Fork · the summary of a scorecard event

    Before
    The Spanish Fork City Council voted to table the ordinance after a six and a-half hour meeting with extensive public comment
    After
    The Spanish Fork City Council voted to table the ordinance after a six and a half hour meeting with extensive public comment
    Why
    A hyphenated compound in the record's own sentence, which the writing rule does not allow, split into words before the row is published; nothing else changed.

  4052. · Wyoming County · the summary of a scorecard event

    Before
    Maximum noise level threshold set at 55 decibels during normal operations for high-intensity nonresidential projects.
    After
    Maximum noise level threshold set at 55 decibels during normal operations for high intensity nonresidential projects.
    Why
    A hyphenated compound in the record's own sentence, which the writing rule does not allow, split into words; nothing else changed. Found when publishing the Wyoming County row stopped the site build on 2026-09-23.

  4053. · Wyoming County · the summary of a scorecard event

    Before
    Wyoming County Planning Commission voted unanimously on a proposed SALDO amendment to regulate high intensity nonresidential land development such as data centers with a 10,000-square-foot threshold.
    After
    Wyoming County Planning Commission voted unanimously on a proposed SALDO amendment to regulate high intensity nonresidential land development such as data centers with a 10,000 square foot threshold.
    Why
    A hyphenated compound in the record's own sentence, which the writing rule does not allow, split into words; nothing else changed. Found when publishing the Wyoming County row stopped the site build on 2026-09-23.

  4054. · Wyoming County · the scorecard row of a scorecard event

    Before
    unknown
    After
    wyoming-county
    Why
    The event names the Wyoming County Commissioners and the county's own ordinance; it had been filed on a placeholder row with no real name. Moved to the Wyoming County row on 2026-09-23.

  4055. · Wyoming County · the scorecard row of a scorecard event

    Before
    unknown
    After
    wyoming-county
    Why
    The event names the Wyoming County Commissioners and the county's own ordinance; it had been filed on a placeholder row with no real name. Moved to the Wyoming County row on 2026-09-23.

  4056. · Wyoming County · the scorecard row of a scorecard event

    Before
    unknown
    After
    wyoming-county
    Why
    The event names the Wyoming County Commissioners and the county's own ordinance; it had been filed on a placeholder row with no real name. Moved to the Wyoming County row on 2026-09-23.

  4057. · a record · the source url of a figure

    Before
    https://google.com/goto?url=CAESjgEB6zswFecK3eaojBwUA6Vi8U-AEWx6ZeNJ9h-ddO-j5NAN_nuIquptHxpxwmaAvy-ZxITnehGYfSJRSSAF5JKWMIMOX-Yk7-xzjWFM_NgBHnPfDj0rMnWe_4_4pLcKTVKtpJEpNpHSGr61RdJBl_qtnseP3n6iBNDnINFDUZ05qt9zxCB0usO8i4l209O-
    After
    https://www.scdailypress.com/2026/09/08/opposition-organizes-data-center-grant-county/
    Why
    The source was a google.com goto redirect, which names no publisher; it now cites the page the redirect leads to. The fact and its date did not change.

  4058. · a record · the source url of a figure

    Before
    https://google.com/goto?url=CAESjgEB6zswFecK3eaojBwUA6Vi8U-AEWx6ZeNJ9h-ddO-j5NAN_nuIquptHxpxwmaAvy-ZxITnehGYfSJRSSAF5JKWMIMOX-Yk7-xzjWFM_NgBHnPfDj0rMnWe_4_4pLcKTVKtpJEpNpHSGr61RdJBl_qtnseP3n6iBNDnINFDUZ05qt9zxCB0usO8i4l209O-
    After
    https://www.scdailypress.com/2026/09/08/opposition-organizes-data-center-grant-county/
    Why
    The source was a google.com goto redirect, which names no publisher; it now cites the page the redirect leads to. The fact and its date did not change.

  4059. · a record · the source url of a figure

    Before
    https://google.com/goto?url=CAESkAEB6zswFTCcC3wZsXii467IeyIHVIc0m9UGlScGtEqt188KIp7hB_NA8RXEfrcSK3_-lkVphU1e3vj4zbdwD3BBOUa5Zy0gQdV0WWhDHyTQyKU-bSsI8FJYdgk9hcuvapo7HCF4VGY8-zpXRVMHKGbGN-Q2PK8_4f9SXoX76gq57qJrPpJeNoPE83KYVSqS8XA
    After
    https://goodauthority.org/news/opposing-ai-data-centers-is-one-thing-americans-agree-on/
    Why
    The source was a google.com goto redirect, which names no publisher; it now cites the page the redirect leads to. The fact and its date did not change.

  4060. · a record · the source url of a figure

    Before
    https://google.com/goto?url=CAESkAEB6zswFTCcC3wZsXii467IeyIHVIc0m9UGlScGtEqt188KIp7hB_NA8RXEfrcSK3_-lkVphU1e3vj4zbdwD3BBOUa5Zy0gQdV0WWhDHyTQyKU-bSsI8FJYdgk9hcuvapo7HCF4VGY8-zpXRVMHKGbGN-Q2PK8_4f9SXoX76gq57qJrPpJeNoPE83KYVSqS8XA
    After
    https://goodauthority.org/news/opposing-ai-data-centers-is-one-thing-americans-agree-on/
    Why
    The source was a google.com goto redirect, which names no publisher; it now cites the page the redirect leads to. The fact and its date did not change.

  4061. · a record · the source url of a figure

    Before
    https://google.com/goto?url=CAESkAEB6zswFTCcC3wZsXii467IeyIHVIc0m9UGlScGtEqt188KIp7hB_NA8RXEfrcSK3_-lkVphU1e3vj4zbdwD3BBOUa5Zy0gQdV0WWhDHyTQyKU-bSsI8FJYdgk9hcuvapo7HCF4VGY8-zpXRVMHKGbGN-Q2PK8_4f9SXoX76gq57qJrPpJeNoPE83KYVSqS8XA
    After
    https://goodauthority.org/news/opposing-ai-data-centers-is-one-thing-americans-agree-on/
    Why
    The source was a google.com goto redirect, which names no publisher; it now cites the page the redirect leads to. The fact and its date did not change.

  4062. · a record · the source url of a figure

    Before
    https://google.com/goto?url=CAESkAEB6zswFTCcC3wZsXii467IeyIHVIc0m9UGlScGtEqt188KIp7hB_NA8RXEfrcSK3_-lkVphU1e3vj4zbdwD3BBOUa5Zy0gQdV0WWhDHyTQyKU-bSsI8FJYdgk9hcuvapo7HCF4VGY8-zpXRVMHKGbGN-Q2PK8_4f9SXoX76gq57qJrPpJeNoPE83KYVSqS8XA
    After
    https://goodauthority.org/news/opposing-ai-data-centers-is-one-thing-americans-agree-on/
    Why
    The source was a google.com goto redirect, which names no publisher; it now cites the page the redirect leads to. The fact and its date did not change.

  4063. · a record · the source url of a figure

    Before
    https://google.com/goto?url=CAESkAEB6zswFTCcC3wZsXii467IeyIHVIc0m9UGlScGtEqt188KIp7hB_NA8RXEfrcSK3_-lkVphU1e3vj4zbdwD3BBOUa5Zy0gQdV0WWhDHyTQyKU-bSsI8FJYdgk9hcuvapo7HCF4VGY8-zpXRVMHKGbGN-Q2PK8_4f9SXoX76gq57qJrPpJeNoPE83KYVSqS8XA
    After
    https://goodauthority.org/news/opposing-ai-data-centers-is-one-thing-americans-agree-on/
    Why
    The source was a google.com goto redirect, which names no publisher; it now cites the page the redirect leads to. The fact and its date did not change.

  4064. · a record · the source url of a figure

    Before
    https://google.com/goto?url=CAESkAEB6zswFTCcC3wZsXii467IeyIHVIc0m9UGlScGtEqt188KIp7hB_NA8RXEfrcSK3_-lkVphU1e3vj4zbdwD3BBOUa5Zy0gQdV0WWhDHyTQyKU-bSsI8FJYdgk9hcuvapo7HCF4VGY8-zpXRVMHKGbGN-Q2PK8_4f9SXoX76gq57qJrPpJeNoPE83KYVSqS8XA
    After
    https://goodauthority.org/news/opposing-ai-data-centers-is-one-thing-americans-agree-on/
    Why
    The source was a google.com goto redirect, which names no publisher; it now cites the page the redirect leads to. The fact and its date did not change.

  4065. · a record · the source url of a figure

    Before
    https://google.com/goto?url=CAESkAEB6zswFTCcC3wZsXii467IeyIHVIc0m9UGlScGtEqt188KIp7hB_NA8RXEfrcSK3_-lkVphU1e3vj4zbdwD3BBOUa5Zy0gQdV0WWhDHyTQyKU-bSsI8FJYdgk9hcuvapo7HCF4VGY8-zpXRVMHKGbGN-Q2PK8_4f9SXoX76gq57qJrPpJeNoPE83KYVSqS8XA
    After
    https://goodauthority.org/news/opposing-ai-data-centers-is-one-thing-americans-agree-on/
    Why
    The source was a google.com goto redirect, which names no publisher; it now cites the page the redirect leads to. The fact and its date did not change.

  4066. · a record · the source url of a figure

    Before
    https://google.com/goto?url=CAESkAEB6zswFTCcC3wZsXii467IeyIHVIc0m9UGlScGtEqt188KIp7hB_NA8RXEfrcSK3_-lkVphU1e3vj4zbdwD3BBOUa5Zy0gQdV0WWhDHyTQyKU-bSsI8FJYdgk9hcuvapo7HCF4VGY8-zpXRVMHKGbGN-Q2PK8_4f9SXoX76gq57qJrPpJeNoPE83KYVSqS8XA
    After
    https://goodauthority.org/news/opposing-ai-data-centers-is-one-thing-americans-agree-on/
    Why
    The source was a google.com goto redirect, which names no publisher; it now cites the page the redirect leads to. The fact and its date did not change.

  4067. · a record · the source url of a figure

    Before
    https://google.com/goto?url=CAESkAEB6zswFTCcC3wZsXii467IeyIHVIc0m9UGlScGtEqt188KIp7hB_NA8RXEfrcSK3_-lkVphU1e3vj4zbdwD3BBOUa5Zy0gQdV0WWhDHyTQyKU-bSsI8FJYdgk9hcuvapo7HCF4VGY8-zpXRVMHKGbGN-Q2PK8_4f9SXoX76gq57qJrPpJeNoPE83KYVSqS8XA
    After
    https://goodauthority.org/news/opposing-ai-data-centers-is-one-thing-americans-agree-on/
    Why
    The source was a google.com goto redirect, which names no publisher; it now cites the page the redirect leads to. The fact and its date did not change.

  4068. · a record · the source url of a figure

    Before
    https://google.com/goto?url=CAESkAEB6zswFTCcC3wZsXii467IeyIHVIc0m9UGlScGtEqt188KIp7hB_NA8RXEfrcSK3_-lkVphU1e3vj4zbdwD3BBOUa5Zy0gQdV0WWhDHyTQyKU-bSsI8FJYdgk9hcuvapo7HCF4VGY8-zpXRVMHKGbGN-Q2PK8_4f9SXoX76gq57qJrPpJeNoPE83KYVSqS8XA
    After
    https://goodauthority.org/news/opposing-ai-data-centers-is-one-thing-americans-agree-on/
    Why
    The source was a google.com goto redirect, which names no publisher; it now cites the page the redirect leads to. The fact and its date did not change.

  4069. · a record · the source url of a figure

    Before
    https://google.com/goto?url=CAESmQEB6zswFZc_uXyLfYh_Bxg6lg72LBCSpPoM-cnaTPyFTglyMZc8-mUGXvRVQOu8M-CwUWIL8xDInZupkRDRVqI0fsSfi3jxtYsIrxsud2bRYW-pZ2bNSwXD9PHTELqJIF56stMlw38FlKheLOTwWUhGYyk1VrhWfJDpIx0ubVBVb5Tws-VNW8I_RUhBY4DL_nAaKR3573WECSo
    After
    https://www.realtor.com/news/real-estate-news/federal-data-center-tax-senator-wyden-energy-costs/
    Why
    The source was a google.com goto redirect, which names no publisher; it now cites the page the redirect leads to. The fact and its date did not change.

  4070. · a record · the source url of a figure

    Before
    https://google.com/goto?url=CAESmQEB6zswFZc_uXyLfYh_Bxg6lg72LBCSpPoM-cnaTPyFTglyMZc8-mUGXvRVQOu8M-CwUWIL8xDInZupkRDRVqI0fsSfi3jxtYsIrxsud2bRYW-pZ2bNSwXD9PHTELqJIF56stMlw38FlKheLOTwWUhGYyk1VrhWfJDpIx0ubVBVb5Tws-VNW8I_RUhBY4DL_nAaKR3573WECSo
    After
    https://www.realtor.com/news/real-estate-news/federal-data-center-tax-senator-wyden-energy-costs/
    Why
    The source was a google.com goto redirect, which names no publisher; it now cites the page the redirect leads to. The fact and its date did not change.

  4071. · Allyson Siwik · the source url of a statement

    Before
    https://google.com/goto?url=CAESjgEB6zswFecK3eaojBwUA6Vi8U-AEWx6ZeNJ9h-ddO-j5NAN_nuIquptHxpxwmaAvy-ZxITnehGYfSJRSSAF5JKWMIMOX-Yk7-xzjWFM_NgBHnPfDj0rMnWe_4_4pLcKTVKtpJEpNpHSGr61RdJBl_qtnseP3n6iBNDnINFDUZ05qt9zxCB0usO8i4l209O-
    After
    https://www.scdailypress.com/2026/09/08/opposition-organizes-data-center-grant-county/
    Why
    The source was a google.com goto redirect, which names no publisher; it now cites the page the redirect leads to. The fact and its date did not change.

  4072. · Gila Resources Information Project · the source url of a statement

    Before
    https://google.com/goto?url=CAESjgEB6zswFecK3eaojBwUA6Vi8U-AEWx6ZeNJ9h-ddO-j5NAN_nuIquptHxpxwmaAvy-ZxITnehGYfSJRSSAF5JKWMIMOX-Yk7-xzjWFM_NgBHnPfDj0rMnWe_4_4pLcKTVKtpJEpNpHSGr61RdJBl_qtnseP3n6iBNDnINFDUZ05qt9zxCB0usO8i4l209O-
    After
    https://www.scdailypress.com/2026/09/08/opposition-organizes-data-center-grant-county/
    Why
    The source was a google.com goto redirect, which names no publisher; it now cites the page the redirect leads to. The fact and its date did not change.

  4073. · Ron Wyden · the source url of a statement

    Before
    https://google.com/goto?url=CAESmQEB6zswFZc_uXyLfYh_Bxg6lg72LBCSpPoM-cnaTPyFTglyMZc8-mUGXvRVQOu8M-CwUWIL8xDInZupkRDRVqI0fsSfi3jxtYsIrxsud2bRYW-pZ2bNSwXD9PHTELqJIF56stMlw38FlKheLOTwWUhGYyk1VrhWfJDpIx0ubVBVb5Tws-VNW8I_RUhBY4DL_nAaKR3573WECSo
    After
    https://www.realtor.com/news/real-estate-news/federal-data-center-tax-senator-wyden-energy-costs/
    Why
    The source was a google.com goto redirect, which names no publisher; it now cites the page the redirect leads to. The fact and its date did not change.

  4074. · Ron Wyden · the source url of a statement

    Before
    https://google.com/goto?url=CAESmQEB6zswFZc_uXyLfYh_Bxg6lg72LBCSpPoM-cnaTPyFTglyMZc8-mUGXvRVQOu8M-CwUWIL8xDInZupkRDRVqI0fsSfi3jxtYsIrxsud2bRYW-pZ2bNSwXD9PHTELqJIF56stMlw38FlKheLOTwWUhGYyk1VrhWfJDpIx0ubVBVb5Tws-VNW8I_RUhBY4DL_nAaKR3573WECSo
    After
    https://www.realtor.com/news/real-estate-news/federal-data-center-tax-senator-wyden-energy-costs/
    Why
    The source was a google.com goto redirect, which names no publisher; it now cites the page the redirect leads to. The fact and its date did not change.

  4075. · Ohio · the source url of a scorecard event

    Before
    https://google.com/goto?url=CAESmQEB6zswFZc_uXyLfYh_Bxg6lg72LBCSpPoM-cnaTPyFTglyMZc8-mUGXvRVQOu8M-CwUWIL8xDInZupkRDRVqI0fsSfi3jxtYsIrxsud2bRYW-pZ2bNSwXD9PHTELqJIF56stMlw38FlKheLOTwWUhGYyk1VrhWfJDpIx0ubVBVb5Tws-VNW8I_RUhBY4DL_nAaKR3573WECSo
    After
    https://www.realtor.com/news/real-estate-news/federal-data-center-tax-senator-wyden-energy-costs/
    Why
    The source was a google.com goto redirect, which names no publisher; it now cites the page the redirect leads to. The fact and its date did not change.

  4076. · Salem · the source url of a scorecard event

    Before
    https://google.com/goto?url=CAESpgEB6zswFfWPVgb60AXHLzZg1qZXSSPb7PIErJYACAvdDdztO422xslmoFuQMARsO6b4Ox7pLfzMAP8T3S7CwocO6XaozjdT9LJ8Wx8r2HiEr3iuqhzkx3i7kwY6ltKn4G5ES8uZ2tr_kMo1Eozn1KIOI5j0zX0Nd-pejRn3ABZf3_rr6lLJMjLl_XzqkLjKFxh1S7hTrGwaEodaKGxH4mAjMlqCKSrz
    After
    https://www.statesmanjournal.com/story/news/local/2026/09/08/salem-town-halls-data-centers-policy/91658873007/
    Why
    The source was a google.com goto redirect, which names no publisher; it now cites the page the redirect leads to. The fact and its date did not change.

  4077. · Salem · the source url of a scorecard event

    Before
    https://google.com/goto?url=CAESpgEB6zswFfWPVgb60AXHLzZg1qZXSSPb7PIErJYACAvdDdztO422xslmoFuQMARsO6b4Ox7pLfzMAP8T3S7CwocO6XaozjdT9LJ8Wx8r2HiEr3iuqhzkx3i7kwY6ltKn4G5ES8uZ2tr_kMo1Eozn1KIOI5j0zX0Nd-pejRn3ABZf3_rr6lLJMjLl_XzqkLjKFxh1S7hTrGwaEodaKGxH4mAjMlqCKSrz
    After
    https://www.statesmanjournal.com/story/news/local/2026/09/08/salem-town-halls-data-centers-policy/91658873007/
    Why
    The source was a google.com goto redirect, which names no publisher; it now cites the page the redirect leads to. The fact and its date did not change.

  4078. · Salem · the source url of a scorecard event

    Before
    https://google.com/goto?url=CAESpgEB6zswFfWPVgb60AXHLzZg1qZXSSPb7PIErJYACAvdDdztO422xslmoFuQMARsO6b4Ox7pLfzMAP8T3S7CwocO6XaozjdT9LJ8Wx8r2HiEr3iuqhzkx3i7kwY6ltKn4G5ES8uZ2tr_kMo1Eozn1KIOI5j0zX0Nd-pejRn3ABZf3_rr6lLJMjLl_XzqkLjKFxh1S7hTrGwaEodaKGxH4mAjMlqCKSrz
    After
    https://www.statesmanjournal.com/story/news/local/2026/09/08/salem-town-halls-data-centers-policy/91658873007/
    Why
    The source was a google.com goto redirect, which names no publisher; it now cites the page the redirect leads to. The fact and its date did not change.

  4079. · Salem · the source url of a scorecard event

    Before
    https://google.com/goto?url=CAESpgEB6zswFfWPVgb60AXHLzZg1qZXSSPb7PIErJYACAvdDdztO422xslmoFuQMARsO6b4Ox7pLfzMAP8T3S7CwocO6XaozjdT9LJ8Wx8r2HiEr3iuqhzkx3i7kwY6ltKn4G5ES8uZ2tr_kMo1Eozn1KIOI5j0zX0Nd-pejRn3ABZf3_rr6lLJMjLl_XzqkLjKFxh1S7hTrGwaEodaKGxH4mAjMlqCKSrz
    After
    https://www.statesmanjournal.com/story/news/local/2026/09/08/salem-town-halls-data-centers-policy/91658873007/
    Why
    The source was a google.com goto redirect, which names no publisher; it now cites the page the redirect leads to. The fact and its date did not change.

  4080. · Oakline at Mill Creek · the source url of a timeline entry

    Before
    https://google.com/goto?url=CAESpgEB6zswFfWPVgb60AXHLzZg1qZXSSPb7PIErJYACAvdDdztO422xslmoFuQMARsO6b4Ox7pLfzMAP8T3S7CwocO6XaozjdT9LJ8Wx8r2HiEr3iuqhzkx3i7kwY6ltKn4G5ES8uZ2tr_kMo1Eozn1KIOI5j0zX0Nd-pejRn3ABZf3_rr6lLJMjLl_XzqkLjKFxh1S7hTrGwaEodaKGxH4mAjMlqCKSrz
    After
    https://www.statesmanjournal.com/story/news/local/2026/09/08/salem-town-halls-data-centers-policy/91658873007/
    Why
    The source was a google.com goto redirect, which names no publisher; it now cites the page the redirect leads to. The fact and its date did not change.

  4081. · DRFortress · the publication of a statement

    Before
    false
    After
    true
    Why
    The statement names drfortress-hi, which is a draft record, so no page can carry it and the build refuses it. Returned to draft 2026-09-22 until the record is approved; the words are unchanged.

  4082. · DRFortress · the publication of a statement

    Before
    false
    After
    true
    Why
    The statement names drfortress-hi, which is a draft record, so no page can carry it and the build refuses it. Returned to draft 2026-09-22 until the record is approved; the words are unchanged.

  4083. · h5-virginia-va · the record link of a statement

    Before
    h5-virginia-va
    After
    Why
    The statement is about Virginia legislation, a utility or the governor's framework, not about the H5 facility at Chantilly. Its card carried this slug through the alias "Virginia" the operator census of 2026-09-14 had put on the record, removed 2026-09-21. The statement itself is unchanged. Repair of 2026-09-22.

  4084. · h5-virginia-va · the record link of a statement

    Before
    h5-virginia-va
    After
    Why
    The statement is about Virginia legislation, a utility or the governor's framework, not about the H5 facility at Chantilly. Its card carried this slug through the alias "Virginia" the operator census of 2026-09-14 had put on the record, removed 2026-09-21. The statement itself is unchanged. Repair of 2026-09-22.

  4085. · h5-virginia-va · the record link of a statement

    Before
    h5-virginia-va
    After
    Why
    The statement is about Virginia legislation, a utility or the governor's framework, not about the H5 facility at Chantilly. Its card carried this slug through the alias "Virginia" the operator census of 2026-09-14 had put on the record, removed 2026-09-21. The statement itself is unchanged. Repair of 2026-09-22.

  4086. · h5-virginia-va · the record link of a statement

    Before
    h5-virginia-va
    After
    Why
    The statement is about Virginia legislation, a utility or the governor's framework, not about the H5 facility at Chantilly. Its card carried this slug through the alias "Virginia" the operator census of 2026-09-14 had put on the record, removed 2026-09-21. The statement itself is unchanged. Repair of 2026-09-22.

  4087. · h5-virginia-va · the record link of a statement

    Before
    h5-virginia-va
    After
    Why
    The statement is about Virginia legislation, a utility or the governor's framework, not about the H5 facility at Chantilly. Its card carried this slug through the alias "Virginia" the operator census of 2026-09-14 had put on the record, removed 2026-09-21. The statement itself is unchanged. Repair of 2026-09-22.

  4088. · h5-virginia-va · the record link of a statement

    Before
    h5-virginia-va
    After
    Why
    The statement is about Virginia legislation, a utility or the governor's framework, not about the H5 facility at Chantilly. Its card carried this slug through the alias "Virginia" the operator census of 2026-09-14 had put on the record, removed 2026-09-21. The statement itself is unchanged. Repair of 2026-09-22.

  4089. · h5-virginia-va · the record link of a statement

    Before
    h5-virginia-va
    After
    Why
    The statement is about Virginia legislation, a utility or the governor's framework, not about the H5 facility at Chantilly. Its card carried this slug through the alias "Virginia" the operator census of 2026-09-14 had put on the record, removed 2026-09-21. The statement itself is unchanged. Repair of 2026-09-22.

  4090. · h5-virginia-va · the record link of a statement

    Before
    h5-virginia-va
    After
    Why
    The statement is about Virginia legislation, a utility or the governor's framework, not about the H5 facility at Chantilly. Its card carried this slug through the alias "Virginia" the operator census of 2026-09-14 had put on the record, removed 2026-09-21. The statement itself is unchanged. Repair of 2026-09-22.

  4091. · h5-virginia-va · the record link of a statement

    Before
    h5-virginia-va
    After
    Why
    The statement is about Virginia legislation, a utility or the governor's framework, not about the H5 facility at Chantilly. Its card carried this slug through the alias "Virginia" the operator census of 2026-09-14 had put on the record, removed 2026-09-21. The statement itself is unchanged. Repair of 2026-09-22.

  4092. · h5-virginia-va · the record link of a statement

    Before
    h5-virginia-va
    After
    Why
    The statement is about Virginia legislation, a utility or the governor's framework, not about the H5 facility at Chantilly. Its card carried this slug through the alias "Virginia" the operator census of 2026-09-14 had put on the record, removed 2026-09-21. The statement itself is unchanged. Repair of 2026-09-22.

  4093. · h5-virginia-va · the record link of a statement

    Before
    h5-virginia-va
    After
    Why
    The statement is about Virginia legislation, a utility or the governor's framework, not about the H5 facility at Chantilly. Its card carried this slug through the alias "Virginia" the operator census of 2026-09-14 had put on the record, removed 2026-09-21. The statement itself is unchanged. Repair of 2026-09-22.

  4094. · h5-virginia-va · the record link of a statement

    Before
    h5-virginia-va
    After
    Why
    The statement is about Virginia legislation, a utility or the governor's framework, not about the H5 facility at Chantilly. Its card carried this slug through the alias "Virginia" the operator census of 2026-09-14 had put on the record, removed 2026-09-21. The statement itself is unchanged. Repair of 2026-09-22.

  4095. · h5-virginia-va · the record link of a statement

    Before
    h5-virginia-va
    After
    Why
    The statement is about Virginia legislation, a utility or the governor's framework, not about the H5 facility at Chantilly. Its card carried this slug through the alias "Virginia" the operator census of 2026-09-14 had put on the record, removed 2026-09-21. The statement itself is unchanged. Repair of 2026-09-22.

  4096. · h5-virginia-va · the record link of a statement

    Before
    h5-virginia-va
    After
    Why
    The statement is about Virginia legislation, a utility or the governor's framework, not about the H5 facility at Chantilly. Its card carried this slug through the alias "Virginia" the operator census of 2026-09-14 had put on the record, removed 2026-09-21. The statement itself is unchanged. Repair of 2026-09-22.

  4097. · h5-virginia-va · the record link of a statement

    Before
    h5-virginia-va
    After
    Why
    The statement is about Virginia legislation, a utility or the governor's framework, not about the H5 facility at Chantilly. Its card carried this slug through the alias "Virginia" the operator census of 2026-09-14 had put on the record, removed 2026-09-21. The statement itself is unchanged. Repair of 2026-09-22.

  4098. · h5-virginia-va · the record link of a statement

    Before
    h5-virginia-va
    After
    Why
    The statement is about Virginia legislation, a utility or the governor's framework, not about the H5 facility at Chantilly. Its card carried this slug through the alias "Virginia" the operator census of 2026-09-14 had put on the record, removed 2026-09-21. The statement itself is unchanged. Repair of 2026-09-22.

  4099. · a record · the summary of a law

    Before
    S.B. 2128 of the 114th General Assembly was signed on 2026-05-18. The legislature titles it: AN ACT to amend Tennessee Code Annotated, Title 5; Title 6; Title 7; Title 13 and Title 65, relative to data centers. What the act requires is not yet on the record; its text has not been read.
    After
    S.B. 2128 of the 114th General Assembly was substituted by the Senate on 2026-04-22 for its House companion H.B. 1847, which was approved by the Governor on 2026-05-07 and assigned Public Chapter 961 by the Secretary of State on 2026-05-18. S.B. 2128 has no chapter of its own. The legislature titles it: AN ACT to amend Tennessee Code Annotated, Title 5; Title 6; Title 7; Title 13 and Title 65, relative to data centers. What it requires was read from Public Chapter 961 as filed with the Secretary of State.
    Why
    The summary said the act's text had not been read, and it also left the reader to assume S.B. 2128 became a chapter of its own, which it did not. Corrected 2026-09-21 from Public Chapter 961 and the legislature's own bill pages. This summary no longer renders on /laws/tn, since the entry shows the anchor's, but it is still in the CSV and the JSON.

  4100. · a record · the summary of a law

    Before
    H.B. 1847 of the 114th General Assembly was signed on 2026-05-18. The legislature titles it: AN ACT to amend Tennessee Code Annotated, Title 5; Title 6; Title 7; Title 13 and Title 65, relative to data centers. What the act requires is not yet on the record; its text has not been read.
    After
    H.B. 1847 of the 114th General Assembly was approved by the Governor on 2026-05-07 and assigned Public Chapter 961 by the Secretary of State on 2026-05-18, the Senate having substituted it for its companion S.B. 2128. The legislature titles it: AN ACT to amend Tennessee Code Annotated, Title 5; Title 6; Title 7; Title 13 and Title 65, relative to data centers. What it requires was read from Public Chapter 961 as filed with the Secretary of State.
    Why
    The summary said the act's text had not been read, directly above the requires block that says what it requires. The text was read from Public Chapter 961 and the row has carried the reading since; the sentence had not been updated. Corrected 2026-09-21.

  4101. · a record · the companion of of a law

    Before
    After
    28
    Why
    H.B. 1847 and S.B. 2128 of the 114th General Assembly are one act. The Senate substituted the House bill on 2026-04-22 and the Secretary of State assigned Public Chapter 961 to H.B. 1847 alone; S.B. 2128 has no chapter of its own. Linked on 2026-09-21 after reading Public Chapter 961 from publications.tnsosfiles.com and both bill pages from wapp.capitol.tn.gov, so the laws page renders the measure once.

  4102. · h5-virginia-va · the record link of a statement

    Before
    h5-virginia-va
    After
    Why
    The statement is about Virginia legislation or utilities, not about the H5 facility at Chantilly. It carried this slug because the record holds the alias "Virginia", taken from a page heading by the operator census of 2026-09-14. The statement itself is unchanged.

  4103. · h5-virginia-va · the record link of a statement

    Before
    h5-virginia-va
    After
    Why
    The statement is about Virginia legislation or utilities, not about the H5 facility at Chantilly. It carried this slug because the record holds the alias "Virginia", taken from a page heading by the operator census of 2026-09-14. The statement itself is unchanged.

  4104. · h5-virginia-va · the record link of a statement

    Before
    h5-virginia-va
    After
    Why
    The statement is about Virginia legislation or utilities, not about the H5 facility at Chantilly. It carried this slug because the record holds the alias "Virginia", taken from a page heading by the operator census of 2026-09-14. The statement itself is unchanged.

  4105. · h5-virginia-va · the record link of a statement

    Before
    h5-virginia-va
    After
    Why
    The statement is about Virginia legislation or utilities, not about the H5 facility at Chantilly. It carried this slug because the record holds the alias "Virginia", taken from a page heading by the operator census of 2026-09-14. The statement itself is unchanged.

  4106. · h5-virginia-va · the record link of a statement

    Before
    h5-virginia-va
    After
    Why
    The statement is about Virginia legislation or utilities, not about the H5 facility at Chantilly. It carried this slug because the record holds the alias "Virginia", taken from a page heading by the operator census of 2026-09-14. The statement itself is unchanged.

  4107. · h5-virginia-va · the record link of a statement

    Before
    h5-virginia-va
    After
    Why
    The statement is about Virginia legislation or utilities, not about the H5 facility at Chantilly. It carried this slug because the record holds the alias "Virginia", taken from a page heading by the operator census of 2026-09-14. The statement itself is unchanged.

  4108. · h5-virginia-va · the record link of a statement

    Before
    h5-virginia-va
    After
    Why
    The statement is about Virginia legislation or utilities, not about the H5 facility at Chantilly. It carried this slug because the record holds the alias "Virginia", taken from a page heading by the operator census of 2026-09-14. The statement itself is unchanged.

  4109. · h5-virginia-va · the record link of a statement

    Before
    h5-virginia-va
    After
    Why
    The statement is about Virginia legislation or utilities, not about the H5 facility at Chantilly. It carried this slug because the record holds the alias "Virginia", taken from a page heading by the operator census of 2026-09-14. The statement itself is unchanged.

  4110. · h5-virginia-va · the record link of a statement

    Before
    h5-virginia-va
    After
    Why
    The statement is about Virginia legislation or utilities, not about the H5 facility at Chantilly. It carried this slug because the record holds the alias "Virginia", taken from a page heading by the operator census of 2026-09-14. The statement itself is unchanged.

  4111. · h5-virginia-va · the record link of a statement

    Before
    h5-virginia-va
    After
    Why
    The statement is about Virginia legislation or utilities, not about the H5 facility at Chantilly. It carried this slug because the record holds the alias "Virginia", taken from a page heading by the operator census of 2026-09-14. The statement itself is unchanged.

  4112. · h5-virginia-va · the record link of a statement

    Before
    h5-virginia-va
    After
    Why
    The statement is about Virginia legislation or utilities, not about the H5 facility at Chantilly. It carried this slug because the record holds the alias "Virginia", taken from a page heading by the operator census of 2026-09-14. The statement itself is unchanged.

  4113. · h5-virginia-va · the record link of a statement

    Before
    h5-virginia-va
    After
    Why
    The statement is about Virginia legislation or utilities, not about the H5 facility at Chantilly. It carried this slug because the record holds the alias "Virginia", taken from a page heading by the operator census of 2026-09-14. The statement itself is unchanged.

  4114. · h5-virginia-va · the record link of a statement

    Before
    h5-virginia-va
    After
    Why
    The statement is about Virginia legislation or utilities, not about the H5 facility at Chantilly. It carried this slug because the record holds the alias "Virginia", taken from a page heading by the operator census of 2026-09-14. The statement itself is unchanged.

  4115. · h5-virginia-va · the record link of a statement

    Before
    h5-virginia-va
    After
    Why
    The statement is about Virginia legislation or utilities, not about the H5 facility at Chantilly. It carried this slug because the record holds the alias "Virginia", taken from a page heading by the operator census of 2026-09-14. The statement itself is unchanged.

  4116. · h5-virginia-va · the record link of a statement

    Before
    h5-virginia-va
    After
    Why
    The statement is about Virginia legislation or utilities, not about the H5 facility at Chantilly. It carried this slug because the record holds the alias "Virginia", taken from a page heading by the operator census of 2026-09-14. The statement itself is unchanged.

  4117. · a record · the official url of a bill

    Before
    https://alison.legislature.state.al.us/bill-search
    After
    https://alison.legislature.state.al.us/files/pdf/SearchableInstruments/2026RS/SB270-enr.pdf
    Why
    The citation was ALISON's search form, which names no act. It is now the enrolled act on the legislature's own server, read 2026-09-20 and kept under data/archive/bills.

  4118. · Franklin County data center proposal · the source url of a timeline entry

    Before
    https://news.google.com/rss/articles/CBMihAFBVV95cUxQZ1BKTTBxTnlzX1p1UmN4Y0ttcnVBUXVGd1VYXzVkUjJzdGFYdUk4MGhuNTZsRC1SeG9ZVjE0a2Y1dGh2OXJ2SklNcktXU2xOR1B1ZWl4dFdNa3owbHRpQXhZQ05USDRoaGJnUGNMZTgtYS1aNWpkQ24xX3NGMVN6M1B4cmzSAZgBQVVfeXFMT3E3V2dyS1pCRzJxOFoyRmpoSmJxZTJrNGRVNWRNQ2JjQlg4bDgyZGNOa01vZGhZZEczSXVZajZZZWhwNy12RmtfcjJsWHRaX01IR2IwdjJGdW1iWHp6UTBXWnItU2xXbndqMU9scjk1YzBfYXZoSzdKcGlETTlqUHJWYk5iRG1fdGtHZ0xWdVRFQjgyWWMxb00?oc=5
    After
    https://www.wdbj7.com/2026/08/17/data-center-proposal-dropped-franklin-county/
    Why
    The source was a news.google.com wrapper url, which names no publisher and does not last. Resolved to the publisher's own page by the monitor's resolver on 2026-09-20 (docs/batch-va-record-fixes-0920.md, item 3). The outlet and the date on the row are unchanged.

  4119. · Iron Horse data center campus · the source url of a timeline entry

    Before
    https://news.google.com/rss/articles/CBMilgFBVV95cUxQMk1WLWRIdU04eXdkT1NINHV4WHdjSjBxcV9OSUJxb0RrempxZzUwX29sVEF4SzMzaURnYVp2a1dDY0N5T010Vnc0YjlST1o0MTdmV1l5WnpNMzZ5SFlCZmd4d0pQbmhtRHlwMUlOQTdBanZGVEdoWlNSQkp0QURXTVNLUFdobkhiU21HTWhPRXpNWFI2ZUHSAZsBQVVfeXFMT1ZIRXJlYUwzTmJMZUFpUUtsOXQ4VHRtdHVmN01YX1JHOFZBMm4ydEozWXdWZmh6N3ZzMFduaUxYeDliaTdscnBibW13ODY4NF9YcmZVMzl6VURzQ0l6ZDAwZlFEY3RfTzZuY1NLZHhfckc0U3Y4dDUzc1FwRFBfZXlnR19nN1VUNldIcmNvZnlhVGZuVE1pVGptUDQ?oc=5
    After
    https://www.wric.com/news/local-news/hanover-county/hanover-planning-commission-iron-horse/
    Why
    The source was a news.google.com wrapper url, which names no publisher and does not last. Resolved to the publisher's own page by the monitor's resolver on 2026-09-20 (docs/batch-va-record-fixes-0920.md, item 3). The outlet and the date on the row are unchanged.

  4120. · Stafford County data center complex · the source url of a timeline entry

    Before
    https://news.google.com/rss/articles/CBMi7wFBVV95cUxOSGdyLUk1OVBGQXhWMU1MV3BScjNhanE1TGxXa1JnRnp2amJXTnFYMnFwSkhZcFRka2gzdS1sLU8xNWdvY0xLRGRPMjdsZUFVRlhkc3ZXeUQ4LXlZOTZNeTZjTllPWVlHWDFZTU03R3VuZXZqdUNoY0NRQkVPSnFOUDFMaDV0ZVZWM2RpMkZES2I2OTVGcUFvaTllck9USnhOd1VaVE5VTUlsZ284RUpLY0xOU1hjbDhHSHp2VlNyNzEzTG8xTmlhbEtqVUNqRTF6LUIweXpRUVllMFJHelU1RElsTEpNczlLWWJHV0FPQQ?oc=5
    After
    https://wjla.com/news/local/stafford-county-virginia-planning-commission-greenlights-another-data-center-properties-taxes-homeowners-communities-neighborhoods
    Why
    The source was a news.google.com wrapper url, which names no publisher and does not last. Resolved to the publisher's own page by the monitor's resolver on 2026-09-20 (docs/batch-va-record-fixes-0920.md, item 3). The outlet and the date on the row are unchanged.

  4121. · CyrusOne Sterling · the summary of a timeline entry

    Before
    CyrusOne lists CyrusOne Sterling NVA1-NVA3, CyrusOne Sterling NVA4, CyrusOne Sterling NVA5-NVA7, CyrusOne Sterling NVA8, CyrusOne Sterling NVA9 at Sterling, Virginia on its own page of data center locations, read September 14, 2026.
    After
    CyrusOne lists CyrusOne Sterling NVA1 to NVA3, CyrusOne Sterling NVA4, CyrusOne Sterling NVA5 to NVA7, CyrusOne Sterling NVA8, CyrusOne Sterling NVA9 at Sterling, Virginia on its own page of data center locations, read September 14, 2026.
    Why
    The census line printed two facility code ranges with a hyphen (NVA1-NVA3, NVA5-NVA7), which the writing rule reads as a compound and which stopped the build of 2026-09-20; the ranges now read with "to". Corrected 2026-09-20 by the state page batch.

  4122. · Google Loudoun County data center · the summary of a timeline entry

    Before
    Google lists Google Loundoun County data center at Loudoun County, Virginia on its own page of data center locations, read September 14, 2026.
    After
    Google lists Google Loudoun County data center at Loudoun County, Virginia on its own page of data center locations, read September 14, 2026.
    Why
    The county is Loudoun County, Virginia; the census entry of 2026-09-14 misspelled it. Corrected 2026-09-20 by the state page batch.

  4123. · Google Loudoun County data center · the alias of a project aliases entry

    Before
    Google Loundoun County data center
    After
    Google Loudoun County data center
    Why
    The county is Loudoun County, Virginia; the alias carried the census extraction's misspelling. Corrected 2026-09-20 by the state page batch.

  4124. · Google Loudoun County data center · the alias of a project aliases entry

    Before
    Google Loundoun County, Virginia
    After
    Google Loudoun County, Virginia
    Why
    The county is Loudoun County, Virginia; the alias carried the census extraction's misspelling. Corrected 2026-09-20 by the state page batch.

  4125. · Google Loudoun County data center · the name of a record

    Before
    Google Loundoun County data center
    After
    Google Loudoun County data center
    Why
    The county is Loudoun County, Virginia (U.S. Census Bureau county list); the census extraction of 2026-09-14 misspelled it in the record's name. Corrected 2026-09-20 by the state page batch; the slug keeps the misspelling because a published slug never changes.

  4126. · a record · the session of a bill

    Before
    2026 Regular Regular Session
    After
    2026 Regular Session
    Why
    LegiScan serves the session name with a word doubled ("2026 Regular Regular Session"); its session_title reads "2026 Regular Session". Collapsed on 2026-09-20 by the state page batch; monitor/src/bills.ts sessionName() keeps it from recurring.

  4127. · a record · the session of a bill

    Before
    2026 Regular Regular Session
    After
    2026 Regular Session
    Why
    LegiScan serves the session name with a word doubled ("2026 Regular Regular Session"); its session_title reads "2026 Regular Session". Collapsed on 2026-09-20 by the state page batch; monitor/src/bills.ts sessionName() keeps it from recurring.

  4128. · a record · the session of a bill

    Before
    2026 Regular Regular Session
    After
    2026 Regular Session
    Why
    LegiScan serves the session name with a word doubled ("2026 Regular Regular Session"); its session_title reads "2026 Regular Session". Collapsed on 2026-09-20 by the state page batch; monitor/src/bills.ts sessionName() keeps it from recurring.

  4129. · a record · the session of a bill

    Before
    2026 Regular Regular Session
    After
    2026 Regular Session
    Why
    LegiScan serves the session name with a word doubled ("2026 Regular Regular Session"); its session_title reads "2026 Regular Session". Collapsed on 2026-09-20 by the state page batch; monitor/src/bills.ts sessionName() keeps it from recurring.

  4130. · a record · the session of a bill

    Before
    2026 Regular Regular Session
    After
    2026 Regular Session
    Why
    LegiScan serves the session name with a word doubled ("2026 Regular Regular Session"); its session_title reads "2026 Regular Session". Collapsed on 2026-09-20 by the state page batch; monitor/src/bills.ts sessionName() keeps it from recurring.

  4131. · a record · the session of a bill

    Before
    2026 Regular Regular Session
    After
    2026 Regular Session
    Why
    LegiScan serves the session name with a word doubled ("2026 Regular Regular Session"); its session_title reads "2026 Regular Session". Collapsed on 2026-09-20 by the state page batch; monitor/src/bills.ts sessionName() keeps it from recurring.

  4132. · a record · the session of a bill

    Before
    2026 Regular Regular Session
    After
    2026 Regular Session
    Why
    LegiScan serves the session name with a word doubled ("2026 Regular Regular Session"); its session_title reads "2026 Regular Session". Collapsed on 2026-09-20 by the state page batch; monitor/src/bills.ts sessionName() keeps it from recurring.

  4133. · a record · the session of a bill

    Before
    2026 Regular Regular Session
    After
    2026 Regular Session
    Why
    LegiScan serves the session name with a word doubled ("2026 Regular Regular Session"); its session_title reads "2026 Regular Session". Collapsed on 2026-09-20 by the state page batch; monitor/src/bills.ts sessionName() keeps it from recurring.

  4134. · a record · the session of a bill

    Before
    2026 Regular Regular Session
    After
    2026 Regular Session
    Why
    LegiScan serves the session name with a word doubled ("2026 Regular Regular Session"); its session_title reads "2026 Regular Session". Collapsed on 2026-09-20 by the state page batch; monitor/src/bills.ts sessionName() keeps it from recurring.

  4135. · a record · the session of a bill

    Before
    2026 Regular Regular Session
    After
    2026 Regular Session
    Why
    LegiScan serves the session name with a word doubled ("2026 Regular Regular Session"); its session_title reads "2026 Regular Session". Collapsed on 2026-09-20 by the state page batch; monitor/src/bills.ts sessionName() keeps it from recurring.

  4136. · a record · the session of a bill

    Before
    2026 Regular Regular Session
    After
    2026 Regular Session
    Why
    LegiScan serves the session name with a word doubled ("2026 Regular Regular Session"); its session_title reads "2026 Regular Session". Collapsed on 2026-09-20 by the state page batch; monitor/src/bills.ts sessionName() keeps it from recurring.

  4137. · a record · the session of a bill

    Before
    2026 Regular Regular Session
    After
    2026 Regular Session
    Why
    LegiScan serves the session name with a word doubled ("2026 Regular Regular Session"); its session_title reads "2026 Regular Session". Collapsed on 2026-09-20 by the state page batch; monitor/src/bills.ts sessionName() keeps it from recurring.

  4138. · a record · the session of a bill

    Before
    2026 Regular Regular Session
    After
    2026 Regular Session
    Why
    LegiScan serves the session name with a word doubled ("2026 Regular Regular Session"); its session_title reads "2026 Regular Session". Collapsed on 2026-09-20 by the state page batch; monitor/src/bills.ts sessionName() keeps it from recurring.

  4139. · a record · the session of a bill

    Before
    2026 Regular Regular Session
    After
    2026 Regular Session
    Why
    LegiScan serves the session name with a word doubled ("2026 Regular Regular Session"); its session_title reads "2026 Regular Session". Collapsed on 2026-09-20 by the state page batch; monitor/src/bills.ts sessionName() keeps it from recurring.

  4140. · a record · the session of a bill

    Before
    2026 Regular Regular Session
    After
    2026 Regular Session
    Why
    LegiScan serves the session name with a word doubled ("2026 Regular Regular Session"); its session_title reads "2026 Regular Session". Collapsed on 2026-09-20 by the state page batch; monitor/src/bills.ts sessionName() keeps it from recurring.

  4141. · a record · the session of a bill

    Before
    2026 Regular Regular Session
    After
    2026 Regular Session
    Why
    LegiScan serves the session name with a word doubled ("2026 Regular Regular Session"); its session_title reads "2026 Regular Session". Collapsed on 2026-09-20 by the state page batch; monitor/src/bills.ts sessionName() keeps it from recurring.

  4142. · a record · the session of a bill

    Before
    2026 Regular Regular Session
    After
    2026 Regular Session
    Why
    LegiScan serves the session name with a word doubled ("2026 Regular Regular Session"); its session_title reads "2026 Regular Session". Collapsed on 2026-09-20 by the state page batch; monitor/src/bills.ts sessionName() keeps it from recurring.

  4143. · a record · the session of a bill

    Before
    2026 Regular Regular Session
    After
    2026 Regular Session
    Why
    LegiScan serves the session name with a word doubled ("2026 Regular Regular Session"); its session_title reads "2026 Regular Session". Collapsed on 2026-09-20 by the state page batch; monitor/src/bills.ts sessionName() keeps it from recurring.

  4144. · a record · the session of a bill

    Before
    2026 Regular Regular Session
    After
    2026 Regular Session
    Why
    LegiScan serves the session name with a word doubled ("2026 Regular Regular Session"); its session_title reads "2026 Regular Session". Collapsed on 2026-09-20 by the state page batch; monitor/src/bills.ts sessionName() keeps it from recurring.

  4145. · a record · the session of a bill

    Before
    2026 Regular Regular Session
    After
    2026 Regular Session
    Why
    LegiScan serves the session name with a word doubled ("2026 Regular Regular Session"); its session_title reads "2026 Regular Session". Collapsed on 2026-09-20 by the state page batch; monitor/src/bills.ts sessionName() keeps it from recurring.

  4146. · a record · the session of a bill

    Before
    2026 Regular Regular Session
    After
    2026 Regular Session
    Why
    LegiScan serves the session name with a word doubled ("2026 Regular Regular Session"); its session_title reads "2026 Regular Session". Collapsed on 2026-09-20 by the state page batch; monitor/src/bills.ts sessionName() keeps it from recurring.

  4147. · a record · the session of a bill

    Before
    2026 Regular Regular Session
    After
    2026 Regular Session
    Why
    LegiScan serves the session name with a word doubled ("2026 Regular Regular Session"); its session_title reads "2026 Regular Session". Collapsed on 2026-09-20 by the state page batch; monitor/src/bills.ts sessionName() keeps it from recurring.

  4148. · a record · the session of a bill

    Before
    2026 Regular Regular Session
    After
    2026 Regular Session
    Why
    LegiScan serves the session name with a word doubled ("2026 Regular Regular Session"); its session_title reads "2026 Regular Session". Collapsed on 2026-09-20 by the state page batch; monitor/src/bills.ts sessionName() keeps it from recurring.

  4149. · a record · the session of a bill

    Before
    2026 Regular Regular Session
    After
    2026 Regular Session
    Why
    LegiScan serves the session name with a word doubled ("2026 Regular Regular Session"); its session_title reads "2026 Regular Session". Collapsed on 2026-09-20 by the state page batch; monitor/src/bills.ts sessionName() keeps it from recurring.

  4150. · a record · the session of a bill

    Before
    2026 Regular Regular Session
    After
    2026 Regular Session
    Why
    LegiScan serves the session name with a word doubled ("2026 Regular Regular Session"); its session_title reads "2026 Regular Session". Collapsed on 2026-09-20 by the state page batch; monitor/src/bills.ts sessionName() keeps it from recurring.

  4151. · a record · the session of a bill

    Before
    2026 Regular Regular Session
    After
    2026 Regular Session
    Why
    LegiScan serves the session name with a word doubled ("2026 Regular Regular Session"); its session_title reads "2026 Regular Session". Collapsed on 2026-09-20 by the state page batch; monitor/src/bills.ts sessionName() keeps it from recurring.

  4152. · San Marcos · the scorecard row of a scorecard event

    Before
    austin
    After
    san-marcos
    Why
    The event names the San Marcos City Council, not Austin's; San Marcos sits in Hays, Caldwell and Guadalupe counties. Moved to the new San Marcos row on 2026-09-18 by the jurisdiction row check, and given a primary county (Hays) with the other two listed.

  4153. · a record · the scorecard row of a scorecard event

    Before
    NB/new-brunswick
    After
    ME/maine
    Why
    Maine lawmakers moved to pause data centre projects; the row was the province of New Brunswick. Moved to the Maine state row 2026-09-18 by the jurisdiction row check.

  4154. · a record · the scorecard row of a scorecard event

    Before
    NB/new-brunswick
    After
    NJ/new-jersey
    Why
    A New Jersey tax break; the row was the province of New Brunswick. Moved to the New Jersey state row 2026-09-18 by the jurisdiction row check.

  4155. · a record · the scorecard row of a scorecard event

    Before
    NB/new-brunswick
    After
    NJ/new-jersey
    Why
    A question about New Jersey pausing AI data center development; the row was the province of New Brunswick. Moved to the New Jersey state row 2026-09-18 by the jurisdiction row check.

  4156. · a record · the scorecard row of a scorecard event

    Before
    NB/new-brunswick
    After
    NJ/new-brunswick
    Why
    New Brunswick, New Jersey city council (Middlesex County); the row was the province of New Brunswick. Moved 2026-09-18 by the jurisdiction row check.

  4157. · a record · the scorecard row of a scorecard event

    Before
    YT/yukon
    After
    OK/oklahoma
    Why
    Oklahoma lawmakers advanced a state bill; the row was the Yukon territory. Moved to the Oklahoma state row 2026-09-18 by the jurisdiction row check.

  4158. · a record · the scorecard row of a scorecard event

    Before
    YT/yukon
    After
    OK/yukon
    Why
    Yukon Mayor Brian Pillmore is the mayor of Yukon, Oklahoma (Canadian County); the row was the Yukon territory. Moved 2026-09-18 by the jurisdiction row check.

  4159. · a record · the scorecard row of a scorecard event

    Before
    YT/yukon
    After
    OK/yukon
    Why
    Yukon City Council is the council of Yukon, Oklahoma (Canadian County); the row was the Yukon territory. Moved 2026-09-18 by the jurisdiction row check.

  4160. · a record · the scorecard row of a scorecard event

    Before
    YT/yukon
    After
    OK/yukon
    Why
    The Yukon planning commission is Yukon, Oklahoma's (Canadian County); the row was the Yukon territory. Moved 2026-09-18 by the jurisdiction row check.

  4161. · a record · the scorecard row of a scorecard event

    Before
    YT/yukon
    After
    OK/yukon
    Why
    Yukon City Council is the council of Yukon, Oklahoma (Canadian County); the row was the Yukon territory. Moved 2026-09-18 by the jurisdiction row check.

  4162. · a record · the scorecard row of a scorecard event

    Before
    YT/yukon
    After
    OK/yukon
    Why
    Yukon City Council is the council of Yukon, Oklahoma (Canadian County); the row was the Yukon territory. Moved 2026-09-18 by the jurisdiction row check.

  4163. · Clearfield City · the scorecard row of a scorecard event

    Before
    box-elder-county
    After
    clearfield-city
    Why
    The event names the Clearfield City Council; Clearfield is in Davis County, not Box Elder County (U.S. Census Bureau, 2020 places by county). Moved to the Clearfield City row on 2026-09-18 by the jurisdiction row check.

  4164. · Laramie County Data Center (Bit-O-Wyo rezoning) · the summary of a record

    Before
    Laramie County commissioners approved rezoning for a data center project alongside Bit O Wyo event operations.
    After
    Laramie County commissioners approved rezoning for a data center project alongside Bit-O-Wyo event operations.
    Why
    The name restored: a hyphenated word in the record's own name is not a compound to split (DECISIONS section 12, amended 2026-09-18).

  4165. · AI Data Center near Mar-a-Lago · the summary of a record

    Before
    A large AI data center is planned near Mar a Lago in Palm Beach County, with environmental advocates raising concerns about potential impacts to the Everglades.
    After
    A large AI data center is planned near Mar-a-Lago in Palm Beach County, with environmental advocates raising concerns about potential impacts to the Everglades.
    Why
    The name restored: a hyphenated word in the record's own name is not a compound to split (DECISIONS section 12, amended 2026-09-18).

  4166. · Laramie County Data Center (Bit-O-Wyo rezoning) · the summary of a record

    Before
    Laramie County commissioners approved rezoning for a data center project alongside Bit O-Wyo event operations.
    After
    Laramie County commissioners approved rezoning for a data center project alongside Bit O Wyo event operations.
    Why
    Hyphenated compound split to meet the writing rule (DECISIONS section 12); the words are unchanged and the record name keeps the hyphens.

  4167. · AI Data Center near Mar-a-Lago · the summary of a record

    Before
    A large AI data center is planned near Mar a-Lago in Palm Beach County, with environmental advocates raising concerns about potential impacts to the Everglades.
    After
    A large AI data center is planned near Mar a Lago in Palm Beach County, with environmental advocates raising concerns about potential impacts to the Everglades.
    Why
    Hyphenated compound split to meet the writing rule (DECISIONS section 12); the words are unchanged and the record name keeps the hyphens.

  4168. · phoenix-data-center-firm-repurposing-portfolio-az · the summary of a record

    Before
    A Phoenix-based data center firm raised $1 billion to repurpose older facilities amid construction backlash.
    After
    A Phoenix based data center firm raised $1 billion to repurpose older facilities amid construction backlash.
    Why
    Hyphenated compound split to meet the writing rule (DECISIONS section 12); the words are unchanged.

  4169. · Stafford County data center complex · the summary of a record

    Before
    Stafford County Planning Commission backed a new 590,000-square-foot data center complex.
    After
    Stafford County Planning Commission backed a new 590,000 square foot data center complex.
    Why
    Hyphenated compound split to meet the writing rule (DECISIONS section 12); the words are unchanged.

  4170. · Boxminer.io La Pine Industrial Park · the summary of a record

    Before
    Boxminer.io proposed a 20-megawatt data center on approximately 19.5 to 20 acres at the La Pine Industrial Park on Reed Road, which La Pine City Council unanimously voted to reject on May 27, 2026 after strong public opposition.
    After
    Boxminer.io proposed a 20 megawatt data center on approximately 19.5 to 20 acres at the La Pine Industrial Park on Reed Road, which La Pine City Council unanimously voted to reject on May 27, 2026 after strong public opposition.
    Why
    Hyphenated compound split to meet the writing rule (DECISIONS section 12); the words are unchanged.

  4171. · Apple Prineville Campus · the summary of a record

    Before
    Apple operates a large data center campus in Prineville, Oregon, benefiting from Long-Term Rural Enterprise Zone tax exemptions that are nearing expiration.
    After
    Apple operates a large data center campus in Prineville, Oregon, benefiting from Long Term Rural Enterprise Zone tax exemptions that are nearing expiration.
    Why
    Hyphenated compound split to meet the writing rule (DECISIONS section 12); the words are unchanged.

  4172. · a statement · the record link of a statement

    Before
    tooele-valley-inland-port-data-center-ut
    After
    tooele-valley-data-center-ut
    Why
    The slug named in related_project_slugs was never a project or an alias; corrected to the real record, which is still a draft skeleton short of the record's skeleton minimum rule, so the statement returned to draft with it on 2026-09-17.

  4173. · a statement · the record link of a statement

    Before
    amazon-aws-data-center-campus-at-calvert-cliffs-cancelled-md
    After
    amazon-aws-data-center-campus-at-calvert-cliffs-md
    Why
    The slug named in related_project_slugs was never a project or an alias; corrected to the real record, which is still a draft skeleton short of the record's skeleton minimum rule, so the statement returned to draft with it on 2026-09-17.

  4174. · a statement · the record link of a statement

    Before
    amazon-aws-data-center-campus-at-calvert-cliffs-cancelled-md
    After
    amazon-aws-data-center-campus-at-calvert-cliffs-md
    Why
    The slug named in related_project_slugs was never a project or an alias; corrected to the real record, which is still a draft skeleton short of the record's skeleton minimum rule, so the statement returned to draft with it on 2026-09-17.

  4175. · a statement · the record link of a statement

    Before
    amazon-aws-data-center-campus-at-calvert-cliffs-cancelled-md
    After
    amazon-aws-data-center-campus-at-calvert-cliffs-md
    Why
    The slug named in related_project_slugs was never a project or an alias; corrected to the real record, which is still a draft skeleton short of the record's skeleton minimum rule, so the statement returned to draft with it on 2026-09-17.

  4176. · a statement · the record link of a statement

    Before
    amazon-aws-data-center-campus-at-calvert-cliffs-cancelled-md
    After
    amazon-aws-data-center-campus-at-calvert-cliffs-md
    Why
    The slug named in related_project_slugs was never a project or an alias; corrected to the real record, which is still a draft skeleton short of the record's skeleton minimum rule, so the statement returned to draft with it on 2026-09-17.

  4177. · a statement · the record link of a statement

    Before
    amazon-aws-data-center-campus-at-calvert-cliffs-cancelled-md
    After
    amazon-aws-data-center-campus-at-calvert-cliffs-md
    Why
    The slug named in related_project_slugs was never a project or an alias; corrected to the real record, which is still a draft skeleton short of the record's skeleton minimum rule, so the statement returned to draft with it on 2026-09-17.

  4178. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4179. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4180. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4181. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4182. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4183. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4184. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4185. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4186. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4187. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4188. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4189. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4190. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4191. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4192. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4193. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4194. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4195. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4196. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4197. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4198. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4199. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4200. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4201. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4202. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4203. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4204. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4205. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4206. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4207. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4208. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4209. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4210. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4211. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4212. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4213. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4214. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4215. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4216. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4217. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4218. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4219. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4220. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4221. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4222. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4223. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4224. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4225. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4226. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4227. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4228. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4229. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4230. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4231. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4232. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4233. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4234. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4235. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4236. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4237. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4238. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4239. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4240. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4241. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4242. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4243. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4244. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4245. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4246. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4247. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4248. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4249. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4250. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4251. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4252. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4253. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4254. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4255. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4256. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4257. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4258. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4259. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4260. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4261. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4262. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4263. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4264. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4265. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4266. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4267. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4268. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4269. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4270. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4271. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4272. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4273. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4274. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4275. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4276. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4277. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4278. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4279. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4280. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4281. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4282. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4283. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4284. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4285. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4286. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4287. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4288. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4289. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4290. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4291. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4292. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4293. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4294. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4295. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4296. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4297. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4298. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4299. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4300. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4301. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4302. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4303. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4304. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4305. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4306. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4307. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4308. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4309. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4310. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4311. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4312. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4313. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4314. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4315. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4316. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4317. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4318. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4319. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4320. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4321. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4322. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4323. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4324. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4325. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4326. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4327. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4328. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4329. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4330. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4331. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4332. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4333. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4334. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4335. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4336. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4337. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4338. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4339. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4340. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4341. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4342. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4343. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4344. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4345. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4346. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4347. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4348. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4349. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4350. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4351. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4352. · a record · the publication of a figure

    Before
    published
    After
    draft
    Why
    Resolved by geography to a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4353. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4354. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4355. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4356. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4357. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4358. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4359. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4360. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4361. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4362. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4363. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4364. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4365. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4366. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4367. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4368. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4369. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4370. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4371. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4372. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4373. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4374. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4375. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4376. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4377. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4378. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4379. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4380. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4381. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4382. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4383. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4384. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4385. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4386. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4387. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4388. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4389. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4390. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4391. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4392. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4393. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4394. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4395. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4396. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4397. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4398. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4399. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4400. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4401. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4402. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4403. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4404. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4405. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4406. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4407. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4408. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4409. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4410. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4411. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4412. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4413. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4414. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4415. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4416. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4417. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4418. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4419. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4420. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4421. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4422. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4423. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4424. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4425. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4426. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4427. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4428. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4429. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4430. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4431. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4432. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4433. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4434. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4435. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4436. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4437. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4438. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4439. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4440. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4441. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4442. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4443. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4444. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4445. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4446. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4447. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4448. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4449. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4450. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4451. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4452. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4453. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4454. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4455. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4456. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4457. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4458. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4459. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4460. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4461. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4462. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4463. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4464. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4465. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4466. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4467. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4468. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4469. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4470. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4471. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4472. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4473. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4474. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4475. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4476. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4477. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4478. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4479. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4480. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4481. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4482. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4483. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4484. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4485. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4486. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4487. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4488. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4489. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4490. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4491. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4492. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4493. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4494. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4495. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4496. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4497. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4498. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4499. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4500. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4501. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4502. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4503. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4504. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4505. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4506. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4507. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4508. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4509. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4510. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4511. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4512. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4513. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4514. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4515. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4516. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4517. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4518. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4519. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4520. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4521. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4522. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4523. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4524. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4525. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4526. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4527. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4528. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4529. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4530. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4531. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4532. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4533. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4534. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4535. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4536. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4537. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4538. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4539. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4540. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4541. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4542. · a statement · the publication of a statement

    Before
    published
    After
    draft
    Why
    Named, in related_project_slugs, a draft skeleton project still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4543. · Project Jupiter · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4544. · Project Jupiter · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4545. · Project Jupiter · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4546. · Project Jupiter · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4547. · Project Jupiter · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4548. · Project Jupiter · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4549. · Project Jupiter · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4550. · St. Louis Armory Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4551. · St. Louis Armory Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4552. · St. Louis Armory Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4553. · Frederick County Data Center Expansion · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4554. · Frederick County Data Center Expansion · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4555. · Boulder City BLM Land Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4556. · Boulder City BLM Land Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4557. · NScale Mason County Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4558. · NScale Mason County Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4559. · shadowbox-studios-data-center-ga · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4560. · shadowbox-studios-data-center-ga · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4561. · shadowbox-studios-data-center-ga · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4562. · shadowbox-studios-data-center-ga · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4563. · Claremore Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4564. · Claremore Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4565. · Claremore Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4566. · Claremore Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4567. · Claremore Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4568. · Bell Works Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4569. · Bell Works Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4570. · Bell Works Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4571. · Bell Works Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4572. · Bell Works Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4573. · prosper-data-center-500m-tx · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4574. · prosper-data-center-500m-tx · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4575. · prosper-data-center-500m-tx · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4576. · DeepGreen Western Passage Underwater AI Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4577. · DeepGreen Western Passage Underwater AI Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4578. · DeepGreen Western Passage Underwater AI Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4579. · U-M / Los Alamos Data Center (Van Buren Township) · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4580. · U-M / Los Alamos Data Center (Van Buren Township) · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4581. · Hillsboro data center projects (7 in permitting) · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4582. · Hillsboro data center projects (7 in permitting) · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4583. · Hillsboro data center projects (7 in permitting) · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4584. · energiacres-franklin-township-data-center-oh · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4585. · energiacres-franklin-township-data-center-oh · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4586. · Apple Prineville Campus · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4587. · Apple Prineville Campus · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4588. · Apple Prineville Campus · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4589. · Apple Prineville Campus · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4590. · meta-data-centre-alberta-ab · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4591. · meta-data-centre-alberta-ab · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4592. · algoma-steel-data-centre-on · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4593. · algoma-steel-data-centre-on · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4594. · Kearney Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4595. · Kearney Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4596. · Kearney Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4597. · Kearney Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4598. · Kearney Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4599. · Quantica Broadview Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4600. · Quantica Broadview Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4601. · Quantica Broadview Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4602. · Amazon Canton Data Centers · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4603. · Amazon Canton Data Centers · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4604. · SpaceXAI Southaven Data Center (Fifth Location) · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4605. · SpaceXAI Southaven Data Center (Fifth Location) · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4606. · SpaceXAI Southaven Data Center (Fifth Location) · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4607. · SpaceXAI Southaven Data Center (Fifth Location) · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4608. · Oracle and OpenAI Saline Township Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4609. · Oracle and OpenAI Saline Township Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4610. · Oracle and OpenAI Saline Township Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4611. · Oracle and OpenAI Saline Township Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4612. · Oracle and OpenAI Saline Township Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4613. · Markley Group Lowell Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4614. · Markley Group Lowell Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4615. · Markley Group Lowell Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4616. · Markley Group Lowell Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4617. · Markley Group Lowell Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4618. · Amazon / AWS Data Center Campus at Calvert Cliffs · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4619. · Amazon / AWS Data Center Campus at Calvert Cliffs · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4620. · Amazon / AWS Data Center Campus at Calvert Cliffs · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4621. · Amazon / AWS Data Center Campus at Calvert Cliffs · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4622. · SpaceX Starbase Louisiana / orbital data center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4623. · SpaceX Starbase Louisiana / orbital data center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4624. · SpaceX Starbase Louisiana / orbital data center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4625. · SpaceX Starbase Louisiana / orbital data center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4626. · SpaceX Starbase Louisiana / orbital data center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4627. · SpaceX Starbase Louisiana / orbital data center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4628. · lehigh-valley-data-center-s-pa · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4629. · lehigh-valley-data-center-s-pa · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4630. · Eaton Corp. North Little Rock Manufacturing Site · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4631. · TierPoint Nashville Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4632. · TierPoint Valley Forge Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4633. · h5-virginia-va · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4634. · h5-silicon-valley-ca · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4635. · h5-nashville-tn · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4636. · databank-new-york-city-data-center-ny · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4637. · centersquare-toronto-data-center-on · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4638. · oracle-montreal-cloud-region-qc · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4639. · equinix-ot1-gatineau-qc · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4640. · equinix-mt2-vaudreuil-dorion-qc · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4641. · equinix-mt1-saint-laurent-qc · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4642. · keel-infrastructure-sherbrooke-data-center-qc · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4643. · indigenous-owned-data-centre-in-cree-community-qc · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4644. · indigenous-owned-data-centre-in-cree-community-qc · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4645. · Leola Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4646. · Leola Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4647. · Leola Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4648. · Leola Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4649. · Leola Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4650. · Leola Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4651. · Leola Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4652. · Leola Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4653. · Project Jupiter · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4654. · Project Jupiter · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4655. · Project Jupiter · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4656. · Project Jupiter · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4657. · Project Jupiter · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4658. · Project Jupiter · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4659. · Project Jupiter · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4660. · Project Jupiter · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4661. · Project Jupiter · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4662. · Project Jupiter · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4663. · Project Jupiter · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4664. · Project Jupiter · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4665. · Project Jupiter · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4666. · Project Jupiter · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4667. · Project Jupiter · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4668. · Project Jupiter · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4669. · Project Jupiter · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4670. · Project Jupiter · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4671. · Project Jupiter · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4672. · Project Jupiter · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4673. · Grant County Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4674. · Grant County Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4675. · Grant County Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4676. · Grant County Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4677. · Grant County Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4678. · Grant County Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4679. · Grant County Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4680. · Project Jupiter · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4681. · Project Jupiter · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4682. · Project Jupiter · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4683. · Project Jupiter · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4684. · Project Jupiter · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4685. · Project Jupiter · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4686. · Project Jupiter · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4687. · Project Jupiter · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4688. · Project Jupiter · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4689. · Project Jupiter · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4690. · Project Jupiter · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4691. · Project Jupiter · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4692. · Project Jupiter · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4693. · Project Jupiter · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4694. · Project Jupiter · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4695. · Project Jupiter · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4696. · GNM New York PoP at Tribeca · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4697. · trumbull-ai-data-center-at-nasdaq-site-ct · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4698. · trumbull-ai-data-center-at-nasdaq-site-ct · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4699. · Beacon Falls Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4700. · Beacon Falls Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4701. · Beacon Falls Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4702. · Beacon Falls Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4703. · Beacon Falls Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4704. · Data Center Edgerton · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4705. · Data Center Edgerton · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4706. · Data Center Edgerton · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4707. · Data Center Edgerton · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4708. · Data Center Edgerton · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4709. · Data Center Edgerton · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4710. · Downtown Kansas City Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4711. · Applied Digital Polaris Forge 3 (Oliver County) · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4712. · Applied Digital Polaris Forge 3 (Oliver County) · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4713. · Applied Digital Polaris Forge 3 (Oliver County) · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4714. · Former Star Tribune Printing Plant Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4715. · Markley Group Lowell Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4716. · Markley Group Lowell Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4717. · Former Star Tribune Printing Plant Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4718. · Former Star Tribune Printing Plant Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4719. · Markley Group Lowell Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4720. · Former Star Tribune Printing Plant Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4721. · Former Star Tribune Printing Plant Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4722. · Former Star Tribune Printing Plant Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4723. · Proposed data center near Mandan · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4724. · Proposed data center near Mandan · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4725. · Proposed data center near Mandan · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4726. · Proposed data center near Mandan · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4727. · Proposed data center near Mandan · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4728. · Proposed data center near Mandan · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4729. · Proposed data center near Mandan · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4730. · olds-data-centre-ab · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4731. · Pittsburg County Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4732. · Pittsburg County Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4733. · Former Star Tribune Printing Plant Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4734. · project-cayman-la · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4735. · project-cayman-la · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4736. · project-cayman-la · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4737. · project-cayman-la · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4738. · Project Jupiter · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4739. · DeepGreen Western Passage Underwater AI Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4740. · DeepGreen Western Passage Underwater AI Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4741. · DeepGreen Western Passage Underwater AI Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4742. · DeepGreen Western Passage Underwater AI Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4743. · DeepGreen Western Passage Underwater AI Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4744. · Homer City Energy Campus Redevelopment · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4745. · Homer City Energy Campus Redevelopment · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4746. · Homer City Energy Campus Redevelopment · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4747. · Ypsilanti Township / University of Michigan & Los Alamos Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4748. · Ypsilanti Township / University of Michigan & Los Alamos Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4749. · Ypsilanti Township / University of Michigan & Los Alamos Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4750. · Kearney Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4751. · Global AI data center (Weld County) · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4752. · Global AI data center (Weld County) · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4753. · Global AI data center (Weld County) · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4754. · Global AI data center (Weld County) · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4755. · Global AI data center (Weld County) · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4756. · Global AI data center (Weld County) · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4757. · Global AI data center (Weld County) · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4758. · Global AI data center (Weld County) · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4759. · Global AI data center (Weld County) · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4760. · Global AI data center (Weld County) · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4761. · Global AI data center (Weld County) · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4762. · Global AI data center (Weld County) · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4763. · Global AI data center (Weld County) · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4764. · Global AI data center (Weld County) · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4765. · Global AI data center (Weld County) · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4766. · project-tembo-co · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4767. · project-tembo-co · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4768. · project-tembo-co · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4769. · project-tembo-co · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4770. · meta-data-centre-alberta-ab · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4771. · project-tembo-co · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4772. · meta-data-centre-alberta-ab · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4773. · project-tembo-co · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4774. · project-tembo-co · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4775. · meta-data-centre-alberta-ab · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4776. · Project Jupiter · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4777. · Global AI data center (Weld County) · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4778. · Project Jupiter · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4779. · Global AI data center (Weld County) · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4780. · Project Jupiter · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4781. · Project Jupiter · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4782. · Global AI data center (Weld County) · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4783. · Project Jupiter · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4784. · Data Center Edgerton · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4785. · T5 Grayslake data center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4786. · T5 Grayslake data center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4787. · Global AI data center (Weld County) · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4788. · Global AI data center (Weld County) · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4789. · Global AI data center (Weld County) · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4790. · Boston Neighborhood Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4791. · Oracle and OpenAI Saline Township Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4792. · ahwatukee-data-center-project-az · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4793. · ahwatukee-data-center-project-az · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4794. · ahwatukee-data-center-project-az · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4795. · ahwatukee-data-center-project-az · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4796. · ahwatukee-data-center-project-az · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4797. · Project Taurus · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4798. · Project Taurus · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4799. · Project Taurus · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4800. · AVAIO Pulaski County Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4801. · AVAIO Pulaski County Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4802. · Kearney Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4803. · Project Taurus · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4804. · AVAIO Pulaski County Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4805. · AVAIO Pulaski County Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4806. · AVAIO Pulaski County Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4807. · Kearney Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4808. · whitefiber-north-carolina-sites-nc · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4809. · Microsoft Mount Pleasant Data Center Campus · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4810. · Microsoft Mount Pleasant Data Center Campus · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4811. · Microsoft Mount Pleasant Data Center Campus · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4812. · whitefiber-north-carolina-sites-nc · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4813. · Microsoft Mount Pleasant Data Center Campus · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4814. · whitefiber-north-carolina-sites-nc · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4815. · whitefiber-north-carolina-sites-nc · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4816. · whitefiber-north-carolina-sites-nc · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4817. · whitefiber-north-carolina-sites-nc · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4818. · Global AI data center (Weld County) · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4819. · AVAIO Pulaski County Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4820. · AVAIO Pulaski County Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4821. · AVAIO Pulaski County Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4822. · AVAIO Pulaski County Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4823. · Imperial Valley AI Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4824. · AVAIO Pulaski County Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4825. · Imperial Valley AI Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4826. · shadowbox-studios-data-center-ga · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4827. · shadowbox-studios-data-center-ga · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4828. · Grady County Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4829. · Google Barber County Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4830. · stack-tor01-toronto-on · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4831. · oracle-toronto-cloud-region-on · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4832. · Meta Stanton Springs Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4833. · equinix-wi1-winnipeg-mb · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4834. · equinix-va1-burnaby-bc · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4835. · equinix-brampton-on · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4836. · equinix-tr5-markham-on · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4837. · equinix-toronto-on · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4838. · equinix-sj1-saint-john-nb · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4839. · equinix-ka1-kamloops-bc · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4840. · equinix-calgary-ab · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4841. · digital-realty-yyz12-toronto-on · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4842. · digital-realty-yyz10-markham-on · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4843. · digital-realty-vaughan-on · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4844. · Aligned PHX-07 · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4845. · Starwood Digital Ventures Mason County Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4846. · Starwood Digital Ventures Mason County Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4847. · Google Barber County Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4848. · Google Barber County Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4849. · Google Barber County Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4850. · Google Barber County Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4851. · Google Barber County Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4852. · Google Barber County Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4853. · Amazon Web Services Louisiana data centers · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4854. · Nebius AI Data Center (Vineland) · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4855. · Nebius AI Data Center (Vineland) · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4856. · Nebius AI Data Center (Vineland) · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4857. · Nebius AI Data Center (Vineland) · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4858. · Nebius AI Data Center (Vineland) · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4859. · Nebius AI Data Center (Vineland) · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4860. · NextEra and Brookfield Kentucky Data Center Campus · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4861. · NextEra and Brookfield Kentucky Data Center Campus · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4862. · NextEra and Brookfield Kentucky Data Center Campus · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4863. · NextEra and Brookfield Kentucky Data Center Campus · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4864. · Downtown Kansas City Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4865. · Downtown Kansas City Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4866. · Downtown Kansas City Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4867. · whitefiber-north-carolina-sites-nc · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4868. · whitefiber-north-carolina-sites-nc · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4869. · whitefiber-north-carolina-sites-nc · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4870. · whitefiber-north-carolina-sites-nc · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4871. · whitefiber-north-carolina-sites-nc · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4872. · University of Michigan / Los Alamos National Laboratory Hyperscale Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4873. · PAX-1 Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4874. · PAX-1 Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4875. · Global AI data center (Weld County) · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4876. · Raeden Gibraltar Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4877. · Raeden Gibraltar Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4878. · DeepGreen Western Passage Underwater AI Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4879. · DeepGreen Western Passage Underwater AI Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4880. · Markley Group Lowell Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4881. · Markley Group Lowell Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4882. · Las Vegas Data Center Expansion · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4883. · Las Vegas Data Center Expansion · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4884. · Project Jupiter · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4885. · Parker Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4886. · Parker Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4887. · Parker Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4888. · Parker Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4889. · Parker Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4890. · Parker Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4891. · Amazon Web Services Louisiana data centers · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4892. · Amazon Web Services Louisiana data centers · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4893. · NScale Mason County Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4894. · NScale Mason County Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4895. · SENS Longmont Facility · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4896. · University of Michigan / Los Alamos National Laboratory Hyperscale Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4897. · University of Michigan / Los Alamos National Laboratory Hyperscale Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4898. · meta-data-centre-alberta-ab · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4899. · meta-data-centre-alberta-ab · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4900. · meta-data-centre-alberta-ab · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4901. · meta-data-centre-alberta-ab · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4902. · meta-data-centre-alberta-ab · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4903. · meta-data-centre-alberta-ab · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4904. · meta-data-centre-alberta-ab · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4905. · meta-data-centre-alberta-ab · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4906. · meta-data-centre-alberta-ab · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4907. · meta-data-centre-alberta-ab · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4908. · meta-data-centre-alberta-ab · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4909. · meta-data-centre-alberta-ab · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4910. · meta-data-centre-alberta-ab · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4911. · meta-data-centre-alberta-ab · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4912. · meta-data-centre-alberta-ab · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4913. · meta-data-centre-alberta-ab · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4914. · bell-ai-fabric-saskatchewan-data-centre-sherwood-sk · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4915. · bell-ai-fabric-saskatchewan-data-centre-sherwood-sk · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4916. · bell-ai-fabric-saskatchewan-data-centre-sherwood-sk · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4917. · bell-ai-fabric-saskatchewan-data-centre-sherwood-sk · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4918. · bell-ai-fabric-saskatchewan-data-centre-sherwood-sk · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4919. · Raeden Gibraltar Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4920. · Raeden Gibraltar Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4921. · Raeden Gibraltar Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4922. · University of Michigan / Los Alamos National Laboratory Hyperscale Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4923. · Oracle and OpenAI Saline Township Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4924. · Oracle and OpenAI Saline Township Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4925. · google-michigan-data-center-mi · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4926. · Amazon / AWS Data Center Campus at Calvert Cliffs · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4927. · Amazon / AWS Data Center Campus at Calvert Cliffs · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4928. · Amazon / AWS Data Center Campus at Calvert Cliffs · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4929. · Amazon / AWS Data Center Campus at Calvert Cliffs · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4930. · Frederick Data Center Campus · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4931. · Frederick Data Center Campus · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4932. · Amazon / AWS Data Center Campus at Calvert Cliffs · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4933. · DeepGreen Western Passage Underwater AI Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4934. · DeepGreen Western Passage Underwater AI Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4935. · DeepGreen Western Passage Underwater AI Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4936. · DeepGreen Western Passage Underwater AI Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4937. · Bow Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4938. · Amazon Web Services Louisiana data centers · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4939. · Amazon Web Services Louisiana data centers · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4940. · Amazon Web Services Louisiana data centers · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4941. · Amazon Web Services Louisiana data centers · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4942. · Amazon Web Services Louisiana data centers · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4943. · Amazon Web Services Louisiana data centers · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4944. · Amazon Web Services Louisiana data centers · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4945. · Amazon Web Services Louisiana data centers · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4946. · Amazon Web Services Louisiana data centers · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4947. · project-cayman-la · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4948. · project-cayman-la · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4949. · project-cayman-la · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4950. · canadian-data-center-company-at-spaceport-america-nm · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4951. · canadian-data-center-company-at-spaceport-america-nm · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4952. · Homer City Energy Campus Redevelopment · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4953. · Homer City Energy Campus Redevelopment · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4954. · Homer City Energy Campus Redevelopment · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4955. · Homer City Energy Campus Redevelopment · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4956. · Delta Forge 1 · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4957. · Delta Forge 1 · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4958. · Delta Forge 1 · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4959. · Delta Forge 1 · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4960. · Delta Forge 1 · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4961. · google-fervo-geothermal-utah-ut · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4962. · google-fervo-geothermal-utah-ut · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4963. · google-fervo-geothermal-utah-ut · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4964. · google-fervo-geothermal-utah-ut · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4965. · google-fervo-geothermal-utah-ut · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4966. · google-fervo-geothermal-utah-ut · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4967. · google-fervo-geothermal-utah-ut · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4968. · tooele-valley-data-center-ut · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4969. · tooele-valley-data-center-ut · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4970. · google-fervo-geothermal-utah-ut · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4971. · google-fervo-geothermal-utah-ut · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4972. · google-fervo-geothermal-utah-ut · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4973. · google-fervo-geothermal-utah-ut · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4974. · google-fervo-geothermal-utah-ut · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4975. · google-fervo-geothermal-utah-ut · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4976. · google-fervo-geothermal-utah-ut · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4977. · google-fervo-geothermal-utah-ut · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4978. · google-fervo-geothermal-utah-ut · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4979. · tooele-valley-data-center-ut · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4980. · google-fervo-geothermal-utah-ut · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4981. · google-fervo-geothermal-utah-ut · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4982. · tooele-valley-data-center-ut · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4983. · tooele-valley-data-center-ut · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4984. · DC Blox Montgomery data center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4985. · DC Blox Montgomery data center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4986. · DC Blox Montgomery data center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval.

  4987. · Meta Louisiana data center · the record link of a statement

    Before
    meta-louisiana-data-center-richland-la
    After
    energiacres-franklin-township-data-center-oh
    Why
    Richland County, Ohio commissioner Tony Vero speaks about the Ohio proposal; the statement now names the Ohio record (2026-09-16).

  4988. · Meta Louisiana data center · the record link of a statement

    Before
    meta-louisiana-data-center-richland-la
    After
    energiacres-franklin-township-data-center-oh
    Why
    Richland County, Ohio commissioner Cliff Mears speaks about the Ohio proposal; the statement now names the Ohio record (2026-09-16).

  4989. · Meta Louisiana data center · the record link of a statement

    Before
    meta-louisiana-data-center-richland-la
    After
    energiacres-franklin-township-data-center-oh
    Why
    Richland County, Ohio commissioner Darrell Banks speaks about the Ohio proposal; the statement now names the Ohio record (2026-09-16).

  4990. · Meta Louisiana data center · the record link of a statement

    Before
    meta-louisiana-data-center-richland-la
    After
    energiacres-franklin-township-data-center-oh
    Why
    Shawn Cutter of EnergiAcres speaks about the Ohio proposal; the statement now names the Ohio record (2026-09-16).

  4991. · Meta Louisiana data center · the record of a source list entry

    Before
    meta-louisiana-data-center-richland-la
    After
    energiacres-franklin-township-data-center-oh
    Why
    The Mansfield News Journal article of April 15, 2026 is about Richland County, Ohio; moved to the Ohio record on 2026-09-16.

  4992. · Meta Louisiana data center · the record of a timeline entry

    Before
    meta-louisiana-data-center-richland-la
    After
    energiacres-franklin-township-data-center-oh
    Why
    The entry describes the EnergiAcres proposal in Franklin Township, Richland County, Ohio, not Richland Parish, Louisiana; moved to the Ohio record on 2026-09-16.

  4993. · Meta Louisiana data center · the record of a timeline entry

    Before
    meta-louisiana-data-center-richland-la
    After
    energiacres-franklin-township-data-center-oh
    Why
    The entry describes the EnergiAcres proposal in Franklin Township, Richland County, Ohio, not Richland Parish, Louisiana; moved to the Ohio record on 2026-09-16.

  4994. · Amazon Eastern Oregon Data Centers · the date of a timeline entry

    Before
    2026-09-14
    After
    2026-03-31
    Why
    Dated from its source: hbsslaw.com (its own cited source) answers 403 and could not be read directly; independent reporting on the same settlement (oregoncapitalchronicle.com/2026/03/31/..., KOIN, The Food and Environment Reporting Network) agrees the motion was filed March 31, 2026.

  4995. · Google West Memphis Data Center · the date of a timeline entry

    Before
    2026-09-14
    After
    2025-10-02
    Why
    Dated from its source: the video's own upload date (Oct 2, 2025, via DataForSEO youtube/video_info)

  4996. · Google West Memphis Data Center · the date of a timeline entry

    Before
    2026-09-14
    After
    2025-10-02
    Why
    Dated from its source: the video's own upload date (Oct 2, 2025, via DataForSEO youtube/video_info)

  4997. · Google West Memphis Data Center · the date of a timeline entry

    Before
    2026-09-14
    After
    2025-10-02
    Why
    Dated from its source: the video's own upload date (Oct 2, 2025, via DataForSEO youtube/video_info)

  4998. · Google West Memphis Data Center · the date of a timeline entry

    Before
    2026-09-14
    After
    2025-10-02
    Why
    Dated from its source: the row's own text ("Google broke ground...") matches the video's own description, which says "on Thursday"; published Thursday October 2, 2025, the same day

  4999. · Vantage Port Washington Data Center · the date of a timeline entry

    Before
    2026-09-14
    After
    2026-02-25
    Why
    Dated from its source: the video's own upload date (Feb 25, 2026, via DataForSEO youtube/video_info)

  5000. · Vantage Port Washington Data Center · the date of a timeline entry

    Before
    2026-09-13
    After
    2026-04-16
    Why
    Dated from its source: the video's own upload date (Apr 16, 2026, via DataForSEO youtube/video_info)

  5001. · meta-data-centre-alberta-ab · the date of a timeline entry

    Before
    2026-09-13
    After
    2026-07-08
    Why
    Dated from its source: the video's own upload date (Streamed live on Jul 8, 2026, via DataForSEO youtube/video_info)

  5002. · meta-data-centre-alberta-ab · the date of a timeline entry

    Before
    2026-09-13
    After
    2026-07-08
    Why
    Dated from its source: the video's own upload date (Streamed live on Jul 8, 2026, via DataForSEO youtube/video_info)

  5003. · meta-data-centre-alberta-ab · the date of a timeline entry

    Before
    2026-09-13
    After
    2026-07-08
    Why
    Dated from its source: the video's own upload date (Streamed live on Jul 8, 2026, via DataForSEO youtube/video_info)

  5004. · meta-data-centre-alberta-ab · the date of a timeline entry

    Before
    2026-09-13
    After
    2026-07-08
    Why
    Dated from its source: the video's own upload date (Streamed live on Jul 8, 2026, via DataForSEO youtube/video_info)

  5005. · meta-data-centre-alberta-ab · the date of a timeline entry

    Before
    2026-09-13
    After
    2026-07-09
    Why
    Dated from its source: the video's own upload date (Jul 9, 2026, via DataForSEO youtube/video_info)

  5006. · meta-data-centre-alberta-ab · the date of a timeline entry

    Before
    2026-09-13
    After
    2026-07-09
    Why
    Dated from its source: the video's own upload date (Jul 9, 2026, via DataForSEO youtube/video_info)

  5007. · meta-data-centre-alberta-ab · the date of a timeline entry

    Before
    2026-09-13
    After
    2026-07-09
    Why
    Dated from its source: the video's own upload date (Jul 9, 2026, via DataForSEO youtube/video_info)

  5008. · meta-data-centre-alberta-ab · the date of a timeline entry

    Before
    2026-09-13
    After
    2026-07-08
    Why
    Dated from its source: the video's own upload date (Jul 8, 2026, via DataForSEO youtube/video_info)

  5009. · meta-data-centre-alberta-ab · the date of a timeline entry

    Before
    2026-09-13
    After
    2026-07-08
    Why
    Dated from its source: the video's own upload date (Jul 8, 2026, via DataForSEO youtube/video_info)

  5010. · meta-data-centre-alberta-ab · the date of a timeline entry

    Before
    2026-09-13
    After
    2026-07-08
    Why
    Dated from its source: the video's own upload date (Jul 8, 2026, via DataForSEO youtube/video_info)

  5011. · meta-data-centre-alberta-ab · the date of a timeline entry

    Before
    2026-09-13
    After
    2026-07-08
    Why
    Dated from its source: the video's own upload date (Jul 8, 2026, via DataForSEO youtube/video_info)

  5012. · meta-data-centre-alberta-ab · the date of a timeline entry

    Before
    2026-09-13
    After
    2026-07-08
    Why
    Dated from its source: the video's own upload date (Jul 8, 2026, via DataForSEO youtube/video_info)

  5013. · meta-data-centre-alberta-ab · the date of a timeline entry

    Before
    2026-09-13
    After
    2026-07-08
    Why
    Dated from its source: the video's own upload date (Jul 8, 2026, via DataForSEO youtube/video_info)

  5014. · meta-data-centre-alberta-ab · the date of a timeline entry

    Before
    2026-09-13
    After
    2026-07-08
    Why
    Dated from its source: the video's own upload date (Jul 8, 2026, via DataForSEO youtube/video_info)

  5015. · meta-data-centre-alberta-ab · the date of a timeline entry

    Before
    2026-09-13
    After
    2026-07-11
    Why
    Dated from its source: the video's own upload date (Jul 11, 2026, via DataForSEO youtube/video_info)

  5016. · meta-data-centre-alberta-ab · the date of a timeline entry

    Before
    2026-09-13
    After
    2026-07-11
    Why
    Dated from its source: the video's own upload date (Jul 11, 2026, via DataForSEO youtube/video_info)

  5017. · meta-data-centre-alberta-ab · the date of a timeline entry

    Before
    2026-09-15
    After
    2026-07-08
    Why
    Dated from its source: the video's own upload date (Jul 8, 2026, via DataForSEO youtube/video_info)

  5018. · meta-data-centre-alberta-ab · the date of a timeline entry

    Before
    2026-09-15
    After
    2026-07-08
    Why
    Dated from its source: the video's own upload date (Jul 8, 2026, via DataForSEO youtube/video_info)

  5019. · TierPoint Kansas City - Lenexa Data Center · the date of a timeline entry

    Before
    2026-09-14
    After
    2026-09-14
    Why
    Dated from its source: the row's own text states it: "... read September 14, 2026."

  5020. · TierPoint Spokane Data Centers · the date of a timeline entry

    Before
    2026-09-14
    After
    2026-09-14
    Why
    Dated from its source: the row's own text states it: "... read September 14, 2026."

  5021. · TierPoint Seattle Data Center · the date of a timeline entry

    Before
    2026-09-14
    After
    2026-09-14
    Why
    Dated from its source: the row's own text states it: "... read September 14, 2026."

  5022. · H5 Seattle · the date of a timeline entry

    Before
    2026-09-14
    After
    2026-09-14
    Why
    Dated from its source: the row's own text states it: "... read September 14, 2026."

  5023. · H5 Data Centers Quincy · the date of a timeline entry

    Before
    2026-09-14
    After
    2026-09-14
    Why
    Dated from its source: the row's own text states it: "... read September 14, 2026."

  5024. · DataBank Seattle data center · the date of a timeline entry

    Before
    2026-09-14
    After
    2026-09-14
    Why
    Dated from its source: the row's own text states it: "... read September 14, 2026."

  5025. · Centersquare Seattle data center · the date of a timeline entry

    Before
    2026-09-14
    After
    2026-09-14
    Why
    Dated from its source: the row's own text states it: "... read September 14, 2026."

  5026. · oracle-montreal-cloud-region-qc · the date of a timeline entry

    Before
    2026-09-14
    After
    2026-09-14
    Why
    Dated from its source: the row's own text states it: "... read September 14, 2026."

  5027. · equinix-ot1-gatineau-qc · the date of a timeline entry

    Before
    2026-09-14
    After
    2026-09-14
    Why
    Dated from its source: the row's own text states it: "... read September 14, 2026."

  5028. · equinix-mt2-vaudreuil-dorion-qc · the date of a timeline entry

    Before
    2026-09-14
    After
    2026-09-14
    Why
    Dated from its source: the row's own text states it: "... read September 14, 2026."

  5029. · equinix-mt1-saint-laurent-qc · the date of a timeline entry

    Before
    2026-09-14
    After
    2026-09-14
    Why
    Dated from its source: the row's own text states it: "... read September 14, 2026."

  5030. · Equinix NY13 · the date of a timeline entry

    Before
    2026-09-14
    After
    2026-09-14
    Why
    Dated from its source: the row's own text states it: "... read September 14, 2026."

  5031. · Equinix NY9 · the date of a timeline entry

    Before
    2026-09-14
    After
    2026-09-14
    Why
    Dated from its source: the row's own text states it: "... read September 14, 2026."

  5032. · Digital Realty New York · the date of a timeline entry

    Before
    2026-09-14
    After
    2026-09-14
    Why
    Dated from its source: the row's own text states it: "... read September 14, 2026."

  5033. · CyrusOne Wappingers Falls NYM7 · the date of a timeline entry

    Before
    2026-09-14
    After
    2026-09-14
    Why
    Dated from its source: the row's own text states it: "... read September 14, 2026."

  5034. · CyrusOne Norwalk NYM5 · the date of a timeline entry

    Before
    2026-09-14
    After
    2026-09-14
    Why
    Dated from its source: the row's own text states it: "... read September 14, 2026."

  5035. · Vantage Quincy · the date of a timeline entry

    Before
    2026-09-14
    After
    2026-09-14
    Why
    Dated from its source: the row's own text states it: "... read September 14, 2026."

  5036. · Equinix SE4 · the date of a timeline entry

    Before
    2026-09-14
    After
    2026-09-14
    Why
    Dated from its source: the row's own text states it: "... read September 14, 2026."

  5037. · Equinix Seattle · the date of a timeline entry

    Before
    2026-09-14
    After
    2026-09-14
    Why
    Dated from its source: the row's own text states it: "... read September 14, 2026."

  5038. · Digital Realty Seattle · the date of a timeline entry

    Before
    2026-09-14
    After
    2026-09-14
    Why
    Dated from its source: the row's own text states it: "... read September 14, 2026."

  5039. · CyrusOne Quincy PNW1 · the date of a timeline entry

    Before
    2026-09-14
    After
    2026-09-14
    Why
    Dated from its source: the row's own text states it: "... read September 14, 2026."

  5040. · xAI Southaven turbine site · the date of a timeline entry

    Before
    2026-09-14
    After
    2026-04-01
    Why
    Dated from its source: the row's own text states "April 2026", a month only date (first of the month, the standing rule)

  5041. · Microsoft Mount Pleasant Data Center Campus · the date of a timeline entry

    Before
    2026-09-14
    After
    2026-06-18
    Why
    Dated from its source: the row's own text states "June 18 update"

  5042. · xAI Southaven turbine site · the date of a timeline entry

    Before
    2026-09-14
    After
    2026-06-08
    Why
    Dated from its source: the row's own text states "filed Monday, June 8, 2026"

  5043. · Microsoft Mount Pleasant Data Center Campus · the date of a timeline entry

    Before
    2026-09-14
    After
    2026-04-15
    Why
    Dated from its source: the row's own text states "April 15 update"

  5044. · xAI Southaven turbine site · the date of a timeline entry

    Before
    2026-09-14
    After
    2025-08-01
    Why
    Dated from its source: the row's own text states turbines "began operating in or around August 2025", a month only date (first of the month, the standing rule)

  5045. · Microsoft Mount Pleasant Data Center Campus · the date of a timeline entry

    Before
    2026-09-14
    After
    2026-07-01
    Why
    Dated from its source: the article says the suit was filed "Wednesday"; published Thursday July 2, 2026, so Wednesday is July 1, 2026

  5046. · xAI Southaven turbine site · the date of a timeline entry

    Before
    2026-09-14
    After
    2026-06-17
    Why
    Dated from its source: the page's own publish date (06.17.2026, stated at its foot)

  5047. · Microsoft Mount Pleasant Data Center Campus · the date of a timeline entry

    Before
    2026-09-14
    After
    2026-07-02
    Why
    Dated from its source: the article's own publish date

  5048. · a statement · the date of a statement

    Before
    undated (source, no source_date)
    After
    2025-10-02
    Why
    Dated from its source: the video's own upload date (Oct 2, 2025, via DataForSEO youtube/video_info)

  5049. · a statement · the date of a statement

    Before
    undated (source, no source_date)
    After
    2026-07-11
    Why
    Dated from its source: the video's own upload date (Jul 11, 2026, via DataForSEO youtube/video_info)

  5050. · Marco McClendon · the date of a statement

    Before
    undated (source, no source_date)
    After
    2025-10-02
    Why
    Dated from its source: the video's own upload date (Oct 2, 2025, via DataForSEO youtube/video_info)

  5051. · a statement · the date of a statement

    Before
    undated (source, no source_date)
    After
    2026-07-08
    Why
    Dated from its source: the video's own upload date (Streamed live on Jul 8, 2026, via DataForSEO youtube/video_info)

  5052. · a statement · the date of a statement

    Before
    undated (source, no source_date)
    After
    2026-07-11
    Why
    Dated from its source: the video's own upload date (Jul 11, 2026, via DataForSEO youtube/video_info)

  5053. · a statement · the date of a statement

    Before
    undated (source, no source_date)
    After
    2026-07-09
    Why
    Dated from its source: the video's own upload date (Jul 9, 2026, via DataForSEO youtube/video_info)

  5054. · Southaven residents suing xAI over turbine noise · the date of a statement

    Before
    undated (source, no source_date)
    After
    2026-06-10
    Why
    Dated from its source: the article's own publish date

  5055. · a statement · the date of a statement

    Before
    undated (source, no source_date)
    After
    2026-07-09
    Why
    Dated from its source: the video's own upload date (Jul 9, 2026, via DataForSEO youtube/video_info)

  5056. · a statement · the date of a statement

    Before
    undated (source, no source_date)
    After
    2026-07-08
    Why
    Dated from its source: the video's own upload date (Jul 8, 2026, via DataForSEO youtube/video_info)

  5057. · a statement · the date of a statement

    Before
    undated (source, no source_date)
    After
    2026-07-08
    Why
    Dated from its source: the video's own upload date (Streamed live on Jul 8, 2026, via DataForSEO youtube/video_info)

  5058. · a statement · the date of a statement

    Before
    undated (source, no source_date)
    After
    2026-07-08
    Why
    Dated from its source: the video's own upload date (Jul 8, 2026, via DataForSEO youtube/video_info)

  5059. · a statement · the date of a statement

    Before
    undated (source, no source_date)
    After
    2026-07-08
    Why
    Dated from its source: the video's own upload date (Jul 8, 2026, via DataForSEO youtube/video_info)

  5060. · a statement · the date of a statement

    Before
    undated (source, no source_date)
    After
    2026-07-08
    Why
    Dated from its source: the video's own upload date (Jul 8, 2026, via DataForSEO youtube/video_info)

  5061. · Ted Neitzke · the date of a statement

    Before
    undated (source, no source_date)
    After
    2026-04-16
    Why
    Dated from its source: the video's own upload date (Apr 16, 2026, via DataForSEO youtube/video_info)

  5062. · a statement · the date of a statement

    Before
    undated (source, no source_date)
    After
    2026-07-08
    Why
    Dated from its source: the video's own upload date (Jul 8, 2026, via DataForSEO youtube/video_info)

  5063. · Ted Neitzke · the date of a statement

    Before
    undated (source, no source_date)
    After
    2026-04-16
    Why
    Dated from its source: the video's own upload date (Apr 16, 2026, via DataForSEO youtube/video_info)

  5064. · a statement · the date of a statement

    Before
    undated (source, no source_date)
    After
    2026-07-11
    Why
    Dated from its source: the video's own upload date (Jul 11, 2026, via DataForSEO youtube/video_info)

  5065. · Southaven and Horn Lake residents in the class action against xAI, SpaceX and MZX Tech · the date of a statement

    Before
    undated (source, no source_date)
    After
    2026-06-17
    Why
    Dated from its source: the page's own publish date (06.17.2026, stated at its foot)

  5066. · a statement · the date of a statement

    Before
    undated (source, no source_date)
    After
    2026-07-02
    Why
    Dated from its source: the article's own publish date

  5067. · a statement · the date of a statement

    Before
    undated (source, no source_date)
    After
    2026-07-08
    Why
    Dated from its source: the video's own upload date (Jul 8, 2026, via DataForSEO youtube/video_info)

  5068. · a statement · the date of a statement

    Before
    undated (source, no source_date)
    After
    2026-07-08
    Why
    Dated from its source: the video's own upload date (Jul 8, 2026, via DataForSEO youtube/video_info)

  5069. · a statement · the date of a statement

    Before
    undated (source, no source_date)
    After
    2026-07-09
    Why
    Dated from its source: the video's own upload date (Jul 9, 2026, via DataForSEO youtube/video_info)

  5070. · Sarah Huckabee Sanders · the date of a statement

    Before
    undated (source, no source_date)
    After
    2025-10-02
    Why
    Dated from its source: the video's own upload date (Oct 2, 2025, via DataForSEO youtube/video_info)

  5071. · a statement · the date of a statement

    Before
    undated (source, no source_date)
    After
    2026-07-08
    Why
    Dated from its source: the video's own upload date (Jul 8, 2026, via DataForSEO youtube/video_info)

  5072. · a statement · the date of a statement

    Before
    undated (source, no source_date)
    After
    2026-07-08
    Why
    Dated from its source: the video's own upload date (Jul 8, 2026, via DataForSEO youtube/video_info)

  5073. · Corner (venture capital firm) · the date of a statement

    Before
    undated (source, no source_date)
    After
    2026-09-05
    Why
    Dated from its source: the article's own publish date

  5074. · Edwin Van Velzen · the date of a statement

    Before
    undated (source, no source_date)
    After
    2026-02-25
    Why
    Dated from its source: the video's own upload date (Feb 25, 2026, via DataForSEO youtube/video_info)

  5075. · a statement · the date of a statement

    Before
    undated (source, no source_date)
    After
    2026-07-11
    Why
    Dated from its source: the video's own upload date (Jul 11, 2026, via DataForSEO youtube/video_info)

  5076. · Raul Turrieta · the date of a statement

    Before
    undated (source, no source_date)
    After
    2026-09-05
    Why
    Dated from its source: the article's own publish date

  5077. · a statement · the date of a statement

    Before
    undated (source, no source_date)
    After
    2026-07-08
    Why
    Dated from its source: the video's own upload date (Jul 8, 2026, via DataForSEO youtube/video_info)

  5078. · a statement · the date of a statement

    Before
    undated (source, no source_date)
    After
    2026-07-08
    Why
    Dated from its source: the video's own upload date (Jul 8, 2026, via DataForSEO youtube/video_info)

  5079. · a statement · the date of a statement

    Before
    undated (source, no source_date)
    After
    2026-07-11
    Why
    Dated from its source: the video's own upload date (Jul 11, 2026, via DataForSEO youtube/video_info)

  5080. · a statement · the date of a statement

    Before
    undated (source, no source_date)
    After
    2026-07-09
    Why
    Dated from its source: the video's own upload date (Jul 9, 2026, via DataForSEO youtube/video_info)

  5081. · a statement · the date of a statement

    Before
    undated (source, no source_date)
    After
    2026-07-08
    Why
    Dated from its source: the video's own upload date (Jul 8, 2026, via DataForSEO youtube/video_info)

  5082. · a statement · the date of a statement

    Before
    undated (source, no source_date)
    After
    2026-07-08
    Why
    Dated from its source: the video's own upload date (Jul 8, 2026, via DataForSEO youtube/video_info)

  5083. · a statement · the date of a statement

    Before
    undated (source, no source_date)
    After
    2026-07-08
    Why
    Dated from its source: the video's own upload date (Streamed live on Jul 8, 2026, via DataForSEO youtube/video_info)

  5084. · Andrew Marsh · the date of a statement

    Before
    undated (source, no source_date)
    After
    2025-10-02
    Why
    Dated from its source: the video's own upload date (Oct 2, 2025, via DataForSEO youtube/video_info)

  5085. · a statement · the date of a statement

    Before
    undated (source, no source_date)
    After
    2026-07-08
    Why
    Dated from its source: the video's own upload date (Jul 8, 2026, via DataForSEO youtube/video_info)

  5086. · Southaven residents suing xAI over turbine noise · the date of a statement

    Before
    undated (source, no source_date)
    After
    2026-06-10
    Why
    Dated from its source: the article's own publish date

  5087. · Oly Perez · the date of a statement

    Before
    undated (source, no source_date)
    After
    2026-09-05
    Why
    Dated from its source: the article's own publish date

  5088. · a statement · the date of a statement

    Before
    undated (source, no source_date)
    After
    2026-07-09
    Why
    Dated from its source: the video's own upload date (Jul 9, 2026, via DataForSEO youtube/video_info)

  5089. · a record · the date of a figure

    Before
    undated (source, no source_date)
    After
    2026-07-09
    Why
    Dated from its source: the video's own upload date (Jul 9, 2026, via DataForSEO youtube/video_info)

  5090. · a record · the date of a figure

    Before
    undated (source, no source_date)
    After
    2026-04-16
    Why
    Dated from its source: the video's own upload date (Apr 16, 2026, via DataForSEO youtube/video_info)

  5091. · a record · the date of a figure

    Before
    undated (source, no source_date)
    After
    2026-03-11
    Why
    Dated from its source: the video's own upload date (Mar 11, 2026, via DataForSEO youtube/video_info)

  5092. · a record · the date of a figure

    Before
    undated (source, no source_date)
    After
    2026-04-16
    Why
    Dated from its source: the video's own upload date (Apr 16, 2026, via DataForSEO youtube/video_info)

  5093. · a record · the date of a figure

    Before
    undated (source, no source_date)
    After
    2025-10-02
    Why
    Dated from its source: the video's own upload date (Oct 2, 2025, via DataForSEO youtube/video_info)

  5094. · a record · the date of a figure

    Before
    undated (source, no source_date)
    After
    2026-06-10
    Why
    Dated from its source: the article's own publish date

  5095. · a record · the date of a figure

    Before
    undated (source, no source_date)
    After
    2026-09-05
    Why
    Dated from its source: the article's own publish date

  5096. · a record · the date of a figure

    Before
    undated (source, no source_date)
    After
    2026-07-02
    Why
    Dated from its source: the article's own publish date

  5097. · a record · the date of a figure

    Before
    undated (source, no source_date)
    After
    2026-04-16
    Why
    Dated from its source: the video's own upload date (Apr 16, 2026, via DataForSEO youtube/video_info)

  5098. · a record · the date of a figure

    Before
    undated (source, no source_date)
    After
    2026-07-08
    Why
    Dated from its source: the video's own upload date (Streamed live on Jul 8, 2026, via DataForSEO youtube/video_info)

  5099. · a record · the date of a figure

    Before
    undated (source, no source_date)
    After
    2026-07-08
    Why
    Dated from its source: the video's own upload date (Jul 8, 2026, via DataForSEO youtube/video_info)

  5100. · a record · the date of a figure

    Before
    undated (source, no source_date)
    After
    2026-07-09
    Why
    Dated from its source: the video's own upload date (Jul 9, 2026, via DataForSEO youtube/video_info)

  5101. · a record · the date of a figure

    Before
    undated (source, no source_date)
    After
    2026-07-08
    Why
    Dated from its source: the video's own upload date (Jul 8, 2026, via DataForSEO youtube/video_info)

  5102. · a record · the date of a figure

    Before
    undated (source, no source_date)
    After
    2026-02-25
    Why
    Dated from its source: the video's own upload date (Feb 25, 2026, via DataForSEO youtube/video_info)

  5103. · a record · the date of a figure

    Before
    undated (source, no source_date)
    After
    2026-06-17
    Why
    Dated from its source: the page's own publish date (06.17.2026, stated at its foot)

  5104. · a record · the date of a figure

    Before
    undated (source, no source_date)
    After
    2026-09-05
    Why
    Dated from its source: the article's own publish date

  5105. · a record · the date of a figure

    Before
    undated (source, no source_date)
    After
    2025-10-02
    Why
    Dated from its source: the video's own upload date (Oct 2, 2025, via DataForSEO youtube/video_info)

  5106. · a record · the date of a figure

    Before
    undated (source, no source_date)
    After
    2026-07-08
    Why
    Dated from its source: the video's own upload date (Jul 8, 2026, via DataForSEO youtube/video_info)

  5107. · a record · the date of a figure

    Before
    undated (source, no source_date)
    After
    2025-10-02
    Why
    Dated from its source: the video's own upload date (Oct 2, 2025, via DataForSEO youtube/video_info)

  5108. · a record · the date of a figure

    Before
    undated (source, no source_date)
    After
    2026-07-08
    Why
    Dated from its source: the video's own upload date (Jul 8, 2026, via DataForSEO youtube/video_info)

  5109. · a record · the date of a figure

    Before
    undated (source, no source_date)
    After
    2026-07-08
    Why
    Dated from its source: the video's own upload date (Streamed live on Jul 8, 2026, via DataForSEO youtube/video_info)

  5110. · a record · the date of a figure

    Before
    undated (source, no source_date)
    After
    2026-07-08
    Why
    Dated from its source: the video's own upload date (Jul 8, 2026, via DataForSEO youtube/video_info)

  5111. · a record · the date of a figure

    Before
    undated (source, no source_date)
    After
    2026-07-08
    Why
    Dated from its source: the video's own upload date (Streamed live on Jul 8, 2026, via DataForSEO youtube/video_info)

  5112. · a record · the date of a figure

    Before
    undated (source, no source_date)
    After
    2026-07-08
    Why
    Dated from its source: the video's own upload date (Streamed live on Jul 8, 2026, via DataForSEO youtube/video_info)

  5113. · a record · the date of a figure

    Before
    undated (source, no source_date)
    After
    2026-07-08
    Why
    Dated from its source: the video's own upload date (Streamed live on Jul 8, 2026, via DataForSEO youtube/video_info)

  5114. · a record · the date of a figure

    Before
    undated (source, no source_date)
    After
    2026-07-11
    Why
    Dated from its source: the video's own upload date (Jul 11, 2026, via DataForSEO youtube/video_info)

  5115. · a record · the date of a figure

    Before
    undated (source, no source_date)
    After
    2026-04-16
    Why
    Dated from its source: the video's own upload date (Apr 16, 2026, via DataForSEO youtube/video_info)

  5116. · a record · the date of a figure

    Before
    undated (source, no source_date)
    After
    2026-07-08
    Why
    Dated from its source: the video's own upload date (Streamed live on Jul 8, 2026, via DataForSEO youtube/video_info)

  5117. · a record · the date of a figure

    Before
    undated (source, no source_date)
    After
    2026-07-08
    Why
    Dated from its source: the video's own upload date (Jul 8, 2026, via DataForSEO youtube/video_info)

  5118. · a record · the date of a figure

    Before
    undated (source, no source_date)
    After
    2026-02-25
    Why
    Dated from its source: the video's own upload date (Feb 25, 2026, via DataForSEO youtube/video_info)

  5119. · a record · the date of a figure

    Before
    undated (source, no source_date)
    After
    2026-07-08
    Why
    Dated from its source: the video's own upload date (Streamed live on Jul 8, 2026, via DataForSEO youtube/video_info)

  5120. · a record · the date of a figure

    Before
    undated (source, no source_date)
    After
    2025-10-02
    Why
    Dated from its source: the video's own upload date (Oct 2, 2025, via DataForSEO youtube/video_info)

  5121. · a record · the date of a figure

    Before
    undated (source, no source_date)
    After
    2026-07-08
    Why
    Dated from its source: the video's own upload date (Streamed live on Jul 8, 2026, via DataForSEO youtube/video_info)

  5122. · a record · the date of a figure

    Before
    undated (source, no source_date)
    After
    2026-07-08
    Why
    Dated from its source: the video's own upload date (Streamed live on Jul 8, 2026, via DataForSEO youtube/video_info)

  5123. · a record · the date of a figure

    Before
    undated (source, no source_date)
    After
    2026-04-16
    Why
    Dated from its source: the video's own upload date (Apr 16, 2026, via DataForSEO youtube/video_info)

  5124. · a record · the date of a figure

    Before
    undated (source, no source_date)
    After
    2026-07-08
    Why
    Dated from its source: the video's own upload date (Jul 8, 2026, via DataForSEO youtube/video_info)

  5125. · a record · the date of a figure

    Before
    undated (source, no source_date)
    After
    2026-07-08
    Why
    Dated from its source: the video's own upload date (Streamed live on Jul 8, 2026, via DataForSEO youtube/video_info)

  5126. · a record · the date of a figure

    Before
    undated (source, no source_date)
    After
    2026-02-25
    Why
    Dated from its source: the video's own upload date (Feb 25, 2026, via DataForSEO youtube/video_info)

  5127. · a record · the date of a figure

    Before
    undated (source, no source_date)
    After
    2026-04-16
    Why
    Dated from its source: the video's own upload date (Apr 16, 2026, via DataForSEO youtube/video_info)

  5128. · a record · the date of a figure

    Before
    undated (source, no source_date)
    After
    2025-10-02
    Why
    Dated from its source: the video's own upload date (Oct 2, 2025, via DataForSEO youtube/video_info)

  5129. · a record · the date of a figure

    Before
    undated (source, no source_date)
    After
    2026-07-02
    Why
    Dated from its source: the article's own publish date

  5130. · a record · the date of a figure

    Before
    undated (source, no source_date)
    After
    2025-10-02
    Why
    Dated from its source: the video's own upload date (Oct 2, 2025, via DataForSEO youtube/video_info)

  5131. · a record · the date of a figure

    Before
    undated (source, no source_date)
    After
    2026-07-08
    Why
    Dated from its source: the video's own upload date (Streamed live on Jul 8, 2026, via DataForSEO youtube/video_info)

  5132. · a record · the date of a figure

    Before
    undated (source, no source_date)
    After
    2026-07-08
    Why
    Dated from its source: the video's own upload date (Streamed live on Jul 8, 2026, via DataForSEO youtube/video_info)

  5133. · a record · the date of a figure

    Before
    undated (source, no source_date)
    After
    2026-07-09
    Why
    Dated from its source: the video's own upload date (Jul 9, 2026, via DataForSEO youtube/video_info)

  5134. · a record · the date of a figure

    Before
    undated (source, no source_date)
    After
    2026-02-25
    Why
    Dated from its source: the video's own upload date (Feb 25, 2026, via DataForSEO youtube/video_info)

  5135. · a record · the date of a figure

    Before
    undated (source, no source_date)
    After
    2026-06-10
    Why
    Dated from its source: the article's own publish date

  5136. · a record · the date of a figure

    Before
    undated (source, no source_date)
    After
    2026-07-08
    Why
    Dated from its source: the video's own upload date (Jul 8, 2026, via DataForSEO youtube/video_info)

  5137. · a record · the date of a figure

    Before
    undated (source, no source_date)
    After
    2026-07-08
    Why
    Dated from its source: the video's own upload date (Jul 8, 2026, via DataForSEO youtube/video_info)

  5138. · Arkansas · the date of a scorecard event

    Before
    2026-09-14
    After
    2025-10-02
    Why
    Dated from its source: the video's own upload date (Oct 2, 2025, via DataForSEO youtube/video_info)

  5139. · Wisconsin · the date of a scorecard event

    Before
    2026-09-14
    After
    2026-02-25
    Why
    Dated from its source: the video's own upload date (Feb 25, 2026, via DataForSEO youtube/video_info)

  5140. · Volition Industries Spanish Fork · the date of a timeline entry

    Before
    2026-09-13
    After
    2026-08-18
    Why
    Dated from its source: the video's own upload date (Aug 18, 2026, via DataForSEO youtube/video_info)

  5141. · Volition Industries Spanish Fork · the date of a timeline entry

    Before
    2026-09-13
    After
    2026-08-18
    Why
    Dated from its source: the video's own upload date (Aug 18, 2026, via DataForSEO youtube/video_info)

  5142. · Volition Industries Spanish Fork · the date of a timeline entry

    Before
    2026-09-13
    After
    2026-03-11
    Why
    Dated from its source: the video's own upload date (Mar 11, 2026, via DataForSEO youtube/video_info)

  5143. · Volition Industries Spanish Fork · the date of a timeline entry

    Before
    2026-09-13
    After
    2026-03-11
    Why
    Dated from its source: the video's own upload date (Mar 11, 2026, via DataForSEO youtube/video_info)

  5144. · Volition Industries Spanish Fork · the date of a timeline entry

    Before
    2026-09-13
    After
    2026-08-18
    Why
    Dated from its source: the video's own upload date (Aug 18, 2026, via DataForSEO youtube/video_info)

  5145. · Volition Industries Spanish Fork · the date of a timeline entry

    Before
    2026-09-13
    After
    2026-08-05
    Why
    Dated from its source: the video's own title states "August 5, 2026", the planning commission meeting's date, and every row from it is something said at that one meeting

  5146. · Volition Industries Spanish Fork · the date of a timeline entry

    Before
    2026-09-13
    After
    2026-08-05
    Why
    Dated from its source: the video's own title states "August 5, 2026", the planning commission meeting's date, and every row from it is something said at that one meeting

  5147. · QTS Eagle Mountain · the date of a timeline entry

    Before
    2026-09-14
    After
    2026-09-14
    Why
    Dated from its source: the row's own text states it: "... read September 14, 2026."

  5148. · Novva West Jordan Data Center Campus · the date of a timeline entry

    Before
    2026-09-14
    After
    2026-09-14
    Why
    Dated from its source: the row's own text states it: "... read September 14, 2026."

  5149. · DataBank Granite Point Campus (SLC2, SLC3, SLC4, SLC5, SLC6) · the date of a timeline entry

    Before
    2026-09-14
    After
    2026-09-14
    Why
    Dated from its source: the row's own text states it: "... read September 14, 2026."

  5150. · Meta Eagle Mountain Data Center · the date of a timeline entry

    Before
    2026-09-14
    After
    2026-09-14
    Why
    Dated from its source: the row's own text states it: "... read September 14, 2026."

  5151. · Aligned SLC-04 · the date of a timeline entry

    Before
    2026-09-14
    After
    2026-09-14
    Why
    Dated from its source: the row's own text states it: "... read September 14, 2026."

  5152. · Aligned Data Centers West Jordan (SLC-01, SLC-02, SLC-03) · the date of a timeline entry

    Before
    2026-09-14
    After
    2026-09-14
    Why
    Dated from its source: the row's own text states it: "... read September 14, 2026."

  5153. · Paul Dayton · the date of a statement

    Before
    undated (source, no source_date)
    After
    2026-08-05
    Why
    Dated from its source: the video's own title states "August 5, 2026", the planning commission meeting's date, and every row from it is something said at that one meeting

  5154. · Dave Anderson · the date of a statement

    Before
    undated (source, no source_date)
    After
    2026-08-05
    Why
    Dated from its source: the video's own title states "August 5, 2026", the planning commission meeting's date, and every row from it is something said at that one meeting

  5155. · Scott McKane · the date of a statement

    Before
    undated (source, no source_date)
    After
    2026-09-02
    Why
    Dated from its source: the video's own upload date (Sep 2, 2026, via DataForSEO youtube/video_info)

  5156. · Jack Urquhart · the date of a statement

    Before
    undated (source, no source_date)
    After
    2026-08-18
    Why
    Dated from its source: the video's own upload date (Aug 18, 2026, via DataForSEO youtube/video_info)

  5157. · Jeff Chavez · the date of a statement

    Before
    undated (source, no source_date)
    After
    2026-08-05
    Why
    Dated from its source: the video's own title states "August 5, 2026", the planning commission meeting's date, and every row from it is something said at that one meeting

  5158. · Carla Shade · the date of a statement

    Before
    undated (source, no source_date)
    After
    2026-08-05
    Why
    Dated from its source: the video's own title states "August 5, 2026", the planning commission meeting's date, and every row from it is something said at that one meeting

  5159. · Jeff Chavez · the date of a statement

    Before
    undated (source, no source_date)
    After
    2026-08-05
    Why
    Dated from its source: the video's own title states "August 5, 2026", the planning commission meeting's date, and every row from it is something said at that one meeting

  5160. · Megan Banks · the date of a statement

    Before
    undated (source, no source_date)
    After
    2026-08-05
    Why
    Dated from its source: the video's own title states "August 5, 2026", the planning commission meeting's date, and every row from it is something said at that one meeting

  5161. · unnamed narrator · the date of a statement

    Before
    undated (source, no source_date)
    After
    2025-10-24
    Why
    Dated from its source: the video's own upload date (Oct 24, 2025, via DataForSEO youtube/video_info)

  5162. · Rod Yelm · the date of a statement

    Before
    undated (source, no source_date)
    After
    2026-08-05
    Why
    Dated from its source: the video's own title states "August 5, 2026", the planning commission meeting's date, and every row from it is something said at that one meeting

  5163. · Teresa Pierce · the date of a statement

    Before
    undated (source, no source_date)
    After
    2026-08-18
    Why
    Dated from its source: the video's own upload date (Aug 18, 2026, via DataForSEO youtube/video_info)

  5164. · Jesse Harrison · the date of a statement

    Before
    undated (source, no source_date)
    After
    2026-03-11
    Why
    Dated from its source: the video's own upload date (Mar 11, 2026, via DataForSEO youtube/video_info)

  5165. · Jeff Chavez · the date of a statement

    Before
    undated (source, no source_date)
    After
    2026-08-05
    Why
    Dated from its source: the video's own title states "August 5, 2026", the planning commission meeting's date, and every row from it is something said at that one meeting

  5166. · Dan Davis · the date of a statement

    Before
    undated (source, no source_date)
    After
    2026-08-05
    Why
    Dated from its source: the video's own title states "August 5, 2026", the planning commission meeting's date, and every row from it is something said at that one meeting

  5167. · unnamed narrator · the date of a statement

    Before
    undated (source, no source_date)
    After
    2025-10-24
    Why
    Dated from its source: the video's own upload date (Oct 24, 2025, via DataForSEO youtube/video_info)

  5168. · Jeff Chavez · the date of a statement

    Before
    undated (source, no source_date)
    After
    2026-08-05
    Why
    Dated from its source: the video's own title states "August 5, 2026", the planning commission meeting's date, and every row from it is something said at that one meeting

  5169. · Jeff Chavez · the date of a statement

    Before
    undated (source, no source_date)
    After
    2026-08-05
    Why
    Dated from its source: the video's own title states "August 5, 2026", the planning commission meeting's date, and every row from it is something said at that one meeting

  5170. · Allen Westmind · the date of a statement

    Before
    undated (source, no source_date)
    After
    2026-08-05
    Why
    Dated from its source: the video's own title states "August 5, 2026", the planning commission meeting's date, and every row from it is something said at that one meeting

  5171. · Jeff Chavez · the date of a statement

    Before
    undated (source, no source_date)
    After
    2026-08-05
    Why
    Dated from its source: the video's own title states "August 5, 2026", the planning commission meeting's date, and every row from it is something said at that one meeting

  5172. · Jeff Chavez · the date of a statement

    Before
    undated (source, no source_date)
    After
    2026-08-18
    Why
    Dated from its source: the video's own upload date (Aug 18, 2026, via DataForSEO youtube/video_info)

  5173. · Jeff Chavez · the date of a statement

    Before
    undated (source, no source_date)
    After
    2026-08-05
    Why
    Dated from its source: the video's own title states "August 5, 2026", the planning commission meeting's date, and every row from it is something said at that one meeting

  5174. · a record · the date of a figure

    Before
    undated (source, no source_date)
    After
    2026-08-05
    Why
    Dated from its source: the video's own title states "August 5, 2026", the planning commission meeting's date, and every row from it is something said at that one meeting

  5175. · a record · the date of a figure

    Before
    undated (source, no source_date)
    After
    2026-08-18
    Why
    Dated from its source: the video's own upload date (Aug 18, 2026, via DataForSEO youtube/video_info)

  5176. · a record · the date of a figure

    Before
    undated (source, no source_date)
    After
    2026-09-02
    Why
    Dated from its source: the video's own upload date (Sep 2, 2026, via DataForSEO youtube/video_info)

  5177. · a record · the date of a figure

    Before
    undated (source, no source_date)
    After
    2026-05-08
    Why
    Dated from its source: the video's own upload date (May 8, 2026, via DataForSEO youtube/video_info)

  5178. · a record · the date of a figure

    Before
    undated (source, no source_date)
    After
    2025-10-24
    Why
    Dated from its source: the video's own upload date (Oct 24, 2025, via DataForSEO youtube/video_info)

  5179. · Stratos Project · the date of a timeline entry

    Before
    2026-09-13
    After
    2026-05-14
    Why
    Dated from its source: the video's own upload date (Premiered May 14, 2026, via DataForSEO youtube/video_info)

  5180. · Stratos Project · the date of a timeline entry

    Before
    2026-09-13
    After
    2026-05-07
    Why
    Dated from its source: the video's own upload date (May 7, 2026, via DataForSEO youtube/video_info)

  5181. · Stratos Project · the date of a timeline entry

    Before
    2026-09-13
    After
    2026-07-26
    Why
    Dated from its source: the video's own upload date (Jul 26, 2026, via DataForSEO youtube/video_info)

  5182. · Stratos Project · the date of a timeline entry

    Before
    2026-09-13
    After
    2026-05-07
    Why
    Dated from its source: the video's own upload date (May 7, 2026, via DataForSEO youtube/video_info)

  5183. · Stratos Project · the date of a timeline entry

    Before
    2026-09-13
    After
    2026-07-26
    Why
    Dated from its source: the video's own upload date (Jul 26, 2026, via DataForSEO youtube/video_info)

  5184. · Stratos Project · the date of a timeline entry

    Before
    2026-09-13
    After
    2026-07-26
    Why
    Dated from its source: the video's own upload date (Jul 26, 2026, via DataForSEO youtube/video_info)

  5185. · Stratos Project · the date of a timeline entry

    Before
    2026-09-13
    After
    2026-06-20
    Why
    Dated from its source: the video's own upload date (Jun 20, 2026, via DataForSEO youtube/video_info)

  5186. · Stratos Project · the date of a timeline entry

    Before
    2026-09-13
    After
    2026-07-26
    Why
    Dated from its source: the video's own upload date (Jul 26, 2026, via DataForSEO youtube/video_info)

  5187. · Tina Cannon · the date of a statement

    Before
    undated (source, no source_date)
    After
    2026-05-28
    Why
    Dated from its source: the video's own upload date (May 28, 2026, via DataForSEO youtube/video_info)

  5188. · Kevin O'Leary · the date of a statement

    Before
    undated (source, no source_date)
    After
    2026-05-14
    Why
    Dated from its source: the video's own upload date (Premiered May 14, 2026, via DataForSEO youtube/video_info)

  5189. · Robert Davies · the date of a statement

    Before
    undated (source, no source_date)
    After
    2026-06-20
    Why
    Dated from its source: the video's own upload date (Jun 20, 2026, via DataForSEO youtube/video_info)

  5190. · Kevin O'Leary · the date of a statement

    Before
    undated (source, no source_date)
    After
    2026-05-19
    Why
    Dated from its source: the video's own upload date (May 19, 2026, via DataForSEO youtube/video_info)

  5191. · Davy Musser · the date of a statement

    Before
    undated (source, no source_date)
    After
    2026-05-08
    Why
    Dated from its source: the video's own upload date (May 8, 2026, via DataForSEO youtube/video_info)

  5192. · Max Roth · the date of a statement

    Before
    undated (source, no source_date)
    After
    2026-05-19
    Why
    Dated from its source: the video's own upload date (May 19, 2026, via DataForSEO youtube/video_info)

  5193. · Spencer Cox · the date of a statement

    Before
    undated (source, no source_date)
    After
    2026-07-26
    Why
    Dated from its source: the video's own upload date (Jul 26, 2026, via DataForSEO youtube/video_info)

  5194. · County officials · the date of a statement

    Before
    undated (source, no source_date)
    After
    2026-05-08
    Why
    Dated from its source: the video's own upload date (May 8, 2026, via DataForSEO youtube/video_info)

  5195. · Rob Davies · the date of a statement

    Before
    undated (source, no source_date)
    After
    2026-05-14
    Why
    Dated from its source: the video's own upload date (Premiered May 14, 2026, via DataForSEO youtube/video_info)

  5196. · Utah Military Installation Development Authority · the date of a statement

    Before
    undated (source, no source_date)
    After
    2026-05-08
    Why
    Dated from its source: the video's own upload date (May 8, 2026, via DataForSEO youtube/video_info)

  5197. · Kevin O'Leary · the date of a statement

    Before
    undated (source, no source_date)
    After
    2026-05-19
    Why
    Dated from its source: the video's own upload date (May 19, 2026, via DataForSEO youtube/video_info)

  5198. · Rob Davies · the date of a statement

    Before
    undated (source, no source_date)
    After
    2026-05-14
    Why
    Dated from its source: the video's own upload date (Premiered May 14, 2026, via DataForSEO youtube/video_info)

  5199. · Davy Musser · the date of a statement

    Before
    undated (source, no source_date)
    After
    2026-05-08
    Why
    Dated from its source: the video's own upload date (May 8, 2026, via DataForSEO youtube/video_info)

  5200. · Kevin O'Leary · the date of a statement

    Before
    undated (source, no source_date)
    After
    2026-05-08
    Why
    Dated from its source: the video's own upload date (May 8, 2026, via DataForSEO youtube/video_info)

  5201. · Kevin O'Leary · the date of a statement

    Before
    undated (source, no source_date)
    After
    2026-05-14
    Why
    Dated from its source: the video's own upload date (Premiered May 14, 2026, via DataForSEO youtube/video_info)

  5202. · a statement · the date of a statement

    Before
    undated (source, no source_date)
    After
    2026-05-14
    Why
    Dated from its source: the video's own upload date (Premiered May 14, 2026, via DataForSEO youtube/video_info)

  5203. · a record · the date of a figure

    Before
    undated (source, no source_date)
    After
    2026-05-08
    Why
    Dated from its source: the video's own upload date (May 8, 2026, via DataForSEO youtube/video_info)

  5204. · a record · the date of a figure

    Before
    undated (source, no source_date)
    After
    2026-05-08
    Why
    Dated from its source: the video's own upload date (May 8, 2026, via DataForSEO youtube/video_info)

  5205. · a record · the date of a figure

    Before
    undated (source, no source_date)
    After
    2026-05-08
    Why
    Dated from its source: the video's own upload date (May 8, 2026, via DataForSEO youtube/video_info)

  5206. · a record · the date of a figure

    Before
    undated (source, no source_date)
    After
    2026-05-08
    Why
    Dated from its source: the video's own upload date (May 8, 2026, via DataForSEO youtube/video_info)

  5207. · a record · the date of a figure

    Before
    undated (source, no source_date)
    After
    2026-05-08
    Why
    Dated from its source: the video's own upload date (May 8, 2026, via DataForSEO youtube/video_info)

  5208. · Stratos Project · the duplicate mark of a figure

    Before
    After
    802a705e-459a-449b-822f-83e0ffb31afa
    Why
    The same video gave the 9 GW figure twice on the record (a total planned capacity line and a households line); the second now defers to the first so the source is listed once (2026-09-15).

  5209. · Stratos Project · the metric of a figure

    Before
    Project backers cited roughly 10,000 construction jobs and 2,000 permanent positions (value 10000 jobs)
    After
    Project backers cited roughly 10,000 construction jobs (value 10000 construction jobs); the 2,000 permanent positions are their own row
    Why
    One row had carried two figures, construction and permanent jobs, under one value, and the permanent jobs block read the construction count. Split into two rows with the same source (2026-09-15).

  5210. · a record · the place of a figure

    Before
    Box Elder County, UT
    After
    Utah
    Why
    A statewide figure, filed under the geography of the Stratos card that carried it; with the Stratos comparison block it would have listed beside the project's own figures. Moved to the state (2026-09-15).

  5211. · a record · the place of a figure

    Before
    Box Elder County, UT
    After
    Utah
    Why
    A statewide figure, filed under the geography of the Stratos card that carried it; with the Stratos comparison block it would have listed beside the project's own figures. Moved to the state (2026-09-15).

  5212. · Stratos Project · the unit of a figure

    Before
    acres
    After
    acre feet
    Why
    The figure is 13,000 acre feet of water rights, as its own text says; the unit had been recorded as acres, which would have listed it as a footprint figure (2026-09-15).

  5213. · Stratos Project · the source url of a timeline entry

    Before
    https://eciks.org/22984-kevin-oleary-utah-data-center-transparency
    After
    https://senate.utah.gov/oleary-concedes-to-president-adams-demands-including-75-reduction-in-proposed-data-center-project-area-and-new-water-for-great-salt-lake/
    Why
    Re-sourced from eciks.org, an aggregator with no original reporting, to the Utah Senate release of June 4, 2026 saying O'Leary agreed to the letter's conditions (sources row 2232, tier 2). The entry keeps its source date of August 24; the release is dated June 4 (2026-09-15).

  5214. · Stratos Project · the source url of a timeline entry

    Before
    https://eciks.org/22984-kevin-oleary-utah-data-center-transparency
    After
    https://npr.brightspotcdn.com/19/bd/abf5d30e4d01a41cd0c162e90638/oleary-letter-6-1-2026.pdf
    Why
    Re-sourced from eciks.org, an aggregator with no original reporting, to the letter itself: Senate President J. Stuart Adams to Kevin O'Leary, dated June 1, 2026, hosted by Utah Public Radio (sources row 2230, tier 2). The entry keeps its source date of August 24; the letter is dated June 1 (2026-09-15).

  5215. · Stratos Project · the date of a timeline entry

    Before
    2026-08-13
    After
    2026-02-01
    Why
    The article states the announcement was made in February 2026, a month only date (first of the month, per the standing rule); the row read the article's own August 13 publish date as the announcement date.

  5216. · Arkansas · the date of a scorecard event

    Before
    2026-09-14
    After
    2026-09-14
    Why
    No date anywhere on file: a YouTube video with no captured upload date and none read from its content. Marked source with no source_date so it reads and is excluded as undated, rather than "content" (that column's pre fix default, not a real signal here), until a dated source exists.

  5217. · Wisconsin · the date of a scorecard event

    Before
    2026-09-14
    After
    2026-09-14
    Why
    No date anywhere on file: a YouTube video with no captured upload date and none read from its content. Marked source with no source_date so it reads and is excluded as undated, rather than "content" (that column's pre fix default, not a real signal here), until a dated source exists.

  5218. · a record · the date of a scorecard event

    Before
    2026-09-14
    After
    2026-09-11
    Why
    The article's own publish date, September 11, 2026, is in its url (spokesman.com/stories/2026/sep/11/...) and was never captured; the row read the approve day instead. The content says only "Monday", not which one, so this is dated to the source, not the content.

  5219. · a record · the date of a scorecard event

    Before
    2026-09-14
    After
    2026-09-11
    Why
    The article's own publish date, September 11, 2026, is in its url (spokesman.com/stories/2026/sep/11/...) and was never captured; the row read the approve day instead. The content says only "Monday", not which one, so this is dated to the source, not the content.

  5220. · Utah · the date of a scorecard event

    Before
    2026-09-13
    After
    2026-04-15
    Why
    The hearing was held April 15, 2026 per the cited KSL article's own text; the row read the article's September 13 publish date as if it were the hearing's date.

  5221. · Utah · the date of a scorecard event

    Before
    2026-09-12
    After
    2026-09-08
    Why
    The rally happened September 8, 2026 per the cited letter's own photo caption; the row read the letter's September 12 publish date as if it were the rally's date.

  5222. · Stratos Project · the summary of a record

    Before
    O'Leary Digital and the Military Installation Development Authority propose a data center campus with an onsite natural gas power plant on about 40,000 acres of unincorporated land in Hansel Valley, north of the Great Salt Lake, after Box Elder County commissioners consented to the MIDA project area on 2026-05-04.
    After
    O'Leary Digital and the Military Installation Development Authority propose a data center campus of approximately 9 GW at full buildout, with an onsite natural gas power plant, on about 40,000 acres of unincorporated land in Hansel Valley, north of the Great Salt Lake, after Box Elder County commissioners consented to the MIDA project area on 2026-05-04.
    Why
    Where a record carries two capacity figures from different sources, the summary uses the figure from the primary source: 9 GW from the Military Installation Development Authority's project page. KSL's 9.5 GW of generating capacity is listed on the record page beside it (the editor, 2026-09-14).

  5223. · Stratos Project · the capacity source url of a record

    Before
    After
    https://www.midaut.org/stratos
    Why
    The 9,000 MW on the record had no source and no basis on the row. The Military Installation Development Authority's project page, a primary source already cited, gives the buildout as approximately 9 GW; recorded as the developer's figure with that page as its source (the editor, 2026-09-14).

  5224. · Sturtevant residents suing Microsoft over noise at the Mount Pleasant data center · the speaker of a statement

    Before
    Lawsuit allegation
    After
    Sturtevant residents suing Microsoft over noise at the Mount Pleasant data center
    Why
    A statement with no named speaker carries the source's description of who spoke, never a label for what the statement is. Three residents of Sturtevant who live near the data center filed the class action in the Eastern District of Wisconsin, as the source reports; the statement is their allegation in the filing. (2026-09-14)

  5225. · Southaven and Horn Lake residents in the class action against xAI, SpaceX and MZX Tech · the speaker of a statement

    Before
    Lawsuit allegation
    After
    Southaven and Horn Lake residents in the class action against xAI, SpaceX and MZX Tech
    Why
    A statement with no named speaker carries the source's description of who spoke, never a label for what the statement is. The class action the law firm's page describes was brought by Southaven and Horn Lake residents; the statement is their allegation in the filing. (2026-09-14)

  5226. · Southaven residents suing xAI over turbine noise · the speaker of a statement

    Before
    Lawsuit allegation
    After
    Southaven residents suing xAI over turbine noise
    Why
    A statement with no named speaker carries the source's description of who spoke, never a label for what the statement is. A group of Southaven, Mississippi residents filed the suit against xAI on June 8, 2026, as the source reports; the statement is their allegation in the filing. (2026-09-14)

  5227. · Southaven residents suing xAI over turbine noise · the speaker of a statement

    Before
    Lawsuit allegation
    After
    Southaven residents suing xAI over turbine noise
    Why
    A statement with no named speaker carries the source's description of who spoke, never a label for what the statement is. A group of Southaven, Mississippi residents filed the suit against xAI on June 8, 2026, as the source reports; the statement is their allegation in the filing. (2026-09-14)

  5228. · OpenAI Effingham County Data Center · the summary of a record

    Before
    OpenAI is planning a large data center in Effingham County, Georgia, for which Georgia Power received approval for a 3.2 GW power deal, and which faces a citizen-led zoning lawsuit and questions about water and electric bill impacts.
    After
    OpenAI is planning a large data center in Effingham County, Georgia, for which Georgia Power received approval for a 3.2 GW power deal, and which faces a citizen led zoning lawsuit and questions about water and electric bill impacts.
    Why
    The writing rule (DECISIONS section 12): no hyphenated compound in record prose. The compound is written as separate words; the fact is unchanged (2026-09-14).

  5229. · Prometheus Hyperscale Natrona County Data Center · the summary of a record

    Before
    Prometheus Hyperscale proposed a 940-acre, gigawatt-scale data center campus in Natrona County, Wyoming, requesting the county bypass state environmental review amid divided commissioner opinion.
    After
    Prometheus Hyperscale proposed a 940 acre, gigawatt scale data center campus in Natrona County, Wyoming, requesting the county bypass state environmental review amid divided commissioner opinion.
    Why
    The writing rule (DECISIONS section 12): no hyphenated compound in record prose. The compound is written as separate words; the fact is unchanged (2026-09-14).

  5230. · Brian O'Neill · the wording of a statement

    Before
    O'Neill called the township council's claim that he rejected safeguards a 'bald-faced lie' and said he agreed to most requests
    After
    O'Neill called the township council's claim that he rejected safeguards a 'bald faced lie' and said he agreed to most requests
    Why
    The writing rule (DECISIONS section 12): no hyphenated compound in record prose. The compound is written as separate words; the fact is unchanged (2026-09-14).

  5231. · Brian O'Neill · the wording of a statement

    Before
    O'Neill said his proposed facilities would use closed-loop water systems, generate their own electricity, create no light pollution and comply with local noise limits
    After
    O'Neill said his proposed facilities would use closed loop water systems, generate their own electricity, create no light pollution and comply with local noise limits
    Why
    The writing rule (DECISIONS section 12): no hyphenated compound in record prose. The compound is written as separate words; the fact is unchanged (2026-09-14).

  5232. · Craig M. Gianetti · the wording of a statement

    Before
    Attorney Craig M. Gianetti argued that the township should prioritize evaluation over prohibition and noted the property has dual 69,000-volt transmission lines
    After
    Attorney Craig M. Gianetti argued that the township should prioritize evaluation over prohibition and noted the property has dual 69,000 volt transmission lines
    Why
    The writing rule (DECISIONS section 12): no hyphenated compound in record prose. The compound is written as separate words; the fact is unchanged (2026-09-14).

  5233. · Sarah Kogel-Smucker · the wording of a statement

    Before
    County Climate Change Officer Sarah Kogel-Smucker said data centers consume large amounts of energy and water and the goal is to shape development aligned with climate goals
    After
    County Climate Change Officer Sarah Kogel Smucker said data centers consume large amounts of energy and water and the goal is to shape development aligned with climate goals
    Why
    The writing rule (DECISIONS section 12): no hyphenated compound in record prose. The compound is written as separate words; the fact is unchanged (2026-09-14).

  5234. · Natali Fani-Gonzalez · the wording of a statement

    Before
    Montgomery County Council President Natali Fani-Gonzalez stated the compromise went from six months to two years, settling on 18 months
    After
    Montgomery County Council President Natali Fani Gonzalez stated the compromise went from six months to two years, settling on 18 months
    Why
    The writing rule (DECISIONS section 12): no hyphenated compound in record prose. The compound is written as separate words; the fact is unchanged (2026-09-14).

  5235. · Tim Callanan · the wording of a statement

    Before
    County Manager Tim Callanan said negotiations began under non-disclosure agreements in early February 2026
    After
    County Manager Tim Callanan said negotiations began under non disclosure agreements in early February 2026
    Why
    The writing rule (DECISIONS section 12): no hyphenated compound in record prose. The compound is written as separate words; the fact is unchanged (2026-09-14).

  5236. · OpenAI spokesperson · the wording of a statement

    Before
    OpenAI stated closed-loop cooling after initial fill would have ongoing water needs comparable to a typical office building for restrooms, kitchens, cleaning, sanitation, and maintenance
    After
    OpenAI stated closed loop cooling after initial fill would have ongoing water needs comparable to a typical office building for restrooms, kitchens, cleaning, sanitation, and maintenance
    Why
    The writing rule (DECISIONS section 12): no hyphenated compound in record prose. The compound is written as separate words; the fact is unchanged (2026-09-14).

  5237. · OpenAI spokesperson · the wording of a statement

    Before
    OpenAI stated dirty fluids will be properly and lawfully disposed of off-site at drainage time and will never be discharged into local environment
    After
    OpenAI stated dirty fluids will be properly and lawfully disposed of off site at drainage time and will never be discharged into local environment
    Why
    The writing rule (DECISIONS section 12): no hyphenated compound in record prose. The compound is written as separate words; the fact is unchanged (2026-09-14).

  5238. · Steven Uhles · the wording of a statement

    Before
    Savannah Riverkeeper raised concerns about periodic closed-loop drainage with chemical additives, water for power generation, and stormwater drainage and runoff
    After
    Savannah Riverkeeper raised concerns about periodic closed loop drainage with chemical additives, water for power generation, and stormwater drainage and runoff
    Why
    The writing rule (DECISIONS section 12): no hyphenated compound in record prose. The compound is written as separate words; the fact is unchanged (2026-09-14).

  5239. · Trisha Boyett · the wording of a statement

    Before
    Board member Trisha Boyett said revised fixed-rate structure would produce greater tax payments over life of agreement than using lower millage rates
    After
    Board member Trisha Boyett said revised fixed rate structure would produce greater tax payments over life of agreement than using lower millage rates
    Why
    The writing rule (DECISIONS section 12): no hyphenated compound in record prose. The compound is written as separate words; the fact is unchanged (2026-09-14).

  5240. · Ford · the wording of a statement

    Before
    OpenAI will pay the school district based on the 18.018-mill rate rather than the 16.45-mill rate for 15 years
    After
    OpenAI will pay the school district based on the 18.018 mill rate rather than the 16.45 mill rate for 15 years
    Why
    The writing rule (DECISIONS section 12): no hyphenated compound in record prose. The compound is written as separate words; the fact is unchanged (2026-09-14).

  5241. · Google · the wording of a statement

    Before
    Google will use air-cooled technology instead of water cooling in Mesa
    After
    Google will use air cooled technology instead of water cooling in Mesa
    Why
    The writing rule (DECISIONS section 12): no hyphenated compound in record prose. The compound is written as separate words; the fact is unchanged (2026-09-14).

  5242. · Google · the wording of a statement

    Before
    Google Mesa data center will reach at least 80% carbon-free energy by 2026
    After
    Google Mesa data center will reach at least 80% carbon free energy by 2026
    Why
    The writing rule (DECISIONS section 12): no hyphenated compound in record prose. The compound is written as separate words; the fact is unchanged (2026-09-14).

  5243. · Jay Irvin · the wording of a statement

    Before
    Jay Irvin of the Butler Design Group said 400-foot setback was outside the standards for setbacks for other types of industrial buildings which range from 15 to 30 feet
    After
    Jay Irvin of the Butler Design Group said 400 foot setback was outside the standards for setbacks for other types of industrial buildings which range from 15 to 30 feet
    Why
    The writing rule (DECISIONS section 12): no hyphenated compound in record prose. The compound is written as separate words; the fact is unchanged (2026-09-14).

  5244. · Mary Kopaskie-Brown · the wording of a statement

    Before
    Mary Kopaskie-Brown is Mesa's planning director
    After
    Mary Kopaskie Brown is Mesa's planning director
    Why
    The writing rule (DECISIONS section 12): no hyphenated compound in record prose. The compound is written as separate words; the fact is unchanged (2026-09-14).

  5245. · Chris Greene · the wording of a statement

    Before
    Chris Greene, speaking for International Association of Fire Fighters, stated fire departments ill-prepared for data center facilities
    After
    Chris Greene, speaking for International Association of Fire Fighters, stated fire departments ill prepared for data center facilities
    Why
    The writing rule (DECISIONS section 12): no hyphenated compound in record prose. The compound is written as separate words; the fact is unchanged (2026-09-14).

  5246. · Jaye O'Donnell · the wording of a statement

    Before
    Jaye O'Donnell said data centers located in industrial zones is a win-win for those facilities, the industry and community
    After
    Jaye O'Donnell said data centers located in industrial zones is a win for those facilities, the industry and the community alike
    Why
    The writing rule (DECISIONS section 12): no hyphenated compound in record prose. The compound is written as separate words; the fact is unchanged (2026-09-14).

  5247. · Arizona Energy Promise Taskforce · the wording of a statement

    Before
    Large-load facility construction is exceeding historical growth patterns and challenging how utilities make investment and planning decisions
    After
    Large load facility construction is exceeding historical growth patterns and challenging how utilities make investment and planning decisions
    Why
    The writing rule (DECISIONS section 12): no hyphenated compound in record prose. The compound is written as separate words; the fact is unchanged (2026-09-14).

  5248. · Arizona Energy Promise Taskforce · the wording of a statement

    Before
    Arizona utilities traditionally schedule maintenance during periods of lower demand, such as winter months, but continuous demand from large-load facilities can limit these windows
    After
    Arizona utilities traditionally schedule maintenance during periods of lower demand, such as winter months, but continuous demand from large load facilities can limit these windows
    Why
    The writing rule (DECISIONS section 12): no hyphenated compound in record prose. The compound is written as separate words; the fact is unchanged (2026-09-14).

  5249. · Asif Kazimm · the wording of a statement

    Before
    Each building would have internal closed loop and chiller system on roof with closed-loop water cooling system filled up only once
    After
    Each building would have internal closed loop and chiller system on roof with closed loop water cooling system filled up only once
    Why
    The writing rule (DECISIONS section 12): no hyphenated compound in record prose. The compound is written as separate words; the fact is unchanged (2026-09-14).

  5250. · Nathan Taylor Taft · the wording of a statement

    Before
    Nathan Taylor Taft, Mesa High School student and co-director of East Valley Unite, urged Mesa City Council on June 8 to reject the proposed NTT data center
    After
    Nathan Taylor Taft, Mesa High School student and co director of East Valley Unite, urged Mesa City Council on June 8 to reject the proposed NTT data center
    Why
    The writing rule (DECISIONS section 12): no hyphenated compound in record prose. The compound is written as separate words; the fact is unchanged (2026-09-14).

  5251. · Google spokesperson · the wording of a statement

    Before
    Google Mesa facility is air-cooled and consumes water typical of a standard office building
    After
    Google Mesa facility is air cooled and consumes water typical of a standard office building
    Why
    The writing rule (DECISIONS section 12): no hyphenated compound in record prose. The compound is written as separate words; the fact is unchanged (2026-09-14).

  5252. · Meta · the wording of a statement

    Before
    Meta's broader goal is to reach net-zero emissions across its supply chain by 2030.
    After
    Meta's broader goal is to reach net zero emissions across its supply chain by 2030.
    Why
    The writing rule (DECISIONS section 12): no hyphenated compound in record prose. The compound is written as separate words; the fact is unchanged (2026-09-14).

  5253. · a statement · the wording of a statement

    Before
    Meta is advancing its goal of achieving net-zero emissions across their value chain by 2030.
    After
    Meta is advancing its goal of achieving net zero emissions across their value chain by 2030.
    Why
    The writing rule (DECISIONS section 12): no hyphenated compound in record prose. The compound is written as separate words; the fact is unchanged (2026-09-14).

  5254. · Utah · the summary of a scorecard event

    Before
    Senate President Stuart Adams, R-Layton, served as a MIDA board member and chair and lost his primary election in June, with outrage over the Stratos data center project being a key factor
    After
    Senate President Stuart Adams, a Republican from Layton, served as a MIDA board member and chair and lost his primary election in June, with outrage over the Stratos data center project being a key factor
    Why
    The writing rule (DECISIONS section 12): no hyphenated compound in record prose. The compound is written as separate words; the fact is unchanged (2026-09-14).

  5255. · Savannah · the summary of a scorecard event

    Before
    Savannah City Council approved a 155-day moratorium on large-scale data centers
    After
    Savannah City Council approved a 155 day moratorium on large scale data centers
    Why
    The writing rule (DECISIONS section 12): no hyphenated compound in record prose. The compound is written as separate words; the fact is unchanged (2026-09-14).

  5256. · Savannah · the summary of a scorecard event

    Before
    The moratorium defines large-scale data centers as those with an electrical capacity of 10 megawatts or more
    After
    The moratorium defines large scale data centers as those with an electrical capacity of 10 megawatts or more
    Why
    The writing rule (DECISIONS section 12): no hyphenated compound in record prose. The compound is written as separate words; the fact is unchanged (2026-09-14).

  5257. · Prometheus Hyperscale Natrona County Data Center · the summary of a timeline entry

    Before
    Prometheus previously proposed 1.5-gigawatt campus across Natrona-Converse county line on Falls Ranch property north of Interstate 25
    After
    Prometheus previously proposed 1.5 gigawatt campus across the Natrona and Converse county line on Falls Ranch property north of Interstate 25
    Why
    The writing rule (DECISIONS section 12): no hyphenated compound in record prose. The compound is written as separate words; the fact is unchanged (2026-09-14).

  5258. · MLP Ventures King of Prussia Data Center Campus · the summary of a timeline entry

    Before
    Brian O'Neill of MLP Ventures is seeking approval for a 4.5 million-square-foot data center campus in King of Prussia
    After
    Brian O'Neill of MLP Ventures is seeking approval for a 4.5 million square foot data center campus in King of Prussia
    Why
    The writing rule (DECISIONS section 12): no hyphenated compound in record prose. The compound is written as separate words; the fact is unchanged (2026-09-14).

  5259. · MLP Ventures King of Prussia Data Center Campus · the summary of a timeline entry

    Before
    Brian O'Neill is seeking approval for a 2 million-square-foot data center facility at 900 Conshohocken Road in Plymouth Township
    After
    Brian O'Neill is seeking approval for a 2 million square foot data center facility at 900 Conshohocken Road in Plymouth Township
    Why
    The writing rule (DECISIONS section 12): no hyphenated compound in record prose. The compound is written as separate words; the fact is unchanged (2026-09-14).

  5260. · Atmosphere Dickerson data center · the summary of a timeline entry

    Before
    Atmosphere Data Centers challenged the six-month data center moratorium in Montgomery County
    After
    Atmosphere Data Centers challenged the six month data center moratorium in Montgomery County
    Why
    The writing rule (DECISIONS section 12): no hyphenated compound in record prose. The compound is written as separate words; the fact is unchanged (2026-09-14).

  5261. · OpenAI Effingham County Data Center · the summary of a timeline entry

    Before
    25-year agreement with Georgia Power
    After
    25 year agreement with Georgia Power
    Why
    The writing rule (DECISIONS section 12): no hyphenated compound in record prose. The compound is written as separate words; the fact is unchanged (2026-09-14).

  5262. · OpenAI Effingham County Data Center · the summary of a timeline entry

    Before
    Under a 25-year agreement, OpenAI agreed to cut up to 1,000 megawatts during peak demand to help grid reliability
    After
    Under a 25 year agreement, OpenAI agreed to cut up to 1,000 megawatts during peak demand to help grid reliability
    Why
    The writing rule (DECISIONS section 12): no hyphenated compound in record prose. The compound is written as separate words; the fact is unchanged (2026-09-14).

  5263. · OpenAI Effingham County Data Center · the summary of a timeline entry

    Before
    OpenAI will receive short-term tax abatements during construction and become the county's largest taxpayer after opening in 2028
    After
    OpenAI will receive short term tax abatements during construction and become the county's largest taxpayer after opening in 2028
    Why
    The writing rule (DECISIONS section 12): no hyphenated compound in record prose. The compound is written as separate words; the fact is unchanged (2026-09-14).

  5264. · OpenAI Effingham County Data Center · the summary of a timeline entry

    Before
    Project Camellia is a planned 1,400-acre data center campus at the Savannah Gateway Industrial Hub
    After
    Project Camellia is a planned 1,400 acre data center campus at the Savannah Gateway Industrial Hub
    Why
    The writing rule (DECISIONS section 12): no hyphenated compound in record prose. The compound is written as separate words; the fact is unchanged (2026-09-14).

  5265. · OpenAI Effingham County Data Center · the summary of a timeline entry

    Before
    Agreement gave Broe and OmniTRAX authority as sole and exclusive agent, attorney-in-fact and master developer of nearly 2,600 acres of ECIDA-owned land
    After
    Agreement gave Broe and OmniTRAX authority as sole and exclusive agent, attorney in fact and master developer of nearly 2,600 acres of ECIDA owned land
    Why
    The writing rule (DECISIONS section 12): no hyphenated compound in record prose. The compound is written as separate words; the fact is unchanged (2026-09-14).

  5266. · OpenAI Effingham County Data Center · the summary of a timeline entry

    Before
    Project has multi-year five-phase timeline with first phase targeted to begin construction by late 2028 and entire project completed by end of 2034
    After
    Project has multi year five phase timeline with first phase targeted to begin construction by late 2028 and entire project completed by end of 2034
    Why
    The writing rule (DECISIONS section 12): no hyphenated compound in record prose. The compound is written as separate words; the fact is unchanged (2026-09-14).

  5267. · OpenAI Effingham County Data Center · the summary of a timeline entry

    Before
    1,440-acre data center campus with four buildings and combined footprint of 720,000 square feet
    After
    1,440 acre data center campus with four buildings and combined footprint of 720,000 square feet
    Why
    The writing rule (DECISIONS section 12): no hyphenated compound in record prose. The compound is written as separate words; the fact is unchanged (2026-09-14).

  5268. · OpenAI Effingham County Data Center · the summary of a timeline entry

    Before
    Site will operate a closed-loop cooling system to continuously recycle the same water instead of relying on evaporative methods
    After
    Site will operate a closed loop cooling system to continuously recycle the same water instead of relying on evaporative methods
    Why
    The writing rule (DECISIONS section 12): no hyphenated compound in record prose. The compound is written as separate words; the fact is unchanged (2026-09-14).

  5269. · OpenAI Effingham County Data Center · the summary of a timeline entry

    Before
    Georgia Power entered into a 25-year agreement with OpenAI to provide 3.2 gigawatts of electricity
    After
    Georgia Power entered into a 25 year agreement with OpenAI to provide 3.2 gigawatts of electricity
    Why
    The writing rule (DECISIONS section 12): no hyphenated compound in record prose. The compound is written as separate words; the fact is unchanged (2026-09-14).

  5270. · Project Baccara · the summary of a timeline entry

    Before
    160-acre Project Baccara recommended for approval in Maricopa County
    After
    160 acre Project Baccara recommended for approval in Maricopa County
    Why
    The writing rule (DECISIONS section 12): no hyphenated compound in record prose. The compound is written as separate words; the fact is unchanged (2026-09-14).

  5271. · Project Baccara · the summary of a timeline entry

    Before
    Project Baccara is a 2 million-square-foot data center endorsed for approval in Maricopa County
    After
    Project Baccara is a 2 million square foot data center endorsed for approval in Maricopa County
    Why
    The writing rule (DECISIONS section 12): no hyphenated compound in record prose. The compound is written as separate words; the fact is unchanged (2026-09-14).

  5272. · Project Baccara · the summary of a timeline entry

    Before
    DigitalBridge-backed developer Takanock is behind the Project Baccara project
    After
    DigitalBridge backed developer Takanock is behind the Project Baccara project
    Why
    The writing rule (DECISIONS section 12): no hyphenated compound in record prose. The compound is written as separate words; the fact is unchanged (2026-09-14).

  5273. · NTT Mesa data center campus · the summary of a timeline entry

    Before
    NTT Data Centers acquired 173-acre planned data center park in Mesa for $300 million in March 2025
    After
    NTT Data Centers acquired 173 acre planned data center park in Mesa for $300 million in March 2025
    Why
    The writing rule (DECISIONS section 12): no hyphenated compound in record prose. The compound is written as separate words; the fact is unchanged (2026-09-14).

  5274. · NTT Mesa data center campus · the summary of a timeline entry

    Before
    NTT also owns a 102-acre data campus in the Elliot Road Technology Corridor in Mesa with first of seven planned data centers opened in 2022 with 126,000 square feet
    After
    NTT also owns a 102 acre data campus in the Elliot Road Technology Corridor in Mesa with first of seven planned data centers opened in 2022 with 126,000 square feet
    Why
    The writing rule (DECISIONS section 12): no hyphenated compound in record prose. The compound is written as separate words; the fact is unchanged (2026-09-14).

  5275. · NTT Mesa data center campus · the summary of a timeline entry

    Before
    NTT Data Centers phases PH1-PH5 are under construction or in operation
    After
    NTT Data Centers phases PH1 to PH5 are under construction or in operation
    Why
    The writing rule (DECISIONS section 12): no hyphenated compound in record prose. The compound is written as separate words; the fact is unchanged (2026-09-14).

  5276. · NTT Mesa data center campus · the summary of a timeline entry

    Before
    Tokyo-based NTT Data Group purchased 173 acres at 10126 E. Pecos Road for 300 million dollars in 2025
    After
    Tokyo based NTT Data Group purchased 173 acres at 10126 E. Pecos Road for 300 million dollars in 2025
    Why
    The writing rule (DECISIONS section 12): no hyphenated compound in record prose. The compound is written as separate words; the fact is unchanged (2026-09-14).

  5277. · Google Mesa data center · the summary of a timeline entry

    Before
    Total planned development on 186-acre site is 750,000 square feet
    After
    Total planned development on 186 acre site is 750,000 square feet
    Why
    The writing rule (DECISIONS section 12): no hyphenated compound in record prose. The compound is written as separate words; the fact is unchanged (2026-09-14).

  5278. · Google Mesa data center · the summary of a timeline entry

    Before
    Google received Design Review Board approval for 288,000-square-foot data hall as phase 1
    After
    Google received Design Review Board approval for 288,000 square foot data hall as phase 1
    Why
    The writing rule (DECISIONS section 12): no hyphenated compound in record prose. The compound is written as separate words; the fact is unchanged (2026-09-14).

  5279. · Google Mesa data center · the summary of a timeline entry

    Before
    Google committed to air-cooled technology to limit water usage
    After
    Google committed to air cooled technology to limit water usage
    Why
    The writing rule (DECISIONS section 12): no hyphenated compound in record prose. The compound is written as separate words; the fact is unchanged (2026-09-14).

  5280. · Google Mesa data center · the summary of a timeline entry

    Before
    Google uses air-cooled technology and uses no water in its cooling technology
    After
    Google uses air cooled technology and uses no water in its cooling technology
    Why
    The writing rule (DECISIONS section 12): no hyphenated compound in record prose. The compound is written as separate words; the fact is unchanged (2026-09-14).

  5281. · Google Mesa data center · the summary of a timeline entry

    Before
    The Mesa data center will use state-of-the-art air-cool technology
    After
    The Mesa data center will use state of the art air cool technology
    Why
    The writing rule (DECISIONS section 12): no hyphenated compound in record prose. The compound is written as separate words; the fact is unchanged (2026-09-14).

  5282. · Google Mesa data center · the summary of a timeline entry

    Before
    Data center will use air-cooling technology instead of water cooling
    After
    Data center will use air cooling technology instead of water cooling
    Why
    The writing rule (DECISIONS section 12): no hyphenated compound in record prose. The compound is written as separate words; the fact is unchanged (2026-09-14).

  5283. · Google Mesa data center · the summary of a timeline entry

    Before
    Mesa data center will use air-cooled technology and be operational in 2025
    After
    Mesa data center will use air cooled technology and be operational in 2025
    Why
    The writing rule (DECISIONS section 12): no hyphenated compound in record prose. The compound is written as separate words; the fact is unchanged (2026-09-14).

  5284. · Google Mesa data center · the summary of a timeline entry

    Before
    Google signed eight-year contract with Salt River Project for 434 MW of renewable energy
    After
    Google signed eight year contract with Salt River Project for 434 MW of renewable energy
    Why
    The writing rule (DECISIONS section 12): no hyphenated compound in record prose. The compound is written as separate words; the fact is unchanged (2026-09-14).

  5285. · Google Mesa data center · the summary of a timeline entry

    Before
    Google entered GPLET agreement with Mesa for 25-year term with reduced property taxes
    After
    Google entered GPLET agreement with Mesa for 25 year term with reduced property taxes
    Why
    The writing rule (DECISIONS section 12): no hyphenated compound in record prose. The compound is written as separate words; the fact is unchanged (2026-09-14).

  5286. · Google Mesa data center · the summary of a timeline entry

    Before
    First phase includes 288,530-square-foot data center building, utility switchyard, medium voltage substation, security kiosk, road upgrades, and employee office building
    After
    First phase includes 288,530 square foot data center building, utility switchyard, medium voltage substation, security kiosk, road upgrades, and employee office building
    Why
    The writing rule (DECISIONS section 12): no hyphenated compound in record prose. The compound is written as separate words; the fact is unchanged (2026-09-14).

  5287. · EdgeCore Mesa North Campus · the summary of a timeline entry

    Before
    EdgeCore exploring 750-acre site in Florence for future data center campus as part of 1,500-acre industrial technology park
    After
    EdgeCore exploring 750 acre site in Florence for future data center campus as part of 1,500 acre industrial technology park
    Why
    The writing rule (DECISIONS section 12): no hyphenated compound in record prose. The compound is written as separate words; the fact is unchanged (2026-09-14).

  5288. · EdgeCore Mesa North Campus · the summary of a timeline entry

    Before
    EdgeCore will build a 1.2 million-square-foot data center in southeast Mesa, cut from the original 2.1 million-square-foot plan
    After
    EdgeCore will build a 1.2 million square foot data center in southeast Mesa, cut from the original 2.1 million square foot plan
    Why
    The writing rule (DECISIONS section 12): no hyphenated compound in record prose. The compound is written as separate words; the fact is unchanged (2026-09-14).

  5289. · Montgomery Meta Investment · the summary of a timeline entry

    Before
    The administrative facility utilizes mass timber construction as a renewable, lower-carbon alternative to traditional steel and concrete.
    After
    The administrative facility utilizes mass timber construction as a renewable, lower carbon alternative to traditional steel and concrete.
    Why
    The writing rule (DECISIONS section 12): no hyphenated compound in record prose. The compound is written as separate words; the fact is unchanged (2026-09-14).

  5290. · Montgomery Meta Investment · the summary of a timeline entry

    Before
    Meta has donated to STEM programs at Montgomery Public Schools and launched district-wide robotics program
    After
    Meta has donated to STEM programs at Montgomery Public Schools and launched district wide robotics program
    Why
    The writing rule (DECISIONS section 12): no hyphenated compound in record prose. The compound is written as separate words; the fact is unchanged (2026-09-14).

  5291. · a record · the place of a figure

    Before
    Utah; Ohio; Texas; Pennsylvania; national
    After
    United States
    Why
    A national poll; the figure carried the states the report discussed as its geography. Moved to national scope (the editor, 2026-09-13).

  5292. · a record · the place of a figure

    Before
    Utah; Ohio; Texas; Pennsylvania; national
    After
    United States
    Why
    A national poll; the figure carried the states the report discussed as its geography. Moved to national scope (the editor, 2026-09-13).

  5293. · a record · the place of a figure

    Before
    Utah; national
    After
    United States
    Why
    A national poll; the figure carried the states the report discussed as its geography. Moved to national scope (the editor, 2026-09-13).

  5294. · a record · the place of a figure

    Before
    Box Elder County, UT
    After
    United States
    Why
    A national poll; the figure was filed under the geography of the card that carried it. Moved to national scope (the editor, 2026-09-13).

  5295. · Stratos Project · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Restates the May 4 county approval already on the record as row 13 (Utah News Dispatch); folded into that row with the outlet as a citation (2026-09-13).

  5296. · Stratos Project · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Restates the May 4 county approval already on the record as row 13 (Utah News Dispatch); folded into that row with the outlet as a citation (2026-09-13).

  5297. · Stratos Project · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Restates the MIDA initial approval already on the record as row 464 (Utah News Dispatch, August 20); folded into that row with the outlet as a citation (2026-09-13).

  5298. · Stratos Project · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Restates the MIDA initial approval already on the record as row 464 (Utah News Dispatch, August 20); folded into that row with the outlet as a citation (2026-09-13).

  5299. · Stratos Project · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Restates the MIDA initial approval already on the record as row 464 (Utah News Dispatch, August 20); folded into that row with the outlet as a citation (2026-09-13).

  5300. · a record · the row of a figure

    Before
    The project will initially use water equivalent to 600 homes annually and then recycle that water indefinitely
    After
    deleted
    Why
    Duplicate of the figure the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5301. · a record · the row of a figure

    Before
    Volition shares surplus clean energy with neighboring homes and businesses at rates up to 50 percent below utility costs
    After
    deleted
    Why
    Duplicate of the figure the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5302. · a record · the row of a figure

    Before
    The proposed data center would generate 250 megawatts of power on site
    After
    deleted
    Why
    Duplicate of the figure the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5303. · a record · the row of a figure

    Before
    The facility uses a closed loop cooling system requiring 250,000 gallons of annual water usage, equivalent to one Utah County household
    After
    deleted
    Why
    Duplicate of the figure the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5304. · a record · the row of a figure

    Before
    Fervo has committed more than $2 billion to the Cape Station project
    After
    deleted
    Why
    Duplicate of the figure the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5305. · a record · the row of a figure

    Before
    14 percent of respondents said they would be willing to live close to a data center
    After
    deleted
    Why
    Duplicate of the figure the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5306. · a record · the row of a figure

    Before
    14 percent of respondents said they would be willing to live close to a data center
    After
    deleted
    Why
    Duplicate of the figure the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5307. · a record · the row of a figure

    Before
    77 percent of survey respondents worry data centers will increase their electricity rates
    After
    deleted
    Why
    Duplicate of the figure the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5308. · a record · the row of a figure

    Before
    14 percent of respondents said they would be willing to live close to a data center
    After
    deleted
    Why
    Duplicate of the figure the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5309. · a record · the row of a figure

    Before
    77 percent of survey respondents worry data centers will increase their electricity rates
    After
    deleted
    Why
    Duplicate of the figure the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5310. · a record · the row of a figure

    Before
    64 percent of Reuters/Ipsos survey respondents said they do not think it is a good thing to build data centers at a rapid rate
    After
    deleted
    Why
    Duplicate of the figure the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5311. · a record · the row of a figure

    Before
    77 percent of survey respondents worry data centers will increase their electricity rates
    After
    deleted
    Why
    Duplicate of the figure the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5312. · a record · the row of a figure

    Before
    64 percent of Reuters/Ipsos survey respondents said they do not think it is a good thing to build data centers at a rapid rate
    After
    deleted
    Why
    Duplicate of the figure the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5313. · a record · the row of a figure

    Before
    A September 2025 Heatmap poll showed the public evenly split with 44 percent supporting data center construction and 42 percent opposed
    After
    deleted
    Why
    Duplicate of the figure the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5314. · a record · the row of a figure

    Before
    64 percent of Reuters/Ipsos survey respondents said they do not think it is a good thing to build data centers at a rapid rate
    After
    deleted
    Why
    Duplicate of the figure the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5315. · a record · the row of a figure

    Before
    A September 2025 Heatmap poll showed the public evenly split with 44 percent supporting data center construction and 42 percent opposed
    After
    deleted
    Why
    Duplicate of the figure the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5316. · a record · the row of a figure

    Before
    A September 2025 Heatmap poll showed the public evenly split with 44 percent supporting data center construction and 42 percent opposed
    After
    deleted
    Why
    Duplicate of the figure the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5317. · a record · the row of a figure

    Before
    A Heatmap News poll shows 75 percent of respondents oppose construction of data centers near them, with just 15 percent supporting, compared to a year ago when data centers won 43 percent support and
    After
    deleted
    Why
    Duplicate of the figure the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5318. · a record · the row of a figure

    Before
    A Heatmap News poll shows 75 percent of respondents oppose construction of data centers near them, with just 15 percent supporting, compared to a year ago when data centers won 43 percent support and
    After
    deleted
    Why
    Duplicate of the figure the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5319. · a record · the row of a figure

    Before
    A Heatmap News poll shows 75 percent of respondents oppose construction of data centers near them, with just 15 percent supporting, compared to a year ago when data centers won 43 percent support and
    After
    deleted
    Why
    Duplicate of the figure the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5320. · a record · the row of a figure

    Before
    Fervo is permitted for up to 2 gigawatts at Cape Station site
    After
    deleted
    Why
    Duplicate of the figure the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5321. · a record · the row of a figure

    Before
    Fervo is permitted for up to 2 gigawatts at Cape Station site
    After
    deleted
    Why
    Duplicate of the figure the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5322. · a record · the row of a figure

    Before
    Fervo is permitted for up to 2 gigawatts at Cape Station site
    After
    deleted
    Why
    Duplicate of the figure the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5323. · a record · the row of a figure

    Before
    Google has option to expand agreement by 600 megawatts pushing total toward nearly 1 gigawatt by June 2030
    After
    deleted
    Why
    Duplicate of the figure the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5324. · a record · the row of a figure

    Before
    Google signed PPA with Fervo Energy for 396 megawatts of geothermal power
    After
    deleted
    Why
    Duplicate of the figure the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5325. · a record · the row of a figure

    Before
    Google has option to expand agreement by 600 megawatts pushing total toward nearly 1 gigawatt by June 2030
    After
    deleted
    Why
    Duplicate of the figure the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5326. · a record · the row of a figure

    Before
    Google signed PPA with Fervo Energy for 396 megawatts of geothermal power
    After
    deleted
    Why
    Duplicate of the figure the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5327. · a record · the row of a figure

    Before
    Google has option to expand agreement by 600 megawatts pushing total toward nearly 1 gigawatt by June 2030
    After
    deleted
    Why
    Duplicate of the figure the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5328. · a record · the row of a figure

    Before
    Google signed PPA with Fervo Energy for 396 megawatts of geothermal power
    After
    deleted
    Why
    Duplicate of the figure the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5329. · a record · the row of a figure

    Before
    Hypothetical $2 billion data center with $1.5 billion worth of personal property can substantially reduce tax rate of counties during first year
    After
    deleted
    Why
    Duplicate of the figure the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5330. · a record · the row of a figure

    Before
    Hypothetical $2 billion data center with $1.5 billion worth of personal property can substantially reduce tax rate of counties during first year
    After
    deleted
    Why
    Duplicate of the figure the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5331. · a record · the row of a figure

    Before
    Hypothetical $2 billion data center with $1.5 billion worth of personal property can substantially reduce tax rate of counties during first year
    After
    deleted
    Why
    Duplicate of the figure the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5332. · a record · the row of a figure

    Before
    Gallup survey found 71% of Americans oppose data centers being built near their homes
    After
    deleted
    Why
    Duplicate of the figure the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5333. · a record · the row of a figure

    Before
    At least 75 data center projects worth roughly $130 billion were blocked or delayed in the first quarter of 2026
    After
    deleted
    Why
    Duplicate of the figure the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5334. · a record · the row of a figure

    Before
    Gallup survey found 71% of Americans oppose data centers being built near their homes
    After
    deleted
    Why
    Duplicate of the figure the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5335. · a record · the row of a figure

    Before
    Gallup survey found 71% of Americans oppose data centers being built near their homes
    After
    deleted
    Why
    Duplicate of the figure the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5336. · a record · the row of a figure

    Before
    At least 75 data center projects worth roughly $130 billion were blocked or delayed in the first quarter of 2026
    After
    deleted
    Why
    Duplicate of the figure the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5337. · a record · the row of a figure

    Before
    At least 75 data center projects worth roughly $130 billion were blocked or delayed in the first quarter of 2026
    After
    deleted
    Why
    Duplicate of the figure the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5338. · a record · the row of a figure

    Before
    Project backers cited roughly 10,000 construction jobs and 2,000 permanent positions
    After
    deleted
    Why
    Duplicate of the figure the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5339. · a record · the row of a figure

    Before
    Project backers cited roughly 10,000 construction jobs and 2,000 permanent positions
    After
    deleted
    Why
    Duplicate of the figure the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5340. · a record · the row of a figure

    Before
    Project backers cited roughly 10,000 construction jobs and 2,000 permanent positions
    After
    deleted
    Why
    Duplicate of the figure the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5341. · a record · the row of a figure

    Before
    The proposed Nebo North LLC data center campus would span 3 million square feet across 10 buildings
    After
    deleted
    Why
    Duplicate of the figure the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5342. · a record · the row of a figure

    Before
    The proposed Nebo North LLC data center campus would span 3 million square feet across 10 buildings
    After
    deleted
    Why
    Duplicate of the figure the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5343. · a record · the row of a figure

    Before
    The proposed Nebo North LLC data center campus would span 3 million square feet across 10 buildings
    After
    deleted
    Why
    Duplicate of the figure the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5344. · a record · the row of a figure

    Before
    The proposed Volition project would be a billion dollar, self powered data center that would generate between 250 and 400 megawatts of its own power using natural gas
    After
    deleted
    Why
    Duplicate of the figure the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5345. · a record · the row of a figure

    Before
    The proposed Volition project would be a billion dollar, self powered data center that would generate between 250 and 400 megawatts of its own power using natural gas
    After
    deleted
    Why
    Duplicate of the figure the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5346. · a record · the row of a figure

    Before
    The proposed Volition project would be a billion dollar, self powered data center that would generate between 250 and 400 megawatts of its own power using natural gas
    After
    deleted
    Why
    Duplicate of the figure the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5347. · a record · the row of a figure

    Before
    The proposed Volition data center would generate between 250 and 400 megawatts of its own power using natural gas
    After
    deleted
    Why
    Duplicate of the figure the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5348. · a record · the row of a figure

    Before
    The proposed Volition data center would generate between 250 and 400 megawatts of its own power using natural gas
    After
    deleted
    Why
    Duplicate of the figure the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5349. · a record · the row of a figure

    Before
    The proposed Volition data center would generate between 250 and 400 megawatts of its own power using natural gas
    After
    deleted
    Why
    Duplicate of the figure the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5350. · a statement · the row of a statement

    Before
    Jack Urquhart, Spanish Fork communications manager, explained the municipal code amendment is needed because the developer proposes generating its own power
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5351. · a statement · the row of a statement

    Before
    Jesse Harrison, local IT expert, stated that many data center promises get broken repeatedly based on historical patterns
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5352. · a statement · the row of a statement

    Before
    Volition facilities deploy in six to nine months using on site fuel cell electricity generation
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5353. · a statement · the row of a statement

    Before
    Traditional data centers require massive grid power and two to four years of utility infrastructure upgrades
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5354. · a statement · the row of a statement

    Before
    Teresa Pierce, Spanish Fork resident, expressed concern that data centers should not be built in residential backyards regardless of need
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5355. · a statement · the row of a statement

    Before
    Jeff Chavez, Volition CEO, stated data center developers should reuse existing infrastructure instead of buying thousands of acres
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5356. · a statement · the row of a statement

    Before
    Transparency from the developer and rigorous questioning by the planning commission changed resident sentiment toward supporting the project
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5357. · a statement · the row of a statement

    Before
    Enforceable contractual guardrails and community benefit agreements are necessary to protect clean air and water for future data center projects
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5358. · a statement · the row of a statement

    Before
    Computer chips transform electricity into heat, creating a large thermal output that should be regulated as heavy industrial use
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5359. · a statement · the row of a statement

    Before
    Data centers pose environmental and fire concerns and benefit wealthy entities at the expense of local residents
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5360. · a statement · the row of a statement

    Before
    The proposed data center facility is a good reuse of the existing building and resolves water and heat concerns
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5361. · a statement · the row of a statement

    Before
    The proposed 250 megawatt facility would produce more than double the peak power draw of the entire city of Spanish Fork
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5362. · a statement · the row of a statement

    Before
    Volition will include enforceable covenants in the development agreement covering water caps, noise limits, no grid connection, and no diesel
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5363. · a statement · the row of a statement

    Before
    Volition commits to providing more than 500,000 dollars per year in direct community contributions and educational partnerships
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5364. · a statement · the row of a statement

    Before
    Converting the existing industrial building to a data center reduces traffic from 3,500 trucks per month to 100-200 employee car trips per day with zero heavy truck traffic
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5365. · a statement · the row of a statement

    Before
    Volition is not requesting any additional water rights from the city
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5366. · a statement · the row of a statement

    Before
    Volition received a New Minor Source air quality permit approval from the Utah Department of Environmental Quality
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5367. · a statement · the row of a statement

    Before
    The fuel cell technology generates electricity through an electrochemical reaction with no combustion, flame, or fumes
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5368. · a statement · the row of a statement

    Before
    Volition's data centers produce zero draw on Spanish Fork's municipal power grid and use no local utility power
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5369. · a statement · the row of a statement

    Before
    Volition Industries proposes a data center inside Spanish Fork City powered entirely on site without connection to the city electric grid
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5370. · a statement · the row of a statement

    Before
    Tim Latimer, Fervo Energy CEO and co founder, said reliable electricity is needed for data centers that operate around the clock
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5371. · a statement · the row of a statement

    Before
    Google's director of advanced energy technologies Lucia Tian said the company does not yet know where in Utah the data center will be located
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5372. · a statement · the row of a statement

    Before
    Personal property taxes from data centers could create a boomerang or yo yo effect of initial tax decreases followed by offsetting future increases
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5373. · a statement · the row of a statement

    Before
    New data center facilities would likely provide initial property tax relief through increased property valuation
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5374. · a statement · the row of a statement

    Before
    Data centers present both opportunities and challenges for Utah's property tax system
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5375. · a statement · the row of a statement

    Before
    O'Leary said he has no interest in causing an environmental disaster on his legacy
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5376. · a statement · the row of a statement

    Before
    O'Leary said he has no interest in causing an environmental disaster on his legacy
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5377. · a statement · the row of a statement

    Before
    O'Leary said he has no interest in causing an environmental disaster on his legacy
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5378. · a statement · the row of a statement

    Before
    O'Leary said the data center industry has not communicated what it does to communities
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5379. · a statement · the row of a statement

    Before
    O'Leary said the data center industry has not communicated what it does to communities
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5380. · a statement · the row of a statement

    Before
    Kevin O'Leary said his company screwed up in communicating the Stratos project
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5381. · a statement · the row of a statement

    Before
    O'Leary said the data center industry has not communicated what it does to communities
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5382. · a statement · the row of a statement

    Before
    Kevin O'Leary said his company screwed up in communicating the Stratos project
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5383. · a statement · the row of a statement

    Before
    Kevin O'Leary said his company screwed up in communicating the Stratos project
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5384. · a statement · the row of a statement

    Before
    Jake Garfield, Utah Office of Energy Development Deputy Director, said adopting new water efficient technologies is necessary in a state with constrained water resources
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5385. · a statement · the row of a statement

    Before
    Jake Garfield, Utah Office of Energy Development Deputy Director, said adopting new water efficient technologies is necessary in a state with constrained water resources
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5386. · a statement · the row of a statement

    Before
    Jake Garfield, Utah Office of Energy Development Deputy Director, said adopting new water efficient technologies is necessary in a state with constrained water resources
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5387. · a statement · the row of a statement

    Before
    Cox said he would be open to requiring all future data center proposals to use closed loop cooling
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5388. · a statement · the row of a statement

    Before
    Cox said he would be open to requiring all future data center proposals to use closed loop cooling
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5389. · a statement · the row of a statement

    Before
    Cox said he would be open to requiring all future data center proposals to use closed loop cooling
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5390. · a statement · the row of a statement

    Before
    Cox said the approval process was not good and called for major reform of the MIDA process
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5391. · a statement · the row of a statement

    Before
    Cox said the approval process was not good and called for major reform of the MIDA process
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5392. · a statement · the row of a statement

    Before
    Cox said the approval process was not good and called for major reform of the MIDA process
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5393. · a statement · the row of a statement

    Before
    Cox said the Stratos Project in Box Elder County experienced incredible public pushback earlier this year
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5394. · a statement · the row of a statement

    Before
    Cox said the Stratos Project in Box Elder County experienced incredible public pushback earlier this year
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5395. · a statement · the row of a statement

    Before
    Cox said the Stratos Project in Box Elder County experienced incredible public pushback earlier this year
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5396. · a statement · the row of a statement

    Before
    Dr. Brian Moench with Utah Physicians for a Healthy Environment called for a one year moratorium on data centers throughout Utah
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5397. · a statement · the row of a statement

    Before
    Dr. Brian Moench with Utah Physicians for a Healthy Environment called for a one year moratorium on data centers throughout Utah
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5398. · a statement · the row of a statement

    Before
    Dr. Brian Moench with Utah Physicians for a Healthy Environment called for a one year moratorium on data centers throughout Utah
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5399. · a statement · the row of a statement

    Before
    Brittany Lopez, Assistant County Manager, said the county is establishing land use to ensure responsible planning and smart growth if data centers are proposed
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5400. · a statement · the row of a statement

    Before
    Brittany Lopez, Assistant County Manager, said the county is establishing land use to ensure responsible planning and smart growth if data centers are proposed
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5401. · a statement · the row of a statement

    Before
    Brittany Lopez, Assistant County Manager, said the county is establishing land use to ensure responsible planning and smart growth if data centers are proposed
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5402. · a statement · the row of a statement

    Before
    Amy Lawson said residents want to preserve Tooele County's quiet, peace, and land for future generations
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5403. · a statement · the row of a statement

    Before
    Amy Lawson said residents want to preserve Tooele County's quiet, peace, and land for future generations
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5404. · a statement · the row of a statement

    Before
    Amy Lawson said residents want to preserve Tooele County's quiet, peace, and land for future generations
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5405. · a statement · the row of a statement

    Before
    Pennsylvania Gov. Josh Shapiro shifted his stance from generally supporting data centers to placing restrictions after Republican opposition criticism, recently signing an executive order imposing new
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5406. · a statement · the row of a statement

    Before
    Pennsylvania Gov. Josh Shapiro shifted his stance from generally supporting data centers to placing restrictions after Republican opposition criticism, recently signing an executive order imposing new
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5407. · a statement · the row of a statement

    Before
    Gov. Greg Abbott recently endorsed an 'audit' of data center development while Texas studies their impact
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5408. · a statement · the row of a statement

    Before
    Gov. Greg Abbott recently endorsed an 'audit' of data center development while Texas studies their impact
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5409. · a statement · the row of a statement

    Before
    Pennsylvania Gov. Josh Shapiro shifted his stance from generally supporting data centers to placing restrictions after Republican opposition criticism, recently signing an executive order imposing new
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5410. · a statement · the row of a statement

    Before
    Texas Democratic gubernatorial candidate Gina Hinojosa asserted that Gov. Greg Abbott is too sympathetic to data centers and that there needs better balance between tech and community concerns
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5411. · a statement · the row of a statement

    Before
    Texas Democratic gubernatorial candidate Gina Hinojosa asserted that Gov. Greg Abbott is too sympathetic to data centers and that there needs better balance between tech and community concerns
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5412. · a statement · the row of a statement

    Before
    Gov. Greg Abbott recently endorsed an 'audit' of data center development while Texas studies their impact
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5413. · a statement · the row of a statement

    Before
    Ohio Democratic Senate candidate Sherrod Brown is running an ad calling incumbent Sen. Jon Husted the 'face of data centers' for supporting tax breaks and economic benefits
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5414. · a statement · the row of a statement

    Before
    Ohio Democratic Senate candidate Sherrod Brown is running an ad calling incumbent Sen. Jon Husted the 'face of data centers' for supporting tax breaks and economic benefits
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5415. · a statement · the row of a statement

    Before
    Texas Democratic gubernatorial candidate Gina Hinojosa asserted that Gov. Greg Abbott is too sympathetic to data centers and that there needs better balance between tech and community concerns
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5416. · a statement · the row of a statement

    Before
    Ohio Democratic Senate candidate Sherrod Brown is running an ad calling incumbent Sen. Jon Husted the 'face of data centers' for supporting tax breaks and economic benefits
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5417. · a statement · the row of a statement

    Before
    The article describes data center opposition as rooted in opposition to water rationing, spikes in electrical bills, and resource plunder affecting quality of life
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5418. · a statement · the row of a statement

    Before
    Ryan Cooper of The American Prospect characterizes the data center rollout as reflective of Silicon Valley arrogance by billionaires promoting AI as revolutionary and requiring trillions in spending
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5419. · a statement · the row of a statement

    Before
    The article describes data center opposition as rooted in opposition to water rationing, spikes in electrical bills, and resource plunder affecting quality of life
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5420. · a statement · the row of a statement

    Before
    The article describes data center opposition as rooted in opposition to water rationing, spikes in electrical bills, and resource plunder affecting quality of life
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5421. · a statement · the row of a statement

    Before
    Ryan Cooper of The American Prospect characterizes the data center rollout as reflective of Silicon Valley arrogance by billionaires promoting AI as revolutionary and requiring trillions in spending
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5422. · a statement · the row of a statement

    Before
    Ryan Cooper of The American Prospect characterizes the data center rollout as reflective of Silicon Valley arrogance by billionaires promoting AI as revolutionary and requiring trillions in spending
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5423. · a statement · the row of a statement

    Before
    Trump warned that if Americans 'kill the Golden Goose' on data centers, 'you will have only yourselves to blame' and that China is happy about anti data center sentiment
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5424. · a statement · the row of a statement

    Before
    President Donald Trump posted on Truth Social saying data centers will serve economic self interest and national security, telling supporters to 'let Data Reign' or risk being 'backwards and poor'
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5425. · a statement · the row of a statement

    Before
    Trump warned that if Americans 'kill the Golden Goose' on data centers, 'you will have only yourselves to blame' and that China is happy about anti data center sentiment
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5426. · a statement · the row of a statement

    Before
    Trump warned that if Americans 'kill the Golden Goose' on data centers, 'you will have only yourselves to blame' and that China is happy about anti data center sentiment
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5427. · a statement · the row of a statement

    Before
    President Donald Trump posted on Truth Social saying data centers will serve economic self interest and national security, telling supporters to 'let Data Reign' or risk being 'backwards and poor'
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5428. · a statement · the row of a statement

    Before
    President Donald Trump posted on Truth Social saying data centers will serve economic self interest and national security, telling supporters to 'let Data Reign' or risk being 'backwards and poor'
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5429. · a statement · the row of a statement

    Before
    House Speaker Mike Schultz said 'One thing that I think we're united on is we do not want a state full of data centers'
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5430. · a statement · the row of a statement

    Before
    Cox said people need an opportunity to weigh in on data center development and local communities need a better opportunity
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5431. · a statement · the row of a statement

    Before
    House Speaker Mike Schultz said 'One thing that I think we're united on is we do not want a state full of data centers'
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5432. · a statement · the row of a statement

    Before
    Cox advocated for changes to MIDA including more involvement from the governor's office
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5433. · a statement · the row of a statement

    Before
    Cox said people need an opportunity to weigh in on data center development and local communities need a better opportunity
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5434. · a statement · the row of a statement

    Before
    House Speaker Mike Schultz said 'One thing that I think we're united on is we do not want a state full of data centers'
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5435. · a statement · the row of a statement

    Before
    Cox said the process for approving the Stratos Project was not good
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5436. · a statement · the row of a statement

    Before
    Cox advocated for changes to MIDA including more involvement from the governor's office
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5437. · a statement · the row of a statement

    Before
    Cox said people need an opportunity to weigh in on data center development and local communities need a better opportunity
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5438. · a statement · the row of a statement

    Before
    Cox said the process for approving the Stratos Project was not good
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5439. · a statement · the row of a statement

    Before
    Cox advocated for changes to MIDA including more involvement from the governor's office
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5440. · a statement · the row of a statement

    Before
    Cox said the process for approving the Stratos Project was not good
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5441. · a statement · the row of a statement

    Before
    Gov. Cox said MIDA has had mission creep and needs major reform
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5442. · a statement · the row of a statement

    Before
    Gov. Cox said MIDA has had mission creep and needs major reform
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5443. · a statement · the row of a statement

    Before
    Gov. Spencer Cox said the Stratos project process was not good and the MIDA process especially needed scrutiny
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5444. · a statement · the row of a statement

    Before
    Gov. Cox said MIDA has had mission creep and needs major reform
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5445. · a statement · the row of a statement

    Before
    Gov. Spencer Cox said the Stratos project process was not good and the MIDA process especially needed scrutiny
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5446. · a statement · the row of a statement

    Before
    Gov. Spencer Cox said the Stratos project process was not good and the MIDA process especially needed scrutiny
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5447. · a statement · the row of a statement

    Before
    Maddy Oritt, director of public finance research at Gardner Institute, said careful project specific analysis can help communities maximize benefits of data center investment while minimizing unintend
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5448. · a statement · the row of a statement

    Before
    Maddy Oritt, director of public finance research at Gardner Institute, said careful project specific analysis can help communities maximize benefits of data center investment while minimizing unintend
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5449. · a statement · the row of a statement

    Before
    Maddy Oritt, director of public finance research at Gardner Institute, said careful project specific analysis can help communities maximize benefits of data center investment while minimizing unintend
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5450. · a statement · the row of a statement

    Before
    Jessica Wiarda, Salt Lake City resident, expressed concerns about data center effects on wildlife, especially deer, and about lack of public information on the Stratos project before officials voted o
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5451. · a statement · the row of a statement

    Before
    Jessica Wiarda, Salt Lake City resident, expressed concerns about data center effects on wildlife, especially deer, and about lack of public information on the Stratos project before officials voted o
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5452. · a statement · the row of a statement

    Before
    Rep. Jim Dunnigan, R Taylorsville, expressed concern about Utah giving away significant tax breaks to attract data centers while needing the jobs
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5453. · a statement · the row of a statement

    Before
    Rep. Jim Dunnigan, R Taylorsville, expressed concern about Utah giving away significant tax breaks to attract data centers while needing the jobs
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5454. · a statement · the row of a statement

    Before
    Kevin O'Leary told The Salt Lake Tribune in July that Stratos backers are full steam ahead on the project
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5455. · a statement · the row of a statement

    Before
    Jessica Wiarda, Salt Lake City resident, expressed concerns about data center effects on wildlife, especially deer, and about lack of public information on the Stratos project before officials voted o
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5456. · a statement · the row of a statement

    Before
    Kevin O'Leary told The Salt Lake Tribune in July that Stratos backers are full steam ahead on the project
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5457. · a statement · the row of a statement

    Before
    Davis stated that the Department of Environmental Quality has not yet begun air quality permitting work for the Box Elder County Stratos project and that once it does, it will take a year just to obta
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5458. · a statement · the row of a statement

    Before
    Davis stated that the Department of Environmental Quality has not yet begun air quality permitting work for the Box Elder County Stratos project and that once it does, it will take a year just to obta
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5459. · a statement · the row of a statement

    Before
    Rep. Jim Dunnigan, R Taylorsville, expressed concern about Utah giving away significant tax breaks to attract data centers while needing the jobs
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5460. · a statement · the row of a statement

    Before
    Tim Davis said state agencies have been discussing how to coordinate better on data center approvals
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5461. · a statement · the row of a statement

    Before
    Kevin O'Leary told The Salt Lake Tribune in July that Stratos backers are full steam ahead on the project
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5462. · a statement · the row of a statement

    Before
    Tim Davis said state agencies have been discussing how to coordinate better on data center approvals
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5463. · a statement · the row of a statement

    Before
    Rep. Doug Fiefia, R Herriman, expressed concern about who constituents could hold accountable if something falls through the cracks in a data center approval process
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5464. · a statement · the row of a statement

    Before
    Davis stated that the Department of Environmental Quality has not yet begun air quality permitting work for the Box Elder County Stratos project and that once it does, it will take a year just to obta
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5465. · a statement · the row of a statement

    Before
    Rep. Doug Fiefia, R Herriman, expressed concern about who constituents could hold accountable if something falls through the cracks in a data center approval process
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5466. · a statement · the row of a statement

    Before
    Tim Davis, commissioner of Utah's Department of Environmental Quality, noted that no single state agency can fully approve a data center on its own and showed lawmakers a chart displaying many layers
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5467. · a statement · the row of a statement

    Before
    Tim Davis said state agencies have been discussing how to coordinate better on data center approvals
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5468. · a statement · the row of a statement

    Before
    Tim Davis, commissioner of Utah's Department of Environmental Quality, noted that no single state agency can fully approve a data center on its own and showed lawmakers a chart displaying many layers
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5469. · a statement · the row of a statement

    Before
    Rep. Jon Hawkins, R Pleasant Grove, chair of the Economic Development and Workforce Services Interim Committee, stated that lawmakers have received probably hundreds of emails on data centers and that
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5470. · a statement · the row of a statement

    Before
    Rep. Doug Fiefia, R Herriman, expressed concern about who constituents could hold accountable if something falls through the cracks in a data center approval process
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5471. · a statement · the row of a statement

    Before
    Rep. Jon Hawkins, R Pleasant Grove, chair of the Economic Development and Workforce Services Interim Committee, stated that lawmakers have received probably hundreds of emails on data centers and that
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5472. · a statement · the row of a statement

    Before
    Tim Davis, commissioner of Utah's Department of Environmental Quality, noted that no single state agency can fully approve a data center on its own and showed lawmakers a chart displaying many layers
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5473. · a statement · the row of a statement

    Before
    Rep. Jon Hawkins, R Pleasant Grove, chair of the Economic Development and Workforce Services Interim Committee, stated that lawmakers have received probably hundreds of emails on data centers and that
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5474. · a statement · the row of a statement

    Before
    Brenna Williams, co founder of Box Elder Accountability Referendum, says data center economic promises are 'all smoke and mirrors'
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5475. · a statement · the row of a statement

    Before
    Brenna Williams, co founder of Box Elder Accountability Referendum, says data center economic promises are 'all smoke and mirrors'
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5476. · a statement · the row of a statement

    Before
    Shon Hiatt said he would expect larger data centers coming in now to have an impact on power prices wholesale
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5477. · a statement · the row of a statement

    Before
    Shon Hiatt said he would expect larger data centers coming in now to have an impact on power prices wholesale
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5478. · a statement · the row of a statement

    Before
    Non investor owned utilities have difficulty handling new data centers and raise prices as a result
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5479. · a statement · the row of a statement

    Before
    Brenna Williams, co founder of Box Elder Accountability Referendum, says data center economic promises are 'all smoke and mirrors'
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5480. · a statement · the row of a statement

    Before
    Non investor owned utilities have difficulty handling new data centers and raise prices as a result
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5481. · a statement · the row of a statement

    Before
    Shon Hiatt, associate professor at USC, found investor owned utilities like Rocky Mountain Power experienced no effect on power prices from data center entry from 2020 to 2025
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5482. · a statement · the row of a statement

    Before
    Shon Hiatt said he would expect larger data centers coming in now to have an impact on power prices wholesale
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5483. · a statement · the row of a statement

    Before
    Shon Hiatt, associate professor at USC, found investor owned utilities like Rocky Mountain Power experienced no effect on power prices from data center entry from 2020 to 2025
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5484. · a statement · the row of a statement

    Before
    Non investor owned utilities have difficulty handling new data centers and raise prices as a result
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5485. · a statement · the row of a statement

    Before
    Shon Hiatt, associate professor at USC, found investor owned utilities like Rocky Mountain Power experienced no effect on power prices from data center entry from 2020 to 2025
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5486. · a statement · the row of a statement

    Before
    Local resident Teresa Pierce expressed concern about noise, emissions and impact on properties near the proposed data center
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5487. · a statement · the row of a statement

    Before
    Volition CEO said their closed loop cooling system would only need about two Utah households' worth of water to fill
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5488. · a statement · the row of a statement

    Before
    Local resident Teresa Pierce expressed concern about noise, emissions and impact on properties near the proposed data center
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5489. · a statement · the row of a statement

    Before
    Volition CEO Jeff Chavez said their data center project would generate about 250 megawatts of power and use an existing distribution center of about 28 acres
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5490. · a statement · the row of a statement

    Before
    Local resident Teresa Pierce expressed concern about noise, emissions and impact on properties near the proposed data center
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5491. · a statement · the row of a statement

    Before
    Volition CEO said their closed loop cooling system would only need about two Utah households' worth of water to fill
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5492. · a statement · the row of a statement

    Before
    Volition CEO said their closed loop cooling system would only need about two Utah households' worth of water to fill
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5493. · a statement · the row of a statement

    Before
    Volition CEO Jeff Chavez said their data center project would generate about 250 megawatts of power and use an existing distribution center of about 28 acres
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5494. · a statement · the row of a statement

    Before
    Volition CEO Jeff Chavez said their data center project would generate about 250 megawatts of power and use an existing distribution center of about 28 acres
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5495. · a statement · the row of a statement

    Before
    Many data centers already operate in Utah without public protest
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5496. · a statement · the row of a statement

    Before
    Many data centers already operate in Utah without public protest
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5497. · a statement · the row of a statement

    Before
    Alex Kellgreen created an interactive tool called The Elephant in the Desert showing every data center operating in Utah
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5498. · a statement · the row of a statement

    Before
    Many data centers already operate in Utah without public protest
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5499. · a statement · the row of a statement

    Before
    Alex Kellgreen created an interactive tool called The Elephant in the Desert showing every data center operating in Utah
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5500. · a statement · the row of a statement

    Before
    Alex Kellgreen created an interactive tool called The Elephant in the Desert showing every data center operating in Utah
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5501. · a statement · the row of a statement

    Before
    Rep. Paul Cutler said smaller data centers don't have the outsize impact that the 100 megawatt plus data centers do
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5502. · a statement · the row of a statement

    Before
    Rep. Paul Cutler said smaller data centers don't have the outsize impact that the 100 megawatt plus data centers do
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5503. · a statement · the row of a statement

    Before
    Kasia Tarczynska, who authored the Good Jobs First report, said states created tax exemptions based on smaller scale data centers from 10 to 15 years ago but the industry has changed dramatically due
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5504. · a statement · the row of a statement

    Before
    Kasia Tarczynska, who authored the Good Jobs First report, said states created tax exemptions based on smaller scale data centers from 10 to 15 years ago but the industry has changed dramatically due
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5505. · a statement · the row of a statement

    Before
    Kristian Fors, analyst with Libertas Institute, stated 'You can't manage what you can't measure' and stressed the need for transparency and accountability in government policy
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5506. · a statement · the row of a statement

    Before
    Kristian Fors, analyst with Libertas Institute, stated 'You can't manage what you can't measure' and stressed the need for transparency and accountability in government policy
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5507. · a statement · the row of a statement

    Before
    Kasia Tarczynska, who authored the Good Jobs First report, said states created tax exemptions based on smaller scale data centers from 10 to 15 years ago but the industry has changed dramatically due
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5508. · a statement · the row of a statement

    Before
    Rep. Jill Koford, R Ogden, stated that the scale and rapid growth of data center investment raise legitimate questions about whether the current framework and available data remain adequate
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5509. · a statement · the row of a statement

    Before
    Kristian Fors, analyst with Libertas Institute, stated 'You can't manage what you can't measure' and stressed the need for transparency and accountability in government policy
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5510. · a statement · the row of a statement

    Before
    Rep. Jill Koford, R Ogden, stated that the scale and rapid growth of data center investment raise legitimate questions about whether the current framework and available data remain adequate
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5511. · a statement · the row of a statement

    Before
    Rep. Jill Koford, R Ogden, stated that the scale and rapid growth of data center investment raise legitimate questions about whether the current framework and available data remain adequate
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5512. · a statement · the row of a statement

    Before
    Physicist Robert Davies of Utah State University estimated the project could reach 16 gigawatts at full capacity
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5513. · a statement · the row of a statement

    Before
    Physicist Robert Davies of Utah State University estimated the project could reach 16 gigawatts at full capacity
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5514. · a statement · the row of a statement

    Before
    Utah Senate President J. Stuart Adams publicly called for a 75% reduction in the facility's size
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5515. · a statement · the row of a statement

    Before
    Physicist Robert Davies of Utah State University estimated the project could reach 16 gigawatts at full capacity
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5516. · a statement · the row of a statement

    Before
    Utah Senate President J. Stuart Adams publicly called for a 75% reduction in the facility's size
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5517. · a statement · the row of a statement

    Before
    Utah Senate President J. Stuart Adams publicly called for a 75% reduction in the facility's size
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5518. · a statement · the row of a statement

    Before
    O'Leary pledged to release plans for a one gigawatt facility detailing its heat, light, noise and water profile
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5519. · a statement · the row of a statement

    Before
    Kevin O'Leary said 'We have not properly communicated what we do. I have no interest in causing an environmental disaster on my legacy.'
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5520. · a statement · the row of a statement

    Before
    O'Leary pledged to release plans for a one gigawatt facility detailing its heat, light, noise and water profile
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5521. · a statement · the row of a statement

    Before
    O'Leary pledged to release plans for a one gigawatt facility detailing its heat, light, noise and water profile
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5522. · a statement · the row of a statement

    Before
    Kevin O'Leary said 'We have not properly communicated what we do. I have no interest in causing an environmental disaster on my legacy.'
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5523. · a statement · the row of a statement

    Before
    Kevin O'Leary said 'We have not properly communicated what we do. I have no interest in causing an environmental disaster on my legacy.'
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5524. · a statement · the row of a statement

    Before
    Author Allyson Flake Matsoso expresses concerns about data centers changing small town America, citing impacts like noise, traffic, heat and light pollution
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5525. · a statement · the row of a statement

    Before
    West Jordan Mayor Dirk Burton argued that data centers help keep taxes low for residents and provide needed services
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5526. · a statement · the row of a statement

    Before
    Author Allyson Flake Matsoso expresses concerns about data centers changing small town America, citing impacts like noise, traffic, heat and light pollution
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5527. · a statement · the row of a statement

    Before
    Author Allyson Flake Matsoso expresses concerns about data centers changing small town America, citing impacts like noise, traffic, heat and light pollution
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5528. · a statement · the row of a statement

    Before
    Mona City government said they had not received any formal data center application or development requests and have not made a commitment of water, sewer, or electricity for this data center
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5529. · a statement · the row of a statement

    Before
    West Jordan Mayor Dirk Burton argued that data centers help keep taxes low for residents and provide needed services
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5530. · a statement · the row of a statement

    Before
    West Jordan Mayor Dirk Burton argued that data centers help keep taxes low for residents and provide needed services
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5531. · a statement · the row of a statement

    Before
    Mona City government said they had not received any formal data center application or development requests and have not made a commitment of water, sewer, or electricity for this data center
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5532. · a statement · the row of a statement

    Before
    Mona City government said they had not received any formal data center application or development requests and have not made a commitment of water, sewer, or electricity for this data center
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5533. · a statement · the row of a statement

    Before
    Volition executives said they would not be drawing off the local power grid or emitting excess heat, noise, and air pollution
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5534. · a statement · the row of a statement

    Before
    Volition executives said they would not be drawing off the local power grid or emitting excess heat, noise, and air pollution
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5535. · a statement · the row of a statement

    Before
    Volition said they may have to seek a new community to build their data center if further delays occur
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5536. · a statement · the row of a statement

    Before
    Volition executives said they would not be drawing off the local power grid or emitting excess heat, noise, and air pollution
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5537. · a statement · the row of a statement

    Before
    Volition said they may have to seek a new community to build their data center if further delays occur
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5538. · a statement · the row of a statement

    Before
    Volition said they may have to seek a new community to build their data center if further delays occur
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5539. · a statement · the row of a statement

    Before
    Volition CEO Jeff Chavez said Volition facilities differ from traditional data centers by generating their own power using natural gas powered fuel cells that do not connect to or place demands on the
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5540. · a statement · the row of a statement

    Before
    Mayor Mike Mendenhall said on social media he thought the Volition proposal could be good for the city
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5541. · a statement · the row of a statement

    Before
    Volition CEO Jeff Chavez said Volition facilities differ from traditional data centers by generating their own power using natural gas powered fuel cells that do not connect to or place demands on the
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5542. · a statement · the row of a statement

    Before
    Mayor Mike Mendenhall said on social media he thought the Volition proposal could be good for the city
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5543. · a statement · the row of a statement

    Before
    Volition CEO Jeff Chavez said Volition facilities differ from traditional data centers by generating their own power using natural gas powered fuel cells that do not connect to or place demands on the
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5544. · a statement · the row of a statement

    Before
    Mayor Mike Mendenhall said on social media he thought the Volition proposal could be good for the city
    After
    deleted
    Why
    Duplicate of the statement the card names, written by the repeated checklist Apply of 2026-09-13; deleted.

  5545. · Volition Industries Spanish Fork · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Duplicate of the row the card names, written by the repeated checklist Apply of 2026-09-13; returned to draft.

  5546. · Volition Industries Spanish Fork · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Duplicate of the row the card names, written by the repeated checklist Apply of 2026-09-13; returned to draft.

  5547. · Volition Industries Spanish Fork · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Duplicate of the row the card names, written by the repeated checklist Apply of 2026-09-13; returned to draft.

  5548. · Volition Industries Spanish Fork · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Duplicate of the row the card names, written by the repeated checklist Apply of 2026-09-13; returned to draft.

  5549. · Volition Industries Spanish Fork · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Duplicate of the row the card names, written by the repeated checklist Apply of 2026-09-13; returned to draft.

  5550. · Volition Industries Spanish Fork · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Duplicate of the row the card names, written by the repeated checklist Apply of 2026-09-13; returned to draft.

  5551. · Volition Industries Spanish Fork · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Duplicate of the row the card names, written by the repeated checklist Apply of 2026-09-13; returned to draft.

  5552. · google-fervo-geothermal-utah-ut · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Duplicate of the row the card names, written by the repeated checklist Apply of 2026-09-13; returned to draft.

  5553. · google-fervo-geothermal-utah-ut · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Duplicate of the row the card names, written by the repeated checklist Apply of 2026-09-13; returned to draft.

  5554. · google-fervo-geothermal-utah-ut · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Duplicate of the row the card names, written by the repeated checklist Apply of 2026-09-13; returned to draft.

  5555. · google-fervo-geothermal-utah-ut · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Duplicate of the row the card names, written by the repeated checklist Apply of 2026-09-13; returned to draft.

  5556. · google-fervo-geothermal-utah-ut · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Duplicate of the row the card names, written by the repeated checklist Apply of 2026-09-13; returned to draft.

  5557. · google-fervo-geothermal-utah-ut · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Duplicate of the row the card names, written by the repeated checklist Apply of 2026-09-13; returned to draft.

  5558. · google-fervo-geothermal-utah-ut · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Duplicate of the row the card names, written by the repeated checklist Apply of 2026-09-13; returned to draft.

  5559. · Stratos Project · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Duplicate of the row the card names, written by the repeated checklist Apply of 2026-09-13; returned to draft.

  5560. · Stratos Project · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Duplicate of the row the card names, written by the repeated checklist Apply of 2026-09-13; returned to draft.

  5561. · Stratos Project · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Duplicate of the row the card names, written by the repeated checklist Apply of 2026-09-13; returned to draft.

  5562. · Stratos Project · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Duplicate of the row the card names, written by the repeated checklist Apply of 2026-09-13; returned to draft.

  5563. · Stratos Project · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Duplicate of the row the card names, written by the repeated checklist Apply of 2026-09-13; returned to draft.

  5564. · Stratos Project · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Duplicate of the row the card names, written by the repeated checklist Apply of 2026-09-13; returned to draft.

  5565. · Stratos Project · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Duplicate of the row the card names, written by the repeated checklist Apply of 2026-09-13; returned to draft.

  5566. · Stratos Project · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Duplicate of the row the card names, written by the repeated checklist Apply of 2026-09-13; returned to draft.

  5567. · Stratos Project · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Duplicate of the row the card names, written by the repeated checklist Apply of 2026-09-13; returned to draft.

  5568. · Stratos Project · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Duplicate of the row the card names, written by the repeated checklist Apply of 2026-09-13; returned to draft.

  5569. · Stratos Project · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Duplicate of the row the card names, written by the repeated checklist Apply of 2026-09-13; returned to draft.

  5570. · Stratos Project · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Duplicate of the row the card names, written by the repeated checklist Apply of 2026-09-13; returned to draft.

  5571. · Stratos Project · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Duplicate of the row the card names, written by the repeated checklist Apply of 2026-09-13; returned to draft.

  5572. · Stratos Project · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Duplicate of the row the card names, written by the repeated checklist Apply of 2026-09-13; returned to draft.

  5573. · Stratos Project · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Duplicate of the row the card names, written by the repeated checklist Apply of 2026-09-13; returned to draft.

  5574. · google-fervo-geothermal-utah-ut · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Duplicate of the row the card names, written by the repeated checklist Apply of 2026-09-13; returned to draft.

  5575. · google-fervo-geothermal-utah-ut · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Duplicate of the row the card names, written by the repeated checklist Apply of 2026-09-13; returned to draft.

  5576. · google-fervo-geothermal-utah-ut · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Duplicate of the row the card names, written by the repeated checklist Apply of 2026-09-13; returned to draft.

  5577. · google-fervo-geothermal-utah-ut · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Duplicate of the row the card names, written by the repeated checklist Apply of 2026-09-13; returned to draft.

  5578. · google-fervo-geothermal-utah-ut · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Duplicate of the row the card names, written by the repeated checklist Apply of 2026-09-13; returned to draft.

  5579. · google-fervo-geothermal-utah-ut · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Duplicate of the row the card names, written by the repeated checklist Apply of 2026-09-13; returned to draft.

  5580. · Stratos Project · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Duplicate of the row the card names, written by the repeated checklist Apply of 2026-09-13; returned to draft.

  5581. · Stratos Project · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Duplicate of the row the card names, written by the repeated checklist Apply of 2026-09-13; returned to draft.

  5582. · Stratos Project · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Duplicate of the row the card names, written by the repeated checklist Apply of 2026-09-13; returned to draft.

  5583. · Stratos Project · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Duplicate of the row the card names, written by the repeated checklist Apply of 2026-09-13; returned to draft.

  5584. · Stratos Project · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Duplicate of the row the card names, written by the repeated checklist Apply of 2026-09-13; returned to draft.

  5585. · Stratos Project · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Duplicate of the row the card names, written by the repeated checklist Apply of 2026-09-13; returned to draft.

  5586. · Stratos Project · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Duplicate of the row the card names, written by the repeated checklist Apply of 2026-09-13; returned to draft.

  5587. · Stratos Project · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Duplicate of the row the card names, written by the repeated checklist Apply of 2026-09-13; returned to draft.

  5588. · Stratos Project · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Duplicate of the row the card names, written by the repeated checklist Apply of 2026-09-13; returned to draft.

  5589. · Stratos Project · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Duplicate of the row the card names, written by the repeated checklist Apply of 2026-09-13; returned to draft.

  5590. · Stratos Project · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Duplicate of the row the card names, written by the repeated checklist Apply of 2026-09-13; returned to draft.

  5591. · Stratos Project · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Duplicate of the row the card names, written by the repeated checklist Apply of 2026-09-13; returned to draft.

  5592. · Volition Industries Spanish Fork · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Duplicate of the row the card names, written by the repeated checklist Apply of 2026-09-13; returned to draft.

  5593. · Volition Industries Spanish Fork · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Duplicate of the row the card names, written by the repeated checklist Apply of 2026-09-13; returned to draft.

  5594. · Volition Industries Spanish Fork · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Duplicate of the row the card names, written by the repeated checklist Apply of 2026-09-13; returned to draft.

  5595. · Stratos Project · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Duplicate of the row the card names, written by the repeated checklist Apply of 2026-09-13; returned to draft.

  5596. · Stratos Project · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Duplicate of the row the card names, written by the repeated checklist Apply of 2026-09-13; returned to draft.

  5597. · Stratos Project · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Duplicate of the row the card names, written by the repeated checklist Apply of 2026-09-13; returned to draft.

  5598. · Stratos Project · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Duplicate of the row the card names, written by the repeated checklist Apply of 2026-09-13; returned to draft.

  5599. · Stratos Project · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Duplicate of the row the card names, written by the repeated checklist Apply of 2026-09-13; returned to draft.

  5600. · Stratos Project · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Duplicate of the row the card names, written by the repeated checklist Apply of 2026-09-13; returned to draft.

  5601. · Volition Industries Spanish Fork · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Duplicate of the row the card names, written by the repeated checklist Apply of 2026-09-13; returned to draft.

  5602. · Volition Industries Spanish Fork · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Duplicate of the row the card names, written by the repeated checklist Apply of 2026-09-13; returned to draft.

  5603. · Volition Industries Spanish Fork · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Duplicate of the row the card names, written by the repeated checklist Apply of 2026-09-13; returned to draft.

  5604. · Google Bridgeport data center · the summary of a timeline entry

    Before
    The data center began operating in 2019 (Entry dated by the video's upload date; see the correction.)
    After
    The data center began operating in 2019
    Why
    The note "(Entry dated by the video's upload date; see the correction.)" appended by the date correction of 2026-09-08 belongs in this log, not in the event sentence; the date basis of the row already says the date is the source's. The sentence is restored to the event only (2026-09-13).

  5605. · Google Bridgeport data center · the summary of a timeline entry

    Before
    Less than a quarter of the campus property has been developed so far (Entry dated by the video's upload date; see the correction.)
    After
    Less than a quarter of the campus property has been developed so far
    Why
    The note "(Entry dated by the video's upload date; see the correction.)" appended by the date correction of 2026-09-08 belongs in this log, not in the event sentence; the date basis of the row already says the date is the source's. The sentence is restored to the event only (2026-09-13).

  5606. · Meta Louisiana data center · the summary of a timeline entry

    Before
    The data center will be fueled by 10 newly constructed natural gas plants (Entry dated by the video's upload date; see the correction.)
    After
    The data center will be fueled by 10 newly constructed natural gas plants
    Why
    The note "(Entry dated by the video's upload date; see the correction.)" appended by the date correction of 2026-09-08 belongs in this log, not in the event sentence; the date basis of the row already says the date is the source's. The sentence is restored to the event only (2026-09-13).

  5607. · Meta Louisiana data center · the summary of a timeline entry

    Before
    Meta is building its largest AI data center in Richland Parish, Louisiana (Entry dated by the video's upload date; see the correction.)
    After
    Meta is building its largest AI data center in Richland Parish, Louisiana
    Why
    The note "(Entry dated by the video's upload date; see the correction.)" appended by the date correction of 2026-09-08 belongs in this log, not in the event sentence; the date basis of the row already says the date is the source's. The sentence is restored to the event only (2026-09-13).

  5608. · Google Pine Island Data Center · the summary of a timeline entry

    Before
    The project site is located less than half a mile from a nearby residential home (Entry dated by the video's upload date; see the correction.)
    After
    The project site is located less than half a mile from a nearby residential home
    Why
    The note "(Entry dated by the video's upload date; see the correction.)" appended by the date correction of 2026-09-08 belongs in this log, not in the event sentence; the date basis of the row already says the date is the source's. The sentence is restored to the event only (2026-09-13).

  5609. · Google Pine Island Data Center · the summary of a timeline entry

    Before
    The proposed data center will use advanced air cooling and minimal water compared to other data centers (Entry dated by the video's upload date; see the correction.)
    After
    The proposed data center will use advanced air cooling and minimal water compared to other data centers
    Why
    The note "(Entry dated by the video's upload date; see the correction.)" appended by the date correction of 2026-09-08 belongs in this log, not in the event sentence; the date basis of the row already says the date is the source's. The sentence is restored to the event only (2026-09-13).

  5610. · Google Berkeley County data center · the summary of a timeline entry

    Before
    Google has 15 years of presence in South Carolina (Entry dated by the video's upload date; see the correction.)
    After
    Google has 15 years of presence in South Carolina
    Why
    The note "(Entry dated by the video's upload date; see the correction.)" appended by the date correction of 2026-09-08 belongs in this log, not in the event sentence; the date basis of the row already says the date is the source's. The sentence is restored to the event only (2026-09-13).

  5611. · DC Blox Montgomery data center · the summary of a timeline entry

    Before
    Construction on Montgomery data center is scheduled to begin in June of next year (Entry dated by the video's upload date; see the correction.)
    After
    Construction on Montgomery data center is scheduled to begin in June of next year
    Why
    The note "(Entry dated by the video's upload date; see the correction.)" appended by the date correction of 2026-09-08 belongs in this log, not in the event sentence; the date basis of the row already says the date is the source's. The sentence is restored to the event only (2026-09-13).

  5612. · DC Blox Montgomery data center · the summary of a timeline entry

    Before
    DC Blox data center will be located at Interstate Industrial Park near Hope Hull exit on I-65 (Entry dated by the video's upload date; see the correction.)
    After
    DC Blox data center will be located at Interstate Industrial Park near Hope Hull exit on I-65
    Why
    The note "(Entry dated by the video's upload date; see the correction.)" appended by the date correction of 2026-09-08 belongs in this log, not in the event sentence; the date basis of the row already says the date is the source's. The sentence is restored to the event only (2026-09-13).

  5613. · Volition Industries Spanish Fork · the summary of a timeline entry

    Before
    This entry recorded the September 1 delay under the status permitting, before the status rule adopted on 2026-09-05, under which a project waiting on an enabling text amendment is proposed. The entry of the same date and source records the same event as proposed. Spanish Fork City Council delayed the Title 15 vote a second time, for two more weeks, and Volition Industries said it may take the project to another community.
    After
    Spanish Fork City Council delayed the Title 15 vote a second time, for two more weeks, and Volition Industries said it may take the project to another community.
    Why
    The explanation written into this summary by correction 2 (the entry recorded the September 1 delay as permitting before the status rule of 2026-09-05; the entry of the same date and source records it as proposed) belongs in this log, not in the event sentence. The sentence is restored to the event only (2026-09-13).

  5614. · Prometheus Hyperscale Natrona County Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published by a promotion without passing through Approve on 2026-09-08; returned to draft and opened as an Inbox card.

  5615. · Montgomery Meta Investment · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published by a promotion without passing through Approve on 2026-09-08; returned to draft and opened as an Inbox card.

  5616. · Google New Florence data center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published by a promotion without passing through Approve on 2026-09-08; returned to draft and opened as an Inbox card.

  5617. · OpenAI Effingham County Data Center · the publication of a timeline entry

    Before
    published
    After
    draft
    Why
    Published by a promotion without passing through Approve on 2026-09-08; returned to draft and opened as an Inbox card.

  5618. · a record · the publication of a scorecard event

    Before
    published
    After
    draft
    Why
    Published by a promotion without passing through Approve on 2026-09-08; returned to draft and opened as an Inbox card.

  5619. · a record · the publication of a scorecard event

    Before
    published
    After
    draft
    Why
    Published by a promotion without passing through Approve on 2026-09-08; returned to draft and opened as an Inbox card.

  5620. · a record · the publication of a scorecard event

    Before
    published
    After
    draft
    Why
    Published by a promotion without passing through Approve on 2026-09-08; returned to draft and opened as an Inbox card.

  5621. · a record · the publication of a scorecard event

    Before
    published
    After
    draft
    Why
    Published by a promotion without passing through Approve on 2026-09-08; returned to draft and opened as an Inbox card.

  5622. · a record · the publication of a scorecard event

    Before
    published
    After
    draft
    Why
    Published by a promotion without passing through Approve on 2026-09-08; returned to draft and opened as an Inbox card.

  5623. · a record · the publication of a scorecard event

    Before
    published
    After
    draft
    Why
    Published by a promotion without passing through Approve on 2026-09-08; returned to draft and opened as an Inbox card.

  5624. · a record · the publication of a scorecard event

    Before
    published
    After
    draft
    Why
    Published by a promotion without passing through Approve on 2026-09-08; returned to draft and opened as an Inbox card.

  5625. · a record · the publication of a scorecard event

    Before
    published
    After
    draft
    Why
    Published by a promotion without passing through Approve on 2026-09-08; returned to draft and opened as an Inbox card.

  5626. · a record · the publication of a scorecard event

    Before
    published
    After
    draft
    Why
    Published by a promotion without passing through Approve on 2026-09-08; returned to draft and opened as an Inbox card.

  5627. · a record · the publication of a scorecard event

    Before
    published
    After
    draft
    Why
    Published by a promotion without passing through Approve on 2026-09-08; returned to draft and opened as an Inbox card.

  5628. · a record · the publication of a scorecard event

    Before
    published
    After
    draft
    Why
    Published by a promotion without passing through Approve on 2026-09-08; returned to draft and opened as an Inbox card.

  5629. · a record · the publication of a scorecard event

    Before
    published
    After
    draft
    Why
    Published by a promotion without passing through Approve on 2026-09-08; returned to draft and opened as an Inbox card.

  5630. · a record · the publication of a scorecard event

    Before
    published
    After
    draft
    Why
    Published by a promotion without passing through Approve on 2026-09-08; returned to draft and opened as an Inbox card.

  5631. · a record · the publication of a scorecard event

    Before
    published
    After
    draft
    Why
    Published by a promotion without passing through Approve on 2026-09-08; returned to draft and opened as an Inbox card.

  5632. · a record · the publication of a scorecard event

    Before
    published
    After
    draft
    Why
    Published by a promotion without passing through Approve on 2026-09-08; returned to draft and opened as an Inbox card.

  5633. · a record · the publication of a scorecard event

    Before
    published
    After
    draft
    Why
    Published by a promotion without passing through Approve on 2026-09-08; returned to draft and opened as an Inbox card.

  5634. · a record · the publication of a scorecard event

    Before
    published
    After
    draft
    Why
    Published by a promotion without passing through Approve on 2026-09-08; returned to draft and opened as an Inbox card.

  5635. · a record · the publication of a scorecard event

    Before
    published
    After
    draft
    Why
    Published by a promotion without passing through Approve on 2026-09-08; returned to draft and opened as an Inbox card.

  5636. · a record · the publication of a scorecard event

    Before
    published
    After
    draft
    Why
    Published by a promotion without passing through Approve on 2026-09-08; returned to draft and opened as an Inbox card.

  5637. · a record · the publication of a scorecard event

    Before
    published
    After
    draft
    Why
    Published by a promotion without passing through Approve on 2026-09-08; returned to draft and opened as an Inbox card.

  5638. · a record · the publication of a scorecard event

    Before
    published
    After
    draft
    Why
    Published by a promotion without passing through Approve on 2026-09-08; returned to draft and opened as an Inbox card.

  5639. · a statement · the date label of a statement

    Before
    content
    After
    source
    Why
    Date basis recorded (2026-09-08, /methodology#dates): Unnamed resident speaks in the video, so the statement is dated by the video's upload date.

  5640. · Kate Gallego · the date label of a statement

    Before
    content
    After
    source
    Why
    Date basis recorded (2026-09-08, /methodology#dates): Kate Gallego speaks in the video, so the statement is dated by the video's upload date.

  5641. · a statement · the date label of a statement

    Before
    content
    After
    source
    Why
    Date basis recorded (2026-09-08, /methodology#dates): Unnamed resident speaks in the video, so the statement is dated by the video's upload date.

  5642. · a statement · the date label of a statement

    Before
    content
    After
    source
    Why
    Date basis recorded (2026-09-08, /methodology#dates): Patrick Bogle speaks in the video, so the statement is dated by the video's upload date.

  5643. · a statement · the date label of a statement

    Before
    content
    After
    source
    Why
    Date basis recorded (2026-09-08, /methodology#dates): Kate Gallego speaks in the video, so the statement is dated by the video's upload date.

  5644. · a statement · the date label of a statement

    Before
    content
    After
    source
    Why
    Date basis recorded (2026-09-08, /methodology#dates): Patrick Bogle speaks in the video, so the statement is dated by the video's upload date.

  5645. · a statement · the date label of a statement

    Before
    content
    After
    source
    Why
    Date basis recorded (2026-09-08, /methodology#dates): Adam Klepp speaks in the video, so the statement is dated by the video's upload date.

  5646. · a record · the date label of a figure

    Before
    content
    After
    source
    Why
    Date basis recorded (2026-09-08, /methodology#dates): the row's date is the video's upload date, the source's own date, because the content gives no date of its own.

  5647. · a record · the date label of a figure

    Before
    content
    After
    source
    Why
    Date basis recorded (2026-09-08, /methodology#dates): the row's date is the video's upload date, the source's own date, because the content gives no date of its own.

  5648. · a statement · the date label of a statement

    Before
    content
    After
    source
    Why
    Date basis recorded (2026-09-08, /methodology#dates): Patrick Bogle speaks in the video, so the statement is dated by the video's upload date.

  5649. · Google Pine Island Data Center · the date label of a figure

    Before
    content
    After
    source
    Why
    Date basis recorded (2026-09-08, /methodology#dates): the row's date is the video's upload date, the source's own date, because the content gives no date of its own.

  5650. · Google Pine Island Data Center · the date label of a statement

    Before
    content
    After
    source
    Why
    Date basis recorded (2026-09-08, /methodology#dates): Jack Ailey speaks in the video, so the statement is dated by the video's upload date.

  5651. · Google Pine Island Data Center · the date label of a figure

    Before
    content
    After
    source
    Why
    Date basis recorded (2026-09-08, /methodology#dates): the row's date is the video's upload date, the source's own date, because the content gives no date of its own.

  5652. · Google Berkeley County data center · the date label of a figure

    Before
    content
    After
    source
    Why
    Date basis recorded (2026-09-08, /methodology#dates): the row's date is the video's upload date, the source's own date, because the content gives no date of its own.

  5653. · Google Bridgeport data center · the date label of a figure

    Before
    content
    After
    source
    Why
    Date basis recorded (2026-09-08, /methodology#dates): the row's date is the video's upload date, the source's own date, because the content gives no date of its own.

  5654. · Google Bridgeport data center · the date label of a figure

    Before
    content
    After
    source
    Why
    Date basis recorded (2026-09-08, /methodology#dates): the row's date is the video's upload date, the source's own date, because the content gives no date of its own.

  5655. · Google Bridgeport data center · the date label of a figure

    Before
    content
    After
    source
    Why
    Date basis recorded (2026-09-08, /methodology#dates): the row's date is the video's upload date, the source's own date, because the content gives no date of its own.

  5656. · Meta Louisiana data center · the date label of a statement

    Before
    content
    After
    source
    Why
    Date basis recorded (2026-09-08, /methodology#dates): Riley Griffin speaks in the video, so the statement is dated by the video's upload date.

  5657. · Meta Louisiana data center · the date label of a figure

    Before
    content
    After
    source
    Why
    Date basis recorded (2026-09-08, /methodology#dates): the row's date is the video's upload date, the source's own date, because the content gives no date of its own.

  5658. · Meta Louisiana data center · the date label of a statement

    Before
    content
    After
    source
    Why
    Date basis recorded (2026-09-08, /methodology#dates): Riley Griffin speaks in the video, so the statement is dated by the video's upload date.

  5659. · Meta Louisiana data center · the date label of a statement

    Before
    content
    After
    source
    Why
    Date basis recorded (2026-09-08, /methodology#dates): Riley Griffin speaks in the video, so the statement is dated by the video's upload date.

  5660. · Meta Louisiana data center · the date label of a figure

    Before
    content
    After
    source
    Why
    Date basis recorded (2026-09-08, /methodology#dates): the row's date is the video's upload date, the source's own date, because the content gives no date of its own.

  5661. · Meta Louisiana data center · the date label of a figure

    Before
    content
    After
    source
    Why
    Date basis recorded (2026-09-08, /methodology#dates): the row's date is the video's upload date, the source's own date, because the content gives no date of its own.

  5662. · Meta Louisiana data center · the date label of a figure

    Before
    content
    After
    source
    Why
    Date basis recorded (2026-09-08, /methodology#dates): the row's date is the video's upload date, the source's own date, because the content gives no date of its own.

  5663. · Meta Louisiana data center · the date label of a statement

    Before
    content
    After
    source
    Why
    Date basis recorded (2026-09-08, /methodology#dates): Riley Griffin speaks in the video, so the statement is dated by the video's upload date.

  5664. · Meta Louisiana data center · the date label of a figure

    Before
    content
    After
    source
    Why
    Date basis recorded (2026-09-08, /methodology#dates): the row's date is the video's upload date, the source's own date, because the content gives no date of its own.

  5665. · Meta Louisiana data center · the date label of a figure

    Before
    content
    After
    source
    Why
    Date basis recorded (2026-09-08, /methodology#dates): the row's date is the video's upload date, the source's own date, because the content gives no date of its own.

  5666. · DC Blox Montgomery data center · the date label of a statement

    Before
    content
    After
    source
    Why
    Date basis recorded (2026-09-08, /methodology#dates): Valorie Lawson speaks in the video, so the statement is dated by the video's upload date.

  5667. · DC Blox Montgomery data center · the date label of a figure

    Before
    content
    After
    source
    Why
    Date basis recorded (2026-09-08, /methodology#dates): the row's date is the video's upload date, the source's own date, because the content gives no date of its own.

  5668. · DC Blox Montgomery data center · the date label of a statement

    Before
    content
    After
    source
    Why
    Date basis recorded (2026-09-08, /methodology#dates): Valorie Lawson speaks in the video, so the statement is dated by the video's upload date.

  5669. · DC Blox Montgomery data center · the planned of a timeline entry

    Before
    false
    After
    true
    Why
    Planned date recorded (2026-09-08, /methodology#dates): the content states June 2025 as a target, later than the video's date of November 27, 2024.

  5670. · Google Bridgeport data center · the date label of a timeline entry

    Before
    content
    After
    source
    Why
    Date basis recorded (2026-09-08, /methodology#dates): the row's date is the video's upload date, the source's own date, because the content gives no date of its own.

  5671. · Google Bridgeport data center · the date label of a timeline entry

    Before
    content
    After
    source
    Why
    Date basis recorded (2026-09-08, /methodology#dates): the row's date is the video's upload date, the source's own date, because the content gives no date of its own.

  5672. · Meta Louisiana data center · the date label of a timeline entry

    Before
    content
    After
    source
    Why
    Date basis recorded (2026-09-08, /methodology#dates): the row's date is the video's upload date, the source's own date, because the content gives no date of its own.

  5673. · Meta Louisiana data center · the date label of a timeline entry

    Before
    content
    After
    source
    Why
    Date basis recorded (2026-09-08, /methodology#dates): the row's date is the video's upload date, the source's own date, because the content gives no date of its own.

  5674. · Google Pine Island Data Center · the date label of a timeline entry

    Before
    content
    After
    source
    Why
    Date basis recorded (2026-09-08, /methodology#dates): the row's date is the video's upload date, the source's own date, because the content gives no date of its own.

  5675. · Google Pine Island Data Center · the date label of a timeline entry

    Before
    content
    After
    source
    Why
    Date basis recorded (2026-09-08, /methodology#dates): the row's date is the video's upload date, the source's own date, because the content gives no date of its own.

  5676. · Google Berkeley County data center · the date label of a timeline entry

    Before
    content
    After
    source
    Why
    Date basis recorded (2026-09-08, /methodology#dates): the row's date is the video's upload date, the source's own date, because the content gives no date of its own.

  5677. · DC Blox Montgomery data center · the date label of a timeline entry

    Before
    content
    After
    source
    Why
    Date basis recorded (2026-09-08, /methodology#dates): the row's date is the video's upload date, the source's own date, because the content gives no date of its own.

  5678. · DC Blox Montgomery data center · the date label of a timeline entry

    Before
    content
    After
    source
    Why
    Date basis recorded (2026-09-08, /methodology#dates): the row's date is the video's upload date, the source's own date, because the content gives no date of its own.

  5679. · Google Bridgeport data center · the summary of a timeline entry

    Before
    The data center began operating in 2019
    After
    The data center began operating in 2019 (Entry dated by the video's upload date; see the correction.)
    Why
    Dated by the video's upload date (ABC News, 2026-06-19), which is the source date; the corrected entry dated 2019-01-01 carries the year the video gives.

  5680. · Google Bridgeport data center · the summary of a timeline entry

    Before
    Less than a quarter of the campus property has been developed so far
    After
    Less than a quarter of the campus property has been developed so far (Entry dated by the video's upload date; see the correction.)
    Why
    Dated by the video's upload date (ABC News, 2026-06-19), which is the source date; the content says so far, no other date.

  5681. · Meta Louisiana data center · the summary of a timeline entry

    Before
    The data center will be fueled by 10 newly constructed natural gas plants
    After
    The data center will be fueled by 10 newly constructed natural gas plants (Entry dated by the video's upload date; see the correction.)
    Why
    Dated by the video's upload date (Bloomberg Television, 2026-05-23), which is the source date; the content gives no other date.

  5682. · Meta Louisiana data center · the summary of a timeline entry

    Before
    Meta is building its largest AI data center in Richland Parish, Louisiana
    After
    Meta is building its largest AI data center in Richland Parish, Louisiana (Entry dated by the video's upload date; see the correction.)
    Why
    Dated by the video's upload date (Bloomberg Television, 2026-05-23), which is the source date; the content gives no other date.

  5683. · Google Pine Island Data Center · the summary of a timeline entry

    Before
    The project site is located less than half a mile from a nearby residential home
    After
    The project site is located less than half a mile from a nearby residential home (Entry dated by the video's upload date; see the correction.)
    Why
    Dated by the video's upload date (KARE 11, 2026-02-25), which is the source date; the content gives no other date.

  5684. · Google Pine Island Data Center · the summary of a timeline entry

    Before
    The proposed data center will use advanced air cooling and minimal water compared to other data centers
    After
    The proposed data center will use advanced air cooling and minimal water compared to other data centers (Entry dated by the video's upload date; see the correction.)
    Why
    Dated by the video's upload date (KARE 11, 2026-02-25), which is the source date; the content gives no other date.

  5685. · Google Berkeley County data center · the summary of a timeline entry

    Before
    Google has 15 years of presence in South Carolina
    After
    Google has 15 years of presence in South Carolina (Entry dated by the video's upload date; see the correction.)
    Why
    Dated by the video's upload date (ABC News 4, 2025-10-13), which is the source date; the content gives no other date.

  5686. · DC Blox Montgomery data center · the summary of a timeline entry

    Before
    Construction on Montgomery data center is scheduled to begin in June of next year
    After
    Construction on Montgomery data center is scheduled to begin in June of next year (Entry dated by the video's upload date; see the correction.)
    Why
    Dated by the video's upload date (WSFA, 2024-11-27), which is the source date; the corrected entry dated 2025-06-01 carries the month the video gives.

  5687. · DC Blox Montgomery data center · the summary of a timeline entry

    Before
    DC Blox data center will be located at Interstate Industrial Park near Hope Hull exit on I-65
    After
    DC Blox data center will be located at Interstate Industrial Park near Hope Hull exit on I-65 (Entry dated by the video's upload date; see the correction.)
    Why
    Dated by the video's upload date (WSFA, 2024-11-27), which is the source date; the content gives no other date for the site.

  5688. · Volition Industries Spanish Fork · the summary of a timeline entry

    Before
    Spanish Fork City Council delayed the Title 15 vote a second time, for two more weeks, and Volition Industries said it may take the project to another community.
    After
    This entry recorded the September 1 delay under the status permitting, before the status rule adopted on 2026-09-05, under which a project waiting on an enabling text amendment is proposed. The entry of the same date and source records the same event as proposed. Spanish Fork City Council delayed the Title 15 vote a second time, for two more weeks, and Volition Industries said it may take the project to another community.
    Why
    The status was recorded as permitting before the status rule of 2026-09-05; the same event is recorded as proposed in the entry of the same date, and the summary now says so.

  5689. · Volition Industries Spanish Fork · the summary of a timeline entry

    Before
    The project is proposed under the status rule adopted 2026-09-05: it is waiting on the Title 15 text amendment before it can apply, and no application in its name is on file. On September 1 the City Council delayed the Title 15 vote a second time and Volition Industries said it may take the project to another community.
    After
    Spanish Fork City Council delayed the Title 15 vote a second time, for two more weeks, and Volition Industries said it may take the project to another community
    Why
    internal rule text removed from a public entry

Added automatically

Four low risk kinds of item reach the record without a person's approval: a Daily Record news item, which only links to the article and is added from the start; and, once the record's own reading of them has agreed with the editor's decisions 98 times in 100, a source added to a row already on file, a timeline line on a skeleton record from a primary source, the trade press or a local outlet, and a facility the EPA's registry lists, published as not yet verified. Every such item is listed here on the day it was added, with the page it appears on. An item the editor takes back stays on the list with the date it was taken back. The method is on the methodology page.

  1. · 141 items added automatically

    The 141 items

  2. · 87 items added automatically

    The 87 items

  3. · 50 items added automatically

    The 50 items

  4. · 205 items added automatically

    The 205 items

  5. · 175 items added automatically

    The 175 items

  6. · 168 items added automatically

    The 168 items

  7. · 141 items added automatically

    The 141 items

  8. · 40 items added automatically

    The 40 items

  9. · 70 items added automatically

    The 70 items

  10. · 311 items added automatically

    The 311 items

  11. · 240 items added automatically

    The 240 items

  12. · 169 items added automatically

    The 169 items

  13. · 3 items added automatically

  14. · 11 items added automatically

  15. · 7,154 items added automatically

    The 7,154 items

  16. · 16 items added automatically

Removed

A Daily Record news item found to be outside the record's scope, which is US data center development, is unpublished rather than deleted: its address on the day it was filed answers with a short note saying so, and the line below says when. Nothing else about it is kept on the site.

  1. · 23 items removed

  2. · 1 item removed

  3. · 38 items removed

  4. · 29 items removed

How corrections work

A correction is recorded against the record it affects, with the date and a note describing what changed. The earlier value stays visible in the record's history rather than being overwritten, and the correction is listed on this page.

On a status history entry the status, the date and the source never change and entries are never deleted. The sentence describing the entry is the record's own prose and may be corrected; when it is, the database writes the old text, the new text and the reason to this log automatically, so nothing is rewritten without a trace.

One label on a source may also be corrected: the kind of source it is. A story found through a Google News search once kept the search's kind, a lead, although the row cites the outlet's own page. The link never changes; the kind becomes the outlet's, and every such change is logged, grouped above by day and listed row by row in the corrections file. A date's label is corrected the same way: whether a date is the day of the act or the day of the report that carried it. Where only the label changes, the day stays, and the change is grouped above by day.

To report an error, write to corrections@datacenterrecord.org with the record and the source that shows the correct information. The full process is on the methodology page.

Researcher view · basis and source tier on every row · docket and Census GEOIDs · citation and export tools

Commercial and bulk data