VALAR WATCH
Key findingsTheir claims, annotatedEvidenceTake action
374 facts · 512 sources · updated 2026-09-30

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 10 · claim not supported 2 · unresolved 34 · claim holds up 10

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: Valar's only public safety paper for Ward 250 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 HALEU of up to 19.9% U-235 for use in Ward 250. A reading favourable 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.
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 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 the later analysis is not public 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, orig-009, orig-034, orig-040, safe-010, safe-011, dir-009, plan-014, csite-007, safe-025, orig-033 · checked 2026-09-29: Defence pass 2026-09-29: Defended from Valar's side: 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 verify pass: Re-read on 2026-09-29 (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 from the seeded entry: 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. | Correction 2026-09-29 (calculation audit): 'Against that reading' record no longer infers the HALEU fuel existed on 13 Oct 2025; states the 30-day interval instead. | Correction 2026-09-29 (wording review): 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'). Correction 2026-09-30 (source objectivity review): reworded why it matters; reworded the plain-language text; reworded the summary line; reworded the gap.
documented conflictsafety 'No dose at the site boundary', said the state lab director; Valar's own worst case gives a small dose there, judged against non-zero guideline figures
disc-009

What was said

What the record shows

The gap: The state lab's director told local readers that companies must show no dose at the site boundary in an accident and that the public would 'never see a dose of radiation above background'. Valar's own worst-case analysis, deliberately extreme, gives an upper bound at the 400 m boundary of 100 millirem (with an earlier, looser preliminary bound of 0.5 rem) and judges it against a 25 rem evaluation guideline and a 1 rem figure the paper labels USNRC NPUF (the NRC's emergency-planning-zone test for research reactors it licenses), not zero. The small size of the dose is not in dispute; the stated requirement and the 'no dose' description are. Our check: the 400 m dispersion factor behind the 100 millirem is 3.1 to 12.3 times lower than standard rural methods give; rescaled, the bound would be about 0.31 to 1.23 rem, still far below 25 rem.
In plain termsIn a worst-case accident, Valar's own paper estimates that someone at the edge of the site would get less than 100 millirem of radiation, about one year of the natural background everyone in central Utah already receives. The scenario is built to be extreme; the paper says it 'substantially exceeds any realistic release scenario.' That is small, and far under the figures the paper measures it against (a 25 rem evaluation guideline, and a 1 rem figure the paper labels USNRC NPUF, the NRC's emergency-planning-zone test for research reactors it licenses). But the state lab's director told local readers that companies are required to show 'no dose' at the boundary, and that the public would never get a dose above background. That is not the rule the paper follows and not what its numbers say. Whether he meant routine operation or a different standard is not in the record.

Why it matters: Public statements from the officials hosting the reactor should match the numbers in its safety paper; the looser figure is the one the paper uses to justify on-site-only emergency planning.

What would settle it: The final boundary dose in the approved DSA (FOIA to DOE Idaho Operations Office); GRAMA to the Utah Office of Energy Development for any USREL requirement of 'no dose' at the fence.

facts safe-013, safe-015, loc-035, safe-016 · checked 2026-09-29: Defence pass 2026-09-29: Defended: re-read ETV 10 Oct 2025 (the director's words are explicit: 'during an accident event' and 'above background'), NSDA pp. 11, 14, 32-38, 54. The earlier 'stated two ways' point was withdrawn: <0.5 rem and <100 mrem are both upper bounds and consistent, and the looser one is the cautious choice for the emergency-planning argument. The conflict between the official's description of the requirement and the paper survives. Summary line rewritten to the paper's exact bound ('<1 mSv (100 mrem)'). | Earlier verify pass: Re-read on 2026-09-29: ETV 10 Oct 2025 (quotes exact), NSDA pp. 11, 32, 37-38, 54, CX p. 5. The director's words rest on one news report. | Correction 2026-09-29 (calculation audit): Table 4's 1 rem now labelled 'USNRC NPUF' and matched to the NRC EPZ test (10 CFR 50.33(g)(2)); 'still air' now light wind in stable air; gap adds the 400 m dispersion-factor check. | Correction 2026-09-29 (wording review): the 25 rem and 1 rem figures are no longer called limits; the director's reported words and the paper's figures are set side by side; verification wording updated ('summary line').
documented conflictsafety DOE's review: 'No major emission sources' within 10 miles (a coal plant is about 6 away); it names only a fault 150 km off (another zone is about 15)
disc-012

What was said

What the record shows

The gap: DOE's statement that no major emission source lies within 10 miles is contradicted by the state's power-plant data, which place the Hunter coal plant about 6 miles away; the sentence sits in the air-quality section and does not change the radiological analysis. On faults, DOE's statement that none lies at or next to the site holds; naming only the Wasatch Fault, about 150 km away, leaves out the Joes Valley fault zone about 15 km away with young strands, an omission rather than a false statement. Valar's paper calls its earthquake values preliminary pending site studies; its page-13 wording describes the method and is not a contradiction.
In plain termsUnder its categorical exclusion, which does not require a full environmental study, DOE wrote a short review of the site. It says there is no major pollution source within 10 miles; the state's data put the Hunter coal plant about 6 miles away. That sentence concerns the area's background air, not the reactor's safety math. On earthquakes, the review correctly says no fault runs under or right beside the site, but the only fault it names is the Wasatch, about 95 miles away; it leaves out the Joes Valley fault zone about 9 miles away, parts of which moved in the last 15,000 years. None of this shows the reactor is unsafe in an earthquake. It shows a public review with one statement the state's data contradict and one notable omission.

Why it matters: A categorical exclusion rests on DOE's finding that the site has no extraordinary circumstances; missing a nearby young fault is the kind of fact that review is meant to weigh.

What would settle it: The site-specific seismic study and final earthquake parameters in the approved DSA (FOIA to DOE Idaho Operations Office); the CX file DOE-ID-26-005 including Valar's environmental checklist (FOIA).

facts safe-021, safe-022 · checked 2026-09-29: Defence pass 2026-09-29: Defended: re-read CX pp. 2-3 (the emission sentence is in the air-quality section; 'at or adjacent to site' holds) and NSDA pp. 13, 40-41 (method statement vs preliminary values: consistent). The earlier 'site data vs generic values' point and the airport point ('nearby' is a judgment) are withdrawn as conflicts. The emission-source sentence still conflicts with the state's power-plant layer (safe-022; the UGRC host answered 403 to robots.txt today, so it was not re-queried here). Summary line rewritten to quote the CX sentence exactly and state the distance from safe-022. | Earlier verify pass: Re-read on 2026-09-29: CX pp. 2-3 (quotes exact), NSDA pp. 13, 40-41. The UGS fault query was re-run in this pass (14.7-19.0 km; ages '<15,000' for four strands). The power-plant and airport distances rest on the safety pass (safe-021, safe-022); the UGRC services1 host's robots.txt answered 403, so it was not re-queried here. Synthesis check 2026-09-29: this entry gives the nearest Joes Valley strand as 14.7 km and safe-021 as 14.8 km, from the same day's query against a reference point good to about 2 km; the difference is rounding, and 'about 15 km' is used in plain text. | Correction 2026-09-29 (wording review): wording restated; verification wording updated ('summary line'). Correction 2026-10-01 (precision review): wording made more exact against the cited records.
documented conflictregulatory Who oversees the reactor: the governor spoke of the NRC and the state lab's FAQ still promises NRC licenses; the record, and Valar's own papers, say DOE alone
disc-021

What was said

What the record shows

The gap: Valar's own papers say DOE alone, and its staff's 'license' and 'permits' refer to the DOE authorization, as its safety paper's 'License limit' does. The statements that do not match the record are the state's: the governor, as KUTV reported in May 2025, spoke of NRC oversight, and the state lab's live FAQ, which names Valar and was last edited in November 2025, still promises NRC Part 50 licensing and NRC-tested operators. Its references to steam and containment suggest generic text never updated; that explains it but does not correct it.
In plain termsThere are two federal routes for a reactor. The Nuclear Regulatory Commission licenses reactors through a public process with hearings and tests their operators. DOE can authorize test reactors itself, faster and without public hearings. Ward 250 took the DOE route: no NRC license, none planned, and operators trained to an industry standard rather than licensed by the NRC (Valar's quality program still calls them licensed, apparently meaning qualified under DOE's authorization), and Valar's own papers say so plainly. The mismatch is on the state's side. In 2025 the governor told a TV reporter that working with the NRC would keep the project safe, and the state lab's website, which mentions Valar by name, still tells the public the reactor will get NRC licensing and NRC-licensed operators. The page looks like old, generic text nobody updated. But it is what residents who look it up are told today.

Why it matters: People judge a reactor's safety partly by who checks it; several public statements named a regulator that has no role on the record.

What would settle it: GRAMA to the Governor's Office and OED for briefing materials on Valar before May 2025; GRAMA to OED for the lab FAQ's drafting history; ask OED to correct the FAQ; FOIA to the NRC for any record of engagement with Valar.

facts orig-065, gov-012, gov-026, safe-001, safe-017, safe-008, gov-011 · checked 2026-09-29: Defence pass 2026-09-29: Defended: Valar's papers (NSDA pp. 2, 25, 52 'License limit'; web summary 'under DOE jurisdiction') are consistent with the record, so Valar's 'licensed' is not a misstatement. Re-read the lab FAQ: it names Valar in its spent-fuel answer and describes steam/containment (generic LWR text); last modified 19 Nov 2025 per gov-026. That corrects gov-026's 'does not name the reactor' (government.json not edited here; logged). The governor's words rest on KUTV's paraphrase. Conflict survives for the state's statements. Summary line literally true of the KUTV report and the record. | Earlier verify pass: Re-read on 2026-09-29: KUTV (page dated 28 May 2025; the governor's NRC remark is KUTV's paraphrase, the only report found), UIJP, lab FAQ (quotes exact), By the Numbers, ETV Price council, NSDA pp. 2 and 54, EO 14301, CX, OED MOU (page image) and the July 2025 slides (image). The FAQ does not name the reactor and was first published in September 2024; stated fairly. | Correction 2026-09-29 (calculation audit): added that the quality program (pp.9-10) still calls operators licensed. | Correction 2026-09-29 (wording review): source title parenthetical now 'not listed in Valar's library'; verification wording updated ('summary line').
documented conflicttechnical State documents: 'full-power' criticality on 18 June and full power on 21 June; DOE and Valar itself describe 18 June as a zero-power test
disc-024

What was said

What the record shows

The gap: The state lab's page says Ward 250 achieved 'full-power' criticality on 18 June, which DOE's release and Valar's own page contradict: 18 June was a zero-power test. The Trust Lands memo's 21 June full-power date is possible but unconfirmed: Valar announced 10 kW on 22 June (ANS) and said on 24 June it had reached full power, and an announcement can trail the event. No DOE or independent record of the power reached has been published; the state board had the 21 June date in its packet when it voted.
In plain terms'Criticality' only means the chain reaction sustains itself; a reactor can be critical at almost zero power, and DOE and Valar both describe Ward 250's 18 June milestone that way. The state lab's web page instead calls it 'full-power' criticality, which is wrong. The state land board's memo says full power came on 21 June. Valar announced reaching 10 kilowatts on 22 June and told Price City Council on 24 June that it had reached its 100-kilowatt limit, so full power came somewhere around then; announcements can trail events, so 21 June may be right, but no DOE or outside record shows it. The issue here is state paperwork repeating, and in one case overstating, company milestones, not a Valar claim.

Why it matters: State agencies are repeating performance claims as fact in documents that officials rely on to make decisions.

What would settle it: FOIA to DOE Idaho Operations Office for the power-ascension approvals, hold-point records and operating logs; GRAMA to Trust Lands for the application materials that supplied the 21 June date; ask OED to correct its lab page.

facts mine-016, plan-009, plan-006, plan-007, orig-012, orig-013, ppl-026, safe-020 · checked 2026-09-29: Defence pass 2026-09-29: Defended: Castle Country ('completed zero-power testing'; full power 'days later'), POWER (Valar's 18 June statement: 'begun non-commercial power ascension'), ANS (10 kW announced 22 June; the date reached is not given), ETV Price (full power by 24 June), lab page ('full-power fueled criticality'; 'configured for power operations'). Valar is cleared of the 18 June claim; the state page's error survives; the 21 June date is left unproven. Summary line rewritten: the old line set a memo date against an announcement that may lag; the new one quotes the lab page and DOE/Valar exactly. | Earlier verify pass: Re-read on 2026-09-29: TLA September memo p. 18 (quote exact; the memo does not say who supplied the date), lab page (still says 'full-power fueled criticality'), ETV Price council, Castle Country, Series B, DOE release and fact sheet, UIPA update, ANS; chart per plan-007. | Correction 2026-09-29 (wording review): 'inflating' now 'overstating'; state-page inference restated neutrally; verification wording updated ('summary line').
documented conflictpublic_process Carbon site: first public record tying Valar to Section 16 is the 10 Aug 2026 agenda; Valar's April 'open with all plans' was said at the Emery parcel hearing
disc-029

What was said

What the record shows

The gap: Valar promised openness about all its plans and describes an open-door policy. The public record shows the Carbon site mapped two days after that promise, noticed in April and July without Valar's name or any nuclear use, first tied to Valar on an agenda of 10 August, not recorded in the minutes of Valar's 19 August presentation to the Carbon County Commission, and not named on any Valar page. In Valar's favour: the promise was made to Emery residents about the Emery parcel, the notices were the state's to write, Valar answered questions at the state board's public meetings, and minutes summarize. None of that put the site, the company and the nuclear use together in public before 10 August.
In plain termsOn 7 April Valar promised Emery County residents it would be open with all its plans. Two days later the state drew up the lease map for Valar's site north of Wellington. The public notices that followed, in April and July, never said who wanted the land or that it was for nuclear use; those notices were written by the state, not Valar. Valar's name first appeared with the site on a state agenda on 10 August. On 19 August Valar told the Carbon County Commission about its open-door policy, and the minutes do not mention the Wellington site (minutes are summaries; the recording would settle it). Valar did answer questions at the state board's public meetings in August and September. People had heard since 2025 that Valar might build something in Carbon County; what they did not have until August was this site, this lease and the word 'nuclear' together.

Why it matters: Residents cannot comment on, bid against or object to a project they are not told about; the state approved the lease before local news reported it.

What would settle it: GRAMA to Trust Lands for the SULA 2095 application (received date), notice file and correspondence with Valar; GRAMA to Carbon County for the 19 August 2026 audio and all correspondence with Valar about Section 16; ask Valar when it chose the Wellington site.

facts csite-028, csite-018, csite-032, csite-005, csite-026, csite-027, mine-041, mine-048, gov-038, loc-032, loc-034, gov-020, ppl-027, orig-075, fld-001 · checked 2026-09-29: Defence pass 2026-09-29: Defended: the 7 Apr promise's Emery context, the state's authorship of the notices, Valar's appearances at the 20 Aug and 17 Sept board meetings (20 Aug final minutes), and the limits of summary minutes. The conflict survives because no Valar statement named the site between April and the 10 August agenda, and Valar's pages still do not. Summary line literally true (7 Apr minutes; 10 Aug agenda). | Earlier verify pass: Re-read on 2026-09-29: Emery 7 Apr minutes, Carbon 19 Aug minutes (page image; quote exact), Castle Country, By the Numbers, RDCC record 87203 (re-queried), ETV legal notices (Wellington; solar), TLA 10 Aug agenda, ETV 18 Sept, TLA September memo, ETV 10 Oct 2025, Emery 17 June 2025 minutes. A resident's view 'nobody knew' holds for the site and the lease, not for a general Carbon County plan. No intent is asserted. | Correction 2026-09-29 (wording review): title restated with dates and context; verification wording updated ('summary line').
documented conflictpublic_process 'Not trying to keep anything from anyone', said the lab director; the state's MOU with Valar made it confidential
disc-030

What was said

What the record shows

The gap: At the first public hearing on the project, the state's lab director said nothing was being kept from anyone; the state's signed agreement with Valar, then a month old, made the arrangement confidential, required Valar's approval for outside disclosures and barred publicity without consent.
In plain termsAt Emery County's first public hearing on the reactor, the state official who runs the lab told residents transparency was 'imperative' and that nothing was being kept from anyone. 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 other nuclear companies, and it later posted the agreement online; the clause reads like routine business confidentiality. 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 records it withheld or redacted at Valar's request under the MOU, and for Valar's confidentiality designations.

facts gov-011, gov-020, orig-065 · checked 2026-09-29: Defence pass 2026-09-29: Defended: the MOU's GRAMA clause, OED's similar MOUs with other companies (gov-011) and the January 2026 posting are routine-confidentiality points in the state's favour; the groundbreaking release confirms the lab is a unit within OED. The conflict survives narrowly: an absolute statement ('not trying to keep anything from anyone') against a signed confidentiality term then in force. Summary line literally true. | Earlier verify pass: Re-read on 2026-09-29: Emery 17 June 2025 minutes (docx; quote exact; the minutes spell him 'Jaren Wallis'), OED MOU (page image read; clauses 4, 5 and 8 quoted exactly). Residents named in the minutes are not named here. | Correction 2026-09-29 (wording review): why-it-matters restated as the two records side by side; verification wording updated ('summary line').
documented conflictpublic_process Valar's safety agreement commits to state-permit compliance; district minutes record a staff report of a sewer tie-in 'without prior authorization'
disc-020

What was said

What the record shows

  • Castle Valley Special Service District minutes, 19 March 2026: sewer plans 'were not submitted to the State as required'; 'Valar tied into the county sewer system without prior authorization'; water service paused pending state approval; Valar asked for restroom sewer service only, no process water.
    CVSSD Regular Meeting Minutes, March 19, 2026 (approved) (Castle Valley Special Service District, 2026-03-19)
  • The district's later minutes (May, July, August 2026) do not return to it; whether the state permit was issued or the tie-in corrected is not in any record read (loc-015).
    CVSSD Regular Meeting Minutes, March 19, 2026 (approved) (Castle Valley Special Service District, 2026-03-19)
  • The report is one staff member's account ('Jacob also reported') in the district's approved minutes; no Valar response is recorded, and the district's later minutes do not return to it. Valar's request was for restroom sewer service only, with no process water.
    CVSSD Regular Meeting Minutes, March 19, 2026 (approved) (Castle Valley Special Service District, 2026-03-19)
The gap: Valar's safety agreement commits to complying with state permits; the local utility's approved minutes record a staff report that Valar connected to the county sewer before authorization and had not sent its sewer plans to the state as required. The account is a single staff report with no Valar response recorded, and what happened next is not on record.
In plain termsEven a nuclear site needs ordinary permits: water, sewer, fire. Valar's safety paper promises it will comply with state permits. The local water and sewer district's approved minutes record a staff report that in early 2026 Valar 'tied into the county sewer system without prior authorization' and that its sewer plans 'were not submitted to the State as required'. The request was only for restrooms, with no process water, so this is not a radiation issue. No Valar response or later resolution appears in the record read.

Why it matters: Small permits are where local agencies can check a project; the district's minutes record a staff report on this one, and what followed is not in the record read.

What would settle it: GRAMA to the Utah Division of Water Quality for any permit, inspection or correspondence naming Valar Atomics; GRAMA to Castle Valley Special Service District for its Valar file and the unposted April and June 2026 minutes.

facts loc-015, loc-030 · checked 2026-09-29: Defence pass 2026-09-29: Defended: re-read the CVSSD 19 March 2026 minutes (staff report; restroom-only service; site visit with the regional DEQ engineer planned; water withheld until permits in place). No Valar explanation found. The approved minutes are the district's own record, so the conflict survives, stated as a staff report. Summary line literally true. | Earlier verify pass: Re-read on 2026-09-29: NSDA p. 21 and CVSSD 19 March 2026 minutes (quotes exact). The minutes' opening line misdates the meeting to 19 February. | Correction 2026-09-29 (wording review): the sewer tie-in is attributed to the staff report in the approved minutes; what followed is stated as not in the record read; verification wording updated ('summary line').
documented conflictpeople 'The first company ever to take a reactor critical outside a national lab': General Atomics did it in 1958
disc-036

What was said

What the record shows

The gap: The Series B 'first company ever' claim is contradicted by General Atomics' 1958 TRIGA reactor at its own site; the narrower claims DOE and Valar make elsewhere (first DOE-authorized reactor built outside a national lab; first venture-backed criticality) hold. The claim to be the only private company founded since the Manhattan Project to generate nuclear electricity (Carbon minutes, a summary) is contradicted, on Wikipedia's account, by Yankee Atomic Electric (founded 1954, electricity from about 1960); the Series B's narrower 'first time in history a startup generated nuclear power' is not tested by that example.
In plain termsValar's Series B post said it was the first company ever to make a reactor go critical outside a national laboratory. A private company, General Atomics, did that in 1958 at its own site in San Diego. What is true is narrower, and it is DOE's wording: Ward 250 is the first reactor DOE authorized that was built outside a national lab, and Valar's own local web page says it that way. Valar's staff also told Carbon County it is the only private company founded since the Manhattan Project to make nuclear electricity; New England utilities formed a private company in 1954, Yankee Atomic Electric, whose nuclear plant made electricity from about 1960. Public milestone claims should match the record.

Why it matters: Public milestone claims should match the record: the broader wording appears in the Series B post and in a presentation summarized in Carbon County's minutes, and the narrower DOE wording is the one the record supports.

What would settle it: Valar correcting the wording; the OSTI record and DOE's release already settle the first claim; the NRC's historical plant records would settle the second.

facts ppl-030, orig-066, orig-047, mine-033, ppl-026, orig-010 · checked 2026-09-29: Defence pass 2026-09-29: Defended: tested whether the Series B sentence could be read narrowly; Valar's own narrower wordings (NOVA release: 'venture-backed'; Castle Country: 'under the DOE's Reactor Pilot Program') show the narrower limits exist but do not appear in the Series B post. The GA TRIGA counterexample (OSTI abstract) stands. The Carbon wording rests on summary minutes and a secondary source; the 'startup' wording is not contradicted. Conflict survives for the Series B sentence. Summary line literally true. | Earlier verify pass: Re-read on 2026-09-29: Series B (quote exact), Carbon 19 Aug minutes (page image; quote exact), 17 Sept auto-transcript, OSTI TRIGA abstract (quote exact), DOE release, Castle Country. New in this pass: the Yankee Atomic counterexample from Wikipedia (secondary; the minutes summarize the presentation, not verbatim). The Carbon-minutes wording ('generate nuclear electricity') is what the counterexample tests. | Correction 2026-09-29 (wording review): the Series B wording is cited as the Series B post; verification wording updated ('summary line').
documented conflicttimeline 'Just a week later': Valar's own dates put its first electricity 13 days after criticality (two other date gaps have innocent explanations)
disc-040

What was said

What the record shows

The gap: Valar's Series B post says electricity came 'just a week' after criticality; its own website dates the two 13 days apart (18 June and 1 July). The two other mismatches first recorded here have innocent explanations: the '14 days' page is an unfinished draft apparently written in early July, and '09.17.2025' is the date of the joint press release for a groundbreaking held on 11 September.
In plain termsThis is a small slip, not a safety issue. Valar's Series B post says the reactor made electricity 'just a week' after first going critical; its own website dates the two events 13 days apart. Two other date mismatches first listed here turned out to have ordinary explanations: a page counting '14 days' since criticality appears to have been written in early July and left with an earlier date, and Valar's '17 September' groundbreaking is the day the press release went out for a ceremony held on 11 September.

Why it matters: Minor: a company's public timeline should match its own records.

What would settle it: Ward 250's startup log (FOIA to DOE Idaho Operations Office) for the criticality and 1 July dates; the state's groundbreaking records.

facts orig-070, safe-019, plan-005, gov-015, orig-007, orig-067 · checked 2026-09-29: Defence pass 2026-09-29: Defended: ETV and Utah Business (joint release of 17 Sept 2025; 'coincides with the 24th anniversary of 9/11'), By the Numbers ('two weeks'; 'July XX'). Two of the three sub-points withdrawn; 'just a week later' for 13 days (Castle Country: criticality 18 June, first electricity 1 July) has no innocent reading beyond loose wording. Conflict kept, narrowed and labelled minor. Summary line literally true. | Earlier verify pass: Re-read on 2026-09-29: Series B, By the Numbers, Ward 250 page, Castle Country, DOE release, OED 15 Oct 2025 legislative slides (quote exact), Emery 9 Sept 2025 economic board minutes. DOE's 'Today' may describe the announcement rather than the moment; Valar's own Series B and Castle Country also give 18 June. | Correction 2026-09-29 (wording review): 'investor letter' now 'Series B post'; verification wording updated ('summary line').
claim not supportedsafety Spent fuel for five minutes like a CAT scan: no supporting calculation or correction found on Valar's site as of 29 Sept 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 29 September 2026, where the post stands unchanged; since mid-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 29 September 2026.

What would settle it: Valar publishing its calculation or a correction; Site Watch records any change to the post.

facts orig-017, orig-061, safe-026 · checked 2026-09-29: Defence pass 2026-09-29: Defended: re-read the NRC-lawsuit post (the sentence concerns Ward One, 100 kWt, lifetime under a month; no cooling time stated), UIJP (Taylor posted calculations; engineers' 90 s and 85 ms results), TNR ('updated the calcs', via Touran), Mother Jones, Philippine Collegian. No Valar correction or supporting calculation was found on its site. A reported private revision is not a published correction, so 'corrected' does not apply. Status stays claim_unsupported; summary line literally true ('No correction found'). | Earlier verify pass: Re-read on 2026-09-29: the live post (sentence present; meta robots 'noindex, nofollow' confirmed in the page HTML), UIJP, Mother Jones, TNR, NSDA Table 1. The engineers' figures are their analyses as reported, not a regulator's finding. Synthesis check 2026-09-29: one record gave The New Republic's article a 2026-02 date; every other file that read it (ppl-010, ppl-024, ppl-028) dates it 26 May 2026. Corrected. | Correction 2026-09-29 (calculation audit): gap adds the CT-scan dose-rate scale (12-120 mSv/h over five minutes). | Correction 2026-09-29 (wording review): title restated as no correction found; noindex stated with 'who added it and why is not in the record'; 'handle' corrected to 'hold' (as TNR reports it); Mother Jones cited as 'Mother Jones (Kiera Butler), 26 Feb 2026' (narrow quote; headline not repeated); verification wording updated ('summary line'). Correction 2026-09-30 (source objectivity review): reworded the title; reworded the gap; reworded the plain-language text; reworded why it matters; reworded a record statement; removed orig-025 from facts (that item is held pending primary sources); removed ppl-028 from facts (its account of the dispute rests on removed sources); removed the record statement that rested only on The Utah Investigative Journalism Project (with Utah News Dispatch); removed the citation of The Utah Investigative Journalism Project (with Utah News Dispatch) (the piece mocks or attacks people personally); removed the record statement that rested only on Mother Jones; removed the citation of Mother Jones (the piece mocks or attacks people personally); removed the record statement that rested only on The New Republic; removed the citation of The New Republic (the piece mocks or attacks people personally); removed the record statement that rested only on Philippine Collegian; removed the citation of Philippine Collegian (the sentence relied on names no one); now also cites U.S. Energy Information Administration.
claim not supportedtechnical 'Cheap and abundant hydrogen' via a sulfur-iodine process: no hydrogen on record, and the process has never run commercially
disc-037

What was said

What the record shows

The gap: The home page states, in the present tense, that Valar's reactors paired with its sulfur-iodine process produce cheap, abundant hydrogen. It can be read as a description of design intent ('When paired with'), but no hydrogen production is on record, the process has never been deployed commercially (per a Valar investor's own profile), and it needs heat of about 800-1000°C. The only Valar reactor with a public safety paper, the Ward 250 test unit, is limited to 650°C; Valar describes its future designs as hotter, but none has a public safety paper.
In plain termsValar's home page says its reactors, paired with a chemical process called the sulfur-iodine cycle, make cheap and plentiful hydrogen. Read kindly, that describes what the design is meant to do. But no record shows Valar has made any hydrogen, the process has never run commercially anywhere (according even to a Valar investor), and it needs heat of roughly 800 to 1,000°C. Ward 250, the only Valar reactor with a public safety paper, is a test unit limited to 650°C; Valar's future reactors may run hotter, but none has a safety paper yet. The hydrogen plan may come true one day; today it is written as if it already works.

Why it matters: Claims on the company's front page shape what investors, officials and neighbors believe the technology does now.

What would settle it: Valar publishing any hydrogen-production test data, or rewording the page as a goal.

facts orig-063, orig-023, orig-024, orig-006 · checked 2026-09-29: Defence pass 2026-09-29: Defended: read the home-page sentence as design intent ('When paired with'); noted that 650°C is Ward 250's test limit, not a limit on future designs (TechCrunch 2025: up to 900°C, Valar technology generally). No hydrogen production or supporting data found. Status stays claim_unsupported; summary line literally true. | Earlier verify pass: Re-read on 2026-09-29: home page (quote exact), TechCrunch 2025, Initialized blog, Contrary profile (quotes exact), DOE thermochemical page, NSDA pp. 25, 52. | Correction 2026-09-29 (wording review): verification wording updated ('summary line').
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 234.94 g of U-235 in 1.18 kg of uranium. No single enrichment fits both (76 such blocks holding 250 kg would need 7.14%), 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, is not public.
    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. No public document states what is actually in the reactor, or how the safety analysis was adjusted for that core.
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. What is missing is a public statement of what is actually inside the reactor, and of the safety numbers for that core.

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 orig-034, safe-011, mine-033, ppl-026, safe-010 · checked 2026-09-29: Defence pass 2026-09-29: Defended: 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 verify pass: Re-read on 2026-09-29: 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. | Correction 2026-09-29 (calculation audit): summary line says 'fuel elements' (the NSDA's term); record adds the per-element U-235 and heavy-metal comparison. | Correction 2026-09-29 (wording review): 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, matching the 30 MWd limit rather than the 3 MWd analysis.
    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 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 innocent reading is a unit slip (30 days written as 30 megawatt-days); only the approved Technical Safety Requirements, which are not public, 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 and noble-gas dose would rise about 4%; cesium-137 and strontium-90 about tenfold, but still about 4% of the iodine-131 activity. Even scaling the whole 100 millirem bound up tenfold gives 1 rem, far 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 Valar has said '30 days' everywhere else too. 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 rest of the paper 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 longer adds little. Slower-fading materials would keep growing. The approved limits that would settle it are not public.

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-034, orig-035, orig-045, mine-019, safe-013 · checked 2026-09-29: Defence pass 2026-09-29: Defended: 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 (fetched from epa.gov, robots.txt checked; arithmetic: 1 - 0.5^(30/8) = 0.926). Moved from documented_conflict to unresolved: the innocent reading is plausible and the dose effect for the named main contributor is small, but the TSRs are not public. Summary line literally true of p. 25. | Earlier verify pass: Re-read on 2026-09-29: 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. Defend 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. | Correction 2026-09-29 (calculation audit): gap adds our scaled check (iodine and noble-gas dose about +4%; tenfold bound still 1 rem). | Correction 2026-09-29 (wording review): verification wording updated ('summary line').
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 are not public.
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. Still, a safety paper should not contradict its own limit, and the approved limits that would settle it are not public.

Why it matters: Limits tied to material strength are the numbers that should not quietly move; the published draft gives two, and the binding one is not public.

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-034, orig-040, orig-011, orig-006, orig-023, safe-008 · checked 2026-09-29: Defence pass 2026-09-29: Defended: 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 verify pass: Re-read on 2026-09-29: NSDA pp. 8, 23, 25, 49 and 52 (all quotes exact), the web summary and the August 2025 post. New in this pass: 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. Defend note added: using the higher temperature for the creep check is conservative for the vessel. | Correction 2026-09-29 (wording review): source title parenthetical now 'not listed in Valar's library'; verification wording updated ('summary line').
unresolvedtechnical How big is Ward 250? 100 kW day to day; 250 kW for one hour per run (safety paper) or 'up to one day', possibly a total (unfinished Valar page); '5 MW' in airlift news
disc-006

What was said

What the record shows

The gap: The safety paper allows 250 kW for one hour per run; an unfinished, unlisted Valar page from June 2026 says up to one day. Read as a total across runs, the two can fit; read as one continuous day, it is 24 times the paper's limit. Neither says which, and the approved limits are not public. The difference could reflect limits set when DOE approved the final safety analysis in 2026, or an error in a draft page. DOE's description of a '250 kilowatt thermal (kWth)' reactor matches the paper's own '≤250 kWth' rating and is not a conflict, and Valar staff called the 100 kW limit 'full power'. The '5 MW' in airlift coverage appears, as reported, to come from the airlift's federal publicity and the design's planned future size, not from Valar's own words.
In plain termsA reactor's 'size' can mean what it runs at day to day or the most it may reach in a short test. Ward 250's safety paper says 100 kilowatts of heat day to day and 250 kilowatts for no more than an hour per run, and calls it a reactor of 'up to 250' kilowatts; that is why DOE calls it a 250-kilowatt reactor, and why Valar staff call 100 kilowatts 'full power.' Those fit together. Two things may not. An unfinished Valar web page says 250 kilowatts is allowed for up to a day; read as a total across runs, that can fit, but read as one continuous day, it is 24 times the paper's limit. And airlift news called it 5 megawatts, a figure that appears to come from the military's publicity and from the size the design is meant to grow to. The limits DOE actually approved would settle the hour-or-day question; they are not public.

Why it matters: Power and time at power set how much heat and radioactivity the reactor makes; the limits DOE actually approved are not public, and the company's unfinished page and its safety paper give different figures that may or may not conflict.

What would settle it: FOIA to DOE Idaho Operations Office for the Technical Safety Requirements, any approval to exceed 100 kWth, and the Ward 250 operating logs; ask Valar to publish the authorized limits.

facts safe-008, orig-031, orig-035, orig-011, gov-027, orig-030, safe-001 · checked 2026-09-29: Defence pass 2026-09-29: Defended: NSDA exec summary ('≤250 kWth') explains DOE's 250 kWth; ETV Price council (Gardner: 'full 100-kilowatt limit'); ExecutiveGov attributes the 5,000-homes description to 'DOW', and Stripes cites a Pentagon release (war.gov article linked from both refused our reader: robots.txt and page answer 403). The one-day claim is on an unfinished, unlisted draft page. Moved to unresolved: the only surviving difference (hour vs day) has a plausible reading (later-approved limits) that only the non-public TSRs can settle. Summary line literally true (NSDA p. 25; the draft page is online). | Earlier verify pass: Re-read on 2026-09-29: By the Numbers (quotes exact), CX p. 1, NSDA web summary, NSDA pp. 2, 25, 52, ANS, POWER, WNN, Stars and Stripes, ExecutiveGov, Utah lab page. The 5 MW figure in the airlift articles is not attributed to Valar or DOE in the text read; it is recorded as press wording. | Correction 2026-09-29 (calculation audit): gap, plain and summary line now read the paper's hour as per run and the page's day as possibly a total (24 times only if continuous). | Correction 2026-09-29 (wording review): source title parenthetical now 'not listed in Valar's library'; framed as a difference that may or may not be a conflict (per-run hour vs possibly cumulative day); verification wording updated ('summary line').
unresolvedtimeline A 12-month test on paper; a permanent home and '165 years' of fuel in public
disc-007

What was said

What the record shows

The gap: The safety, quality and environmental documents all treat Ward 250 as a one-time mission of about 12 months of operation followed by teardown, and use that short life to justify lighter requirements. Since mid-2026 Valar has described the site, not Ward 250 itself, as permanent and expanding, and its CEO's '165 years' was, in context, an illustration of the fuel's energy content. No public document states when Ward 250 will stop, or whether its short-life assumptions would be revisited if it ran longer.
In plain termsWard 250 got lighter rules partly because it was supposed to run only about a year: the steel vessel's aging check, the inspection plan and the quality program were all sized for 12 months, and DOE used a categorical exclusion, with no full environmental study, for a 'single limited-duration research mission.' Since then Valar has called the site home and 'no longer just a test facility,' and its CEO said the fuel could keep the reactor running 165 years. Read in context, both are about something else: the first describes the whole Utah operation, and '165 years' was a way of showing how much energy is packed into the fuel, most of which the test will never use. But nothing public says when Ward 250 will stop, and if it ran well past a year, the short-life reasoning in its paperwork would no longer fit it.

Why it matters: The lighter requirements were justified by a short mission; a longer life would need them re-examined, and the public has no stated end date to hold anyone to.

What would settle it: FOIA to DOE Idaho Operations Office for the approved DSA's operating-period assumptions and decommissioning chapter, the TSRs and the OTA milestone schedule (DENE0009560, which runs to 4 July 2027); ask DOE-ID's NEPA office whether any successor reactor or extended operation would get a new review.

facts plan-003, orig-034, orig-045, mine-019, safe-009, csite-021, gov-033, fund-017, ppl-006, orig-055, safe-005 · checked 2026-09-29: Defence pass 2026-09-29: Defended: KSL/Deseret context for '165 years' (energy-content passage), CX (<1% of fissile material consumed), 20 Aug transcript context (site, not reactor). No Valar statement of an end date or extension was found. Status stays unresolved; summary line literally true (KSL: 'The fuel inside the Ward250 will let it continue running for 165 years, Taylor said'). | Earlier verify pass: Re-read on 2026-09-29: NSDA pp. 2, 8, 10, 49 (new in this pass: the vessel-aging sentence and the 'Absence of commercial production pressure' factor), NSDA web summary, QAPD, CX, slides (image), KSL, 20 Aug transcript, Castle Country, GOED materials. Status unresolved: a company may stay while a test reactor ends; the gap is the missing end date and review. Synthesis check 2026-09-29: one KSL source was dated 2026-07-01; KSL's page reads 'Posted - July 6, 2026' (re-read 2026-09-29; the event was Wednesday 1 July, and the Deseret News original, cited in orig-042, is dated 1 July). Corrected to 2026-07-06. | Correction 2026-09-29 (calculation audit): 18-month record adds that the NSDA's own schedule already runs about 19.75 months. | Correction 2026-09-29 (wording review): source title parenthetical now 'not listed in Valar's library'; verification wording updated ('summary line'). Correction 2026-10-01 (precision review): wording made more exact against the cited records.
unresolvedsafety The accident math assumes the public stays 400 m away; the lab is 20.6 acres, and officials called the fence buffer enough
disc-008

What was said

What the record shows

The gap: The worst-case analysis in Valar's draft paper assumes no member of the public is closer than 400 m, which it calls 'the nearest point of public access'; no DOE document read sets 400 m as a required boundary, and DOE's approved analysis may use a different one. The reactor's fence encloses about 2 acres of a 20.6-acre state lab, far less than the roughly 124 acres a 400 m circle covers. An access-control agreement, state control of surrounding land, or Valar's purchase of the adjacent 112 acres (which the lab director linked to 'contiguous ownership to maintain safety') may cover the difference; no record read shows any of them in place. Local officials, as reported, told residents the fence line is buffer enough.
In plain termsIn an accident, distance is protection: the farther away people are, the smaller the dose. Valar's worst-case math places the nearest member of the public 400 meters from the reactor. A circle that size covers about 124 acres, but the state lab the reactor sits on is 20.6 acres, and the reactor's fenced area about 2. So the math assumes the public is kept off land outside the lab, and no public record says who does that. Residents who asked about a buffer zone were told, as the local paper reported, that the fence is buffer enough. The land may be controlled by an agreement, or covered by the land next door that Valar is buying; the records read do not say.

Why it matters: If people can stand closer than 400 m, the paper's own numbers show the air concentration, and so the dose, rises steeply (16 times at 100 m).

What would settle it: The site description and public-access control in the approved DSA (FOIA to DOE Idaho Operations Office); GRAMA to the Utah Office of Energy Development for the USREL site plan, Valar's use agreement and any access-control agreements; the Emery County Recorder's deed for parcel 04-0019-0030.

facts safe-014, ppl-021, mine-035, gov-022, loc-035, mine-046 · checked 2026-09-29: Defence pass 2026-09-29: Defended: looked for an access-control arrangement in the NSDA, CX, Emery minutes and the lab pages; the only lead is the lab director's 'contiguous ownership' remark and the pending purchase of parcel 04-0019-0030 (disc-055). Nothing shows who controls public access out to 400 m. Status stays unresolved; summary line literally true. | Earlier verify pass: Re-read on 2026-09-29: NSDA pp. 10, 36-38 (quotes exact), CX pp. 1-2, ETV 9 Apr 2026 and 10 Oct 2025, Emery 7 Apr 2026 minutes (the minutes record a different answer to the buffer question than ETV; both are given). Geometry re-checked. Private residents who asked questions are not named. | Correction 2026-09-29 (calculation audit): claim pages corrected to 10, 11 and 39; dispersion-factor record reworded ('under 5 rem'; chi/Q not a concentration) with the 400 m check added. | Correction 2026-09-29 (wording review): verification wording updated ('summary line'). Correction 2026-10-01 (precision review): wording made more exact against the cited records.
unresolvedsafety Emergency planning: Valar asked for on-site only, cited state-DOE agreements and drills; none found in public
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, no state-DOE agreement, no emergency plan and no drill record are public. The State Fire Marshal declined to review the reactor building's fire plans. The paper's justification (p.54) calls boundary doses under 0.5 rem well below EPA's Protective Action Guides. EPA's lowest guide is 1 rem, 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, and in June the local ambulance was available 13% of the time. Plans may exist that simply are not published; only records requests can 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, safe-034, loc-018, loc-008, safe-005, safe-029 · checked 2026-09-29: Defence pass 2026-09-29: Defended: 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 an unpublished decision. Absence is 'none found', not proof none exists. Status stays unresolved; summary line literally true. | Earlier verify pass: Re-read on 2026-09-29: 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. | Correction 2026-09-29 (calculation audit): gap adds EPA's lowest guide (1 rem, a factor of 2) and the unaddressed 5 rem child-thyroid guide. | Correction 2026-09-29 (wording review): verification wording updated ('summary line').
unresolvedsafety 'Walk-away' cooling: Valar's design target is 72 hours hands-off; DOE's review says 'indefinitely'; neither analysis is public
disc-011

What was said

What the record shows

The gap: Valar's safety paper sets a minimum target of 72 hours with no operator action; DOE's categorical-exclusion review, under which no full environmental study was required, states that the passive system keeps fuel within limits indefinitely. A design can exceed its minimum target, so the two are not in conflict. The stronger 'indefinitely' is not backed by any public analysis, and the 26 June demonstration rests on Valar's account.
In plain terms'Walk-away safe' means that after shutdown the reactor can shed its leftover heat with no pumps, no power and no people. Valar's safety paper sets a minimum target: nobody needs to act for at least 72 hours. DOE's environmental review goes further and says the cooling works 'indefinitely.' Both can be true, because a design can beat its minimum. What is missing is proof the public can see: the heat analysis behind 'indefinitely' is not published, and Valar's 26 June public test of passive cooling has no DOE or outside record.

Why it matters: DOE relied on attributes like this to find the risk of an offsite release low enough for a categorical exclusion.

What would settle it: FOIA to DOE Idaho Operations Office for the approved DSA's decay-heat analysis, the 26 June 2026 test plan and results, the Joint Test Group records and the power history before the test.

facts safe-020, csite-009, csite-020, plan-006 · checked 2026-09-29: Defence pass 2026-09-29: Defended: re-read NSDA pp. 15 and 23 (72 hours is 'target performance'; conduction path 'cannot be disabled') and CX p. 5. A minimum target and an analysed indefinite capability are compatible, so the earlier 'conflict' does not survive; what remains is that neither the decay-heat analysis nor the 26 June test is public. Moved to unresolved; summary line rewritten to state only what the records show. | Earlier verify pass: Re-read on 2026-09-29: CX p. 5, NSDA p. 23, Castle Country, ANS (quotes exact). | Correction 2026-09-29 (wording review): verification wording updated ('summary line'). Correction 2026-10-01 (precision review): wording made more exact against the cited records.
unresolvedsafety Valar promised monitoring data and 'regular environmental reporting' to the state; none has been found in public
disc-051

What was said

What the record shows

The gap: Valar promised monitoring data and regular reports to state environmental agencies and an EPA air-emission evaluation. Three months into operation, none of it is public; the only other public document says no air permits are needed.
In plain termsDOE's review says Ward 250's routine gas releases are negligible, and Valar's own paper promised to back that up with monitoring. Valar's safety paper promised monitoring data and regular reports to Utah's environmental agencies, and an evaluation under EPA's air rule for radioactive emissions. Ward 250 has now been running for three months, and no monitoring result, EPA determination or state report naming it could be found. The reports may exist and simply not be posted; only a records request can show it.

Why it matters: Monitoring is how neighbors would learn whether anything is leaving the site; none of it is public.

What would settle it: FOIA to DOE Idaho Operations Office for Ward 250's environmental monitoring plan, results and any NESHAP (40 CFR 61 Subpart H) determination; FOIA to EPA Region 8; GRAMA to Utah DEQ for any monitoring data or reports received from Valar.

facts safe-024, safe-029 · checked 2026-09-29: Defence pass 2026-09-29: Defended: re-read NSDA p. 21 (reporting runs through DOE-ID and to state agencies, not to the public directly) and CX (gaseous effluents 'negligible'; no Clean Air Act permits). The promise was of reporting to agencies, which may exist unpublished; no monitoring result or report was found in public. Status stays unresolved; summary line literally true ('Reports found in public: none'). | Earlier verify pass: Re-read on 2026-09-29: NSDA pp. 21, 23-24 (quotes exact), CX, NIRS comments. Absence is 'none found', not proof none exists. | Correction 2026-09-29 (calculation audit): claim source page corrected to pp. 21-22. | Correction 2026-09-29 (wording review): verification wording updated ('summary line').
unresolvedsafety Safety case leans on Ward Zero tests; no test data is public, and an unlisted page titled 'Ward Zero Whitepaper' contains no Ward Zero data
disc-013

What was said

What the record shows

The gap: Valar's safety paper credits Ward Zero tests for natural circulation and cavity cooling, and for filing its final safety analysis early. Valar has described the testing publicly only in summary. The data may have gone to DOE with the non-public safety analyses DOE approved, which is a plausible reading, but no test report or DOE review of it is public. The only page titled as a Ward Zero technical paper is an unlisted page whose text matches a 2019 Cairo Review essay by another author; it may be placeholder text (Valar has not said), and it is not a technical account of Ward Zero.
In plain termsWard Zero was Valar's full-size, electrically heated practice reactor in California, and hardware from it was reused in Ward 250. Valar's safety paper leans on Ward Zero's tests for two key points: that the helium will keep circulating by itself if the pumps stop, and that the cooling system around the reactor can carry enough heat away. Valar has described those tests in public only in general terms (months of heat and pressure testing, temperatures above 750°C). DOE may well have seen the data with the safety analyses it approved, but none of it is public. The one page Valar titled 'Ward Zero Whitepaper' contains no Ward Zero information at all: its text matches, word for word, a 2019 magazine essay by another author about reactor exports to the Middle East. The page is not listed in Valar's library and may be leftover placeholder text (Valar has not said), but it is still online.

Why it matters: Key safety credits rest on tests the public cannot see; DOE may have reviewed them, but the record does not show it.

What would settle it: FOIA to DOE Idaho Operations Office for Ward Zero test reports and data submitted with the PDSA and DSA and DOE's review of them; ask Valar to publish the data and explain the whitepaper page.

facts orig-058, orig-059, orig-005, orig-071, safe-018 · checked 2026-09-29: Defence pass 2026-09-29: Defended: Valar's own public descriptions of Ward Zero testing (August 2025 post: 'five months of heat and pressure testing'; By the Numbers draft), POWER on the PDSA/DSA approvals as Valar announced them, and the library listing (whitepaper not listed). No Ward Zero data or DOE review found. Moved from claim_unsupported to unresolved: the claim that tests were done is supported in summary by Valar; whether they show what the safety paper credits is unproven either way. Summary line literally true. | Earlier verify pass: Re-read on 2026-09-29: NSDA pp. 13, 15, 55 and QAPD (quotes exact), slide 7 (viewed as an image), whitepaper page and the Cairo Review essay (Barakah sentence identical in both). 'Placeholder' is an inference, stated as such. | Correction 2026-09-29 (wording review): wording on the unlisted page and the 2019 essay restated; placeholder reading attributed as unconfirmed; source title parenthetical now 'not listed in Valar's library'; verification wording updated ('summary line').
unresolvedsafety Fuel factory: 'largest manufacturer of this fuel', no outside suppliers; record: a pilot line, no public authorization
disc-017

What was said

  • Harry Hansen, Valar public affairs, to the Orangeville City Council (minutes) (2026-06-11): The second building will make Valar's own fuel: "Once completed they will be the largest manufacturer of this fuel in the United States".
    June 11, 2026 City Council Minutes (Orangeville) (Orangeville City (Utah Public Notice Website), 2026-06-11)
  • Isaiah Taylor (Series B post) (2026-08-04): "Valar will not rely on outside suppliers for the fuel needed to deploy and operate."
    Announcing our $1B Series B Led By Sequoia (Isaiah Taylor) (Valar Atomics, 2026-08-04)

What the record shows

The gap: Valar tells local councils and investors it will make its own fuel, at the largest scale in the country. Those are future goals that cannot be tested yet; DOE's own selection of Valar for its fuel-line pilot supports that Valar is building a fuel line. The record shows a pilot uranium-processing line being installed under a quality program sized for a 12-month demonstration, no public safety authorization for it (DOE authorizes such lines, and has published none), and Ward 250's fuel supplied from a federal site.
In plain termsMaking TRISO fuel means handling enriched uranium powder and chemicals, a nuclear operation of its own. Valar told Orangeville its second building will make it the country's largest maker of this fuel, and told investors it will not rely on outside suppliers. Those are promises about the future, and DOE did pick Valar for its program to build such fuel lines, so the plan is real. What the public can see today is a pilot line being set up, according to Valar's own job ads, under paperwork written for a one-year demonstration and designed to stay below DOE's lowest nuclear hazard category. DOE approves fuel lines in its program, but no approval for Valar's has been published, and Ward 250's own fuel came from a federal site in Nevada.

Why it matters: A uranium processing plant beside homes needs its own safety review; none is public, and the plant is described locally as heading for production.

What would settle it: FOIA to DOE Idaho Operations Office and DOE-NE (Fuel Line Pilot Program) for Valar's fuel-line safety design agreement, hazard categorization and authorization; GRAMA to Utah DEQ's Division of Waste Management and Radiation Control for any radioactive-materials license.

facts safe-031, plan-015, loc-016, loc-019, orig-038, orig-070, plan-014 · checked 2026-09-29: Defence pass 2026-09-29: Defended: DOE fuel-line release re-read ('conditional selections'; 'leverage the Department's authorization process'; Valar's project 'for the Ward250 reactor deployment'), QAPD, Greenhouse feed, Orangeville minutes. 'Largest' and 'will not rely on outside suppliers' are future claims; the plan is corroborated by DOE's selection; the authorization gap is the same non-publication seen for Ward 250. Moved from claim_unsupported to unresolved. Summary line literally true. | Earlier verify pass: Re-read on 2026-09-29: Orangeville 11 June 2026 minutes, Series B post, QAPD, the live Greenhouse feed (92 postings; quotes exact), DOE fuel-line release ('conditional selections'), SER. | Correction 2026-09-29 (calculation audit): <HC3 record adds that no inventory or threshold is given, so it cannot be checked. | Correction 2026-09-29 (wording review): verification wording updated ('summary line').
unresolvedsafety Spent fuel to 'a DOE-approved facility' no record names; the state permit Utah law requires was not found
disc-033

What was said

What the record shows

The gap: Where Ward 250's spent core will go, when, and who pays if Valar cannot, are not stated in any record read. The state permit Utah law requires to store it here in the meantime was not found. A federal-state pact cites Ward 250's 'successful permitting', which can fairly mean DOE's authorization, while no state permit appears in the record; and the state lab's FAQ tells residents Valar 'will not produce spent reactor fuel with this reactor', which DOE's own review contradicts in plain terms.
In plain termsWhen Ward 250's test ends, its used fuel stays dangerously radioactive and must go somewhere. DOE's review says it will go in casks to 'a DOE-approved facility,' without saying which one or when. Utah law lets such waste be stored in the state only with a state permit and license, and none naming Valar could be found. Meanwhile, the governor and the Energy Secretary signed a pact that points to Ward 250's 'successful permitting' as the model for a Utah campus that could take other states' spent fuel. The permits on record are DOE's; the state's own permit is not.

Why it matters: Spent fuel is the longest-lasting hazard a reactor leaves; the public has no named destination, date or state permit.

What would settle it: FOIA to DOE Idaho Operations Office for the OTA's waste and decommissioning terms and the spent-fuel disposition plan; GRAMA to Utah DEQ's Division of Waste Management and Radiation Control for any application, permit or license naming Valar under Utah Code 19-3-321.

facts safe-023, csite-023, gov-017, gov-030, gov-032 · checked 2026-09-29: Defence pass 2026-09-29: Defended: 'successful permitting' read as DOE's authorization (fair); DOE's CX does commit to removal and 'No radioactive waste will be left on site'. Added the lab FAQ's 'will not produce spent reactor fuel' statement, found in this pass, beside DOE's 'spent fuel' wording, with its likely meaning. No destination, date or DWMRC permit found. Status stays unresolved; summary line literally true. | Earlier verify pass: Re-read on 2026-09-29: CX pp. 1 and 4 (quotes exact), NSDA p. 9, Hogan Lovells, Utah Code 19-3-321, NLIC MOU page 1 (image; quote exact). 'Successful permitting' can fairly refer to DOE's authorization; the gap is the missing state permit and destination, not the word. | Correction 2026-09-29 (wording review): verification wording updated ('summary line').
unresolvedregulatory Where did the HALEU come from? Pilot rules point to DOE's allocation program; Valar is in none of its announced rounds
disc-018

What was said

What the record shows

The gap: Valar is in none of DOE's three announced HALEU allocation rounds, yet HALEU fuel for Ward 250 was cleared to ship from a federal site, most likely the NOVA fuel Valar says it provided. DOE's own words make its allocation program one route among others ('may apply'). No public record says who fabricated the fuel, who owns the uranium, or on what terms Valar received it.
In plain termsHALEU is scarce; the U.S. has little of it, and DOE hands it out in announced rounds. The pilot program's rules told companies needing HALEU to get into that process. Valar is not on any of the three announced lists, yet DOE cleared HALEU fuel for Ward 250 to ship from a federal nuclear site in Nevada. Valar says it 'provided' the fuel for its Los Alamos test and will make its own in future. The fuel may have come under an agreement that is simply not public; the record does not show whose uranium is in the reactor or on what terms.

Why it matters: Who owns and supplies the uranium decides who is accountable for it; who owns the uranium and on what terms it was supplied are not in the public record.

What would settle it: FOIA to DOE Office of Nuclear Energy (HALEU Availability Program) and NNSA Nevada Field Office for any allocation, loan, lease or sale of HALEU to Valar or for Project NOVA and Ward 250, and the fuel fabricator's identity; FOIA to DOE Savannah River Operations Office for the Model 9979 application.

facts gov-008, gov-032, orig-032, safe-010, plan-014, orig-070 · checked 2026-09-29: Defence pass 2026-09-29: Defended: NOVA ('Valar Atomics provided the reactor core, TRISO fuel'), SER (shipments from NCERC), DOE fuel-line release ('may apply' for HALEU; companies source their own feedstock). The allocation program is optional per DOE; the supplier remains unstated. Status stays unresolved. Summary line rewritten: 'anyway' implied a rule was broken, which DOE's 'may apply' wording does not support. | Earlier verify pass: Re-read on 2026-09-29: Hogan Lovells (quote exact), DOE HALEU rounds 1-3 (no 'Valar' in any), SER, NOVA release, Series B post. A gap in the public record, not evidence of wrongdoing. | Correction 2026-09-29 (wording review): why-it-matters restated as what is not in the public record; verification wording updated ('summary line').
unresolvedsafety State officials vouch for safety at the lab; on 25 Sept the state lab posted a time-limited Safety Manager position (a Radiation Safety Officer is already in place)
disc-053

What was said

What the record shows

The gap: State officials describe Valar as closely supervised and diligent on safety. Under the safety agreement the state can observe but not direct DOE's oversight, and DOE puts reactor safety on the developer. The state lab already has a Radiation Safety Officer; it is now hiring, in a time-limited post, a Safety Manager for its lab-wide program, with radiological experience only 'desirable'. The records do not say whether the post is new or a replacement, or whether state staff fill Valar's radiation-safety role.
In plain termsState officials have told the public and the land board that Valar is under strict supervision and diligent about safety. The supervision of the reactor itself is DOE's job, and DOE says the company is responsible for the reactor's safety; the state can only watch. The state lab has its own safety staff, including a Radiation Safety Officer, and on 25 September it advertised a time-limited Safety Manager to run its overall safety program, with radiation experience listed as 'desirable.' The post may be new or a replacement; the listing does not say. None of this shows anything unsafe; under the safety agreement the state's role at the reactor is to observe.

Why it matters: Officials' safety assurances carry weight with residents; the record read shows the state's role at the reactor is to observe, and the lab's safety staffing is described only by the 25 Sept listing.

What would settle it: GRAMA to the Utah Department of Natural Resources / Office of Energy Development for the position description and whether it is new, the lab's EHS program and emergency plan, any agreement for USREL staff to serve Valar's radiation-safety role, and the lab's radioactive-materials license.

facts dir-006, ppl-018, safe-034, safe-017 · checked 2026-09-29: Defence pass 2026-09-29: Defended: re-read the state listing (existing 'Radiation Safety Officer'; UOSH and DEQ named), DOE 5 Fast Facts (developer responsible for reactor safety), NSDA p. 21, QAPD. The earlier 'record does not show who has been responsible' is narrowed: the lab has an RSO. Status stays unresolved; summary line literally true (TLA transcript quote; listing posted 25 Sept). | Earlier verify pass: Re-read on 2026-09-29: the state careers page for requisition 2646 (posted 2026-09-25, valid through 2026-10-02; 'TL - Time Limited', radiological experience 'desirable'; quotes exact), matching the archived copy; TLA transcripts (quotes exact), ETV 10 Oct 2025, NSDA p. 21, QAPD. | Correction 2026-09-29 (wording review): title, plain and why-it-matters restated as what the listing shows; background-check detail removed; verification wording updated ('summary line').
unresolvedsafety Worker safety: DOE's worker rule swapped for OSHA 'approved through the OTA'; the OTA and any DOE approval are not public
disc-019

What was said

What the record shows

The gap: Valar says the swap of DOE's worker-safety rule for OSHA standards during construction was approved through its DOE agreement, which is not public; its own paper says the formal exemption was still in process, pending a DOE rule revision, and Valar's list of DOE-approved alternatives omits it. DOE's standard says DOE authorization can be exempt from OSHA. Which agency inspects and enforces worker safety at Ward 250 now that it operates is not stated in any record read.
In plain termsWorkers at federal nuclear sites are normally protected by DOE's own worker-safety rule. Valar's paper replaces it with ordinary OSHA workplace rules and says that was 'approved through' its private contract with DOE. The contract is not public, and the same paper says the formal exemption was still being requested. DOE's own standard says DOE-authorized sites can be exempt from OSHA. So the public record does not show which rulebook is enforced at the site, which agency would inspect it, or who would take a worker's complaint.

Why it matters: Workers need a clear rulebook and an inspector; the public record shows neither for this reactor.

What would settle it: FOIA to DOE Idaho Operations Office for the 10 CFR 851 exemption request and decision and the OTA's worker-safety terms; GRAMA to the Utah Labor Commission (UOSH) for any jurisdiction determination, inspection or complaint concerning Valar at the San Rafael lab.

facts safe-017, safe-005, orig-055 · checked 2026-09-29: Defence pass 2026-09-29: Defended: NSDA pp. 45, 48 (exemption pending a 10 CFR 851 revision; 'Phased'), 55 (construction phase only; 'approved through the OTA'), NSDA web summary (approved alternatives omit it), state listing (UOSH named), DOE-STD-1271. The company's reading (construction-phase swap agreed in the OTA) is plausible; the OTA is not public. Status stays unresolved; summary line literally true. | Earlier verify pass: Re-read on 2026-09-29: NSDA pp. 45, 48, 55 (quotes exact), DOE-STD-1271 section 1 ('In some instances (e.g. worker industrial safety)...'), USAspending record. | Correction 2026-09-29 (wording review): verification wording updated ('summary line').
unresolvedsafety 'Unmatched safety profile and proliferation resistance' with TRISO: the fuel cleared for Ward 250 is HALEU
disc-016

What was said

  • Valar Atomics (home page; technology page lists 'ANTI-PROLIFERATION'): "an unmatched safety profile and proliferation resistance when paired with TRISO fuel".
    The New Atomic Age (home page) (Valar Atomics)

What the record shows

The gap: 'Unmatched' is a comparison no record tests. On proliferation, the record points both ways: the fuel is HALEU, which an independent science group calls more attractive for weapons development than ordinary reactor fuel, but the same group says TRISO spent fuel may be harder for a proliferator to reprocess, which supports part of Valar's claim. No regulator finding settles it.
In plain termsValar's home page says its reactor design has an 'unmatched' safety profile and resists misuse of its fuel for weapons when paired with TRISO fuel. 'Unmatched' is marketing that no document can test. On weapons misuse, the picture is mixed, and the same science group supplies both sides: the fuel DOE cleared for Ward 250 is HALEU, which the Union of Concerned Scientists says is more attractive to would-be bomb makers than ordinary reactor fuel (though not usable in a weapon directly and far less of a risk than plutonium), while TRISO's tough coatings may make its used fuel harder to reprocess. The same group warns that reactors without a traditional sealed containment building, like Ward 250, may give up some of their built-in safety advantage. These are expert views, not rulings.

Why it matters: Security of the fuel and the lack of a containment building are real design choices the public should weigh, not settled by a slogan.

What would settle it: DOE's security categorization of Ward 250's fuel and its Physical Security Plan review (FOIA to DOE Idaho Operations Office; likely partly withheld), and the approved DSA's containment analysis.

facts safe-025, safe-010, orig-004 · checked 2026-09-29: Defence pass 2026-09-29: Defended: re-read the UCS executive summary in full on HTGRs (TRISO spent fuel may be harder to reprocess; HALEU 'impractical for direct use' but more attractive than LWR LEU; 'to a far lesser extent than using plutonium'). The claim is partly supported by the critics' own source. Status stays unresolved. Summary line rewritten: the fuel is HALEU TRISO, so 'paired with TRISO' is met; the new line states only that. | Earlier verify pass: Re-read on 2026-09-29: home and technology pages, UCS executive summary (quotes exact), SER, NSDA p. 8. UCS's 'far less than plutonium' point is in safe-025. | Correction 2026-09-29 (wording review): verification wording updated ('summary line').
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 are not in any public record found. The one approval Valar dated to 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 innocent 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 the public cannot see is the individual approvals or 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; state boards cited them when voting for 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-027, safe-005, safe-006, safe-007, safe-018, safe-019, gov-037, gov-013, plan-009, mine-016, dir-031 · checked 2026-09-29: Defence pass 2026-09-29: Defended: 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 innocent reading. Status stays unresolved; summary line literally true (web post 'has approved'; PDF Table 7 'In Review'). | Earlier verify pass: Re-read on 2026-09-29: 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. | Correction 2026-09-29 (calculation audit): gap adds the 45-day review end (6 Nov 2025) and the quality program's approver role. | Correction 2026-09-29 (wording review): source title parenthetical now 'not listed in Valar's library'; verification wording updated ('summary line'). Correction 2026-10-01 (precision review): wording made more exact against the cited records.
unresolvedtechnical 'Raw and uncleaned' data for 'external peer review', said an unfinished, unlisted Valar page in June; the only data is one unlabeled chart
disc-052

What was said

What the record shows

  • The page shares one chart, 'Reactor Power Ascension', plotting an unlabeled 0-100 'Q_Total' and thermocouple readings of about 30-80 F against a 'sample index', with no units, dates or times; the page is unlisted and still carries placeholders ('July XX', '[xxx]') (plan-007).
    Reactor Power Ascension chart (image on the By the Numbers page) (Valar Atomics, 2026-06-28)
  • Valar's library page lists no later data release or peer-review result as of 29 September 2026.
    Library (Valar Atomics)
  • The page carrying the promise is unfinished and unlisted: it breaks off mid-sentence ('This aspect', 'All of these'), keeps placeholders ('made power on July XX', '[xxx]') and is not listed in Valar's library (orig-071). It may be a draft never meant for release.
    Ward 250 By the Numbers (Isaiah Taylor; unlisted page that still carries placeholders) (Valar Atomics, 2026-06-28)
The gap: The promise sits on a page that is unfinished and unlisted in Valar's library, so it may be a draft never meant to be read, which is a plausible innocent reading. But it is live at a public address under the CEO's name, and three months later no reviewed data, and no other data release, has appeared.
In plain termsOn an unfinished page dated June, Valar's founder wrote that the company was sharing its raw reactor data and would have outsiders check it over the following weeks, as part of being 'a very open and transparent company.' The page was never finished or listed in Valar's library, so it may be a draft that was never meant to go out. But it is on Valar's public website under his name. What it actually shows is one chart with no units, no dates and no time scale, so no one can tell from it how much power the reactor made or when. Three months later, no checked data has appeared anywhere.

Why it matters: Independent review of real operating data is the best way for the public to know what the reactor does; it has been promised, not delivered.

What would settle it: Valar publishing the power, temperature and radiation data with units and times, and naming its external reviewers; FOIA to DOE Idaho Operations Office for the operating logs.

facts safe-040, plan-007, orig-035, orig-071 · checked 2026-09-29: Defence pass 2026-09-29: Defended: re-read the page (truncated sentences, placeholders; not listed in the library per orig-071). The draft reading is plausible and weakens 'promised'; the page is nonetheless public and no data release has followed. Moved from claim_unsupported to unresolved. Summary line rewritten to call the page a draft and say what it shares. | Earlier verify pass: Re-read on 2026-09-29: By the Numbers page (quotes exact; placeholders present), chart per plan-007, library page (five listed posts, no data release). | Correction 2026-09-29 (wording review): listing wording now 'not listed'; verification wording updated ('summary line').
unresolvedregulatory 'The same standards as the NRC': DOE rewrote the rules, Valar swapped several, and the proof is not public
disc-023

What was said

What the record shows

The gap: Valar and DOE say the DOE route applies safety standards equivalent to the NRC's. The record shows a rewritten DOE rulebook; six substitutions Valar requested, three of which Valar says DOE approved, mostly standards used at NRC-licensed research reactors; DOE reviewers as observers at design reviews; and no public copy of the approvals that would show the result. 'Same standards' may hold for research-reactor rules; the public cannot test it.
In plain termsValar's CEO says DOE held Ward 250 to the same safety standards the NRC would have, and DOE says its process is 'fundamentally similar.' Valar asked to use lighter substitutes in six areas; by its own account DOE approved three, and those three are standards that NRC-licensed university research reactors also use, which supports part of the claim. But DOE rewrote its rulebook for these reactors in 2025, the NRC's process is public with hearings and published reviews, and DOE's review of Ward 250 is not. So 'the same standards' may be true, but the public has no way to test it, and a science group that follows reactor safety says the new rules leave companies wide discretion.

Why it matters: 'Same standards' is the core reassurance offered for authorizing the reactor under DOE instead of NRC licensing, the route EO 14301 set up; without the documents it cannot be checked.

What would settle it: FOIA to DOE Idaho Operations Office for DOE's decisions on each requested alternative, the approved DSA and TSRs, and DOE's Safety Evaluation Report.

facts ppl-024, safe-003, safe-004, safe-005, safe-002, safe-018 · checked 2026-09-29: Defence pass 2026-09-29: Defended: NSDA web summary (three approved alternatives), NSDA pp. 10, 49, 54 (research-reactor comparison; ANS-15 standards), DOE 5 Fast Facts, TNR. The substitutions are largely research-reactor standards, supporting part of 'same standards'; the approvals remain unpublished. Status stays unresolved; summary line literally true (six requested, NSDA pp. 45-56). | Earlier verify pass: Re-read on 2026-09-29: TNR (delivered part; quote exact), DOE 5 Fast Facts, NSDA pp. 49-56, DOE-STD-1271, UCS statement of 28 Jan 2026 (quotes exact). Taylor's words rest on one report. | Correction 2026-09-29 (calculation audit): substitution record adds the 18-criteria versus 10 CFR 830.122's 10 point. | Correction 2026-09-29 (wording review): source title parenthetical now 'not listed in Valar's library'; verification wording updated ('summary line'). Correction 2026-10-01 (precision review): wording made more exact against the cited records.
unresolvedregulatory From 'why engage?' with the NRC and 'no transition to NRC licensing' to NRC licensing presented as the Carbon safeguard
disc-027

What was said

What the record shows

The gap: In 2025 Valar was suing the NRC and saw no reason to engage it; Ward 250's safety paper rules out NRC licensing for that reactor. Valar's own later account (to The New Republic, February 2026) is that it will apply to the NRC 'Once we're ready', which fits its current hiring for NRC licensing. The gap is that the state presented NRC licensing and an NRC decommissioning bond as safeguards for Valar's Carbon campus while no record shows Valar has begun any NRC process.
In plain termsA year ago Valar's founder was suing the Nuclear Regulatory Commission and asked why his company should deal with a regulator it believed had no say. Now the state is telling Carbon County that the NRC's public licensing process, and an NRC-required cleanup bond, will protect them at Valar's planned campus near Wellington, and Valar is hiring people for NRC licensing. Companies can change course, and the new hiring suggests Valar may. But nothing public shows Valar has started an NRC process, and the safeguards the state listed depend on it.

Why it matters: The Carbon lease's promised public hearings and cleanup bond exist only if Valar goes through the NRC.

What would settle it: FOIA to the NRC for records of meetings or correspondence with Valar Atomics since 2024; a resident can search NRC ADAMS for 'Valar' by hand; ask Valar and Trust Lands which regulator the Carbon campus will use.

facts csite-022, safe-032, safe-028, csite-010, ppl-024, gov-012 · checked 2026-09-29: Defence pass 2026-09-29: Defended: Valar's stated change of course (TNR, 'Once we're ready') and the Director of Licensing posting (DOE and NRC pathways) are consistent with each other; 'No transition to NRC licensing' applies to Ward 250 only. The open question is whether the state's NRC-based safeguards will exist. nrc.gov still refuses our reader. Status stays unresolved; summary line literally true. | Earlier verify pass: Re-read on 2026-09-29: E&E (quotes exact), NRC-lawsuit post, NSDA p. 2, TNR (delivered part), TLA slides and memo, live Greenhouse feed. | Correction 2026-09-29 (wording review): verification wording updated ('summary line').
unresolvedpublic_process DOE reviewed a single 12-month test 'not segmented' and with 'no expansion'; Valar had a 10,270-acre application pending
disc-028

What was said

  • U.S. Department of Energy (categorical exclusion for Ward 250, signed 22 April 2026) (2026-04-22): A "single limited-duration research mission"; "No expansion of site boundaries occurs"; construction "confined to the existing USREL site"; "The proposal has not been segmented to meet the definition of a categorical exclusion."
    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)

What the record shows

The gap: DOE's review describes one short test with no expansion and states the proposal was not split up to fit an exclusion; its own text says phases with their own decisions are not segmentation. By its signing date Valar had a 10,270-acre reactor and data-center application pending with BLM (described by Valar as a survey-access request), a Carbon County lease mapped and noticed, county approval for a staging area for work on adjacent properties, and a stated plan to buy neighboring land for fuel fabrication. Ward 250 may truly be separate; whether DOE knew of or weighed the larger plan is not in the records read.
In plain termsFederal agencies need not write a full environmental study for small, self-contained projects that fit a categorical exclusion, but they are not supposed to cut a big project into small pieces to qualify. DOE's review of Ward 250 says it is one short test that will not expand, and was not cut into pieces. At the same moment, the public record shows Valar applying for a 10,270-acre reactor and data-center site on federal land, lining up a lease in Carbon County, using county land beside the lab for construction staging, and planning a fuel factory next door. DOE's rules allow later phases to get their own decisions, and Ward 250 may truly be separate. But no public document shows DOE weighed the larger plan.

Why it matters: A categorical exclusion means no public environmental study and no comment period; whether that fits depends on the whole plan.

What would settle it: FOIA to DOE Idaho Operations Office for the CX file DOE-ID-26-005 (Valar's environmental checklist and correspondence about other sites); FOIA to BLM Price Field Office for the Green River and Beehive case files.

facts csite-021, csite-020, mine-006, mine-048, csite-032, gov-022, plan-024, gov-033, safe-029 · checked 2026-09-29: Defence pass 2026-09-29: Defended: CX segmentation text (phases with their own decisions excluded), Emery 7 Apr minutes (staging for 'adjacent properties'), Washington Sun (survey access). Each later project would need its own decision, which is the company-side reading. Status stays unresolved; summary line literally true. | Earlier verify pass: Re-read on 2026-09-29: CX (quotes exact), BLM rights-of-way layer re-queried (three pending Valar cases; Green River case date 2026-02-13), RDCC record 87203 re-queried (created 2026-04-20), TLA packet map footer ('Produced: April 09, 2026'), Emery 7 Apr minutes (staging agreement; new in this pass), GOED materials and minutes. Valar told a reporter it dropped the Green River site (mine-008); BLM still lists it pending. | Correction 2026-09-29 (wording review): verification wording updated ('summary line'). Correction 2026-10-01 (precision review): wording made more exact against the cited records.
unresolvedpublic_process Officials called the Carbon lease process open and 'not hiding anything'; the county records read did not name the site
disc-031

What was said

What the record shows

The gap: Officials described the process as open and Valar as hiding nothing. Their words can fairly be read as praise of Valar's 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). 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, the committee meetings were not publicly noticed, 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's commissioners 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' to get the proposal approved. Read generously, the officials meant Valar had been open with them, and the record supports that: the county had worked with Valar for months. But residents were not in the room. 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; the committee meetings where the deal was shaped were not publicly announced; 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-019, ppl-020, csite-028, csite-017, mine-013, mine-014, mine-047, csite-026, csite-030, csite-005 · checked 2026-09-29: Defence pass 2026-09-29: Defended: 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 innocent 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). | Earlier verify pass: Re-read on 2026-09-29: 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. | Correction 2026-09-29 (wording review): why-it-matters restated as the open legal question; verification wording updated ('summary line'); review: title, gap and summary line state the agenda absence as what the records read show.
unresolvedsite A posted notice names Valar as locator of a lode claim where the only 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 posted at the RW 453 monument; photo) (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.
    Photo of the Notice of Location posted at the RW 453 location monument (resident fieldwork, 2026-09)

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 favour: 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 naming Valar Atomics as locator stands 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; it has not said. Under 30 U.S.C. 612 an unpatented claim may be used only for prospecting, mining or processing. 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 (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 fld-001, fld-002, dir-001, dir-002, dir-003, dir-004, dir-005, mine-022, csite-019 · checked 2026-09-29: Defence pass 2026-09-29: Defended: no Valar statement about the RW claims was found on its site or in any record read; the innocent 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 mining pass's mineral records (dir-003). | Earlier verify pass: Seeded entry kept and extended on 2026-09-29 with the survey-tie and land-status findings (dir-001, dir-002). Re-read that day: 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 layers rest on the mining pass (the UGRC host's robots.txt answered 403; not re-queried). Status unresolved until the filings say what mineral is claimed. | Correction 2026-09-29 (wording review): title attributes the claim to the posted notice; 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'). Correction 2026-09-30 (source objectivity review): 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 queried during the 28-30 September 2026 research; that server's robots rules do not allow a saved copy, so none is kept and the figures rest on the cited layer as queried that day.
unresolvedsite Valar says it dropped its 10,270-acre Green River site; BLM still lists the reactor case pending
disc-054

What was said

What the record shows

The gap: Valar describes its Green River application as a survey-access request it has dropped. BLM's public record still shows the case pending, titled for a reactor and data center; that title and a survey-access request are consistent (a survey of a possible reactor and data-center site). BLM's record was last modified on 26 May 2026, before Valar's statement, so a withdrawal not yet processed is a plausible reading. A second reactor-and-data-center case ('Project Beehive') is pending and named in no Valar publication.
In plain termsValar applied to use a 10,270-acre piece of federal land near Green River, and BLM's records title it a site for small modular reactors and a data center. When a reporter found it, Valar said it had only asked for access to survey the land and had dropped the idea. Two weeks later BLM still lists the case as pending, with the same title, and a second Valar reactor-and-data-center case ('Project Beehive') is pending too. The withdrawal may just not have been processed yet; only BLM's case file can show what was asked for and whether it was withdrawn.

Why it matters: Federal land applications for reactors are the earliest sign of where Valar may build next; neither is on any Valar page.

What would settle it: FOIA to BLM Utah State Office / Price Field Office for the case files of UTUT106784007, UTUT106801248 and UTUT106833224 (applications, maps, correspondence and any withdrawal).

facts mine-008, mine-006, mine-007, plan-017 · checked 2026-09-29: Defence pass 2026-09-29: Defended: the BLM title and Valar's 'survey access' account are compatible; the layer's last-modified date (26 May 2026, per mine-008) predates Valar's 18 Sept statement, so processing lag is plausible. Status stays unresolved; summary line literally true (Washington Sun update; BLM layer re-queried 29 Sept). | Earlier verify pass: Re-read on 2026-09-29: Washington Sun (update text; quotes exact) and the BLM rights-of-way layer (query CUST_NM_SEC like 'VALAR': three pending cases; Green River case date 2026-02-13, 10,270.61 acres). | Correction 2026-09-29 (wording review): verification wording updated ('summary line').
unresolvedsite 'No burden on our water supply'; yet 10 acre-feet 'for industrial use' and up to 1,000 more water shares sought
disc-034

What was said

What the record shows

The gap: The reactor needs no cooling water, so that part of the claim holds, and Valar's 'waterless' wording refers to cooling. The site and campus plans do use water: Valar told Castle Dale about 10 acre-feet 'for industrial use', with no time period (it could be an allocation rather than a yearly draw), which DOE's review does not mention; Valar is working toward up to 1,000 more water shares for future development; and a Carbon campus would have to buy rights in a fully appropriated basin.
In plain termsWard 250 is cooled by helium gas, not water, and DOE's review lists only household-scale water use; so 'the reactor needs almost no water' holds. But Valar told one city council the reactor needs about 10 acre-feet 'for industrial use,' which, if that is a yearly figure, is roughly nine times DOE's number and appears nowhere in DOE's review. Valar is also working toward up to 1,000 more water shares for future projects, and its Carbon County campus would have to buy water in a basin where the state says all water is already spoken for. 'No burden on our water supply' is true of the reactor's cooling, not of everything Valar plans to build around it.

Why it matters: Water is scarce in Castle Country; figures in the federal review and in local statements should match, and campus-scale use is where the burden would fall.

What would settle it: FOIA to DOE Idaho Operations Office for the environmental checklist Valar submitted for the categorical exclusion; GRAMA to Orangeville City and Castle Valley SSD for Valar's water connection records; watch the State Engineer's 'Notice to Water Users' for any Valar application.

facts loc-025, loc-017, mine-042, mine-017, orig-070, loc-005, loc-031 · checked 2026-09-29: Defence pass 2026-09-29: Defended: 'no burden on our water supply' in the Series B post refers to reactors cooled without water, which holds for Ward 250 (CX: domestic use under 1,000 gal/day). The 10 acre-feet figure has no stated period and may be an allocation. Status stays unresolved; summary line literally true. | Earlier verify pass: Re-read on 2026-09-29: Series B, GOED minutes, ETV 3 July (quote exact), CX, Castle Dale 12 March 2026 minutes (page image; quote exact), Orangeville 9 July minutes, ETV 28 July, TLA September memo. Arithmetic: 10 acre-feet = about 3.26 million gallons. | Correction 2026-09-29 (wording review): verification wording updated ('summary line').
unresolvedsite Has Valar bought the 112 acres by the lab? The state says 'has purchased'; Valar said it awaited clean title
disc-055

What was said

What the record shows

The gap: A state agency says Valar has bought the land; Valar itself said in mid-August that it was still waiting on clean title. Whether the sale closed between 20 August and 10 September is not shown by any record read.
In plain termsValar agreed in May to buy about 112 acres of county land next to the state lab for $394,500, for fuel-making and manufacturing. In August Valar told a city council it was still waiting on clean title, and told the state land board it was 'currently purchasing' the land. In September the state's Inland Port Authority wrote that Valar 'has also purchased' it. Both can be true if the sale closed in between. A deed at the county recorder would settle it.

Why it matters: Who owns the land beside the reactor bears on the public-access boundary in the accident math (disc-008) and on annexation and zoning.

What would settle it: Emery County Recorder: a deed from Emery County or its Local Building Authority to Valar Atomics Inc for parcel 04-0019-0030 (public record).

facts loc-014, mine-018, gov-022, mine-046 · checked 2026-09-29: Defence pass 2026-09-29: Defended: both statements can be true if the sale closed between 20 August and 10 September; no deed was read and no Valar statement after 20 August was found. Status stays unresolved; summary line literally true (UIPA 'has also purchased'; transcript 'currently purchasing'). | Earlier verify pass: Re-read on 2026-09-29: UIPA update, Orangeville 13 Aug minutes, 20 Aug auto-transcript, Emery 19 May minutes (quotes exact). | Correction 2026-09-29 (wording review): verification wording updated ('summary line').
unresolvedfunding Governor: the deal would cost Utah 'virtually nothing'; the state later approved up to $106.7 million in tax credits
disc-035

What was said

What the record shows

The gap: In May 2025 the governor described the state's cost as virtually nothing beyond space and infrastructure, describing the MOU as it then stood. The record shows that the space is a publicly funded lab whose use terms are not public, and that in July 2026 the state approved up to $106.7 million in post-performance tax credits for Valar, paid only out of new state tax revenue the project generates, and conditioned on a local incentive the county said in April it had not been asked for. Whether a credit paid from new revenue is a 'cost' is a matter of definition.
In plain termsWhen the deal was announced, Utah's governor said it would cost the state 'virtually nothing,' since Utah was only providing space. That space is a research lab the public paid about $15 million to build and $2 million to buy. In July 2026 a state board approved up to $106.7 million in tax credits for Valar over ten years. Those credits are paid only out of new tax money the company generates, so they are not a check written from existing funds; reasonable people can argue whether that is a 'cost.' But the state's financial commitment grew far beyond 'space,' and the vote was taken before the public agenda named the company.

Why it matters: Taxpayers are entitled to know what the state gives in exchange; the lab-use terms remain unpublished.

What would settle it: GRAMA to the Governor's Office of Economic Opportunity for Valar's incentive application and agreement; GRAMA to the Utah Office of Energy Development for the lab-use agreement and payments; search Transparent Utah for payments to or from Valar.

facts orig-065, csite-024, gov-033, fund-015, fund-016, fund-017, gov-021 · checked 2026-09-29: Defence pass 2026-09-29: Defended: the governor spoke about the 2025 MOU; the 2026 credit is post-performance (GOED materials) and came 14 months later; the county's April answer ('None') was accurate when given. Status stays unresolved; summary line literally true (KUTV; GOED materials). | Earlier verify pass: Re-read on 2026-09-29: KUTV, Emery 7 Apr minutes (quotes exact), GOED materials (Valar summary: $106,737,499; 50%; 10 years; site specific), HB 410 fiscal note ($2,000,000 one-time), Emery 19 Nov 2024 minutes ($2,111,444), ETV 2022 (about $15 million). The governor's words rest on one outlet. | Correction 2026-09-29 (wording review): verification wording updated ('summary line').
unresolvedfunding Funding as announced and as filed: no Valar filing states its rounds, and its lead lender's director is a Valar backer
disc-043

What was said

What the record shows

The gap: Valar's announced totals are not in any Valar filing; the seed round is $19 million or $18 million depending on the source; valuations come only from Bloomberg as relayed; rounds overlap by an unstated amount. The bank leading Valar's credit facility has a Valar investor as a director and principal shareholder, which the announcements do not mention. Nothing read shows improper terms.
In plain termsValar says it has raised over a billion dollars, but the company itself has filed nothing with the SEC that states how much it sold, to whom, or who its directors are; the figures come from its own posts and from press reports. Even the first big round is reported as $19 million by one source and $18 million by an investor. The SEC requires a Form D for offerings under Regulation D, the most common route, but not for every private sale, and nine investor pools that bought Valar shares did file; so the missing company filing may reflect a different legal route rather than a skipped one. The bank leading Valar's $200 million credit line lists Palmer Luckey, a reported Valar investor, as a director and major shareholder, and neither Valar nor its lawyers mentioned that; nothing read shows improper terms.

Why it matters: Money decides whether Valar can pay to clean up and store its waste; its size and sources are known only from announcements.

What would settle it: Ask Valar which securities exemption it used and why no Form D was filed; Hercules Capital's 10-Q for the quarter ending 30 September 2026 may show its share of the credit facility; the Delaware certificate of incorporation (by hand) would show share classes.

facts fund-003, fund-006, fund-007, fund-008, fund-009, fund-010, orig-057 · checked 2026-09-29: Defence pass 2026-09-29: Defended: SEC 'Exempt Offerings' page (Form D tied to Regulation D) replaces the earlier unsourced sentence about exemptions; the nine pool Form Ds (fund-010) show investors' vehicles filed. The Erebor-Luckey tie is a disclosure point, not evidence of improper terms. Status stays unresolved; summary line literally true ('Valar's own SEC filings found: none'). | Earlier verify pass: Re-read on 2026-09-29: Series B post, TechCrunch 20 Feb 2025, 17 July 2026 and 3 Aug 2026, Initialized blog, OCC letter (layout text: 'Palmer Luckey Director, Principal Shareholder'), Goodwin announcement (quotes exact). The EDGAR Form D search rests on the funding pass; not re-run here. | Correction 2026-09-29 (wording review): tool names removed from the note; verification wording updated ('summary line').
unresolvedfunding Emery County voted to take Valar's parcel out of the Inland Port tax zone; the port authority still says it is in
disc-056

What was said

What the record shows

The gap: The county voted to remove Valar's parcel from the port authority's tax-capture zone; the port authority's plan, adopted two days later, and its September statement still count it in. If the county's resolution needs port-authority action to take effect, the port authority's statement is accurate and the county's vote is pending; if not, the port authority's statement is out of date. No record read shows which, and the answer decides where most new property tax on Valar's land goes for 25 years.
In plain termsThe Inland Port Authority keeps most of the growth in property taxes inside its project zones for 25 years. In May, Emery County voted to take Valar's parcel next to the lab out of that zone. The port authority's plan, adopted two days later, and its September news update still say the land is inside it. Both can be accurate if the county's vote only takes effect once the port authority acts on it, which the records read do not show. The answer decides whether future taxes on Valar's land go mostly to the port authority or to local schools and services.

Why it matters: Money: which public bodies get the tax revenue the project is supposed to bring.

What would settle it: GRAMA to the Utah Inland Port Authority for any action on Emery County's 19 May 2026 resolution and the current parcel list; GRAMA to Emery County for the resolution as transmitted.

facts gov-023, gov-018 · checked 2026-09-29: Defence pass 2026-09-29: Defended: tested whether the two records can both be right (a county resolution awaiting port-authority action). No record of UIPA action on the resolution was found; the legal effect of the county vote alone is not shown. Moved from documented_conflict to unresolved. Summary line literally true. | Earlier verify pass: Re-read on 2026-09-29: UIPA update (quote exact), Emery 19 May minutes (quotes exact). The Amendment #3 plan was read in the government pass (gov-018) and not re-opened here. | Correction 2026-09-29 (wording review): verification wording updated ('summary line').
unresolvedtechnical Electricity demo: 'directly powered AI infrastructure' at 37% power via a thermoelectric generator; output unpublished
disc-025

What was said

What the record shows

The gap: Valar's 'first and only' claims about powering AI and a startup generating nuclear power cannot be tested: no measured output has been published. Valar's own description of the event is narrow ('directly powering an NVIDIA chip'); the larger figures ('a 100-kilowatt generator', '100 kilowatts of electricity') are local press wording, while the reactor's heat limit is 100 kW and the demonstration ran at 37% power through a thermoelectric converter.
In plain termsOn 1 July Valar ran a website server on electricity from Ward 250. That did happen in front of an audience. But how much electricity it made has never been published. The reactor was at about a third of its power, and a thermoelectric generator turns only part of that heat into electricity, so the output was far below the '100 kilowatts of electricity' one newspaper printed. 'The first and only time an advanced reactor powered AI' and 'the first startup to generate nuclear power' are claims no record can check.

Why it matters: Public milestone claims should match the record; no measured output has been published to test these 'firsts', and some press figures overstate what the reactor's limits allow.

What would settle it: Valar publishing the measured electrical output of the 1 July demonstration; FOIA to DOE Idaho Operations Office for the operating log of that day.

facts orig-013, orig-042, plan-010, orig-066, orig-070, safe-030 · checked 2026-09-29: Defence pass 2026-09-29: Defended: Castle Country's own wording is narrow ('directly powering an NVIDIA chip'); the 100 kW electricity figures are ETV narration and Deseret wording, not Valar's. No output measurement or counterexample to the 'firsts' was found. Status stays unresolved; summary line literally true (Series B; ETV's 37%). | Earlier verify pass: Re-read on 2026-09-29: Series B, Castle Country, ETV 1 July (quotes exact), Deseret 1 July, NSDA p. 25. The Deseret figure is press narration, recorded as such. | Correction 2026-09-29 (wording review): why-it-matters restated; press figures now 'the larger figures'; verification wording updated ('summary line').
unresolvedtimeline 'We are building and testing this reactor in the Philippines instead' (April 2025); a year later, not built
disc-038

What was said

What the record shows

The gap: In April 2025 Valar said it was 'building and testing' its first reactor in the Philippines. The record shows a real, continuing project: a partnership with the Philippine Nuclear Research Institute, licensing begun (per Valar), a Philippine department's approval (per PNRI's director), and a target of two to three years from April 2026. What the record does not show is any construction or testing, so 'building and testing' described plans as if they were work under way.
In plain termsIn April 2025 Valar said U.S. rules forced it to build and test its first reactor in the Philippines. The Philippine project is real: Valar signed a partnership with the country's nuclear research institute, said it had begun licensing there, and the institute's director says a Philippine department has approved it. But a year later, according to the University of the Philippines student paper, nothing had been built, and the project was still seeking permission to use a site, with completion two to three years away. Meanwhile U.S. rules changed in May 2025 and Valar built in Utah first. 'We are building' described a plan, not construction.

Why it matters: Public statements about work under way should match the record; the April 2025 post described the Philippine project as building and testing, and no construction is on record.

What would settle it: A Philippine Freedom of Information request to the Philippine Nuclear Research Institute for the Valar agreement and license application; ask Valar for the project's status.

facts orig-018, orig-064, ppl-002, fund-020 · checked 2026-09-29: Defence pass 2026-09-29: Defended: GMA (licensing begun with PNRI), Power Philippines (100 kW, not grid-connected), Collegian (DOST approval; 2-3 years; site approval pending). The project exists and continues, so 'building' can be read as a plan in progress; no construction is on record. Moved from claim_unsupported to unresolved. Summary line literally true (Collegian, April 2026). | Earlier verify pass: Re-read on 2026-09-29: NRC-lawsuit post, GMA, Power Philippines, Philippine Collegian (quotes exact). PNRI's own site refused our reader (sources_not_read in origins.json). | Correction 2026-09-29 (wording review): why-it-matters restated; verification wording updated ('summary line').
unresolvedpeople Local jobs and 'relocated' from California: the numbers told to towns, the state and job boards do not line up
disc-039

What was said

What the record shows

The gap: Valar told Carbon County it relocated from California, and told the state of about 40 full-time local residents and 275 future jobs. The record shows most of its openings and its registered place of work in California, and, in April, Valar saying many of its 120 Emery workers did not live in Utah. The figures count different things; no payroll record exists to check them.
In plain termsValar has told local officials it moved to the region from California and employs about 40 local people, and told the state it will create 275 jobs averaging $137,567 a year. But most of its job openings are in Torrance, California, its federal paperwork lists California as where the work is done, and in April its own Utah director said many of the 120 people working in Emery County did not live in Utah. These numbers can all be true at once, counting different groups at different times. None can be checked against a payroll, and the state tax credit depends on the 275.

Why it matters: Local jobs are the main public benefit officials cite; the state's $106.7 million credit is tied to them.

What would settle it: GRAMA to the Governor's Office of Economic Opportunity for Valar's incentive application and any annual job and wage reports.

facts loc-004, loc-029, plan-022, fund-017, orig-036, loc-019 · checked 2026-09-29: Defence pass 2026-09-29: Defended: the figures count different groups at different times (site staff, company-wide staff, contractors, future jobs); 'relocated... two years ago' rests on summary minutes. No payroll or GOED job report found. Status stays unresolved; summary line literally true (Carbon minutes; job feed 71 of 92 in Torrance). | Earlier verify pass: Re-read on 2026-09-29: Carbon 19 Aug minutes (image), 20 Aug TLA minutes, GOED materials, Ferron 15 Apr minutes (page image; quote exact), live job feed (70 'Torrance, California' + 1 'Torrance, CA', 21 Orangeville), USAspending record, ETV town-hall report. | Correction 2026-09-29 (wording review): verification wording updated ('summary line').
unresolvedfunding What the Wellington parcel earns now: '$4,000 per year' in the staff memo, '$4,000 per month' in the board's minutes
disc-042

What was said

What the record shows

  • The board's approved minutes of 20 August 2026 record staff telling a trustee the parcel yields 'approximately $4,000 per month from the Utah National Guard'.
    08.20.2026 FINAL TLA Minutes (Utah Trust Lands Administration (Utah Public Notice Website), 2026-09-17)
  • The meeting's own transcript records staff saying 'Right now, we are making $4,000 and some change' from the Guard lease, with no period stated; the approved minutes' 'per month' is not in the recorded words.
    2026-08-20 TLA Board of Trustees Meeting Audio Transcript (auto-generated) (Utah Trust Lands Administration (Utah Public Notice Website), 2026-08-20)
The gap: The memo says the parcel earns about $4,000 a year; the approved minutes say $4,000 a month. The meeting's transcript shows staff naming no period, so the minutes' 'per month' may be the minute-taker's addition and the memo's figure may be right. The Guard lease rent would settle it.
In plain termsTo show the Valar deal was a good one for school funding, the state's memo said the land now earns only about $4,000 a year. The board's approved minutes record staff saying $4,000 a month, twelve times as much. The meeting recording's transcript shows the staffer said only '$4,000 and some change,' with no 'a year' or 'a month,' so the minutes may simply have added the wrong period. The Guard's lease rent would settle it; the two public records still disagree until one is corrected.

Why it matters: The trust's duty is to get fair value for school land; the baseline the board relied on is stated two ways.

What would settle it: GRAMA to Trust Lands for the Utah National Guard lease (SULA 1321) rent and the parcel's revenue history.

facts mine-032, csite-003 · checked 2026-09-29: Defence pass 2026-09-29: Defended: the 20 Aug auto-transcript ('Right now, we are making $4,000 and some change'; no period) makes a minutes error the likeliest explanation. Moved from documented_conflict to unresolved: the records disagree, but the conflict probably lies in the minutes, not the memo the board relied on. Summary line literally true (memo 'per year'; minutes 'per month'). | Earlier verify pass: Re-read on 2026-09-29: TLA September memo and 20 Aug final minutes (quotes exact). | Correction 2026-09-29 (wording review): verification wording updated ('summary line').
unresolvedpeople Valar's safety papers say they are 'the property of Valar Atomics Limited'; every registry names Valar Atomics Inc.
disc-041

What was said

What the record shows

The gap: The two public safety documents name an owner, 'Valar Atomics Limited', that appears in no registry or federal record read; the DOE authorization and award name Valar Atomics Inc.
In plain termsThe cover of each of Valar's two public safety papers says the document belongs to 'Valar Atomics Limited.' Every government record found (DOE's review, the federal award, the trademark file) names 'Valar Atomics, Inc.,' a Delaware corporation, and no company called Valar Atomics Limited turned up. It may be a leftover template line. But which legal entity holds a nuclear authorization decides who is responsible, and who pays for cleanup.

Why it matters: Responsibility and liability attach to a specific legal entity.

What would settle it: Ask Valar; FOIA to DOE Idaho Operations Office for the submitting entity on the approved safety documents and the OTA.

facts orig-037, orig-051, orig-055 · checked 2026-09-29: Defence pass 2026-09-29: Defended: both covers share one document template ('Layout: DLT001-00'), which makes a leftover template line plausible; the QAPD's own text says 'Valar Atomics, Inc.'. No 'Valar Atomics Limited' was found in any registry read (orig-037). Status stays unresolved; summary line literally true. | Earlier verify pass: Re-read on 2026-09-29: NSDA and QAPD covers (quote exact), CX, USAspending record, QAPD text. | Correction 2026-09-29 (wording review): verification wording updated ('summary line').
claim holds upregulatory 'Not a commercial power plant': holds for Ward 250; the 'commercial units' Valar plans next have no named regulator
disc-026

What was said

What the record shows

The gap: None for Valar's claim: Ward 250 is a research reactor under DOE, as Valar consistently says. The wording that does not hold is others': a Carbon commissioner called it a 'commercial reactor', and the state lab's page speaks of moving 'directly from localized testing to the commercial grid'. Valar's 'every design has to be reviewed and approved by the Department of Energy' answered a question about the lab, where it holds. Valar's planned 'commercial units' and behind-the-meter power sales would fall outside the DOE test-reactor route, and Valar has not said which regulator it will use for them.
In plain termsWard 250 is allowed to run under DOE alone because it is a research reactor that does not sell power, and Valar says exactly that, every time. That claim holds. Valar has also told the state it plans more 'commercial units' nearby and wants to sell power directly to customers; selling power is a different legal category that, under DOE's own terms, falls outside the test-reactor route. Valar has not said which regulator will review those, though it is now hiring for NRC licensing work. The inaccurate descriptions came from others: a Carbon County commissioner called Ward 250 a 'commercial reactor,' and the state lab's page talks of going 'directly' to the commercial grid.

Why it matters: Which regulator applies decides whether there is a public hearing; the route for Valar's commercial units is not yet stated.

What would settle it: Ask Valar which regulator it will use for its 'commercial units'; FOIA to the NRC for any pre-application contact; FOIA to DOE-NE for any Launch Pad or DOE authorization covering sites beyond the San Rafael lab.

facts safe-030, gov-033, gov-039, loc-005, gov-026, gov-007, csite-010, plan-013 · checked 2026-09-29: Defence pass 2026-09-29: Defended: Castle Country and POWER ('non-commercial power ascension') show Valar's framing is consistent; the Emery answer (7 Apr minutes) concerned the lab. The mismatches are a commissioner's and the state lab page's wording. Moved from unresolved to claim_holds for Valar's claim; the open question (regulator for commercial units) moves to what_would_settle_it. Summary line rewritten to credit the claim and state the plan, both literally from the record (Castle Country; GOED 9 July minutes). | Earlier verify pass: Re-read on 2026-09-29: Castle Country, GOED 9 July minutes, ETV 3 July (quote exact), lab page, Emery 7 Apr minutes, EO 14301, DOE pathway release, NSDA p. 10, TLA September memo. | Correction 2026-09-29 (wording review): verification wording updated ('summary line').
claim holds upsite 'Storage of nuclear waste is strictly prohibited on the lease': holds as worded; the deal lets Valar buy land to store spent fuel
disc-032

What was said

What the record shows

  • The staff memo: before any part of the property is used to store radioactive waste, 'that portion, as determined by TLA, must be purchased by the lessee'; Valar must buy any portion 'required for the interim storage of spent fuel prior to any storage operations'.
    09.17.2026 TLA Board Packet (Item 10A: SULA 2095-OBA Board of Trustees Memorandum, Carbon County letter, lease map) (Utah Trust Lands Administration (Utah Public Notice Website), 2026-09-17)
  • Utah Code 19-3-321 (2026) exempts interim storage of waste from the state's high-level-waste rules only when it comes from a DOE-authorized test reactor at a facility owned by the state and is permitted by the state; land Valar buys would not be state-owned. Whether spent fuel at a private Carbon campus would fall under Utah's ban is not answered in any record read (csite-008).
    Utah Code 19-3-321: Exemptions (effective 5/6/2026) (Utah State Legislature, 2026-05-06)
The gap: None as worded: waste storage is barred on land under the lease. The limit: the written memo in the same public board packet lets Valar buy any portion it wants for interim spent-fuel storage before storing anything there, which the summary slide did not mention. Whether Utah law would allow spent fuel on land Valar owns is a separate, open question.
In plain termsThe slide shown to the state land board said storing nuclear waste is 'strictly prohibited on the lease.' That is true: the land stays waste-free while it is under the lease. The written deal in the same public packet adds a route the slide left out: Valar may buy any part of the land it wants to use for storing used reactor fuel, and store it there once it owns it. So the slide is accurate but incomplete, and the full terms were public for anyone who read the memo. Whether Utah law would actually allow spent fuel at a private campus like this is a separate, unanswered question.

Why it matters: Whether used reactor fuel could stay near Wellington is among the first questions residents ask; the short answer the board saw omits the route the deal provides.

What would settle it: The signed SULA 2095 OBA agreement (GRAMA to Trust Lands); a Utah DEQ or Attorney General opinion on whether Utah Code 19-3-301 bars spent-fuel storage at a private site.

facts csite-008, csite-023, mine-015 · checked 2026-09-29: Defence pass 2026-09-29: Defended: the slide is literally accurate and the purchase route was disclosed in the same public board packet (September memo pp. 22-24). Moved from unresolved to claim_holds with its limit stated. Summary line literally true of the slide and memo, and fair for a claim that holds. | Earlier verify pass: Re-read on 2026-09-29: TLA slides (quote exact), September memo pp. 22-24 (quotes exact), Utah Code 19-3-321. Status unresolved rather than conflict: the slide is accurate as worded. | Correction 2026-09-29 (wording review): lease wording restated; verification wording updated ('summary line').
claim holds uptimeline Criticality before July 4, 2026, as promised: it happened June 18, the only pilot reactor 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 (disc-024, disc-025).
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, orig-041, gov-006, fund-020, plan-004 · checked 2026-09-29: Defence pass 2026-09-29: Defended from the critics' side too: 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 verify pass: Re-read on 2026-09-29: August 2025 post (quote exact), July 2025 slide 6 (image), NSDA Table 7, DOE release, DOE fact sheet. | Correction 2026-09-29 (wording review): verification wording updated ('summary line').
claim holds upsafety 'Impossible to melt': DOE itself says TRISO particles cannot melt in a reactor; that is not the same as 'cannot leak'
disc-015

What was said

What the record shows

The gap: None: 'cannot melt' matches DOE's own description of TRISO fuel. The limit of the claim is that 'cannot melt' does not mean 'cannot release radioactivity'; Valar's worst-case analysis assumes some particles fail and release gases, and a science group says release speeds up at very high temperatures.
In plain termsWard 250's fuel beads are built to survive extreme heat, and DOE itself says TRISO particles 'cannot melt' in a reactor; DOE's tests took them to 1,800°C. So the claim holds as worded. What it does not mean is that nothing could ever escape. Valar's own worst-case calculation assumes some beads crack and let out radioactive gases, and one science group notes the beads leak faster above about 1,600°C. 'Won't melt' is true; 'can't release radiation' is not what the safety papers say.

Why it matters: Fairness: a strong safety claim that the record supports, with its limits stated.

What would settle it: Settled as worded by DOE's TRISO page; the approved DSA would show the as-built accident analysis.

facts safe-025, orig-012, loc-006, safe-013 · checked 2026-09-29: Defence pass 2026-09-29: Re-checked for overstatement in Valar's favour: DOE's TRISO page ('TRISO particles cannot melt in a reactor'; 1,800°C tests) supports 'impossible to melt'; the ETV narration's 'completely removing the risk of a meltdown' is press wording; the NSDA still assumes some particle failures and releases, and UCS says release speeds up above about 1,600°C. Holds as worded, limits stated. Summary line literally true. | Earlier verify pass: Re-read on 2026-09-29: DOE TRISO page ('TRISO particles cannot melt in a reactor'; 1,800°C tests), lab page, ETV 24 Aug 2026, NOVA release, NSDA pp. 32-37, UCS, CX. New in this pass: DOE's own 'cannot melt' wording, which qualifies safe-025's 'not meltdown-proof, per DOE limits' framing; logged in verify_log. | Correction 2026-09-29 (calculation audit): 'twice the AGR test rate' now twice unspecified 'AGR-1/2 test program values'. | Correction 2026-09-29 (wording review): verification wording updated ('summary line').
claim holds upfunding 'Each company will be responsible for all costs': Valar's federal award is $0, as DOE said; help in kind is unpriced
disc-046

What was said

What the record shows

The gap: None on cash: the record shows $0 in federal money, as DOE said. The public value of DOE's free review, the federal fuel route and the Los Alamos test is not stated anywhere.
In plain termsDOE said companies in its pilot program pay their own way, and the federal spending database agrees: Valar's DOE agreement carries $0. That claim holds. What the $0 leaves out is help that is not cash: DOE reviews Valar's safety papers at no charge, the fuel came from a federal nuclear site on terms that are not public, and a national laboratory ran Valar's first core test. None of that has a published price tag.

Why it matters: Fairness on money: no federal grants; the unpriced help is the open question.

What would settle it: FOIA to DOE Idaho Operations Office for the OTA and DOE staff and contractor hours spent on Valar's reviews; FOIA to NNSA for the NOVA agreement and costs.

facts orig-041, orig-055, gov-003, fund-011, fund-012, gov-032 · checked 2026-09-29: Defence pass 2026-09-29: Re-checked: USAspending shows $0 obligated on DENE0009560; DOE's fuel-line release applies the same 'responsible for all costs' rule to fuel lines. In-kind help (DOE review time, federal fuel route, Los Alamos test) remains unpriced. Holds. Summary line literally true. | Earlier verify pass: Re-read on 2026-09-29: DOE selections release (quote exact), USAspending award record (re-fetched: $0; 2025-10-22 to 2027-07-04; Idaho Operations Office), Hogan Lovells. | Correction 2026-09-29 (wording review): verification wording updated ('summary line').
claim holds uptimeline 'The first-ever C-17 airlift of a nuclear reactor': holds as worded; it flew unfueled, in pieces
disc-045

What was said

What the record shows

  • World Nuclear News: the reactor was loaded 'without its nuclear fuel' and flown from California to Hill Air Force Base on 15 February 2026.
    US microreactor transported by air (World Nuclear News, 2026-02-18)
  • The Partnership for Global Security: what flew was 'a single, non-operational, and unfueled unit, delivered in three pieces', and 'not the first time a small reactor had been transported by the US military' (on other aircraft).
    A Hollywood Highlight Reel for the Nuclear Renaissance (Ken Luongo) (Partnership for Global Security, 2026-03-13)
  • Neutron Bytes captioned the cargo as components of a 'mock up'; Valar says the modules were Ward 250 itself, and no record read shows otherwise.
    Questions Abound About Valar Atomics (Dan Yurman) (Neutron Bytes, 2026-02-28)
The gap: None as worded: no earlier C-17 reactor airlift was found. Broader 'first air transport of a reactor' framing in coverage does not hold, and the flight carried no fuel.
In plain termsValar says Ward 250 was the first nuclear reactor ever flown on a C-17 cargo plane, and no record contradicts that. It flew without fuel, in pieces, which is the safe way to move it. The U.S. military had flown small reactors before on other aircraft, so 'first reactor ever flown' would not hold; Valar's own wording is narrower and holds.

Why it matters: Fairness: a claim that holds, with its scope stated.

What would settle it: Settled as worded.

facts orig-030, orig-027, orig-066, orig-073, safe-012 · checked 2026-09-29: Defence pass 2026-09-29: Re-checked: Castle Country wording ('the first-ever C-17 airlift of a nuclear reactor'), WNN (unfueled), PGS (earlier small-reactor transports on other aircraft), Neutron Bytes. No earlier C-17 reactor airlift found. Holds as worded. Summary line literally true. | Earlier verify pass: Re-read on 2026-09-29: Castle Country, WNN, PGS, Neutron Bytes (quotes exact). | Correction 2026-09-29 (wording review): verification wording updated ('summary line').
claim holds uptimeline 'Seven months to take Ward 250 critical' and 'nine months ago, an empty site': both hold; the hardware is older
disc-047

What was said

What the record shows

The gap: None as worded: both time spans match the record. 'Record time' is true of the Utah site and the step from the Nevada test, not of the reactor hardware, which came from earlier work in California.
In plain termsValar's two headline timings check out. From its test core going critical in Nevada in November 2025 to Ward 250 going critical in June 2026 was seven months; from an empty site in September 2025 to criticality was nine. The reactor hardware itself was older: much of it came from Valar's practice reactor, built over about ten months in California before that. Fast, as claimed, measured from the Utah start.

Why it matters: Fairness: speed claims that hold, with their starting points stated.

What would settle it: Settled by the dates in DOE's and Valar's releases.

facts orig-015, orig-060, orig-005, orig-008, orig-007 · checked 2026-09-29: Defence pass 2026-09-29: Re-checked: Series B ('It took seven months to take Ward 250 critical'), NOVA (17 Nov 2025), DOE release (18 June 2026; 'Nine months ago, this was an empty site'), groundbreaking 11 Sept 2025 (joint release of 17 Sept). Both spans hold. Summary line literally true. | Earlier verify pass: Re-read on 2026-09-29: Series B, DOE release (quote exact), NOVA release (17 Nov 2025, 11:45 AM PT), technology page, July 2025 slide 7 (image), TechCrunch 2025. | Correction 2026-09-29 (wording review): 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

The gap: None for Emery County: Valar went before local bodies often and opened its site. The claim does not extend to the Carbon County site (disc-029), 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 an Orangeville councilman called it 'very transparent.' That record deserves credit. Meeting minutes are summaries, so they cannot show how complete each answer was. The same openness did not reach Carbon County about the Wellington site before the state approved it; 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 (disc-029).

facts loc-027, loc-007, loc-033, csite-028 · checked 2026-09-29: Defence pass 2026-09-29: Re-checked: the Emery record of repeated public appearances and the Orangeville councilman's remark stand; the limit (Carbon County, disc-029) is stated. Holds for Emery County. Summary line literally true. | Earlier verify pass: Re-read on 2026-09-29: Castle Country (quote exact), Ferron 15 Apr and Orangeville 9 July minutes (quote exact), Carbon 19 Aug minutes; the count of appearances rests on loc-027. | Correction 2026-09-29 (wording review): verification wording updated ('summary line').
claim holds upsite Valar told the state no young faults lie within the Carbon site: that holds on the state's fault map
disc-048

What was said

What the record shows

The gap: None: the applicant's statement matches the state's fault map. Its 'low-seismicity zone' description was not tested.
In plain termsValar told the state its Carbon County site has no geologically young faults running through it, and the Utah Geological Survey's map agrees: the nearest mapped faults are about 14 miles away. That is what the company claimed, and it checks out. A final judgment on earthquake risk would come from a site-specific study, which does not exist yet for a Carbon reactor.

Why it matters: Fairness: a site claim that checks out.

What would settle it: Settled against the state fault map; a site-specific seismic study would come with any license application.

facts mine-040, csite-009 · checked 2026-09-29: Defence pass 2026-09-29: Re-checked: UGS fault query from the centre of Section 16 (nearest mapped faults 22.9-24.0 km). Holds. Summary line literally true. | Earlier verify pass: Re-read on 2026-09-29: TLA September memo (quote exact); UGS query re-run in this pass from about 39.608 N, 110.692 W (center of Section 16 estimated from the BLM grid in dir-001/dir-002): Price River Area faults at 22.9 and 24.0 km, nothing closer. | Correction 2026-09-29 (wording review): 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 table supports the commissioner's statement. (The board chair's remark that this was the 'first year in history' with none does not hold: the table shows none since 2020.)
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 table agrees: no Carbon County mine has reported coal since 2019. That is the economic background every local decision about Valar sits in.

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-09-29: Defence pass 2026-09-29: Re-checked: UGS Table 2.8 shows no Carbon County coal output after 2019. Holds. Summary line literally true. | Earlier verify pass: Re-read on 2026-09-29: 17 Sept auto-transcript (quote exact) and UGS Table 2.8 (re-downloaded). | Correction 2026-09-29 (wording review): verification wording updated ('summary line').