TransformOS · live demo

Drag a legacy payroll batch. Watch it modernize with byte-exact parity.

No slides. The panel below holds a real mainframe batch — EBCDIC text, COMP-3 packed-decimal money. Run the sample, drop in your own batch, or inject an exception to watch a drifted record get held for review. Every field is decoded from raw bytes, the legacy totals are matched to the cent by an independently recomputed native pipeline, a governed verdict decides cutover, and the signed receipt verifies green in the public verifier.

PRMAST.2026-06-12.BATCH

EBCDIC-CP037 · COMP-3 packed decimal

496 bytes
loading raw batch…

This is the unmodified binary a mainframe would hand you — not a CSV. Names are EBCDIC; pay amounts are sign-nibbled packed decimal.

Record contract

Or bring your own batch

No copybook? We decode against the bundled PRMAST contract. Your bytes never leave this run.

Ingest

Raw EBCDIC + COMP-3 batch off the mainframe

Byte-exact decode

Copybook-driven, field-by-field, with hex audit

Parity proof

Legacy == native, recomputed to the cent

Governed review

Cutover verdict from the governed model

Governed Receipt

Ed25519-signed, verifies at lockedinlabs.ai

Why this isn't a mockup

Most "modernization demos" show a converter. This shows the proof a regulated team actually needs.

01

It reads the bytes, not a CSV

Names come in as EBCDIC code page 037. Pay amounts are COMP-3 packed decimal with the sign in the last nibble. TransformOS decodes the actual wire format off the mainframe — the format that quietly corrupts data when a converter guesses.

02

Parity is recomputed, not asserted

The native pipeline re-derives gross, federal tax, and net from inputs using the modernized rule engine, then compares to what the legacy system stored — field by field, to the cent. Drift becomes an exception. Nothing is swallowed.

03

Cutover leaves evidence anyone can re-check

Each run emits a Governed Receipt — an Ed25519 signature over the canonical body plus a prev_hash evidence chain. Paste it into the public verifier at lockedinlabs.ai/verify and it goes green, offline, with nothing of ours in the trust path. It's what a change-control board signs.

From demo to estate

Your batch is bigger than eight records. The proof model is the same.

TransformOS runs the same decode → parity → governed-review → signed-receipt loop against real DB2 estates, copybook-heavy interfaces, and stored-procedure surfaces — close to your environment, with every exception visible and every cutover documented.