---
title: ROADMAP
slug: roadmap
order: 11
description: Open-source vision, future software architecture, AI selection, infrastructure, and release stages.
---

# ROADMAP

Where FLUX is going.

---

## CURRENT PRIORITY

**Documentation and stabilization phase.**

- Lock the protocol language
- Lock the zine layout
- Lock QR code structure
- Lock naming conventions
- Build the wiki
- Clean the archive
- Standardize all existing PDFs
- Improve the generator
- Onboard first users

Do not build the future until the present is stable.

---

## SUMMER 2026

Use the summer to consolidate, not expand.

- Consolidate and document the system
- Refine existing infrastructure
- Write the manifesto
- Lock the protocol
- Build the public generator (v1)
- Help existing students begin making issues
- Prepare institutional language
- Begin FLUX Node proposal for one library

This is builder mode, not launch mode.

---

## V1 — CURRENT STATE

- Personal FLUX generator: operational (304 issues)
- FLUX archive: live at `flux.dantesisofo.com`
- Collaborative projects: Broad Street In Flux published
- Protocol page: locked
- Zine format: locked
- Wiki: building now

---

## V2 — PUBLIC GENERATOR

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

A browser-based or downloadable tool that allows any photographer to run the FLUX protocol on their own photographs.

Requirements:
- No account required
- Standard: 36 photographs per issue (canonical — same as personal generator)
- Protocol page included in every output PDF
- Output structurally identical to personal volumes
- GPS optional

The public generator is the outward-facing expression of the system's reproducibility philosophy. Anyone who scans the protocol QR code can run it.

---

## V2 — FLUX NODE (PROTOTYPE)

Physical archive terminal in one public institution.

Start extremely small. One successful node is more important than scale.

Target: a library or camera store in Philadelphia.

---

## V3 — INFRASTRUCTURE

Possible future hardware:

- Maxed-out MacBook Pro
- Mac mini (always-on local server)
- NAS archive (local backup of all originals)
- S3 bucket (current — continues as public layer)

Ideal flow:

1. Photograph
2. Transfer to phone via RICOH app
3. Phone to home machine via sync
4. Archive receives files automatically
5. Metadata extraction
6. Queue update
7. Zine generation (when threshold reached)
8. Web page creation
9. PDF + ZIP upload
10. Archive update
11. FLUX Node sync (if applicable)

---

## V3 — COLLABORATOR ONBOARDING

Once the public generator exists:

- Students begin making their own issues
- Private community shares PDFs and archive pages
- First non-Dante FLUX issues published
- A naming convention for public user issues is finalized

Possible naming:

```
FLUX_001 — PhotographerName
```

Where `FLUX_001` is the photographer's own sequential number, not Dante's.

---

## V4 — AI SELECTION

Train an AI model on:

- Original photographs
- Accepted frames (selects)
- Rejected frames
- Chronological sequences
- Metadata
- Visual preferences over time

Goal:

- Learn what the photographer keeps
- Learn what the photographer rejects
- Learn sequencing rhythm
- Automate culling
- Automate zine production

The dream:

> Go out and photograph. FLUX does the rest.

This is not the immediate priority. This is V4 or V5.

---

## OPEN SOURCE

FLUX should become open and upgradeable.

Not a closed social platform.  
Not the next Instagram.

More like:
- open protocol
- open publishing system
- open archive format
- open photographic workflow
- open-source cultural infrastructure

People should be able to use it, fork it, improve it, generate their own zines, publish their own archives, contribute fixes, build on top of it.

The generator code, the protocol specification, and the archive format should all be publicly documented and reproducible.

---

## WHAT NOT TO BUILD

- No social feed
- No likes or engagement metrics
- No algorithmic ranking
- No advertising layer
- No subscription paywall for the archive
- No proprietary file formats
- No vendor lock-in

---

## FINAL PRINCIPLE

The stronger the archive system becomes:

- the less explanation is needed
- the less manifesto is needed
- the more self-evident the concept becomes

The archive itself creates belief.

---

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