# AI use cases for AI Charter (mrtinkz/ai-charter) Repo: [mrtinkz/ai-charter](https://github.com/mrtinkz/ai-charter) | Use cases: 4 | Page: https://dedupedai.com/use-cases/mrtinkz-ai-charter/ A public website and open registry for the Universal AI Charter, a set of plain-language AI governance principles, where companies can certify their AI models. This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL. - Certify a model and submit it to the public registry: https://dedupedai.com/use-cases/mrtinkz-ai-charter/certify-model-in-public-registry/ - Propose a new hazard placard category: https://dedupedai.com/use-cases/mrtinkz-ai-charter/propose-new-hazard-placard/ - Check a certification file before submitting it: https://dedupedai.com/use-cases/mrtinkz-ai-charter/check-certification-file-before-submitting/ - Read the charter to draft an internal AI policy: https://dedupedai.com/use-cases/mrtinkz-ai-charter/read-charter-to-draft-internal-policy/ ## How to certify a model and submit it to the public registry with AI Charter Repo: [mrtinkz/ai-charter](https://github.com/mrtinkz/ai-charter) | Difficulty: Intermediate | Time: 60 minutes | Basis: From the README Fill in the certify form, save the JSON file, and open a pull request to list the model in the registry. **Who it is for:** A company compliance or AI team that wants to disclose a model's training sources, hazards, and known problems against the charter. **The problem:** Disclosing a model's details to the public in a consistent format is hard without a shared template and a review process. **The outcome:** A certification JSON file is added to the registry through a pull request that others can review before it goes live. ### Steps 1. Clone the repository with git and open the project folder. (inferred, check the README) 2. Run `npm install` in the project folder. 3. Run `npm run dev` and open the local address it prints, then go to /certify. 4. Fill in the form for company, version, status, training sources, agentic decision-making, hazard categories, and unintended consequences, then download the certification JSON file. 5. Add the file to src/data/certifications/ and open a pull request. ### Prompt to paste into your agent ```text Work in the mrtinkz/ai-charter repository. Use the certify form at /certify to create a certification JSON file for , then copy it into src/data/certifications/ and run `npm run build`. Expected output: a new JSON file in that folder and a passing build. Verify the file appears in the /registry page after `npm run dev`. ``` ### Caveat The README says anyone can review a pull request before it goes live, but it does not describe how review decisions are made. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/mrtinkz-ai-charter/certify-model-in-public-registry/ ## How to propose a new hazard placard category with AI Charter Repo: [mrtinkz/ai-charter](https://github.com/mrtinkz/ai-charter) | Difficulty: Intermediate | Time: 45 minutes | Basis: From the README Add a labeled, severity-rated hazard entry to the placard definitions and open a pull request. **Who it is for:** An AI safety or risk researcher who has found a hazard type that the current placard list does not cover. **The problem:** A certification cannot disclose a hazard that has no placard category, and the list has no built-in way to add one. **The outcome:** A pull request that adds a new hazard placard with a label, severity, and one-line description to the shared definitions. ### Steps 1. Clone the repository with git and open the project folder. (inferred, check the README) 2. Run `npm install` in the project folder. 3. Open src/types/certification.ts and add an entry to HAZARD_CATEGORY_DEFINITIONS with a label, severity, and one-line description. 4. Run `npm run build` to type-check the change. 5. Open a pull request against src/types/certification.ts. ### Prompt to paste into your agent ```text In the mrtinkz/ai-charter repository, add a hazard entry to HAZARD_CATEGORY_DEFINITIONS in src/types/certification.ts for , with a label, severity, and one-line description. Run `npm run build`. Expected output: a passing build and a diff that adds only that entry. Verify the new entry appears on /placards after `npm run dev`. ``` ### Caveat The README does not say how severity levels are defined, so the severity value a contributor picks needs to be justified in the pull request. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/mrtinkz-ai-charter/propose-new-hazard-placard/ ## How to check a certification file before submitting it with AI Charter Repo: [mrtinkz/ai-charter](https://github.com/mrtinkz/ai-charter) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Run the type-check, build, and lint steps on a new certification file before opening a pull request. **Who it is for:** A developer or compliance engineer who has written a certification JSON file and wants to confirm the project still builds before review. **The problem:** A malformed or inconsistent certification file could break the build or get rejected in review. **The outcome:** A clean type-check, build, and lint result that shows the new certification file does not break the project. ### Steps 1. Place the certification JSON file in src/data/certifications/. 2. Run `npm run build` to type-check and build for production. 3. Run `npm run lint` to run oxlint. 4. Run `npm run preview` and open the registry to confirm the model is listed. ### Prompt to paste into your agent ```text In the mrtinkz/ai-charter repository, place the certification file .json in src/data/certifications/, then run `npm run build` and `npm run lint`. Expected output: both commands finish without errors. Verify with `npm run preview` that the model appears on the /registry page. ``` ### Caveat The README says the build type-checks, but it does not list the fields a certification file must include, so a passing build does not confirm the content is complete. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/mrtinkz-ai-charter/check-certification-file-before-submitting/ ## How to read the charter to draft an internal AI policy with AI Charter Repo: [mrtinkz/ai-charter](https://github.com/mrtinkz/ai-charter) | Difficulty: Beginner | Time: 30 minutes | Basis: From the README Use the charter sections as a checklist when drafting a company's own AI governance policy. **Who it is for:** A policy lead or legal reviewer at an organization that builds or uses AI models and needs a governance starting point. **The problem:** Writing an AI governance policy from nothing takes time, and it is easy to miss topics like disclosure and accountability. **The outcome:** A list of charter topics mapped to the organization's own policy sections, with gaps marked for the internal team to fill. ### Steps 1. Open the live site at https://mrtinkz.github.io/ai-charter/ and go to /charter. 2. Read each section: Access & Equity, Innovation & Freedom, Governance & Disclosure, Accountability & Safety, Infrastructure & Data Centers, and Global & Historical. 3. List the principles in each section that match your organization's current policy. 4. Mark the principles with no matching policy as gaps for the internal review. ### Prompt to paste into your agent ```text Using the Universal AI Charter at https://mrtinkz.github.io/ai-charter/charter, compare its six sections against this policy document: . Expected output: a table of charter principles marked as covered or missing in the policy. Verify that each principle you cite appears on the charter page. ``` ### Caveat The charter is described as a living document that is revised over time, so a mapping done today may not match a later version. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/mrtinkz-ai-charter/read-charter-to-draft-internal-policy/