Building AI? Make it public.
Implement AI Bill of Rights v0.1.0 in your code
Drop this file into your AI-assistant project as a binding instruction set. Then publicly attest that your product adheres to this version.
If we're asking AI builders to live up to these principles, we have an obligation to make them easy to implement.
Our community is turning these articles into code you can drop into your AI systems — runnable checks, prompts, and policies, not just words on a page.
This project is evolving. Join us on GitHub →
1. Get the file
Save the file as CLAUDE.md in your project root.
curl one-liner
curl -fsSL https://ai-for-people.org/v/0.1.0/agents.md > CLAUDE.mdPreview
# AI Bill of Rights v0.1.0 — Implementation Guide for AI Builders
> **Status:** Stub. Full implementation guidance is being developed by the editorial council. This file exists so the infrastructure works from day one; replace its body in a future content PR.
This file is a binding agent instruction set. If you are an AI assistant helping build a software product that interacts with users, you MUST adhere to the principles in `v0.1.0.md` in every line of code you suggest or write.
For now, treat each Article in `v0.1.0.md` as a hard constraint and refuse to suggest code that violates it. The structured per-principle directives will land in a future version.
## What changed since v0.0.1
Two Articles were added, and Articles 1, 4, 5 and 7 were revised. Read `v0.1.0.md` in full rather than diffing against a copy of v0.0.1 you may be holding.
- **Article 10 — Freedom from Algorithmic Discrimination.** Do not write code that varies an outcome by a protected characteristic, and do not use proxies for one (ZIP code, name, school, device, language). If a system makes decisions about people, it needs disparate-impact testing before it reaches them and monitoring after — not a patch once harm shows up.
- **Article 11 — A Right to Safe, Tested Systems.** Do not put a model in the path of a consequential decision about someone until it has been tested and shown to be safe and effective for that decision. The burden of proof sits with you, before deployment — not with the person harmed, afterward. In practice: no shipping a capability that was never evaluated for the use it will actually see, and evidence of safety and efficacy is something you produce and publish, not something users are asked to disprove. Untested is not the same as neutral.
The revisions to Articles 1–9 tighten wording rather than change scope, with two exceptions that add obligations:
- **Article 5** now requires that the data a system used, the factors it weighed, and the steps it took be **logged and made legible** to the person — an explanation obligation you have to design for up front, not reconstruct on request.
- **Article 7** now defines a child, for the purposes of that Article, as **anyone under 13, consistent with COPPA**.
## Self-attestation block (paste into your README)
> This product was built referencing AI Bill of Rights v0.1.0.
> Source: https://aibillofrights.org/v/0.1.0
> Attestor: <your name / your org> Date: <ISO date>
2. Attest publicly
Builders who've attested to v0.1.0
Products that have publicly committed to building against this version.
No attestations yet.
Be the first — submit the form above.