The working A prototype: use its controls to test the build question.
Show what happens after someone reports that a system is wrong or harmful.
RN conceived the question, structured the evidence boundaries, designed the experience, implemented the prototype and documented its limits.
This independent prototype demonstrates an approach; it is not a deployed client system, professional advice or proof of real-world outcomes.
Work through the controls with a situation of your own rather than the sample values. The tool responds to what you put in, so the useful output comes from real input, and everything is processed in your browser as you go. Any sample content you find already loaded is there to show the shape of a filled-in state, and you can clear it and start again at any point.
The build overview sets out the question, the purpose, the role and the evidence status in one place, and the public record behind it states what changed, what another person can reuse and what supports the system. If you want to judge how far this build should be trusted, the record is the page to read, not this one.
Feedback → Change Governance Lab
Show what happens after someone reports that a system is wrong or harmful.
CHANGE OR OUTCOME PENDING
Next: Triage and route
Synthetic redacted report. Anonymity is requested and identity is not stored. The response target is not an SLA promise; stage completion is not remedy or measured effectiveness.
Waiting for prior governed stage.
Evidence pending · Owner pendingWaiting for prior governed stage.
Evidence pending · Owner pendingWaiting for prior governed stage.
Evidence pending · Owner pendingWaiting for prior governed stage.
Evidence pending · Owner pendingWaiting for prior governed stage.
Evidence pending · Owner pendingReporter safety, linkage, and non-claims
- Consent, anti-retaliation safety, anonymity, escalation, appeal, and affected-person communication have distinct synthetic records.
- Duplicate/related report links are preserved without silently merging reports.
- Change links back to feedback and includes synthetic regression and rollback records.
- Record completeness does not prove the report true, triage correct, response timely, decision fair, change effective, harm remedied, or duties satisfied.
- A response target is not an SLA guarantee; implementation verification is distinct from measured affected-person outcome.
- Anonymity, retaliation safety, appeals, reopening, communication, regression, and rollback require real operational and participant validation.