I build personal AI infrastructure: a private platform where bounded agents work over my own data (documents, messages, photos, health, location) instead of a vendor's cloud memory. By day I direct information security; this account is the personal work.
Most of the system is private. What is public here falls into two kinds: maintained open-source projects, and dated snapshot editions of private systems, published so the architecture can be read without pretending to be a live mirror. Each snapshot says so on its front page and carries a provenance note.
Nexus — the platform itself. Bounded AI agents over a personal data and memory lakehouse: Postgres, a knowledge graph, an MCP tool surface, and a fleet of specialized agent personas. Public snapshot edition, refreshed October 2026; the private system has moved well past it, and the repo documents how and why.
Muster — cross-runtime agent coordination: a registry, declared conditions, and a typed message stream, served by one API that enforces identity, authority, and addressability. Public snapshot edition (Apache-2.0).
Mosvera — a declarative aesthetic runtime: composable expression profiles, JSON Schemas, a TypeScript reference runtime, and an MCP server that compiles aesthetics into provider payloads. Apache-2.0, and public by design rather than by snapshot.
looki-mcp — an MCP server for the Looki wearable camera, giving AI assistants access to moments, photos, highlights, and journal entries. Maintained and current.
Imprint — a public-first identity and expression profile compiler: human-authored writing and transcripts in, structured expression profiles out, with the raw corpus never exposed. Pre-release.
Herald — a DIY desk companion on an ESP32-S3: RGB light shows, speech, and remote management, built on the Muse Gadget SDK.
- broadside-public — snapshot edition of a personal publishing pipeline (May 2026 snapshot; refresh in progress).
- discord-tools-public — a local Discord MCP server and gateway examples.
- bumblebee — fork of Perplexity's supply-chain exposure scanner; my one change makes the HTTP output sink retry transient failures.
The pattern for the snapshot editions: curated, scrubbed, provenance-stamped, and honest about their date. If a repo here looks quiet, it is probably a snapshot, not an abandonment.