Goal
Most scaffold policies in `international/eu_ai_act/v1/` and elsewhere ship without a populated `metadata` block. Add proper `metadata` (title, description, version, references) to as many of them as you have appetite for.
Why this matters
A scaffold with a real `metadata` block is discoverable and useful even before the rule logic is filled in: tooling can list it, contributors can find it, and the next person upgrading it from Scaffold to Implemented has the article references already in place.
This is also a great reading-heavy / light-coding contribution — you don't need to write or change any rule logic, just look up the article and write a few JSON-shaped lines.
Pattern
See `international/eu_ai_act/v1/transparency/transparency.rego` for a fully-populated example:
```rego
metadata := {
"title": "EU AI Act Transparency Requirements",
"description": "Policy to evaluate compliance with EU AI Act transparency requirements",
"version": "1.0.0",
"references": [
"Article 13 of the EU AI Act - Transparency and provision of information to users",
"Article 52 of the EU AI Act - Transparency obligations for certain AI systems",
],
"category": "international/eu_ai_act",
"import_path": "international.eu_ai_act.v1.transparency",
}
```
Target files (start anywhere)
Any scaffold in docs/coverage/eu-ai-act.md marked ⚠️ that lacks metadata. Roughly:
- `compliance/*` — CE marking, conformity, declaration, registration
- `data_governance/*` — data quality, training data
- `documentation/*` — record keeping, automated logs
- `gpai/*` — downstream transparency, systemic risk, technical documentation
- `human_oversight/human_oversight`
- `obligations/*` — deployer, provider, importer, distributor
- `prohibited_practices/*` (the unnamed ones)
- `technical_robustness/robustness`
Same exercise applies to scaffold policies under other frameworks.
Acceptance criteria
Get help
Comment with the file(s) you want to claim. Coordinate here to avoid duplicating work.
Goal
Most scaffold policies in `international/eu_ai_act/v1/` and elsewhere ship without a populated `metadata` block. Add proper `metadata` (title, description, version, references) to as many of them as you have appetite for.
Why this matters
A scaffold with a real `metadata` block is discoverable and useful even before the rule logic is filled in: tooling can list it, contributors can find it, and the next person upgrading it from Scaffold to Implemented has the article references already in place.
This is also a great reading-heavy / light-coding contribution — you don't need to write or change any rule logic, just look up the article and write a few JSON-shaped lines.
Pattern
See `international/eu_ai_act/v1/transparency/transparency.rego` for a fully-populated example:
```rego
metadata := {
"title": "EU AI Act Transparency Requirements",
"description": "Policy to evaluate compliance with EU AI Act transparency requirements",
"version": "1.0.0",
"references": [
"Article 13 of the EU AI Act - Transparency and provision of information to users",
"Article 52 of the EU AI Act - Transparency obligations for certain AI systems",
],
"category": "international/eu_ai_act",
"import_path": "international.eu_ai_act.v1.transparency",
}
```
Target files (start anywhere)
Any scaffold in docs/coverage/eu-ai-act.md marked⚠️ that lacks metadata. Roughly:
Same exercise applies to scaffold policies under other frameworks.
Acceptance criteria
Get help
Comment with the file(s) you want to claim. Coordinate here to avoid duplicating work.