Corerope

An open research program

Making a frontier-quality LLM roughly 1000x cheaper to run

The invented stack reaches about 750x less energy and about 260x lower cost per solved task than a late-2026 frontier deployment in the central case of its cost model. Energy passes 1000x if no task falls back to GPUs; dollars reach 1000x only in the optimistic case. The range is wide, from 15x to 46,000x in energy, because one scientific bet decides most of it: whether a ~12B-parameter ternary reasoning core paired with a huge lookup memory can match frontier quality.

Status: a design, not a result

Nothing here is proven at scale. Each part comes with the first experiment that would falsify it.

The numbers, and how sure they are

The design's cost model against a late-2026 frontier deployment (B2026), beside what the survey found every known lever can do against the same baseline.

Less energy per solved task, central case

749x

Range 15x to 46,009x. Modeled, not measured.

Lower cost per solved task, central case

263x

Range 1.9x to 10,533x. Modeled, not measured.

What the known levers give against B2026, central

~35x in dollars

~80x in energy. The survey's overlap-adjusted estimate.

Gain per task if 1% of tasks fall back to GPUs

92x

Why every task must stay on the new stack.

Central case: 749x less energy and 263x lower cost per task

How many times cheaper the Corerope stack would be than a late-2026 frontier deployment (B2026), from its cost model. The dot is the central case; the whisker runs from the pessimistic to the optimistic case.

Per solved task
Energy per task
Dollars per task
Per token
Energy per token
Dollars per token
Times cheaper than B2026 (log scale)

A model of a design, not a measurement: every input is an assumption that the experiments on this site would test.

Show the numbers
Multipliers by case
MeasurePessimisticCentralOptimistic
Energy per task (per task)15x749x46,009x
Dollars per task (per task)1.9x263x10,533x
Energy per token (per token)27x801x11,502x
Dollars per token (per token)2.9x203x2,633x

The name

Weights woven into the hardware

The Apollo Guidance Computer stored its software in core rope memory: each bit was set by whether a wire was threaded through a magnetic core or around it, so the program was literally woven into the hardware. Corerope does the same with a neural network's weights: in wired-weight silicon a weight is a connection to an adder's plus input, its minus input, or nothing.

Core rope memoryFive ring cores in a row and three wires. Each wire either threads through a core, which stores a 1, or bends around it, which stores a 0. The bits under each core read 101, 011, 110, 001 and 111.101011110001111

Core rope memory. A wire threaded through a core is a 1; a wire passing around it is a 0. The Apollo Guidance Computer's software was woven in this way, so it could not change.

A wired weightFour inputs, x1 to x4, and an adder with a plus and a minus input. x1 is wired to plus, x2 to nothing, x3 to minus and x4 to plus, so the output is x1 minus x3 plus x4.x1+1x20x3−1x4+1Σ+−x1 − x3 + x4

A wired weight. Each input is wired to an adder's plus input (+1), its minus input (−1), or nothing (0). No weight is stored, so none is ever fetched, and no multiplier exists.