What runs, step by step

The 3 things Capsid does that are worth watching, each told step by step over the parts it really touches. Open one to watch it run.

• A job's life

  One job from the moment it is posted to the moment GitHub's record is checked against what its agent claimed.

  9 steps over 5 parts of Capsid.

  1. PostedA session posts a job over MCP. The Worker checks the caller's grant, picks the model, signs the body and stores the job.MCP WorkerAgentscapsid
  2. ClaimedAn agent claims it. The Worker verifies the body's signature first and records who holds the job.MCP WorkerAgentscapsid
  3. WorkedThe agent works on one branch of one repo.MCP WorkerAgentscapsid
  4. BlockedAt 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.MCP WorkerAgentscapsid
  5. Pull requestThe pull request opens through Capsid's GitHub App, and CI runs on it.MCP WorkerGitHub
  6. MergedThe 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.Five-minute tickGitHub
  7. DeployedThe merge to master runs CI on GitHub Actions, which deploys the Worker.GitHubMCP Worker
  8. VerifiedCI's live gate reads the Worker's /health and checks it reports the commit that was merged.GitHubMCP Worker
  9. Claims checkedWhen the job completes, the Worker reads the pull request, its commits and CI from GitHub and records each claim beside what GitHub says.MCP WorkerGitHubcapsid

  Watch it run

• The nightly backup

  Once a day the Worker copies the whole store to R2, keeps a graduated set of copies, trims old history only once a copy holds it, and the watcher checks that the copy kept off the account is fresh.

  7 steps over 6 parts of Capsid.

  1. DumpedAt 09:00 UTC a daily cron in the Worker dumps every table to R2 with d1-dump, one JSON file each plus the schema.MCP Workercapsid-mediacapsid
  2. Marked completeA completion marker is written last, and only when the dumped tables match the ones the migrations create. A run without it is never counted as a backup.MCP Workercapsid-mediacapsid
  3. MirroredEvery document body is written beside the dump as plain markdown, one file per document.MCP Workercapsid-mediacapsid
  4. PrunedThe newest complete run of each of the last 14 days, 8 weeks and 6 months is kept, and every other run is deleted whole. The newest complete run is never deleted.MCP Workercapsid-media
  5. TrimmedDocument versions older than 90 days and audit rows older than 180 are pruned, after the dump, so every pruned row is in a kept copy.MCP Workercapsid
  6. StampedThe run records its success, and /health warns once that stamp is more than 26 hours old.MCP Workerapp KV
  7. WatchedEvery half hour the watcher reads the newest copy kept off the Cloudflare account and files a finding once it is more than 36 hours old.Five-minute tickGitHub

  Watch it run

• Publishing a post

  A post goes from a private draft in Carrel to a live page on dustinedwards.info, through the one contract every site speaks, with the site deciding what may go live.

  7 steps over 5 parts of Carrel, dustinedwards.info.

  1. DraftedThe writer works in Carrel's editor, which autosaves a working draft only that person can see.Carrel Workercarrel
  2. PreviewedCarrel shows the site's own render of the draft in a sandbox, with the checks' flags and any reviewer's beside it.Carrel WorkerSite Worker
  3. SavedAn Editor or the Owner saves the draft to the site, naming the version it replaces. The site refuses a stale one, so nobody overwrites a newer save.Carrel WorkerSite Workerdustinedwards
  4. PublishedOnly the Owner publishes, and a first publish asks for confirmation. The site's own publish policy decides, so there is one authority.Carrel WorkerSite Workerdustinedwards
  5. Or by instructionThe Owner's AI session may publish through the MCP door, never while a flag is open. It sends no text, so only the saved version goes live, and Dustin is emailed an unpublish link.Carrel WorkerSite Workerdustinedwards
  6. RecordedCarrel indexes the live post, records who published it (an AI session by its client name) and clears the draft that was sent.Carrel Workercarrel
  7. WatchedEvery 15 minutes Carrel runs site-api's conformance suite against the site and emails when its state changes.Fifteen-minute checkSite Worker

  Watch it run