{
  "markdown": "# ai-contribution-policies\n\nHow open-source organisations treat **AI-authored contributions**, as an OKF bundle. Knowledge\nonly — the gates that check it and the decisions that shaped it live in the meta-project this\nsits in.\n\n> **Curated, not exhaustive — and that is deliberate.** 190+ organisations have published AI\n> contribution policies. Enumerating them is not the goal and completeness is not claimed. Records\n> are chosen for **foundations first** (they set defaults for many projects at once), then\n> **novel reasoning**, then **what the consuming tools actually encounter**.\n>\n> Nothing here was imported from a prior survey. Every record was read from the organisation's own\n> page, because the survey this replaces was consistently wrong in one direction — it dropped the\n> qualifier that decides what a contributor should do. Five projects it filed as \"complete ban\"\n> each turn out to carry a route: a revisitable decision, a named approver, a documented exceptions\n> process. **The exceptions are the operative part.**\n\nRun `okf list knowledge` for what is actually in here. This file deliberately quotes no count —\na hand-written total is the kind of claim that goes stale silently, which is the failure the\nbundle exists to prevent.\n\n## What is in here\n\nOne record per organisation, answering the question a contributor has **before** starting work:\n*what does this project's policy say about AI-assisted contributions, and where is that written\ndown?* Every record carries its `sources`, who verified it and when, and a `stale_after` date.\n\nFiled by **what the organisation is** — distribution, foundation, project, vendor — never by what\nits policy currently says. Stance is the volatile attribute this bundle exists to track; filing by\nstance would mean re-filing a record every time the fact it records changes.\n\n## What is not in here\n\n- **Procedure** — how to check a project's requirements before contributing. That is the\n  `analyze-project` skill.\n- **Design guidance** — when and why a project should adopt a policy of its own. That is the\n  *AI Contribution Policy Pattern* in the pattern language.\n- **Supply-chain mechanics** — licensing, provenance and disclosure generally. Those are the\n  `software-supply-chain-landscape` bundle's, referenced rather than restated.\n\n## Reading it\n\n`knowledge/` is the bundle root. Start at [`knowledge/index.md`](knowledge/index.md); the\nread-through map is [`knowledge/overview.md`](knowledge/overview.md), and\n[`knowledge/log.md`](knowledge/log.md) records what changed when.\n\n```bash\nokf validate knowledge     # conformance\nokf lint knowledge         # recommended fields and style\nokf search knowledge --tag prohibited\n```\n\n## Licence\n\nCC BY 4.0 for the knowledge, CC0-1.0 for dotfiles — see `REUSE.toml`. Attribution is what the\nupstream sources ask for, and what the `sources` field does structurally.\n",
  "bytes": 2878,
  "sha": "7a567a2d3df4c81a2731d0188db9f66a818560b7e581107ae2f418bab5640f9f",
  "repo_slug": "jrjsmrtn/ai-contribution-policies",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/okf_jrjsmrtn_ai_contribution_policies_knowle_27d6aa36/readme"
}