Hi, I’m Ryan.

I build the systems other engineers avoid.

20+ years shipping software end-to-end: interactive frontends, distributed backends, data and forecasting systems, developer platforms, and the occasional operating system. I take on the parts of the stack other people postpone, and I ship the architecture, not just the demo.

20+ years · Meta Reality Labs · TypeScript · React · C# · Go · Rust · Python · PostgreSQL

ryan / systemsopen to work
experience20+y
shipped10+
domains05
Systems-first · production judgment · shipped code

Selected work

Eight systems worth reading the code for.

Real, working repositories spanning full-stack application architecture, forecasting and data systems, reverse engineering, and systems research — not a portfolio grid of screenshots.

Encounter Lab 3D battlefield showing the Player fighter facing the Fire Demon, with HP engine and dice controls

Full-stack systems

Encounter Lab

A server-authoritative combat application: the backend owns every state transition — hit points, resistance, dice, command versioning, event history — and the React/Three.js client only sends intent and renders what the server committed.

ReactTypeScriptASP.NET CoreGraphQLSignalRSQLite
DispatchLayer forecasting dashboard showing confidence bands and error diagnostics

Data & forecasting

DispatchLayer

Archive-first forecasting and decision-support for grid assets — physics-informed generation models, P10/P50/P90 uncertainty bands, and holdout-validated accuracy across 5 years of hourly data on 10 demo sites.

PythonFastAPIVuePostgreSQLForecasting

Systems research

SCCE

An experimental cognitive runtime built around a persistent, inspectable evidence graph instead of a foundation-model inference loop — document/code ingestion, graph-based reasoning and planning, and a local HTTP API, CLI, and VS Code integration, all CPU-native.

Graph systemsReasoningLocal runtimesCLI

Operating systems

LaplacianOS

A capability-oriented OS kernel written in Rust, booting through a custom UEFI loader, with a native typed graph runtime driving predictive system control and a GPU-composited desktop for native ring-3 applications.

RustKernelUEFIGraph runtime
Bao1702 Desktop safety-first codeplug programmer and reverse-engineering workstation

Reverse engineering

Bao1702

An independently written Windows configuration toolkit for DM-1702-series radios — binary codeplug modeling from reverse-engineered protocol captures, and a safety model that treats every device write as destructive until proven otherwise.

C#WPFBinary protocolsReverse engineering

Backend / infrastructure

SearchAPI

A Go backend for field-deployed hardware test environments: asset and telemetry ingestion, threshold alarms, and a replayable, searchable audit trail backed by Postgres with optional Elasticsearch indexing.

GoPostgreSQLElasticsearchTelemetry
Trustless Voting System landing page describing end-to-end encryption, public verifiability, and zero-knowledge proofs

Cryptography

Blockchain Voting System

A tamper-evident election platform with independently auditable votes and signed administrative actions, built on real cryptographic primitives — not a "blockchain" buzzword slapped on a CRUD app.

TypeScriptNode.jsPrismaCryptographyReact
Onboard Diagnostics Tool's Connect OBD2 Adapter screen with vehicle selection and Bluetooth pairing

Hardware / browser

Onboard Diagnostics Tool

A React app that talks directly to ELM327 Bluetooth OBD2 adapters from the browser via Web Bluetooth — live PID charting, DTC read/clear, and a raw hex command console, no native app required.

ReactWeb BluetoothVite

More on GitHub

The public lab

RiskLab is the toolbox I wanted on the last five complicated projects.

Four focused TypeScript packages for serious analytical software: inspectable, composable, and useful enough to ship. Every card below opens a live demo running on this site, not a README.

Published on npm Apache 2.0 React, Vue, Svelte, Angular, Lit and Solid

How I work

Calm screens. Honest data. No mystery meat.

I care about traceable state, fast feedback, good empty states, and interfaces that explain what just happened. I use automation and AI aggressively in my own workflow, but I don't delegate architectural judgment to either — invariants live in tests and static checks, not in a prompt.

Inside the lab

Explore the system from the angle you need.

Hiring for Staff/Principal engineering?

If the workflow is messy, the data is dense, and the easy answers already failed, we should talk.

I’m interested in Staff and Principal engineering work where systems architecture, production judgment, and execution across the whole stack all matter. Find me on LinkedIn or GitHub.