Chris Zemmel.

Foundation is my personal operating layer, the meta-layer that sits underneath everything else on this page. It is not a product and it is not for sale. It is the internal control plane I built to run all of my own work from one place: every project, repo, service, and database becomes a typed resource with a desired spec, an observed status, and typed edges, so I have a single live source of truth for the whole portfolio instead of a dozen dashboards. It orchestrates the software I already trust (Docker, Postgres, Redis, Git, Cloudflare, SaaS) rather than replacing it, and a reconciliation engine converges what is running toward what I declared. On top of that sits Repository Intelligence: every repo is a living resource that Foundation statically analyses and keeps understanding, and scoped agents ride that knowledge to automate parts of my workflow and push each project forward with less manual effort. The point is leverage: one person operating like a team, shipping more across every other thing I build. Docker deploys software; Foundation understands it.

OneHealth is the system of record for a person's health, with a navigator built on top of it. Every input (lab document, wearable export, clinician's note, pharmacy slip, image) is normalised into one lifelong, source-agnostic record, where each value carries its unit, reference range, timestamp, source and quality flag, and nothing is ever overwritten. The product sits on that record: you set a destination (lose fat, lower cardiovascular risk, sleep deeper, age slower), the system computes a ranked, reasoned route, a licensed clinician approves it, and it recalculates every time your data changes. The system proposes; a human stays accountable. Built on an event-sourced canonical layer, an AI agent council, and a clinician review loop.

nimimo is a non-custodial crypto identity layer. One link (nimimo.com/@chris) receives Bitcoin, Ethereum, Solana, and USDC, abstracting wallet complexity away from the user. The architecture deliberately separates access, identity, ownership, and recovery, with keys remaining fully on-device. Built for security-critical flows, cross-chain usability, and reducing friction in real-world crypto transactions, with no app, no exchange, and no KYC. Ships with a lightweight, no-API-key developer SDK.

An autonomous AI security-audit pipeline that reviews critical code the way a specialist team would, invariant by invariant, across smart contracts, bridges, light clients, ZK circuits, and the web2 systems that guard identity, authentication, and access-control. To date: 160+ targets reviewed across 29 ecosystems against 150+ vulnerability classes, with 24 confirmed findings, every one human-triaged and severity-calibrated by a human, not the model alone. That calibration is the point: in a live cross-chain bridge that has moved $100M+ across its routes, the pipeline flagged real consensus-verification gaps in the non-flagship light clients as critical; human review downgraded the severity to conditional, but the gap between the bridge's marketed trustless verification and what those clients actually check still stood (responsibly and privately disclosed). Detection-only: it finds and reports, never exploits. One engine spanning EVM, Solana, Move, Cosmos, Substrate, Bitcoin, ZK circuits, and web2 access-control.

A full-stack governance client for Enjin OpenGov, all backed by live chain RPC. Browse referenda, cast conviction votes, file treasury requests end to end, comment, and manage a profile, straight from the browser. Multi-wallet support (Enjin Wallet, WalletConnect, and the four major Polkadot extensions), four chains with dedicated archive RPCs, zero required indexers, SIWE-style sign-in by signature, and the EGOV1 on-chain metadata standard that lets any third party rebuild the proposal corpus. The funding proposal passed, and the client is open-source on GitHub.

A free, MIT-licensed scanner for the person a suspicious take-home task was sent to. Fake-interview campaigns hide a payload in a postinstall hook, an obfuscated config, or a dependency pinned deep in a lockfile, and it runs the moment you type npm install: browser passwords, SSH keys, cloud tokens and wallets, gone before you have read a line. RepoCanary never clones, installs, executes or evaluates the target. It reads a bounded set of files as plain text through the GitHub API and matches signatures, so pointing it at malware is exactly as dangerous as reading it in a browser. Detection is measured against a corpus of the techniques these campaigns actually use, and the evasions it cannot catch are written into the threat model rather than hidden. Green means nothing known matched, never safe, and the tool never says anything stronger. One command, zero runtime dependencies, and one shared engine behind the CLI, the website and a GitHub Action. The code is open-source on GitHub.

The complete digital surface of a Vietnamese street-food restaurant in Schwäbisch Gmünd, built end to end and shipped solo. The public site carries the menu (allergens, vegan and vegetarian markers, spice levels, sold-out for today), opening hours, online ordering with pickup slots, reservations, and events. Behind it sits an eleven-tab dashboard where the owners edit all of it themselves, with no deploy and no developer in the loop: dishes, prices, opening hours, holidays, the editorial copy, and the FAQ. Orders and reservations arrive by mail and Telegram and stay in the dashboard, with each path standing on its own: if the database is down the mails still go out, and if the mail provider is down the order is still in the dashboard. Next.js 16, React 19, Tailwind v4, Drizzle and Postgres.

Substreak is a Substrate reward and asset-distribution system, funded by the Enjin ecosystem's first accepted on-chain treasury proposal and featured by Enjin. It began with a Telegram interface, but rather than run custodial wallet infrastructure on users' behalf, the user-facing layer was wound down by choice. It now runs as backend infrastructure: automated reward distributions continue on schedule, and the integration APIs stay live so dependent systems keep pulling reliable Substrate data. The non-custodial direction carried forward into nimimo, which receives crypto in the browser with keys on-device instead of through managed wallets.

A solo worldbuilding project exploring procedural generation, persistence, and discovery. Every world is generated deterministically from a single seed, producing its geography, climate, weather, life, and sky. A seed is a place rather than a session, meaning worlds can be revisited, shared, and explored together while remaining identical for everyone who visits. Build a homestead, light a watchfire, plant your standard, and leave a mark on the world. Time passes, weather changes, moons drift overhead, and every world develops its own character from the same underlying rules. Built with React, TypeScript, React Three Fiber, and a fully procedural audio system. No accounts, no downloads, and no backend required.