Independent public-records research · Evidence and updates
Site Layer 4 Project RecordIndependent public-records researchPart ofState 44

Safeguards → Governance

Governance, transparency & enforcement

General authority exists; stronger project-specific commitments proposed

The county already has general enforcement authority and successor rules, and the applicant and landowner are identified. What remains unverified in the reviewed records is project-specific: who ultimately owns and operates the campus, a public reporting and inspection regime, and a recorded agreement that binds future owners.

Good rules are only as good as the ability to see compliance and enforce it against whoever owns the site next. The distinction here is between general authority that already exists and the project-specific commitments proposed for this campus; existing general obligations remain distinct.

Who would own and operate the campus

Applicant & landowner identified · ultimate owner/operator unresolved

The filing identifies the applicant (Site Layer 4, LLC), a contact (Ian Marcus), and the landowner (Lazy V Six) — so it isn't true that ownership is undisclosed. What remains open is the ultimate beneficial owner, the final data-center end-user, and the operating entities. Expanded disclosure, and identifying who is responsible for each component, is a proposed requirement, not an established one.

COUNTY-027

Enforcement and public reporting

General enforcement exists · campus program & public reporting proposed

Existing rules already assign enforcement (the Planning Officer monitors; the County Attorney prosecutes as directed) and provide daily fines and court remedies — so "there is no enforcement authority" would be wrong. What's not established is a project-specific inspection schedule, a named inspector, authority for the proposed administrative stop-work or curtailment remedies, and public reporting of the campus's water, gas, and electricity use. (Covered solar reports annually to the Planning Office — that is not the same as public campus-use reporting.)

COUNTY-021 · COUNTY-022

A recorded agreement that binds successors

General successor rule exists · recorded agreement not verified

Existing industrial permit conditions already reach successors, but that is not the same as an executed, recorded development agreement that runs with the land, survives a sale, and secures every obligation. No such recorded instrument for this project is established in the reviewed records; stronger recorded obligations are proposed.

COUNTY-024

Expansion, phasing, and a whole-campus plan

Expansion review recommended · phase gates & PUD proposed/discussed

P&Z recommended a new or amended permit when server capacity, power draw, or cooling exceeds the original approval — a real safeguard worth keeping (note the proposed text doesn't use an undefined "material" threshold). Phased approvals with defined off-ramps are a proposed request, not adopted; the applicant's multi-year buildout narrative isn't a binding staged approval. A whole-campus master plan/PUD was discussed for future study — not included in the recommended amendments.

COUNTY-008 · COUNTY-025 · COUNTY-026

The conflict-of-interest question

Recorded statement verified · letter outstanding · no misconduct established

The August 26 signed minutes record Chair Shepard stating that legal counsel advised he had no conflict and that he would participate. A County Attorney letter was referenced on September 16, and its contents are not verified here. The posted P&Z bylaws require a member with a conflict to withdraw from discussion and voting; whether that applied is unresolved. This is a transparency item — obtain the letter and the record — not a finding of wrongdoing, and the audience's family-relationship assertion is not established as fact.

COUNTY-028 · COUNTY-029

What you can ask for in county rule comments

The hearing concerns proposed countywide land-use rules, not a Site Layer 4 project permit. Distinguish a requested countywide standard from a future project-specific condition.

These are proposed safeguards, not adopted requirements. The responsible body, legal authority and project applicability must be verified before adoption.

  • Disclosure of the ultimate owner, end-user, and operator as a condition of a complete application.
  • A named inspector, public use-reporting, and a recorded agreement that binds future owners and survives a sale.
  • Keep the expansion-review rule so a bigger build needs a fresh review, not an automatic pass.

Countywide rules hearing — how and when to comment →

Go deeper: the full governance entries (COUNTY-021–029). Where the record is silent — as with the conflict letter — this page says so rather than filling the gap.

Read all 59 detailed evidence checks and source findings →

Who would own and operate the campus?

The reviewed filings identify Site Layer 4, LLC as the applicant, Ian Marcus as its county application contact, Lazy V Six, Inc. as the participating landowner in the application narrative, and SWCA Environmental Consultants as the consultant. February air-permitting correspondence says SWCA was acting on behalf of Granite Renewables; a separate February introduction names Ian and Blake Marcus as Site Layer 4 representatives. These statements establish the roles described in those records, not the complete ownership or control chain. (C13, pp. 2, 8, 19; W1, p. 1; W2, p. 2; COUNTY-027)

Open question: Who are the ultimate beneficial owners, final data-center end-user, and operators of the data center, generation, storage, and water systems? The reviewed records do not establish those identities or which entities would guarantee each obligation. A contact, representative, landowner, and operator are not interchangeable roles.

Proposed safeguard: Identify the entities responsible for each component and require enforceable obligations, authorized successor terms, and continuing security before the relevant approval or operation. See Request P7 and scorecard rows G01–G04.