Thanks for helping improve the Regulation-as-Code (RaC) specification.
All contributions are made under the repository's CC0 1.0 dedication. Sign off every commit to certify you have the right to contribute it:
git commit -s -m "your message"
This appends a Signed-off-by: line, asserting the Developer Certificate of Origin.
The grammar is frozen at v1. Changes to normative behavior (grammar, compilation, evaluation, receipt) require an RFC — see rfcs/README.md and GOVERNANCE.md. Editorial improvements (typos, clarifications, examples, conformance vectors) can be opened as ordinary PRs.
A regulation profile (e.g. AI-Act, DORA) is a SourceManifest plus its citations, placed under profiles/<regulation>/v1.md. New profiles ship continuously and do not require an RFC. To propose one:
- Add
profiles/<regulation>/v1.mdfollowing the structure ofprofiles/gdpr/v1.md. - Bind requirements to evidence families documented in
spec/evidence.md(or add a new family binding there). - Include at least one conformance vector under
conformance/vectors/exercising the profile. - Cite the authoritative legal source (e.g. EUR-Lex) via
citationUrlfor each obligation where a stable citation exists (citationUrlis a SHOULD, not a MUST — seespec/grammar.md§4).
Use the PR template. State whether the change is normative or editorial, and which spec file(s) it touches.
Participation is governed by CODE_OF_CONDUCT.md.