Scene branch of a longer practice

Studio Portfolio

This is the scene-facing branch of a practice that began in photography and darkroom process, where threshold, translation, memory, and technical limitation first became central. What now appears here as control, participation, room logic, or recovery path grows out of a much longer line of windows, prototypes, wounds, glitched images, sound pressure, and public experiments.

The current scene systems are not separate from the earlier work. They are one later container for the same questions: how people enter a work, what a medium withholds, what it remembers, and how care appears in structure.

Open the fleet map Open methods Open privacy & ethics Open studio-notes

Selected Works

A quick entry into the current public project set

This compact grid keeps the newer project pages and the broader Studio narrative in one place. For cross-project patterns and public boundary notes, use the Methods and Privacy & Ethics layers directly.

Lineage

What now looks like infrastructure began as image, risk, grief, and proof

The studio work still carries its earlier materials inside it. Photography becomes consent-forward seeing. Youthful launch-thinking becomes instrument design. Injury becomes maintenance culture. Temporary rooms become repeatable public systems.

  1. Windows and thresholdNight Stalker Re-Runs on Channel 4 begins the line of mediated seeing.
  2. Flight and prototype logicI was young once turns ambition, numbering, and risk into early structure.
  3. Injury and continuationScar makes repair, bodily memory, and still riding the same machine part of the work.
  4. Rooms and hybrid stacksAre you ready to fly?, Two lefts..., and Symbolizing Everything show that systems were already present.
  5. Care as methodThe current instruments, memory environments, learning platforms, and rebuild work keep those same questions legible.

Scene Systems

Three systems that make the studio legible

These are not just works. They are operating systems for scenes: how people enter, how control behaves, how media lanes synchronize, and how the work stays understandable after the first build moment. Each one also carries older concerns about translation, unstable memory, bodily pressure, and shared structure.

Scene system

Memory Engine

A participant memory environment where invitation, consent, retention, and steward intervention are part of the work itself, not hidden support logic.

Atlas node Repository
Show Memory Engine flow

Control system

MOARkNOBS-42

An embodied control instrument whose interface, firmware, bench work, and documentation all stay auditable enough to teach, rebuild, and measure.

Atlas node Repository
Show MOARkNOBS-42 stack

Performance system

live-rig

A three-lane performance rig where audio, control, and video stay synchronized through explicit setup, mapping, and recovery logic.

Atlas node Repository
Show live-rig topology

Where truth lives

Project repos hold the live scene- and tool-specific truth. studio-notes holds the cross-project patterns, decisions, reference, and teaching cards harvested from that work. Atlas shows how those systems relate across the fleet. The archive stays public because current scene logic still depends on those earlier experiments.

Methods and Privacy & Ethics explain how evidence, documentation, assumptions, and public boundaries are being handled across this branch.

Project Catalog

More studio projects

The broader studio catalog stays here. The featured systems above are starting points, not the whole scene branch. Read the lineage notes on each card as quiet reminders that today’s public systems grew out of much older experiments in image, pressure, risk, and maintenance.