FLUX DOCUMENTATION SYSTEM Layer 2 — PROTOCOL | archive flux.dantesisofo.com/wiki/archive/
The FLUX archive is a static website presenting the complete chronological record of every published FLUX issue.
It is not a portfolio. It displays everything, in order. The archive is the system made visible.
The explore interface provides five views:
| View | Description |
|---|---|
| GRID | Thumbnail grid of all photographs, chronological |
| LIST | Table view with filename, timestamp, issue, download links |
| SEQUENCE | Continuous vertical scroll, full width, one frame per row |
| PUBLICATIONS | Index of all issues, newest first, with PDF and ZIP links |
| PROTOCOL | The FLUX protocol page |
https://flux.dantesisofo.com/ ← explore interface
https://flux.dantesisofo.com/explore.html ← same
https://flux.dantesisofo.com/issues/FLUX_NNN/ ← individual issue page
https://flux.dantesisofo.com/FLUX_ISSUES/FLUX_NNN/FLUX_NNN.pdf
https://flux.dantesisofo.com/FLUX_ISSUES/FLUX_NNN/ORIGINALS.zip
https://flux.dantesisofo.com/FLUX_ISSUES/FLUX_NNN/manifest.csv
https://flux.dantesisofo.com/timeline.json ← complete archive data
https://flux.dantesisofo.com/catalog/ ← catalog index
https://flux.dantesisofo.com/catalog/CAT_NNN/ ← individual catalog issue page
https://flux.dantesisofo.com/FLUX_CATALOG/CAT_NNN/manifest.json
https://flux.dantesisofo.com/FLUX_CATALOG/CAT_NNN/contact_sheet.jpg
https://flux.dantesisofo.com/FLUX_CATALOG/CAT_NNN/{title}.pdf
https://flux.dantesisofo.com/generator/ ← public generator
https://flux.dantesisofo.com/wiki/ ← this wiki
https://flux.dantesisofo.com/{project-slug}/ ← collaborative projects
Each issue page at https://flux.dantesisofo.com/issues/FLUX_NNN/ contains:
The FLUX system has two distinct archives, each with its own namespace, URL structure, and index.
Dante Sisofo's chronological record. Every session, in order. The full timeline is navigable from the explore interface. Issue pages live at /issues/FLUX_NNN/.
A collection of issues submitted by photographers using the public generator. Each entry is reviewed and approved before publication. Catalog pages live at /catalog/CAT_NNN/.
The two archives share a protocol, a visual language, and a PDF structure. They are separate records with separate numbering systems. A catalog entry is not part of the personal archive sequence, and a personal issue is not part of the catalog.
See PUBLIC CATALOG for the submission process and the full distinction.
| File | Location | Contents |
|---|---|---|
FLUX_NNN.pdf |
Issue page | Complete 44-page publication (36 photographs) |
ORIGINALS.zip |
Issue page | All original source JPEGs |
manifest.csv |
Issue page | Per-frame metadata (EXIF, GPS, filenames) |
contact_sheet.png |
Issue page | Contact sheet at 300 DPI (6 × 6 grid) |
timeline.json |
Archive root | Complete archive data (all issues, all frames) |
| File | Location | Contents |
|---|---|---|
{title}.pdf |
Catalog issue page | Complete 44-page publication (36 photographs) |
manifest.json |
Catalog issue page | Per-frame metadata (timestamps, GPS, filenames) |
contact_sheet.jpg |
Catalog issue page | Contact sheet JPEG (6 × 6 grid) |
Every published issue generates these files in FLUX_ISSUES/FLUX_NNN/:
FLUX_NNN.pdf — complete publication
manifest.csv — frame-level metadata
issue.json — machine-readable issue metadata
cover.png — cover image at 300 DPI
contact_sheet.png — contact sheet at 300 DPI
derivatives/*.JPG — web-optimized images (1400 px long edge)
thumbnails/*.JPG — contact sheet thumbnails
ORIGINALS.zip — original source files
Before an issue is formally published, new photographs enter the FLUX Queue (FLUX_QUEUE).
The queue holds photographs that have been processed but not yet assigned to a numbered issue. The queue is visible in the public archive as an unnamed, unnumbered stream of recent work.
When the queue accumulates enough photographs for a session, the issue is formally published and the queue entries become a numbered issue.
Queue photographs are always uploaded to S3 on every deploy, so the archive always reflects the most recent unprocessed work.
| Asset type | Cache-Control | Rationale |
|---|---|---|
explore.html, timeline.json |
no-cache | Updated every deploy |
style.css, script.js |
5 minutes + content hash | Propagates without invalidation |
Issue pages (index.html) |
no-cache | May change on rebuild |
| Photographs, PDFs, ZIPs | 1 year immutable | Content never changes |
The archive is fully reproducible. Given the original photographs and the generator scripts, the entire website — all HTML, all derivatives, all contact sheets, all PDFs — can be regenerated from scratch.
The manifest CSV, archive JSON, and metadata are all publicly downloadable. A researcher, archivist, or future system can reconstruct the complete record from these files.
FLUX is built to last. The archive that exists today should be legible and usable in twenty years, regardless of whether the specific tools that built it still exist.
| Document | Layer | Relationship |
|---|---|---|
| GENERATOR | Layer 4 — Infrastructure | The tool that builds the archive contents |
| CATALOG | Layer 4 — Infrastructure | The public catalog namespace (CAT_NNN) |
| PRESERVATION | Layer 7 — Preservation | Cryptographic verification and decentralized redundancy |
| ZINE SPECIFICATION | Layer 2 — Protocol | The PDF format that lives inside the archive |
| BOOTSTRAP | Layer 4 — Infrastructure | The NAS architecture that underpins the archive |
FLUX_WIKI_v1.1 — flux.dantesisofo.com/wiki/archive/