Use cases · Software supply chain & CI

A record for every pull request, agent-written or not.

Coding agents open pull requests all day. Later, when someone asks what changed, whether the tests ran and who or what wrote it, the answer is spread across a CI system and a chat history.

What gets recorded

  • Per pull request: the repo, PR number and head SHA, digests of the diff and the CI job results, and the declared author.
  • The agent and model, if the PR declares them. They are self-attested and labeled that way.
  • Only digests. The diff, prompt and CI output stay on the runner.

What anyone can check

  • The capsule id is posted on the PR. Anyone can verify the capsule and its witness receipt offline.

What runs today

What's built, and what isn't yet.

  • Runs today The Seal PR Capsule GitHub Action in capsule-cli ↗. There is no tagged release yet, so pin it to a commit.

The workflow template ↗