Horizon Accord | Mason County KY | Data Center | Accountability | Machine Learning
Accountability Patterns
The Anonymous Applicant
A replicable methodology for identifying anonymous corporate actors in public processes — demonstrated on a live, unresolved case
The Methodology
Pattern analysis is not speculation dressed in confidence. It is a discipline with rules. This piece states those rules explicitly — not because they are novel, but because analysis that calls itself pattern-based frequently violates them without acknowledgment, producing conclusions that feel rigorous while being decorative.
The rules are four.
Rule 1 Every claim must be classified before it is used. A Documented Fact is sourced and verifiable by any third party from public records. A Structural Observation is a pattern identified from two or more documented facts. A Hypothesis is a reasoned conclusion from structural observations — it can be strong, but it cannot be stated as fact. Claims cannot be upgraded silently. If a claim sounds right but lacks sourcing, it stays a hypothesis or it gets cut.
Rule 2 The fingerprint must be built from confirmed prior cases before the live case is examined. You cannot construct a signature from the evidence you are trying to match. If an element appears in the live case but cannot be traced to a confirmed prior deployment of the same actor, it is not a fingerprint element. It is a data point whose significance is unknown.
Rule 3 Elimination is as important as identification. A candidate that fails on one high-weight factor is eliminated regardless of how many lower-weight factors it satisfies. The analysis must state what would disconfirm its conclusion, not only what confirms it. And disconfirmation evidence must be reported honestly, including when it dismantles a previously held position.
Rule 4 The confidence level of the output must be derived from the evidence, not from the analyst's conviction. Pattern analysis produces a probability-weighted hypothesis — not a name on a document. Overstating confidence is a methodological failure, not a rhetorical choice.
This piece applies that methodology to a live, unresolved case: a Fortune 20 company that has submitted a rezoning application for a 2,080-acre hyperscale data center campus in Mason County, Kentucky, and has not been publicly named at any stage of the process. The April 22, 2026 planning commission meeting is days from this writing. The case is open.
The Instruments of Concealment
This is a prerequisite step, not optional context. Documenting the concealment architecture before building the fingerprint matters because the instruments used to hide an actor's identity are themselves pattern elements. They shape what counts as a fingerprint element and why. A methodology that skips this step will miss the structural signature entirely.
The anonymity in this case is not accidental. It is constructed from instruments with documented histories.
Non-disclosure agreements originated in trade secret law — protecting genuinely proprietary technical information shared between parties in a competitive context. What the NDA became through decades of expansion is something different. It has been used to silence employees who witnessed workplace misconduct. To suppress knowledge of defective products. To conceal corporate actors from the communities affected by their decisions. And to bind elected officials to confidentiality provisions that prevent their constituents from knowing what is being decided on their behalf.
In every documented expansion of NDA use beyond its original technical purpose, the protection runs to institutional power. There is no documented case in which an NDA has been deployed to protect a tenant from a developer, a worker from a corporation, or a community from an anonymous buyer. The instrument does not work in that direction. Enforcement requires legal resources. Common people are on the receiving end — signing them as a condition of employment, settlement, or in this case, as elected officials bound by penalty of law.
Shell companies and intermediary buffer structures have a similarly narrow legitimate use case and a much wider documented history of misuse. The one protective application of LLC anonymity structures for common people is this: individuals fleeing domestic violence occasionally use them to obscure a home address from an abuser. This is not a redeeming feature of the instrument. It is evidence of a failure in every other protective system those individuals should have been able to rely on. And it is a use case available only to people with legal resources, financial literacy, and access to attorneys. The residents of Meadowland Village did not have those things. They received a letter from a property management company. It told them they had ninety days to leave. They had no mechanism to know who was buying their community. No leverage to negotiate. No instrument in the entire legal architecture of this process was designed with their interests in mind.
Structural Observation The instruments deployed in Mason County — the NDA binding local officials, the Industrial Development Authority as formal applicant buffer, the absent end user — are not neutral administrative choices. Their documented history of use at scale runs in one direction. That they appear together, in sequence, in a public zoning process affecting 28 households is not incidental. It is the pattern expressing itself. The methodology exists to read that expression.
Building the Fingerprint
Rule 2 applied A fingerprint is only valid if built from confirmed prior cases — not from the case under investigation. The elements below are drawn exclusively from publicly confirmed and named Amazon Web Services deployments. Each source is listed in the verification section.
Across confirmed AWS deployments in Mississippi, Indiana, North Carolina, and Wilmington, Ohio, the following structural elements recur with documented consistency. Each element is assessed for discriminating power — that is, its ability to distinguish AWS from other large hyperscale operators, not merely its presence in the record.
Element 1 — High discriminating weight The structural concealment sequence: NDA binding local officials through the entire public process, a local development authority or port authority as formal applicant buffer, and a utility or electric cooperative as the first point of contact between the company and local government — not the company itself. These three elements appear together in confirmed AWS deployments. They do not appear together in the one confirmed Meta deployment available for comparison: Meta's Howell Township project used an NDA and a shell LLC, but did not use a utility as intermediary and did not use an IDA as formal applicant. The combination of all three is consistent with the confirmed AWS pattern. It was not observed in the one confirmed Meta case in this dataset. This makes it a promising discriminator. The comparative sample is small, so it is not yet a proven one.
Element 2 — High discriminating weight Single-site power demand in the 2.0–2.5 gigawatt range. The confirmed AWS Indiana campus required 2.4 GW. The Mason County EKPC filing requests 2.2 GW — among the largest single-customer power requests in the history of the regional PJM grid. Google's confirmed Scioto County project is described as 500,000 square feet and does not approach this power scale. Meta's Howell Township project did not involve power demands at this order of magnitude. This element places the Mason County project in a very narrow class of confirmed precedents. The confirmed precedents at this power scale in this dataset are AWS. No other hyperscale operator has been publicly confirmed at comparable single-site demand in the cases reviewed here — which is not the same as saying no other operator could reach this scale.
Element 3 — Medium discriminating weight Campus design specifying not only data center buildings but administrative offices, full restaurant with culinary services, and campus amenities — a self-contained employer campus, not a technical facility. This design signature appears in confirmed AWS deployments in Indiana, Mississippi, and North Carolina. It does not appear in confirmed Meta or Google data center descriptions at comparable projects. It is not uniquely AWS, but it is consistently AWS across multiple confirmed cases.
Element 4 — Low-to-medium weight, noted but not decisive Air-based cooling specified rather than liquid cooling. This weakly favors AWS over Google, which has publicly emphasized liquid cooling for AI-density infrastructure. However, Google's own documentation acknowledges using multiple cooling methods depending on site conditions. This element is noted but does not function as a disqualifier for any candidate on its own.
Mason County Applied
Documented Fact The rezoning application filed with the Maysville-Mason County Joint Planning Commission names the Maysville-Mason County Industrial Authority, Inc. as formal applicant of record. The end user is not named anywhere in the application. Non-disclosure agreements were signed by the local judge-executive, IDA executive director Tyler McHugh, and EKPC leadership. At the March 25, 2026 public hearing, attorney Tanner Nichols of FBT Gibbons appeared for the developer. The company did not appear.
Documented Fact East Kentucky Power Cooperative — which operates the coal-fired Hugh L. Spurlock Generating Station in Mason County — filed plans with the Kentucky Public Service Commission to increase its load by 2.2 gigawatts for a single unnamed data center customer. EKPC was the first entity to approach local officials about the project. IDA director Tyler McHugh described the applicant as a "Fortune 20 tech company," "global top-10," with "hundreds of thousands of employees" operating "large-scale technology campuses worldwide."
Documented Fact The development plan describes a campus including data center buildings, administrative offices with meeting rooms, a full restaurant with culinary services, and logistical areas — a self-contained campus environment.
The fingerprint is now applied to the Mason County facts. But first, the officials' own descriptions narrow the field before the fingerprint is needed. McHugh described a "Fortune 20 tech company," "global top-10," with "hundreds of thousands of employees" operating "large-scale technology campuses worldwide." Structural Observation The Fortune 20 as of 2025 includes approximately five technology companies that operate large-scale public cloud or platform infrastructure at global scale with employee counts in the hundreds of thousands: Amazon, Apple, Microsoft, Google's parent Alphabet, and Meta. Apple employs roughly 160,000 people — below the "hundreds of thousands" threshold implied, and as noted below, does not operate external-facing cloud campuses. Meta employs approximately 70,000 — well below the threshold. That reduces the plausible field to three before any fingerprint analysis begins: Amazon, Microsoft, and Google. The fingerprint determines which of those three.
| Fingerprint Element | AWS Precedent | Mason County Record | Weight |
|---|---|---|---|
| Primary Discriminators — These two elements drive the identification | |||
| NDA + IDA buffer + utility intermediary — all three together | Mississippi: NDA bound officials, IDA as applicant buffer, utility as first contact. Indiana: same sequence. Wilmington OH: Port Authority as intermediary, AES Ohio as first utility contact. | Confirmed. NDA signed by judge-executive, IDA director, EKPC. IDA is applicant of record. EKPC was first point of contact with local officials. | High |
| Single-site power demand 2.0–2.5 GW range | Indiana (Project Rainier): 2.4 GW confirmed. Mississippi: multi-GW confirmed. No other hyperscale operator confirmed at this scale in the cases reviewed. | Confirmed. EKPC filed 2.2 GW load increase with KPSC for this single customer. | High |
| Supporting Context — Consistent with AWS; not uniquely discriminating | |||
| Campus with culinary services, offices, amenities | Indiana, Mississippi, North Carolina: administrative offices, culinary services, campus amenities. Consistent across three confirmed AWS deployments. | Confirmed in development plan: administrative offices, restaurant with culinary services, campus amenities, logistical areas. | Medium |
| Outside consultants represent project; company absent from hearings | Wilmington OH: Werkman confirmed this is AWS "standard procedure." Industry-wide practice — not uniquely AWS. | Confirmed. FBT Gibbons and Stantec appeared. Company sent no representative to any hearing. | Corroborative |
| Air-based cooling specified | Indiana, Wilmington OH: documented. Multiple operators use air cooling by site — not AWS-specific. | Confirmed in development plan. | Low–Med |
| Rural agricultural land, hyperscale acreage | Indiana: 2,400 acres. Wilmington OH: 471 acres. Common across multiple hyperscale operators — not AWS-specific. | Confirmed. 2,080 acres, 28 parcels, A-2 Agricultural to I-3 Rural Industrial. | Low |
Structural Observation All six fingerprint elements are present in the Mason County record. Two carry high discriminating weight. The three-part concealment structure is consistent with confirmed AWS deployments and was not observed in the one confirmed Meta case reviewed. The 2.2 GW power demand matches confirmed AWS precedents and is not matched by any confirmed deployment of the other candidates in this dataset. No element diverges from the fingerprint. The independent discriminating elements — the three-part concealment structure and the 2.2 GW power demand — carry the analytical weight, with the honest caveat that the comparative sample supporting both is limited.
Elimination Analysis
Candidates are evaluated against the highest-weight fingerprint elements. Elimination requires a documented disqualifying factor, not merely lower probability. The status of each candidate is stated precisely.
| Candidate | Status | Basis |
|---|---|---|
| Eliminated — Cannot satisfy the case | ||
| Apple | Eliminated — business model | Apple meets the Fortune 20 threshold and employs approximately 160,000 people globally — consistent with the scale described by officials. But Apple does not operate customer-facing cloud infrastructure. The economic development argument made to Mason County officials describes a public cloud provider. Apple's data center footprint is internal infrastructure only. It has no documented history of the IDA-intermediary concealment structure. |
| Substantially Weakened — Multiple documented factors work against fit | ||
| Meta | Substantially weakened | Three converging factors. First: Meta employs approximately 70,000 people globally. McHugh described "hundreds of thousands of employees." That description may not be precise, so it is not a hard disqualifier on its own. Second: Meta requires 100% renewable energy at all data centers. EKPC operates coal-fired generation. That is a meaningful structural conflict. Third: the confirmed Howell Township deployment (Project Splitrock) used a different structural template — no IDA buffer, no utility intermediary. One case is a thin sample, but the divergence is documented. Across all three factors, Meta is a poor fit. |
| Weakened — Specific documented factors reduce fit; not eliminated | ||
| Microsoft | Materially weakened | In March 2026, Microsoft publicly announced the termination of NDAs with local governments worldwide. Microsoft's corporate VP and general counsel Rima Alaily stated directly: "We will continue to use NDAs in connection with private transactions when acquiring land, and we will continue to rigorously protect our trade secrets and datacenter design information. But we will not use NDAs as a default mechanism in our engagement with local governments." That land acquisition carve-out is a named, sourced, documented statement — not an inference. It means Microsoft's policy permits NDAs in land transactions but explicitly disavows them as a tool for binding local governments through a public zoning process. The Mason County NDA structure bound the judge-executive, the IDA director, and EKPC through the entire planning commission approval process — not merely a land transaction. That specific behavior is what Alaily disavowed. It is what makes Microsoft materially inconsistent with the Mason County pattern. Microsoft is not eliminated because the carve-out creates a narrow technical window. It is significantly weakened because the behavior in question falls squarely outside what Microsoft publicly committed to continuing. |
| Weakened on geography and scale | Google was confirmed in January 2026 as the company behind Project Dazzler — a $1 billion, 792-acre campus on the Ohio River in Scioto County, Ohio, approximately 50 miles from Mason County. Google has already established its Ohio River corridor position with an active approved project. Two simultaneous Ohio River corridor campuses from the same company is not impossible, but it is an argument Google must clear. Additionally, Google's Scioto County campus is 500,000 square feet — far below the 2.2 GW power scale of Mason County. What would eliminate Google entirely: a public statement from Google that they are not pursuing additional Kentucky or Ohio River corridor sites, or a confirmed identity for Mason County naming a different company. Neither exists in the public record. Google is weakened on geography and power scale; not formally eliminated. | |
| Active Candidate — Satisfies all fingerprint elements; not weakened on any factor | ||
| Amazon Web Services | Active | Satisfies both primary discriminators. The three-part concealment structure is documented across confirmed AWS deployments in Mississippi, Indiana, and Wilmington, Ohio, and is not observed in the confirmed deployments reviewed. The 2.2 GW power demand matches confirmed AWS precedents in Indiana (2.4 GW) and Mississippi, and is not matched by any confirmed deployment of the other candidates. Not weakened on any factor. |
Confidence Assessment
The methodology requires an explicit confidence statement derived from the evidence.
Hypothesis The company behind the Mason County data center project is Amazon Web Services. This is classified as Hypothesis because no document in the public record names the company. Hypothesis classification does not indicate weakness — it indicates epistemic precision. The confidence level on this hypothesis is high, earned from the following:
Two high-weight fingerprint elements drawn from confirmed AWS deployments both match Mason County. One — the three-part concealment structure — was not observed in the one confirmed Meta case reviewed, which is useful but limited to a single comparison. Two candidates are substantially weakened. Two are weakened on specific factors. AWS satisfies all elements and is not weakened on any factor. The confidence level is high but the honest constraint is this: the discriminating power of the fingerprint rests on a small comparative dataset. The conclusion is the most defensible available from the public record — not the only possible one.
What constrains the confidence level from certainty: the fingerprint contains fewer high-weight independent discriminators than earlier versions of this analysis claimed. The removal of the Stantec element was correct and necessary. What remains is a leaner, honest fingerprint that supports a high-confidence hypothesis — not a certainty.
Documented Fact The next disclosure pressure points are the April 22, 2026 planning commission vote; the post-zoning KEDFA incentive application, which per Kentucky's Qualified Data Center Program fact sheet discloses the company name at a public board meeting; and any Army Corps Section 404 pre-construction notification, which names the applicant owner of record.
Structural Observation What would confirm: the KEDFA board meeting names Amazon Web Services, or a deed transfer to an Amazon-affiliated LLC appears in Mason County property records post-approval. What would disconfirm: either of those events names a different company. The methodology holds either way — the output is the most defensible conclusion available from the public record at this moment, with its constraints stated explicitly.
Why This Methodology Exists
Pattern analysis is a discipline, not an abstraction. It exists because without it, people do not know what is happening to their homes.
Twenty-eight households at Meadowland Village Mobile Home Park on Germantown Road in Maysville received notice in late March 2026 that their park was under contract for sale. They were given approximately 90 days to vacate. The notice came from DPD Property Management on behalf of the Porter family, who own the land.
A significant number of residents are elderly or disabled. Roger Purcell is battling kidney disease and has a ramp at his home that will need to be moved or rebuilt. Pastor Greg Jones bought his home in the park seven years ago. Resident Rico Roberts, when told the developer was offering up to $20,000 per household for approved moving expenses, said: "$20,000 ain't nothing."
The developer subsequently raised that figure to $50,000 — contingent on the property being rezoned. The people being displaced do not receive their relocation assistance unless the process displacing them is approved.
Roger Purcell noted there are no mobile home parks in the area with enough capacity to absorb the displaced residents. Local ordinances requiring five-acre lots for mobile home placement mean that for most of them, there is functionally nowhere nearby to go.
The farmers selling land are making rational decisions inside a system that has been defunding rural agriculture for decades — commodity prices, input costs, consolidation. A check that arrives at ten times market value is not a choice in any meaningful sense. The company offering that check is part of the same economic infrastructure that made farming unviable. The land does not simply change use. It gets absorbed into the system that made the previous use unsustainable.
The residents of Meadowland Village had no role in any of it. They are renters in a park on land they do not own, managed by a company they have no leverage over, being displaced by a buyer whose identity they are legally prevented from knowing. Three layers of removal from any accountability. No instrument in the legal architecture of this process was designed with their interests in mind.
Hank Graddy, representing We Are Mason County, filed suit against Mason County and argued at the March 25, 2026 public hearing that residents cannot cross-examine an anonymous entity. Developer attorney Tanner Nichols refused to name the company. The planning commission proceeded.
Structural Observation A zoning process exists to weigh the interests of a community against the interests of a developer. When the developer's identity is legally concealed, only one side of that weighing can be examined. The methodology in this piece exists to restore, partially and imperfectly, the public's ability to examine the other side. It does not replace the legal protections that should have existed. It documents their absence.
The framework described in the methodology section is replicable. The next anonymous applicant in the next county will use the same instruments. The fingerprint will be different. The rules will be the same.
Sources for Verification
All sources are publicly accessible. Primary documents are linked directly where available. Independent verification is encouraged.
Blue Water Healthy Living. "Planners shoot down data center in Howell Township." September 24, 2025. Jack Ammerman of Stantec appeared and stated anonymity is "industry standard."
Daily Caller. "Trailer Park Residents Told They Have 3 Months To Make Way For Massive Data Center." April 6, 2026. $50,000 figure contingent on rezoning confirmed.
WEKU. "Mason County official says data center could bring 400 jobs averaging $80,000." August 21, 2025.
Kentucky Lantern. "Kentucky could be on the eve of a data center boom." August 21, 2025.
Methodology note: This analysis is pattern observation based entirely on publicly available, sourced information. No insider knowledge, confidential sources, or non-public documents were used. All epistemic classifications — Documented Fact, Structural Observation, Hypothesis — are applied per Horizon Accord editorial standards. The identification of Amazon Web Services as the most likely candidate is classified as Hypothesis: a reasoned, high-confidence conclusion from available evidence, not a confirmed fact. A previous version of this analysis treated the Stantec/Ammerman presence as a high-weight fingerprint element. That element was removed after research confirmed Stantec's Ammerman represented Meta Platforms in a concurrent Michigan data center process using the same anonymity structure. The correction is documented in the methodology section. No claim in this piece is stated beyond what the sourced record supports.
Intended use: This document is offered as a public record brief and methodology demonstration. It may be reproduced and shared freely with attribution to Horizon Accord (horizonaccord.com). The framework described in the methodology section may be applied independently to other cases.
Process Update
On April 22, 2026, the Mason County Joint Planning Commission unanimously approved the proposed data center development plan, with a single condition: that an existing berm along Germantown Road may be extended if necessary. The commission also approved the rezoning findings of fact and entered all related documents into the record. Residents who attended described the meeting as brief — and said they had hoped for more discussion before the vote.
On May 12, 2026, the Mason County Fiscal Court held a first reading of the ordinance to rezone the 28 properties — approximately 2,080 acres north of Germantown Road — from A-2 Agricultural to I-3 Rural Industrial. A second reading is tentatively scheduled for May 22, 2026, at a special meeting where the court will consider argument-style presentations before a final vote. That second reading is the last procedural gate before the rezoning is either approved or denied.
The process from the April 1 forwarding vote to the May 22 second reading traces the sequence the original analysis identified as the final disclosure pressure zone: once the Fiscal Court acts, the KEDFA incentive application — which names the company at a public board meeting — becomes the next stage. No identity disclosure has appeared in the public record at any point in this process.
The lawsuit filed by We Are Mason County, represented by attorney Hank Graddy, remains active. The suit argues that the data center ordinance conflicts with the county's comprehensive plan. At the April 1 planning commission meeting, Commissioner Kirby Rosser raised the lawsuit on the record and questioned whether the board should continue voting while litigation advanced. Commission attorney Michael Clarke acknowledged the suit and declined to stop the vote.
| Date | Event |
|---|---|
| Apr 1, 2026 | Planning Commission votes 4-1-1 to forward rezoning to Fiscal Court with recommendation for approval. Lawsuit acknowledged in session. |
| Apr 15–16, 2026 | Kentucky legislative session ends. Data center ratepayer protection provisions stripped from SB 197 on final day. |
| Apr 22, 2026 | Planning Commission unanimously approves development plan with berm condition. Rezoning findings of fact entered into record. |
| May 12, 2026 | Fiscal Court holds first reading of rezoning ordinance. |
| May 22, 2026 (tentative) | Fiscal Court second reading. Argument-style presentations. Final vote on rezoning. |
The Legislative Gate That Did Not Hold
On the final day of the 2026 Kentucky legislative session, the data center provisions sponsored by Republican Representative Josh Bray of Mount Vernon were stripped from Senate Bill 197 in a House budget committee meeting. The bill passed both chambers that evening without the data center language and was sent to the governor. Bray confirmed the removal to reporters and attributed it to "the Senate in general," adding that Louisville Gas and Electric and Kentucky Utilities had opposed the bill.
Bray's provisions had been designed to require data centers to pay for utility infrastructure improvements serving only their facilities, protecting existing ratepayers from subsidizing those costs. Senate President Robert Stivers argued the Kentucky Public Service Commission had already done adequate work approving data center tariffs for EKPC and LG&E/KU. LG&E and KU issued a statement praising the legislature's focus on energy and economic growth.
The legislative protection failed at exactly the moment the Mason County process was entering its final local gate. The sequence is not coincidental in any structural sense — it reflects a pattern in which industry opposition consolidates against regulation at the state level while individual counties are left to negotiate whatever local protections they can produce before the process is complete. Mason County's planning commission had already approved the project by the time the bill died.
Democratic Representative Adam Moore of Lexington, who had filed a separate bill requiring data center contract terms protective of ratepayers, called the failure "incredibly frustrating" and noted it was not a partisan issue — he had received calls from Mercer and Mason County residents on both sides of the aisle. No data center ratepayer protection legislation passed the 2026 session. The next regular session is 2027.
Hypothesis Status
The original analysis closed with an explicit confidence assessment. That assessment has not changed. The public record has not produced a disclosure confirming or disconfirming the identification of Amazon Web Services as the company behind the Mason County project. The hypothesis stands as written.
The company behind the Mason County data center project is Amazon Web Services. This remains classified as Hypothesis: a reasoned, high-confidence conclusion from the available public record. No document in the public record has named the company. No element has emerged since original publication that requires revision to the fingerprint analysis or the elimination table.
Attorney Tanner Nichols, representing the developer, stated at the March 25 public hearing that it was not likely residents would learn the identity of the company until the zone change had been approved and land contracts had been signed. WEKU reported that the company's identity would remain undisclosed until the process was complete. Neither condition has been met as of this addendum's writing.
The concealment has held through every stage of the public process — public hearings, a lawsuit, two rounds of fiscal court proceedings, and sustained local media coverage. This is consistent with the original analysis's characterization of the concealment architecture as deliberate and durable, not incidental to the process. The instruments hold because no procedural mechanism compels disclosure before the zone change is recorded.
What Comes Next
The original analysis identified three post-approval disclosure pressure points. Their status as of this writing:
May 22, 2026 — Fiscal Court second reading. The final local vote on the rezoning ordinance. If approved, the land transaction and incentive application phases follow. This is the gate currently open.
KEDFA incentive application. Kentucky's Qualified Data Center Program fact sheet specifies that the company name is disclosed at a public KEDFA board meeting. This stage is post-approval and has not yet been reached.
Deed transfer. Post-zoning deed transfers to an Amazon-affiliated LLC in Mason County property records would confirm the identification. No such transfer is in the public record as of this writing.
The methodology described in the original analysis remains replicable. The Mason County case is not closed. This addendum will be updated if the record changes.
Sources — Addendum
- WXIX/Fox19. "Board approves Maysville data center plans, but residents demand regulations." April 22, 2026. fox19.com
- WCPO. "Maysville data center proposal moves toward final approval despite lawsuit." April 2, 2026. wcpo.com
- Louisville Public Media / WFPL. "Kentucky data center regulations stripped from bill as legislative session closes." April 15–16, 2026. lpm.org
- Kentucky Lantern. "Housing, data center legislation dies on final day of 2026 session." April 16, 2026. kentuckylantern.com
- City of Maysville — Data Center Zoning Public Information Page. Meeting timeline and Fiscal Court schedule. cityofmaysvilleky.gov
- Kentucky Lantern. "Local data center battles in Kentucky are contentious. They're also inspiring runs for office." May 11, 2026. kentuckylantern.com
- WEKU. "Mason County officials approve ordinance paving the way for potential large-scale data center." March 1, 2026. weku.org
Fiscal Court Approves Rezoning
On May 22, 2026, the Mason County Fiscal Court held its second reading and voted to approve the ordinance rezoning the 28 properties — approximately 2,080 acres north of Germantown Road — from A-2 Agricultural to I-3 Rural Industrial. The vote completed the final local procedural gate in the rezoning process.
The company's identity was not disclosed at any point in the public process — not at the March public hearings, not at the April planning commission meetings, not at the May fiscal court readings, and not at the final vote. The concealment architecture held through every stage.
The lawsuit filed by We Are Mason County, represented by attorney Hank Graddy, remains active. The case is scheduled to be heard at the end of June 2026. The lawsuit argues that the data center ordinance conflicts with the county's comprehensive plan.
Hypothesis Status — Unchanged
The company behind the Mason County data center project is Amazon Web Services. This classification is unchanged. The Fiscal Court vote produced no disclosure and no disconfirming evidence. The fingerprint analysis and elimination table from the original piece remain as published. The hypothesis is high-confidence; it is not confirmed fact. The public record has not named the company.
Remaining Disclosure Pressure Points
With rezoning approved, the process moves to the land transaction and state incentive application phases. Kentucky's Qualified Data Center Program requires the company name to be disclosed at a public KEDFA board meeting. That stage has not yet been reached as of this writing.
Post-zoning deed transfers to an Amazon-affiliated LLC in Mason County property records would also constitute confirmation. No such transfer appears in the public record as of this writing.
The concealment held through a full public process — two rounds of public hearings, a planning commission vote, a planning commission development plan approval, a fiscal court first reading, a fiscal court second reading, and sustained regional media coverage spanning nine months. This is the documented behavior of a deliberate concealment architecture, not an administrative oversight. The instruments perform as designed until a procedural gate compels disclosure. KEDFA is the next such gate.
Sources — May 22 Update
- WKRC / Local 12. "New data center now approved for Northern Kentucky." May 22, 2026. local12.com
- City of Maysville — Data Center Zoning Public Information Page. Meeting timeline and Fiscal Court schedule. cityofmaysvilleky.gov
The Gregorski Fingerprint
New reporting points to Meta behind Mason County's data center. Here's what changed in our analysis — and what didn't.
What Changed
This piece originally named Amazon Web Services as the leading hypothesis behind the anonymous applicant, Crisham LLC. Reporting from the Wall Street Journal has since surfaced evidence pointing elsewhere. Public records reviewed by WSJ reporters name Pamela Gregorski, a senior manager at Corporation Service Company, as the contact listed on Crisham LLC's public filings. Gregorski's name carries weight: she has now been tied, directly or through matching filing patterns, to four confirmed Meta data-center fronts — and a fifth strongly tied to Meta — across four states.
Crediting the Record
Credit belongs with the Journal. Horizon Accord is unpaid, independent research; when this piece was originally written, several of the underlying records — the Project Crisham filings among them — sat behind paywalls or required costs we didn't have. WSJ's reporters had that access, and their work surfaced the Gregorski connection before we found it ourselves.
Two corrections belong on our side of the ledger. The original piece had already surfaced a Meta-linked comparison case through Stantec and Jack Ammerman, and we did not weight that overlap heavily enough. We also let differences drawn from a small sample of known Meta projects carry more discriminating power than a small sample can bear.
The Gregorski Signal
The pattern behind that judgment comes from investigative outlet Hunterbrook, which in April 2026 reviewed all 78 companies listing Gregorski as an officer in OpenCorporates. Six were tied to data-center projects. Four were confirmed Meta front companies at the time: Orla LLC in Indiana, Laidley LLC and Pelican Leap LLC in Louisiana, and Wurldwide LLC in Texas. A fifth, J5 LLC — doing business as Shaytura LLC, developer of Ohio's "Project Klondike" — has since been traced independently to Meta's Menlo Park headquarters through a Nevada filing, and to a former Facebook deputy general counsel listed as its manager.
Laidley is the clearest primary-record case. Louisiana Public Service Commission filings identify it outright as "a subsidiary of Meta Platforms, Inc." — and litigation before the commission is captioned Laidley, LLC/Meta Platforms, LLC. Local reporting names Gregorski as Laidley's LLC president and CSC's vice president of global financial services — the same role, the same firm, appearing again across a confirmed case.
Sixth on Hunterbrook's list is Hatchbo LLC, a data-center project in Clarksville, Arkansas. Hunterbrook found no confirmation that Meta is behind it, and neither did we — Hatchbo's actual parent remains undisclosed as of this writing.
What Corporation Service Company Doesn't Prove
CSC is not a Meta-specific vendor. It's one of the country's largest registered-agent firms, founded in 1899, serving well over a hundred thousand businesses. Amazon entities file through CSC too. Amazon Web Services, Inc. is registered — per its Legal Entity Identifier filing — at 251 Little Falls Drive, Wilmington, Delaware: the identical CSC address listed for Crisham LLC in the Mason County application.
That overlap cuts one direction only. It means a CSC-registered address was never a Meta fingerprint by itself — Crisham sharing an address with AWS's own registered filings proves nothing about who's behind Crisham, in either direction. It does not, on its own, provide evidence that AWS is involved in this project. The address is noise. Gregorski's name — a specific individual, recurring as officer or contact across a specific, non-random cluster of confirmed Meta shells — is signal. Those are different claims, and the address doesn't do work the name is already doing.
Reweighing the Original Discriminators
Three of the discriminators that favored AWS in the original piece read differently now.
The secrecy argument no longer distinguishes AWS from Meta. Meta has run its own confirmed data-center projects — Piqua, Ohio's Project Klondike among them — behind city NDAs and Delaware shell filings that concealed the developer's identity from local officials themselves. Concealment through shell LLCs is documented Meta practice, not evidence pointing away from it.
Scale no longer distinguishes them either. The 2.2 gigawatt figure that once looked AWS-specific sits comfortably inside Meta's current build-out: a 1 GW campus breaking ground in Lebanon, Indiana; a $27 billion joint venture with Blue Owl Capital for the Hyperion campus in Louisiana; a $14 billion AI campus announced for El Paso. Gigawatt-scale sites are now Meta's stated standard, not an outlier.
The renewable-energy argument was overstated. Meta's public commitment is to match its electricity consumption with clean-energy procurement — power purchase agreements, credits — not to require the physical grid supplying a given campus to be locally renewable. A gas-heavy local grid is consistent with a Meta project under that model. It was never the discriminator the original piece treated it as.
A Separate Question: Meta and AWS
One thread is worth keeping separate from all of this. Meta and AWS have a real, current infrastructure relationship. In April 2026, the companies expanded a partnership to deploy tens of millions of AWS Graviton processor cores as part of Meta's AI infrastructure — described by an Amazon vice president as combining "purpose-built silicon with the full AWS AI stack." Meta has named AWS a long-term strategic cloud provider since 2021.
That relationship makes a Meta/AWS division of labor on some future project plausible in principle — Meta as sponsor, AWS supplying some portion of compute or infrastructure. It does not make it true of Crisham. Nothing in the public record ties AWS to the Mason County site specifically, and this thread should not be read as strengthening or weakening the Gregorski evidence. They are separate questions until a document says otherwise.
Where This Leaves Crisham
Meta is now the strongest-supported candidate behind Crisham LLC. The Gregorski signal is company-specific in a way the original AWS indicators — secrecy, scale, renewable-energy posture — turned out not to be; those describe hyperscale data-center development generally, not AWS uniquely. That's the actual shape of what changed: new evidence arrived, and some of the discriminators we built the AWS hypothesis on carried less weight than we gave them.
It is not proof. Crisham's own filings do not name Gregorski in any primary document Horizon Accord has independently verified — that link currently rests on WSJ's public-records reporting, not on a document we've seen firsthand. Hatchbo's unresolved status is a real gap in the pattern, not a footnote to wave past. We're publishing this update because the balance of evidence has moved, not because the question is settled.
Sources for This Update
- Wall Street Journal, syndicated copy — Project Crisham public-records identification of Pamela Gregorski. itiger.com/news/2659179719
- Hunterbrook Media, "Meta Secretly Behind $1B Ohio Data Center" — the Gregorski/78-company pattern. hntrbrk.com/meta-data-centers
- Shreveport-Bossier Advocate — Gregorski named as Laidley LLC president and CSC VP. shreveportbossieradvocate.com
- Earthjustice — Louisiana PSC filings naming Laidley a Meta Platforms subsidiary. earthjustice.org
- Stop Ohio Data Centers — J5 LLC / Shaytura traced to Meta's Menlo Park headquarters. stopohiodatacenters.org/miami-county
- Bloomberg LEI / GLEIF — Amazon Web Services, Inc. registered agent filing, 251 Little Falls Drive, Wilmington, DE. lei.bloomberg.com
- Meta Newsroom — April 2026 AWS Graviton infrastructure partnership. about.fb.com
- Data Center Dynamics — Meta names AWS a long-term strategic cloud provider (2021). datacenterdynamics.com
