Part of Temporal Constructs Main Text, which states the research questions, the proposals, the work done and what is still open.

General definition

CONDUCTOR is a modular MIDI routing and sequencing framework. Human operators and AI agents work on legacy instruments through one shared command language, CUE (Conductor Unified Execution). It runs on a Raspberry Pi 4 as sixteen independent modules, which arrange material on a single timeline of sixteen tracks.

Relation to the practice

CONDUCTOR is the practice’s digital framework, and it began as the name of the installation inside ALTERITY. It became a framework whose main interface is the agent that operates it, and hardware is part of it without defining it. It is the staging environment in which the instruments and languages of the MIDI era are studied, among them M, Trip-A-Tron, KML, HMSL and the Kurzweil K2000.

Origin of the name

The name first belonged to the installation in ALTERITY, where it refers to the apparatus itself. In the research, CONDUCTOR means the framework that operates that apparatus and can operate others. The agent suggested the name in July 2025, before the doctorate began; the practice worked through Claude in that period, before it moved to the Hermes Agent framework.

Five versions of the framework have followed that suggestion, and they are numbered. The installation sense of the name has no number. V1 was the hardware-based version the installation was made with, orchestrated by Max 2.0 on the Macintosh SE/30 with an Emagic AMT8 interface handling the MIDI. V5 is the version presented at MU in August 2026. The framework now runs on the Raspberry Pi with Pure Data and the agent operating it.

Role in the research

The framework records how decisions are shared as a by-product of operation. It lets the artist choose how involved to be, from delegating programming to agents to sharing it closely. Its transferability is tested by handing it over. Its command language and its agent are parts of the framework, so someone taking it up inherits a way of working along with the software. ALTERITY is the work built with it so far.

Component names

The system is sixteen modules, one per MIDI channel, arranging material on a single timeline. Inside each module sits its controller, the gatekeeper and the contract of what that module can be asked to do. A conversation layer carries the dialogue between the people and the agents. One workbench stands outside the modules, with direct access to the hardware. CUE is the shared command language that addresses them all.

A module is operated with a device written in Max or Pure Data. Image and light are addressed as the instruments are, through a video mixer such as the Edirol V4 and through DMX. The stations the system runs in ALTERITY include the Kurzweil K2000, which makes the sound, and the two Lexicon LXP-5 units, which place it across the four channels. Its image comes from the sequencer M and from Trip-A-Tron, which drives the visuals.

Scope of the system

The scope claimed for CONDUCTOR was narrowed in October 2026. CONDUCTOR routes and sequences and judges nothing itself. It is therefore not a new kind of creative intelligence. It is not a modular MIDI mediation system either, because that description fits a machine of the 1980s equally well. The new part is the shared command grammar, which lets human operators and agents act together with legacy instruments.

Another practitioner who builds a performance like ALTERITY with entirely different hardware is still working in CONDUCTOR, because almost none of the framework is specific to this rig. The rules the system is built to follow are gathered under Design principles.

Agents

Two kinds of agent appear in the research, so the word on its own is ambiguous. The operating agent is the one the practice works with most. It is the framework’s main interface, and it runs on Hermes Agent, the open source agent framework that Nous Research published in February 2026. The practice both runs and studies that framework. It did not exist at the premiere of ALTERITY in January 2026. The second kind is the builder agent, which writes and repairs code and never performs; a runtime agent performs and never writes code. The agent roles are set out in full on a page of their own.

Strummer example

The strummer is a working device written for the explainer that accompanies the masterclass, to show what a device is. It is not one of the sixteen modules. Devices are used in performances, and the strummer can be one of them.

Explaining the system

What was built to explain CONDUCTOR is a touch controller of sixteen numbered slots that the agent relabels as the task changes. The build also includes an interactive deck whose dialogue is spoken by the agent and by the system itself. A guided tour is hosted by Nexus, the guide agent of the explainer, with a timeline, a chain and a hardware column, a working strummer device, and a companion wiki of twenty-five articles.

Unforeseen

Here the unforeseen situations, sometimes difficult, sometimes unexpectedly interesting, will be described as the project runs. Many of these unforeseen situations have already occurred and have been recorded. They will be added in the time to come.

The following pages are part of this page but are not needed to understand it. They can be opened from here for further exploration.