Opened to the last member,
each read by its own handler.

A container is not a document; it holds them. The handler opens an archive to its members, routes each one to the handler for its own format, and keeps the path it was found at.

LLX-HANDLER-ARC · R2 · 7 formats

ziprartargzbz2cab
What it reads · 01 Structure level, not string level

Three things treating an archive as one file loses.

01

The member path

Where a file sat inside the archive is kept, so a document can be located exactly as it was disclosed.

02

Nested containers

An archive inside an archive is opened in turn, to the last member, however deep it goes.

03

Per-member custody

Each member is sealed on its own bytes, so a citation points at a file rather than at a bundle.

What it settles · 02 Where the handler earns its place

The questions bundles usually decide.

01

What was actually disclosed

Every member is listed with its path and digest, so the contents of a disclosure are established.

Disclosure
02

Whether a file was in the bundle

Absence is reported as absence, with the archive listing as the evidence of it.

Completeness
03

Which copy is the original

The same document across several archives is matched, and each copy keeps its own custody record.

Duplicates
Custody

Read in place, in the format it arrived in.

The file is never converted or re-saved. It is read where it lies, and the handler records a SHA-512 of the bytes it read — so a passage cited today can be replayed against the same file years from now.

See it on your own bundles All file formats