Open source · Apache 2.0
Boards, counsel and regulators need a shared, inspectable way to set and evidence AI risk appetite. The app suite is open source under the Apache License 2.0, so anyone can check how it reaches a finding and run it on their own terms. There are four ways to help. Choose the one that suits your role; none depends on the others.
Four ways to help
Developers, lawyers, internal counsel and organisations can each give something different. Every way of helping works without your name attached.
01
Run the apps, open an issue when something is unclear or wrong, and send fixes. Starring a repository helps others find it. Need help running them? See the support options.
Sign commits with a Developer Certificate of Origin sign-off (git commit -s). Contributions are made under the Apache License, as its section 5 provides.
02
Review one framework step, one Atlas record or one regulatory mapping, about an hour. Tell us where it is wrong or unclear.
Anonymous or credited, your choice. Review is not advice: you give no view on any organisation’s obligations and take no responsibility for how the apps are used.
Offer a review →03
Tell us privately that your organisation uses or is trialling the apps, and what would make them more useful.
Private by default. We never name a person or an organisation without written approval from both, and either can withdraw it.
Tell us privately →04
Sponsor the apps through GitHub Sponsors, or fund their upkeep by invoice: maintenance, security fixes and keeping the Obligations Atlas current. We report how funds were used once a year.
Funding buys no influence over the method or its outputs, and is separate from fees for Triodian’s facilitation and deployments.
Ask about funding →Not legal advice. The apps record positions and state what documents show. Reviewers give no legal advice and form no client relationship. Whether anything meets a legal obligation is a question for your counsel.
What we promise
The people best placed to help are often the least able to be named. These rules apply to every way of helping.
Nobody is named on this site, in a repository or in any material without written consent from the person and, where relevant, their organisation. Consent can be withdrawn at any time.
Current or recent regulator staff can review anonymously only, and are never listed.
Funding for the apps is reported once a year and kept separate from Triodian’s paid services, so supporting the project never buys the method.
The Apache License does not cover the Triodian name or logo (section 6). You may say truthfully that your work uses or is based on the apps, but please do not imply that Triodian endorses it.
The five repositories
Every repository carries the Apache 2.0 licence, a NOTICE file and a SUPPORTING.md saying what to review in that app.
| App | What it does | Repository |
|---|---|---|
| AI Obligations Atlas | What applies, by jurisdiction and entity type | github.com/Triodian/obligations-atlas How to help with this app |
| AI Board Direction | The board’s position on AI | github.com/Triodian/board-direction How to help with this app |
| AI Risk Appetite | The appetite, decision by decision | github.com/Triodian/risk_appetite How to help with this app |
| AI Use Assessment | Evidence that each AI use stays within it | github.com/Triodian/use-assessment How to help with this app |
| AI Confidentiality Exposure Assessment | Keeping a confidential matter out of AI | github.com/Triodian/Confidentiality-Exposure-Assessment How to help with this app |