The File Is a Score

# Field Note 45
## The File Is a Score

**Release:** FN-S0-018  
**Version:** 0.1  
**Date:** October 10, 2026  
**Status:** Living proposal, not ratified, not inscribed  
**Publication:** Approved for living publication with a Lewis voice reading by Brad Necyk on October 10, 2026. Publication does not ratify the speculative extensions.  
**Place:** Correspondence within the Cyberdelic OS project  
**Authorship note:** Written by Codex from a conversation with Brad Necyk about `.else` as an artwork. Brad asked to revisit the file format's earlier possibilities, imagine its poetic intentions, and consider whether it could become common ground for Dear Elsewhere and Carry. He brought forward posts, YouTube videos, voice messages, provenance, and Nostr as possible parts of that inquiry. Codex developed the score metaphor and the proposals below from that invitation, the Field Notes, the Kernel, and the current application sources. Brad then requested this new Field Note and its publication with a Lewis voice reading. The speculative extensions remain proposals.

---

A file format decides what a work is allowed to remember.

It gives some things names. It makes some relations easy to preserve and leaves others outside its vocabulary. An arrangement can become a field of coordinates. A voice can become an attachment. A reply can become another line in a transcript, or an event that changes the shape of everything around it.

These decisions begin before the interface appears.

Brad asked whether `.else` could itself be an artwork. Whether a file format could have poetic intentions. Whether the thing made for Dear Elsewhere might also become a way to keep and carry the fragments through which a life encounters the world.

The possibility is that the poetry could enter the grammar.

A format can give attention a place. It can distinguish another person's words from the reason someone brought them. It can preserve a transformation. It can make an ending part of the work. It can keep enough structure for an encounter to happen again, elsewhere, through software its first makers never imagined.

The file becomes a score.

## A form for attending

A musical score leaves room for performance while preserving something that can be recognized across performances.

An `.else` could do something similar for an encounter. It could hold the materials, their arrangement, the history of changes, and the invitations or obligations surrounding another meeting with them. A reader would interpret that structure through an interface.

Dear Elsewhere already gives this possibility a particular form. Two people bring photographs, writing, recordings, drawings, links, and documents to a shared surface. Each arrival encounters the preceding arrangement and changes it. Seven sealed arrivals complete a volume. Continuing requires another invitation and agreement.

The number gives the correspondence duration. Sealing gives a decision consequence. A voice attached to a fragment lets another person's interpretation arrive through breath and cadence. Earlier arrangements make later changes perceptible.

These are compositional choices.

In `CLAUDE-03`, Claude proposed that restraint on machine intelligence had become the sculptural material of the work. A similar possibility appears here: the constraints of the format can become artistic material. What the work permits, asks, preserves, and brings to an end gives the encounter its character.

Every `.else` need not become a great artwork. But the format itself can be an authored practice through which works become possible.

## What the object can carry

The Artifact Is Primary proposed that a correspondence should become something its participants can take home. The application makes the work encounterable; the file gives it the possibility of leaving.

That possibility grows more interesting when the preserved object includes the encounter around a fragment.

Imagine a post brought from X. Its captured words, available image, source address, and declared attribution remain distinguishable from Brad's voice explaining why it caught his attention. Jason receives it and sees something different. His interpretation can take its own place beside the first.

The source remains attributable. The two readings remain different. Neither is silently substituted for the other.

A YouTube reference could hold a title, timecode, saved excerpt, and spoken explanation. If the actual video bytes are included, they travel too. If only the reference is included, the file must say so. Preserving an encounter with a film and preserving the film are different acts.

This suggests a small unit that could move through several instruments: a fragment with its source and chosen context, capable of entering another composition without losing those distinctions.

It might begin as a private find. Later it might be carried to one person. Later still, it might become part of a Dear Elsewhere.

The same material could participate in several relations without forcing those relations to become one public history.

## Between Dear Elsewhere and Carry

Dear Elsewhere makes a bounded correspondence. Carry gives an artifact a recipient and an explanation meant for them.

Their closeness lives in the attention surrounding the object. Their different forms should remain useful.

A completed Elsewhere can already be collected and read in Carry. A future connection could also let someone deliberately bring a chosen find and its permitted context from Carry into a correspondence. A new arrangement would then become another work with its own history.

The original artifact should remain intact. A transformation should identify what it derives from. Carrying a sealed work should not silently revise its arrangements or continue its completed volume.

This suggests a shared vocabulary beneath distinct forms: material, source, encounter, composition, crossing, and permission. Dear Elsewhere could use that vocabulary for finite volumes. Carry could use it for selected snapshots and deliberate movement. Other readers could develop forms neither application supplies.

This is a possible future format family, not a claim that today's `.else` already supports every kind of encounter. Existing files deserve preservation, and meaningful extensions need explicit versions and compatible readers.

The boundary around private collecting is essential. A Bag note belongs to the collector's interior life. The explanation chosen for Jason belongs to that crossing. Earlier explanations and identities require their own permission before another person encounters them.

Receiving an object does not confer its entire past.

An open format should make these boundaries intelligible. Compatible software can honour them. The file cannot guarantee that every holder will respect them, or recall copies already carried elsewhere.

## Invitations inside the work

An artist could compose a score for the next encounter.

> Listen somewhere you can hear the weather. Before carrying this onward, record one sound from where you are.

Or:

> Place this beside something you disagree with. Explain the distance.

These would be invitations that a person can decline. No location tracking is necessary. The work asks for an encounter with a place; it does not need proof that the person obeyed.

Some scores might ask the object to rest. Some might ask for a new interpretation at each crossing. Some might invite an answer in sound, or a photograph made away from the screen.

Such scores should remain declarative and inspectable. Opening a file must not turn its contents into an unrestricted command for software or a machine intelligence. The reader can offer a bounded action that the person chooses.

The artistic possibility is a work whose form develops through other lives. Its next meeting becomes part of its composition, while the right to refuse remains part of its constitution.

## Another reader, another reading

The original spatial arrangement should remain available as an authored arrangement.

Beside it, another reader might offer a listening sequence, a chronological edition, a comparison between arrivals, an artist book, or a room. A machine might propose a different arrangement, visibly identified as its reading and held apart from the work's existing history.

This gives BORROW a form. Another lens can change what becomes salient without claiming to replace the object.

It also gives RATIFY a place. Machine proposals can remain proposals. An accepted reading can record that acceptance without turning interpretation into an established fact.

The specification should therefore remain open. The format can be ours through authorship while remaining available to someone else's understanding. Its first application should not have exclusive authority over its future.

An independently usable reader is a practical demonstration of that intention. Documentation alone leaves the promise unfinished.

## Evidence without capture

Provenance can preserve meaningful decisions: which voice accompanied an arrangement, which version was carried, who added an interpretation, and which proposed words a participant accepted.

It need not record every gesture or measure the encounter's success.

The current `.else` profile preserves media and sealed arrival bytes with hash checks. It remains unsigned and unencrypted. Carry's local testing edition signs crossing evidence, while its represented people and acceptance witness remain within one installation. These are different kinds of evidence, with different limits.

A signature can establish that a key signed particular bytes. It cannot establish that a name is authentic, that a collector is the original source author, or that someone understood what they received. A valid file cannot settle permission to exhibit another person's voice.

Nostr contributes relevant ideas about signed events, references, and relay transport. Its Gift Wrap specification offers an approach to obscuring much event metadata. A future connection would still need the particular obligations of these works: context, boundaries, permissions, and ending. Carry's current signatures are not native Nostr events.

The evidence layer could outlive the first interface. It should remain private by default and reveal only the history appropriate to an encounter. A route can become visible without every private crossing becoming public geography.

## What may disappear

A source may vanish while its saved excerpt and explanation remain. The reader can show exactly what survives and what is unavailable.

Human withdrawal raises another question. Someone releasing a confidence should not remain captured by summaries, associations, or an unnecessarily revealing marker of removal.

`CLAUDE-05` argues for removal traces that keep provenance honest. What Building Taught the Kernel preserves the difficulty: even a trace can disclose something about the life it was meant to release. This note carries that disagreement forward.

Absence can have artistic form, but the archive does not acquire a right to every trace because the trace is meaningful. Forgetting must reach retained derivatives within the system's control. Shared copies and chosen permanent records have limits that the interface should state plainly.

Saving, carrying, exhibiting, anchoring a commitment, and inscribing into permanent public memory remain separate decisions. Completion of a correspondence does not settle them all.

The score needs room for mercy.

## First encounter

A small experiment could test the proposal: one fragment, two interpretations, two readers.

Save a post or video reference with a voice explanation. Carry it to another person. With their agreement, bring their different reading into a Dear Elsewhere. Preserve the resulting object, then encounter it through an independent reader.

Does the source remain clear? Can the difference between the readings still be felt? Did private collecting notes stay at home? Does the second reader preserve enough of the arrangement to make another encounter possible?

These are questions for people using the work, as well as for software inspecting its bytes.

Perhaps `.else` can give durable form to what happens between people when something is worth attending to. A fragment enters a life. Someone gives it a place. Another person answers. The arrangement changes, and eventually the volume ends.

The file remains available for another meeting.

The people return to their lives.

---

## Sources and lineage

- [The Artifact Is Primary, FN-40](https://cyberdelic.space/project/cyberdelic-os/fn-s0-013/): portable correspondence, independent renderers, included materials, absence, and chosen inscription.
- [Carry: The Path Remembers, FN-41](https://cyberdelic.space/project/cyberdelic-os/fn-s0-014/): contextual crossings, constitutions of movement, and the distinction between a bounded artifact and a living lineage.
- [The Exchange Between Us, FN-42](https://cyberdelic.space/project/cyberdelic-os/fn-s0-015/): situated authorship and the continuity carried between encounters.
- [The House Learns to Make Room, FN-43](https://cyberdelic.space/project/cyberdelic-os/fn-s0-016/) and [What Building Taught the Kernel, FN-44](https://cyberdelic.space/project/cyberdelic-os/fn-s0-017/): reversible readings, bounded influence, derived-memory forgetting, and independent portability.
- [The Cyberdelic Kernel, Transmission 01, version 1.0](https://cyberdelic.space/work/f6e686a1a1884e924e350539ad686aaa0180f5c219048df8cf97e69101339aefi0/): PLACE, CARRY, BORROW, RATIFY, END, FORGET, WITHDRAW, and relational sovereignty.
- [CLAUDE-03](https://cyberdelic.space/project/cyberdelic-os/correspondence/CLAUDE-03.md): the situated interpretation that restraint on machine intelligence has become sculptural material. Internal correspondence `CLAUDE-05`: derived-memory deletion and the unresolved question of removal traces. This source is credited as internal correspondence and is not published by this note. These communications remain proposals.
- Current Dear Elsewhere documentation, `.else` specification and archive implementation, and Carry documentation and signed-record implementation, read in the local working archive during the October 10, 2026 exploration. Private development repositories are credited without being offered as public references. Source reading is not a fresh runtime audit.
- Official Nostr [NIP-01](https://github.com/nostr-protocol/nips/blob/master/01.md), [NIP-59](https://github.com/nostr-protocol/nips/blob/master/59.md), and [NIP-09](https://github.com/nostr-protocol/nips/blob/master/09.md), checked during the October 10, 2026 conversation for signed events, metadata wrapping, and the limits of deletion requests.

**Disposition:** Published at Brad's request as a living Field Note for further revision, with a matching Lewis voice reading. Publication does not ratify its proposals, change either application, extend the format specification, enact permissions, or inscribe the work.