Object
SAAR v7
A complete object with original length, metadata, payload and an SHA-256 envelope digest. Stored bytes remain a valid fallback.
Developers · Formats
Versioned bytes.
No silent changes.
Saar makes the format, version and recovery contract explicit. A faster or smaller engine does not get to break data you already stored.
ObjectSAAR v7current
StreamSAST v3current
CompatibilitySAST v2 readableexplicit
RecoverySource bytesmandatory
Formats
One recovery contract, explicit containers.
Each format has a different delivery purpose. The common rule is that a successful decode returns the original bytes and integrity failure is explicit.
Stream
SAST v3
Ordered, checked chunks with a complete transcript. SAST v2 remains readable and explicitly writable for compatibility.
Bundle
Saar Bundle draft
A portable multi-file container in draft. It is not a published standard and is not presented as a ZIP/TAR replacement yet.
Encryption
Experimental wrapper
A local AES-256-GCM wrapper for experiments. It is not QNSI key management and is not an independent security review.
Limits
Bounded, not unbounded by accident.
Objects, stream chunks and workers have explicit bounds. Output limits are enforced during extraction and verification.
SAAR v7 objects
Maximum object size: 16 MiB. Longer inputs are split into independent chunks.
SAST v3 streams
Maximum chunk: 16 MiB. Up to 64 workers.
Compatibility history
Versions you can rely on.
Version numbers change only when the bytes on the wire change. The history below comes from the public product catalog.
| Change | Version | Status |
|---|---|---|
| Readers for modes 1–4 Historical strand representations are retained for decoding only; no current encoder emits them. | Legacy | Current / historical |
| Objects with separate digests Source and envelope digests were recorded independently. V5 objects remain readable. | V5 | Current / historical |
| Stored & general envelope One SHA-256 over the complete encoded envelope, a 49-byte binary overhead, and stored fallback that bounds expansion. V6 remains the envelope for stored and non-binary chunks, and old objects stay readable. | V6 | Current / historical |
| Compact binary objects The active compact binary strand envelope. It carries only what the frame cannot: no repeated size or modality fields. v7 is emitted for compressed binary chunks; other modalities still use v6. | V7 · current | Current / historical |
| Checked stream chunks Independent chunks with a whole-stream digest and completeness check at end of stream. | SAST v2 | Current / historical |
| Parallel stream workers The POSIX native CLI encodes and decodes chunk batches across host threads while an ordered transcript digest verifies the stream. Windows currently uses the serial path. | SAST v3 · current | Current / historical |
| Accelerator kernels GPU, FPGA and multi-device execution are design directions until a single-device kernel beats its CPU control. | Research | Planned |