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.

CORE PRINCIPLES

Static. No server-side computation. No database. No CMS. HTML, CSS, JavaScript, JSON, and image files. Runs on any static host.
Self-contained. Every issue page contains everything needed to understand that issue: contact sheet, all photographs, manifest, PDF.
Timeline-first. Primary navigation is chronological. The timeline sidebar navigates by year, month, and day.
No editorial framing. No category labels. No thematic tags. No written commentary. Issues are identified by number and date only.
Downloadable. Original photographs, manifest CSV, archive JSON, and PDFs are all publicly available.

VIEWS

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

URL ROUTING

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/wiki/                    ← this wiki
https://flux.dantesisofo.com/generator/               ← public generator (future)
https://flux.dantesisofo.com/{project-slug}/          ← collaborative projects

ISSUE PAGE

Each issue page at https://flux.dantesisofo.com/issues/FLUX_NNN/ contains:

Issue identifier and date range
Contact sheet (full-resolution PNG)
All photographs (derivative-quality JPEGs, viewable in lightbox)
Metadata table (camera, format, page count, PDF size)
Download bar: PDF, ZIP, manifest, contact sheet
Individual JPEG download links

WHAT IS DOWNLOADABLE

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)

ISSUE ARTIFACTS

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

FLUX QUEUE

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.

CACHE STRATEGY

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

REPRODUCIBILITY

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.

FLUX_WIKI_v1.0 — flux.dantesisofo.com/wiki/archive/