Kaizen-3C infinity mark Kaizen-3C

memory-safe migration · evidence with every delivery

Memory-safe code,
with the proof attached.

We migrate critical C libraries to memory-safe Rust or hardened C — and deliver evidence, re-runnable by the customer, that the new code behaves exactly like the old. Every delivery comes with a differential check the customer runs themselves: one command, their machine, their inputs. The translation is becoming free. The proof is not.

Run the check → copied to clipboard

Proof in public — run the check

0 unsafe · 265 commands

bzip2-safe-rs · C → Rust

bzip2 1.0.8 in Rust with zero unsafe code — byte-for-byte identical to the C reference over 265 commands, including malformed streams, with a single make check.

see the proof →
12/12 byte-identical

libtiff-rs · C → Rust

libtiff's TIFF decode path in Rust, unsafe forbidden crate-wide — TIFF files decode to the same pixel bytes as the C library, re-checked in public CI.

see the proof →
2 targets · 0 diffs

qoi-safe-c · one decoder, both ways

One C image decoder taken both ways — safe Rust and hardened C — each byte-identical to the original, checked in CI on x86-64, ARM64 and big-endian.

see the proof →

What's shipping

What does the 3C mean?

code · compose · compliance

A reframing of the original Kaizen 3C method (Concern · Cause · Countermeasure) — born on Toyota factory floors as a structured problem-solving discipline — for the software industry.

Code
The legacy artifact you need to evolve. What's in front of you.
Compose
ADR-driven decompose, then recompose. How you understand the system before changing it.
Compliance
Auditable, governable, ratifiable change. Not a checkbox bolted on after — the emergent property of doing the architecture right.