Definition

Its purpose is to record the messy, lived circumstances that may otherwise be forgotten, reconstructed, or lost over time. A REED does not explain, justify, evaluate, or interpret a finished work. It stands as evidence of the lived physical experience of inspiration that often - but not always - leads to the creation of art.

A REED may be captured before, during, or shortly after the act of making, while the details of the experience are still vivid.

Purpose

As contemporary cultural production becomes increasingly automated and detached from lived experience, the context of inspiration often disappears. Especially online, finished works frequently survive longer than the documented details of the conditions and inspirations from which they were created.

Without a deliberate capture method, the details of inspiration that inspire human agency and intent within the creative process are easily lost.

A REED provides this structured method for anchoring a work to reality while that reality remains accessible. It captures the initial spark—whether fluid play, systematic repetition, or raw material exploration—preserving information that cannot be reverse-engineered from the finished art alone.

Why It Matters

It matters because without that primary context, a finished work is completely unmoored from the reality of its making.

When you strip away the situational data—the temperature of the room, a sudden glitch in the software, a physical limit in your hands, or a specific constraint you were fighting against—you strip away the why. You are left with a polished, consumer-facing object that feels like it could have been generated by an algorithm in a vacuum.

If those details are lost, three real structural issues occur:

• We lose the baseline. You can't reliably return to the exact parameters that triggered your own work if you're relying entirely on a faulty human memory months or years down the road.
• We lose the blueprint. A finished piece of art or code hides its own labor. The final product cannot be reverse-engineered to show the actual friction, the mistakes, or the raw human choices that shaped it.
• We default to the machine. As automation scales, looking at a finished artifact tells us less and less about the human experience behind it. Preserving the mess, the environment, and the flaws is how we retain clear, unedited evidence of human presence.

Ultimately, it matters because the finished object is only half the data. The REED is the infrastructure that preserves the other half before it evaporates.

Principles

• 1. Proximity Documentation is strongest as close as practical to the moment the information is observed, experienced, or recognized as relevant to the creative impulse, but anything is better than nothing.
• 2. Preservation over Perfection The objective is to preserve the details of an experience, it's fine if it's messy, it should be raw.
• 3. The Value of the Flaw Documentation should preserve the unedited character of reality. Grammatical errors, fragmented thoughts, sensor artifacts, physical mistakes, and system anomalies aren't mistakes; they're evidence of you, of human presence and vital contextual information.
• 4. Specificity Specific details of an experience are going to be more interesting to you and others rather than some vague summary of things.
• 5. Flexibility The methodology is an open framework, applicable to any medium, discipline, workflow, or creative practice, regardless of the creator's background.
• 6. Optionality Use of the methodology is voluntary. Not all works require a REED, although this is a tool for everybody.

Structure & Mediums

A REED consists of one or more records created near a moment of inspiration. It privileges raw capture over polished presentation. It's deliberately messy and imperfect and human.

Because the methodology is format-agnostic, a REED may take any form necessary to capture the details of the context of inspiration, including but not limited to:

• Raw text fragments and process logs
• Environmental data and sensor outputs
• Corrupted files, glitches, or skips in a digital signal
• Audio, video, and photographic recordings
• Written notes and physical artifacts
• Hybrid or mixed-media formats

The method concerns the authentic preservation of the details of an experience of inspiration, not the medium used to preserve it.

The Explainer: What Does a REED Record?

A REED collects primary context data across six distinct categories to capture the specific details of an experience of inspiration. All categories are optional; record only the fields that are directly relevant to the circumstances of your current work:

Scope

A REED may document any information the creator considers relevant to the origin of the work, including:

• Specific human experiences, events, or observations
• Environmental conditions and locations
• The physical tension or emotional states present during creation
• Glitches, system failures, and interruptions
• Conversations, assignments, or research activities
• Materials, tools, and raw technical processes
• Routine practice, study, or experimental procedures

No specific category of information is required. The creator determines what constitutes the vital context of the moment.

What a REED Is Not

A REED is not:

• An artist statement or declaration of intent
• A critical analysis or review of completed work
• A journal, diary, or project proposal
• Proof of authenticity or a measure of artistic value
• An attempt to create a flawless, idealized record

The existence of a REREEDED does not inherently make a work better or more meaningful. It exists solely to preserve the initial conditions of inspiration and the need to create that would otherwise be lost to time and memory.

Applications & Utility

Because a REED is intended to be adaptable rather than prescriptive, the resulting documentation can be utilized in several ways, depending on the nature of the project:

• As a Co-Equal Artifact: Presented alongside the finished visual art, code, video, or performance as a vital record of the encounter.
• As an Integrated Element: Woven directly into the systems, software, or physical materials of the work itself.
• As an Archival Record / Compilation: Kept behind the scenes in personal or institutional archives to support future research, education, or experimental practice, organizing systems over time into permanent databases tracking recurring patterns.
• Autonomous Stand-Alone Document: Maintained solely to preserve a moment of experience while parameters are vivid, standing entirely on its own utility inside technical logs, research papers, or installation spaces.
• Source Material: Used as a structured blueprint or text source to derive new physical, visual, or coded works.
• Private Use: Held securely in personal records as a confidential tool for individual memory retention.

Thesis

If you're still interested, I go into much more detail in a thesis paper: here.

A Printable REED