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

General definition

The role is one of four that a professional doctorate candidate must combine. It is the ability to design and conduct methodical and transparent research. That research connects with and enriches the practices of the arts and design sector.

Relation to the practice

The role covers the independent development of a relevant research question. It covers mastery of the methods and methodologies needed to answer that question, and the ability to communicate about the research. In this professional doctorate the question is the Principal question. Its methods are those of artistic research and practice-based research, and its communication runs through the decision log and method articulation.

Question changes

The Principal question asks what forms of creative intelligence surface when artists and agents create within the rule-based instruments of the MIDI era. Four subsidiary questions and a set of learning goals sit behind it. The question moved during the first year, from autonomous human-machine co-creation towards a more limited, human-anchored arrangement. That movement appears as a dated change of position. Exhaustive addressability became the criterion settled on in September 2026, which asks whether every parameter of an instrument can be reached. That reach decides whether an agent can work in the instrument at all.

Method

The method is temporal systems archaeology through creative reconstruction. It uses authentic period hardware and software of the 1980s and early 1990s. FPGA reconstructions of period machines supplement the original hardware, and the practice works on these reconstructions as physical hardware and does not emulate them. A reconstruction is itself a research instrument. A machine kept playable keeps its rules readable.

The oral history strand tests the practice’s reading of the period against the people who made it. The interview with David Rosenboom, co-creator of HMSL, was prepared on 19 October 2026 and held on 22 October. Its transcript was compared with sources on 27 October, which corrected a death date, a surname, a chronology and the dating of an instrument (Gardner and Rosenboom 2026).

Disciplines of the method

Four disciplines sustain the method, and each appears in the account. The session history comes first, because every working session of the project was kept. The accounts of each month from February to October 2026 turn that history into a describable source. Coding comes next, and the sessions are coded against a codebook so cases can be traced and counted. That coding turns a year of work into evidence with a method behind it (Session record).

The evidence rule is the strictest rule in this practice. What has been witnessed is separate from what has been inferred, and the practice never accepts an agent’s report as evidence of a result. The system’s own history showed why. An architecture an agent reported as running turned out to be largely invented. A success flag read as proof of delivery concealed a fault that took days to trace. Sixteen past incidents were classified by cause in the audit of August 2026, and four remain unexplained in the account.

The practice handles sources with care. The literature on the period is cited from the sources themselves. The standing rule is that sources are compared with their originals before citation, and corrections are kept as part of the account.

Transparency of the research

The research is transparent by design, because humans and agents work through one shared command language. Nothing is hidden from either, and every action can be read, repeated or corrected (Shared language and transparency). Failures in the system are left visible. The difficulties expected of the method and the results it did not look for are recorded in two ledgers, which keep what a project usually leaves out. The demonstration overlays the decision record on the work, so what was delegated, withheld, initiated unprompted or overridden can be watched as it happens.

Publication for the sector

The method is published in a form the sector can use, namely the archive with the tools beside it. The technical notes carry the parts that are engineering. Beside the archive sit the archive with its classes and its governance, and a data management plan written to the requirements of the ethics module. The claim on the reader is bounded, and the findings are offered as an account of what this arrangement produced, with the cases traced. Another practitioner can then judge whether it applies where they work (Transferability).

Evidence for the method

The method is evidenced in five places:

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.