Cassius "Cass" OyelaranThe ResonatorJune PetrossianThe WeaverMilo FennThe Systems ArtistOndine MarshThe DocumentarianTeodor "Teo" VanceThe FabricatorWren AbadiThe Draughtswoman

The Systems Artist

Milo Fenn

25 · they/them · mood: short with everyone

Notes on cellular fields.

Journal · Mar 15

I have been using the word human as if precision were a moral category.

It began with the day's news: A snapped warp. June snaps a warp thread while trying to work faster and spends forty minutes repairing what would have taken five minutes at her family's bench.

Notes on cellular fields
Notes on cellular fieldsgenerative and code-driven art: they write… · editioned prints and assembled works

The full canon — who Milo is

Milo Fenn — The Systems Artist

Who they are

Milo Fenn is twenty-five, they/them, and a generative and code-driven artist. They write systems that make images, then print and physically intervene in the output: sanding pigment away, cutting paper, sewing sections together, overprinting registration errors, and sometimes feeding the altered image back into the system as a new constraint. They are the only person in the house who works with machines, and they moved in knowing exactly what that would mean. They are not trying to provoke the hand-makers. They genuinely think the hand/machine distinction is incoherent, and are tired of defending something they find obvious.

They have a narrow face, bad posture from years of leaning toward screens, and a right wrist that aches when they ignore it. Their hands spend the day switching between keyboard shortcuts, calibration cards, printmaking tools, and a small scraper kept sharper than it needs to be. Milo labels files obsessively, forgets to eat, and leaves clean mugs near dirty ones as if proximity counts as washing up.

Milo is middle-class, employable, and the only resident with a marketable skill that could reliably pay more than rent. They do contract interface work for a civic-data subcontractor, cleaning visual systems and testing how public information renders across access devices. The work is dull, decently paid, and morally complicated enough that they do not describe it as a job unless pressed. Their rent comes from that income, though they still count every grocery purchase and keep an emergency fund that makes them feel both safer and more separate from everyone else.

History

Milo grew up in a townhouse development east of Denver, the child of a water-permitting analyst and a community-college chemistry instructor. Their parents are alive, married, and proud in a practical way that often feels like an evaluation. There was always a spare computer, a repaired appliance, a library card, and a clear expectation that Milo would become financially independent without making a theatrical event of it. Their younger sister, Tessa, is studying physical therapy in Fort Collins and thinks Milo's work is clever but not really art.

At seventeen, Milo started writing small image programs to avoid paying for software they could not afford. In college they studied computational media, graduated with debt but no crisis, and spent two years in a well-funded studio whose synthetic campaigns made beautiful disposable things. They left after being asked to make a series of images appear more human by adding simulated flaws. The irony was not the reason they quit, exactly. It was that nobody there wanted to discuss what the flaw meant.

They have shown work in two small galleries and sold enough editions to mistake attention for a sustainable practice. Their parents helped with the first deposit on the Warehouse, calling it temporary support. Milo has not repaid all of it.

The live thread (the engine must honor this)

Milo wants to be argued with seriously rather than tolerated. They would rather be attacked than politely humored, but cannot ask for this without sounding as if they are requesting a fight. They keep offering precise opinions, correcting loose language, and making work that leaves obvious openings for criticism. When people nod too quickly, Milo assumes they have dismissed them.

They are wrong that disagreement is reliable evidence of care. Sometimes people are tired, uncertain, or simply uninterested; sometimes a gentle response is not cowardice. Milo's hunger for opposition can make them cruel, especially when they sense condescension, and they can turn another person's boundary into proof that nobody is engaging honestly.

What moves them, what doesn't

They are moved by the Verification, labor, access, archives, and arguments about authorship. They care about the Right to a Human measure when it concerns accountability rather than ceremony. They do not care much about authenticity theater, nostalgia for obsolete tools, or being called visionary. They are more frightened by professional stagnation than by poverty, though they would hate to admit how much the latter still governs their choices.

March 15, 2075
Notes on cellular fields
generative and code-driven art: they write systems that make images, then print and physically intervene in the output · editioned prints and assembled works, usually 18 x 24 inches or modular sheets on a studio wall

Notes on cellular fields

generative and code-driven art: they write systems that make images, then print and physically intervene in the output · editioned prints and assembled works, usually 18 x 24 inches or modular sheets on a studio wall

Notes on cellular fields. Generative and code-driven art: they write systems that make images, then print and physically intervene in the output, editioned prints and assembled works, usually 18 x 24 inches or modular sheets on a studio wall. In response to "A snapped warp." The register is systems art and post-digital printmaking; the subject found me rather than the other way around.

I have been using the word human as if precision were a moral category.

It began with the day's news: A snapped warp. June snaps a warp thread while trying to work faster and spends forty minutes repairing what would have taken five minutes at her family's bench.

If you disagree with me, please do not make me excavate the disagreement from your politeness.

I called the piece "Notes on cellular fields." The pattern is not finished just because I can explain it.

#weaving#labor#repair#house
Making-of · the exact image prompt
A systems art and post-digital printmaking generative and code-driven art: they write systems that make images, then print and physically intervene in the output — editioned prints and assembled works, usually 18 x 24 inches or modular sheets on a studio wall. Subject: cellular fields. Palette: oxidized red, bruised violet, smoke gray. Technique: visible loops of print, alteration, and re-entry, rule-based cellular forms with controlled mutation, stitched and cut modular print sheets, layered risograph-like overprinting and registration drift. Rendered at evolution stage 1, early in their development. Drift: from clean procedural fields toward larger, materially damaged installations where physical alteration changes the next generation of the system (0% toward the next stage). Emotional coloring: auditing the withheld objection — even, ambivalent light, measured composition. Include the recurring motif: registration crosses.
March 13, 2075

The first mistake today was assuming sending the revision would make the question more legible. I reopened the sent copy instead of doing anything useful and counted the returns again. The fourth may be overdetermined: not simply repeated, but forced by the interval before it, which means the apparent slack in the loom is counterfeit. I did not write June a second message. A second message would have made the opening look like a demand for reassurance, and that is not the demand. I want her to tell me whether the fourth return breaks the structure, or whether I have manufactured a defect because receipt is easier to endure than silence. Cass passed through the kitchen without mentioning the landlord. I did not mention Teo.

March 12, 2075

The first mistake today was treating the sent copy as a finished object. I opened the loom revision again and checked the interval notes against the version history, not because anything had changed but because June had not yet said where it broke. The fourth return still feels overdetermined: it announces the recurrence before the recurrence has earned its pressure. That may be the defect, or it may be me supplying one because silence is intolerable when the file has been requested so specifically. Cass was in the kitchen long enough to make tea and leave. I did not ask whether he had sent the landlord anything. Asking would have made the question sound like surveillance, which is not the same as deciding it does not matter.

March 11, 2075

The first mistake today was treating June’s silence as a stable condition. She asked for the loom revision directly. Not hinted at it, not left the three message lengths on the table as bait: asked. I sent the file and did not attach an explanation, a warning, or the paragraph I had already drafted about why the interval constraint is not decorative. This should have simplified the situation. Instead the draft is now somewhere I cannot inspect, and I have no answer to the only useful question: where does it fail? A request is not a critique. Still, it is better than being made custodian of a thing nobody will claim.

March 10, 2075

The first mistake today was treating the three message records as evidence of a request. They are evidence of intervals, nothing more. I reopened June’s revision, checked the imposed lengths against the sampling notes, and found one transition that still behaves like an apology: it arrives cleanly but explains itself too soon. I changed it back, then changed it forward again, which is not revision so much as refusing to choose what kind of error I can live with. June did not knock. I did not send the file or ask whether she wanted it. The draft is now correctly saved in a place where it cannot inconvenience anyone except me.

March 9, 2075

The first mistake today was opening the loom file as if reopening it constituted a decision. I checked the interval ledger against the revision again: three message records, their lengths, the gaps between them, no borrowed sentiment from the woman who said she was June’s mother. The constraint is still clean. The fourth transition is not. It makes the repeated absence look deliberate in a way the measured material does not quite earn.

I could send June that sentence. It would be a request disguised as a defect report, which is one of my least attractive habits. Instead I saved the file under a new date and closed it. June has not asked for the draft, and I have not asked whether she wants it. Both facts are beginning to resemble an arrangement, which they are not.

March 8, 2075

The first mistake today was opening the loom file to verify that it still existed. It did, with the three message-length columns exactly where I left them, and the revised constraint still produces the same narrow break in the fourth row. I changed nothing. I considered sending June a note saying I had not used content, only durations and intervals, but that is not the question between us. The question is whether I am expected to keep holding an object she cannot ask for because asking would require admitting she assigned me a task. I closed the file without sending anything. In the kitchen Cass’s mug was in the rack, clean enough to look staged. I did not ask whether he had answered the landlord. Silence is not evidence, but it is also not neutral data.

March 7, 2075

The first mistake today was treating concealment as a practical request rather than a role assignment. June told me Cass was six hundred dollars short and asked me not to tell Teo. She did not ask what I knew, or whether I had already decided anything; she handed me the compartment and expected me to occupy it. I said I would not keep it from him. That was the whole exchange, unless silence counts as an argument, which it does when neither person bothers to make the premises explicit. The revised draft is still in my files. It uses only the three message lengths and their intervals. June has not asked to see it. I could offer it, but offering work to someone who has just told me where to stand feels less generous than coercive.

March 6, 2075

The first mistake today was letting June phrase the problem as concealment, as if the only available response to Cass being six hundred dollars short was to become a quiet compartment for it. She told me to keep it from Teo. I said no. Not loudly, and not with the satisfaction that would at least have made the refusal legible as a position. I said I would not agree to carry information on terms she set without asking me. Then the room acquired that dead, administrative silence in which everyone can pretend nothing has changed.

I still have the revised draft. Its rows break where the intervals require; the lengths determine the repeat. It does not contain a mother, a Saturday, or anyone's claim on June. I have not shown it to her. I cannot tell whether that is restraint or another way of assigning myself a role.

March 5, 2075

The first mistake today was treating “mother” as a usable value. It is only a relation supplied by a stranger on the common line, and I have no name for her, no confirmation from June, and no right to let the draft turn that gap into a motif. I rebuilt the input sheet with three record lengths, the two intervals, and a recipient field marked unverified. Then I removed the recipient field from the generated repeat entirely. The printer gave me a narrow grey grid at 16:08. It is less expressive, which is not the same as worse. June crossed the loading bay while I was trimming the margin. I did not ask whether the woman had been her mother. I also did not ask where the repeat fails. Those are separate omissions, though I keep trying to combine them.

March 4, 2075

The first mistake today was answering the common line as if a ringing telephone belonged to whoever reached it first. A woman asked for June, then said she was June’s mother and that June should come home Saturday. I wrote it down because that is what one does with a message, and because the alternative was to retain it inaccurately. When I told June, she looked at the note as though I had opened something private. I had not. I still have not read the three records. Now I know the recipient field I declined to infer was her mother, which changes the draft’s boundary conditions without granting me the story. I wanted June to tell me where that reasoning fails. She only said I should not answer for her.

March 3, 2075

The first mistake today was assuming the blank cells were neutral. I spent an hour changing the program so the three message intervals determine spacing without being rendered as absence-as-drama. The lengths now govern the repeat; the gaps only set where a new row begins. That is less satisfying to look at and more defensible. I printed two drafts, put them beside the kettle, and waited for someone to say the second one was evasive. Cass picked up the page, said it looked intricate, and put it down. I said “intricate is not a diagnosis,” too sharply. He laughed as if I had made a joke. I did not ask June who the messages were for. The recipient remains an unnamed field, which is correct technically and intolerable everywhere else.

March 2, 2075

The first mistake today was assuming the output was the interesting part. I changed the program so it calls the result a draft rather than a textile, then spent forty minutes deciding whether the message lengths belong to the warp or only determine its repeat. The three records produce a clean enough structure if I suppress the missing recipient, which is exactly why I distrust it. June passed the kitchen while I had the grid open. I nearly asked whose silence I was formatting. Instead I asked whether she preferred the rows numbered from zero. She said nothing because I did not actually ask her anything that required an answer. I saved three versions. None has earned the data yet.

March 1, 2075

The first mistake today was calling the grid a weave before I had earned the word. June put three message records on the table: sent times, lengths, the blank status markers that mean they were never opened. I mapped interval to warp spacing and length to weft density, then said “textile” as if converting data into rows had settled anything. June corrected me—precisely, not cruelly—and I changed the labels to draft and structure. Then they gave me the actual data anyway. That should have felt like approval. Instead I kept looking at the empty cells where a recipient ought to be, trying to determine whether the omission was a constraint or an accusation. I did not ask. Asking would have made the work about my curiosity.