Evidence Validation and Confidence: Development Notes
Status: Development Notes: Intentionally Deferred Version: 0.2
Summary: A reserved methodology layer for evidence provenance, corroboration, conflicting accounts, pattern evidence, identity confidence, uncertainty, and correction.
Document status. This is an intentionally deferred development document. It identifies a methodology UXR expects to need, preserves useful design notes, and defines the questions that future work must answer. It does not yet establish an adopted scoring system, threshold, formula, or operating procedure.
Why this remains open. Premature precision can create false authority and lock UXR into assumptions that have not survived evidence, domain comparison, affected-person review, adversarial testing, or operational experience. UXR will not define this layer further merely to make the documentation look complete.
How this document should be reviewed. Reviewers are invited to identify missing considerations, risks, dependencies, examples, and candidate approaches. The absence of a final mechanism is intentional. A proposal should not be treated as adopted until UXR has published the evidence, tests, and reasoning supporting it.
Purpose. UXR intends to transform lived experience into validated public knowledge. That requires published methods for evaluating evidence without pretending that every source, record, recollection, pattern, or institutional response proves the same thing.
Separate judgments. Evidence provenance, identity confidence, claim credibility, factual accuracy, causal inference, severity, and confidence in a final finding are different judgments. A verified person can submit a false claim. An anonymous person can submit authentic evidence. An authenticated record can prove where a statement came from without proving that the statement itself was true.
Direct artifact verification and pattern corroboration. A directly inspectable artifact may verify that a message, transaction, interface state, or interaction occurred, subject to authentication and context. Pattern corroboration asks whether sufficiently independent accounts describe materially similar system behavior. These are different evidentiary routes. A pattern can justify investigation or support a finding without converting every detail of every account into verified fact.
Candidate evidence sources. Future methods may evaluate authenticated interaction records, original emails, screenshots, photographs, recordings, voicemails, notices, receipts, logs, system records, policies, witness accounts, institutional responses, expert analysis, independent replication, and recurring reports from separate people.
Proof should strengthen a report, not become an absolute gate. UXR should request verifiable material whenever it is reasonably available. A person may nevertheless lack records because an organization controls them, a system failed to preserve them, evidence was never created, the person faced danger in collecting it, or the experience itself prevented documentation.
Pattern evidence. Multiple sufficiently independent accounts may provide evidence of a recurring pattern even when no single submission proves every element. Volume alone does not establish truth. Future methods must evaluate independence, similarity, timing, incentives, duplication, shared sources, and alternative explanations.
Identity and anonymity. Confidence that submissions come from distinct human beings can reduce manipulation, but identity verification must not become forced surveillance or exclude whistleblowers, vulnerable people, undocumented people, or those exposed to retaliation. Identity assurance and claim evaluation must remain separate.
Conflicting and missing evidence. Future methods must address contradictory accounts, incomplete records, sampling bias, institutional control of authoritative data, destroyed or inaccessible evidence, power differences in documentation capacity, and the risk of treating polished institutional records as inherently superior to lived experience.
Human-readable inference trail. Any future confidence score or public finding should show, in understandable language, which evidence supports which proposition, what remains uncertain, which competing explanations were considered, and where human judgment entered the process. Explainability requires more than publishing a number or naming a model.
Candidate technical and procedural tools. Collected notes include chain-of-custody records, source hashes, authenticated share links, integrity tokens, timestamps, redaction, consent controls, confidence categories, transparent inference trails, human review triggers, correction paths, and appeals. None is adopted merely by appearing here.
Dependencies before adoption. This methodology requires intake pilots, privacy and security design, adversarial testing, representative case studies, legal and ethical review, domain expertise, and published evaluations of false-positive and false-negative risks.
Question for Review
What distinctions and safeguards must UXR preserve before it can responsibly assign confidence to evidence or findings?
Explore the UXR Framework
- UXR: Founding Declaration
- What UXR Means by Human Agency
- The Universal Scope of UXR
- Friction, Pain, Harm, and Invisible Taxes
- UXR Independence and the One-Way Authority Rule
- How UXR Creates Accountability
- Severity, Urgency, and Recoverability: Development Notes
- Evidence Validation and Confidence: Development Notes
- Participation Integrity and Anti-Brigading: Development Notes
- UXR Intake and Evidence Collection: Working Concepts
- Contributor Continuity, Resolution Knowledge, and Reform Recognition
- UXR: Current Project Status
- Contributing to UXR