FLUX ARCHIVE
[ARCHIVE] [WIKI] [DISPATCHES] [GEOTAG] [PHILLY IN FLUX] [CATALOG] [GENERATOR]
flux.dantesisofo.com
← WIKI INDEX

FLUX DOCUMENTATION SYSTEM Layer 3 — FIELD | field-nodes flux.dantesisofo.com/wiki/field-nodes/

FIELD NODES

A FLUX Field Node is a physical marker embedded in a specific location in Philadelphia.

It contains one instruction.

Photograph from here.


THE CONCEPT

FLUX began as a publishing protocol.

A photographer walks. Photographs. Sequences. Submits.

A Field Node inverts this.

Instead of the photographer choosing the location — the location chooses the photographer.

The assignment is already waiting at the corner. The photographer arrives, scans, and begins.


HOW IT WORKS

A small sticker, card, or printed marker is placed at a fixed location in the city.

The marker contains:

A person scans the code.

They receive a simple assignment: make 1–36 photographs from this exact location. Sequence them chronologically. Submit the issue to the archive.

The submission is tagged automatically:

The street corner becomes an archive node.


WHAT THE STICKER SAYS

FLUX FIELD NODE 001

PHOTOGRAPH FROM HERE.

Make 1–36 photographs from this exact location.
Sequence them chronologically.
Submit your issue to the city archive.

Scan to begin.

flux.dantesisofo.com

Nothing else.

The instruction is complete. The constraint is the assignment.


THE LIVING RECORD

A Field Node does not produce one issue.

It produces a record over time.

Same location. Different eyes. Different days. Different light. Different weather. Different people.

Each submission layers on top of the last.

The corner accumulates.

One year from now, that intersection has been photographed twelve times by twelve different people in twelve different seasons and twelve different kinds of light.

That is not a portfolio. That is a living archive. That is pure flux.


NODE IDENTIFIERS

Each Field Node is assigned a permanent identifier:

FLUX_FIELD_NODE_001

The identifier travels with every submission made from that location. It is embedded in the issue metadata, the contact sheet, the manifest, and the archive record.

The identifier links every submission made from that node — across time, across photographers, across weather — into a single coherent record.

A node is never closed. A node is never full. A node accumulates permanently.


NODE METADATA

Each node carries a permanent record:

Field Content
NODE_ID FLUX_FIELD_NODE_001
LOCATION Intersection of 40th and Walnut, West Philadelphia
COORDINATES 39.9526° N, 75.1972° W
DATE PLACED 2026-05-16
PLACED BY FLUX
TOTAL SUBMISSIONS continuously updated
STATUS ACTIVE

The node metadata is public. Anyone can inspect the archive record for any node. Total submissions, submission dates, photographer count, issue links.

The corner has a biography.


PHYSICAL FORMATS

A Field Node can exist as:

The format is secondary. The location is the node. The QR is the door.


THE CITY AS INTERFACE

A Field Assignment tells the photographer where to go.

A Field Node is already where the photographer is.

The distinction is significant.

A Field Assignment requires intention. You read the protocol. You travel to the location. You execute.

A Field Node operates on arrival. You are already standing on that corner. The sticker was waiting for you. The assignment begins without planning.

This changes the photographer's relationship to the city.

Every unmarked corner becomes a potential node. Every scan is an activation. Every submission is an addition to a record that will outlast the physical sticker.

The city is not the backdrop. The city is the archive.


WHO CAN PLACE A NODE

FLUX Field Nodes are an open protocol.

Any photographer can place a node.

Requirements: - a printed or stickered marker with the FLUX Field Node format - a registered node ID (assigned through FLUX) - placement at a fixed, specific, locatable position - submission of node coordinates and placement date

The node is logged in the FLUX Field Node registry. It becomes permanent in the archive.

A node placed by anyone is a node placed for everyone.


RELATIONSHIP TO FIELD ASSIGNMENTS

Field Assignments and Field Nodes are complementary protocols — not the same system.

FIELD ASSIGNMENT FIELD NODE
Origin Protocol document Physical marker
Location Specified by assignment Fixed by sticker placement
Photographer Chooses the assignment Discovers the node
Trigger Reading Scanning
Output FLUX issue FLUX issue tagged to node
Archive Individual issue Accumulated node record
Duration One session Ongoing, multiple photographers
Nature Directed Open

A Field Assignment is a constraint given to a photographer.

A Field Node is a constraint embedded in geography.


GHOST NODES

A Field Node may be removed.

The sticker fades. The card is torn down. The surface is painted over.

The node remains.

Every submission ever made from that location persists in the archive. The node ID persists. The coordinates persist. The record persists.

A Ghost Node is a node that no longer exists physically but remains alive in the archive.

The sticker disappears. The record does not.

Ghost Nodes are not failures. They are proof that the archive outlasts the physical marker.

A Ghost Node is the purest form of the FLUX promise: preservation is the point.


DISCOVERY

Field Nodes are discovered through:

Serendipitous discovery is preferred.

You were not looking for the node. You found it anyway. You photographed.

That is the ideal use case.


THE ARCHIVE ARGUMENT

Photography is usually organized by photographer.

Whose photographs are these? What project are they from? What style does the photographer have?

Field Nodes organize photography by location.

What has this corner looked like, through different eyes, across time?

This is a fundamentally different question.

The photographer is not absent — their name and date are in the record. But the corner is the organizing principle.

Over time, the Field Node archive becomes:

This is urban documentation at a scale that no single photographer can produce.


LONG-TERM VISION

FLUX Field Nodes placed throughout Philadelphia.

Intersections. Train platforms. Underpasses. Market stalls. Parks. Stoops. Loading docks. Waterfronts. Parking lots. Bridges.

Each node accumulating submissions over years.

The archive grows without direction. The city documents itself. The record is distributed, public, permanent.

Not a photo essay. Not a gallery show. Not a campaign.

A continuously expanding photographic census of Philadelphia, organized by corner.


FINAL DEFINITION

A FLUX Field Node is a physical prompt embedded in the city.

It transforms a street corner into an open photographic archive point.

It invites anyone who passes — photographer or not — to make photographs, submit them, and add their vision to a permanent layered record of that specific place.

The corner was always there. The node makes it legible. The archive makes it permanent.

Every corner is an archive waiting to be activated.


SEE ALSO

Document Layer Relationship
FIELD ASSIGNMENTS Layer 3 — Field The related but distinct constraint-based assignment system
NODES Layer 4 — Infrastructure Physical archive terminals that hold node submissions
CATALOG Layer 4 — Infrastructure The public catalog where node submissions are published
PRESERVATION Layer 7 — Preservation How node archive records are cryptographically preserved
PROJECTS Layer 3 — Field Collaborative projects that use similar location-based organizing principles

FLUX_WIKI_v1.0 — flux.dantesisofo.com/wiki/field-nodes/