T15 Orchestrator is lossless compression that returns your data byte-for-byte. Every restore is SHA-256-verified, and the output carries a +1 byte never-worse floor: it is never larger than the best standard codec (worst case +1 byte). It uses SRD math partly together with standard codecs (xz, zstd, brotli) and keeps the smallest verified output.
input -> orchestrate (SRD math + codecs) -> smallest verified .pdli -> restore -> SHA-256 match
LESS WEIGHT - SAME BYTES - VERIFIED RESTORE
No lossy promises: every result must restore the original byte-for-byte, or it stays proof-only / diagnostic.
The three guarantees
T15 Orchestrator turns any input into a restorable .pdli container and keeps only output it can prove. Three properties hold on every run.
Input is read as exact bytes. Restore reconstructs the original byte stream exactly - no lossy re-encode, no approximation, no hidden mutation. What you put in is what you get back.
Every output is roundtripped: the restored bytes are hashed and the SHA-256 must match the original. If it does not match, it is not shipped. Integrity is checked, not assumed.
Because the Orchestrator keeps the smallest verified output, it is never larger than the best standard codec - worst case +1 byte of container overhead. No fake savings on random or already-compressed data.
How the Orchestrator works
The Orchestrator does not just run one method. It applies SRD math to your data and also runs standard codecs (xz, zstd, brotli), then keeps the smallest output that passes the SHA-256 roundtrip. You get the best of both - SRD structure gains where they exist, standard-codec strength everywhere else.
Any file, folder or stream enters as raw bytes. Nothing is interpreted, transcoded or reordered before processing.
SRD math runs on your data alongside standard codecs (xz, zstd, brotli). Multiple reversible candidates are produced in parallel.
Every candidate is restored and its SHA-256 checked against the original. Only candidates that roundtrip exactly stay eligible.
The smallest verified candidate wins. Because standard codecs are in the race, the result is never larger than the best of them (worst case +1 byte).
The output is a portable .pdli container - API-ready, CLI-ready, designed for exact restore.
If no candidate shrinks the input honestly, the result is proof-only / diagnostic with exact restore preserved - never a fake win.
COMPRESS
input -> SRD math + codecs -> smallest verified .pdli
RESTORE
file.pdli -> inverse -> original bytes (SHA-256 match)
What it handles
The Orchestrator works on whatever you give it - single files, whole folder trees, and arbitrarily large inputs via streaming, so memory never has to hold the entire payload at once.
MP4, PDF, ZIP, JSON, logs, datasets, source, backups, raw bitstreams. The entry point is raw bytes, so format is irrelevant to correctness.
Point it at a folder and the full tree is compressed to a restorable container - structure, paths and byte content preserved exactly.
Large inputs stream through in bounded memory. There is no requirement to fit the whole file in RAM, so size is not a limit.
Advisory surfaces
The Orchestrator exposes advisory surfaces so you can estimate, compare and plan up front - then run with confidence.
Suggests the best path for your input class so you start from the strongest candidate, not a guess.
Projects expected size reduction before a full run, so you can size storage and transfer plans.
Shows how candidates stack up side by side so the winning verified output is transparent.
Explains the +1 byte never-worse floor and why incompressible input stays proof-only instead of expanding.
Lays out how to wire the Orchestrator into your pipeline via API or CLI without building compression in-house.
Predicts the achievable compression ratio for your data so expectations are set before the job runs.
Where it wins - and where it ties the best
Because the Orchestrator keeps the smallest verified output among SRD math and the standard codecs, it is never larger than the best standard codec (worst case +1 byte): it wins outright on structured classes and ties the best codec everywhere else. Not "superior to all", not "past any entropy bound".
FAQ
Drop a file in the browser, get a byte-exact .pdli, and confirm the SHA-256 roundtrip yourself. Then see the measured numbers.
No credit card - zero storage on the browser trial - SHA-256 byte-exact restore