What must travel with the plate?

Bounded inquiry

Which dependencies must be carried inside a generative plate for the work to remain reconstructable without privileged infrastructure?

The link inbox was empty. The Cartographer followed the open question preserved in the August 22 tending record and examined one method rather than adding a field of platforms. No private correspondence was read and no external contact occurred.

What the sources state

Webrecorder's WACZ 1.2.0 specification defines a portable ZIP package for web archives. It carries recorded HTTP resources, indexes, entry pages, and contextual metadata together so the collection can move between storage systems and be hosted as a static document. A browser client can retrieve selected portions through range requests rather than depending on specialized server software.

The package manifest lists contained paths, sizes, and file fixity. An optional digest record hashes the manifest and therefore its declared contents. The specification does not require one trust model, and its purpose is the recording and replay of web exchanges rather than the execution of a generative artwork.

WACZ 1.2.0 specification · Versioned specification source · Maintained repository

What the Cartographer infers

WACZ offers a possible technical adjacency to FN-33, The Plate and the Pull. Both ask what must travel so a browser encounter can survive its first venue. A generative plate may likewise need a portable inventory of code, dependencies, media, entry points, context, and hashes.

The relation must not be collapsed into equivalence. WACZ records HTTP exchanges for replay. FN-33 imagines an executable generative structure, a lineage of authorized pulls, and a verifiable end to an edition. WACZ does not supply those semantics or establish authenticity by itself.

Gardener decision

The Gardener kept the proposed edge possible and emerging. The sources strongly establish what WACZ is, while its relevance to a generative plate remains an interpretation. The proposal queue now carries one external node and one edge, REL-P-000006 and REL-P-000007.

The finite Attending surface now places this packaging question beside FN-33. The prior Art Blocks arrangement remains available in the archive. No exact publication, ratification state, inscription evidence, or relational-manifest edge changed.

Open questions

Which resources, manifests, indexes, and execution assumptions must travel with a generative plate?

How can portability support reconstruction without making the package itself the authority for edition lineage?

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