Independent and open source
Applications for service businesses and personal health records, connected through shared identity, permissioned APIs, and agent access. Employment and client work are summarized on the resume.
SVC and PHR share authentication and agent integration libraries. Each keeps its own records and permissions, and exposes explicit interfaces for the workflows other applications and agents need.
Service-business operations · Alpha
Clients, agreements, projects, time, and billing in one workflow, with a permissioned client portal. The design keeps business commitments and the invoices derived from them consistent.
Authorized agents can log time and help prepare invoices through REST or MCP. A scoped reconciliation API lets a finance system link its transactions to SVC invoice payments.
Personal health records · Self-hosted
An open-source, self-hosted personal health record system for structured clinical records, source documents, DICOM medical imaging, interoperability imports and exports, and AI-assisted document extraction.
Patient-scoped APIs support records and delegated billing access. REST and MCP clients can process source documents into proposals that a person reviews before acceptance.
Deployment model: the source code is public and intended for self-hosting. No public hosted signup is offered.
PHR is not offered as a HIPAA-compliant service. Organizations considering regulated use must conduct their own security, privacy, and compliance assessment.
The connections are part of the design: shared identity, REST APIs for agents such as Meta Muse, and MCP integrations for compatible clients, including ChatGPT dots through plugins. The infrastructure page explains the libraries, permission boundaries, and operating tradeoffs behind them.
Open source
Contributions to Meta's public Sapling source-control tooling, including interactive smartlog and related code-review workflows.
Interactive product work · Public source
A collection of browser games sharing one application shell and authenticated cloud saves. A different kind of product work: something you can understand by playing it, with the account and persistence details still treated as engineering problems.
Rules-based computation · TypeScript and PHP
A shared dataset of US retirement-account limits with native TypeScript and PHP engines over it. The engineering interest is consistent behaviour across two runtimes and explicit treatment of missing facts, unsupported periods, and indeterminate results.
Experimental library · Public source
An early, reviewable take on SQL-first privacy-policy enforcement for Eloquent models. Published to be read and argued with, not recommended as a production security control.