Contributing to UXR

UXR is in Private Alpha, and limited real-world submissions are open. The project is being engineered and tested in public, and the intake process now needs a small, varied stream of real experiences to expose missing entities, relationships, evidence boundaries, vocabulary, and safeguards.

You do not need a dramatic case

You can submit an experience involving an app, website, business, government service, street condition, customer-service interaction, positive outcome, frustrating outcome, mixed outcome, or an ordinary interaction that made you wonder whether the system could work better. Positive experiences matter because UXR also wants to identify practices that preserve agency and deserve replication.

Outside sandboxed regression testing, UXR uses real submissions rather than invented case stories. A real submission may lead to internal case, institution, system, evidence, pathway, or research records. Being mentioned or involved does not automatically make an organization responsible for an outcome.

Submission and publication are separate

Sending material does not automatically create a public case and does not authorize publication. Intake, consent and use authorization, privacy review, evidence analysis, and public release are separate decisions. During Private Alpha, public release remains human-gated.

Ways to contribute

• Share a real experience: serious or casual, positive or negative, as long as it is yours to share.

• Review the method: challenge evidence boundaries, privacy controls, attribution, governance, terminology, and claims of maturity.

• Program or design: help build intake tooling, structured review, deterministic broker checks, automation, testing, accessibility, data modeling, and public interfaces.

• Bring domain knowledge: help UXR understand institutions, public systems, healthcare, finance, consumer services, accessibility, research methods, auditing, law, journalism, or other applicable fields without converting expertise into unreviewable authority.

• Improve verification: help design blind re-grading, inter-grader agreement checks, privacy tests, duplicate handling, and audit-friendly automation.

• Document reforms and good practice: point to institutions or systems that have measurably improved or already handle people well.

What contributors should expect

UXR is unfinished. Categories, schemas, analytical methods, and intake behavior may change as testing finds defects. The first manual regression baseline failed overall, and UXR is publishing that fact while keeping the answer key private. The project does not claim that its executable broker has been validated.

Capacity and independence

UXR currently has no formal programming team, board, or dedicated domain. Human review is the pilot's throughput limit. Contributions can help the project grow, but no contributor, funder, institution, or technical partner receives authority to displace meaningful human agency as UXR's governing center.