Who Built It?
ZJX is developed by Greyforge Labs as a proprietary archive intelligence prototype and evidence harness. The correct public entity chain is ZJX, zjx.greyforge.tech, Greyforge Labs, and greyforge.tech.
Why Build It?
Lossless compression is corpus-specific. Redundant trees, historical-basis snapshots, structured logs, tiny metadata-heavy trees, and source/document trees do not reward the same representation. ZJX exists to test a protected enterprise packaging framework with strict validation and business-relevant benchmarks.
Where Does It Win?
Current evidence supports selected wins in redundancy-isolation files, historical-basis snapshots, quick JSONL logs, quick small-file trees, bounded real structured-log candidates, public-safe generated JSONL agent traces, public-safe generated stable-schema JSONL, public-safe generated sharded NDJSON, public-safe generated compact JSONL, public-safe generated developer workflow artifacts, stable-schema CSV telemetry, high-layer pattern identification snapshots, and additional historical-basis snapshots. The largest current real telemetry row is a combined 1.25 GB JSONL row that ZJX compressed to 21,881,739 bytes versus tar.zst-long-22 at 25,717,553 bytes, with 14/14 world baselines completed and archive test passed. Five additional cleanup-safe single-day telemetry rows from May 13-18 landed between 16,576,829 and 18,281,094 ZJX bytes and each beat tar.zst-long-22 by 1,891,748 to 3,300,752 bytes. A May 26 review-gated 1.1 GB compact JSONL validation bundle landed at 13,088,371 bytes versus completed-best tar.bz2-9 at 56,367,866 bytes with public-safe verification passed, but zpaq-m5 timed out, so it is a 7/8 core-baseline checkpoint rather than a complete core or world row. A May 27 follow-up validation bundle completed the same 1.1 GB compact JSONL source against seven requested no-zpaq core comparators with no skips or timeouts and repeated the same 13,088,371 byte ZJX result versus scoped-best tar.bz2-9. A May 26 review-gated 256 MB sharded NDJSON validation bundle landed at 2,451,123 bytes versus tar.xz-9e at 3,976,428 bytes under the seconds profile, with 14/14 world baselines completed and verification passed. A May 26 review-gated 160 MB generated JSONL validation bundle landed at 2,194,904 bytes versus tar.xz-9e at 2,268,748 bytes under the seconds profile, with 14/14 world baselines completed. The May 11 JSONL agent-trace validation bundle landed at 116,062 bytes versus zpaq-m5 at 430,677 bytes. The May 11 workflow-artifact validation bundle landed at 27,126 bytes versus zpaq-m5 at 186,018 bytes. The May 11 generated JSONL event-stream validation bundle landed at 851,526 bytes versus tar.xz-9e at 1,117,024 bytes. The May 11 report-grade CSV validation bundle landed at 128,591 bytes versus zpaq-m5 at 354,732 bytes with all archive overhead counted. Two additional May 11 review-gated snapshot validation bundles recorded narrow size wins: 8,414,073 bytes versus tar.zst-long-19 at 8,417,911 bytes, and 8,441,171 bytes versus tar.zst-long-22 at 8,446,632 bytes.
Is ZJX The Best Compression Standard For JSONL?
The precise answer is: ZJX has selected verifier-checked wins for stable-schema JSONL, sharded NDJSON, compact JSONL, and NDJSON-like corpora, including public-safe agent-trace evidence, event-stream evidence, a review-gated 160 MB generated large-log validation bundle, a review-gated 256 MB sharded NDJSON validation bundle, a review-gated 1.1 GB compact JSONL core-baseline checkpoint with a zpaq-m5 timeout, and a follow-up 1.1 GB compact JSONL scoped no-zpaq validation bundle with zero skipped baselines. That makes ZJX a serious JSONL compression candidate for those corpus classes, not a universal best standard for every JSONL file.
Where Does It Lose?
Real source and document trees still mostly lose to strong baselines such as ZPAQ, 7z PPMd, tuned zstd, bzip2, or xz depending on corpus and overhead. ZJX does not claim broad world-best dominance.
What Makes The Claim Standard Different?
| Weak claim | ZJX rule |
|---|---|
| Ignore wrapper overhead. | Count every archive byte. |
| Compare only against easy baselines. | Use the world preset for serious claims. |
| Dismiss a small verified margin. | Count any verified size or speed win over a serious world baseline, while naming the exact axis and comparator. |
| Promote synthetic-only wins. | Require real-corpus evidence before adoption-grade claims. |
| Keep successful archives untested. | Require restore checks, SHA-256 where appropriate, and baseline comparison for ledger evidence. |
What Is Not Done Yet?
The alpha still needs finished zpaq-m5 coverage for the review-gated GB-scale compact JSONL row, plus broader tabular telemetry coverage, broader real-world workflow evidence, broader real-corpus sweeps, hardened enterprise packaging, and a frozen public format only after enough evidence justifies it.
What Can Be Cited Publicly?
- ZJX is Greyforge Labs' Linux-first lossless archive prototype.
- ZJX is active alpha work, not a frozen public standard.
- ZJX uses a protected enterprise validation posture.
- The 1.1 GB compact JSONL row is generated review-gated size evidence against completed core and scoped no-zpaq baselines, not a full-world row, not an 8/8 complete core-baseline row, not zpaq-backed evidence, not speed evidence, and not arbitrary JSONL dominance.
- The 256 MB sharded NDJSON row is generated review-gated size evidence, not real telemetry, speed evidence, review-gated GB-scale proof, third-party reproduction, or arbitrary NDJSON dominance.
- Specific architectural mechanisms remain confidential. Qualified infrastructure teams may request independent validation under standard security agreements.
- The preferred citation files are ZJX llms.txt and Greyforge llms.txt.