Archived page snapshot: October 3, 2026. Check current notices and source dates before acting on deadlines.
Detailed evidence checks: all 59 entries
The complete matrix preserves each evidence status, responsible body, milestone, payer, next step and source. Start with the six-topic summary.
General rules · project evidence · proposed safeguards
Safeguard checks and evidence
This scorecard separates general rules from project commitments and proposals. A filed document is not an adopted rule; an adopted rule is not proof of a signed agreement; a signed agreement is not proof that security has been posted and remains available. “Not established” means the reviewed records do not answer the question, not that the protection does not exist.
Evidence labels: General rule; recommendation/proposal; reported action; applicant statement; discussed; project evidence unresolved; proposed request. “Executed” and “security verified” should be used only when the actual instruments and evidence support them.
Requested policy standard: The parties creating additional demand should fund its attributable costs, with commitments secured before exposure arises and enforceable through the appropriate legal vehicle. This is a proposal, not a finding that every requested obligation is already law.
Reading the table: “D” identifies a documented payer rule or commitment; “P” identifies the requested payer. “Unresolved” never assigns a default bill to residents. Proposed timing is explicitly marked. BOCC means the Board of County Commissioners; SUP means Special Use Permit. Each row was last checked 2026-09-20, within the source/search boundaries recorded in the dated source reviews. Source dates may be earlier.
Read the status in context
Use these questions alongside each entry’s precise evidence label. A general rule, recommendation or discussion is not proof of a secured project commitment; mixed entries keep their qualifications.
Secured
Is the applicable obligation executed, and is any required security posted and available? The actual instruments and evidence must support that conclusion.
Still decidable
Is this a proposal or recommendation for a remaining decision? Check the relevant process and its authority.
Not established
Do reviewed records leave execution, applicability or authority unanswered? Unverified does not mean nonexistent.
Water11 entries
W01 — Water needs and nearby-well mapping
Evidence status
General application rule. Industrial applications require quantified proposed needs and nearby habitation/well mapping; this is not a binding use cap.
Responsibility & evidence
Details & sources for W01
Vehicle / responsible body
Existing industrial application rules / county
Deadline or prerequisite milestone
Applicable application review
Documented versus proposed payer
D: applicant supplies application information; no mitigation funding proved. P: developer funds additional review where authorized.
Next step
Obtain complete project report and well map; distinguish map radius from setback.
Sources; checked
C7 §7.05.050(A)(e); COUNTY-032; 2026-09-20
W02 — Annual withdrawal limits by phase/full buildout
Evidence status
Applicant estimates; binding limit unresolved. Less than 15 and no more than 800 acre-feet annually have unreconciled scopes.
Responsibility & evidence
Details & sources for W02
Vehicle / responsible body
Water permits/supply instruments; authorized SUP or agreement / State Engineer, supplier, county within authority
Deadline or prerequisite milestone
P: settle before relevant SUP decision and water use; no project date verified
Documented versus proposed payer
D: no executed cap/funding instrument established. P: developer funds water budget and compliance.
Next step
Reconcile all components, counties, phases, source rights, and meter boundaries; adopt lawful maximums.
Sources; checked
W03 — Consumptive-use cap
Evidence status
Proposed request. Withdrawal, delivered supply, and consumption are different quantities.
Responsibility & evidence
Details & sources for W03
Vehicle / responsible body
Authorized water/land-use instrument / State Engineer and relevant approving body
Deadline or prerequisite milestone
P: before water-dependent approval/operation
Documented versus proposed payer
D: no project obligation verified. P: developer/operator.
Next step
Define a complete water balance, losses/returns, accounting period, and enforceable limit.
Sources; checked
W04 — Cooling design
Evidence status
Applicant statement. Closed-loop cooling is described, not proved as a binding final design or zero-water operation.
Responsibility & evidence
Details & sources for W04
Vehicle / responsible body
Design documents and applicable permits / applicant and permitting bodies
Deadline or prerequisite milestone
Design review, before construction
Documented versus proposed payer
D: no final compliance cost agreement verified. P: developer/operator.
Next step
Verify initial fill, makeup, heat rejection, discharge, and permit incorporation.
Sources; checked
W05 — Dry/air cooling, reuse, and cooling-source restrictions
Evidence status
Proposed request. Require feasible low-water alternatives and consider restrictions on fresh groundwater/potable cooling supply.
Responsibility & evidence
Details & sources for W05
Vehicle / responsible body
Authorized permits and supply contracts / relevant agencies, supplier, county within authority
Deadline or prerequisite milestone
P: feasibility review before design approval
Documented versus proposed payer
D: no such project requirement verified. P: developer funds evaluation and selected design.
Next step
Compare feasible alternatives; verify authority and supply rights before imposing restrictions.
Sources; checked
W06 — Independent hydrologic baseline
Evidence status
Discussed; detailed program proposed. Project mandate/funding unresolved.
Responsibility & evidence
Details & sources for W06
Vehicle / responsible body
Authorized study agreement/condition / county, independent hydrologist, State Engineer as applicable
Deadline or prerequisite milestone
P: before pumping or construction affects baseline
Documented versus proposed payer
D: no escrow verified. P: developer, with independent selection and oversight.
Next step
Specify seasonal baseline, reference wells, access, methods, and funding.
Sources; checked
COUNTY-032; WATER-010; C5 ~1:51:47–1:55; 2026-09-20
W07 — Public well/aquifer monitoring
Evidence status
Discussed; detailed program proposed. No project network or public reporting duty verified.
Responsibility & evidence
Details & sources for W07
Vehicle / responsible body
Monitoring/access agreements and applicable permits / regulator and independent reviewer
Deadline or prerequisite milestone
P: establish with baseline; continue through operation/recovery
Documented versus proposed payer
D: no secured funding verified. P: developer/operator.
Next step
Define locations, frequency, calibration, publication, access consent, and privacy treatment.
Sources; checked
WATER-011,014; COUNTY-022,032; 2026-09-20
W08 — Bonded well mitigation
Evidence status
Proposed request; execution/security unresolved. Drawdown alone is not a determination of legal injury.
Responsibility & evidence
Details & sources for W08
Vehicle / responsible body
Authorized mitigation agreement / developer, affected beneficiaries, regulator within authority
Deadline or prerequisite milestone
P: security before pumping; interim supply on defined trigger
Documented versus proposed payer
D: no project guarantee verified. P: developer/operator.
Next step
Define baseline/causation, prompt interim supply, lowering/deepening/replacement remedies, dispute review, and draw rights.
Sources; checked
W09 — Drought curtailment and household/agricultural protection
Evidence status
Proposed request. A county contract cannot reorder nonparty state water rights.
Responsibility & evidence
Details & sources for W09
Vehicle / responsible body
Lawful project/supplier commitments and state administration / operator, supplier, State Engineer
Deadline or prerequisite milestone
P: drought plan before operation; defined indicators trigger reductions
Documented versus proposed payer
D: no project commitment verified. P: developer/operator.
Next step
Seek project-first reductions protecting essential household/agricultural supply within lawful rights and priority rules.
Sources; checked
W10 — Metering and full-cost water infrastructure/service
Evidence status
Proposed request; project pricing and meters unresolved.
Responsibility & evidence
Details & sources for W10
Vehicle / responsible body
Supply/rate agreements and permits / provider, operator, relevant regulator
Deadline or prerequisite milestone
P: before delivery/pumping; periodic audit
Documented versus proposed payer
D: supplier terms/cost allocation unverified. P: developer funds attributable capital, operating, replacement, and emergency costs.
Next step
Verify meters, rates, infrastructure obligations, cost study, security, and lawful rate authority.
Sources; checked
W11 — ISA-linked State Engineer supply review
Evidence status
Conditional statutory requirement; project trigger unresolved. Applies to permit/application-waiver applicants whose facility requires ≥800 acre-feet of Wyoming waters annually.
Responsibility & evidence
Details & sources for W11
Vehicle / responsible body
W.S. §35-12-108 / State Engineer, Industrial Siting Council
Deadline or prerequisite milestone
Statutory process after acceptable analysis; no Site Layer 4 notice/date established
Documented versus proposed payer
D: applicant-funded review under §108. P: developer funds any additional lawful independent study.
Next step
Verify required use and legal route; track published written-comment period. Separate hearing is discretionary.
Sources; checked
Electricity, generation, and storage11 entries
E01 — Wholesale economic/planning framework
Evidence status
General tariff accepted subject to condition. Protects defined wholesale interests; does not guarantee unchanged retail bills.
Responsibility & evidence
Details & sources for E01
Vehicle / responsible body
HILT / Tri-State, utility member, FERC
Deadline or prerequisite milestone
Covered-load evaluation before tariff service readiness
Documented versus proposed payer
D: wholesale obligations on member; customer recovery not established. P: attributable customer costs recovered from customer.
Next step
Establish applicability, requested grid load, forecasts, and evaluation results.
Sources; checked
E1 ¶¶64–68; E3 §§2.13,5.10; ENERGY-008–012,017; 2026-09-20
E02 — September compliance revisions
Evidence status
Filed, not verified subsequently accepted. No later acceptance order in the September 20 search of ER26-1929 filings dated September 9–20, without a subdocket restriction.
Responsibility & evidence
Details & sources for E02
Vehicle / responsible body
ER26-1929-002 / FERC
Deadline or prerequisite milestone
Published deadline in Take action; both identified erratum bodies read and concern other dockets
Documented versus proposed payer
D: no Site Layer 4 payer/security established by filing. P: none created by this comment process.
Next step
Refresh the docket before filing/publication; evaluate §§3.6/5.3.1 against the August order.
Sources; checked
E03 — Signed service/customer agreements
Evidence status
Project evidence unresolved. General participation sequence requires member–customer contract and member–Tri-State HILA; Tri-State countersigns after successful evaluation.
Responsibility & evidence
Details & sources for E03
Vehicle / responsible body
MCHIL and HILA / customer, serving member, Tri-State
Deadline or prerequisite milestone
Tariff participation/evaluation milestones; service readiness separately required
Documented versus proposed payer
D: member is wholesale obligor; customer’s share requires its contract. P: developer/customer bears attributable costs.
Next step
Obtain actual parties, signatures, exhibits, dates, amendments, evaluation, and Serve Ready Notice. Conforming HILA need not be publicly filed.
Sources; checked
E3 §§5.3–5.6, Appendix A §§3–4; ENERGY-013–014,021,025; 2026-09-20
E04 — Facilities and transmission cost rule
Evidence status
General requirement. FCA/security for specified directly assigned facilities/upgrades; SPP Attachment AX exception and mutually agreed timing variation exist.
Responsibility & evidence
Details & sources for E04
Vehicle / responsible body
Applicable OATT and FCA / member, Tri-State, transmission provider, FERC
Deadline or prerequisite milestone
Ordinarily before OATT study agreement unless mutually agreed; executed FCA filed within 15 Business Days of receipt
Documented versus proposed payer
D: member under §6.2; actual customer pass-through unresolved. P: project customer funds attributable costs within lawful allocation.
Next step
Verify itemized costs, exceptions, receipt date, FCA filing, and timing agreement.
Sources; checked
E3 §6.2 p. 13; ENERGY-015–017; 2026-09-20
E05 — Project generation/facilities funding chain
Evidence status
Applicant describes on-site generation; executed financing/cost allocation unresolved. On-site generation does not prove grid isolation.
Responsibility & evidence
Details & sources for E05
Vehicle / responsible body
Project financing, interconnection, FCA, customer contracts / identified counterparties
Deadline or prerequisite milestone
P: commitments before attributable exposure; applicable tariff milestones still control
Documented versus proposed payer
D: complete developer-to-utility funding chain unverified. P: developer/customer funds generation and attributable connection/transmission/facilities obligations.
Next step
Map each component and delivery point, import/export/standby demand, responsible party, and remaining member exposure.
Sources; checked
C2 p. 2; W1 p. 1; ENERGY-024–025; 2026-09-20
E06 — Minimum billing and utility security rule
Evidence status
General protection. Defined security, minimum charges, termination, renewal, and release provisions; not universal cash up front.
Responsibility & evidence
Details & sources for E06
Vehicle / responsible body
HILA and separate FCA / member and Tri-State
Deadline or prerequisite milestone
Notice-based HILA posting milestones; FCA has its own terms
Documented versus proposed payer
D: member posts or causes qualifying credit support/cash in Tri-State’s favor. P: customer supports attributable obligations through contract.
Next step
Apply defined Security MW, adjustments and Basin exception; do not multiply campus nameplate MW.
Sources; checked
E3 Appendix A §§7,10; ENERGY-018–020; 2026-09-20
E07 — Actual posted security and stranded-asset coverage
Evidence status
Project evidence unresolved. A template or signature is not proof of a current drawable instrument.
Responsibility & evidence
Details & sources for E07
Vehicle / responsible body
Actual HILA/FCA/customer security / beneficiaries and issuers
Deadline or prerequisite milestone
Before applicable exposure/service milestones and throughout term
Documented versus proposed payer
D: Site Layer 4 amount/provider/posting unresolved. P: customer funds sufficient attributable coverage.
Next step
Obtain due notices, instruments, receipt, beneficiary, expiry, renewal/replenishment, cancellation/shrinkage remedies; distinguish FCA damages.
Sources; checked
ENERGY-019–021,025; E3 Appendix A §§7,10; 2026-09-20
E08 — Independent tariff-process review
Evidence status
General requirement; project results unresolved. Independent evaluator checks tariff consistency; member results are subject to confidentiality.
Responsibility & evidence
Details & sources for E08
Vehicle / responsible body
HILT §5.13 / Tri-State and evaluator
Deadline or prerequisite milestone
After evaluation cycle
Documented versus proposed payer
D: member evaluation fees support process. P: no claim that this funds county experts.
Next step
Obtain result or releasable summary; verify economic-test assumptions/outcome.
Sources; checked
E3 §§5.9–5.13; ENERGY-011–012,022; 2026-09-20
E09 — Independent public load/economic study
Evidence status
Proposed request. Not equivalent to tariff-process review.
Responsibility & evidence
Details & sources for E09
Vehicle / responsible body
Authorized review funding/agreements / county-selected expert, participating utilities
Deadline or prerequisite milestone
P: before relevant approval and each major phase
Documented versus proposed payer
D: no project public-study funding verified. P: developer/customer.
Next step
Review actual load ramp, generation/import assumptions, costs and stranded exposure; publish lawful summary.
Sources; checked
ENERGY-012,022,025; COUNTY-020; 2026-09-20
E10 — Associated generation/storage SUP review
Evidence status
Recommended/proposed county rule. Applies to facilities built for data-center needs, not only same-parcel facilities.
Responsibility & evidence
Details & sources for E10
Vehicle / responsible body
Proposed §§6.10.000,7.10.000,8.05.060 / BOCC, then applicable SUP bodies
Deadline or prerequisite milestone
Commissioner consideration; qualifying applications thereafter
Documented versus proposed payer
D: no project permit/funding package proved. P: applicant funds compliance and attributable review costs where authorized.
Next step
Verify adopted wording and component permits; retain applicable federal/state requirements.
Sources; checked
C4 pp. 30,35,38; COUNTY-009; 2026-09-20
E11 — Battery thermal-runaway/fire response
Evidence status
Proposed campus/component request. Existing solar emergency provisions require separate applicability review; they do not prove a campus battery plan.
Responsibility & evidence
Details & sources for E11
Vehicle / responsible body
Component permits and emergency/service agreement / operator, responders, county, relevant agencies
Deadline or prerequisite milestone
P: funded plan, equipment and training before energization
Documented versus proposed payer
D: project funding unresolved; covered solar has separate rules. P: developer/operator.
Next step
Approve hazard-specific plan, access/water resources, drills, equipment, response costs and security.
Sources; checked
C8 §§13.15.060(L),.070; COUNTY-031; ENERGY-026; 2026-09-20
Public costs and long-term financial protection11 entries
F01 — Road Use Agreement
Evidence status
Staff anticipates agreement; project execution unresolved. In the September 18 reply to item 3 of the September 15 county records request, the clerk reported no agreements entered into at that time. This does not establish the status of every draft or private contract.
Responsibility & evidence
Details & sources for F01
Vehicle / responsible body
Road agreement/SUP as authorized / county and developer
Deadline or prerequisite milestone
P: executed and secured before development approval and road exposure
Documented versus proposed payer
D: no executed allocation established. P: developer funds attributable road work, maintenance and restoration.
Next step
Obtain traffic/cost study, signed terms, payment schedule, security and overrun remedy.
Sources; checked
(C2, C3) p. 3; C9; COUNTY-019,030; 2026-09-20
F02 — Fire/EMS, law enforcement and emergency services
Evidence status
Future review described; binding funding package unresolved.
Responsibility & evidence
Details & sources for F02
Vehicle / responsible body
Authorized service/development agreements / service bodies, county, operator
Deadline or prerequisite milestone
P: executed before development approval; capacity funded before demand
Documented versus proposed payer
D: no comprehensive payer allocation verified. P: developer funds attributable capital, staffing, operating and emergency costs.
Next step
Quantify demand and costs; secure payments, annual true-up and shortfalls.
Sources; checked
C2 p. 3; C9; COUNTY-019; 2026-09-20
F03 — Independent expert escrow
Evidence status
Broad idea discussed; dedicated escrow proposed.
Responsibility & evidence
Details & sources for F03
Vehicle / responsible body
Authorized fees/agreement and procurement / county and independent specialists
Deadline or prerequisite milestone
P: funded before technical review; replenish on defined threshold
Documented versus proposed payer
D: no project escrow verified. P: developer, without control over findings.
Next step
Verify authority and budget for hydrology, energy economics, land-use counsel, noise and air review.
Sources; checked
C5 ~37:27–38:45; C12 p. 5; COUNTY-020; 2026-09-20
F04 — Net fiscal effects and assessed value
Evidence status
Applicant investment estimate; fiscal outcome unresolved. Approximately $26 billion is not assessed value or guaranteed revenue.
Responsibility & evidence
Details & sources for F04
Vehicle / responsible body
Fiscal study; lawful assessment/budget processes / assessor, fiscal authorities, independent reviewer
Deadline or prerequisite milestone
P: before incentive/funding decisions; update with phases
Documented versus proposed payer
D: no net-positive fiscal result established. P: developer funds independent study where authorized.
Next step
Separate taxable value, lawful exemptions, collections, service costs, timing, and downside scenarios.
Sources; checked
F05 — PILOT/abatement safeguards
Evidence status
Conditional proposal only. No reviewed handoff establishes a specific incentive or PILOT.
Responsibility & evidence
Details & sources for F05
Vehicle / responsible body
Any lawful incentive/tax agreement / authorized taxing bodies and beneficiary
Deadline or prerequisite milestone
P: before any incentive approval
Documented versus proposed payer
D: no agreement or foregone-revenue amount verified. P: beneficiary funds enforceable obligations and clawback security.
Next step
If proposed, assess legality, net public benefit, escalating obligations, measurable terms and secured clawbacks.
Sources; checked
Evaluation fiscal bullet 3; COUNTY-033; L18; 2026-09-20
F06 — Zoning reversion
Evidence status
P&Z recommendation verified; final adopted terms unresolved. Noncommencement/permanent-decommissioning triggers require final text.
Responsibility & evidence
Details & sources for F06
Vehicle / responsible body
Final zoning instrument / BOCC and owner
Deadline or prerequisite milestone
Recommended five-year commencement trigger; no certified final clock here
Documented versus proposed payer
D: condition itself supplies no cleanup fund. P: developer separately funds cleanup.
Next step
Obtain final signed action, acceptance, trigger definitions, extensions and recording.
Sources; checked
C1 pp. 2–3; C2 pp. 4–5; COUNTY-002,005; 2026-09-20
F07 — General industrial cleanup bonding
Evidence status
Existing discretionary rule. Commissioners may require adequate cleanup/restoration bond.
Responsibility & evidence
Details & sources for F07
Vehicle / responsible body
Existing §7.05.050(B)(d) / BOCC
Deadline or prerequisite milestone
As lawfully imposed in applicable SUP
Documented versus proposed payer
D: bond may be required of permittee; no project posting proved. P: developer funds comprehensive applicable coverage.
Next step
Identify imposed condition and actual instrument; do not treat discretion as execution.
Sources; checked
C7 p. 30; COUNTY-023; 2026-09-20
F08 — Whole-campus funded cleanup security
Evidence status
Proposed request; project security unresolved. Distinct from reversion and financial-capacity evidence.
Responsibility & evidence
Details & sources for F08
Vehicle / responsible body
Authorized permits/secured agreement / responsible owners/operators and beneficiaries
Deadline or prerequisite milestone
P: before disturbance; resize before expansion and periodically
Documented versus proposed payer
D: no whole-campus funded instrument verified. P: developer/operator and agreed guarantors.
Next step
Independent teardown/reclamation estimate; verify amount, draw rights, renewal, successor coverage and release.
Sources; checked
COUNTY-023; STATE-009–012; (C7, C8); L35; 2026-09-20
F09 — State financial-ability review
Evidence status
Conditional statutory permit requirement. Not a verified project finding or cleanup deposit.
Responsibility & evidence
Details & sources for F09
Vehicle / responsible body
Applicable ISA permit/waiver route / Industrial Siting Council
Deadline or prerequisite milestone
Permit decision under applicable route
Documented versus proposed payer
D: applicant supplies financial evidence; no cash security follows merely from finding. P: developer funds any separately required assurance.
Next step
Obtain application financials, findings and conditions; distinguish assets from drawable security.
Sources; checked
F10 — Unfinished-project expenditure bond
Evidence status
Discretionary state mechanism. Covers specified local preparatory spending, with limits; not a universal teardown bond.
Responsibility & evidence
Details & sources for F10
Vehicle / responsible body
§35-12-113(e) / Council
Deadline or prerequisite milestone
If imposed as permit condition
Documented versus proposed payer
D: permit holder if imposed; project condition unverified. P: developer secures attributable unrecovered local commitments.
Next step
Check condition, protected spending, exceptions, beneficiary and actual instrument.
Sources; checked
F11 — Solar decommissioning/assurance
Evidence status
Existing component-specific rules; applicability/compliance unresolved. Some state assurance requirements survive through county wind/solar law.
Responsibility & evidence
Details & sources for F11
Vehicle / responsible body
Applicable solar permit / county and state under controlling law
Deadline or prerequisite milestone
Applicable permit/security milestones; current rules need confirmation
Documented versus proposed payer
D: covered permit holder under applicable rules; no project posting verified. P: developer covers lawful gaps.
Next step
Determine capacity, sales/accessory status, component boundary, PSC status, preemption, current rules and assurance.
Sources; checked
C8 §§13.15.060(Q),.070(N); L18 §18-5-503(b); L35 §105; STATE-011; 2026-09-20
Operating standards9 entries
O01 — Campus noise limits
Evidence status
Discussed; measurable campus limits proposed. Industrial noise can trigger SUP treatment; no new uniform campus numeric standard established here.
Responsibility & evidence
Details & sources for O01
Vehicle / responsible body
Authorized ordinance/SUP; applicable air/operating permits / county and relevant agencies
Deadline or prerequisite milestone
P: standards before approval; baseline before construction; tests at commissioning/operation
Documented versus proposed payer
D: no project compliance program funded. P: developer/operator.
Next step
Specify day/night dBA, averaging period, tonal/impulsive treatment, boundary and nearest-residence measurements, fans/generators, remedies.
Sources; checked
C7 §7.05.030(J); C5 ~1:45:50–1:47:15; COUNTY-016; 2026-09-20
O02 — General commercial/industrial setbacks
Evidence status
Existing rules. General minimums include 30 feet from public road easements/rights-of-way and 10 feet from adjacent property lines; application/waivers require review.
Responsibility & evidence
Details & sources for O02
Vehicle / responsible body
Current zoning rules / county
Deadline or prerequisite milestone
Siting/application review
Documented versus proposed payer
D: applicant must demonstrate compliance; project costs unresolved. P: developer.
Next step
Verify plans and any applicable greater conditions or waiver.
Sources; checked
C7 §§6.05.050,7.05.040; COUNTY-017; 2026-09-20
O03 — Additional data-center setback discretion
Evidence status
Recommended/proposed rule. Additional site-specific setbacks would be discretionary; not a uniform residential buffer.
Responsibility & evidence
Details & sources for O03
Vehicle / responsible body
Proposed district rules / BOCC
Deadline or prerequisite milestone
Commissioner rule consideration, then applicable SUP
Documented versus proposed payer
D: no project additional-setback condition verified. P: developer funds compliant siting.
Next step
Verify adopted text and any actual project condition.
Sources; checked
C4 pp. 29–35; COUNTY-007,017; 2026-09-20
O09 — Fixed residential buffer
Evidence status
Proposed request. One-mile mapping/notice is not a one-mile setback.
Responsibility & evidence
Details & sources for O09
Vehicle / responsible body
Authorized ordinance/SUP / BOCC
Deadline or prerequisite milestone
P: before project siting approval
Documented versus proposed payer
D: no uniform data-center residential buffer verified. P: developer funds compliant siting.
Next step
Establish justified distance using habitable-structure mapping and impact studies; verify authority and exceptions.
Sources; checked
C4 pp. 32–34; COUNTY-011,017; evaluation line 33; 2026-09-20
O04 — Dark-sky lighting
Evidence status
Discussed; campus standard proposed.
Responsibility & evidence
Details & sources for O04
Vehicle / responsible body
Authorized ordinance/SUP / county
Deadline or prerequisite milestone
P: photometric plan before approval; commissioning test
Documented versus proposed payer
D: no campus requirement/funding verified. P: developer/operator.
Next step
Specify shielding, maximum spill, operating schedule and correction procedure based on reviewed design.
Sources; checked
COUNTY-018; C5; 2026-09-20
O05 — Covered solar noise/setback/lighting standards
Evidence status
Existing separate solar rules; component applicability unresolved.
Responsibility & evidence
Details & sources for O05
Vehicle / responsible body
January 20, 2026 solar chapter / county
Deadline or prerequisite milestone
Applicable solar application and operation
Documented versus proposed payer
D: covered solar permittee complies; project funding unverified. P: developer/operator.
Next step
Apply correct chapter and full conditions; do not extend automatically to gas, standalone battery or accessory solar.
Sources; checked
C8 §§13.15.020–.050; COUNTY-031; 2026-09-20
O06 — Air emissions and generator hours
Evidence status
Applicant preliminary PSD assessment; project permit/limits unresolved. Measurable operating/runtime safeguards proposed.
Responsibility & evidence
Details & sources for O06
Vehicle / responsible body
Applicable air permits and authorized local conditions / DEQ Air Quality and county within authority
Deadline or prerequisite milestone
Agency permit prerequisites; P: limits before operation
Documented versus proposed payer
D: no project permit/funding terms established. P: developer/operator.
Next step
Obtain emissions inventory/modeling and actual permit; distinguish routine testing, backup and primary generation; specify hours/logs and emissions compliance.
Sources; checked
W2 p. 2; ENERGY-026; evaluation energy/operating bullets; 2026-09-20
O07 — Water protection and containment information
Evidence status
Existing industrial application framework plus proposed detail. Engineering/effluent information is not proof of implemented safeguards.
Responsibility & evidence
Details & sources for O07
Vehicle / responsible body
Current Ch. 7 and proposed amendments / county; other agencies as applicable
Deadline or prerequisite milestone
Applicable application completeness/review
Documented versus proposed payer
D: applicant provides required studies; no project cleanup fund proved. P: developer/operator.
Next step
Compare clean adopted text and site design, including secondary containment.
Sources; checked
C7 pp. 29–30; C4 pp. 32–34; COUNTY-011,032; 2026-09-20
O08 — Stormwater and hazardous-material operating plans
Evidence status
Detailed project plans/permits unresolved; stronger measurable safeguards proposed. Includes diesel, transformer oil and battery hazards.
Responsibility & evidence
Details & sources for O08
Vehicle / responsible body
Applicable environmental/fire permits and authorized SUP / operator, county, DEQ and responders
Deadline or prerequisite milestone
P: approved/funded before disturbance, storage or operation as relevant
Documented versus proposed payer
D: executed project funding unresolved. P: developer/operator.
Next step
Verify drainage, spill containment, inventories, inspections, incident reporting, response/cleanup funding and applicable permits.
Sources; checked
C13 p. 8 applicant design statement; C4 Ch. 7; C8 conditional; evaluation operating bullet 2; 2026-09-20
Governance, transparency, and enforcement12 entries
G01 — Applicant/contact/landowner identity
Evidence status
Disclosures in filing. Not ultimate ownership, final end-user or operator verification.
Responsibility & evidence
Details & sources for G01
Vehicle / responsible body
County application / applicant and county
Deadline or prerequisite milestone
Application review
Documented versus proposed payer
D: applicant provides information; no guarantee proved. P: applicant maintains accurate disclosures.
Next step
Verify title/control and each disclosed role without merging entities.
Sources; checked
C13 pp. 2,8,19; (W1, W2); COUNTY-027; 2026-09-20
G02 — Beneficial owners, end-user, operators and guarantors
Evidence status
Proposed expanded disclosure; identities unresolved.
Responsibility & evidence
Details & sources for G02
Vehicle / responsible body
Authorized application/contract terms / county, owners, operators, counterparties
Deadline or prerequisite milestone
P: before relevant approval; update before transfers
Documented versus proposed payer
D: no complete duty or funded guarantee verified. P: developer funds disclosure/compliance.
Next step
Obtain control chain, component responsibilities, contracts and guarantor capacity.
Sources; checked
COUNTY-027; ENERGY-025; evaluation governance bullet 1; 2026-09-20
G03 — Existing industrial successor conditions
Evidence status
General adopted provisions. SUP continuation conditions address successors; project compliance unresolved.
Responsibility & evidence
Details & sources for G03
Vehicle / responsible body
Existing industrial rules/SUP / county and successor
Deadline or prerequisite milestone
Applicable use and transfer
Documented versus proposed payer
D: permittee/successor duties under rule; no broad guarantee proved. P: responsible parties fund continuing compliance.
Next step
Obtain actual SUP terms; review transfer exceptions and covered obligations.
Sources; checked
C7 §§1.05.060(A),7.05.050(B); COUNTY-024; 2026-09-20
G04 — Recorded development agreement
Evidence status
Project instrument unresolved; stronger recorded obligations proposed.
Responsibility & evidence
Details & sources for G04
Vehicle / responsible body
Legally supported agreement/recording / county and bound owners/operators
Deadline or prerequisite milestone
P: before approval/exposure; no release on sale without authorized replacement
Documented versus proposed payer
D: no executed recorded instrument verified. P: developer funds obligations, security and lawful costs.
Next step
Verify parcels, signatures, recording, assignment/change-of-control, beneficiary rights, default and insolvency treatment.
Sources; checked
C9; COUNTY-024,033; 2026-09-20
G05 — General enforcement office and remedies
Evidence status
Existing rules. Planning Officer monitors/processes; County Attorney prosecutes as directed by BOCC; penalties/court remedies exist.
Responsibility & evidence
Details & sources for G05
Vehicle / responsible body
Current rules and Title 18 / county and courts
Deadline or prerequisite milestone
On applicable violation, notice and legal procedure
Documented versus proposed payer
D: general county functions; no project inspection-fee agreement verified. P: developer funds attributable oversight where authorized.
Next step
Apply actual duties/remedies; do not say there is no enforcement authority.
Sources; checked
C7 §1.05.050; L18 §§18-5-204–206; COUNTY-021; 2026-09-20
G06 — Campus inspection/reporting and remedy schedule
Evidence status
Proposed request; project program unresolved. Includes named inspector, cadence, cure periods, penalties and lawful stop-work/curtailment triggers.
Responsibility & evidence
Details & sources for G06
Vehicle / responsible body
Authorized conditions/agreement / county, relevant agencies, operator
Deadline or prerequisite milestone
P: before disturbance/operation; recurring and incident-driven
Documented versus proposed payer
D: no funded program verified. P: developer funds authorized oversight and corrective work.
Next step
Publish responsibility matrix; verify each remedy’s authority and due process before adoption.
Sources; checked
COUNTY-021,033; C7; L18; 2026-09-20
G07 — Public water/gas/electricity and compliance reports
Evidence status
Discussed; public campus program proposed. Covered solar reports to Planning Office and utility confidential review are different duties.
Responsibility & evidence
Details & sources for G07
Vehicle / responsible body
Authorized conditions/reporting agreements / operator and oversight body
Deadline or prerequisite milestone
P: monthly use reports, quarterly compliance summary
Documented versus proposed payer
D: no campus publication duty verified. P: developer/operator.
Next step
Define meters, verification, publication, lawful redactions and late-report remedy.
Sources; checked
COUNTY-022,031; ENERGY-022; WATER-014; 2026-09-20
G08 — Expansion review
Evidence status
Recommended/proposed. New/amended SUP when server capacity, power draw or cooling infrastructure exceeds original approval; no added “material” threshold.
Responsibility & evidence
Details & sources for G08
Vehicle / responsible body
Proposed district rules / BOCC, P&Z
Deadline or prerequisite milestone
Before expansion beyond original approval if adopted
Documented versus proposed payer
D: applicant process obligation proposed; no project funding proved. P: developer funds authorized review/compliance.
Next step
Verify adoption and baseline approval quantities.
Sources; checked
C4 pp. 30,35,38; COUNTY-008; 2026-09-20
G09 — Phase gates and off-ramps
Evidence status
Proposed request. Applicant buildout narrative is not binding staged approval.
Responsibility & evidence
Details & sources for G09
Vehicle / responsible body
Authorized SUP/agreements / county and relevant regulators
Deadline or prerequisite milestone
P: before each phase; withhold next phase on defined unmet prerequisites
Documented versus proposed payer
D: no campus phase-gate instrument verified. P: developer funds phase-specific and closure exposure.
Next step
Define capacity ceilings, completion tests, security increments, and lawful pause/closure remedies.
Sources; checked
COUNTY-025; C4; 2026-09-20
G10 — Whole-campus plan/PUD
Evidence status
Discussed for future study; mandatory PUD proposed, not in reviewed recommendation. Preliminary plan review is a separate recommendation.
Responsibility & evidence
Details & sources for G10
Vehicle / responsible body
Authorized master-plan/SUP framework / county; cross-county coordination as needed
Deadline or prerequisite milestone
P: before piecemeal project approvals
Documented versus proposed payer
D: no adopted full-campus PUD/funding proved. P: developer funds plan and independent review.
Next step
Cover the 5,344-acre Platte request and disclose links to the broader Platte–Goshen proposal; verify authority rather than import Laramie rules.
Sources; checked
C1 pp. 2–3; C5 ~2:04:42–2:14; COUNTY-003,026,033; 2026-09-20
G11 — Conflict letter and recusal record
Evidence status
Recorded chair statement and general recusal rule; application unresolved. Minutes record counsel’s no-conflict advice as stated by Chair Shepard.
Responsibility & evidence
Details & sources for G11
Vehicle / responsible body
Bylaws, applicable ethics law, meeting records / county officials/counsel
Deadline or prerequisite milestone
Before affected future participation; historical record review now
Documented versus proposed payer
D: official records/review; no developer-funded adjudication proposed. P: public body uses lawful public resources.
Next step
Obtain referenced letter, disclosed facts, attachments and recorded recusals/votes; missing letter is not proof of misconduct.
Sources; checked
C1 p. 1; C12 p. 6; C5 ~40:20–40:49; COUNTY-028–029; 2026-09-20
G12 — Limits on government secrecy agreements
Evidence status
Proposed policy; no relevant executed government NDA established in this review.
Responsibility & evidence
Details & sources for G12
Vehicle / responsible body
Lawful public-body contract/records policy / county and any participating town
Deadline or prerequisite milestone
P: before entering confidentiality terms
Documented versus proposed payer
D: no agreement/payment verified. P: public body reviews its legal duties; applicant funds its own submissions.
Next step
Request no contractual secrecy beyond lawful protections; publish releasable terms and grounds for redaction. Verify authority and actual agreement before alleging secrecy.
Sources; checked
Evaluation governance bullet 5; COUNTY-033; ENERGY-022 distinguishes utility confidentiality; 2026-09-20
State oversight and community funding5 entries
S01 — Project-specific siting route
Evidence status
Preliminary coordination; current application/exemption/determination unresolved. Full review where legally applicable is a proposed public request.
Responsibility & evidence
Details & sources for S01
Vehicle / responsible body
ISA jurisdiction/permit route / DEQ, Council, applicant
Deadline or prerequisite milestone
No verified Site Layer 4 state hearing/comment date
Documented versus proposed payer
D: no project permit funding terms established. P: applicant funds required review and lawful mitigation.
Next step
Obtain actual file and component-by-component written jurisdiction analysis; do not infer exemption from zoning.
Sources; checked
S02 — County prerequisite for state documentation
Evidence status
Recommended/proposed. Qualifying applicant supplies permit or exemption letter before first P&Z meeting.
Responsibility & evidence
Details & sources for S02
Vehicle / responsible body
Proposed district rules / county and state decision-maker
Deadline or prerequisite milestone
If adopted: before first P&Z meeting for qualifying application
Documented versus proposed payer
D: proposed applicant submission duty; not full-review mandate. P: developer funds compliance.
Next step
Verify final text, qualifying scope and authentic state instrument.
Sources; checked
C4 pp. 30,35,38; COUNTY-010; 2026-09-20
S03 — State hearing, findings and oversight
Evidence status
Conditional statutory process. §107 application waiver differs from §119 exemption; exempt activities are outside Council jurisdiction.
Responsibility & evidence
Details & sources for S03
Vehicle / responsible body
Applicable ISA route / Council and DEQ
Deadline or prerequisite milestone
Actual application/notice milestones; none established here
Documented versus proposed payer
D: applicable permit duties, no project commitments verified. P: developer funds lawful obligations.
Next step
Identify permitted/exempt activities, participation rights and remaining agency review. County agreement cannot recreate Council jurisdiction.
Sources; checked
S04 — Impact assistance
Evidence status
Conditional statutory funding route; project eligibility/award unresolved. Private construction generally requires qualifying ISA permit plus other conditions.
Responsibility & evidence
Details & sources for S04
Vehicle / responsible body
Current §39-15-111(c)–(d) / Council and relevant fiscal authorities
Deadline or prerequisite milestone
Construction-related statutory process; no project award/date verified
Documented versus proposed payer
D: statutory public sales/use-tax distributions if eligible, not developer security. P: developer directly funds attributable costs through separate lawful commitments.
Next step
Verify permitted components, tax eligibility, unmitigated needs, materials-cost caps and any award.
Sources; checked
S05 — Lawful alternatives and irreplaceable state functions
Evidence status
Proposed gap assessment. Local commitments can address some practical impacts, not replace every state protection.
Responsibility & evidence
Details & sources for S05
Vehicle / responsible body
Authorized permits/contracts / county, state, service bodies and bound project parties
Deadline or prerequisite milestone
P: before decisions relying on reduced state review
Documented versus proposed payer
D: no replacement package verified. P: developer secures lawful direct obligations; public bodies retain statutory duties.
Next step
Publish a protection-by-protection matrix, authority, payer and remedy; identify gaps in hearing rights, funding eligibility, §108 opinion and water-right administration.
Sources; checked
STATE exemption matrix; WATER-004–006,013–015; COUNTY-033; 2026-09-20
Water evidence · State consequences · Utility instruments · Retrieval targets · Proposed safeguards P1–P8