Early concept · in development

Optimize hard. Prove the behavior never changed.

Isomer rewrites a codebase for speed and footprint, then refuses any change it cannot machine-check against the original — and signs the proof.

isomer — telemetry_pipeline.c 3 verified · 1 dropped
dot_product · diff
12float dot_product(const float* w,13                 const float* x, int n) {14  float acc = 0.f;15  for (int i = 0; i < n; i++)16    acc += w[i] * x[i];14  float acc = dot_simd(w, x, n);17  return clamp(acc, lo, hi);18}
telemetry_pipeline4 candidates3 verified1 droppedproofs checked independently
The run

Propose, prove, or drop.

Isomer proposes many optimizations and tries to prove each one equivalent to the original. Only the ones that pass an independent checker reach your diff. The one it can’t prove is dropped — it never becomes a change you have to second-guess.

Run · telemetry_pipeline · 4 candidates
TransformationTargetSpeedupProof
SIMD vectorizationdot_product3.1×verified
Bounds hoistingclamp_bounds1.4×verified
Loop reorderfft_stage—dropped
Buffer reusering_buffer2.2×verified
1 change dropped — equivalence could not be proven, so it never reached the diff.
Equivalence certificatesigned
TransformationSIMD vectorization · dot_product
Sourcesha256 4c1a…9f20
Optimizedsha256 e83b…7a14
Equivalenceproven · checker v2.4
StandardDO-178C §6.3.4
Admissible as verification evidenceproduced at the change, not reconstructed later
The certificate

Hand the auditor the proof, not an argument.

Every accepted change ships with a signed certificate: the source and optimized hashes, the checked equivalence proof, and the standard clause it satisfies. It is produced where the change is made, so the evidence exists before anyone asks for it.

Proof, not benchmarks

A faster benchmark is a hint. A checked proof is evidence an auditor can accept.

The same bar for AI code

Hand-written or model-generated, every line is preserved exactly and optimized under the same proof requirement.

The verified library

Every proof it finds, it can find again.

Each verified transformation joins a growing library of transformation-and-proof pairs — so the set of changes Isomer can justify compounds over time.

SIMD vectorization
Dead-path elimination
Memory reuse
Loop fusion
Constant folding
& growing →
The engine

The engine only ships what it can prove.

Most tools generate a change and then test it. Isomer inverts the order: it will not surface an optimization unless it can first construct a proof of behavioral equivalence and have a separate checker verify it. The checker stays small and independent of the part that proposes changes, so trusting a result never means trusting the optimizer — only the proof.

Questions

What engineers ask first.

Is this just a faster compiler?

No. A compiler optimizes within guarantees it already owns and leaves no artifact you can hand an auditor. Isomer works on your source, proposes higher-level changes, and attaches a proof and a certificate to each one, so the result is admissible evidence rather than a faster build you still have to defend.

What happens when it can’t prove a change is safe?

It discards it. An optimization that cannot be shown equivalent is treated as a failure, not a suggestion. You only ever see changes that carry a proof the checker has already accepted.

Does it work on AI-generated code?

Yes. Isomer makes no distinction between hand-written and model-generated code — both are preserved exactly and optimized under the same proof requirement. The code whose origin you trust least is where a machine-checked equivalence proof is worth the most.

Which standards does it map to?

It is being designed around the regimes where behavioral evidence is mandatory — DO-178C in avionics, IEC 62304 in medical devices, ISO 26262 in automotive — and the audit needs of core banking. The certificate references the clause a given optimization satisfies.

We’re building Isomer now

Optimize with a proof, not an argument.

Isomer is an early concept from The Adjacent Possible. We’re building the proof-synthesis engine and the first verified transformation library, and we’re looking for avionics, medtech, automotive, and banking teams who already live by the standards.

Or write to [email protected]