-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add new instrument for technical documentation of AI act #8
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Welcome to our community 🤗 and thank you for your first contribution.
As a first time contributor please make sure to review our contribution guidelines ❤️
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
96c9449
to
8b1a71e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks good to me.
But it would be good to run this before merging (and fix any errors that remain):
./script/validate schema.json instruments/technical_docs_for_high_risk_ai.yaml
This is now fixed with #10
d51d853
to
045ac81
Compare
7f713d4
to
fdc81cb
Compare
Description
This PR adds an instrument with tasks to be done for high-risk AI systems according to the EU AI Act to the registry.
For that purpose the schema has been updated with 'upload_document' and 'form_filling' as type of tasks.
Link to research, assumptions, decisions, risks and questions/open ends on how to incorporate the EU AI Act can be found and reviewed here: https://app.clickup.com/9015737202/v/dc/8cp2evj-515 (Research/AI Act: Technische documentatie)
Link all GitHub issues fixed by this PR.
Make sure to first open an issue, get community approval and only then create Pull Request to resolve it.
All Pull Requests must have an issue attached to them
Resolves #
Checklist
Please check all the boxes that apply to this pull request using "x":