Launch preparedapps/irix
irix
Color Palette
An architectonic color palette system based on Radix colors, and a set of CLI tools to apply it.
- Stage
- 7/8
- Doc files
- 8
- Test files
- 9
- CI config
- Found
Creative full-stack software engineer
A communication-focused engineer pairing full-stack work in Python and TypeScript with an academic approach to artificial systems, HCI, and the software development cycle.
Boston, Massachusetts

Selected work
Launch preparedapps/irix
Color Palette
An architectonic color palette system based on Radix colors, and a set of CLI tools to apply it.
Publishedlibs/basis
Ergonomic Python Utilities
An extensive utility library for python, focusing especially on iterables and a Regex "Store".
corpus
A collection of latent engineering artifacts, both prose and structures.
Public roadmapapps/wikiparse
Wikitext Translation Pipeline
Wikitext to markdown & YAML from scratch, including a powerful citation parser based purely on optimized regular expressions.
libs/tact
Self-Healing File Edits for Agents
A reconciliation ladder that heals stale or drifted edits instead of failing them, with atomic multi-file transactions, patch ingestion, undo, durable anchors, and an LSP client — as a library, a CLI, and an MCP server.
sublime/test
A Modern, PyTest-Backed Testing Framework for Sublime Plugins
Bringing modern pytest composibility to Sublime Text plugin development.
Experience
Doering Thinking Machines
A self-directed research and engineering program exploring general artificial systems that coordinate diverse language-model ensembles with symbolic techniques.
Modernized Google's AdSense product, focusing on JavaScript tag logic and new advertising formats across the stack.
Space Ground System Solutions
Helped move a widely used satellite command-and-control system from a desktop Qt application to a React/Redux web interface backed by Java, C++, and data-intensive partner APIs.
Working method
The repository fleet makes the process inspectable: common templates, staged workflows, task records, tests, documentation, and review evidence.
Keep the footprint small: less code, fewer dependencies, and no surface without a named activity to support.
Treat code, tests, documentation, deployment, and the task record as one maintained system.
Prefer inspectable plans, bounded changes, explicit evidence, and a human verification gate over hidden automation.