Systems

The 17 systems I run, as one drawing. Choose one to see what it connects to; choose Capsid again to go inside it. 6 are private, so they show only a name and, where they have one, an address.

The family of systems

A capsid is the protein shell of a virus, built from repeated parts called capsomers. This family is built the same way: Capsid in the middle, the shared parts around it, what people use on the outside.

The same map as a list

Runs everything

  • Capsid The knowledge store, work queue and credential boundary that every other project is run through. mcp.dustinedwards.info Its page Capsid

Shared parts

  • Capsomer shared The design system every app is drawn in: tokens, the shell and shared controls in plain CSS. capsomer.dustinedwards.info Its page Capsomer
  • site-runtime shared Request-time behaviour every site imports: security headers, the rate limiter and the health format. Its page site-runtime
  • d1-dump shared Per-table backups of a D1 database, with graduated retention and a restore drill. Its page d1-dump
  • devkit shared The shared CI workflow, Renovate rules and test helpers. Its page devkit
  • site-api shared The contract Carrel publishes through. Its page site-api
  • Prelum shared Turns finished writing into pages, feeds and sitemaps. Its page Prelum

What people use

From Capsid's public model of 2026-10-11. Also as markdown.