Part of Temporal Constructs Appendix, which contains details behind the research: dates, quotations, descriptions of instruments, and sources.

General definition

The chronology of the system from January 2026, kept so that each change can be read in the order it happened. It records the order of events, and not the properties of the result.

Relation to the practice

The system was built and rebuilt through the first year of the doctorate, and the order matters because the present framework was built up piece by piece, and its failures shaped it. An account is kept here so the CONDUCTOR page can describe the framework as it stands without holding its history as well.

The episodes below are drawn from the sessions of the year, and the Activity record places them beside everything else that was happening at the time. Two entries state the year’s central change: the system appeared at the festival in January 2026 without any artificial intelligence driving it, and it ran fully agent-driven for the first time in August.

Version history

The system has been through five versions. The numbering is how the practice refers to its own past. V1 is the hardware-based version that ALTERITY was made and performed with. V5 is the version presented at MU Hybrid Art House in August 2026. V2, V3 and V4 were prototypes built in between, while the system was being built into what it is now.

Two of the prototypes are placed by the account below without having been labelled as such at the time, and V4 was specified and never made to work. The July entry refers to it as the failed version, the architecture an agent reported as running under the name Fabric, which turned out to be largely invented. V5 was designed in the same month and carried the presentation at MU. The dates of V2 and V3, and what changed at each, are not written down anywhere in the account, so the chronology below describes the work by month.

The repository’s labels are a different count and are not used here. Its history calls V1 the architecture in which every module carried its own sketchpad, snapshot store, controller map and state log. It calls V2 the shared base that replaced that architecture. Both were revisions inside one system version made in July 2026. Those two revisions are described below by what they did, so the account does not count them as system versions.

The practice’s own account of April 2026 describes the system as three modules with one device to a role. Neither V1 nor V5 accounts for that state. In March 2026 the artificial intelligence ran in Max/MSP on the Macintosh, and it stayed there until the June entry moved it to the Raspberry Pi.

Versions compared

The numbering runs from the version the work was made and performed with to the version that carried the presentation at MU. The history places the first and the last of them. The years between them are where the gaps are.

flowchart LR
  V1["V1<br/>hardware, orchestrated by Max 2.0 on the SE/30<br/>the premiere, January 2026"]
  V2["V2<br/>a prototype, undated in the archive"]
  V3["V3<br/>a prototype, undated in the archive"]
  V4["V4<br/>specified and never made to work<br/>taken for the Fabric architecture, July 2026"]
  V5["V5<br/>designed July 2026 and run agent driven at MU<br/>August 2026"]
  V1 --> V2 --> V3 --> V4 --> V5

Two further states of the system are documented by date and do not yet carry a number. These are the three-module account of April 2026 and the sixteen-module build described in the texts published for the film festival in September 2026. The chronology below records both by month alongside the numbered versions.

System readied (V1)

Most of the work from January 2026 prepared ALTERITY and CONDUCTOR for a festival opening. Every medium of the system was brought together into one. The installation itself was built at Brutus, with the three rear-projected screens among it. The Max programming was written and rewritten as failures appeared, much of that work in the days before IFFR opened.

The period was for a system that runs for audiences on its own. The premiere window left the installation in place for days at a time with no one holding it together. The orchestrator in this version was Max 2.0, running on the SE/30 with an Emagic AMT8 interface for the MIDI. Its preset objects held a whole state in memory and its line objects carried temporal effects, much as the framework’s snapshots and timeline do now. The timeline sat outside the machine and sent recalls into it. The instruments themselves were close to what the later versions run, so what the Raspberry Pi and the agent replaced in June was the orchestrator.

Laboratory designed

The system’s architecture was set out in June 2026 under the name Temporal Constructs Laboratory, as an AI-mediated live performance and research system. The architecture itself is described on CONDUCTOR technical notes. It runs in three modes: a conversational mode for rehearsal and set-up, a command mode for debugging, and a performance mode in which stored macros run within about ten milliseconds. A Faderfox controller gives hands-on control. The Macintosh SE/30 running Opcode Max shows the whole system at once. The connections it draws are passed to the agent, while the real ones live on the Raspberry Pi. The old machine is not critical to operation.

The thinking behind the design is that the interface meets a person in a familiar domain. The legacy machines carry the cultural histories that make working with artificial intelligence less strange. A small command vocabulary lets models of very different sizes drive the same system. This design is the starting point of the sixteen modules the system now runs.

A second architecture proposed in the same month divides the work between two models. A cloud model acts as luthier and builds parameterised instruments in advance. A small local model acts as performer and supplies only target values while the work runs. It is the redistribution the research argues for, built as a working system.

Router on the Pi

What the design needed was a machine for the agent to play from. The Raspberry Pi that runs it was stripped to MIDI alone. The audio system was a load it did not need. With a Pisound card in place, the agent had control of the Kurzweil K2000 by MIDI. That was treated as a research infrastructure breakthrough. It runs on low-cost hardware and free-tier models, so the method can be offered to others. A MIDI router was then written that opens all thirteen ports at once, including the ten outputs of a RetroKits interface.

When a container blocked access to the sound devices, the router runs on the host with the agent reaching it over a network socket. It was rewritten once its first version suffered thread contention and echo floods. Agents repeatedly misread its state, and two onboarding documents were written to be read before it is used. A fault that looked like timing jitter turned out to be a runaway script consuming most of the processor. The agent was in the end moved out of its container onto the machine itself.

System rebuilt for August

The system was rebuilt through July 2026 for the presentation at Hit the City in August. The month opened with the codebase deleted by one agent and reconstructed within the same working session by another, which mixed three generations of the system together. Those were an archived signal bus, the running MIDI router and a fourth version that had been specified and never worked. Four reference documents were written out of that reconstruction so the design would survive its makers’ memories.

Version five was then designed from the diagnosis of the failed version. Each cable behaves like a subscription, and a channel number addresses a module with a ceiling of sixteen. A program-change message recalls a stored set of values, and the system plays gradual parameter movements as scheduled data. A module that fails cannot take the rest down with it. Two roles were separated: a builder agent that constructs a module and never performs, and a smaller runtime agent that performs and never writes code.

The practice records what followed as the case that shows why an agent’s report is not evidence. An architecture an agent had reported as running, under the name Fabric, turned out to be largely invented, with almost none of it in place. The sixteen modules were then built from scratch in small steps, with each result read from the machine by Gardner himself. The same session found the cause of earlier unexplained losses: the Raspberry Pi’s file system was in memory and discarded every write at reboot. The system moved to an SSD under version control.

A performance audit in the same month removed five sources of delay and brought the dispatch of a cue from about six hundred milliseconds to under one. The ceiling on a single port was measured at roughly five hundred control messages a second. A fault that took days to trace in the K2000 module came down to a missing call that left messages waiting in a buffer. Again an agent had read a success flag as proof of delivery.

Code in the repository

The framework’s code history runs from 8 July to 3 August 2026, then stops. The repository was kept as a design and reference branch, with the running system tracked separately from it. Two checkpoints were tagged in the first week. The first marked the sixteen module slots, with delivery verified, and the second was the first module able to drive a device end to end.

The module layer was then rebuilt twice. In the first rebuild, each module carried its own implementation of the sketchpad, the snapshot store, the controller map and the state log, and the copies drifted apart. In the second, those were collapsed into one shared base, so a module declares its configuration and holds no code of its own. That removed about six and a half thousand lines, and a module became a declaration of configuration.

On 23 July the sixteen-slot fleet became eight stations, which the technical notes list. Pure Data became the only route from the modules to the hardware, with a watchdog and an alert to a telephone when it failed. CUE was named on 14 July, and the command language was exposed to agents over the Model Context Protocol (MCP) the next day.

On 16 July the repository was closed to direct work. Agents were barred from committing to the main branch, every change went on its own branch, and a smoke compile had to pass first. The last month of the history is the timing work. The dispatch of a cue was taken from about six hundred milliseconds to under one, and the timeline was given a daemon of its own.

Audit before the performance

In August 2026, with a presentation imminent, the system was audited layer by layer as if it were an unknown machine. The audit found the state a system reaches when a person works on it with agents for months. The Pure Data patches running on the Pi differed substantially from the copies held in version control, and modules were bound to their patches by position alone. A mismatch therefore produced silence and raised no error.

A self-healing watchdog was concealing recurring faults, and file watchers reverted state without being asked. One process had been started by hand and no longer matched the service that was supposed to run it. Sixteen past incidents were classified by cause, and four of them remain unexplained. The outcome was a work order: no new features and no refactoring before the performance. The file watchers were switched off and the live patches were mirrored into version control. Traffic on one overloaded MIDI output was reduced, and a full unattended test was run for the length of the show.

Two faults were traced that month. The Pi was counting about eighty-eight clock pulses a second where thirty-two were expected. The pattern of the gaps pointed to two or more clock sources being merged ahead of it, which had to be confirmed by capturing the traffic at the cable.

When MIDI messages stopped reaching the lights, the habit of blaming a part of the chain nobody can observe was rejected. A diagnostic watched the signal where it enters the patches. Throughout, the discipline is to keep what has been witnessed apart from what has been inferred. It is the agent lesson of the previous month applied to a running system.

First agent-driven operation

The system ran fully agent-driven for the first time at MU Hybrid Art House in August 2026, in what is now called V5. It ran for the presentation of ALTERITY during Hit The City. The agent that operates it did not exist at the premiere in January 2026, so the earlier performances were not fully its work. The difference between the two is how the practice measures what the system carries alone. During the MU exhibition the installation also ran between performance moments with no performer present, which is the furthest the work has gone without a person in it.

Toward plain Pure Data

What the system is written in was reconsidered the same month. Moving from the hybrid of Python and Pure Data to Pure Data alone would make the system reviewable as an artefact and reduce the number of processes and ports. It would also answer months of failures caused by processes left running, which had left the agents unable to see the real state of the system.

The judgement recorded is that the blindness is chiefly a problem of supervision and observability. The language is not the cause. The rewrite still leaves the artist a system he understands from end to end. The decisions taken alongside it were to convert timecode outside Pure Data and pass in a decoded frame position. MIDI files were to be recorded with the standard tools of the operating system.

Snapshots were then to be stored as plain lines of text that the text objects can search, one file per module. The practice also weighed whether the command language would adopt the bracketed notation of Lisp, and took the notation without the runtime. The possibility of embedding a small interpreter later, for scene logic that does not run in real time, was weighed alongside it.

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.