FLUX DOCUMENTATION SYSTEM Layer 3 — FIELD | gallery flux.dantesisofo.com/wiki/gallery/
The gallery print is fragile.
The archive is resilient.
A FLUX print can be:
While simultaneously existing as:
This contradiction is not a problem to solve. It is the conceptual framework itself.
The physical object is disposable. The archive is eternal.
The FLUX generator currently produces issue-level outputs: the PDF, the ZIP, the contact sheet, the manifest.
The Gallery Protocol adds a parallel output layer — the single-image archival exhibition object.
Every photograph becomes multiple things simultaneously:
1. Physical print
2. Digital archive object
3. Verification object
4. Historical document
5. Cryptographic artifact
Two outputs from one session:
ARCHIVAL ISSUE OUTPUT GALLERY OBJECT OUTPUT
───────────────────── ─────────────────────
PDF issue Gallery PDF (per image)
ZIP originals Full-resolution JPEG
Manifest CSV Image metadata JSON
Contact sheet OpenTimestamp proof
Issue JSON QR verification code
The issue output is the chronological record. The gallery output is the exhibition layer. They reference each other but operate independently.
Each gallery object is a single-image archival presentation unit.
File structure:
FLUX_NNN_IMG_NNN/
├── FLUX_NNN_IMG_NNN_FULL.jpg — full-resolution original JPEG
├── FLUX_NNN_IMG_NNN_GALLERY.pdf — printable exhibition sheet
├── FLUX_NNN_IMG_NNN_metadata.json — image-level metadata
├── FLUX_NNN_IMG_NNN_manifest.txt — verification manifest
├── FLUX_NNN_IMG_NNN.ots — OpenTimestamp proof
└── QR.png — QR code linking to verify page
The full-resolution original JPEG is the canonical source object. It carries the original EXIF timestamp, GPS coordinates if present, and camera metadata. It is never recompressed or altered.
The image occupies the majority of the page.
Borders remain minimal and documentary. The aesthetic is infrastructural — not precious.
──────────────────────────────────────────────────
│ │
│ │
│ │
│ PHOTOGRAPH │
│ │
│ │
│ │
──────────────────────────────────────────────────
DANTE SISOFO
PHILADELPHIA, PA
2026-05-15 — 18:42:07
FLUX_NNN / FRAME_023
SHA256 VERIFIED
flux.dantesisofo.com/verify/FLUX_NNN/023
The bottom border contains:
The gallery layout is designed for 8.5 × 11 inch output.
The proportions scale cleanly to:
The same file at any scale. The metadata strip at the bottom remains legible regardless of print size.
The output is intentionally print-native — designed for a laser or inkjet printer, not a screen. The bureaucratic monospace metadata is part of the object, not supplementary to it.
Every gallery object links to a verification page:
flux.dantesisofo.com/verify/FLUX_NNN/023
The URL structure encodes both issue and frame. The page contains:
The verification page answers one question first:
VERIFIED
Everything else is secondary.
The FLUX issue uses 8.5 × 11 deliberately — the same sheet as a laser printer, a photocopier, a standard office. The gallery object inherits this.
The anti-precious aesthetic is structural. The work is not on archival Hahnemühle paper in a white box. It is on the same sheet you print emails on. The preciousness is in the archive, not the object.
This inverts the traditional fine art print economy:
The print can be destroyed. The archive cannot.
FLUX exhibitions do not require:
A FLUX show can be:
The impermanence of the installation is honest. The photograph was made in public space. It returns to public space. The archive preserves what the wall cannot.
In the AI era, authenticity becomes part of the artwork itself.
The photograph is no longer merely visual. It is:
A generated image can look identical to a photograph. It cannot have a timestamp proof on the Bitcoin blockchain anchored to a physical location at a specific moment in time.
The gallery object makes this provenance visible — not as a technical footnote but as a design element. The hash is printed on the object. The QR code links to the proof. The verification is part of the aesthetic.
This is not NFT culture.
The gallery object does not require:
The verification infrastructure is open, free, and archival. Anyone can verify. No transaction required.
The object is free to reproduce. The archive is free to access. The proof is free to check.
The value is in the existence of the record, not the scarcity of the object.
Every gallery object references its parent issue.
FLUX_NNN_IMG_023
↑
lives inside
↑
FLUX_NNN (issue)
↑
lives inside
↑
FLUX ARCHIVE (complete chronological record)
The gallery object is not standalone. It is a fragment of the larger sequence made temporarily visible as a single thing.
The sequence is always the primary document. The single image is always a quotation from it.
The Gallery Protocol is a planned output layer.
The current generator produces issue-level outputs. Single-image gallery objects are the next architectural layer — designed, documented here, not yet automated.
The verification infrastructure (IPFS, Arweave, OpenTimestamps) is described in the PRESERVATION PROTOCOL.
The gallery output layer will be implemented as part of Stage 2 of the preservation protocol rollout.
The gallery wall becomes temporary.
The archive becomes eternal.
| Document | Layer | Relationship |
|---|---|---|
| PRESERVATION | Layer 7 — Preservation | The verification infrastructure (IPFS, Arweave, OpenTimestamps) the Gallery Protocol depends on |
| ARCHIVE | Layer 2 — Protocol | The parent archive every gallery object references |
| PHYSICAL | Layer 6 — Physical | The print infrastructure that produces gallery objects |
| DISPATCH | Layer 3 — Field | The other physical document format — ephemeral by design |
| ZINE SPECIFICATION | Layer 2 — Protocol | The full-issue format the gallery object is extracted from |
FLUX_GALLERY_PROTOCOL_v1.0 — flux.dantesisofo.com/wiki/gallery/