---
title: VERSIONS
slug: versions
layer: GOVERNANCE
layer_order: 3
order: 83
description: Version reference for the FLUX protocol, implementation, and wiki — numbering philosophy, locked semantics, and current status.
---

> **FLUX DOCUMENTATION SYSTEM**
> Layer 9 — GOVERNANCE | versions
> flux.dantesisofo.com/wiki/versions/

# VERSIONS

---

## VERSION TABLE

| Version | Date | Status | Summary |
|---------|------|--------|---------|
| v1.0 | 2026-05-13 | LOCKED | Archive launch. Frame count, PDF structure, filename convention, S3 namespace. |
| v1.1 | 2026-05-14 | LOCKED | Public catalog. CAT_NNN namespace. publish_submission.py. FLUX_CATALOG/ prefix. |
| v1.2 | 2026-05-15 | LOCKED | Physical calibration. Gutter compensation. Auto-generation trigger. File lock. |
| v1.3 | 2026-05-19 | LOCKED | Catalog stability. _next_catalog_id() fix. S3 sync on save. Catalog = 18 entries. |
| v2.0 | 2026-05-20 | CURRENT | Documentation architecture. 8-layer wiki. Intelligence layer. Hardware ordered. NAS structure. |

---

## WHAT "LOCKED" MEANS IN FLUX

LOCKED means the decision cannot be changed without:

1. Writing a new DECISION entry in the decisions log that explicitly supersedes the locked decision
2. Marking the prior decision DEPRECATED
3. Bumping the protocol version (at minimum a minor version bump)
4. Updating all dependent scripts (flux_constants.py and all files that import from it)

LOCKED is not advisory. It is not a strong preference. It is a protocol constraint.

The following are LOCKED as of v2.0:

```
FRAMES_PER_ISSUE = 36
PDF page count   = 44
PDF page layout  = as specified in DECISION-002
Canonical filename format = YYYY-MM-DD_HH-MM-SS_PhotographerName_OriginalFilename.JPG
_next_catalog_id() must scan S3, not catalog.json
_save_catalog() must immediately sync to S3
```

Changing any of these without following the protocol above invalidates the version record.

---

## VERSION NUMBERING PHILOSOPHY

FLUX uses semantic versioning with protocol-specific semantics.

### Major version bump (X.0)
A major version changes when:
- The protocol's core structure changes (frame count, PDF layout, filename format)
- The documentation architecture changes fundamentally
- A new protocol layer is introduced that restructures existing layers
- Backward compatibility with prior issues is broken

v1.0 → v2.0 was a major bump because the documentation architecture was restructured from flat to 8-layer.

### Minor version bump (x.Y)
A minor version changes when:
- New protocol capabilities are added (new pipeline, new namespace, new script)
- Bug fixes that affect protocol behavior (catalog ID collision fix)
- Infrastructure decisions that change system architecture
- New DECISION entries that extend rather than replace prior decisions

v1.0 → v1.1 was a minor bump because the public catalog was added without changing the core protocol.
v1.2 → v1.3 was a minor bump because catalog bugs were fixed without changing protocol constants.

### Patch version (x.y.Z)
FLUX does not currently use patch versions. All changes are either minor or major.

---

## THREE VERSIONED THINGS

FLUX has three distinct versioning tracks:

### Protocol Version
The specification: frame count, PDF structure, filename convention.

The protocol version increments when any DECISION marked LOCKED is created or superseded. The current protocol version is embedded in every generated PDF on the protocol page (page 3).

```
Current: FLUX Protocol v2.0
```

### Implementation Version
The codebase: flux_constants.py, generate_flux_issue.py, approve_worker.py, issue_builder_worker.py, publish_submission.py.

Implementation version increments with code changes. Implementation must be compatible with the protocol version it targets. An implementation at v1.3 code should not be used to generate v2.0 issues.

```
Current: FLUX Implementation v2.0 (tracks protocol)
```

### Wiki Version
The documentation: FLUX_WIKI/*.md, generate_wiki.py.

Wiki version increments with documentation changes. The wiki version is embedded in every wiki page footer and in the generated PDFs.

```
Current: FLUX_WIKI_v2.0
```

The three versions are synchronized at major releases. They may diverge at minor releases (e.g., the wiki can be updated without a protocol change).

---

## CURRENT STATUS

```
Protocol:       FLUX Protocol v2.0 — CURRENT
Implementation: FLUX Implementation v2.0 — CURRENT
Wiki:           FLUX_WIKI_v2.0 — CURRENT
Personal issues: FLUX_001–FLUX_423+ (as of 2026-05-20)
Public catalog:  CAT_001–CAT_018 (as of 2026-05-20)
```

---

## SEE ALSO

| Document | Layer | Relationship |
|----------|-------|-------------|
| [CHANGELOG](../changelog/) | Layer 9 — Governance | Full chronological history of all version changes |
| [DECISIONS LOG](../decisions-log/) | Layer 9 — Governance | RFC records for all LOCKED decisions |
| [PROTOCOL](../protocol/) | Layer 2 — Protocol | The versioned protocol specification |

---

FLUX_WIKI_v2.0 — flux.dantesisofo.com/wiki/versions/