A commercially viable fusion power plant can generate net electricity at grid scale.
Verification position derived from the record’s assessments; dates show when Faultline first recorded each stage.
Causal mechanisms recorded for this claim. The State Warrant above remains the authoritative current assessment.
Engineering energy-chain gap. NIF achieved target gain greater than one by producing 3.15 MJ from 2.05 MJ of laser energy delivered to the target, but the comparison excludes the hundreds of megajoules of electricity needed to operate the laser system and the experiment generated no electricity. Crossing from target or plasma gain to plant-level net electricity requires substantially higher fusion gain together with efficient drivers, heat capture, electricity conversion and low recirculating power. Magnetic-confinement programmes face a different engineering chain but the same claim-level boundary: no approach has yet exported net electricity. The resistance mechanism is not that fusion physics is invalid; it is the unresolved full-system conversion from a fusion experiment to a self-sustaining electricity-generating plant.
Materials and tritium breeding. A commercial fusion plant requires plasma-facing materials that survive neutron bombardment at intensities not yet tested at relevant fluence levels, and must breed its own tritium fuel from lithium blankets at breeding ratios sufficient to sustain operation. Neither materials performance at commercial fluence nor tritium breeding at the required ratio has been demonstrated in a fusion environment. These are threshold 2 problems — they must be solved before grid-scale operation is achievable. They are not currently active research frontiers in the same sense as plasma physics; they are known engineering gaps that will become critical as the field advances toward threshold 2.
Three-threshold sequential dependency. The claim's three thresholds are ordered and each is necessary for the next. Demonstrating threshold 1 does not demonstrate the claim; it removes one obstacle to demonstrating threshold 2, which in turn removes one obstacle to demonstrating threshold 3. This creates a sequential dependency bottleneck: evidence on threshold 2 cannot be gathered until threshold 1 is achieved; evidence on threshold 3 cannot be gathered until threshold 2 is achieved. The record will therefore remain in ESCALATING for threshold-1 evidence for an extended period before threshold-2 evidence begins to accumulate. The bottleneck is structural — it is a property of the claim's architecture, not of any specific technical difficulty.
First plant-level net electricity demonstration. The specific event that would transition this record from ESCALATING toward RESOLVING is a demonstration of net electricity at the plant level — Q > 1 relative to all energy inputs, with the excess delivered to the grid. This is expected to occur, if at all, in a private or public demonstration plant in the 2030s. It would satisfy threshold 1 and open the evidential path to thresholds 2 and 3. The attractor is clearly defined, practically anticipated, and the primary evidence target for this record's near-term development.
Historical narrative recorded for this claim. It does not override the current State Warrant.
Questions retained in this record. The current State Warrant may have narrowed or reframed earlier questions.
When threshold 1 (net electricity) is demonstrated, what pressure state should the claim enter? RESOLVING requires the claim to be on a clear trajectory toward full confirmation. But two further thresholds remain, each requiring decades of additional engineering. The Observatory has no governed procedure for a claim where a major threshold is met but the claim is far from full confirmation. This is the resolution-criteria question for this record.
Raised 2024-01-15Should the three-threshold structure generate three separate records, or does the sequential dependency justify tracking all three within a single record? The corpus lesson from FR-QE-0002 applies: claims that bundle sub-components resolving on different timescales generate bottlenecks belonging to the claim rather than the frontier. The Scope Note acknowledges this tension without resolving it.
Raised 2024-01-15Does the private fusion industry's commercial commitment — particularly the Helion/Microsoft agreement — constitute evidence for the claim, or is it prospective interest rather than demonstrated capability? The corpus has no precedent for a commercial contract as an evidence object.
Raised 2024-01-15SPARC's stated target is plasma net energy (Q > 1), not plant-level net electricity. If achieved, it would be a major magnetic-confinement milestone but would not satisfy threshold 1 because SPARC is not designed to export electricity and plasma Q excludes the plant's full energy chain. What additional evidence boundary — including all-system energy accounting and electricity delivered beyond internal plant demand — must be met before OQ-001's pressure-state question is activated?
Raised 2026-06-29| Mutation | Date | Field | Prior value | Current value |
|---|---|---|---|---|
| M-015 | 2026-09-19 | provenance_repair | LPR-001-D21 discrepancies_found / pending | LPR-001-D21 discrepancies_corrected / completed |
| M-014 | 2026-09-06 | description_restored | Legacy ingestion cutoffs: mechanisms:RM-001, mechanisms:RM-002, mechanisms:BN-001, mechanisms:AT-001, lineage:2023–24 | Source-restored complete descriptions |
| M-013 | 2026-08-27 | instance_logged | — | IN-007 |
| M-012 | 2026-07-09 | description_reordered | — | DESCRIPTION-REORDERED |
| M-011 | 2026-07-08 | realization_note_added | — | REN-001 |
| M-010 | 2026-06-29 | open_question_raised | — | OQ-RAISED |
| M-009 | 2026-06-29 | assessment_issued | AS-001 | AS-002 |
| M-008 | 2026-06-29 | instances_logged | — | INSTANCES-LOGGED |
| M-007 | 2026-06-18 | record_id_migrated | FR-MF-0004 | FR-AM-0004 |
| M-006 | 2024-01-15 | programme_panel_added | — | PROGRAMME-PANEL-ADDED |
| M-005 | 2024-01-15 | null_condition_failed | — | NULL-CONDITION-FAILED |
| M-004 | 2024-01-15 | mechanisms_recorded | — | MECHANISMS-RECORDED |
| M-003 | 2024-01-15 | assessment_issued | — | ASSESSMENT-ISSUED |
| M-002 | 2024-01-15 | instances_logged | — | INSTANCES-LOGGED |
| M-001 | 2024-01-15 | record_created | — | RECORD-CREATED |