Skip to the content

Capsid menu

A job's life

Step 3 of 9

Worked

The agent works on one branch of one repo.

What it touches

The drawing

Inside Capsid
The same map as a list

Runs everything

  • Capsid The store, the queue, and the credentials every other project runs through. mcp.dustinedwards.info Open Capsid

Shared parts

  • d1-dump shared Backs up each table of a D1 database, keeps the backups on a schedule, and drills the restore. Open d1-dump
  • devkit shared Shared CI workflows, Renovate rules, and test helpers. Open devkit
  • site-runtime shared Security headers, the rate limiter, and the health format that every site imports. Open site-runtime
  • Prelum shared Turns finished writing into pages, feeds, and sitemaps. Open Prelum
  • Capsomer shared The tokens, the shell, and the shared controls every app is drawn with, in plain CSS. capsomer.dustinedwards.info Open Capsomer
  • site-api shared The contract Carrel uses to publish. Open site-api

Websites

  • Dustin Edwards Admin admin Runs dustinedwards.info from a chat, covering health, mentions, media, registries, citations, and lab procedures. Writing stays in Carrel. Open Dustin Edwards Admin
  • Germomics site A podcast and writing site about microbiology and history, with interactive virus and bacteria data pages and browser games. germomics.com Open Germomics
  • dustinedwards.info site Dustin's personal site. dustinedwards.info Open dustinedwards.info
  • TXASM site Runs the Texas Branch ASM meetings: registration, abstract submission and review, the program, and the abstract book PDF. txasm.org Open TXASM
  • julieedwards.info site Julie Edwards's campaign site for the Bluff Dale ISD school board. Its copy lives in D1 and is edited through Carrel. julieedwards.info Open julieedwards.info

Apps

  • Foxing app A reading app and web platform, Letterboxd for books: a web app, an Expo phone reader and a Discord Activity for reading clubs. foxing.app Open Foxing
  • Foxhound Admin admin Runs Foxhound from a chat. It holds no Stripe key and no database: every action is a call to the foxhound Worker's admin API. admin-mcp.foxhoundapp.com Open Foxhound Admin
  • Foxhound app Recovers failed Stripe payments, handles disputes and reports subscription health for merchants, and is paid only on money it recovers. foxhoundapp.com Open Foxhound
  • Foxing Admin admin Runs Foxing from a chat: stats, users, badges, journal posts and catalog health, all through the foxing Worker. Built, not yet deployed. Open Foxing Admin

Writing

  • Carrel writing The writing desk, where drafts are written, checked, and published. carrel.dustinedwards.info Open Carrel
  • Enarratio writing An npm package of charts, with a gallery. enarratio.dustinedwards.info Open Enarratio
  • Writing private Dustin's books: scenes, outlines and story bibles, which Carrel reads and commits through its own GitHub App. Open Writing

Tools

  • Skills tool The instructions AI sessions follow. Open Skills
  • Private skills private Dustin's own session setup, which every AI session loads beside the public skills. Open Private skills
  • capsid-bench tool The study harness that compares Claude Code with and without Capsid on the same tasks, scored on hidden tests. Open capsid-bench
  • Capsid backups private Mirrors Capsid's daily database dumps off Cloudflare every day, so losing the account does not lose the store. Open Capsid backups
Inside Capsid, step by step

A job's life

  1. Posted: a session posts a job over MCP. The Worker checks the caller's grant, picks the model, signs the body and stores the job.
  2. Claimed: an agent claims it. The Worker verifies the body's signature first and records who holds the job.
  3. Worked: the agent works on one branch of one repo.
  4. Blocked: at a push, a deploy, a secret or a merge the agent stops. The job waits with the exact command a person or the signed policy must approve, and resume hands it back.
  5. Pull request: the pull request opens through Capsid's GitHub App, and CI runs on it.
  6. Merged: the five-minute tick merges a pull request whose CI is green on its exact head under the signed auto-merge policy, or the session that opened it merges it on green.
  7. Deployed: the merge to master runs CI on GitHub Actions, which deploys the Worker.
  8. Verified: CI's live gate reads the Worker's /health and checks it reports the commit that was merged.
  9. Claims checked: when the job completes, the Worker reads the pull request, its commits and CI from GitHub and records each claim beside what GitHub says.

Every step

  1. Posted A session posts a job over MCP. The Worker checks the caller's grant, picks the model, signs the body and stores the job.
  2. Claimed An agent claims it. The Worker verifies the body's signature first and records who holds the job.
  3. Worked The agent works on one branch of one repo.
  4. Blocked At a push, a deploy, a secret or a merge the agent stops. The job waits with the exact command a person or the signed policy must approve, and resume hands it back.
  5. Pull request The pull request opens through Capsid's GitHub App, and CI runs on it.
  6. Merged The five-minute tick merges a pull request whose CI is green on its exact head under the signed auto-merge policy, or the session that opened it merges it on green.
  7. Deployed The merge to master runs CI on GitHub Actions, which deploys the Worker.
  8. Verified CI's live gate reads the Worker's /health and checks it reports the commit that was merged.
  9. Claims checked When the job completes, the Worker reads the pull request, its commits and CI from GitHub and records each claim beside what GitHub says.