What It Is — and Is Not

SCPN-Fusion-Core is a control-algorithm development and validation framework with explicit fidelity boundaries, fast controller-support models, native research solver contracts, and fail-closed production-parity gates. It is not a replacement for TRANSP, JINTRAC, GENE, CGYRO, GS2, DREAM, Aurora/STRAHL, or EFIT. It is not IEC 61508 / SIL certified — the repository publishes an IEC 61508 functional-safety roadmap for selected control surfaces only.

Accepted vs Blocked

✓ Validated today
Local controller contracts · reduced-order replay lanes · selected Grad-Shafranov / operator-source checks · native kernel benchmarks · formal proof slices · fail-closed benchmark gates · the accepted public FreeGS same-case free-boundary strict-parity lane · 1 accepted public reference artefact.
▲ Blocked / fail-closed
Full GENE/CGYRO/GS2 nonlinear 5D turbulence parity · full Vlasov-Maxwell parity · DREAM kinetic parity · independent mechanistic Aurora/STRAHL recycling validation · EFIT-grade free-boundary reconstruction · full 3D nonlinear MHD · production MPI / multi-GPU scaling · physical HIL / FEA-grade / certified fault tolerance.

Blocked surfaces are not marked full-order until public GENE/CGYRO/GS2, DREAM, and Aurora/STRAHL parity gates are met. Required public artefacts and thresholds are declared in validation/reference_data/full_fidelity_reference_cases.json.

Latency Taxonomy

Latency claims are reported under explicit names so reduced-order kernel timing is never confused with full hardware-in-the-loop integration.

SymbolMeaning
control.pid_kernel_step_usRust reduced-order PID kernel step (0.52 µs P50)
control.closed_loop_step_usController loop with explicit surrogate / full-physics mode
control.hil_loop_usHardware-in-the-loop integration loop (simulated scaffold, not a physical rig)

How to Judge Claims

Follow the linked reports, commands, checksums, thresholds, and accepted/blocked row status. Start with validation/reports/full_fidelity_end_to_end_campaign.md and full_fidelity_acceptance_benchmark.md, then run tools/generate_claims_evidence_map.py --check to confirm the public claim-evidence map.