---
title: PUBLIC CATALOG
slug: catalog
layer: INFRASTRUCTURE
layer_order: 2
order: 32
description: The public FLUX catalog — community issues, submission protocol, and the CAT_NNN namespace.
---

> **FLUX DOCUMENTATION SYSTEM**
> Layer 4 — INFRASTRUCTURE | catalog
> flux.dantesisofo.com/wiki/catalog/

# PUBLIC CATALOG

The public FLUX catalog is an open archive of photographic issues made by photographers using the FLUX protocol.

Anyone can submit.  
Not everything is published.  
What is published is permanent.

---

## TWO ARCHIVES, ONE PROTOCOL

The FLUX system contains two distinct archives. They share a protocol but occupy separate namespaces.

---

### THE PERSONAL ARCHIVE

Dante Sisofo's personal chronological record.  
Issues numbered `FLUX_001` through `FLUX_NNN`.  
Sequential. Continuous. A single photographer's unbroken timeline.

This archive is not open to contributions. It is a single-author document.

---

### THE PUBLIC CATALOG

A curated collection of issues made by photographers outside the personal archive.  
Issues numbered `CAT_001` through `CAT_NNN`.  
Each entry is a standalone artifact — a complete FLUX issue, reviewed and published.

This archive is open to contributions. It grows through participation.

---

## THE DISTINCTION MATTERS

A `FLUX_047` issue and a `CAT_003` issue are made using the same protocol, the same generator, the same 36-photograph standard, the same PDF layout.

They are not the same kind of record.

`FLUX_047` is an entry in a single photographer's lifelong chronological sequence. Its place in the archive is determined by when it was made relative to every other session in that photographer's life.

`CAT_003` is a standalone published artifact. It is numbered in the order it was approved, not the order it was made. It carries its own identity. It belongs to its photographer, not to anyone else's timeline.

The protocol is shared. The records are separate.

---

## WHAT A CATALOG ENTRY IS

Every catalog entry is a complete FLUX issue:

- 36 photographs, in chronological capture order
- A publication PDF (44 pages — cover, protocol page, 36 frames, contact sheet, manifest, blank back)
- A contact sheet (6×6 grid of all frames)
- A manifest (frame list with timestamps and GPS coordinates)
- A permanent catalog page at `flux.dantesisofo.com/catalog/CAT_NNN/`

The catalog page contains the full image sequence, downloadable PDF, and frame index — the same structure as a personal issue page.

---

## HOW TO SUBMIT

**Use the public generator at:**  
`https://flux.dantesisofo.com/generator/`

---

### STEP 1 — MAKE THE PHOTOGRAPHS

Follow the protocol. Walk. Photograph. Work quickly.  
Bring exactly 36 JPEG photographs.

The 36-photograph count is not a default. It is the standard. It is the same for every FLUX issue — personal and public.

---

### STEP 2 — GENERATE THE ISSUE

1. Open the public generator
2. Enter your name in the **Photographer** field — this becomes part of every filename. Use your real name.
3. Enter an issue title, date range, and location
4. Upload your 36 photographs (JPEG only)
5. Approve all 36 in the review queue
6. Click **GENERATE FLUX ISSUE PDF**
7. The system builds your PDF, contact sheet, and manifest automatically

**Important:** Enter your real name in the Photographer field before generating. The name you enter there is embedded in the filenames of your derivatives and your manifest. Both must match — and the generator ensures they do. A placeholder name means broken filenames.

---

### STEP 3 — SUBMIT

After generating, a submission form appears:

- **Your Name** — your name as photographer and author
- **Email** — for notification when your issue is reviewed
- **Issue Title** — required
- **Date Range** — when the photographs were made
- **Location** — where
- **Description** — optional

Click **SUBMIT TO FLUX CATALOG**. Your issue uploads directly.

---

### STEP 4 — REVIEW

Every submission is reviewed before publication.

The review is not aesthetic judgment. It is not a selection for the "best" photographs.

The review confirms:

- The submission follows the FLUX protocol (36 photographs, chronological order, complete issue)
- The submission is the photographer's own work
- The issue is complete and not corrupted

FLUX does not curate. It maintains the record.

---

### STEP 5 — PUBLICATION

If approved:

- Your issue is assigned the next available `CAT_NNN` identifier
- Your catalog page goes live at `flux.dantesisofo.com/catalog/CAT_NNN/`
- You receive an email with your catalog page URL and PDF link

The catalog number is permanent. It is not reassigned. It is yours.

---

## CATALOG NUMBERS

Catalog numbers are assigned sequentially in the order issues are approved.

```
CAT_001  CAT_002  CAT_003  ...  CAT_NNN
```

The number reflects approval order, not the date the photographs were made. A catalog entry from photographs made in 2019, submitted and approved in 2026, receives the next available number in 2026.

This is intentional. The catalog is not a chronological archive of when photographs were made. It is a record of participation — of photographers who ran the protocol and brought their issues into the public record.

---

## PERMANENCE

Once published, a catalog entry is permanent.

The catalog page does not expire. The PDF does not disappear. The photographs do not get taken down.

What is published is archived. This is not a platform. This is a record.

---

## WHAT THE CATALOG IS NOT

The catalog is not a social feed.  
The catalog is not a portfolio showcase.  
The catalog is not a competition.  
The catalog is not an exhibition.

It is a collection of issues made using a protocol.  
The protocol is the curatorial principle.  
The archive is the result.

---

## SUBMIT

`https://flux.dantesisofo.com/generator/`

---

## SEE ALSO

| Document | Layer | Relationship |
|----------|-------|-------------|
| [GENERATOR](../generator/) | Layer 4 — Infrastructure | The tool that produces catalog submissions |
| [ARCHIVE](../archive/) | Layer 2 — Protocol | The two-archive system the catalog is part of |
| [PROTOCOL](../protocol/) | Layer 2 — Protocol | The shared protocol that governs catalog entries |
| [FIELD NODES](../field-nodes/) | Layer 3 — Field | Field node submissions feed into the catalog |
| [PRESERVATION](../preservation/) | Layer 7 — Preservation | Catalog entries participate in the same cryptographic preservation system |

---

FLUX_WIKI_v1.1 — flux.dantesisofo.com/wiki/catalog/
