System identity
Supplier, intended purpose, model and configuration version.
delta-sierra.com
David Salvan | Books, Public Policy and Mars Colonization
A credible system is not one that claims never to fail, but one that detects, documents and corrects failures.
An incident may involve an erroneous output, discriminatory behaviour, unauthorised data exposure, loss of traceability, an uncontrolled model change, a security breach or a failure of human oversight. The response must therefore combine operational, legal, technical and institutional action.
Supplier, intended purpose, model and configuration version.
Detection time, containment, notifications, decisions and recovery.
People, cases, rights, data and services potentially affected.
Logs, inputs, outputs, alerts, user reports and preserved technical artefacts.
Data, model, software, security, process, training or governance failure.
Fix, rollback, compensation, retraining, contract action and follow-up tests.
| Control | Purpose |
|---|---|
| Operational audit | Verify performance, logs, security, human oversight and corrective action. |
| Independent technical audit | Challenge supplier claims and reproduce tests using authorised evidence. |
| Rights review | Examine effects on affected persons, remedies and non-discrimination. |
| Parliamentary reporting | Provide understandable aggregate indicators, incidents and deployment decisions. |
| Public information | Explain purpose, limits, safeguards and significant corrective measures without compromising judicial secrecy or security. |