VALAR WATCHTake action

Claims vs Record

What Valar, its people and officials said, set beside what the documents show. Each entry gives both sides with sources, the exact gap, and what it means in plain terms. Claims that hold up are listed too.

documented conflict 2 · claim not supported 1 · unresolved 7 · claim holds up 3

documented conflicttechnical

Ward 250's fuel: Valar's safety agreement lists 4.95% uranium; its Los Alamos release and DOE's shipping review say HALEU

disc-001

What was said

What the record shows

The gap: The only Valar safety paper for Ward 250 found in public records lists 4.95% (ordinary) uranium. Valar's own Los Alamos release a month later calls the same fuel HALEU, and DOE's shipping review cleared shipments of HALEU of up to 19.9% U-235 to Ward 250 as its fuel. A reading favorable to the company, which Valar has not stated, is that the paper's fuel figures were preliminary design values to be corrected in a later safety analysis DOE reviewed; it is plausible: the paper calls its fuel assumptions preliminary. It does not remove the conflict: the NOVA core began its approach to criticality with HALEU TRISO fuel Valar says it provided on 12 November 2025, 30 days after the 4.95% paper was posted, and no correction to the public paper was found. Whether DOE's approved safety analysis describes HALEU is not shown by any public record found as of late September 2026.
In plain termsReactor fuel is graded by how much of the uranium is the kind that splits (U-235). Ordinary power-plant fuel has up to 5%; HALEU has 5% to just under 20%. Ward 250 burns TRISO fuel: poppy-seed-sized beads of uranium, each sealed in layers of carbon and ceramic and pressed into small pellets. Valar's only public safety paper says the uranium is 4.95%, the ordinary grade. Valar's own Los Alamos announcement a month later calls the same fuel HALEU, and DOE cleared shipments of fuel blocks for Ward 250 enriched up to 19.9%, about four times richer. A possible explanation, which Valar has not stated, is that the paper was an early draft whose fuel numbers were updated in a later safety analysis DOE reviewed; the paper does call its fuel assumptions 'preliminary.' That may be so, but no public copy of the later analysis was found and no correction to the public paper was found. The one safety document the public can read describes different fuel from the fuel DOE cleared for this reactor.

Why it matters: The fuel grade changes the reactor's physics and how much fissile uranium sits in Emery County. The public safety paper does not describe that fuel.

What would settle it: FOIA to DOE Idaho Operations Office for the fuel specification and core description in Ward 250's approved PDSA and final DSA, the Technical Safety Requirements and DOE's Safety Evaluation Report; FOIA to DOE Savannah River Operations Office and NNSA Nevada Field Office for the shipment records under the Model 9979 letter amendment; or Valar publishing the as-loaded enrichment.

facts orig-008, safe-010, dir-009, orig-033 · checked 2026-10-02: Checked in late September 2026 for Valar's side of the record: re-read NSDA pp. 11, 25, 52 (fuel assumptions 'preliminary'; qualification basis AGR-1/2 data; update clause tied to AGR-spec TRISO), NOVA release (approach to criticality from 12 Nov 2025; 'same fuel'; Valar provided the TRISO fuel) and the SER (shipments from NCERC in Nevada). No Valar statement explaining the 4.95% line was found on its site or in the documents read. The design-draft reading is plausible, but the conflict survives because HALEU fuel was in use 30 days after the posting and no revision of the paper was found. Summary line checked: literally true (NOVA says HALEU; NSDA says 4.95%). | Earlier check: re-read in late September 2026 (saved copies): NOVA release ('HALEU TRISO-fueled'; 'the same fuel, moderator, and reactivity-control scheme as Ward250'), NSDA Table 6 p. 52 and p. 11, DOE SER (19.9 wt.% maximum; 234.94 g per block; end use in Ward 250), DOE HALEU page, TLA September memo. Restructured: the NSDA is now shown as a Valar claim beside the NOVA claim, and DOE's shipping review as the record, which is what the documents are. The SER is DOE's review recommending the letter amendment; the amendment letter itself was not read. | Revised before publication (late September 2026): 'Against that reading' record no longer infers the HALEU fuel existed on 13 Oct 2025; states the 30-day interval instead. | Revised before publication (late September 2026): gap no longer infers the HALEU fuel existed at posting; states the 30-day interval; 'never corrected' now 'no correction found'; verification wording updated ('summary line'). Revised before publication (2026-09-30): reworded why it matters; reworded the plain-language text; reworded the summary line; reworded the gap.
documented conflictpublic process

'Not trying to keep anything from anyone', said the lab director; the state's MOU with Valar said it and related information were confidential, except as required by law; the energy office uses similar terms with some other nuclear companies

disc-030

What was said

What the record shows

The gap: At Emery County's June 2025 hearing on nuclear industries, the state's lab director called the meeting 'the first of many' and said nothing was being kept from anyone; the state's signed agreement with Valar, then a month old, said the agreement and related information were confidential, required Valar's approval for outside disclosures and barred publicity without consent.
In plain termsAt Emery County's June 2025 public hearing on nuclear industries, the state official who runs the lab told residents transparency was 'imperative', that nothing was being kept from anyone, and that the meeting was 'the first of many'. A month earlier his agency had signed an agreement with Valar saying the deal and related information were confidential, that the state needed a Valar officer's approval to disclose things, and that neither side would publicize it without the other's consent. In fairness, the state still has to answer public-records requests, it uses similar clauses with some other nuclear companies, and it later posted the agreement online. But on the day he spoke, the agreement itself was confidential, and the minutes do not record him mentioning that.

Why it matters: Residents weigh officials' statements about openness; the lab director's June 2025 statement and the confidentiality terms of OED's May 2025 MOU with Valar sit side by side in the record, and the minutes do not show the MOU being mentioned.

What would settle it: GRAMA to the Utah Office of Energy Development for any records it has classified as protected or redacted at Valar's request under the MOU, and for Valar's confidentiality designations.

facts gov-011, gov-020 · checked 2026-10-02: Re-read in late September 2026: Emery County's 17 June 2025 hearing minutes (the quote is exact; the minutes spell him 'Jaren Wallis') and the scanned pages of the OED MOU (clauses 4, 5 and 8 quoted exactly); the groundbreaking release confirms the lab is a unit within OED. The MOU's GRAMA clause, similar clauses in some of OED's later MOUs with other companies (gov-011) and the January 2026 posting are noted on the state's side. The conflict is narrow: an absolute statement against a signed confidentiality term then in force. Residents named in the minutes are not named here. Corrected in late September 2026: why-it-matters restated as the two records side by side.
claim not supportedsafety

Spent fuel for five minutes like a CAT scan: no supporting calculation or correction found on Valar's site as of late September 2026

disc-014

What was said

  • Isaiah Taylor (Valar's NRC-lawsuit post, still online) (2025-04-07): "Our analysis indicates" that "holding the spent fuel from this system for five minutes" gives the radiation exposure of a CAT scan.
    Valar Atomics is Suing the NRC (Isaiah Taylor) (Valar Atomics, 2025-04-07)

What the record shows

The gap: Valar's public claim that holding its spent fuel for five minutes equals a CT scan concerned Ward One, a planned 100 kWt reactor with a planned lifetime under a month, and gave no cooling time. No supporting calculation and no correction were found on Valar's site as of late September 2026, where the post stands unchanged; since sometime between 23 March and 22 July 2026 the page has carried a tag asking search engines not to list it, and who added it and why is not in the record. For scale: a CT scan is about 1 to 10 millisieverts (FDA), so five minutes would need 12 to 120 millisieverts an hour; the post gives no amount of fuel, cooling time, distance or shielding.
In plain termsUsed reactor fuel, including the TRISO fuel beads Valar uses, is radioactive after it comes out of a reactor, because the split uranium atoms leave behind radioactive fragments; how radioactive depends on the reactor's power, how long it ran and how long the fuel has cooled. In April 2025 Valar's founder wrote that holding the spent fuel from his planned small reactor for five minutes would give about the same radiation as a CT scan, a routine hospital scan. No calculation supporting it has been found on Valar's site. The original sentence is still on Valar's site, unchanged, and since sometime between March and July 2026 the page has carried a tag asking search engines not to list it; who added it and why is not in the record. For Ward 250, Valar's own safety paper treats radiation shielding as a safety function, and DOE's review has the used fuel leave the site in dry storage casks.

Why it matters: A founder's public statement about holding used fuel remains on the company's site; no supporting calculation or correction was found there as of late September 2026.

What would settle it: Valar publishing its calculation or a correction; any later change to the post would show against archived copies.

facts orig-017, orig-061, safe-026 · checked 2026-10-02: Checked in late September 2026: re-read Valar's 7 April 2025 NRC-lawsuit post on the live site (the sentence concerns Ward One, 100 kWt, planned life under a month, and states no cooling time; the robots tag 'noindex, nofollow' confirmed in the page code), Internet Archive copies of 23 March 2026 (no tag) and 22 July 2026 (tag present), the Ward250 Nuclear Safety Design Agreement and DOE's categorical exclusion. No Valar correction or supporting calculation was found on its site. Corrected in late September 2026: added the CT-scan dose-rate scale (12 to 120 millisieverts an hour over five minutes); title and wording restated as 'no correction found'. Updated 30 Sept 2026: news and commentary citations removed so the entry rests on Valar's own words and government records; now also cites the U.S. Energy Information Administration.
unresolvedtechnical

How much fuel is in the core: 76 elements on paper, 24 cleared to ship, and 'very lightly loaded' in Valar's words

disc-004

What was said

What the record shows

  • DOE's shipping review says 'only 24 packages (24 fuel elements) would be authorized for shipment', each block holding 170 TRISO compacts and at most 234.94 g of U-235: at most about 5.64 kg of U-235 in all, in fuel up to 19.9% enriched. Per element, the NSDA's own figures imply 162.83 g of U-235 in 3.29 kg of heavy metal; DOE's block holds at most 234.94 g of U-235 (about 1.18 kg of uranium if at the 19.9% maximum). The per-element figures differ (76 such blocks holding 250 kg would need 7.14% fuel, not Table 6's 4.95%), so Table 6's equal per-element loading does not match the block DOE cleared, unless some of the 76 elements are unfueled or loaded differently, which the paper does not say.
    Safety Evaluation Report, Letter Amendment of Certificate of Compliance No. 9979 for the Model 9979 Package, Docket 26-35-9979 (U.S. Department of Energy, Packaging Certification Program, 2026-05-20)
  • DOE's criticality release reports a 'zero-power fueled criticality demonstration' and gives no core loading. No public record read gives the number of fuel blocks loaded, the startup physics results, or how the safety analyses were adjusted for a partly loaded core of richer fuel; the approved DSA, which would, was not found in public records.
    Department of Energy Celebrates Second Advanced Reactor Achieving Criticality (U.S. Department of Energy, 2026-06-18)
  • DOE's shipping review limits the count to 24 fuel elements 'under this letter amendment', that is, under this one approval; it does not say the core can never hold more, and no other shipment approval was found.
    Safety Evaluation Report, Letter Amendment of Certificate of Compliance No. 9979 for the Model 9979 Package, Docket 26-35-9979 (U.S. Department of Energy, Packaging Certification Program, 2026-05-20)
The gap: The public safety paper describes its design core: 76 elements of 4.95% fuel. DOE's shipping approval covers 24 elements of fuel up to 19.9% enriched under one letter amendment, and a Valar speaker says the core is 'very lightly loaded'; those two statements agree with each other. What is actually in the reactor, and how the safety analysis was adjusted for that core, were not found in public records read to late September 2026.
In plain termsThink of the core as a honeycomb of 76 fuel elements. The paper the public can read describes all 76 filled with ordinary-grade fuel; that was the design on paper. DOE's shipping review cleared 24 fuel blocks (its term for the elements) of richer fuel, and a Valar speaker told the state board the reactor is 'very lightly loaded.' Those two fit together, and a test reactor starting with a partly filled core is not by itself a warning sign. A statement of what is actually inside the reactor, and of the safety numbers for that core, was not found in public records.

Why it matters: How much fuel is in the core, and how rich it is, sets how the reactor behaves and what radioactivity builds up; the published safety analysis describes a different core.

What would settle it: FOIA to DOE Idaho Operations Office for Ward 250's core-loading records, startup physics test results and the approved DSA core description; FOIA to DOE and NNSA for nuclear material transaction reports (NMMSS) recording fuel received at the San Rafael Energy Lab.

facts safe-010 · checked 2026-10-02: Checked for fairness to Valar, late September 2026: the 76-element core is the paper's design value; Gardner's 'very lightly loaded' and the SER's 24 elements agree; the SER's 24 is a limit 'under this letter amendment'. No record of a later shipment approval or of the as-loaded core was found. Status stays unresolved. Summary line literally true of the three sources. | Earlier check: Re-read in late September 2026: NSDA Table 6; SER sections 1 and 6 (24 packages; 170 compacts; 234.94 g U-235 per block); 17 Sept 2026 auto-transcript (Gardner). Arithmetic: 24 x 234.94 g = 5.64 kg; 250 kg x 4.95% = 12.4 kg. Status unresolved: a partial core is not by itself a conflict; the gap is what is loaded and whether the analyses match it. | Revised before publication (late September 2026): summary line says 'fuel elements' (the NSDA's term); record adds the per-element U-235 and heavy-metal comparison. | Revised before publication (late September 2026): plain uses 'fuel elements' for the NSDA and 'block' only for DOE's shipping review; verification wording updated ('summary line').
unresolvedsafety

Worst-case dose built on 30 full-power days (3 megawatt-days); the same paper's burnup limit reads 30 megawatt-days

disc-005

What was said

What the record shows

  • The same safety agreement's operating limit (page 25) is 'Fuel burnup limit: 30 megawatt-days'. At the 100 kW continuous limit, 30 MWd is 300 full-power days: ten times the 30 days (3 MWd) the accident inventory was built on.
    Ward250 Nuclear Safety Design Agreement, No. 100403, Rev 02 (status: Draft), page 25 (Valar Atomics, 2025-10)
  • Its objectives (page 8) call for completing tests 'within the 12-month operational period' with 'availability factors exceeding 80%': 12 months at 80% is about 292 days, which at 100 kW is about 29 MWd, close to the 30 MWd limit rather than the 3 MWd analysis, but only if the reactor ran at full power whenever available (see the availability caveat below).
    Ward250 Nuclear Safety Design Agreement, No. 100403, Rev 02 (status: Draft), page 8 (Valar Atomics, 2025-10)
  • The paper names iodine-131 and noble gases as the main contributors to the worst-case dose and does not show how the dose would change with ten times the fuel use, so the size of the effect cannot be read from it.
    Ward250 Nuclear Safety Design Agreement, No. 100403, Rev 02 (status: Draft), pages 34-37 (Valar Atomics, 2025-10)
  • DOE's environmental review describes about 12 months of operation and says less than 1% of the initial fissile material is consumed; it gives no burnup figure.
    NEPA Determination DOE-ID-26-005: Valar Ward250 Research Reactor (categorical exclusion B5.26) (U.S. Department of Energy, Office of Nuclear Energy, 2026-04-22)
  • The EPA gives iodine-131, which the safety paper names its 'primary dose contributor', a half-life of 8 days ('Iodine-131’s short half-life of 8 days'). By that half-life, 30 days of steady running builds iodine-131 to about 93% of the most it can reach at that power (1 minus 0.5 to the power 30/8); running ten times longer at the same power adds at most about 8% more. Slower-decaying materials the paper lists (such as cesium-137) keep accumulating with use, on the paper's own 'inventory buildup' premise, so they are not bounded the same way.
    Radionuclide Basics: Iodine (U.S. Environmental Protection Agency, 2026-01-22)
  • Every other Valar statement of the operating plan we found in public records gives 30 full-power days: the accident inventory itself ('Conservative 30 EFPD operation', p. 34), the July 2025 slides ('30EFPD, in 12 months') and the June 2026 draft page ('30 Effective Full Power Days at 100kWt'). Only the page-25 limit reads '30 megawatt-days'. A 30-day figure written in the wrong unit would produce exactly this tenfold gap: a plausible reading, not a confirmed one.
    Ward250 Nuclear Safety Design Agreement, No. 100403, Rev 02 (status: Draft), pages 25 and 34 (Valar Atomics, 2025-10)
  • The page-8 goal is 'availability factors exceeding 80% during test campaigns'. Availability describes readiness during campaigns; it does not say the reactor runs at full power that long, so by itself it does not imply about 29 megawatt-days.
    Ward250 Nuclear Safety Design Agreement, No. 100403, Rev 02 (status: Draft), page 8 (Valar Atomics, 2025-10)
The gap: The accident inventory assumes 30 full-power days at 100 kW (3 MWd), matching every other Valar statement of the plan. One line of the same draft sets the burnup limit at 30 megawatt-days, ten times that, and its method statement calls for inventory at maximum licensed power to equilibrium. The likeliest simple reading is a unit slip (30 days written as 30 megawatt-days); only the approved Technical Safety Requirements, which were not found in public records as of late September 2026, can confirm it. Even if the reactor ran ten times longer at the same power, iodine-131, which the paper names as the main contributor to dose, would rise by less than a tenth because it nears its maximum within weeks; slower-decaying materials would grow. Our check: the iodine-131 inventory would rise about 8%; cesium-137 and strontium-90 about tenfold, but still about 4% of the iodine-131 activity. Even scaling the paper's site-boundary bounds up tenfold (under 100 millirem in its dose tables; under 0.5 rem on pages 11, 14 and 54) gives under 1 rem or under 5 rem, both below the paper's 25 rem guideline.
In plain termsIn a nuclear accident, what can escape depends partly on how much radioactive material has built up in the fuel. Valar's worst-case calculation assumed the reactor had run the equivalent of 30 days at full power, and every other Valar statement of the plan we found also says 30 full-power days. But one line of the same paper sets the fuel-use limit at '30 megawatt-days', which is ten times more. That line may simply use the wrong unit; the paper's own accident inventory (30 full-power days) points that way. It also matters less than it sounds: the main contributor to the worst-case dose, iodine-131, loses half its strength every 8 days, so after a month of running it is already near its peak and running ten times longer adds at most about 8% more. Slower-fading materials would keep growing. The approved limits that would settle it were not found in public records.

Why it matters: The accident inventory underlies the dose at the fence, the request for on-site-only emergency planning and the absence of 'Safety Class' equipment; which limit governs decides whether that inventory is the right one.

What would settle it: FOIA to DOE Idaho Operations Office for the source term and burnup assumptions in the approved DSA accident analysis (Chapter 13), the TSR burnup limit, and DOE's Safety Evaluation Report on the DSA.

facts safe-009, orig-045, mine-019 · checked 2026-10-02: Checked for fairness to Valar, late September 2026: tested a unit-slip reading (all other Valar statements say 30 EFPD; only NSDA p. 25 says 30 MWd), the availability wording (p. 8, 'during test campaigns'), and the effect size using EPA's 8-day iodine-131 half-life (read on epa.gov (copy saved 30 September 2026); arithmetic: 1 - 0.5^(30/8) = 0.926). Status changed from documented conflict to unresolved: the simplest reading is plausible and the dose effect for the named main contributor is small, but the approved Technical Safety Requirements were not found in public records. Summary line literally true of p. 25. | Earlier check: Re-read in late September 2026: NSDA pp. 8, 10, 25, 34-37 (quotes exact), July 2025 slide 7 (viewed as an image: 'operates for 30EFPD, in 12 months in a temporary facility'), By the Numbers page, CX. Arithmetic re-checked: 30 d x 0.1 MW = 3 MWd; 30 MWd / 0.1 MW = 300 d; 365 x 0.8 = 292 d. Fairness note: Valar's own later statements (30 EFPD) match the analysis, not the 30 MWd limit; if the approved TSRs cap operation at 30 EFPD the gap closes, which is why the TSRs would settle it. | Revised before publication (late September 2026): gap adds our scaled arithmetic check (tenfold bound still 1 rem). | Revised before publication (late September 2026): verification wording updated.
unresolvedsafety

Outlet temperature: 650°C is the limit, and Valar's public summary says 650°C; the same draft lists 750°C 'under normal operations' as a goal

disc-002

What was said

What the record shows

The gap: In the draft, 650°C is the maximum outlet temperature (a safety limit tied to material limits) and the fuel's normal maximum; 750°C appears as a performance goal 'under normal operations' and as the temperature for a cautious vessel creep check. Valar's public summary sides with 650°C, and 750°C matches the hardware's non-nuclear test range, so the likeliest reading is an out-of-date goal line in a draft. The power goal fits the one-hour 250 kWth limit. Which numbers bind is set by the Technical Safety Requirements, which were not found in public records.
In plain termsA reactor's safety paperwork sets hard limits. Ward 250's draft safety paper says the gas leaving the core may not go above 650°C, a limit set by what the materials can take, and Valar's own public summary repeats 650°C. The same draft also lists, among its goals, reaching 750°C 'under normal operations.' The likeliest explanation is an out-of-date goal: the hardware was run hotter than 750°C in tests before it had fuel, and checking the steel vessel at 750°C is the cautious direction. The approved operating limits that would settle which figure applies were not found in public records.

Why it matters: In the draft, the 650°C outlet temperature is a safety limit tied to material limits, while 750°C is listed as a goal; the approved operating limits that say which applies were not found in public records.

What would settle it: FOIA to DOE Idaho Operations Office for the Technical Safety Requirements (operating limits) in the approved DSA and any DOE approval of power ascension above 100 kWth or outlet temperatures above 650°C.

facts orig-006 · checked 2026-10-02: Checked for fairness to Valar, late September 2026: re-read NSDA pp. 2, 8, 23, 25, 49, 52, the NSDA web summary ('up to 650°C'), By the Numbers ('temps above 750c' in non-nuclear testing) and the August 2025 post. The power half of the old gap dissolves ('steady-state' up to 250 kWth fits the one-hour limit); the temperature half is an internal inconsistency with a plausible stale-goal reading and Valar's own public summary on the 650°C side. Moved to unresolved. Summary line literally true (p. 8 and p. 25). | Earlier check: Re-read in late September 2026: NSDA pp. 8, 23, 25, 49 and 52 (all quotes exact), the web summary and the August 2025 post. New in this check: page 49 calls 750°C the 'maximum operating temperature' for the vessel creep check, and page 23 sets 650°C as the maximum normal fuel operating temperature. Added: using the higher temperature for the creep check is conservative for the vessel. | Revised before publication (late September 2026): source title parenthetical now 'not listed in Valar's library'; verification wording updated ('summary line').
unresolvedsafety

Emergency planning: Valar asked for on-site only, cited state-DOE agreements and drills; none found in public records

disc-010

What was said

What the record shows

The gap: Valar asked DOE to require only on-site emergency response and told DOE that state-DOE notification agreements and local drills would back it up. No DOE decision on the request, state-DOE agreement, emergency plan or drill record was found in public records as of late September 2026. The State Fire Marshal declined to review the reactor building's fire plans; by March 2026 the county fire district's minutes said the issue had been addressed with the chiefs and was not currently a concern. The paper's justification (p.54) calls boundary doses under 0.5 rem well below EPA's Protective Action Guides. EPA's guide for sheltering or evacuation starts at 1 rem over four days, a factor of 2, and the paper does not address EPA's 5 rem child-thyroid guide for potassium iodide, although it names iodine-131 as the main dose contributor.
In plain termsNuclear plants normally plan how to warn and, if needed, move people nearby; Valar's paper calls that 'off-site evacuation planning.' Valar asked DOE to require planning only inside its own site, arguing that even its worst case stays small beyond the fence. It told DOE that Utah already has agreements with DOE for notifying people and that it would run drills with Emery County responders. No such agreement, no emergency plan and no drill record could be found in public records. The state fire marshal's office declined to review the building's fire plans (by March 2026 the county fire district said the issue had been addressed and was not currently a concern), and in June the local ambulance was available 13% of the time. Plans may exist that were not found in public records; records requests could show it.

Why it matters: If something goes wrong, neighbors and first responders depend on plans that no public record shows exist.

What would settle it: FOIA to DOE Idaho Operations Office for the approved emergency management program and DOE's decision on the on-site-only request; GRAMA to Emery County Emergency Management, the Emery County Fire Protection District and the Sheriff for plans, agreements and exercise records; GRAMA to Utah DEQ and the Division of Emergency Management for any DOE notification agreement.

facts safe-016, loc-018, loc-008, safe-029 · checked 2026-10-02: Checked for fairness to Valar, late September 2026: looked for any DOE decision, state-DOE agreement, emergency plan or drill record in the NSDA, NSDA web summary, CX, DOE releases, county and fire-district minutes; none found. The NSDA's page-20 rule dates any decision to before the DSA; the web summary's approved list omits emergency planning, which is consistent either with DOE refusing the request (full DOE emergency order applies) or with a decision that was not found in public records. Absence is 'none found', not proof none exists. Status stays unresolved; summary line literally true. | Earlier check: Re-read in late September 2026: NSDA pp. 20-21, 45, 54 (quotes exact), NIA review, fire district minutes of 17 Nov 2025 and 17 Feb 2026, Orangeville 9 July 2026 minutes, NIRS comments. Absence is 'none found', not proof none exists. | Revised before publication (late September 2026): gap adds EPA's sheltering-or-evacuation guide (1 rem, a factor of 2) and the unaddressed 5 rem child-thyroid guide. | Revised before publication (late September 2026): verification wording updated.
unresolvedregulatory

DOE confirms Ward 250 is authorized and that a federal readiness review took place, but each approval's date is known from Valar's word; the paper it said DOE approved was marked 'In Review'

disc-022

What was said

What the record shows

The gap: DOE confirmed Ward 250 was a DOE-authorized reactor when it went critical. DOE's Office of Environmental Management confirmed on 14 July 2026 that its staff took part in the federal readiness review for the four pilot reactors, naming Ward 250, and that reviewers prepared a final report with a recommendation to the startup authority (dir-031). The dates of the individual steps the public hears about (safety agreement, quality program, safety analyses, readiness review), the 'Certificate of Readiness' and graduation from Joint Test Group oversight are known only from Valar or officials relaying Valar. The review's findings for Ward 250 were not found in public records as of 30 September 2026. The safety-agreement approval Valar announced on 13 October 2025 appears as 'In Review' in the document it linked, and a trade round-up a month later did not count it; a status field not updated in a PDF made the same day is a plausible simple explanation. The table's own 45-day review would have run to 6 November 2025, 24 days after the 13 October post. The quality program has no approval signature page, and its Valar Atomics President approver is not one of the nine roles its organization section defines.
In plain termsBefore a DOE test reactor starts, DOE is supposed to approve a chain of safety papers and then sign off on startup. DOE has confirmed the end result: it calls Ward 250 a 'DOE authorized reactor.' DOE has also said, in July 2026, that federal teams carried out readiness reviews of Ward 250 and three other test reactors before startup. What was not found in public records is DOE's own record of the individual approvals and their dates; those are known only because Valar, or officials repeating Valar, said so. When Valar announced that DOE had approved its first safety paper, the paper itself was marked 'Draft' and 'In Review,' and a nuclear trade publication a month later listed approvals for two other companies but not Valar. That may just be an out-of-date label and a trade paper that missed it. No public copy of DOE's approval letters, readiness report or startup approval was found, so the individual steps cannot be checked.

Why it matters: A reactor's legitimacy rests on these approvals; the staff memo in the state Trust Lands board's packet cited them for its vote approving Valar's Carbon County lease.

What would settle it: FOIA to DOE Idaho Operations Office and DOE-NE for the NSDA, QAPD, PDSA and DSA approval letters, DOE's Safety Evaluation Report, the readiness assessment report, the startup approval (and any delegation of the Secretary's authority), and the Joint Test Group records.

facts safe-007, gov-013, dir-031 · checked 2026-10-02: Checked for fairness to Valar, late September 2026: DOE's 18 June 2026 release confirms Ward 250 is 'DOE authorized' (the earlier title 'every DOE approval is known from Valar's word' overstated). Individual approvals and dates still rest on Valar; the 'In Review' status and ANS's November count are unexplained but have a plausible simple reading. Status stays unresolved; summary line literally true (web post 'has approved'; PDF Table 7 'In Review'). | Earlier check: Re-read in late September 2026: NSDA and QA web summaries, NSDA cover and Table 7, ANS 14 Nov 2025 (quote exact), QAPD, Castle Country, By the Numbers, TLA September memo, Energy Research Board minutes of 13 Aug 2025 and 13 May 2026, DOE selection release, DOE-STD-1271, POWER. Status unresolved: a quick DOE approval is possible under the 45-day standard. | Revised before publication (late September 2026): gap adds the 45-day review end (6 Nov 2025) and the quality program's approver role. | Revised before publication (late September 2026): source title parenthetical now 'not listed in Valar's library'; verification wording updated ('summary line'). Revised before publication (2026-10-01): wording made more exact against the cited records.
unresolvedpublic process

Officials praised Valar as open and 'not hiding anything', citing its public education; Carbon County's agendas and minutes read did not name the site

disc-031

What was said

What the record shows

The gap: Officials described Valar as open and hiding nothing. Their words can fairly be read as praise of Valar's public education and its openness with the county and the board, which the record supports (the county worked with Valar from early on and wrote a support letter in June; Valar held an open house about its operations at the San Rafael Energy Lab, took part in the workshops, and told the county commission on 19 August that it had an open-door policy and planned a town hall in Price). What the record also shows is that the county's agendas and minutes read did not name the site or the support letter, the notices named no applicant or use, no public notice of the committee meetings was found, and the outreach cited was general nuclear education. Whether those meetings had to be noticed, and how the letter was approved, are legal and records questions not answered by any record read. The board chair's words come from an auto-generated transcript.
In plain termsAt the state land board, Carbon County Commissioner Jared Haddock praised Valar for 'not hiding anything,' trustees thanked it for open communication, and the board chair said the trust would help 'speak with one voice' and work 'to make sure that this proposal is approved and that all the parties are satisfied'. Read generously, the officials meant Valar had been open with them and willing to talk with the public, and the record supports that: the county had worked with Valar for over a year, and Valar held an open house and told the county commission in August that it had an open-door policy. But the hearings were in Salt Lake City, with online attendance possible (mine-014). The county's own public agendas never mentioned the Wellington site or the commissioners' letter of support; the public notices left out Valar's name and the word nuclear; no public notice was found for the committee meetings where the deal was shaped; and the workshops counted as outreach were general classes about nuclear power. Whether any rule required more is a legal question the records do not answer.

Why it matters: Residents can weigh in only on what is noticed; whether the committee meetings or the support letter required notice is a legal question the records read do not answer.

What would settle it: GRAMA to Carbon County for how the 29 June 2026 support letter was approved and all correspondence with Valar and Trust Lands about Section 16; GRAMA to Trust Lands for the committee meetings' notices, minutes and recordings and its position on whether they are public bodies.

facts ppl-020, csite-017, mine-013, mine-014, csite-026, csite-005 · checked 2026-10-02: Checked in late September 2026: read the officials' praise as openness toward officials (supported: county support letter, early work with Valar), noted that the chair's words are auto-transcribed, and that notice duties for the committees and the letter are unresolved legal questions. Moved from documented conflict to unresolved: a plausible simple reading of the officials' words exists; the public-notice facts remain as recorded. Summary line literally true (20 Aug transcript; agenda sweep csite-026/mine-013). | Re-read in late September 2026: 20 Aug auto-transcript (quotes exact), 20 Aug approved minutes, TLA September memo (workshops; committee request), RDCC record, ETV legal notices. The Carbon agenda sweep rests on csite-026 and mine-013 (re-verified by those passes today). The chair's words come from an auto-generated transcript. | Corrected in late September 2026: why-it-matters restated as the open legal question; title, gap and summary line state the agenda absence as what the records read show.
unresolvedsite

A Notice of Location names Valar as locator of a lode claim where the only nearby mineral records are gravel pits and a CO2 field; its survey tie points elsewhere

disc-003

What was said

  • Valar Atomics Inc (Notice of Location, RW 453 lode claim) (2026-09-12): Locates the 'RW 453' lode mining claim in the NW and NE quarters of Section 28, T14S R11E, Carbon County, on 12 September 2026, about 1,500 by 600 feet, giving a Torrance, California address.

What the record shows

The gap: A lode claim asserts a discovered vein. The public mineral records for the area show only gravel, which cannot be claimed, and a gas obtained by lease. Most of the claimed quarter-sections are private surface, and the notice's survey tie points outside the section it names. In Valar's favor: a claimant can know of a mineral showing that public databases do not list, and the survey tie may be a clerical error; the county and BLM filings due in October and December will state what is claimed. What vein Valar found, if any, and what the claim is for, are not in any record read.
In plain termsTo stake a lode mining claim in Utah you must first have found a mineral vein. A lode claim notice names Valar Atomics as the locator of a claim about two miles south of the Carbon County site the state approved leasing to Valar. The state's mineral records for that area list only road-gravel pits and carbon dioxide, neither of which can be held by a mining claim. Much of the land in those quarter-sections is private, and the notice's own survey measurement points about two miles away from the section it names. Maybe Valar found something the records do not show, or the tie is a simple error; no statement from Valar about the claim was found in public records read to late September 2026. Under 30 U.S.C. 612 an unpatented claim may be used only for prospecting, mining or processing and uses reasonably incident to them. What mineral RW 453 is for is not stated in any record found; the recorded notices will show it.

Why it matters: Mining claims on federal land may be used only for prospecting, mining or processing and uses reasonably incident to them (30 U.S.C. 612); the county and BLM filings due in October and December will show what RW 453 claims.

What would settle it: The recorded RW location notices at the Carbon County Recorder (due by about 12 October 2026); BLM recordation (due by about 11 December 2026) and any 43 CFR 3809 notice; BLM's Master Title Plat for Section 28; a request to BLM's Price Field Office to examine the claims' validity; ask Valar what mineral it claims.

facts mine-453, dir-001, dir-003, dir-004, dir-005, mine-022 · checked 2026-10-02: Checked for fairness to Valar, late September 2026: no Valar statement about the RW claims was found on its site or in any record read; the simplest readings (unlisted mineral showing; clerical survey-tie error) are plausible and unproven until the recorded notices appear. Status stays unresolved; summary line literally true of the state mineral records as checked 28-30 Sept 2026 (dir-003). | Earlier check: earlier entry kept and extended in late September 2026 with the survey-tie and land-status findings (dir-001). Re-read in that check: Utah Code 40-1 (40-1-1 and 40-1-4 quotes exact), 30 U.S.C. 611 and 612, 43 CFR 3833.11. The mineral, parcel and PLSS figures rest on the state's layers as checked in late September 2026 (not re-checked). Status unresolved until the filings say what mineral is claimed. | Revised before publication (late September 2026): title attributes the claim to the Notice of Location; plain: lease wording now 'approved leasing'; plain and why-it-matters restated as what the law allows and what the filings will show; lease wording restated; verification wording updated ('summary line'). Revised before publication (2026-09-30): reworded the title; reworded the summary line; reworded a record statement; The State's map layer cited here (Utah Geospatial Resource Center, hosted on ArcGIS Online) was checked in late September 2026; no copy of it is kept, and the figures rest on the cited layer as it stood then.
claim holds uptimeline

Criticality before July 4, 2026, as promised: it happened June 18, the only one of four pilot criticalities by July 4 outside a national lab

disc-044

What was said

What the record shows

The gap: None. The promised criticality came on 18 June 2026, ahead of the 4 July goal and of Valar's own 30 June target. What was achieved was a zero-power criticality; full power and electricity rest on Valar's account.
In plain termsValar promised DOE, Emery County and investors that its reactor would go critical, meaning start a self-sustaining chain reaction, before July 4, 2026. DOE confirms it did, on June 18, and that it was the first DOE-authorized reactor built outside a national laboratory. That was a real engineering milestone reached on an aggressive schedule. It was a zero-power test; the later power claims are separate entries.

Why it matters: Fairness: the central promise to the public and investors was kept.

What would settle it: Settled by DOE's release.

facts orig-006, orig-010 · checked 2026-10-02: Checked for fairness to Valar, late September 2026: Also checked from the critics' side: DOE's release confirms the 18 June criticality; Valar's own stricter May target (power operations) rests on Valar's account. Holds. Summary line literally true and fair. | Earlier check: Re-read in late September 2026: August 2025 post (quote exact), July 2025 slide 6 (image), NSDA Table 7, DOE release, DOE fact sheet. | Revised before publication (late September 2026): verification wording updated ('summary line').
claim holds uppublic process

'Our doors remain open through tours, town halls and straight answers': in Emery County, the record bears it out

disc-050

What was said

What the record shows

  • Emery County records show at least 15 Valar public appearances: a July 2025 town hall, open houses in February and September 2026, and repeated reports to the county commission, the Orangeville, Castle Dale and Ferron councils, the utility district and a chamber tour; Emery County's land-sale notice named Valar, and Valar spoke at the hearing.
    Ferron City Council Minutes, April 15, 2026 (scanned) (Ferron City (Utah Public Notice Website), 2026-04-15)
  • Orangeville's minutes record, in the mayor's report, 'For us as a city Valor has been very transparent about what is going on.'
    July 9, 2026 City Council Meeting Minutes (Orangeville) (Orangeville City (Utah Public Notice Website), 2026-07-09)
  • The limit: in Carbon County, no appearance record names the Wellington site before the state vote, and a Carbon County town hall in Price, announced for late September or early October (csite-026, loc-001), was held on 29 September 2026, after the state vote (ETV News, 30 September 2026).
    Aug 19, 2026 Commission Meeting Minutes (Carbon County Board of Commissioners; scanned) (Carbon County Commission (Utah Public Notice Website), 2026-08-19)
The gap: None for Emery County: Valar went before local bodies often and opened its site. This finding does not extend to the Carbon County site (csite-026), and minutes are summaries, so how complete the answers were cannot be judged.
In plain termsIn Emery County, where the reactor sits, Valar did what it says: it held a town hall, opened its site to hundreds of visitors, and reported to city councils, the county and the water district again and again, and the mayor's report in Orangeville's council minutes called it 'very transparent.' That record deserves credit. Meeting minutes are summaries, so they cannot show how complete each answer was. In Carbon County, no county commission agenda or minutes found name the Wellington site before the state approved the lease; that is a separate entry.

Why it matters: Fairness: the company's engagement in Emery is real and on the record.

What would settle it: Settled by the local minutes; the Carbon side remains open.

checked 2026-10-02: Checked for fairness to Valar, late September 2026: Re-checked: the Emery record of repeated public appearances and the remark in the Orangeville mayor's report stand; the limit (Carbon County) is stated. Holds for Emery County. Summary line literally true. | Earlier check: Re-read in late September 2026: Castle Country (quote exact), Ferron 15 Apr and Orangeville 9 July minutes (quote exact), Carbon 19 Aug minutes; the count of appearances rests on a separate record. | Revised before publication (late September 2026): verification wording updated ('summary line').
claim holds uppeople

A Carbon commissioner told the state board no coal has been mined in Carbon County for about four years: it holds

disc-049

What was said

What the record shows

  • Utah Geological Survey's coal production by mine, 2002-2024: Carbon County mines (Dugout Canyon, West Ridge, Horizon) show no output after 2019, 2015 and 2012; Skyline output was last assigned to Carbon in 2018 (mine-039).
    Table 2.8 Coal Production in Utah by Coal Mine, 2002-2024 (Utah Geological Survey, 2025)
The gap: None: the state's production figures support the commissioner's statement; they show no Carbon County output in 2020 through 2024, the latest year reported (mine-039), so if anything the period is longer than four years. (The board chair's remark that this was the 'first year in history' with none does not hold: the state's figures show none in 2020 through 2024 as well.)
In plain termsCommissioner Jensen told the state board that Carbon County has produced no coal for about four years, which is why the county wants new industry. The state geological survey's production figures agree: no coal was produced in Carbon County after 2019, through 2024, the latest year reported. Commissioner Jensen gave this loss as a reason the commission supports Valar.

Why it matters: Fairness: an official's factual claim that checks out, and the reason local officials back the project.

What would settle it: Settled by the state table.

facts mine-039 · checked 2026-10-02: Re-read in late September 2026: the 17 Sept 2026 board meeting auto-transcript (quote exact) and UGS Table 2.8 (the current copy), which shows no Carbon County coal output after 2019. Holds.