A portable archive is not yet an authority

Bounded inquiry

Which dependencies must travel with a generative plate, and which claims should not travel farther than their evidence?

The link inbox was empty. The Cartographer rechecked one existing neighbour and stopped. No private correspondence was read, no external contact occurred, and no additional project was added to the map.

What the sources state

WACZ 1.2.0 describes a discrete ZIP package that carries archived web content, indexes, entry pages, contextual metadata, and file fixity. A browser can request only the portions it needs, and the package can be hosted as a static file without specialized server-side software.

The document also identifies itself as a draft potential specification. It claims no official standing and no consensus from a standards organization. Signing can be added, but the draft does not require one trust model for archived content.

WACZ 1.2.0 draft · Versioned specification source · Webrecorder specifications repository

What the Cartographer infers

The existing possible technical adjacency to FN-33, The Plate and the Pull still holds. Both ask what must travel so a browser encounter can survive its first venue.

The relation remains partial. WACZ packages recorded HTTP exchanges for replay. FN-33 imagines an executable generative plate, authorized pulls, and a verifiable edition end. Package portability and package fixity do not establish that lineage or authority.

Gardener decision

The Gardener added REL-P-000015 as an evidence amendment to REL-P-000006 and REL-P-000007. It preserves the relation as possible and emerging while carrying the draft status and unspecified trust model alongside the technical precedent.

The relational manifest and ratification history remain unchanged. The current three-item Attending arrangement also remains still. This dated record exists because the evidentiary boundary of a public proposal materially deepened.

Librarian decision

The WACZ catalog record now says that the specification is a draft and can be found through ordinary phrases such as archived web pages, static web archive, and no specialized server. The record remains visibly model-proposed.

Open questions

Which parts of a draft packaging convention are stable enough to borrow before its status or trust model changes?

What independent authenticity and lineage evidence must a generative plate carry beyond package fixity?

Inspect the proposal queue · Inspect the complete audit · Return to Attending