Skip to content

CROSSOVER

rg78803 edited this page Sep 3, 2026 · 1 revision

The GPU crossover β€” measured, and the two instruments that lied first

Question: on this branchy, no-multiply, exact-integer verdict law, at what agent count does a Metal round-trip beat 12 CPU cores? Answer, measured on an M4 Max (40 GPU cores): it does not, up to one million agents. The CPU is ~2Γ— faster at every scale, and the GPU is bit-for-bit correct the whole way β€” its loss is a speed result, never a correctness one.

Run it yourself: swift build -c release && .build/release/FusionCourt --selftest-crossover

N CPU (12 core) GPU (round-trip) parity winner
4,096 232 Β΅s 1,037 Β΅s BIT-EXACT CPU
16,384 541 Β΅s 1,641 Β΅s BIT-EXACT CPU
65,536 1,966 Β΅s 4,349 Β΅s BIT-EXACT CPU
262,144 7,479 Β΅s 15,072 Β΅s BIT-EXACT CPU
1,048,576 29,301 Β΅s 58,969 Β΅s BIT-EXACT CPU

Why: a kernel launch is a fixed ~1 ms of encode + dispatch + read-back, and the law is abs, subtract, compare and a run counter β€” no multiply, no divide, nothing a GPU's float lanes accelerate. Twelve CPU cores doing the identical integer work pay no launch and win. This is the founder's call ("we needed it for floating point but we are not that now"), measured rather than asserted.

The two measurements that lied first β€” kept, because they are the reason to trust the third

Run 1 said the GPU wins everywhere. It was wrong: the CPU arm transposed the data column-by-column with a fresh allocation per sample and was charged 72 ms at 65,536 agents against the law's real 128 Β΅s β€” 560Γ— the law's cost, all of it allocation the GPU never paid because it got the flat layout for free. The tell was that 72 ms vs 128 Β΅s gap. A broken benchmark that flattered the GPU.

Run 2 said the crossover was 16k. Still wrong: the CPU arm allocated a fresh [Int32] per agent to widen the Int16 window. Fixed by widening into one reused scratch buffer per slab (12 total, not N) β€” and refusing to add an Int16 overload of the law, which would have re-forked the exact logic a prior phase spent itself merging.

Run 3 is apples-to-apples: same flat input both sides, the single law fed bit-exactly, no per-agent allocation. GPU never wins. Two of three runs flattered the GPU; only the instrument-corrected one is the result.

Parity is enforced as a build-time test (FusionGPUTests), not just measured here β€” the GPU verdict must equal the CPU golden bit-for-bit across a corpus that reaches at least three terminals, or the build fails.

🧬 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