FORMÆTRIX
Design and systems work for publishers and authors — publishing infrastructure, identity systems, editorial web architecture.
Enter the studio →Ryan J. PylesAuthor · Engineer · LinguistChicago
I write experimental fiction as Elian Voigt and build narrative systems through FORMÆTRIX.
The distance between a manuscript, a language, and a software system is smaller than it first appears.
I design narrative systems for publishing, software, and fiction.
Ryan Pyles — Chicago
The personal archive behind all three — the fiction of Elian Voigt, the FORMÆTRIX studio, and the language work.
Narrative systemsfor authors & publishers
Six published novelsas Elian Voigt
Twelve languagesin active study
Work with FORMÆTRIX
What I build for clients
Design and engineering for publishers, authors, and teams where language and systems are inseparable from function — from AI narrative tooling to editorial web architecture and the publishing infrastructure underneath it.
Selected outcomes
- Built an AI-powered narrative-continuity platform for long-form fiction.
- Designed publishing infrastructure supporting a growing catalogue of novels.
- Developed internal tools that replace repetitive editorial workflows.
- Shipped React / TypeScript products from concept through deployment.
How the work moves
- 01Discovery
- 02Architecture
- 03Prototype
- 04AI Integration
- 05Testing
- 06Launch
One origin point · three ways in
The same investigation, run through three instruments — a studio, a body of fiction, and a life spent inside languages.
Elian Voigt
Six published novels in a shared formal universe, three more forthcoming. Fiction that proposes a structure, then inhabits it.
Read the fiction →Ryan Pyles
Twelve languages, field notes, and the long study of how form carries meaning — the origin point behind the studio and the fiction.
Read the biography →Selected engagements through FORMÆTRIX: author sites, publishing systems, editorial interfaces, and narrative tools.
Continuity Atlas
A visual story-memory architecture for authors working with AI.
- 01
Story Memory
Motifs, secrets, and promises tracked as living entries — author-only facts stay hidden from AI output by default.
- 02
Character Drift
A character is an ordered sequence of states, not one biography. Each chapter can carry different voice rules and guardrails.
- 03
Voice Fingerprint
Voice measured as behavior — fragment frequency, sensory density, dialogue evasion — not described as a style.
- 04
Rewrite Assist
Inspect before generate. A Context Receipt shows what is preserved, forbidden, and hidden before any rewrite fires.
- 05
Continuity Graph
Characters, events, places, and motifs as interconnected data — queried and validated across the whole book.
- 06
AI Integration
Semantic retrieval gives the model visible, editable, trustworthy memory of the manuscript.
Books
Six published novels under the Elian Voigt name, three more forthcoming — a shared formal universe held together not by plot but by recurring tensions. Systems that become belief. Languages that reshape their speakers. Grief treated as investigation.
- Terms of UnbeingIVol. ILiterary Horror · Identity
Terms of Unbeing
A lease he doesn't remember signing, in a building where identity is negotiable and every clause hides another beneath it.
View book → - Declensions of Dark WaterIIVol. IIFolk Horror · Language
Declensions of Dark Water
A grammar in which syntax shapes reality. He converts from observer to custodian.
View book → - The Quiet MetricIIIVol. IIIPsychological · Literary Fiction
The Quiet Metric
A relationship built on being understood exactly — until attentiveness hardens into management, then something harder to name.
View book →
Notes
Field Notes
Short fragments written close to the moment — observations, structural curiosities, and language notes before they settle into something more considered.
Gluggaveður and the cruelty of windows
Icelandic has a word for weather that looks beautiful through a window and punishes you the moment you step into it. I've started keeping a list of ideas that work the same way — gorgeous from inside the frame, unlivable once you cross the threshold.
LuaLaTeX as a nervous system
Somewhere between the macro expansion and the rendered glyph, a document stops being yours. LuaLaTeX just makes the nerve endings visible — every \def a synapse firing in the dark, long before anything reaches the page.
§ 04 · The Voigt ProjectA Case Study
A Case Study
in Identity
Ryan Pyles
builds
systems.
Engineer · Architect · Chicago
Elian Voigt
tests
them.
Literary Fiction · Six Novels
A Case Study in Identity
One maker, two voices. Ryan Pyles builds systems; Elian Voigt tests them. Five dimensions where the engineer and the author diverge.
01Naming
Ryan PylesRyan J. Pyles
const identity = {
name: "ryan.pyles",
role: "maker",
city: "chicago",
status: "active",
};Elian VoigtElian Voigt
A constructed identity. A literary voice. No fixed address.
02Voice
Ryan PylesDeclarative
fn approach(
problem: Problem
) -> Outcome {
problem
.decompose()
.map(resolve)
.collect()
}Elian VoigtOblique
Structure first. Meaning emergent. The text never explains itself.
03Typography
Ryan PylesIBM Plex Mono
/* systems infrastructure */ font-family: "IBM Plex Mono"; font-weight: 400; letter-spacing: 0.08em; rendering: gridded;
Elian VoigtEB Garamond
Designed to slow the eye. Warmth through historical weight.
04Constraint
Ryan PylesMinimum viable
// only what the structure requires
function build(input) {
return input
.strip(redundant)
.verify()
.ship();
}Elian VoigtGenerator
Not a limit. The source of strangeness — what remains when everything else is removed.
05The risk
Ryan PylesConvergence
if (engineer === author) {
// the distinction
// collapses here
boundary.dissolve();
}Elian VoigtConvergence
When the author sounds like the engineer, the strangeness disappears.
The Voigt Project
One maker. Two public identities. One ongoing experiment.
For years I found myself writing two kinds of work that demanded opposite instincts. Software rewards precision, reduction, and explicit reasoning. Literary fiction often rewards omission, ambiguity, and structures that reveal themselves only after the reader has lived inside them for a while.
Instead of forcing those instincts into a single public voice, I separated them.
builds systems.
tests them.
The division isn’t marketing. It’s methodology. Each identity protects the other from becoming predictable.
Why separate them?
Because audiences read names before they read ideas. Someone hiring a software architect expects different evidence than someone choosing a literary novel. Separating the identities allows each body of work to be judged on its own terms while remaining part of the same investigation: how language, structure, and formal constraints change human behavior.
The work is different. The questions are the same.
One line, followed
- 2008Software engineering
- 2016Editorial systems
- 2024First novels
- 2025FORMÆTRIX established
- 2026Elian Voigt created
- TodayOne research program · three public expressions
What crosses the boundary?
Software taught me that every complex system eventually exposes its assumptions. Fiction taught me that people do the same. The continuity tools I build began as problems inside novels. My typography comes from publishing. My publishing systems come from engineering. Language study informs all of it.
The boundaries are practical. The research is shared.
The experiment continues
The goal has never been to keep Ryan Pyles and Elian Voigt permanently separate. The goal is to discover what each can learn from the other without collapsing into the same voice.
Every novel changes the software. Every software project changes the writing. The separation exists because the exchange matters.
Research
In Progress
Longer-form work before it closes — language studies, narrative systems, ongoing manuscripts.
Work with Ryan
FORMÆTRIX takes selected engagements for publishers, authors, and organizations where language and form are load-bearing.