Responsible Disclosure

A deliberate split between what is published openly and what is held back keeps the program both credible and safe.

Openness and restraint, together

Credibility in fusion requires openness — a public physics basis, reproducible results, peer review. Responsibility in a dual-use domain requires restraint — no weapons detail, no sensitive specifics, no named affiliations. Responsible disclosure is the discipline of doing both at once, deciding case by case what belongs on each side of the line.

What is published

• The public physics basis and design points (Q_sci 3.076, plug design, TBR levers) with reproducible results.
• Honest gates, timelines, and failure modes — the readiness story in full.
• Standards and compliance intent, at the level of principle.
• Product roles (tritium, helium-3, neutrons, resilient power) described conservatively.

What is held back

Weapons-relevant detail, classified content, controlled technical data, named defense personnel or affiliations, site-specific security configurations, and any claim that would outrun the evidence. A public/private split is maintained at the repository level — public repositories carry only public content, and confidential material is firewalled out and verified against leakage.

The two-edition discipline used across Kronos publications — a public-light edition and a confidential edition with a strict marker firewall — is the same principle applied to documents. Responsible disclosure is what lets the program invite scrutiny without creating risk, and it is a precondition for defense engagement.