The standards change when someone shows where they are wrong or where a system broke them. This page says what to send and where it goes: one inbox, hello@ethotechnics.org, or the public repository.
Contribute
Send postmortems, rulings, and inquiry findings from systems you have worked on or followed. The casebook scores failures a court, an inquiry, or a regulator established; the mechanisms catalog needs evidence of fixes working and failing.
A postmortem, research memo, or public record showing an automated decision system whose safeguards held or failed. A case established by a court, an inquiry, or a regulator can be scored in the casebook.
Reviews are paid work, done by Kanav Jain, who wrote this framework, on healthcare AI systems: a safeguards review, a readiness sprint, investor diligence, or a clinical AI safety evaluation. Lessons from a review are published only with your agreement, and anonymized.
Write to us
Fill this in and your mail app opens with the message written. Nothing is sent from this page.
Links, PDFs, slides, or a short write-up all work.
Public repository
The site, its content, and its data live in a public GitHub repository. You can file an issue, propose an edit, or read the data directly.
Every page on the site is a file in the repository. Issues and discussions are public.
Each pull request runs the same content and code checks, whoever opened it.
One JSON file listing the standards, validators, and research, for anyone building tools on the content.
Templates for reporting a bug or requesting content, so a report arrives with what it needs.
What changed in each release, as JSON.
Badge images for the site's build status and content license.
Corrections
Say what is wrong, unclear, or missing: a broken link, a clause that cannot be tested, an example you needed and could not find. A substantive critique gets a written answer saying what changed, or why nothing did.
Feedback inboxes
Share unclear steps, missing citations, or examples you want us to add.
To object to a clause of a standard, use the Object link beside it in the standard's clause register. Each objection is a public GitHub issue, answered within 30 days, and the site's own record lists every answer.
This inbox is for fixing the site's content, not for challenges to decisions. To challenge a decision an institution made about you, use that institution's appeal route. The self-defense checks list what you can ask for and the wording to use.
Security findings go through a separate process: the vulnerability disclosure policy and the security.txt file.