Skip to content
Ryan J. PylesSoftware · AI · Design · LanguageChicago

I work across software, AI, design, and language — through FORMÆTRIX, and write fiction as Elian Voigt.

Ryan Pyles — Chicago · Software · AI · Design · Language

I build systems for problems that refuse to stay in one discipline.

Four instruments, one practice

  1. 01

    Engineering

    Full-stack systems in React, Next.js, and TypeScript — from architecture and data modeling through deployment.

  2. 02

    Intelligence

    AI systems that reason over long-form context: narrative continuity, retrieval, and structured memory that holds across thousands of pages.

  3. 03

    Design

    Editorial interfaces and design systems where typography, rhythm, and form carry as much meaning as the copy.

  4. 04

    Language

    Multilingual architecture and applied linguistics — twelve languages in active study, built into the systems rather than bolted on.

Work with FORMÆTRIX

For clients

Work for clients runs through FORMÆTRIX: sites, brand systems, publishing infrastructure, and AI tools scoped to a manuscript or a product.

Continuity Atlas, Polytype, and Publish Architecture are studio tools, built for the imprint. Demos are linked from each case study. They are not client engagements.

§ 05 · Narrative Intelligence System

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.

Fig. 05 — Selected systems

Four systems, built — not described.

Each is a working engine with a live demo. The drawing beside it is its own logic, not decoration.

012025

Continuity Atlas

Story memory that behaves like a living manuscript — a visual interface for novelists who need to inspect what the AI thinks is true before it generates, rewrites, or expands anything.

  • React
  • Framer Motion
  • Product Design
  • Narrative Design
Open the case study →
what's mocked
AI generation is mocked in the prototype — the design thinking is the subject. The data is real, extracted from the Liminal 6:17 manuscript.
022026

Polytype

A locale-aware typography engine for multilingual interfaces — script, direction, line breaking, font coverage, and text expansion treated as inputs to the design system, not bugs found after translation.

10scripts classified from Unicode ranges

  • TypeScript
  • Intl / Unicode CLDR
  • React
  • CSS Logical Properties
Open the case study →
deterministic
No model sits in the decision path. Script, direction, leading, and overflow are resolved by inspectable rules — the point is showing where a model does not belong.
032026

FORMÆTRIX Publish Architecture

A publishing system that treats a manuscript as structured source, not a Word file — one canonical source compiled to print, EPUB, and web, so a correction made once reaches every edition.

1canonical source; print, EPUB, and web are outputs

  • TypeScript
  • Canonical Document Model
  • LuaLaTeX
  • EPUB3
Open the case study →
the print path
Print targets a LuaLaTeX pipeline; the live demo renders the canonical model and the build validator in the browser.
042026

Locale-Aware Product System

An interface architecture that treats locale as product behavior, not translated copy — direction, typography, forms, formatting, and layout all resolve from one locale context.

9facets a locale resolves — from direction to week start

  • TypeScript
  • React
  • ECMA Intl / CLDR
  • CSS Logical Properties
Open the case study →
where AI sits
AI is advisory only — a shorter label, an explanation of a QA failure. The authoritative locale behavior is deterministic, over ECMA Intl.

Notes and manuscripts in progress live under Fiction.

Selected engagements through FORMÆTRIX: author sites, publishing systems, editorial interfaces, and narrative tools.

言Japanesegengo
שפהHebrewsafah
لغةArabiclugha
語Japanesekata

Language isload‑bearing

Work with Ryan

FORMÆTRIX takes selected engagements for publishers, authors, and organizations where language and form are load-bearing.