The Artifact Is Primary

# Field Note 40
## The Artifact Is Primary

**Release:** FN-S0-013  
**Version:** 0.2  
**Date:** October 4, 2026  
**Status:** Living, proposed, not inscribed  
**Place:** A hike on Cobble Hill Mountain, Vancouver Island  
**Authorship note:** This note emerged as Brad Necyk returned to Dear Elsewhere after several weeks absorbed in teaching and a new school. Brad and ChatGPT revisited the working prototype, the possibility of a native `.else` format, portable ownership, cryptographic provenance, mobile correspondence, and optional Ethereum inscription. ChatGPT developed this note from that exchange for Brad's revision.

The internet became very good at letting us make things inside places we do not own. We write, photograph, record, correspond, collect, and create inside platforms whose interfaces become inseparable from the work itself.

A post belongs to its feed, a conversation to its app, and a collection to its account.

Dear Elsewhere suggests another relationship. The service should not own the correspondence; the correspondence should become an object. Call that object an **Elsewhere**.

A Dear Elsewhere begins when two or more apertures enter a bounded exchange. They bring photographs, voice, video, writing, links, documents, music, fragments, and whatever else seems worth carrying. Each arrival encounters what came before and changes the shared composition.

The unit is not the message, but the transformation. Something passes between us, yet it does not pass unchanged. The correspondence gradually becomes a third thing.

Neither participant fully authored it, and neither merely received it. The object exists because attention moved through several lives.

This suggests that Dear Elsewhere needs its own native artifact.

Perhaps:

> `.else`

A single file that can be saved, copied, carried, archived, given away, placed on a hard drive, stored in the cloud, sent to a friend, opened years later, or interpreted by software that does not yet exist.

Inside it may live the media, sequence of arrivals, spatial arrangements, participants, provenance, constitution of the correspondence, and cryptographic evidence that its sealed history has not been silently rewritten.

The format should be ours in the sense that we create it, but not in the sense that only we are allowed to understand it. If Dear Elsewhere is serious about sovereignty, the specification should remain open so that another developer can build a `.else` reader.

The artifact must be capable of surviving the company that first made it legible. This changes the role of the application: Dear Elsewhere becomes where the work is made, but not where the work must remain.

The distinction also separates the artifact from its renderer.

A `.else` might first appear as a spatial collage.

Later the same correspondence could become a chronological reader, a film, an artist book, a room inside Cyberdelic OS, an accessibility interface, or a form we cannot yet imagine.

The history remains stable enough to persist while the interface remains free to change.

This also makes provenance native to the medium.

An arrival can remember the state that preceded it.

A photograph can carry the hash of its original bytes.

A sealed arrangement can reference the sealed arrangement before it, allowing the correspondence to become a chain of custody without needing to become a blockchain.

There are limits to this promise. A hash can prove what something was, but it cannot resurrect something we chose not to preserve.

A YouTube video may disappear. A web page may change. A song may no longer be available in the same place.

Dear Elsewhere should not hide these absences. It can remember that the object was once there, who carried it, when they encountered it, why it mattered, and where it once lived. If the original disappears, the correspondence can retain a tombstone, allowing absence itself to become part of provenance.

Some things can remain entirely inside the artifact: the photograph taken on the mountain, the voice recording made while riding through the Dutch countryside, the short film, the handwritten note, the text, and the sound. When those bytes are embedded, the Elsewhere itself carries them.

This gives another meaning to the old progression from Web1 to Web2 to Web3:

**Read. Write. Own.**

Dear Elsewhere adds another verb: **Carry.**

Possession alone is not the deepest concern. The deeper question is whether something meaningful can move between lives without losing the relations that made it meaningful.

Sometimes the participants may keep an Elsewhere entirely private, and sometimes they may publish it. Very rarely, perhaps, they may decide:

> This should enter public memory.

Only then does inscription become relevant.

A completed `.else` could be given a cryptographic fingerprint and that fingerprint committed to Ethereum.

The blockchain would not need to contain every photograph, recording, and film. It would witness the artifact.

Inscription should not be confused with saving. Saving is ordinary; inscription is ceremonial.

The artifact is primary. The account, platform, and blockchain are not. The relationship is primary, and the artifact is what the relationship leaves behind.

At the end, the people involved do not merely possess a transcript of what they said. They possess something they made by attending to one another, something they can take home and carry elsewhere.