Many discussions begin with a strong statement and change when someone asks where it comes from. That is where opinion, narrative and evidence part ways.
Evidence does not make an argument perfect. It makes it accountable. It allows discussion without guesswork and correction without drama.
That is why this site prefers to turn down the volume rather than inflate certainty. When something can be substantiated, it is. When it cannot, that is stated.
A way of looking at things.
This is how I read this topic. The related pieces show that position in practice, dated and signed.
Entries in the corpus.
What is asserted is demonstrated, or it is not asserted
Actor, date, criterion, scope and validity allow a technical claim to be reconstructed. The absence of one does not make the rest false; it reduces what can be concluded and requires the limitation to be stated.
The identifiable responsible party
A significant technical decision must be traceable to human roles with the authority and duty to answer for it. When a machine is involved, traceability extends to those who defined thresholds, approved deployment and retained the ability to intervene.
A verifiable state and public integrity · the cases that already exist
Eight links and the cases that have already tested them · the British algorithmic register that went from 59 to 125 systems in one year, the municipal precursors in Amsterdam and Helsinki, and the FMI's censure of Argentina — and its lifting. Criterion 13 establishes the doctrine; this report provides the evidence, link by link.
Do you have a case that can be read through this criterion?
If this topic intersects with your work — a decision, a source, a question — write to me and share the context.