Pedigree

Pedigree is a cryptographic provenance layer for AI-written code. It is conceptually similar to C2PA, but for source code instead of images. The problem is concrete and near-term. On August 2, 2026, EU AI Act Article 50 begins fining organizations that cannot prove which parts of their software were generated by AI. Around 42 percent of committed code today is AI-assisted, and almost none of it carries provenance metadata. There is no standard record of which model produced a change, which mode the agent was running, which Skills governed it, or who approved the merge. Pedigree fixes this at the commit boundary. When an AI agent produces a commit, Pedigree computes a structured predicate capturing the model identity, custom mode slug, content hashes of the active Skills, AGENTS.md hash, prompt hash, risk class, and human approver. That predicate is wrapped into an in-toto Statement, signed into a DSSE envelope with ed25519 or Sigstore keyless signing, and stored in git attestation refs as a tamper-evident audit trail. The output developers and auditors interact with is the Code Passport. It is a single page that renders any commit's full chain of custody, including origin, agent signature, human approval, and verification status, with a QR code linking back to itself. An auditor can verify a commit's authorship in under ten seconds. A companion GitHub Action runs in CI and blocks merges when attestations are missing, invalid, or fail to satisfy the policy in AGENTS.md. The project uses IBM Bob deeply rather than as a generic coding assistant. A custom Provenance Officer mode enforces signing before every push, and a sign-on-commit Skill is content-hashed into every attestation so workflow versions stay auditable. The Bob MCP Builder generated the FastMCP server for pedigree-mcp, which exposes attest_commit, verify_chain, and render_passport tools. watsonx.ai Granite 3.3 8B produces natural-language summaries of each attestation.