UXR Complete Reviewer Packet

UXR creates accountability by turning credible evidence about human experience into information that reaches every audience capable of rewarding improvement or imposing consequences. Visibility is not the final purpose. Reform is.

The accountability chain. People document friction, exclusion, coercion, delay, harm, or unusually humane performance. UXR evaluates the evidence under published methods. The responsible organization receives the findings, an opportunity to respond, and practical directions for improvement. UXR then publishes and routes validated findings so that people and institutions can act.

The public. UXR gives people an understandable performance signal they can use when deciding where to spend money, work, live, obtain healthcare, study, travel, or place their trust. A Blue Zone designation should mean that an organization has demonstrated strong performance in practical agency, dignity, comprehension, access, contestability, and remedy. Where supported by evidence, UXR may also report a Human Time Dividend showing time reclaimed relative to a documented comparison baseline.

Responsible organizations. Companies, agencies, and other organizations receive the evidence, the affected UXR standards, the observed human consequences, an opportunity to respond, suggested corrective directions, and a path toward reevaluation. UXR should make genuine reform achievable, visible, and worth pursuing without making denial consequence-free.

Corrective grace. When circumstances permit, UXR may notify a responsible organization of substantiated concerns before initial public reporting and provide a reasonable opportunity to begin corrective action. This grace exists to produce reform, not to grant additional time to continue harm or conceal findings. Whether it is offered and how long it lasts depend on urgency, severity, ongoing harm, prior knowledge, the scale of required reform, and demonstrated good faith.

Credible corrective action. An organization need not complete every reform immediately, but it must acknowledge the problem, stop preventable ongoing harm where reasonably possible, establish a credible corrective plan, and begin measurable action. Promises, public relations statements, procedural activity, or requests for additional time do not by themselves constitute reform.

Publication and the reform record. Corrective grace may be shortened or withheld when delay would expose people to continued danger or deprivation, when the organization has already received substantial notice, when it has concealed or defended the harmful practice, when notification could enable retaliation or destruction of evidence, or when prompt public disclosure serves an overriding human need. Notice does not create an indefinite veto over publication. Tactical delay, superficial compliance, or intentional stonewalling may itself be evaluated as strategic friction. When an organization responds constructively, UXR should report both the original condition and the verified corrective action. A record showing that an organization listened, acted, and improved may provide stronger evidence of humane institutional behavior than a claim that no problem ever existed.

Investors and financial decision-makers. UXR findings can help investors, lenders, insurers, boards, and procurement officials identify operational practices that create customer attrition, regulatory exposure, employee exhaustion, reputational risk, inaccessible remedies, or dependence on transferring costs to people with less power.

Government and regulatory authorities. When validated findings indicate possible legal, regulatory, safety, civil-rights, accessibility, labor, or consumer-protection failures, UXR may route those findings to bodies that already possess lawful authority. UXR does not need to impersonate a regulator to make fragmented harm harder to ignore.

Other accountability audiences. Journalists, researchers, advocates, workers, professional associations, elected officials, and affected communities may use UXR findings to investigate patterns, compare institutions, demand correction, or recognize unusually humane performance.

Verifiable interaction records. Organizations seeking Blue Zone recognition should, where feasible, let people securely retrieve, export, or authorize access to records of their own communications and consequential interactions. Records may use an authenticated share link, integrity token, timestamp, digital signature, or another method that lets an independent reviewer confirm that the record came from the organization and has not been altered. Verification establishes provenance, not whether every statement in the record is true or whether the record is complete. Reasonable privacy and security protections remain necessary, but they may not become a pretext for denying people usable access to their own records. This practice strengthens Blue Zone performance but cannot by itself establish Blue Zone status.

Fair process and correction. An organization must have a meaningful opportunity to review the evidence, respond to findings, identify factual errors, and describe corrective action. UXR must publish material responses, correct substantiated errors, explain unresolved disagreements, and provide an appeal or reevaluation path. Fair process protects both human beings and the credibility of UXR. It operates on published, proportionate timelines and does not create an indefinite veto over publication.

Improvement changes the record. UXR should measure and recognize verified improvement. Better scores and Blue Zone recognition must reflect better human experience, not payment, public relations, promises, or access to UXR. An organization that repairs a harmful system should be able to demonstrate that progress publicly.

Equal application. UXR routes findings according to the nature of the evidence, not the political identity or ownership form of the organization examined. Public agencies and private companies receive the same duties of evidence, response, correction, and accountability.

The teeth. UXR's power comes from credible evidence, understandable comparison, public visibility, and deliberate routing to people who control revenue, investment, employment, contracts, regulation, reputation, and legitimacy. An organization need not fear accurate evidence, fair evaluation, meaningful correction, and transparent standards unless it benefits from keeping its effects on human beings invisible.

Document status. This document establishes working principles and preserves design notes for contributor continuity, resolution knowledge, and reform recognition. It does not represent a functioning ticketing system, adopted status taxonomy, verified advice service, causal-attribution method, or rewards program.

Why this layer matters. A reporting system can extract labor from the same people it claims to serve. A contributor may survive the original problem, spend additional time documenting it, surrender evidence, receive a ticket number, and never learn whether anything happened. UXR should not treat a person's testimony, time, and emotional effort as a one-way data transfer.

Contributor continuity. A contributor should retain a durable connection to their original account, submitted evidence, consent and attribution choices, corrections, supplements, and personal report history. UXR should provide a case identifier and a record the contributor can return to without reconstructing the experience from memory.

Understandable report record. A future record may include submission date, evidence received, evidence requested, assessment stage, issue-cluster relationship, organizational response, publication status, accountability routing, reform activity, reported implementation, verification, closure, monitoring, and reopening. The interface must explain what each state means and must not use 'under review' as an indefinite administrative void.

Status reflects evidence, not theater. Not every report will pass through the same sequence. Status changes should correspond to an observable event, decision, dependency, or completed action. When work cannot proceed, UXR should state why, what would change that condition, and whether the report remains preserved as an unresolved signal.

Notifications and control. Progress notifications should be opt-in and granular. A person may want notice only when additional information is needed, a finding is published, an organization responds, a reform is implemented, or a case materially changes. Notification design must not become another source of pressure, surveillance, or administrative noise.

Contributor rights and evidentiary independence. The contributor should be able to review, correct, supplement, export, and manage permitted uses of their own testimony and evidence. The contributor does not gain unilateral control over an aggregate issue cluster, other people's evidence, UXR's independent findings, confidence assessments, or corrections required by contrary evidence. Continuity preserves participation without converting a public finding into private property.

Resolution knowledge. UXR should be able to return practical value by showing what materially similar people did, what happened next, and how well the outcome was verified. This feature should help people recover agency while broader accountability and reform continue.

Workaround is not reform. Every resolution path should be classified. Candidate classes include Temporary Workaround, Individual Resolution, Escalation Path, Organization-Provided Fix, and Verified Systemic Reform. A person who succeeds after six calls, a regulator complaint, and hours of unpaid coordination has found an escape route; the burden of that route remains evidence of the original harm.

Similarity must be specific. Matching should consider the person's objective, organization or responsible system, department, jurisdiction, product or policy, obstruction encountered, time sensitivity, eligibility or account conditions, evidence available, and steps already attempted. Shared brand names or broad complaint categories are not enough.

Confidence and safety labels. A suggested path should disclose its source, the number and independence of reported successes, verification status, date last known to work, applicable jurisdictions or conditions, expected burden, and known costs or risks. Medical, legal, financial, employment, immigration, housing, and safety-sensitive paths require stronger review and clear boundaries. UXR must not present an anecdote as authoritative advice.

Outcome feedback loop. Contributors should be able to report whether a suggested path worked, failed, changed, or caused additional harm. Outcome reports become new evidence subject to the same provenance, independence, and confidence rules as other submissions. They should improve matching without retroactively overstating what UXR knew when advice was shown.

Recognition for consequential contribution. With explicit consent, UXR may recognize contributions that materially supported evidence, pattern discovery, accessibility, resolution knowledge, reform design, or verified implementation. The strongest recognition should describe the actual consequence of the contribution rather than award generic points.

No complaint gamification. UXR should not reward report volume, accusation severity, organizational targets, public outrage, or competitive rankings. Leaderboards and volume-based badges would create incentives for brigading, exaggeration, repeated reporting, and performative participation.

Causal humility. Recognition must distinguish contribution from sole causation. A report may contribute to a cluster, investigation, finding, or reform without proving that one person or UXR alone caused the outcome. Public language should state what changed, what evidence supports the connection, and what remains uncertain.

Privacy and attribution. Recognition must be private by default and public only by explicit choice. Options may include a name, pseudonym, private history, downloadable acknowledgment, or no recognition. Withdrawing public attribution should not require deleting evidence that UXR must lawfully or ethically preserve, and those boundaries must be disclosed before consent.

Systems not yet defined. UXR is intentionally not yet fixing ticket states, matching algorithms, advice-review thresholds, notification defaults, contributor-control mechanics, recognition labels, or causal-attribution rules. Those decisions depend on real intake pilots, evidence methodology, privacy and security design, participation-integrity testing, domain-specific safety requirements, and contributor research.

Next development stage. Prototype the contributor record and resolution loop alongside intake. Test whether people understand status, can correct records, can distinguish workarounds from reform, can evaluate the confidence and risk of suggested paths, and can control recognition without added burden.

UXR is currently in its foundation and public-documentation stage. The project has an extensive conceptual framework, but the complete reporting, validation, scoring, dashboard, governance, and participation systems described in planning documents do not yet operate as public services.

What exists now. A foundational body of work defines the problem, proposed principles, intended scope, economic consequences of friction, early measurement concepts, governance concerns, and possible implementation paths. A structured public documentation system is now being built so those ideas can be reviewed without compressing them into one monolithic document.

Current document architecture. The public framework now has three functional layers. The constitutional layer defines purpose, universal scope, equal application, and the project's enduring obligation to human agency. The principles and governance layer defines agency, invisible costs, independence, accountability, and the boundaries that constrain later systems. The methodology and operations layer preserves developing work on severity, evidence, participation integrity, intake, contributor continuity, case studies, domain methods, and eventual scoring. These labels explain the documents' current roles; they do not place any layer beyond evidence, criticism, revision, or UXR's own standard.

What does not yet exist. UXR does not currently accept public reports through a specialized intake AI, issue official UXR scores, operate public dashboards, certify Blue Zones, publish verified Human Time Dividend estimates, operate authenticated evidence-linking systems, provide durable report tracking or resolution matching, confer contributor recognition, provide regulatory escalation, or claim institutional authority. Descriptions of those systems remain proposals until they are built, tested, governed, and publicly documented.

Why publish before building. The project's central principles need scrutiny before software and organizations make those principles difficult to change. Publishing the constitutional layer first allows people with lived experience, technical expertise, domain knowledge, governance experience, and critical objections to identify missing assumptions.

How documents will be labeled. UXR materials will identify their status and version. Draft means the language remains under development. Open for Review means focused public feedback is requested. Adopted means the document currently governs UXR. Superseded means a newer identified version has replaced it.

The present task. The current work separates UXR's enduring purpose from methodology, operations, business models, domain standards, and case studies. This reduces the risk that one implementation decision, industry, funding theory, or personal experience accidentally becomes the definition of the whole project.

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.

Human beings live inside systems human beings created. Those systems shape what people can understand, choose, accomplish, challenge, repair, and escape. When a system works against the person using it, the cost rarely appears on a receipt. People pay through lost time, confusion, stress, humiliation, physical danger, financial harm, abandonment, and the gradual loss of belief that anything can change.

Purpose. User Experience Reform exists to restore and expand human agency wherever people interact with human-made systems. UXR makes the effects of those systems visible, measurable, comparable, and open to reform.

Universal scope. UXR does not belong to one industry or one kind of interface. If human beings designed, built, maintained, required, regulated, funded, automated, or mediated access through something, UXR may examine and report on how it affects human beings. Its scope includes roads, traffic signals, buildings, light switches, appliances, automobiles, software, customer service, healthcare, schools, workplaces, taxes, laws, government agencies, financial systems, physical spaces, and every future domain in which human-made structures influence human action. This scope defines what UXR may study, not a claim of governmental jurisdiction or coercive authority.

Human agency. Agency means more than the existence of a theoretical choice. It means the practical ability to understand a system, make a meaningful decision, act without unnecessary obstruction or coercion, preserve time and dignity, reverse or contest consequential decisions, obtain an effective remedy, and participate in changing systems that govern one's life.

Friction, pain, and harm. UXR measures friction, but friction alone is not the governing value. Some friction protects safety, consent, deliberation, or security. Some apparently effortless systems quietly remove choice through manipulation, forced defaults, surveillance, lock-in, or deceptive consent. UXR therefore asks not only whether an interaction is easy, but how it distributes control, knowledge, burden, risk, time, and remedy.

The governing test. For every human-made system, UXR asks: Does this system expand, preserve, transfer, constrain, or extract human agency, and who benefits?

Evidence and fair process. UXR transforms individual experience into validated public knowledge. Lived experience identifies effects, patterns, and questions; it does not automatically determine causation or a score. UXR's methods must remain explainable, reproducible, open to correction, and strong enough to reveal recurring patterns that isolated complaint systems conceal. Organizations examined by UXR must receive a meaningful opportunity to respond, and UXR must correct substantiated errors. When circumstances permit, fair process may include corrective notice before initial public reporting, but notice does not create an entitlement to continued confidentiality, delay, or veto over publication.

Human dignity first. People are not merely data sources, customers, claimants, patients, taxpayers, employees, passengers, or users. Every interaction begins with recognition of the human being experiencing it. Systems do not earn immunity because their failures have become ordinary.

Independence. No external party may control UXR or gain decision-making authority, privileged influence, special access, favorable treatment, or exceptions through funding, participation, expertise, partnership, employment, appointment, or service relationships. Contributions may inform UXR only through transparent, evidence-governed processes applied without special treatment. UXR's duty remains with the human beings affected by the systems it examines.

Equal application. UXR applies the same human-agency standard to private companies, governments, nonprofits, schools, unions, technologies, and UXR itself. Ownership, political party, ideology, popularity, or stated intention cannot substitute for evidence of a system's effects on human beings.

UXR under its own standard. UXR must subject its own systems to the same standards it applies to others. Core pathways for submitting evidence, proposing corrections, accessing the public record, understanding decisions, and seeking remedy must remain free and must be designed to meet UXR Blue Zone standards. Optional paid services may add convenience, analysis, or capabilities, but may not degrade the free pathway, withhold public information, reduce agency, or create privileged influence. UXR may not exempt itself from criticism, measurement, correction, or reform.

Reform and positive visibility. UXR exists to produce improvement, not merely outrage. It exposes preventable harm and also identifies systems that return time, understanding, dignity, safety, and control to people. Recognition must never become an endorsement or a substitute for evidence. UXR provides evidence, standards, and public findings. Individuals, markets, democratic institutions, regulators, investors, and communities decide how to act on them.

A public measurement and accountability framework. UXR is not simply a complaint channel. It seeks to create a shared public framework capable of showing the cumulative human cost of systems that currently treat friction, delay, confusion, and attrition as free, while making humane performance visible enough to reward.

A living project with an enduring center. UXR must learn from the people affected by the systems it examines. Its domains, methods, measurements, and language should evolve through evidence and public contribution evaluated for substance, not volume, sponsorship, institutional power, or organized pressure. Substance includes relevant lived experience and does not require institutional credentials, technical language, professional presentation, or conventional access to evidence. Its central obligation does not change: UXR exists to restore and expand human agency. No amendment, partnership, technology, or operating model may reverse that relationship by making institutional or corporate agency its controlling purpose.

The work begins by making the invisible visible, giving isolated experiences a shared structure, and returning to people the knowledge that systems made by humans can be changed by humans.

People pay for poorly designed and poorly governed systems even when no invoice records the charge. The payment may take the form of time, cognitive load, repeated effort, stress, humiliation, financial loss, physical risk, abandoned rights, or lost opportunity. UXR calls these costs invisible taxes because institutions routinely impose them without measuring or disclosing them.

Friction. Friction is the effort a system requires beyond what the person's goal reasonably demands. Repeated forms, unnecessary travel, contradictory instructions, waiting without information, forced channel changes, preventable errors, and administrative loops all consume human life.

Necessary friction. Not every obstacle is harmful. Identity verification, medical consent, safety checks, and confirmation before irreversible actions can protect people. The institution imposing protective friction bears the burden of identifying the protection claimed, demonstrating that the friction meaningfully provides it, and explaining why a less burdensome method would not provide comparable protection. Institutional convenience, liability avoidance, or cost reduction alone does not prove necessity.

Agency-preserving and agency-extracting friction. The central distinction is whether friction preserves agency by protecting people from a demonstrated risk, or extracts agency by transferring avoidable burden, cost, risk, or control to them.

Accidental friction. Some harm comes from mistakes, neglected maintenance, incompatible components, weak testing, or design that failed to consider real users. Accidental harm remains real even when nobody intended it.

Neglected friction. A system creates neglected friction when responsible institutions know about a recurring burden and continually assign it less importance than the time, dignity, or safety of the people experiencing it.

Exploited friction. A system exploits friction when abandonment benefits the organization. Difficult cancellations, small refunds made costly to pursue, confusing claims, unreachable support, and remedies that demand more effort than their value can convert exhaustion into revenue or reduced workload.

Strategic friction. Exhaustion becomes a tactic when delay, repetition, ambiguity, channel switching, or emotional invalidation systematically causes people to give up. No individual employee needs malicious intent for an institution to preserve a process because attrition improves its internal metrics.

Friction is not the whole standard. A smooth interaction can still manipulate, surveil, coerce, lock in, or conceal consequences. UXR therefore measures friction alongside agency, comprehension, dignity, safety, reversibility, contestability, and remedy.

Time and dignity. Time returned and dignity preserved provide human measures beneath every technical score. A system that saves institutional labor by consuming human lives has not eliminated cost. It has transferred cost to people who usually possess less power to refuse it.

Human Time Dividend. UXR should make time returned visible by estimating how many minutes or hours a person regains in a Blue Zone system compared with a documented, relevant comparison baseline. Depending on the system, the result may be expressed per interaction, day, month, year, or affected population. Reduced time counts as an improvement only when comprehension, accuracy, safety, consent, access, and remedy are preserved or improved. UXR should not describe avoidable burden as normal merely because it is common.

UXR uses human agency as its controlling value. Agency does not mean that a menu contains multiple buttons or that a policy technically permits an appeal. It means that a person can realistically understand available choices, act on them, and influence what happens next.

Comprehension. A person needs information presented in language, timing, and form they can actually use. Information that exists but remains buried, ambiguous, contradictory, or unintelligible does not create meaningful agency.

Meaningful choice. A choice must offer materially different paths. Forced defaults, deceptive consent, artificial urgency, hidden consequences, and options designed to punish refusal can preserve the appearance of choice while removing its substance.

Practical ability to act. A right that requires impossible time, money, expertise, stamina, technology, or emotional endurance may exist on paper while failing in practice. UXR examines the distance between formal access and usable access.

Accessible and supported agency. Agency may be exercised directly or with support. Systems must not treat disability, limited literacy, language barriers, limited access to technology, or reliance on caregivers, translators, advocates, assistive technology, or other chosen support as reasons to reduce a person's choices, dignity, control, or access to remedy.

Proportional effort. Systems may require effort for safety, consent, verification, or deliberation. An organization claiming that friction is necessary bears responsibility for identifying the risk, demonstrating how the friction addresses it, and explaining why a less burdensome path would not provide comparable protection. Organizational convenience, liability management, or cost reduction alone does not establish necessity.

Power asymmetry. UXR evaluates choices within the conditions under which people must make them. A choice is not meaningfully voluntary when refusal threatens essential healthcare, housing, employment, legal status, physical safety, basic services, or another necessity, or when one party can impose consequences the other cannot reasonably resist.

Collective and distributed agency. UXR examines not only whether an individual can exercise agency, but how a system distributes agency, burden, risk, opportunity, and remedy across communities, populations, and generations. Claims of collective benefit do not erase identifiable harms or excuse unnecessary coercion. Individual preference also does not automatically override legitimate protections for other people. UXR evaluates who gains agency, who loses it, whether that distribution is justified, and whether affected people can understand, contest, and influence the system.

Legitimate limits. Agency does not mean entitlement to any desired outcome or freedom from rules that protect other people. A limit can be legitimate when its purpose is transparent, supported by evidence, proportionate to the risk, applied consistently, and open to contest or correction.

Reversibility and contestability. People need reasonable ways to correct mistakes, reverse decisions, challenge consequential outcomes, understand why a decision occurred, and reach someone or something capable of changing it.

Access to one's interaction record. People should be able to obtain and review records of consequential communications and interactions involving them, including available chat transcripts, call recordings or transcripts, notices, decisions, commitments, and transfers. Access should be timely, usable, portable, appropriately secure, and shareable with a chosen caregiver, advocate, regulator, or evaluator. A person should not have to take perfect notes during a stressful interaction merely because the organization controls the authoritative record.

Effective remedy. A complaint channel does not provide agency unless it can produce a meaningful response. Repetition, routing, documentation, and escalation matter only when they lead toward resolution.

Participation. People affected by a system should have a path to contribute evidence and influence reform. UXR converts isolated experiences into shared knowledge so that individuals do not have to confront institutional systems alone.

The agency test. UXR asks whether a system expands, preserves, transfers, constrains, or extracts human agency, and who benefits from that distribution.

Agency is not satisfaction. A person may dislike a fair decision while retaining agency. A person may enjoy a convenient interaction that quietly removes agency. UXR therefore examines structure, power, comprehension, burden, and remedy rather than relying only on whether someone reports feeling satisfied.

Possible future structure. UXR may someday create or own a separate service organization that helps companies, government agencies, and other institutions understand and meet published UXR standards or Blue Zone criteria. This remains a possible future structure, not a current program or commitment.

What payment buys. The service organization may charge for its labor and advice, and revenue from that work may help support UXR. Payment buys assistance only. It buys no authority over UXR, no special access to UXR, and no favorable treatment from UXR.

One-way authority. Governance and decision-making authority may flow from UXR to the service organization, never in reverse. Neither the service organization nor any client, funder, officer, employee, contractor, or partner may direct or influence UXR's mission, governance, evidence, methods, standards, scores, findings, publication decisions, corrections, or appeals.

No privilege. The service organization and its customers receive no nonpublic scoring data, advance notice, private interpretation, voting rights, exceptions, or access unavailable to the public.

The entire rule. UXR defines the standards. The service organization may help institutions meet them. Neither the service organization nor its customers may change what the standards mean or how UXR applies them.

Document status. This document establishes working principles and collects design notes for a future UXR intake system. It does not represent a functioning service, adopted evidence methodology, final technical architecture, or promise that every channel will launch at the same time.

Why intake matters. A reporting system can reproduce the harm it seeks to measure. Fax-only submission, broken web forms, voicemail-only fallback, repeated restarts, inaccessible categories, and channels that cannot accept ordinary evidence transfer the organization's operational failure back onto the person seeking help. UXR intake must itself meet UXR Blue Zone standards.

Primary pathway: empathetic conversational AI. The primary concept is a narrowly trained intake AI that accepts voice or text, lets a person describe what happened in their own words, and then asks focused questions to develop a complete report. It should support multiple languages, accessible interaction, plain language, save-and-resume continuity, and a pace appropriate to the person rather than forcing everyone through the same rigid form.

The AI's role. The intake AI should help organize and clarify, not decide whether the person deserves belief. It must avoid leading questions, distinguish the person's words from its own inference, preserve the original account, identify uncertainty, ask for correction, and let the person review and approve the structured summary before submission.

Alternative intake channels. UXR should consider an adaptive web form, conventional category-based forms, email forwarding, secure file and share-link upload, human-assisted telephone or video intake, live chat, submissions through a chosen caregiver or advocate, accessible paper or mail pathways, and future application programming interfaces or structured bulk submission for trusted public-interest organizations.

Cognitive-load threshold and immediate exit. Intake must watch for signs that the process itself is exhausting, confusing, repetitive, distressing, or unsafe. A person should be able to switch immediately to a simple structured form, pause, or request human assistance without re-entering information, re-uploading evidence, defending the request, or starting over. The system should carry forward the existing narrative, answers, attachments, consent choices, and unresolved questions.

Channel continuity. A person should receive a case identifier, save progress, move between channels without starting over, add evidence later, export their own submission, review what UXR recorded, correct mistakes, understand what happens next, and track status. A failed channel must lead to a functioning alternative rather than a dead end.

Evidence requests. The process should request verifiable support when reasonably available, including forwarded emails, screenshots, photographs, recordings, saved voicemails, chat logs, receipts, notices, system exports, authenticated share links, integrity tokens, timestamps, or direct records supplied by the responsible organization.

Evidence remains under human control. People must understand what they are providing, how it may be used, who may receive it, what will be public, what will be redacted, how long it will be retained, and how to withdraw or restrict material where possible. UXR should collect only what serves a defined purpose.

Reports without documentary proof. A report should not be discarded merely because the person lacks an artifact. UXR may seek corroboration, request records from another source, compare independently submitted accounts, examine public information, or preserve the report as an unresolved signal. Accumulated independent evidence can support pattern detection, but volume does not automatically convert an allegation into fact.

Identity confidence and claim confidence. UXR may need ways to estimate whether submissions originate from distinct people rather than bots, paid campaigns, or duplicate accounts. Those controls must remain separate from evaluating the claim and must not require public identity, forced surveillance, or unnecessary personal data. Protected and anonymous reporting must remain possible where risk justifies it.

Human assistance and escalation. People must have a route out of the AI pathway when disability, distress, complexity, safety, language, technical failure, or personal preference makes human assistance necessary. Immediate danger, urgent medical needs, threats of violence, and other time-sensitive conditions require clear routing beyond ordinary research intake.

Continuity after submission. Intake should not end with a receipt number and silence. The future system should preserve the contributor's connection to the report, support correction and supplementation, provide understandable status information, and connect the person to relevant resolution knowledge where appropriate. The separate development document on contributor continuity defines this intended layer without fixing its final workflow.

Systems not yet defined. UXR is intentionally not yet fixing evidence weights, confidence scales, identity-assurance methods, AI evaluation tests, human-review thresholds, retention periods, moderation rules, integration standards, status taxonomies, or scoring consequences. Those decisions depend on the evidence, severity, participation-integrity, privacy, governance, and domain frameworks now under development.

Next development stage. The next step is to design and test a limited intake prototype using representative scenarios, including stressful narratives, incomplete evidence, conflicting records, accessibility needs, anonymous reporting, channel failure, cognitive overload, requests to switch channels, and attempts to manipulate the system. The pilot should measure both information quality and the human burden created by intake itself.

UXR needs participation from people who recognize that human-made systems can preserve or erode human agency, and who believe those effects should become visible enough to change.

Lived experience. People who have encountered friction, exclusion, coercion, delay, confusion, institutional attrition, or unusually humane design can help UXR identify what conventional metrics fail to see. Lived experience identifies effects, patterns, and questions and may supply important evidence. It does not by itself establish causation, wrongdoing, or a score.

Domain knowledge. Healthcare workers, engineers, designers, public servants, educators, attorneys, accessibility specialists, researchers, business operators, tradespeople, and people from fields not yet represented can help distinguish universal principles from domain-specific realities.

Critical review. UXR does not need agreement disguised as feedback. Strong criticism can reveal undefined terms, unintended incentives, measurement bias, governance weaknesses, excluded populations, and places where UXR could reproduce the institutional behavior it intends to examine.

Suggested revisions. Public documents will include focused review questions and a path to propose revisions. Useful proposals should identify the passage at issue, the change suggested, the problem the change solves, and any experience or evidence supporting it. Institutional credentials, technical vocabulary, and professional presentation are not prerequisites for meaningful contribution.

Mission protection. Participation may inform changes to UXR's language, methods, domains, measurements, operations, and governance. Participation may not redefine UXR so that corporate or institutional agency becomes its controlling purpose. Restoring and expanding human agency remains the constitutional center.

Current participation stage. UXR is not currently recruiting employees, promising formal roles, accepting public incident reports, or representing that a completed institution exists. The immediate invitation is to examine the developing public framework and help make it more complete, accurate, resistant to capture, and useful to human beings.

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.

Existing constitutional boundary. UXR already requires public contribution to be evaluated for substance rather than volume, sponsorship, institutional power, or organized pressure. Participation may inform UXR but may not redefine it around corporate or institutional agency.

Purpose. Future participation systems must remain open to criticism and lived experience while resisting attempts to manufacture consensus, exhaust reviewers, intimidate contributors, conceal sponsorship, or overwhelm evidence-based decision-making.

Threats identified so far. Collected concerns include coordinated brigading, astroturfing, duplicate submissions, automated submissions, paid influence campaigns, lobbying disguised as public feedback, harassment, retaliatory reporting, strategic ambiguity, evidence laundering, identity fabrication, and deliberate exhaustion of limited review capacity.

Priority adversarial tests. Early pilots should specifically test AI-generated mass astroturfing, coordinated queue flooding, repeated paraphrases of one source, synthetic identity networks, and campaigns designed to consume reviewer attention rather than contribute new evidence. Testing should also measure whether defenses incorrectly suppress legitimate collective reporting.

Candidate safeguards. Possible tools include behavioral rate controls, anomaly detection across submission patterns, substance-based clustering, duplicate detection, source and sponsorship disclosure, queue separation, representative sampling, provenance checks, conflict-of-interest rules, transparent moderation, escalation for coordinated manipulation, human review, and appeal. Clustering should organize materially similar evidence, not erase minority accounts or treat shared wording as automatic proof of coordination. These remain candidates, not adopted procedures.

Anti-abuse cannot become exclusion. Safeguards must not privilege professional writing, institutional credentials, conventional evidence access, technical fluency, English proficiency, wealth, public identity, or the ability to survive a burdensome verification process. A system that prevents manipulation by excluding the people most affected would violate UXR's purpose.

Anonymous and protected participation. Some contributors require anonymity or intermediary representation because disclosure could cause retaliation, job loss, deportation risk, medical consequences, family harm, or physical danger. Future integrity systems must evaluate contribution quality without treating public identity as a universal prerequisite.

Substance is not consensus. A large campaign may raise a legitimate issue, and an isolated contributor may identify a serious defect. UXR must examine evidence and reasoning rather than automatically rewarding either popularity or rarity.

Dependencies before adoption. UXR needs real participation volume, threat modeling, privacy design, moderation pilots, appeals design, accessibility testing, and evidence about how proposed controls affect legitimate contributors before adopting a fixed system.

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 needs a way to distinguish minor friction from severe, urgent, widespread, or irreversible harm. The same delay can be inconvenient in one setting and life-threatening in another. A credible framework must preserve those differences without letting institutions minimize harm by assigning it a convenient label.

Candidate severity concepts. Current notes include friction, degradation, deprivation, danger, and catastrophic harm. These are working concepts, not adopted levels. Future work must test whether they remain distinct across healthcare, employment, infrastructure, software, finance, education, government, and other domains.

Candidate modifiers. Relevant dimensions may include scale, duration, frequency, reversibility, recoverability, vulnerability, power disparity, foreseeability, prior notice, ongoing exposure, cumulative burden, distribution across populations, and whether delay compounds the harm.

Recoverability window. Recoverability includes more than whether a loss can eventually be reversed. Future methods should examine how much time remains before prevention, appeal, treatment, replacement, correction, or compensation becomes impossible or materially less effective. A moderate harm with a closing remedy window may demand action before a more severe but stable and fully recoverable condition.

Vulnerability and constrained alternatives. Vulnerability should not operate as an automatic numerical multiplier. UXR must examine the concrete conditions that change exposure and recovery: available alternatives, dependence on the system, disability, financial or legal precarity, retaliation risk, time sensitivity, access to assistance, and the consequences of failure. The method must make unequal effects visible without reducing people to a vulnerability label.

Collective and intergenerational effects. Severity may arise through population-level distribution even when each isolated incident appears small. Future methods must examine community burden, concentrated harm, cumulative exclusion, and effects transferred to future people without allowing an abstract collective benefit to erase identifiable individual harm.

Urgency is not severity alone. A high-severity condition may develop slowly, while a moderate harm may require immediate intervention because a short window for prevention or remedy is closing. UXR must eventually distinguish severity, urgency, likelihood, and recoverability rather than compressing them into one number.

Dependencies before adoption. This methodology requires cross-domain pilot cases, evidence-validation rules, participation from affected populations and domain experts, tests for consistency, and analysis of how institutions could manipulate each threshold. Pilot cases should span materially different conditions, including at least one safety-critical or time-sensitive domain, one high-volume digital or administrative system, and one physical or public-service environment. The purpose is contrast, not compliance with an arbitrary domain count.

Next development stage. The next step is comparative case analysis. UXR should apply candidate dimensions to substantially different situations, document where they fail, and revise them before proposing an adopted scale.

UXR is universal by design. It does not treat user experience as a synonym for software interface design, customer service, or commercial transactions. Those fields belong inside UXR, but none defines its boundary.

The scope rule. If human beings designed, built, maintained, required, regulated, funded, automated, or mediated access through something, UXR may examine how it affects human beings.

Products. This includes light switches, appliances, tools, furniture, automobiles, medical devices, packaging, repair processes, and every physical object whose design affects human action.

Digital systems. This includes websites, applications, operating systems, automated decisions, account systems, artificial intelligence, privacy controls, security processes, and the interfaces through which people encounter them.

Services and institutions. This includes healthcare, insurance, education, employment, banking, retail, utilities, transportation, housing, customer support, government agencies, courts, and regulatory systems.

Infrastructure and spaces. This includes roads, traffic signals, sidewalks, buildings, hospitals, schools, offices, public spaces, signs, environmental controls, and the systems governing how people move through them.

Rules and procedures. This includes taxes, laws, regulations, eligibility rules, application procedures, appeals, consent processes, schedules, queues, and the administrative structures that determine access.

Human-mediated interactions. UXR may examine conduct by any person exercising organizational, governmental, commercial, employment, housing, professional, or other system-derived authority. It does not score ordinary interpersonal disagreements in which neither party exercises power derived from a human-made system.

Equal scrutiny of public and private power. UXR evaluates effects rather than political identity, ownership form, or institutional label. A corporation, government agency, nonprofit, union, school, or person exercising system-derived authority receives the same evidentiary standard.

Domains without fragmentation. UXR will require specialized domains because healthcare, traffic engineering, software, taxation, and product design require different expertise and measurements. Those domains remain parts of one parent project governed by the same commitment to human agency.

Operational sequence. Universal scope does not require simultaneous implementation. UXR will develop domain-specific methods in deliberate stages, prioritizing areas where the stakes, available evidence, and ability to produce responsible findings justify action.

Limits of UXR authority. Examining and publishing findings about a system does not give UXR governmental or coercive power. UXR must earn authority through transparent methods, accurate evidence, fair process, public trust, and the lawful actions of people and institutions that use its findings.

Future systems. The scope intentionally remains open. New technologies and institutions will create forms of interaction that do not yet have names. UXR's scope follows the effect on human beings, not a closed list of industries.