Can you outline your creative process for a work developed with AI?
My projects begin with morning hikes in nature. doT.DNA, is an audiovisual piece, starts with the examination of lichen distribution across rocks and tree trunks. The observation is a kind of visual meditation: watching how the organisms change—shape, growth, expansion, transformation across surfaces and over time. The colonies spread slowly. I document that slow evolution, then share the data with the AI through detailed prompting, which analyses it to interpret what the system "understands" of my vision and instructions.

Luz A. Otxoa (LUANOTX),
doT.DNA.
Based on these interactions with the LLM, I ask it to generate code as templates to build on. The first versions are rarely what I need, so the modifying starts, bit by bit. Each result gets tested against the behaviour I intend to produce. I adjust the prompts, go back into the code, change the parameters, and nudge the behaviour in a certain direction until the result is right.
Because the work is audiovisual, the process extends beyond the visual layer. The AI-generated code serves as a template for the visual structures; from there I modify and expand it into the sonic component. Working with binaural beats and generative sound behaviours, I build relationships between image and audio so that both evolve together as parts of the same system.
This is what I call 'IterAItive-Gestures': a methodology of small alterations over many rounds until the system starts behaving the way I want. LLMs are not tools that simply hand over finished work. The method puts the creative process back in play through many changes. With each edit, the system moves away from guessing and toward a specific intention.
As the process unfolds, problems tend to appear in two ways. Sometimes the code contains technical errors and fails to run. Other times the code runs perfectly, but the visual result is not what I expected. The first problem is usually easier to fix. The second is more demanding, as it requires aesthetic judgement rather than technical troubleshooting. It is a process closer to drawing than debugging.
In dot.DNA, these decisions shape both the visual and sonic layers of the work. The finished piece reveals itself as a slow, recursive expansion across the screen, while binaural frequencies and generative sound evolve alongside it. Together, they create an audiovisual environment that invites sustained attention and observation.