Skip to content

fusion control verdict determinism

rg78803 edited this page Sep 8, 2026 · 1 revision

A plasma control law whose verdict is the same integer on every machine

LIBRARY        MATERIALS
IDENTITY_KIND  CONTENT_DIGEST
IDENTITY       f49b576e073835bcab17bee10fe0eee1938774643d900b8ffe1a583b159ab3d7
DIGEST_OF      the ordered verdicts of the exact fusion control law over its whole published corpus
TITLE          The exact fusion control law β€” 2,992 verdicts, one machine-independent digest
MEASURED       400 streaming traces plus a 2,592-point operating-point grid give 2,992 verdicts, and the ordered verdicts digest to a single sha256 that is the same on every machine, because every verdict is an exact integer comparison with no accumulation and no platform math.
PROGRAM        fusion-determinism-digest
FIGURE         VERDICT DIGEST (sha256): f49b576e073835bcab17bee10fe0eee1938774643d900b8ffe1a583b159ab3d7
FIGURE         corpus: 400 streaming traces + a 2592-point operating-point grid = 2992 verdicts
SEAL           f49b576e073835bcab17bee10fe0eee1938774643d900b8ffe1a583b159ab3d7
GRADE          MEASURED
WHERE_THE_LAW_LIVES  reproduce/fusion-determinism-digest.swift, over the single law in app/FusionCourt/Sources/FusionLaw β€” compiled in, never copied, so the law cannot fork
REFUSED        not a claim that the law controls a real plasma. No machine data is behind these verdicts and the study that grades this lane says so on its face
REFUSED        not an energy-gain claim. A prior-era headline of Q = 1.8 traces to an input parameter of a test fixture, and this programme published that correction against itself
REFUSED        not a reactor design and not an operating procedure
FALSIFIER      a second machine computing a different digest from the same corpus, which is precisely the failure this architecture exists to make impossible
REPRODUCE      cd reproduce && d=$(mktemp -d) && cp fusion-determinism-digest.swift $d/main.swift && xcrun swiftc -O -swift-version 5 ../app/FusionCourt/Sources/FusionLaw/*.swift ../app/FusionCourt/Sources/FusionOperatingPoint/*.swift $d/main.swift -o /tmp/run && /tmp/run
NOT_ADVICE     Nothing in this entry is medical advice and it is not a recommendation to take anything.
ADDED          2026-09-07

🧬 CURES β€” read in this order

Each step is the reason the next one exists. Nothing here is medical advice, and no page calls any medicine safe or unsafe.

1 Β· Why an exact safety screen at all

2 Β· The three libraries, which grow rather than close

3 Β· The maps β€” every place a molecule could act, counted

4 Β· One medicine at a time

  • Zilganersen β€” the first treatment for Alexander disease, screened on the real approved sequence
  • A drug an AI designed β€” rentosertib for pulmonary fibrosis, and exactly what our instruments reach
  • CAR-T, halted β€” the verdict a regulator could re-derive
  • N-of-1 antisense β€” the only safety net at a population of one
  • VERVE-102 β€” the off-target lattice a stranger can re-derive
  • PM359 β€” prime editing, certified before anyone is dosed
  • Del-Zota β€” the one safety question that can be made exact

5 Β· What keeps a disease alive, and what moves it

βš–οΈ How to read any page here

πŸ”¬ The method β€” exact against float, domain by domain

The same move every time: take a domain where a floating-point model is the accepted instrument, compute the same quantity in exact integers, and seal the cases where the two render opposite verdicts. The subject under grading is always the instrument, never the phenomenon.

⚑ Fusion β€” the energy case

🌍 The planet, and the sky

πŸ› Markets, money and risk

βš›οΈ Run a court yourself

πŸ“’ Program ledger β€” every study by lifecycle

A study appears here under the state its evidence has earned, and above under the question it answers. The two are different filings of the same work, on purpose.

βœ… LAW FROZEN Β· DATA SEALED

πŸ”΄ LIVE CLAIM β€” standing, not sealed

🌊 CHARTER Β· OPEN β€” the findings, published either way

β˜€οΈπŸŒ‘ Eclipse 2026 β€” Study 01, DATA SEALED

πŸ”¬ Discoveries and flows

Clone this wiki locally