Independent public-interest evaluations of how systems respect dignity and support agency.
HXR Documentation
This packet is a single review surface for the current published HXR Documentation corpus. Read it with HXR’s purpose in view: respecting inherent dignity, strengthening practical agency, and preserving human capacity by learning from good, difficult, and mixed experiences.
What HXR publishes: Evaluations are the main analytical artifacts, supported or challenged by bounded Incident Cases and other evidence. HXR recognizes good practice from the outset, examines where systems create burdens, and explains how effective experiences can benefit both people and organizations. Claims remain limited to the evidence; company benefits are not treated as measured merely because they are plausible.
Automatic assembly: The Complete HXR Reviewer Packet is generated from the current published HXR Documentation articles. Publishing a new documentation article or synchronizing a material edit to an existing published article automatically changes this packet. HXR does not maintain a second manually copied packet.
Synchronization gate: A documentation change is not complete until the canonical structured HXR Document and its linked public article are reconciled. The packet then reflects that public article automatically.
Source rule: Individual canonical HXR Documents and their synchronized public articles remain the source material. This packet is a generated review view, not an independent authority layer.
Current operational context for this review. The documents below accompany public Evaluations supported by bounded Cases and other evidence. Review how HXR recognizes good experiences, examines difficulties, and connects dignity and agency with benefits for people and organizations. The snapshot reflects released records when the packet is viewed.
HXR today · Private Alpha
These counts come from the released public records used by the library. Contributions are handled by people, and public release is reviewed separately.
Counts describe released public records, not how common an experience is or how well an entire organization performs.
These Evaluations recognize useful practices and improvements while preserving the limits of the evidence. Each connects a human benefit with organizational value that can be investigated.
Recognizing useful practice
Value for the person: The City-authored record preserves the request, department, status, date, and response. That continuity can help a resident understand what happened without repeating the story.
Potential value for the organization: Clear records may also reduce duplicate contacts and help staff coordinate. Physical completion, durability, and reliable performance across other requests remain separate questions.
Valuing a good capability within a mixed experience
Value for the person: A contributor values being able to add information to active work. The same experience raises a separate question about talking beside that work without changing it.
Potential value for the organization: Preserving progress may reduce restarts and help people complete useful work with the product. Those organizational benefits are possibilities to test, not measured results.
Preserving credit for an improvement
Value for the person: Adobe documented a change that retains the request to close while a save finishes. It illustrates how software can carry the coordination work for the person.
Potential value for the organization: A dependable workflow may reduce interruption, repeated commands, and support demand. Current-version verification remains open; HXR does not claim credit for Adobe’s historical change.
Document 1
How HXR uses Evaluations, supported by Incident Cases and other evidence, to understand difficult, successful, and mixed experiences—and make better practices visible for people and organizations.
HXR exists to remove the friction people and companies create, so that everyone can achieve more.
Every day, people lose time, money, energy and opportunity to friction that didn't have to exist: support systems built to wear you down, promises nobody keeps, problems acknowledged but never fixed. Most of it is human-made, which means humans can unmake it. HXR documents that friction in public, measures it plainly, and shows how to remove it. Our goal isn't to shame companies. It's to make the cost of friction visible, so that fixing it becomes the obvious choice. When a company fixes what we find, we record it and the score improves. Everyone benefits when friction comes down, the companies included.
Human-made systems shape what people can understand, choose, accomplish, and change. Some make ordinary goals unnecessarily difficult. Others recognize people's dignity, make their choices consequential, and help them use their time and attention well.
HXR studies both. It publishes Evaluations: ongoing, evidence-based analyses of a product, service, organization, workflow, or practice. Each Evaluation can draw on Incident Cases—records of bounded experiences—and other evidence to explain what works well, what causes difficulty, what remains uncertain, and what can be learned or improved.
Think about the difference between repeating your story at every handoff and having it reach the person who can help. Or between receiving a list of options that lead nowhere and making a choice that affects what happens next. HXR examines those differences, including the practices that make good experiences possible.
Better experiences can benefit organizations too. Clear information and effective handoffs can help people achieve their objectives while reducing avoidable repeat contacts and staff rework. HXR distinguishes demonstrated benefits from plausible benefits that still need evidence.
HXR combines observation, explanation, and evaluation to understand how systems affect people's objectives, time, understanding, access, safety, dignified treatment, and practical agency.
Evaluations are the main public analytical records. Incident Cases preserve what happened in bounded occurrences and may support, challenge, narrow, or qualify one or more Evaluations. Other evidence can contribute too. One experience remains one experience even when it informs several analyses; more reports do not automatically establish prevalence or make a conclusion true.
The limited live pilot already publishes Evaluations and Incident Cases. These records make the developing method inspectable against real evidence. They can preserve successful practices, examine failures and mixed performance, and track individual outcomes, verified improvements, and later regressions within the scope the evidence supports.
Formal scoring-method development has begun, but HXR does not yet claim an operational or validated universal score. Its deeper constitutional and methodological rules continue to be developed in public so they can be challenged before future scores, influence, funding, or reputation make them harder to change.
Human dignity is inherent. HXR and the systems it examines do not create it or take it away. They can recognize or disregard it through how people are treated.
The goal is dignified treatment, practical agency, and protected human capacity: people's time, attention, and ability to pursue their goals. Agency means that what a person does has a meaningful possibility of affecting what happens next. It does not guarantee the person's preferred outcome.
Recognizing good practice, documenting harm, sharing useful knowledge, and tracking improvement are ways to pursue those ends. Reform matters when change is needed; a practice that already serves people well also deserves examination, preservation, and appropriate credit. Benefits to an organization can strengthen the case for a good practice, but people's dignity does not depend on a financial return.
Help us test whether these ideas deserve to grow.
HXR applies wherever human-made systems shape what people can understand, choose, do, correct, influence, or recover from. Its scope includes healthcare, insurance, schools, workplaces, products, transportation, public services, laws, courts, physical spaces, digital platforms, and automated systems.
Universal scope is an obligation to remain open, not a claim of complete knowledge.
An experience can matter enough to examine without automatically proving every claim about cause, intent, wrongdoing, or responsibility. HXR separates what happened from explanations for why it happened and from judgments about whether the burden was justified.
If a named organization says the problem is controlled elsewhere, HXR should treat that as a claim to investigate. Responsibility can be corrected or divided as evidence develops. The affected person should not have to map the entire institutional system before their experience can matter.
Silence is ambiguous evidence. Low complaint volume proves neither satisfaction nor resignation by itself.
Time is one powerful metric, but it is not the whole project. HXR also examines practical agency, dignified treatment, understanding, access, safety, opportunity, recovery, and other human consequences where the evidence supports them.
An organization may reduce its own costs by cutting staff, training, coordination, or support. The work does not disappear. Customers, patients, workers, families, or the public may inherit it.
But not every failure saves the institution money. Some broken workflows waste resources on both sides through repeat contacts, transfers, rework, escalation, responsibility disputes, and unresolved outcomes. HXR examines both burden transfer and shared inefficiency without assuming motive that the evidence does not establish.
HXR also examines practices that prevent those costs from arising. An Evaluation can show how a clear choice, a reliable handoff, or a well-designed recovery path helps the person and how it affects the organization providing it. Those effects must be supported separately: an observed human benefit is not automatic proof of lower cost, greater trust, or stronger retention.
Official services may possess authority HXR does not. Use the channel capable of producing an immediate medical, legal, safety, or other time-sensitive outcome first. HXR does not replace those services or guarantee a preferred result. Its limited pilot can preserve experiences and bring evidence into Evaluations so useful findings, organization responses, and supported improvements can be examined over time.
What HXR Adds When the Normal Process Reaches a Dead End explains this application in more detail. The 96-Hour Appointment Loop: DMHC and HXR Compared gives a concrete healthcare example.
Document 2
A welcoming introduction to HXR's Evaluations, the experiences and evidence behind them, and ways to explore successful practice, understand difficulties, or contribute.
Someone thought enough of this project to send you here. Thank you for taking a look.
Human Experience Reform, or HXR, examines every kind of human-made system, not only software, websites, apps, or machine interfaces.
Its scope includes systems of care and support, education and employment, commerce and transportation, government and law, physical environments, digital platforms, and automated decision-making.
HXR publishes Evaluations of how those systems work for people. Supported by Incident Cases and other evidence, an Evaluation can explain a successful practice, a recurring difficulty, or mixed results. The aim is to make dignified treatment, practical agency, and protected human capacity more visible and achievable.
A good experience is worth examining in its own right. HXR looks at what made it work and what people and organizations may learn from it, while keeping each benefit and conclusion within the evidence.
Life does not have to stay harder than it needs to be.
HXR does not treat complaints, praise, scores, visibility, pressure, or reform as the final goal. Those are possible mechanisms or intermediate results. The human end is a system that recognizes people's inherent dignity, treats them accordingly, preserves or restores practical agency, and stops treating human capacity as a cost that does not count.
Universal scope is an obligation to remain open, not a claim of complete knowledge.
You may have found a clear choice, a helpful interaction, a reliable process, or a recovery that preserved your work. You may have encountered a difficult experience, or a system that worked well in one respect and poorly in another. HXR welcomes evidence of all of these outcomes.
You may be the person who spends hours fighting for correction. You may be the person who accepts the first answer because challenging it seems exhausting or pointless. You may not discover that the system failed until much later. You may carry the work for someone else.
Each experience can help HXR examine the system. None must fit an expected pattern of failure to matter.
Recognition is not automatic adjudication. HXR can take an experience seriously while still testing what the evidence establishes about facts, causes, responsibility, benefits, and harm.
A system can waste time without creating anger. It can reduce agency without producing a complaint. It can hide a lost outcome behind ordinary acceptance.
Silence is ambiguous evidence. Low complaint volume does not prove satisfaction, and it does not by itself prove resignation, fear, or burden avoidance.
HXR combines a developing public framework, evidence-based Evaluations, bounded Incident Cases, research, and methods for understanding human experience. It is being built in public, with limited live operations and continuing methodological development.
The purpose is for systems to recognize inherent dignity, enable practical agency, and protect human capacity. Identifying problems, recognizing successful practice, informing decisions, and tracking improvement serve that purpose.
HXR asks what helps or hinders people in pursuing a legitimate objective and what the evidence shows about the consequences for people and organizations:
HXR begins with observation rather than accusation. It asks what happened, what can be measured, what explanation the evidence supports, and what remains uncertain.
This is HXR's core analytical sequence, not its complete future lifecycle.
HXR is scientific in method and ambition, but it is not yet a completed scientific instrument. Its measurements, baselines, weights, and Blue Score methods remain under development and must be tested publicly.
Document 3
HXR’s purpose is dignity recognized in practice, practical agency, and protected human capacity; Evaluations supported by Incident Cases and other evidence identify successful practices and needed improvements, including evidenced benefits to people and organizations.
Human Experience Reform exists to help the systems people use to live, work, learn, travel, receive care, participate in public life, and pursue ordinary goals recognize inherent human dignity, provide dignified treatment, preserve or strengthen practical agency, and protect human capacity. HXR examines successful, difficult, and mixed experiences to identify what should be preserved, shared, or improved.
HXR examines human-made systems of every kind, not only software or machine interfaces.
Human-made systems can support people well, impose avoidable burdens, or do both under different conditions. HXR examines those effects through evidence. It makes supported burdens and benefits visible, explains the practices and constraints behind them, and tracks what changes.
Agency means what you do can matter.
HXR uses human agency to mean the practical capacity of a person's will, choices, evidence, or actions to enter a causal pathway with a meaningful possibility of affecting what happens next. Understanding, choice, action, contestability, correction, recovery, and meaningful alternatives support agency because they preserve a person's ability to participate consequentially in systems that affect them.
Agency is not control, omnipotence, or a guarantee of the preferred outcome. A person can receive a legitimate no and still possess meaningful agency if their evidence, choice, objection, appeal, or action had a real possibility of affecting the process. The central question is not only whether a person was allowed to act, but whether the action could matter.
Human dignity is the inherent worth and standing of a person. It is not granted, earned, purchased, scored, or created by HXR or by any institution. A system recognizes or disregards that dignity through how it treats a person's time, body, objectives, limits, evidence, voice, privacy, and standing.
Dignified treatment is conduct and system behavior consistent with that inherent dignity. Respect is the behavioral recognition of dignity; it does not require admiration, agreement, approval, or surrender of legitimate constraints.
HXR does not exist merely to collect complaints, publish praise, generate scores, expose failures, pressure institutions, or produce reform. Evidence, visibility, aggregation, comparison, accountability, institutional response, and lawful external leverage are mechanisms. Reform is an intermediate system result. The ultimate purpose is better human experience: dignity recognized in practice, practical agency preserved or restored, and human capacity no longer treated as a disposable externality.
HXR should give evidence of successful practice the same disciplined attention as evidence of harm or failure. A good experience does not need a preceding complaint, an institutional mistake, or a reform to deserve examination.
Evaluations are the continuing analytical records. Bounded Incident Cases and other evidence can support, narrow, challenge, or contradict their findings. This structure should preserve favorable, unfavorable, and mixed performance without making report count a substitute for truth.
A practice may benefit people and the organization providing it. HXR should identify and distinguish those effects where evidence permits, helping others understand what may be worth adopting. Dignity remains inherent, and dignified treatment does not require proof of commercial benefit.
Reality imposes constraints that human beings cannot repeal. Human-made laws, policies, workflows, technologies, contracts, institutions, and conventions are different. They may impose legitimate limits, but they remain eligible for evidence, explanation, reconsideration, correction, and reform through legitimate human processes.
HXR therefore distinguishes genuine constraint from contingency. “We cannot” may describe physics, safety, law, another person's rights, current technology, architecture, cost, policy, risk tolerance, or an organizational choice. Those sources are not equivalent. When a burden is defended as necessary, HXR should ask what actually creates the constraint and whether a less burdensome path is reasonably available.
HXR does not begin by assuming malicious intent, and it does not treat moral outrage as a substitute for evidence.
It separates three stages:
HXR is scientific in method and ambition. It is not yet a completed scientific instrument. Its operational measurements, scoring methods, baselines, and weighting rules remain under development and must withstand public testing.
Institutions often possess greater information, continuity, staffing, automation, legal resources, authority, and consequential power than the individuals who depend on them. Greater capability creates greater responsibility to carry work the institution is better equipped to perform, including coordination, recordkeeping, explanation, correction, and responsibility routing.
A supported harmful or burdensome condition can be recognized without first proving malicious intent. Intent matters to culpability. It does not determine whether the condition exists, whether responsibility exists, or whether reform should be investigated.
People should not have to reverse-engineer the institutional architecture surrounding an ordinary objective in order to locate someone capable of correcting a failure. When responsibility crosses organizational boundaries, HXR should trace distinct responsibilities wherever the evidence leads rather than forcing the affected person to resolve the institutional map alone.
HXR applies wherever human-made systems shape people's choices, obligations, access, safety, time, understanding, ability to affect what happens next, or ability to recover from mistakes.
HXR findings do not automatically prescribe one political, regulatory, market, legal, organizational, or revolutionary response. They identify supported conditions, costs, responsibilities, constraints, and corrective possibilities.
Where comparison is appropriate, HXR should use transparent evidence, public definitions, the strongest applicable measurement discipline, explicit uncertainty, and defensible comparability rules. A comparison is contestable, not consent-dependent. An institution may correct facts, challenge methods or inference, explain constraints, provide counterevidence, justify an existing condition, or document reform. It does not receive a right to approve the measurement or suppress a supportable comparison.
HXR is currently building its constitutional, scientific, ethical, governance, and methodological foundation in public before broad operational authority is created.
HXR is not exempt from the responsibility rule it applies to others. As its demonstrated capability and consequential influence grow, its own duties of accuracy, corrigibility, transparency, stewardship, and response must grow with them.
What HXR Means by Human Agency · Responsibility, Capability, and Institutional Asymmetry · How HXR Creates Accountability
Document 4
Defines practical agency as consequential participation, distinguishes it from control, separates inherent dignity from treatment and respect, and explains how Evaluations can preserve evidence of agency-supporting practice.
Agency means what you do can matter.
HXR uses human agency to mean the practical capacity of a person's will, choices, evidence, or actions to enter a causal pathway with a meaningful possibility of affecting what happens next.
Understanding, choice, action, contestability, correction, recovery, and meaningful alternatives matter because they support that causal capacity. They are not sufficient by themselves. A system can provide choices, buttons, complaint forms, appeals, and explanations while making every resulting action causally irrelevant.
Agency does not mean that a person's will must prevail. It does not override physical reality, safety, law, the rights or agency of other people, or every legitimate institutional constraint. A person can lose an appeal, receive a well-supported denial, or choose an option that does not produce the result they wanted and still possess meaningful agency.
The defining question is not only “Were you allowed to act?” It is “Could your action matter?”
Formal agency exists when a system says a person may choose, appeal, opt out, change providers, request help, submit evidence, complain, or seek review.
Practical agency requires a credible path by which the person can understand and use that opportunity under real conditions and by which exercising it can have consequential effect.
A complaint channel that can receive words but cannot produce learning, reconsideration, correction, escalation, or another relevant consequence can simulate agency without providing much practical agency.
Acceptance does not prove satisfaction, informed choice, or lack of harm.
Agency does not require giving every person unrestricted control over every institutional decision. In many systems, an institution legitimately retains authority because of law, professional judgment, safety, contract structure, technical architecture, or coordinated administration.
The relevant agency question is then whether the person can effectively invoke the rights, choices, protections, and remediation mechanisms that properly belong to them and whether that invocation can reliably reach the institutional function that controls the required next action.
A patient does not need to become the health plan, authorize their own referral, or personally administer a provider network. A bank customer does not need direct access to settlement infrastructure. A traveler does not need airline dispatch authority. But when an institution reserves the consequential lever to itself, the person needs a practical way to cause the responsible institution to evaluate and use that lever when the ordinary pathway fails.
The more consequential authority a system reserves to itself, the more important an effective mechanism becomes for invoking that authority when the normal pathway fails.
A system can keep a person extremely busy while leaving them with little ability to affect the outcome. Calling, waiting, appealing, researching, complaining, resubmitting, and asking another participant are actions, but they are not evidence of practical agency merely because the user performed them.
HXR should distinguish user-performable procedural actions from institution-controlled outcome actions. The evaluation is not whether the user personally possessed every institutional power. It is whether reasonable user action could activate the responsible institutional process and produce a consequential response.
This distinction prevents HXR from mistaking a long menu of requests for meaningful agency and prevents the opposite error of treating legitimate institutional control as a failure simply because the user could not bypass it.
A remedy can exist formally while remaining difficult to reach in practice. A policy, appeal right, qualifying-event rule, complaint form, help article, or grievance pathway does not by itself establish practical agency.
HXR asks whether a person can describe the underlying problem in ordinary language and be connected to the process capable of evaluating or correcting it. An organization may technically communicate accurate information while still leaving the person to discover the relevant classification, jurisdiction, exception, or procedural trigger alone.
This creates an important distinction:
A link can be useful. A link is not automatically a remedy.
Continued participation does not necessarily demonstrate satisfaction or free choice. A slow, fragmented, or partially completed process can create switching costs that make exit feel progressively more dangerous or wasteful.
The person may have accumulated waiting time, established relationships, pending approvals, partially completed work, stored data, diagnostic momentum, financial sunk costs, or other dependencies that would be threatened by leaving. In those conditions, retention may reflect continuity lock-in rather than approval of the experience.
HXR should therefore examine whether the system's own performance increased the cost of exit and avoid treating continued participation as evidence that meaningful alternatives were available.
A system can make choices understandable, preserve context across a handoff, let new evidence affect a decision, carry out a person's intended action reliably, or provide a usable way to correct a mistake. These are practices worth examining even when no complaint or reform preceded them.
HXR asks what made the person's participation consequential, who could use the pathway, and where its limits lie. An Evaluation can preserve the evidence of that practice and examine whether it also helps the organization—for example, by reducing repeated explanation or avoidable rework. Those organizational effects require their own support.
Systems can teach people that participation is futile without intending to do so. A person forms an objective, acts, receives no consequential response, tries again, and gradually learns that further effort is unlikely to matter. The eventual silence may reflect learned nonparticipation rather than satisfaction.
HXR should not answer that condition with motivational language alone. It should help create credible grounds for participation by preserving evidence, maintaining continuity, showing what happened next, and making consequential pathways more visible.
Physics can impose limits that human will cannot change. Human-made systems are different. Laws, policies, workflows, technologies, organizational boundaries, contracts, and conventions may impose legitimate constraints, but they remain human-created arrangements subject to evidence, reconsideration, and reform through legitimate processes.
HXR therefore treats corrigibility as an important property of humane systems: people affected by a system should have meaningful ways for evidence, error reports, objections, and demonstrated better methods to reach the parts of the system capable of learning or changing.
A person should not have to understand the institutional architecture surrounding an ordinary objective in order to locate someone capable of correcting a failure. If a doctor's office, medical group, health plan, network, vendor, carrier, platform, regulator, or other participant says the failure belongs elsewhere, that attribution should become a claim that can be tested rather than an instruction for the person to start over.
Different responsibilities may belong to different parties. One entity may control the mechanism, another the policy, another the handoff, another the remedy, and another the governing rule. Correctly locating one responsibility does not erase other responsibilities for disclosure, coordination, or recovery.
HXR cannot promise that a contributor’s preferred result will occur. It can build infrastructure so human effort does not simply disappear.
An experience can be preserved as a bounded Incident Case and contribute, alongside other evidence, to an ongoing Evaluation. Evidence can remain visible, different experiences can challenge a conclusion, organization responses can enter the record, and responsibility or credit can change as the evidence develops. Successful practice can be documented and shared; needed improvements can be proposed, tested, and monitored.
HXR should help a person's contribution enter a credible path toward understanding, learning, correction, or preservation of something that works. The aim is more consequential participation and better human experience, including when no reform is needed.
Institutions usually hold capabilities individuals do not: persistent records, specialized expertise, automation, formal authority, financial resources, time, legal support, and the power to redesign the system itself.
HXR does not assume that one reform can create equal footing. It asks whether avoidable asymmetry can be reduced and whether responsibilities are carried by the side better equipped to perform them.
Agency and dignity overlap but are not identical. Human dignity is the inherent worth and standing of a person. It is not granted, earned, purchased, or removed by a system. Dignified treatment recognizes that dignity by treating the person's time, body, objectives, limits, evidence, voice, privacy, and standing as mattering. Respect is the behavioral recognition of dignity; it does not require admiration, agreement, approval, or the person's preferred outcome.
Agency asks whether the person's voice, choice, evidence, or action can participate meaningfully in what happens next. A system may acknowledge a person's dignity while leaving their action causally irrelevant, or provide a formally consequential choice through a process that remains degrading or dismissive. HXR should examine both.
HXR does not claim that agency can already be reduced to one validated number. It can still study observable indicators: Were choices understandable? Were alternatives realistic? Could consent be informed and withdrawn? Could evidence change a decision? Did appeals produce real review? Could a person locate corrective authority? Did a handoff preserve context? Did anticipated burden suppress pursuit? Did the system learn from repeated reports? Did verified reform make future action more consequential?
Document 5
UXR may examine and compare every kind of human-made system, from products and companies to cities, schools, insurance plans, laws, prisons, and automated gatekeepers.
Status: Open for Review Version: 0.6
HXR is not limited to software, websites, apps, or machine interfaces.
HXR may examine every human interaction with products, services, spaces, infrastructure, rules, institutions, and other systems human beings create or maintain.
The scope rule. If human beings shaped a system or a person's access to it, HXR may examine how that system affects people. Human involvement may include design, construction, maintenance, regulation, funding, automation, or mediation.
Many systems combine several forms at once. A healthcare referral may involve medical judgment, insurance rules, software, telephone support, records, regulation, and organizational incentives.
Healthcare, traffic engineering, software, taxation, education, incarceration, and product design require different expertise and measurements. Those domains remain parts of one parent project governed by the same commitment to human agency, evidence, proportionality, and reform.
Universal scope does not require simultaneous implementation. HXR will develop domain-specific methods in deliberate stages, prioritizing areas where the stakes, available evidence, and ability to produce responsible findings justify action.
Burden transfer and human externalities exist even where no money changes hands. Commercial and noncommercial systems alike can move work downstream.
Public agencies, nonprofits, communal systems, militaries, and post-scarcity systems can transfer delay, coordination, repeated work, confusion, risk, or attention onto the people who depend on them.
Document 6
Status: Open for Review Version: 0.6
Summary: Human-made systems impose costs that may be recognized, normalized, anticipated, avoided, hidden, or defended as unavoidable.
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, delayed care, lost opportunity, or reduced practical agency. 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.
Necessary friction. Not every obstacle is harmful. Identity verification, consent, safety checks, and confirmation before irreversible actions can protect people. The institution imposing protective friction bears responsibility for showing what it protects, how it works, and why a less burdensome path would not provide comparable protection.
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.
When a system says a burden “cannot” be removed, UXR should ask what actually creates the constraint. The answer may be physical reality, safety, the rights of other people, law, current technology, architecture, a contract, policy, risk tolerance, cost or resource allocation, organizational priority, or inherited practice.
Those sources are not equivalent. A physical constraint may be outside human control. A legal rule may bind a front-line organization while remaining reformable through a legislative or regulatory process. A software limitation may describe the current implementation rather than an immutable fact. A cost decision or policy may be a choice that deserves to be described as a choice.
Human-made contingency should not be presented as natural inevitability merely because it is durable, familiar, or difficult to change.
People do not need to describe an experience as friction for the system to constrain them.
Some people challenge a result and spend hours seeking correction. Others accept the first answer because experience has taught them that asking for more will require conflict, delay, uncertainty, or effort they cannot afford. The visible fight disappears, but the lost outcome remains.
A system may appear frictionless because people have learned not to ask it for outcomes they expect will be difficult to obtain.
UXR therefore examines more than complaints. It also examines:
Acceptance does not prove satisfaction, informed choice, or lack of harm. Low complaint volume does not prove low burden.
A person may encounter an underlying failure and then be required to discover which department, company, medical group, insurer, carrier, vendor, regulator, or other system participant can correct it. Calls, transfers, repeated explanations, record reconstruction, and responsibility mapping consume human capacity even when every participant accurately describes its own local boundary.
UXR should therefore distinguish the original failure from any additional burden created by responsibility opacity or poor handoffs. Institutions may legitimately transfer corrective work to another responsible party without automatically transferring the navigation burden to the affected person.
A burden that appears trivial in one interaction may become enormous when multiplied across repeated use, large populations, and long periods. UXR therefore examines both the individual cost and the cumulative human cost.
An average of one avoidable minute per person per day does not mean every person loses exactly one minute every day. One person may lose nothing for weeks while another loses several hours in a single failed interaction. The average communicates scale; the distribution shows who actually pays.
Every unnecessary minute spent waiting, repeating, navigating, correcting, traveling, recovering, or learning an avoidable exception is a minute unavailable for rest, care, work, creation, relationships, participation, or choice. Institutions should not treat human time as an inexhaustible input.
People often stop noticing burdens after adapting to them. Habit may reduce conscious irritation while leaving the time, attention, physical effort, lost opportunity, delayed care, or abandoned objective intact. Common does not mean necessary.
System burden often accumulates through small recurring losses: one more form, one more transfer, one more verification step, one poorly timed traffic signal, one queue that always runs late, one correction path that requires starting over.
Each cut may appear dismissible. Together they can consume years of human life and produce larger cascades involving money, health, safety, infrastructure, environment, dignity, opportunity, and agency.
Accidental, neglected, exploited, and strategic friction. UXR may distinguish errors and weak design from known recurring burdens, conditions that create institutional benefit, and systems in which evidence supports deliberate use of delay, repetition, ambiguity, channel switching, or exhaustion to produce abandonment. Institutional benefit alone does not prove strategic intent; motive and knowledge require their own evidence.
Human Time Dividend. UXR should make time returned visible by estimating how many minutes or hours people regain compared with a documented, relevant baseline. Any estimate must show the population, period, assumptions, distribution, and uncertainty. Reduced time counts as improvement only when comprehension, accuracy, safety, consent, access, remedy, and meaningful agency remain preserved or improve.
When an institution says a burden cannot be removed, what evidence should UXR require to distinguish physical or protective necessity from law, architecture, policy, cost, convention, or another human-made constraint?
Document 7
Status: Development Notes — Published for Review
Responsibility should scale with capability and consequential power.
Institutions commonly possess capabilities that individuals do not: persistent records, operational continuity, staffing, automation, specialized expertise, legal resources, money, formal authority, and the power to redesign or govern systems that affect human lives.
That asymmetry does not make an institution malicious. It does create responsibilities that an individual may be unable to carry safely, efficiently, or at all.
UXR should first establish what the evidence supports about the condition. A harmful or burdensome condition does not automatically prove malice, negligence, exploitation, indifference, or any other motive or mental state.
Intent matters to culpability. It does not determine whether a supported condition exists, whether corrective responsibility exists, or whether reform should be investigated.
An affected person should not have to diagnose the moral or psychological state of an institution before the condition can be taken seriously. UXR can recognize the condition, investigate necessity and cause, identify relevant responsibilities, and pursue correction while keeping motive unresolved when the evidence does not establish it.
The side better equipped to perform coordination, recordkeeping, explanation, correction, risk management, continuity, or responsibility routing should carry proportionally more of that burden.
An institution should not require a person to reconstruct records the institution already holds, coordinate departments the institution controls, repeatedly prove facts the institution already verified, or reverse-engineer a multi-party system merely to find the entity capable of acting.
Some institutions exercise substantial consequential power over human lives through access, authorization, infrastructure, payment, employment, housing, care, mobility, enforcement, communication, or remedy. The greater that capability, the stronger the stewardship responsibility to understand the human consequences of the system and maintain credible ways for affected people and evidence to reach corrective authority.
“Nobody told us” may explain a lack of awareness. It does not by itself answer whether the institution maintained effective mechanisms through which people could tell it.
“Who is responsible?” can be too simple for a multi-party system. UXR may need to distinguish several responsibilities:
These responsibilities may belong to different parties. Correct attribution of one responsibility does not absolve every other participant from every role.
When an organization named in a case says that the relevant failure is controlled elsewhere, UXR should not automatically accept or reject the statement. It should treat the statement as a testable attribution claim.
A useful denial of responsibility should identify, to the extent reasonably known, what the organization controls, what it does not control, who it believes controls the disputed mechanism, why it believes that, what evidence supports the attribution, and what usable path reaches that party.
If the evidence supports reattribution, UXR should correct the case. Accurate reattribution can remove unsupported blame from the initially named organization while preserving any separate responsibility it had for disclosure, coordination, handoff quality, or remedy.
If two institutions point to each other, the conflict is not a reason to abandon the case. It becomes conflicting causal evidence to investigate. If responsibility remains unresolved after reasonable inquiry, UXR should say so rather than manufacture certainty.
A person may encounter one underlying failure and then a second failure: no reliable way to determine who owns correction. The resulting calls, transfers, repeated explanations, record reconstruction, jurisdiction discovery, and responsibility mapping are human burdens even when every participant accurately describes its own limited authority.
Institutions may transfer internal responsibility without transferring the navigation burden. Where practical and lawful, a humane handoff should preserve context, explain the dependency, identify the next responsible party, and move the issue toward the place capable of resolving it rather than forcing the person to restart.
Fragmented responsibility can create an asymmetric institutional advantage because the affected individual bears the cost of determining ownership while each participating institution can limit its involvement to a local boundary. That structural effect can exist regardless of whether any participant intended to create or exploit it.
At scale, UXR can reduce that asymmetry by allowing substantially matching experiences to contribute to one bounded evidentiary record while UXR investigates the responsibility chain. Many affected people should not each have to become amateur investigators of the same institutional architecture.
When a burden is defended with “we cannot,” UXR should ask what produces the constraint. Possible sources include physical reality, safety, the rights of others, law, current technology, architecture, contracts, policy, risk tolerance, cost or resource allocation, organizational priority, or inherited practice. These sources do not carry the same reform path.
A constraint imposed by one layer may be genuine for a front-line actor while remaining corrigible at a governing layer. UXR should trace the constraint to the level at which human decision can meaningfully affect it.
A surgeon's hour may be harder to replace operationally than another worker's hour. That does not make the surgeon a more valuable human being. UXR may account for scarce expertise, opportunity cost, and system risk without ranking inherent human worth.
How should UXR distinguish mechanism, control, policy, coordination, disclosure, remedy, and governance responsibilities without making the responsibility map itself another burden for the affected person?
Document 8
UXR creates accountability by making human costs, system performance, and corrective responsibility visible enough to evaluate.
UXR separates observation, explanation, and evaluation. A harmful outcome does not automatically prove malicious intent. A moral concern does not automatically establish a factual claim. A strong factual claim does not automatically determine the only acceptable remedy.
Responsibility should scale with capability. UXR should trace which responsibilities belong where rather than stopping at the organization first named by a contributor. A claim that responsibility lies elsewhere is evidence to investigate, not an automatic escape hatch.
An institution should not require an individual to reconstruct records the institution already possesses, coordinate departments it controls, or locate corrective authority the institution is better equipped to identify.
A supportable public comparison should be contestable through facts, methods, confounders, constraints, attribution, counterevidence, and demonstrated reform. It is not consent-dependent and does not give measured institutions a right of approval.
Organizations should be able to respond with evidence, explain legitimate constraints, identify errors, propose reform, and demonstrate improvement. Those rights strengthen the record without turning disagreement into a veto.
Accountability is not punishment for its own sake. A useful record should show what happened, what the evidence supports, what response occurred, what reform was proposed or implemented, how it was tested, and what remains unresolved.
UXR should not force organizations to choose between denying a case and accepting a permanent stain. Cases are living evidence records. The durable record preserves the starting condition, the evidence, the response, what changed, how the change was verified, and whether the improvement endured.
An adverse case can become positive organizational evidence when reform is real. The credit comes from demonstrated improvement in human agency, not from deleting the original case, negotiating the finding, or issuing a promise.
The original failure remains part of the record because it explains what was learned and what changed. Later regression also remains visible. If another system later demonstrates a stronger implementation, the benchmark may advance without erasing the improvement already achieved.
An organization may show that an apparent burden follows from a genuine physical, safety, legal, rights-based, technical, contractual, or other necessary constraint. UXR should be capable of documenting that fairly.
But “that is how it works” cannot end the inquiry by itself. The reader should be able to see the constraint's provenance, protected purpose, evidence, proportionality, burden distribution, alternatives considered, and available corrective paths. If the explanation survives scrutiny, the case can document that. If it does not, reform remains the path to stronger evidence and better performance.
When an organization demonstrates a better way to preserve human agency, the case can become evidence that other organizations and systems should examine. UXR should distinguish improvement credit, current performance, and the best demonstrated benchmark rather than collapsing them into one permanent grade.
If counterevidence shows that UXR is wrong, UXR should correct the finding. If evidence shows that an organization improved, UXR should record the improvement with the same seriousness used to document failure.
UXR is not exempt from its own standards. Its methods, authority, funding boundaries, scoring logic, correction procedures, comparison architecture, and effects on contributors and institutions must remain open to evaluation.
Document 9
Status: Open for Review Version: 0.4
Summary: A future UXR service organization may help institutions meet UXR standards, but it and its clients may never influence what UXR is, measures, scores, decides, or publishes.
The rule governs authority, not revenue flow. A downstream service organization may financially support UXR. It may never purchase control, access, interpretation, exceptions, suppression, or favorable treatment.
Possible future structure. UXR may someday create or own a separate service organization that helps companies, government agencies, schools, healthcare systems, cities, 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 analysis, training, redesign, implementation support, and other labor that helps an institution improve the experience it actually provides. Revenue from that work may potentially help support UXR. Payment buys assistance only. It buys no authority over UXR, no special access to UXR, no guaranteed result, and no favorable treatment from UXR.
The plain rule. Companies cannot buy a better UXR score. They may pay qualified people to help them build a better experience.
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 hidden test and no private scoring advantage. The standards an institution is trying to meet must be public. The service organization and its customers receive no nonpublic scoring data, advance notice, private interpretation, voting rights, exceptions, or access unavailable to the public. Expertise may help an institution apply the published target, but it may not reveal a different target.
No suppression or score negotiation. Paid work may not delay publication, suppress a case, alter evidence, negotiate a score, weaken a standard, or convert promised improvement into credit before the improvement is verified.
The entire rule. UXR defines and independently applies the standards. A separate service organization may help institutions meet them and may potentially return revenue to support UXR. Neither the service organization nor its customers may change what the standards mean, what evidence UXR considers, or how UXR applies them.
Does this language distinguish financial support from purchased authority clearly enough?
Document 10
Status: Development Notes, Published for Review
UXR is also a developing scientific framework.
That statement describes a method and a commitment. It does not claim that UXR already possesses validated measures, settled baselines, completed scoring weights, or a mature operational evidence corpus.
UXR studies interactions between human beings and human-made systems of every kind. Those systems may be:
Universal scope is an obligation to remain open, not a claim that UXR already possesses complete knowledge or one method suitable for every domain.
This is the core analytical sequence, not the complete UXR lifecycle.
A future operational lifecycle may include:
Receive → Preserve → Observe → Explain → Evaluate → Respond → Reform → Verify → Learn
Lived experience can identify effects, patterns, and questions. It does not automatically prove every factual, causal, legal, or moral claim.
Recognition is not automatic adjudication. UXR can recognize an account as eligible for examination without accepting every interpretation attached to it.
Silence is also ambiguous. Low complaint volume proves neither satisfaction nor resignation without further evidence.
Likewise, a measurable burden does not automatically prove malicious intent. A strong causal finding does not automatically determine the only lawful or ethical remedy.
Potential measures include:
Some dimensions, including dignity and agency, may require observable indicators, structured qualitative evidence, and multi-dimensional assessment rather than one direct number.
UXR currently has quantitative principles, not a validated quantitative instrument. It can define responsible measurement requirements and illustrate population-scale consequences. It does not yet possess a universal formula, settled weighting model, or accepted method for converting every burden into a common unit.
Future uncertainty reporting may require ranges, quantiles, lower-bound estimates, sensitivity analysis, uncertainty bands, confidence categories, intervals, or other methods appropriate to the evidence. UXR should not require one statistical display before the data and model justify it.
Future methods should distinguish four layers:
UXR should never call a result mathematically undeniable merely because it uses numbers. Quantification can conceal assumptions as easily as it can reveal patterns.
UXR must publish uncertainty, limitations, version changes, correction paths, and failures in its own methods.
Which scientific disciplines, research methods, measurement standards, and validation tests must UXR examine before moving from development notes to operational methodology?
Document 11
UXR uses a growing vocabulary to describe how human-made systems affect time, effort, attention, dignity, agency, safety, opportunity, and recovery.
You do not need to learn this taxonomy before using or understanding UXR. It is a reference system, not an entrance exam.
Any product, service, institution, process, rule, space, infrastructure, technology, or organized practice designed, maintained, required, funded, regulated, or mediated by human beings.
The stage that identifies the person's objective, the sequence of events, the conditions, the measurable or supportable costs, and the outcome without yet claiming a complete cause or moral judgment.
The stage that tests which mechanisms, incentives, policies, decisions, or system components contributed and distinguishes supported inference from uncertainty.
The stage that considers necessity, proportionality, distribution, comprehensibility, contestability, responsibility, and remedy after the evidence boundary has been established.
The combined information, continuity, authority, staffing, automation, expertise, legal resources, financial resources, and redesign capacity available to an institution.
The developing principle that the side better equipped to carry coordination, recordkeeping, explanation, correction, or risk should carry proportionally more of that burden.
A difference in information, records, continuity, authority, expertise, resources, time, or power between an institution and the people who depend on it.
The real ability to understand and use a choice, right, appeal, or remedy under actual conditions.
The work, delay, conflict, uncertainty, or emotional expenditure a person expects would be required to challenge the offered outcome.
Choosing not to pursue a better outcome because the correction or escalation path appears too costly.
Accepting the first available answer after experience has taught the person that challenge is unlikely to justify its cost.
The loss of an outcome that a person wanted or reasonably should have received but stopped pursuing before creating a visible dispute.
A measurable or supportable cost imposed on people, including time, effort, attention, money, dignity, agency, safety, health, or lost opportunity.
A human cost created by a system but excluded from the institution's own accounting, performance metrics, or decision model. Human externalities can exist without money or profit.
The movement of work, complexity, delay, risk, coordination, confusion, or cost from an institution onto the people who use or depend on it.
Burden transfer in which an institution gains while imposing avoidable, disproportionate, uncompensated costs on people who lack meaningful choice or remedy.
A change that reduces work or cost for both the institution and the person rather than merely moving the burden downstream.
A system failure that consumes resources on both sides without producing the intended outcome.
All time spent by the person and institution until the objective is completed or abandoned.
Additional interactions caused by failure to resolve the original objective.
The proportion of interactions that produce a usable, durable result.
The total burden divided across a relevant population and time period. It does not imply equal burden for each person or day.
How a total cost actually falls across different people, including concentration among groups with fewer alternatives or greater exposure.
A primary system failure that produces secondary and downstream costs across time, money, health, safety, infrastructure, environment, attention, or opportunity.
The estimated time returned when a verified reform removes avoidable burden while preserving or improving comprehension, accuracy, safety, consent, access, and remedy. Any estimate should disclose population, period, assumptions, distribution, uncertainty, and baseline.
A development method that examines how different professional, moral, cognitive, cultural, historical, and fictional lenses understand, misclassify, simplify, resist, or over-amplify UXR.
A conclusion that accurately reflects the framework as written.
A new metaphor, explanation, or translation that clarifies an existing UXR idea without changing the framework.
A mistaken interpretation that a careful reader could plausibly reach from the current documentation.
Language or structure that reasonably supports more than one meaning and may require revision.
A conclusion produced mainly by the reviewer's prior worldview rather than by UXR's documentation.
A genuinely new concept or method suggested by a review that UXR has not yet adopted.
Document 12
A reserved methodology layer for distinguishing inconvenience, degradation, deprivation, danger, catastrophic harm, urgency, scale, duration, and reversibility.
Status: Development Notes: Intentionally Deferred Version: 0.2
Summary: A reserved methodology layer for distinguishing inconvenience, degradation, deprivation, danger, catastrophic harm, urgency, scale, duration, and reversibility.
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.
Which dimensions must a future severity framework preserve, and what evidence should UXR require before adopting thresholds?
Document 13
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 durable public knowledge. That requires published methods for identifying where each proposition came from, what supports it, what conflicts with it, and what conclusions the evidence can sustain without treating contributor testimony as presumptively inferior.
Testimony is evidence. A contributor's account is part of the evidence record. UXR should record it plainly and accurately. Documentary support can strengthen, corroborate, refine, or contradict a proposition, but the absence of an artifact does not by itself make the contributor's account suspect.
Provenance without credibility discount. UXR should identify how a proposition entered the record without surrounding testimony with language that rhetorically weakens it. “The contributor reports…” is a provenance statement. If a screenshot, forwarded email, transcript, recording, system record, or other artifact supports the proposition, UXR should say so affirmatively. Terms such as “unverified,” “awaiting verification,” or repeated caveats should be reserved for situations where a real evidentiary issue makes that distinction material, such as conflicting evidence, disputed wording, or a conclusion whose precision depends on the artifact. Evidence provenance should add information, not subtract dignity.
Separate judgments. Evidence provenance, identity confidence, claim credibility, factual accuracy, causal inference, severity, and confidence in a final finding are different judgments. Identifying a statement as contributor testimony says where it came from; it does not itself lower its credibility. An authenticated record can prove where a statement came from without proving every implication drawn from it, and testimony can accurately describe an experience even when no artifact exists.
Direct artifact support and pattern corroboration. A directly inspectable artifact may support or verify a message, transaction, interface state, or interaction, subject to authentication and context. Pattern corroboration asks whether sufficiently independent accounts describe materially similar system behavior. These are different evidentiary routes. Artifact support should be described as added support, not as the point at which a contributor's account first becomes worthy of consideration.
Three record layers. UXR should distinguish the contributor's original account, the internal evidentiary working record, and the public case. The original account should be preserved faithfully. The internal working record should preserve provenance, supplements, corrections, superseded details, material conflicts, and the reasoning used to update the case. The public case should present the strongest current evidentiary account rather than reproduce the entire history of how UXR learned it.
Current-best-evidence public record. When later evidence establishes a more accurate wording, date, time, amount, sequence, or other fact, UXR should update the public case to the better-supported fact and remove the superseded detail when the earlier version no longer helps readers understand the case. The public case should read as though the case manager had all current evidence available when writing it from scratch. New evidence may strengthen, weaken, narrow, or otherwise change the analysis; the public case should change with it.
Superseded details and contributor dignity. Ordinary differences between recollection and later artifacts should not become public credibility events. UXR may preserve the superseded detail privately for provenance and auditability without publishing a narrative that calls out the contributor for having remembered wording, timing, or another detail imperfectly. Accuracy should improve without imposing a reputational tax for ordinary human recollection.
Material discrepancies. A discrepancy should become part of the public case when the discrepancy itself materially affects the case, such as when competing accounts remain unresolved, evidence conflicts in a way that changes the finding, the discrepancy bears directly on causation or responsibility, or understanding the conflict is necessary for a fair public conclusion. The purpose is to disclose relevant evidentiary conflict, not to display every refinement in the contributor's account.
Candidate evidence sources. Future methods may evaluate contributor testimony, 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 and useful. 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. The record should state provenance plainly rather than adding suspicion merely because an artifact is absent.
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. When evidence genuinely conflicts, UXR should describe the conflict directly rather than disguising it as generalized suspicion toward the contributor.
Human-readable inference trail. Any future confidence score or public finding should show, in understandable language, which evidence supports which proposition, what genuinely 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, but it also requires restraint: uncertainty language should identify actual uncertainty, not function as a ritual disclaimer attached to testimony.
Casework as a methodology stress test. Real casework should test whether UXR can document harm accurately, fairly, and usefully. When a bounded case exposes a weakness in evidence language, correction handling, publication practice, responsibility routing, privacy, or another UXR method, that discovery should be treated as operational learning and, when durable, recorded as a methodological development. Case-driven refinement is evidence of a maturing method; it is not by itself scientific validation of that method.
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.
Document 14
A reserved governance and operations layer for resisting astroturfing, brigading, duplication, harassment, lobbying pressure, and review-capacity exhaustion.
Status: Development Notes: Intentionally Deferred Version: 0.2
Summary: A reserved governance and operations layer for resisting astroturfing, brigading, duplication, harassment, lobbying pressure, and review-capacity exhaustion.
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.
Which participation threats and safeguards should UXR test without turning anti-abuse controls into new barriers to legitimate participation?
Document 15
Document status. This document establishes working principles for HXR intake. HXR now has an operational internal intake workbench and governed processing records, but this does not mean a general public intake service, finalized evidence methodology, or final technical architecture has launched. Channel availability and public access remain separate development questions.
Current internal Intake AI reference path. Before processing intake, the agent must read adopted UXR Processing Invariants, use the UXR System Registry to locate the current canonical Notion modules, inspect the live Notion property descriptions and relation types, and read the module's Active Field Contracts in UXR Schema Dictionary & Field Contracts. The normal processing sequence is Intake Session → Candidate Proposition → Proposition Source Resolution → resolved Proposition, with Case Boundary Decisions and Case Work Orders where needed, followed by the appropriate Incident Case, Evaluation, Evidence, Update, Handoff, and release-control records. The agent must read back writes and must not use legacy platform fields or remembered historical schemas as current authority.
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. HXR intake must itself meet HXR 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 genuine uncertainty or conflict without manufacturing suspicion, ask for correction, and let the person review and approve the structured summary before submission.
Record provenance without suspicion. Intake should record the source of a proposition plainly. “The contributor reports…” is sufficient when the proposition comes from the contributor. When a screenshot, forwarded email, transcript, recording, or other artifact supports it, the intake record should add that support affirmatively. The system should not automatically append phrases such as “unverified,” “awaiting verification,” or equivalent credibility-reducing language merely because an artifact has not been provided. Provenance should help readers understand the evidence while preserving contributor dignity.
Alternative intake channels. HXR 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.
Contribution gradient. Different contributions can perform different evidentiary jobs, from a short account through testimony, artifacts, expertise, organization response, and reform verification. This is an internal evidence-and-motivation map, not a requirement to show the contributor a separate button for every contribution type.
Current Phase 1 boundary. The minimal Evaluation pilot uses one Add Your Experience doorway. The contributor describes what happened in ordinary language; the Intake AI or human reviewer classifies the material behind the scenes and asks only the smallest follow-up needed for a responsible candidate match, privacy/permitted-use state, or safe next action. Phase 1 reuses the existing Intake Session path and does not require follow subscriptions, automatic matching, a contributor portal, organization-specific portals, or separate contribution-type workflows. Positive outcomes, materially different experiences, corrections, workarounds, and counterexamples must be accepted through the same doorway.
Low-effort signals are not votes. “This happened to me too” may create a candidate recurrence lead. “My experience was different” may create a counterexample. Neither becomes truth, prevalence, severity, or score through count alone. Intake should seek the minimum additional context needed to determine whether experiences are materially comparable without turning a ten-second contribution into a compulsory full interview.
Phase 1 contribution summary. After pilot intake, HXR should return a plain-language summary from existing intake state: what was recorded, the candidate Evaluation match, privacy and permitted-use state, what the contribution may add, what it does not establish, and the next review step. Useful existing resolution knowledge may be returned when available. A separate persistent Contribution Impact Receipt, contributor portal, automatic notifications, and follow lifecycle remain future product hypotheses and should be implemented only if the simpler pilot summary proves insufficient.
Motivation without manipulation. Intake may show people how their contribution can help themselves, future users, institutional accuracy, public accountability, good-practice recognition, reform, and verification. It must not reward suffering, create harm leaderboards, use guilt or streak pressure, inflate the meaning of a one-tap signal, or imply that a person must disclose more than they choose in order to support reform.
Response-state continuity. Contributors should be able to learn whether an involved organization acknowledged the issue, corrected a fact, explained a constraint, supplied a remedy, proposed reform, demonstrated reform, declined to respond, or did not respond after a documented opportunity. Nonresponse is worth recording under defined contact conditions, but silence remains ambiguous and must not be represented as automatic proof of guilt, agreement, indifference, motive, or inability to reform.
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. The long-term system should let a person save progress, move between supported channels without starting over, add evidence later, export their own submission, review what HXR recorded, correct mistakes, understand what happens next, and track applicable status. Phase 1 does not promise a public account portal, automatic case identifier, cross-channel transfer, or notification service. The immediate requirement is that the private Intake Session preserve completed work and allow correction or supplementation without forcing the contributor to restart. A failed offered channel must not be represented as functioning.
Evidence requests. The process should request verifiable support when reasonably available and useful, 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. The request for supporting material should communicate that the material adds support; it should not imply that the contributor's account has no value without it.
Corrections and supplemental evidence. Contributors should be able to refine dates, wording, amounts, sequence, interpretation, and other details as they remember more or obtain records. Intake should preserve the original account privately while carrying the best-supported current facts forward into the working case. Supplying better evidence should be treated as improving the record, not as creating a credibility penalty for the contributor.
Public correction without contributor callout. When later evidence establishes a better-supported fact, the public case should normally be rewritten around that fact and the superseded public detail removed. HXR does not need to tell public readers that a contributor originally remembered ordinary wording, timing, or another detail differently unless the discrepancy itself materially affects the case. The internal working record should preserve the provenance and correction history needed for auditability.
Evidence can change the case in either direction. New evidence may strengthen a proposition, weaken it, narrow it, contradict it, change responsibility, or require a different case boundary. Intake and case-management systems should support those changes without making correction feel punitive. The objective is a more accurate case, not a performance evaluation of the contributor's memory.
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. HXR should collect only what serves a defined purpose.
Reports without documentary proof. A report remains evidence even when the person lacks an artifact. HXR may seek corroboration, request records from another source, compare independently submitted accounts, examine public information, or preserve the report for future matching and investigation. The absence of documentary proof should not trigger language that treats the contributor as presumptively unreliable. Accumulated independent evidence can support pattern detection, but volume does not automatically establish every proposition.
Identity confidence and claim confidence. HXR 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. HXR 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 stage is to continue exercising the internal intake workbench and regression suite against representative scenarios, including stressful narratives, incomplete evidence, conflicting records, accessibility needs, anonymous reporting, channel failure, cognitive overload, requests to switch channels, later artifacts that refine earlier remembered details, and attempts to manipulate the system. Testing should measure both information quality and the human burden created by intake itself, including whether contributors feel safe correcting the record, while public-service launch remains a separate readiness decision.
Document 16
A person's report should not become a one-way data transfer. UXR should preserve its consequential potential so evidence, matching, responsibility analysis, correction, learning, reform, verification, and comparison can continue after the original interaction.
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.
A UXR case does not cease to exist merely because an individual task was completed, a workflow was locally closed, or systemic reform was verified. The canonical record persists as institutional memory.
A current posture may become stable after verified reform, dormant with no current action, or historical reference. Later evidence can still record maintenance, regression, stronger reform, a changed constraint, or a superior benchmark. No one needs to manufacture a new case simply because time has passed.
If evidence moves responsibility from one organization or institutional unit to another, the contributor should not have to restart. UXR should preserve the account, evidence, prior responses, and interaction history while correcting attribution.
A contributor should be able to improve the record without becoming the object of the correction. Later evidence that establishes a better-supported ordinary fact should update the current case without turning the contributor's earlier recollection into a public credibility event.
The original account and material correction history remain available in the private evidentiary record when needed for provenance and auditability. The public case should normally present the strongest current approved evidence.
An adverse case can become a credible reform trophy when the record shows what changed, how the change affected human agency, what evidence verified it, what burden remained, and whether the improvement endured.
The original failure is not erased. The organization does not receive credit merely for promising change or describing an intention. Verified reform, durable maintenance, transparent explanation, and measurable improvement are the evidence that can transform what the case means for future readers.
UXR should distinguish historical performance from current performance. A later superior implementation can replace an earlier benchmark without making the earlier verified improvement false. The record should show both what the organization achieved and what the best demonstrated alternative has become.
Substantially matching experiences can strengthen one bounded evidentiary record without turning contributor count into proof of truth, severity, prevalence, motive, or responsibility.
UXR should be able to return practical value by showing what materially similar people or systems did, what happened next, and how well the result was verified. A successful escape path remains a workaround when the person had to absorb avoidable burden to use it.
The contributor should be able to review, correct, supplement, export, and manage permitted uses of their own testimony and evidence. Continuity does not give one contributor control over other people's evidence, UXR's independent findings, or corrections required by contrary evidence.
Operational states such as no current action, stable after verified reform, monitoring, or historical reference can reduce active workload. They do not convert the case into a discarded complaint. The evidence remains available for learning, comparison, future reform, and later verification.
Document 17
Status: Development Notes, Published for Review
Interpretive Stress Testing examines how people with different professional backgrounds, moral priorities, cognitive styles, experiences, and prior beliefs understand UXR.
The method may use real professions, social roles, philosophical traditions, historical contexts, fictional characters, or carefully bounded public-figure lenses.
The purpose is not endorsement, imitation, or appeal to authority. It is to identify what different minds notice, misunderstand, simplify, resist, overestimate, or overlook.
Fiction often concentrates recognizable human motives, institutional behaviors, moral assumptions, and power relationships into a bounded perspective. A fictional or nonhuman character can therefore function as a scenario model for conditions human institutions have already produced or may produce under unfamiliar pressures.
The character does not become evidence about the real world. The value lies in asking whether the framework can recognize and withstand the human behavior the character mirrors.
These lenses are especially useful when they model:
A useful lens should retain the traits that make the perspective distinct: ethical emphasis, anger, empathy, skepticism, puzzle-solving, operational priorities, impatience, stewardship, ambition, distrust, or other relevant qualities.
Over-sanitizing the lens defeats the exercise. The reviewer may say things UXR rejects. That friction is often the useful part.
A fictional character, profession, ideology, or public figure does not become an authority over UXR.
A hammer looking for nails may correctly identify some nails, mistake other objects for nails, and ignore everything it cannot strike.
Some lenses naturally share UXR's concern for practical agency. Others expose the framework by treating agency, transparency, or proportional responsibility as obstacles to control.
An adversarial lens can reveal whether UXR quietly assumes that every institution wants to be humane, efficient, publicly credible, or voluntarily reformable. It can also expose likely responses such as suppression, retaliation, evidence destruction, controlled audits, semantic capture, narrative inversion, and shifting burden into less visible forms.
The most important adversarial lesson so far is that a high-burden system may not be malfunctioning relative to the institution's actual objective. It may be successfully producing deterrence, attrition, reduced participation, dependence, extraction, or expressive domination. UXR must identify and evaluate that objective rather than mistaking institutional effectiveness for human legitimacy.
Read the preserved adversarial-system and reform-readiness findings.
Repeated independent misunderstandings create stronger evidence than one reaction. If several lenses classify UXR as a software-interface project, the onboarding should clarify universal scope earlier.
A single collapse-oriented reviewer interpreting every diagnosis as proof that institutions must be destroyed may reveal the reviewer more than the document.
A single adversarial lens can still expose a missing threat model when the framework had implicitly assumed cooperation. The proposed concept must then receive independent evaluation before becoming doctrine.
Which lenses would expose assumptions not yet tested, and how can UXR distinguish documentation failure from predictable worldview-driven interpretation?
Document 18
Status: Development Findings, Published for Review
Version: 0.1
This document preserves findings produced through recent Interpretive Stress Testing. The tests used deliberately different fictional lenses, including cooperative, impatient, institutionally constrained, community-centered, long-lived, and openly adversarial perspectives.
The fictional characters are not authorities over UXR, and their dialogue is not UXR doctrine. They function as bounded scenario models. Fiction often concentrates recognizable human motives, institutional behaviors, moral assumptions, and power relationships into forms that can expose weaknesses before those conditions appear in an operational system.
The most important advance came from introducing a lens that viewed practical human agency as an obstacle to domination rather than a shared objective. That test showed that UXR must prepare not only for accidental failure and reform-minded institutions, but also for systems that benefit from burden, suppress evidence, or adopt reform language while reversing its meaning.
Across the recent lenses, several existing UXR principles remained stable:
The same evidence and corrective strategy will not work equally well with every institution. A candidate working model distinguishes three broad postures.
The institution values the legitimate human objective and may respond when credible evidence reveals ignorance, coordination failure, resource constraints, technical difficulty, or unintended burden.
The institution recognizes some failure but resists because reform threatens budget, convenience, reputation, authority, internal incentives, or established procedure. Likely responses include minimization, delay, selective compliance, cosmetic reform, and methodological dispute.
The institution gains materially, politically, or coercively from the burden itself. Likely responses include suppression, retaliation, evidence destruction, controlled audits, semantic capture, contributor targeting, and shifting the burden into less visible forms.
Status note: This institutional-posture model is a framework proposal under development. It is not yet an adopted classification or scoring system.
UXR must not assume that every harmful system is malfunctioning relative to the institution's actual objective.
A system may fail relative to practical human agency while succeeding relative to objectives such as deterrence, attrition, suppressed participation, forced abandonment, obedience, extraction, surveillance, or expressive domination.
A high-burden system may not be broken. It may be successfully accomplishing an objective that UXR must identify and evaluate rather than mistaking institutional effectiveness for human legitimacy.
This distinction protects UXR from describing an intentional control mechanism as mere inefficiency. It also requires causal humility. UXR must demonstrate the objective, benefit structure, knowledge, and mechanism rather than inferring strategic intent from burden alone.
A candidate spectrum distinguishes:
These are development concepts. A real case would require evidence separating observed effects, institutional knowledge, stated purpose, actual incentives, and supported intent.
Institutions often possess records, archives, staff continuity, precedent, technical systems, and authority unavailable to the individual.
A candidate Duty of Memory principle follows:
An institution that inherits continuity, records, and authority also inherits a duty not to make each new person begin from nothing.
When an institution forgets, it should not automatically charge the cost of remembering to the person least equipped to carry it. An institution should not repeatedly require people to reconstruct facts it already holds, should reasonably preserve, or previously verified.
This principle does not require unlimited retention or unrestricted information sharing. Privacy, consent, safety, accuracy, lawful deletion, data minimization, and role-based access remain legitimate constraints.
Memory Failure is a candidate term for a system's inability to retrieve, preserve, recognize, or carry forward information required to serve the legitimate objective.
Weaponized Discontinuity is a candidate term for the deliberate breaking, withholding, invalidation, fragmentation, or refusal of institutional memory in order to force repeated proof, weaken claims, obstruct continuity, exhaust participants, or increase dependence on authority.
The distinction matters. Ordinary record loss may reflect technical failure or fragmentation. Strategic refusal to honor known history should not be softened into accidental forgetfulness.
A Compensatory Workaround is a candidate term for an unofficial practice that emerges because the formal system cannot reliably produce the required outcome.
Workarounds can preserve safety, care, access, and continuity. They can also create hidden risks:
A system should not depend on heroic insiders, secret workarounds, or sympathetic commanders to produce outcomes its formal process ought to provide reliably.
Discretion can mitigate rigid-system harm, but durable reform should not require access to a compassionate insider. UXR can document why a workaround emerged and whether it reduced greater harm. UXR does not automatically authorize illegal, unsafe, deceptive, or unreviewed conduct.
Families, neighbors, caregivers, advocates, coworkers, and community members often help people survive formal-system failures.
UXR should distinguish voluntary community support from labor the institution quietly depends upon because it failed to carry its own responsibility.
Care freely given should not be confused with burden the institution was entitled to transfer.
A favor can rescue a person. It cannot substitute for a fair system.
Recent stress tests produced a candidate Reform Readiness Pathway:
Visibility → Credibility → Materiality → Leverage → Will → Authorization → Implementation
This is not an adopted UXR diagnostic sequence. It combines evidentiary, political, organizational, legal, and operational conditions and may ultimately function better as a reform-readiness model.
In hostile systems, credible evidence may not lead toward voluntary reform. A competing branch may appear:
Visibility → Credibility → Materiality → Suppression, Co-option, Retaliation, or External Leverage
An adversarial institution may ban the framework, destroy records, expose contributors, manufacture favorable audits, flood review systems, redefine UXR terminology, or move burden into less visible channels.
Evidence may still create deferred leverage. A well-preserved record can support later journalism, oversight, litigation, historical accountability, institutional comparison, or action by external bodies even when local power prevents immediate reform.
Adversarial conditions require UXR to consider:
Transparency about method does not require recklessness about vulnerable sources.
UXR's future evidence and publication systems must distinguish public methodological accountability from unnecessary disclosure of people who face danger.
An institution may adopt UXR language while preserving the burden UXR was created to expose. It may call coercive verification a Duty of Memory, describe suppression as safety, redefine compliance as agency, or issue a controlled UXR-style audit that excludes the most affected population.
Semantic Capture is a candidate term for using UXR language, identity, metrics, or claims in ways that preserve institutional control while reversing the framework's substantive meaning.
UXR terms must remain tied to observable conditions, not accepted through institutional self-description.
UXR does not presume that institutions exist to maximize comfort or eliminate responsibility. Legitimate systems may require verification, safety controls, due process, public duties, emergency restrictions, and shared sacrifice.
UXR asks whether those burdens are necessary, proportionate, evidence-based, competently designed, fairly allocated, contestable, and open to correction.
An opponent may misrepresent that standard as a demand for comfort, convenience, or freedom from obligation. UXR should anticipate and answer that rhetorical move directly.
The recent lenses also clarified that human agency includes access to ordinary life, not only protection from catastrophe.
Human time includes time for rest, relationships, cooking, care, learning, creativity, participation, celebration, and small pleasures. A system can diminish human life through repeated administrative consumption even when no single interaction produces dramatic injury.
A candidate development question asks when available evidence becomes sufficient to justify a bounded, reversible response before complete certainty exists.
Future work may need to compare confidence, severity, urgency, recoverability, cost of delay, reversibility of the proposed action, and ability to monitor the result.
Status note: Action Sufficiency is not an adopted threshold or authorization rule.
Interpretive Stress Testing: Development Notes · Evidence Validation and Confidence · Participation Integrity and Anti-Brigading · UXR Taxonomy
Document 19
Everyday examples of how systems respect inherent dignity and preserve or constrain practical agency, and how good, difficult and mixed experiences can inform HXR Evaluations.
Human agency can sound abstract until it appears in a system someone already uses. This library shows where design preserves, transfers, constrains, or extracts people's practical ability to understand, choose, act, and recover.
Good experiences make agency visible too. A clear control, an accessible route or an understandable choice can help someone act with confidence and dignity. HXR studies why these experiences work, who benefits and what an organization would need to preserve or reproduce them. Concrete experiences can support Evaluations that bring positive, negative and mixed evidence into a continuing analysis.
Recognizing what a system enables or makes difficult is a starting point. HXR should also help people act on what has been learned and help organizations learn from demonstrated good practice.
The HXR Taxonomy explains the terms used across these examples, including Human Agency, Administrative Burden, Shared Efficiency, Burden Transfer, and Resolution Knowledge.
Which example helps you recognize agency in a system you already encounter? Which comparison would help you make a better decision? Which ordinary process gives you useful control or makes something easier, and what makes it work? Which process consumes more of your life than its price, policy, or public description reveals?
HXR welcomes examples of both failure and success. A good system deserves to be understood and copied, not merely enjoyed in isolation.
Document 20
How small design regressions consume time and attention across repeated everyday interactions.
A light switch illustrates micro-friction because the objective is simple, frequent, and well understood: make a light turn on, turn off, or dim.
A control can become less legible when its physical state no longer communicates the light's state, multiple switches control the same fixture, dimming uses a small secondary control, or operation requires trial and correction in a dark room. Each interaction may cost only seconds, but repeated uncertainty consumes attention and interrupts flow.
The lesson is not that everyone should replace a functioning switch immediately. Replacement itself has costs. The UXR question is whether new installation, routine replacement, or future product design should preserve the clearest known interaction rather than normalize a regression.
Agency preserved: immediate comprehension, predictable operation, tactile usability, low cognitive demand.
Tradeoffs to examine: electrical safety, multi-location control, dimming capability, accessibility, installation cost, and compatibility.
What other everyday control makes a simple objective less clear than an older or alternative design? Describe the object, the expected action, the uncertainty it creates, and what design performs better.
Document 21
How a formally approved referral can fail when administrative systems do not produce timely usable access.
HXR Home · Recognizing Human Agency
A referral does not create meaningful access merely because it exists in a database. Agency depends on whether the patient can understand the urgency, reach an available specialist, obtain reassignment when the assigned provider cannot meet the need, learn the applicable access standard, and reach someone capable of correcting the failure.
An urgent referral should be assigned to a provider capable of meeting the urgency. If the system assigns the patient to someone unavailable for weeks, the failure already exists before the patient spends a minute seeking correction.
The patient's later phone calls, office visits, and follow-up may be additional burden created by the original assignment failure. A successful escalation does not erase the cost required to obtain it.
The person who does not fight may lose fewer minutes while losing more of the intended outcome.
An urgent label has little practical value if it does not alter assignment, outreach, scheduling, escalation, or monitoring.
HXR asks whether the system translated the approved need into usable care. It does not ask every patient to become an insurance expert or personally coordinate providers, medical groups, health plans, and regulators.
An official grievance may create legal or regulatory value, but filing it is not the same as obtaining care within the remaining access window. HXR should separately track the immediate appointment, administrative remedy, workaround, and system reform. A workaround that succeeds once is not proof that the system was repaired.
Agency preserved: assignment to an available provider, understandable urgency, timely scheduling, reassignment, status visibility, records access, escalation, and effective remedy.
Tradeoffs to examine: actual specialist capacity, triage, clinical appropriateness, geographic access, continuity of care, and emergency routing.
Describe a healthcare process where formal approval, coverage, or eligibility did not produce practical access. What should the system have done before asking the patient or caregiver to intervene?
Document 22
How accessible environments expand agency without requiring disabled people to negotiate each barrier individually.
Wheelchair access offers a familiar example of civilization recognizing that a barrier created by buildings and infrastructure should not remain the individual's private problem.
Ramps, curb cuts, elevators, adequate door width, reachable controls, accessible restrooms, seating, and clear routes do more than reduce inconvenience. They determine whether a person can enter, move, participate, work, receive care, shop, vote, and leave without depending on improvisation or permission.
Accessible design also demonstrates that reform can help people beyond the group that first made the barrier visible. Curb cuts assist wheelchair users, people using walkers, parents with strollers, workers moving carts, travelers with luggage, and people with temporary injuries.
Agency preserved: independent access, supported access by choice, dignity, predictability, participation, and safe exit.
Tradeoffs to examine: physical constraints, historic structures, safety, cost, maintenance, wayfinding, and whether a nominal accommodation works in practice.
What barrier in a building, service, or public space forces someone to ask for help, use a separate route, or abandon the objective? What design would make access ordinary rather than exceptional?
Document 23
How contradictory instructions, transfers, and dead-end escalation consume agency and make resolution dependent on endurance.
A customer contacts support because they have an objective they cannot complete alone. The department's philosophy determines whether the system treats that person as someone to help, a ticket to close, a risk to contain, or a burden on the queue.
One support organization may believe, “Our purpose is to solve people's problems.” Another may behave as though its purpose is to answer calls, reduce handle time, prevent refunds, protect the company, or move work out of the visible queue.
Those purposes produce recognizable tells: direct answers or intentional ambiguity, listening or interruption, ownership or reflexive transfer, explanation or scripted deflection, and curiosity or contempt.
UXR calls the gradual movement away from the department's human purpose institutional drift.
Employees may not personally intend harm. They may be adapting rationally to what the institution measures and rewards. If ownership increases handle time, transfer becomes safer. If a direct answer creates liability, ambiguity becomes safer. If a refund hurts a metric, exhaustion becomes useful to the system even when nobody says so openly.
In a transfer loop, the institution's departments fail to coordinate internally. The customer must remember the history, repeat the evidence, compare contradictory explanations, identify the responsible office, and carry information between teams.
This is burden transfer. The company saves internal coordination while the customer performs it without authority, training, compensation, or reliable access to the record.
A loop can produce abandonment and benefit the institution without proof that it was deliberately designed for that purpose. UXR distinguishes accidental friction, neglected friction, exploited friction, and strategic friction.
A humane support system should measure more than call speed. It should examine whether the person reached the legitimate objective, understood the result, retained records, avoided unnecessary repetition, could reach someone with authority, and had a usable remedy when the first path failed.
Institutions become what they measure. A department that measures only the queue may learn to manage people out of the queue rather than help them out of the problem.
When Costs Don't Disappear · How UXR Creates Accountability · UXR Taxonomy
Document 24
How transportation systems should account for safety and the cumulative human time consumed by delay.
UXR Home · Recognizing Human Agency
Transportation makes aggregate human cost visible. A trip that takes fifteen minutes rather than seven may appear to cost one person eight minutes. When hundreds or thousands of people experience the same delay repeatedly, the system consumes a large amount of human life.
Speed alone is not the standard. Roads and signals must protect drivers, pedestrians, cyclists, children, disabled people, neighborhoods, emergency response, and competing directions of travel. The UXR question is whether the system achieves those legitimate goals with the least avoidable consumption of time, attention, fuel, predictability, and agency.
An average of one avoidable minute per person per day does not mean every person loses one minute every day. One driver may encounter no delay for several days while another loses twenty minutes during one trip. The average expresses total scale across people and time.
A poorly coordinated traffic signal does more than consume minutes.
UXR calls this a burden cascade: one design choice produces secondary and downstream costs across several systems.
UXR must distinguish infrastructure design, signal timing, maintenance, land-use decisions, demand concentration, transit alternatives, and user behavior. It must test whether a green wave or another coordination strategy would preserve or improve safety rather than assume that faster always means better.
Agency preserved: predictable travel, safe movement, usable route choice, accurate timing, accessible mobility, and efficient coordination.
Tradeoffs to examine: collision risk, pedestrian access, neighborhood impacts, emissions, emergency response, induced demand, cost, and distribution of delay.
Describe a transportation delay or design that repeatedly consumes time. What other effects follow from that delay beyond the minutes themselves?
Document 25
An institution can cut a cost from its own books without removing the cost from the world.
It may reduce staffing, training, coordination, recordkeeping, or support. The financial statement improves. But the work does not disappear. Customers, patients, employees, families, or the public may now spend more time correcting errors, repeating information, waiting, researching, coordinating departments, or finding someone with authority to help.
The cost did not disappear. It changed owners.
A self-service kiosk may save everyone time. A broken support workflow may force a customer through repeated calls while the company pays representatives to manage the same unresolved problem again and again.
A 45-minute support call that produces no solution may consume:
The humane path can also be the cheaper path when the organization equips employees to understand the objective, preserve context, exercise appropriate authority, and produce durable resolution.
UXR should not confuse a short contact with an efficient system.
Financial accounting records payroll and operational savings. It rarely records what people absorb outside the institution:
A company may appear to create value from nothing when it is actually converting human resources it does not own into corporate resources it does own.
One unnecessary transfer may cost ten minutes. Repeated across millions of people, the same design can consume years of human life.
That average may fall unevenly. Some people lose little time while patients, caregivers, disabled people, hourly workers, or people with fewer alternatives absorb concentrated burden.
Returning time and agency gives people more room to care for family, rest, work, learn, create, participate in their communities, or improve their own lives and the lives around them.
Document 26
How HXR Evaluations can help people recognize good experiences, understand tradeoffs and make better-informed choices about products, services and institutions.
HXR’s main analytical artifacts are Evaluations, supported by Cases and other evidence. They examine what works well, what creates difficulty, for whom, and under which conditions. An Evaluation can help a reader recognize a practice that protects dignity and agency while showing the limits of what is known.
People can use this evidence alongside price, availability, personal needs and other relevant information. Where comparison is supported, HXR aims to make good experiences easier to find and meaningful differences easier to understand.
A lower price may hide hours of waiting, repeated calls, difficult correction, poor accessibility, unclear information, or a lack of meaningful remedy.
Price shows what you pay in money. An Evaluation can also examine the time, effort, attention and control an experience requires, and whether it provides dignified treatment.
See a simple comparison: The Cheapest Option Isn't Always the Lowest Cost.
Waiting burden, referral access, communication, billing clarity, record continuity, respect, accessibility, error correction, and remedy.
Care access, referral speed, authorization burden, denial clarity, appeal quality, network accuracy, continuity, and the amount of work shifted onto patients and caregivers.
Curriculum value, student agency, administrative friction, accessibility, support, instructor and staff treatment, degree usefulness, and correction when the institution makes an error.
Worker agency, policy clarity, internal tools, management respect, scheduling, accommodations, support, reporting paths, and whether internal metrics reward humane outcomes.
Learning burden, setup time, support, lock-in, failure recovery, accessibility, repairability, cancellation, and total human cost beyond purchase price.
Travel time, walkability, shade, sidewalks, service access, permitting, public participation, stores and care access, traffic efficiency, safety, and the performance of institutions operating within the city.
Comprehension, practical access, delay, dignity, contestability, proportional burden, records, due process, remedy, and effects across different populations.
Information supports agency only when people can understand it, trust it, compare it, and act on it. HXR calls this decision agency.
A well-supported Evaluation can make an organization’s good work visible and explain why it matters to people choosing a service, workplace or product. That recognition can strengthen earned trust and give teams a reason to preserve effective practices. Any effect on customer choice, recruitment, retention or revenue must be demonstrated rather than assumed.
Organizations may hire consultants to understand the published target and improve their systems. They may not buy influence over HXR's measurements, methodology, publication decisions, evidence, or rating.
Blue Score methods remain under development; HXR does not yet claim an operational or validated universal score. Evaluations and their evidence can be useful before scoring is ready. Any future score or grade must explain:
A future score could provide a quick signal. The underlying Evaluation, evidence and limitations would remain necessary to interpret it.
Document 27
Price tells you how much money leaves your account. It does not tell you how much time, effort, attention, uncertainty, dignity, or control a choice may consume.
Imagine two services:
The second option costs $20 more in money. The first may cost far more in life.
Price shows what you pay in money. A Blue Score should help show what you may pay in time, effort, attention, dignity, and control.
A useful Blue Score cannot operate as a mysterious badge. A person comparing hospitals, insurance plans, schools, employers, cities, products, or service providers should be able to open the score and see why it differs.
The comparison might show:
More information does not automatically create agency. Information must be credible, understandable, relevant, comparable, and available at the point of decision.
UXR calls that practical ability decision agency.
A patient choosing a doctor's office may care that one office typically keeps people waiting ten minutes while another regularly consumes an hour. A student may care whether a school's curriculum, administration, and support help students complete meaningful goals. A resident may care whether a city returns time through better transportation, access, permitting, sidewalks, shade, and public services.
When human performance becomes visible, institutions gain a reason to compete on it. A strong Blue Score could help an organization attract customers, patients, employees, students, residents, investors, contracts, or public trust.
Companies cannot buy a better score. They may pay qualified people to help them build a better experience. Improvement must come from changing the system, not influencing the measurement.
Using UXR to Make Better Choices · Independence and the One-Way Authority Rule · UXR Taxonomy
Document 28
How HXR Evaluations make good experiences and areas for improvement visible, connect dignity and agency with organizational performance, and help successful practices spread.
Organizations already compete on price, speed, quality, reliability, convenience, expertise, trust, and innovation.
HXR gives organizations of every size another dimension on which to improve and, where valid comparison exists, compete: respect for human agency, human time, and human dignity.
HXR examines what helps people understand, choose, act and recover across good, difficult and mixed experiences. Its main analytical artifacts are Evaluations, supported by bounded Incident Cases and other evidence. An Evaluation can recognize an effective practice, explain where it works and for whom, identify limits, and track whether the benefit lasts. An organization does not need to have failed first for its good work to merit attention.
Depending on the domain, that may include policies, staffing, incentives, records, queues, forms, handoffs, physical spaces, legal processes, customer support, procurement, software, and automation.
Organizations often possess capabilities no individual customer, patient, worker, student, resident, or supplier can match, including greater information, continuity, staffing, automation, expertise, legal resources, authority, and the ability to redesign the process.
That greater capability creates greater responsibility. Organizations should carry burdens they are better equipped to handle rather than transferring coordination, recordkeeping, explanation, error correction, and responsibility routing downstream.
HXR should not preserve blame merely because an organization was named first. If evidence shows that a different party controls the relevant mechanism, HXR should correct the attribution.
An organization that says “not us” should help make that claim testable by identifying what it controls, who it believes does control the issue, why, and what path reaches that party. A supported reattribution can remove unfair blame while preserving any separate responsibility for disclosure, coordination, handoff quality, or remedy.
When people can understand their options, obtain clear updates and accomplish their objectives with appropriate support, they retain more control over the interaction. The same practices can help an organization avoid unnecessary repeat contacts, reduce staff rework, and give customers clearer reasons to trust and choose it. HXR can make that connection inspectable: what the person experienced, what practice enabled it, and what organizational benefit the evidence supports. Commercial outcomes such as retention or lower costs remain potential benefits until there is evidence to establish them.
A workflow designed around successful resolution can reduce repeat contacts, transfers, escalations, staff rework, avoidable exceptions, refunds, complaints, churn, regulatory exposure, employee burnout, and queue pressure.
A short contact that fails may cost more than a longer contact that permanently resolves the objective. Organizations should measure total resolution time, repeat-contact burden, and resolution yield rather than rewarding only short handle time or visible queue reduction.
HXR does not need to make “becoming a benchmarking organization” its identity objective. If it accumulates rigorous, comparable evidence about human outcomes and verified reforms, benchmarking becomes a consequence of that knowledge.
Organizations should be able to learn what peers have demonstrated, what analogous systems in other domains have solved, which constraints are genuinely different, and which reforms have been verified. A successful practice should not have to remain trapped inside the organization that discovered it.
Peer comparison requires material comparability. Cross-domain comparison can provide comparative capability evidence and useful questions without pretending that different technical systems are equivalent.
Organizations may comment, provide evidence, challenge errors, explain legitimate constraints, identify responsible parties, propose reforms, share successful practices, and help test standards.
They do not receive a right to approve a supportable public comparison. HXR comparisons should be contestable through evidence and method, not consent-dependent. If an organization's counterevidence shows that HXR is wrong, HXR should correct the finding.
Organizations may not buy a better result or hidden criteria. Improvement must come from changing the evidence, correcting an error, demonstrating a legitimate constraint, or improving the human outcome rather than influencing the ruler.
HXR should recognize both organizations that already handle people well and organizations that improve. Credit belongs to the demonstrated practice, system, team or implementation within the limits of the evidence. An Evaluation can preserve what worked, record what changed, and explain what another organization would need to reproduce the benefit.
Documented good practice can help people make informed choices and give organizations a credible account of the work worth maintaining and sharing. Later evidence may strengthen, narrow or revise that account. Recognition remains independent and open to correction.
Document 29
How designers, builders and system owners can learn from HXR Evaluations, document good experiences, preserve agency and dignity, and test benefits for people and organizations.
HXR is for people who design, build, operate, maintain, regulate, procure, or improve systems.
That includes software teams, engineers, service designers, product managers, clinicians, administrators, tradespeople, operations leaders, accessibility specialists, policy designers, support organizations, and people responsible for physical spaces or public infrastructure.
Traditional UX often examines whether a person can use an interface effectively. HXR also examines the institution around the interface: staffing, policies, incentives, handoffs, records, appeals, recovery, access, and the burden transferred when the designed path fails.
HXR Evaluations examine how a design works in people’s lives. Cases and other evidence can show a successful interaction, a failure, or different results under different conditions. The aim is to identify what preserves dignity and practical agency, what deserves improvement, and which demonstrated practices another team could learn from.
Look at successful paths as closely as recovery paths. What helped the person understand the choices, keep control and reach the intended outcome? What did the organization provide, and did the benefit depend on an exceptional employee or work the person had to supply? Preserve the conditions that made the experience work so the organization can maintain it and other teams can test whether it transfers. Show organizational benefits where they are supported, without treating a completed task as proof of dignity, satisfaction or commercial success.
A humane system cannot assume that every record is correct, every user understands the process, every channel works, or every employee has complete context.
Recovery paths, contestability, accessible assistance, continuity, explanation, and proportionate remedy belong in the design rather than being treated as exceptions after launch.
Internal savings may reflect shared efficiency, or they may represent work transferred downstream. Builders should measure not only completion rates and operating costs but time lost, repeated work, abandonment, correction burden, inaccessible choices, delayed outcomes, and preventable escalation.
HXR needs practical criticism from people who understand real constraints. Identify where its standards ignore safety, fraud, law, staffing, technical limits, operational tradeoffs, or unintended consequences. Share examples where a humane design also improves performance, and cases where an attractive reform merely moves the burden elsewhere.
HXR Taxonomy · Friction, Pain, Harm, and Invisible Taxes · How HXR Creates Accountability · Contributing to HXR
Document 30
How employees, managers and internal advocates can use HXR Evaluations to preserve good practice, investigate burden, and connect dignity and agency with organizational performance.
People inside organizations can help reveal both the practices that serve people well and the conditions that create avoidable burden. You may have seen a clear handoff, an accessible process, a team that preserves context, or an effective way to help someone make an informed choice. These everyday successes deserve to be understood, preserved and shared.
HXR brings this evidence into Evaluations, supported by bounded Incident Cases and other sources. Your experience can help explain how a practice affects dignity and agency, what makes it work, where its limits lie, and whether it also improves the organization’s work. You do not need to hold the highest title or prepare a complete analysis to contribute something useful.
You may care deeply about treating customers, patients, students, coworkers, applicants, or residents with dignity. You may also be looking for another operational lever, a stronger proposal, a way to improve your team's standing, or evidence that a recurring burden deserves resources.
Those motives can coexist. HXR evaluates the resulting system and evidence rather than demanding ideological purity from every participant.
Document the human and organizational effects separately, then examine their relationship. A clear process may help a person act with confidence while reducing repeat explanation for staff. A reliable handoff may spare the person coordination work while reducing internal rework. If you have measured results, describe the method and limits; if you have observed a promising effect, identify it as an observation to test.
Costs to investigate may appear internally as:
Connecting human effects with operational effects can help an organization recognize that respect for agency is not separate from performance.
Do not expose confidential records, personal data, patients, customers, coworkers, or yourself to unnecessary risk. HXR's formal protected-contribution systems are not yet operational. Use lawful internal channels, public records, anonymized examples, or professional advice where appropriate.
Organizations and internal advocates should be able to comment on standards, submit evidence, explain legitimate constraints, document existing good practice, propose reform, and help evaluate implementation. Public credit should follow demonstrated good performance or verified improvement. They should not be able to buy control over findings or scores.
Why Organizations Should Want HXR · How HXR Creates Accountability · Contributing to HXR
Document 31
UXR welcomes auditors, quality professionals, compliance teams, accessibility reviewers, security specialists, red teams, tiger teams, process engineers, reliability teams, and institutional reviewers.
UXR examines human-system vulnerabilities that conventional audits may miss.
When a process becomes too slow, confusing, inaccessible, or repetitive, people create workarounds to accomplish legitimate work.
Those workarounds can become security, safety, privacy, compliance, recordkeeping, reliability, and accessibility failures.
A door-control sequence that causes employees to prop the door open is not only a usability defect. It is a security vulnerability created by friction.
UXR does not yet offer a completed certification, scoring rubric, audit protocol, or Blue Zone standard.
This page identifies a future application and invites people with audit and quality expertise to help define what evidence, sampling, controls, repeatability, and independence a credible UXR audit would require.
A useful development exercise may attempt ordinary objectives under realistic constraints, document the visible and hidden costs, identify workarounds, and test whether the institution fixes the root cause or only blocks the workaround.
Such testing must remain lawful, ethical, safe, authorized where necessary, and designed to avoid harming people or systems.
Help UXR connect human agency with established practices in quality assurance, accessibility, safety engineering, compliance, risk, security, reliability, Lean, Six Sigma, and institutional audit.
Document 32
An on-ramp for researchers, students, educators, authors, and others studying human agency, dignity, time, burden, systems, and institutional behavior.
UXR welcomes researchers, students, educators, authors, and independent thinkers who study human agency, dignity, administrative burden, institutional behavior, accessibility, service systems, attention, public policy, technology, healthcare, labor, design, or the value of human time.
UXR examines human-made systems of every kind, not only software or machine interfaces.
UXR applies scientific discipline to human-system interactions by separating observation, explanation, and evaluation.
It aims to measure supportable costs and outcomes, test causal explanations, preserve uncertainty, expose inference trails, and distinguish factual confidence from moral judgment.
Its measurements, baselines, weights, and Blue Score methods are not yet validated operationally. Researchers should treat the current documents as a developing research program and public methodological foundation, not as a completed scientific instrument.
Scientific framework · Interpretive stress testing · Complete reviewer packet
Document 33
UXR offers journalists a developing framework for examining how institutions consume or preserve human time, attention, effort, dignity, agency, safety, health, and opportunity.
UXR began by documenting a framework, moved into engineering and testing that framework in public, and is now accepting limited real-world submissions in Private Alpha. Outside sandboxed regression tests, its casework uses real experiences and records rather than invented case stories.
The project has reached this stage without a formal programming team, board of directors, or dedicated domain. That makes the development path unusual, but not self-validating. The more consequential fact is inspectability: UXR now has a bounded intake process, evidence and correction records, proposition provenance, release gates, a private regression ledger, and public changelog entries that record failures as well as additions.
The first 12-fixture manual baseline produced eight passes and four failures, so the suite failed overall. It was manual, single-grader, self-graded, and sequential. No executable publication broker was in the decision path. UXR therefore does not claim that broker enforcement has been validated or that the failed suite passed.
The observed defect led to fail-closed candidate/source-resolution records, a no-manufactured-attribution invariant, authoritative result linkage, idempotent write identities, a frozen v1 specification, and draft successor coverage. Fixture scenarios, acceptance criteria, prohibited constructions, and document-to-test mappings remain private so the benchmark cannot be reverse-engineered.
UXR does not yet have a mature or representative case database, validated automated broker, staffed public intake service, operational Blue Score, or broad scientific validation. Private Alpha submissions are limited, and publication remains a separate human-gated process.
Journalists can inspect whether UXR overstates evidence, identify missing domains, contribute public records or reporting methods, challenge governance and privacy assumptions, and point to reforms or institutional responses that deserve documentation. Participation in review does not automatically enroll anyone's experience into a public case.
Live UXR Cases · Complete UXR Reviewer Packet · Current Project Status · Contributing to UXR · Development Changelog
Document 34
You may have found UXR while researching ethics, moral philosophy, human agency, human dignity, institutional responsibility, technology ethics, healthcare ethics, labor, accessibility, religion, public policy, or the moral use of human time.
UXR examines a practical ethical question:
When a human-made system saves money, labor, time, or complexity for an institution by transferring those costs onto people, when does that transfer become unfair, extractive, negligent, or morally unacceptable?
UXR does not rely on moral language alone. It also asks what can be observed and measured: minutes lost, work repeated, choices obscured, care delayed, dignity reduced, risk increased, opportunities denied, and remedies made harder to reach.
UXR is building a scientific, ethical, and institutional framework for evaluating the human costs created by organizations, services, products, laws, technologies, and public systems.
Its method separates several questions that often get collapsed together:
UXR is not morally neutral. Its mission is explicitly concerned with human agency, dignity, and stewardship. Its method, however, must remain evidentially disciplined, causally humble, and open to criticism.
UXR is still developing its ethical framework. It should not quietly invent moral doctrine and then embed it in ratings, scoring rules, governance systems, or public judgments without scrutiny.
Begin with the Founding Declaration and What UXR Means by Human Agency.
Continue to Friction, Pain, Harm, and Invisible Taxes, How UXR Creates Accountability, UXR Independence and the One-Way Authority Rule, Evidence Validation and Confidence, and the UXR Taxonomy.
For the complete current framework, open the Complete UXR Reviewer Packet.
You do not need to endorse the project to improve it.
Useful contributions include identifying hidden assumptions, ethical contradictions, missing traditions, category errors, weak definitions, overclaims, underclaims, neglected populations, conflicting duties, and cases where the framework's moral language outruns its evidence.
UXR especially welcomes input from philosophers, ethicists, theologians, clergy, legal scholars, disability scholars, clinicians, labor researchers, economists, technologists, designers, historians, public administrators, advocates, and people whose lived experience exposes obligations that institutions routinely overlook.
The framework is still being built in public. Serious criticism can still change the foundation.
Document 35
Many people navigate systems on behalf of someone else: a child, parent, spouse, disabled person, patient, student, client, or person who cannot safely or practically act alone.
These relationships create distinctive burdens involving consent, authority, records, privacy, repetition, handoffs, and the preservation of another person's agency.
A caregiver or advocate may act with delegated authority while still preserving the affected person's choices, understanding, dignity, and control wherever possible.
Systems often require the third party to prove authority repeatedly, navigate inconsistent privacy rules, carry records between departments, coordinate appointments, reconstruct history, and absorb delays that affect both people.
UXR does not yet operate a live intake or advocacy service. This page identifies an audience and design requirement that future intake, evidence, continuity, and reform systems must support.
Intake and Evidence Collection · Contributor Continuity and Resolution Knowledge · Supported Agency and Accessibility
Document 36
An on-ramp for people evaluating whether organizations create durable value while respecting human agency and avoiding hidden human liabilities.
Investors and funders evaluate whether an organization can create durable value, manage risk, retain trust, execute well, and survive correction when something goes wrong.
UXR proposes that treatment of human agency, human time, and human dignity may provide another useful signal.
An organization that consistently reduces avoidable burden may demonstrate:
These relationships must be tested. UXR should not claim that a high future Blue Score guarantees financial performance or that humane systems always produce immediate savings.
An institution can report efficiency while shifting administrative work, delay, risk, and coordination onto customers, patients, workers, suppliers, or the public. Those costs may later return as churn, litigation, regulation, poor reputation, staff burnout, failed implementation, or loss of trust.
When Costs Don't Disappear explains this burden-transfer model.
Verified UXR findings and Blue Scores could eventually help investors and funders compare organizations on:
A score should remain one signal among many, with its evidence visible underneath. UXR does not provide investment advice.
Funding must not buy influence over standards, evidence, findings, publication, or scores. Review UXR Independence and the One-Way Authority Rule.
Investors, grantmakers, foundations, procurement officers, and institutional funders can help identify which human-performance measures would be meaningful, which incentives could distort them, and what evidence would make a signal credible rather than promotional.
Document 37
An on-ramp for public officials, agency leaders, policymakers, regulators, civic organizations, and people responsible for public systems.
Public systems distribute time, access, safety, understanding, dignity, opportunity, and remedy across entire populations. Small recurring burdens can become large civic costs when repeated across millions of interactions.
UXR offers public leaders a way to examine those costs without assuming that every delay is avoidable or that every difficult rule lacks a legitimate purpose.
A permit process, benefit application, transportation system, court procedure, healthcare program, school system, or public website may consume only a few extra minutes per person while collectively consuming years of public time.
UXR's developing Human Time Dividend would estimate time returned when reform removes an avoidable burden while preserving safety, accuracy, access, consent, and due process.
Public systems must balance rights, safety, fraud prevention, limited resources, legal duties, competing populations, and long-term effects. UXR does not define every obstacle as failure. It asks whether the purpose is transparent, the evidence supports it, the burden is proportionate, alternatives were considered, and meaningful correction remains available.
Future UXR findings could support:
UXR should not become a tool of one party, ideology, religion, or institutional faction. Different groups may disagree about remedies while still examining the same minutes lost, treatments delayed, forms repeated, risks created, choices constrained, and outcomes changed.
Public officials, civil servants, regulators, policy researchers, civic groups, and affected communities can help identify measurable burdens, lawful constraints, missing populations, better baselines, and reforms that improve public outcomes without merely moving costs elsewhere.
Universal Scope · Evidence Validation and Confidence · Contributing to UXR
Document 38
A research on-ramp for examining how social platforms, recommendation systems, engagement design, and automated mediation affect attention, relationships, understanding, and agency.
Social platforms such as Facebook, TikTok, Instagram, YouTube, Reddit, and future services mediate attention, relationships, news, identity, community, commerce, and public life.
They should fall within UXR's universal scope because human beings design, operate, regulate, fund, and profit from the systems that shape these experiences.
A person may enjoy a platform while losing meaningful control over attention, privacy, information, or social relationships. Another person may dislike a protective limit while retaining or gaining agency.
UXR therefore would not treat engagement, time-on-platform, self-reported satisfaction, or growth as complete measures of benefit.
These questions require careful evidence. Correlation between platform use and an outcome does not automatically prove causation. Effects may differ by age, intensity, content, social context, vulnerability, platform design, and individual objective.
UXR should distinguish:
Social platforms could eventually receive category scores for agency, attention stewardship, transparency, privacy, safety, accessibility, recovery, contestability, and verified reform. No such official UXR scores currently exist.
UXR welcomes people studying teenagers, adults, families, relationships, mental health, attention, misinformation, platform governance, recommender systems, labor, advertising, and online communities.
Share findings that strengthen or complicate these dimensions. Identify established measures UXR should adopt or avoid. Explain where the framework risks oversimplifying different platforms or populations. Help define what humane digital performance should mean without converting one political or moral preference into assumed scientific fact.
UXR for Researchers and Writers · UXR Taxonomy · Contributing to UXR
Document 39
Status: Development Notes
HXR has one framework but many legitimate entry points. A person seeking immediate help, a researcher, an executive, a small-business owner, a journalist, a designer, an auditor, an employee, an investor, and a public official do not arrive with the same question.
An on-ramp should begin with the visitor's objective, vocabulary, prior knowledge, available attention, likely next action, and relationship to the burden. It should not require every visitor to understand the entire constitutional framework before receiving relevant value.
Professional role alone does not determine how someone recognizes HXR. Onboarding should also consider whether the visitor:
A person who spent five hours correcting an urgent referral needs different language from someone who quietly accepted a three-month delay. Both reveal system performance.
An on-ramp should account for why a person might contribute and how much capacity they have. The statements below are motivation and research lenses, not a Phase 1 button menu or a requirement that contributors classify themselves. The current Evaluation pilot presents one Add Your Experience doorway and performs contribution classification behind the scenes. Useful recognition statements include:
These statements help HXR understand distinct motivations and future needs. Phase 1 does not expose every statement as a separate route. The single doorway should accept all of them in ordinary language, preserve privacy and evidence limits, and return a plain-language contribution summary.
HXR should never require the maximum possible contribution before accepting the minimum useful one. A short account should remain short unless one additional fact is genuinely needed for matching, privacy, provenance, or the next safe action. A complete artifact submission should not force the contributor to narrate everything again.
During Phase 1, continuity is preserved through the private Intake Session and the contributor receives a plain-language summary of what HXR recorded, the candidate match, privacy/use state, likely contribution role, and limits. A persistent Contribution Impact Receipt, follow subscriptions, automatic notifications, and contributor portal remain deferred until real use demonstrates that the simpler model is inadequate.
How Your Contribution Can Matter defines the public contribution ladder and motivation model.
HXR may examine its documentation through different professional, moral, cognitive, cultural, historical, and fictional lenses.
The purpose is not to treat any character, public figure, profession, or ideology as an authority. A lens can correctly recover one principle while importing another conclusion from its own worldview.
Useful outputs include:
Document 40
Audience-specific reading paths into HXR Evaluations, successful and difficult experiences, human agency, organizational learning, research, and participation, with current service limits.
HXR publishes Evaluations supported by Incident Cases and other evidence, alongside its principles, methods, examples, and development notes. You can explore a successful practice, understand a difficult experience, compare evidence, or help develop the project. You do not need to read everything in the same order.
Choose the path that best matches why you are here. Each doorway leads into the same framework from a different starting point.
Browse Evaluations. An Evaluation brings evidence together about a defined subject; linked Incident Cases preserve the bounded experiences that inform it. Read the findings, strengths, limits, counterexamples, organization responses, and updates.
Good experiences can reveal practices worth preserving and sharing. Explore a relevant Evaluation or visit Share an experience to describe what happened, what you were trying to accomplish, and what helped. Evidence of benefits to the organization is useful too, when available. A successful experience is welcome even when it did not begin with a complaint or require a reform.
Participation uses the same evidence and publication safeguards as other experiences and remains subject to the pilot's current capacity.
HXR does not yet provide live case intervention, emergency assistance, or direct resolution services.
It may still help you identify the type of burden you are facing, understand which system controls the next step, find relevant examples or resolution knowledge, and prepare a clearer record of what happened.
If you are facing an immediate medical, legal, safety, housing, or other time-sensitive crisis, use the appropriate emergency, regulatory, professional, or public-service channel first.
If the normal process is sending you in circles, read What HXR Adds When the Normal Process Reaches a Dead End. Relevant Evaluations, evidence-bounded resolution knowledge, and durable records can help preserve the objective and what happened next. HXR cannot compel an institution to act; Private Alpha capacity remains limited, and not every intended function is available at broad public scale.
For a concrete healthcare example, read The 96-Hour Appointment Loop: DMHC and HXR Compared.
You can also visit Recognizing Hidden Human Costs in Everyday Systems and begin with the situation closest to yours.
Start with Evaluating HXR, then review HXR Independence and the One-Way Authority Rule, Current Project Status, and the Founding Declaration.
Begin with Welcome to HXR.
Read HXR: Start Here, then continue to the Founding Declaration and What HXR Means by Human Agency.
Read HXR for Ethics, Morality, Human Agency, and Human Dignity. It connects measurable system burdens with moral and institutional responsibility and invites scholars, clergy, researchers, advocates, and serious critics to help shape the framework before its ethical assumptions become scoring rules or public judgments.
Read Why Organizations Should Want HXR.
This path covers learning from successful practice, reducing avoidable work, and examining benefits to people and organizations without giving institutions control over findings.
Read Improving an Organization From Within.
Read HXR for Designers, Builders, and System Owners.
Read HXR for Researchers and Writers.
Read HXR for Journalists.
Read Social Platforms, Attention, and Human Agency.
Read HXR for Caregivers, Proxies, and Advocates.
Investors and funders can begin with HXR for Investors and Funders. Public officials and civic leaders can begin with HXR for Public Leaders and Policymakers.
Use the HXR Taxonomy.
Open the Complete HXR Reviewer Packet.
Read Contributing to HXR.
Document 41
What HXR has established, what its limited Evaluation and Incident Case pilot can do today, and what remains under development.
Document status: Current orientation and project boundary
This page explains what Human Experience Reform has established, what is operating in bounded form, what remains under development, and what does not yet exist. It is designed to prevent readers from mistaking ambition, publication, or polished institutional language for completed operations.
HXR operates a limited, founder-led pilot that publishes Evaluations and Incident Cases. Evaluations bring evidence together around a defined subject; Incident Cases preserve bounded experiences, including direct burdens or benefits and individual outcomes. Evidence can support, qualify, challenge, or contradict an Evaluation. Successful practice and verified improvement can receive appropriate credit without erasing unresolved concerns or extending a finding beyond its evidence.
This is real operational infrastructure. It is not yet a broad staffed public intake service, a large or representative body of evidence, or proof that HXR's future measurement and scoring methods are scientifically validated. Private Alpha participation and publication remain limited by current capacity and safeguards.
A person does not have to be angry, fight for correction, or report a failure for an experience to be worth examining. Successful, difficult, and mixed experiences can all contribute. Taking an account seriously does not automatically validate every factual, causal, legal, moral, or intent-based conclusion attached to it.
Low complaint volume does not establish satisfaction. It also does not, by itself, establish resignation, adaptive acceptance, fear, or burden avoidance. HXR must investigate the possible explanations rather than converting silence into whichever conclusion an institution or critic prefers.
Universal scope is an obligation to remain open, not a claim of complete knowledge.
HXR may examine every human-made system. That does not mean the current framework already represents every population, culture, disability, domain, objective, burden, or corrective path.
Naming anticipated burden, adaptive acceptance, hidden failure, proxy burden, or unexpressed objective loss makes those experiences visible to the framework. It does not yet establish how often they occur, how people who never enter an intake system will be detected, or how population estimates will be validated.
HXR currently has quantitative principles, not a validated universal quantitative instrument. It can illustrate population-scale consequences and identify requirements for responsible measurement. It does not yet possess a universal formula, settled weighting model, or accepted method for converting every burden into a common unit.
HXR's documentation reflects legal-risk awareness and procedural caution. It has not received comprehensive jurisdiction-specific legal validation. Broader intake, scoring, evidence publication at scale, certification, contributor protections, and institutional findings will require qualified legal review.
HXR is changing rapidly as live case work and reviewer feedback expose what works, what fails, and what needs to exist next. Statements on this page describe today's boundary. They should not be read as promises of imminent capability or as permanent declarations of absence.
Reviewers are invited to point to the next capability, safeguard, test, or domain they believe HXR most needs to earn greater confidence.
Document 42
Document status: Current project record
UXR does not mature all at once. Ethical principles, scientific methods, legal safeguards, operational systems, quantitative tools, and governance structures develop at different rates. This map prevents progress in one dimension from being mistaken for completion in another.
| Dimension | Current state | What completion would require |
|---|---|---|
| Ethical and constitutional foundation | Developed and open for public review | Continued stress testing, transparent revision, and durable governance enforcement |
| Conceptual taxonomy | Extensive and actively evolving | Cross-domain testing, definition stability, and evidence that terms improve analysis |
| Relationship-to-burden architecture | Conceptually developed | Research methods capable of detecting avoidance, adaptation, proxy burden, and unexpressed loss |
| Evidence principles | Defined at a high level and being applied in bounded case work | Broader pilots, provenance procedures, privacy design, confidence methods, correction, and appeal testing |
| Core analytical sequence | Defined and integrated into a bounded live case lifecycle | Broader lifecycle testing across domains, institutions, outcomes, corrections, and verification |
| Operational intake | Bounded contributor-to-case workflow operational; broad public intake not launched | Accessible public intake, safety testing, continuity, privacy controls, staffing, and scalable operations |
| Case data architecture | Operational in a bounded pilot | Broader corpus testing, correction/versioning procedures, governance enforcement, and durability at scale |
| Quantitative measurement | Requirements and cautions identified | Validated baselines, sampling methods, uncertainty reporting, distribution analysis, and reliability testing |
| Human Time Dividend | Developing measurement concept | Defensible baselines, population definitions, uncertainty, distribution, and verified outcome preservation |
| Domain-specific rubrics | Not yet developed | Domain expertise, cross-domain consistency, pilots, and published acceptance tests |
| Blue Score | Not operational | Validated categories, weighting, anti-gaming safeguards, appeals, versioning, and predictive usefulness |
| Case publication | Operational in a limited public pilot | Broader evidence review, institutional response, correction, verification, anonymization, and long-duration monitoring tests |
| Governance enforcement | Principles and commitments documented | Legal structure, appointment rules, disclosures, conflicts controls, succession, and enforceable remedies |
| Legal review | Not completed | Qualified jurisdiction-specific review of operations, publication, privacy, marks, licensing, and certification |
| Protection and provenance | Public notices and internal publication records exist | External archival deposits, repository history, permanent identifiers, registrations, and durable succession controls |
| Pilot validation | Limited real-world case pilot underway; validation not complete | A larger and more varied set of pilots with published failures, corrections, method changes, and reliability evidence |
Several capabilities previously described as planned or conceptual are now operating in bounded form: case architecture, contributor-to-case workflow, public case publication, related-incident grouping, resolution-layer tracking, and a public Cases registry. That is operational progress, not proof of scientific validation.
Developed does not mean beyond criticism. Published does not mean universally validated. Operational in a bounded pilot does not mean mature at scale. Scientific in method does not mean scientifically validated as an instrument.
A mature claim must identify the dimension in which maturity has actually been demonstrated.
The maturity map is a current snapshot. Live case work and reviewer feedback are expected to change it. Reviewers are encouraged to identify dimensions that appear overstated, understated, missing, or sequenced incorrectly.
Live UXR Cases · What UXR Is, What It Is Not, and What Exists Today · Current Project Status · UXR Roadmap
Document 43
A factual orientation to HXR’s Evaluations, supporting Incident Cases and evidence, successful and mixed experiences, human and organizational benefits, and explicit current maturity limits.
Document status: Public orientation brief
This is a factual orientation document, not a press release. It gives journalists, writers, researchers, and reviewers a short path into Human Experience Reform while identifying the claims the current project can and cannot support.
Human-made systems shape how people spend time and attention, understand choices, pursue goals, obtain care or support, and affect what happens next. HXR examines successful, difficult, and mixed experiences to understand how those systems recognize dignity, enable practical agency, and protect or consume human capacity.
Its main public analytical artifacts are Evaluations, supported by bounded Incident Cases and other evidence. Evaluations can document good practice, explain avoidable burden, preserve counterexamples, examine constraints, and track supported change. Recognizing effective practice and improving systems are means toward better human experience.
HXR also examines organizational effects where evidence is available. A practice that helps people may reduce rework or improve resolution for the organization, but those benefits must be established rather than assumed. Human dignity is not conditional on a business return.
Human Experience Reform was founded and developed by Sean Arenas. The current public documentation remains under active review and revision.
About the Founder · Contributing to HXR · Official Source of Truth
Document 44
UXR is being built in public.
You may have expected to find a mature intake institution, a large searchable case database, Blue Scores, or comparison tools. Those systems do not yet exist at scale.
What now exists is more than documentation alone: UXR has a bounded operational case workflow and a public Cases registry with live published case records. The constitutional, governance, scientific, and methodological foundation still comes first because the operating machinery must remain answerable to it.
A public system that receives accusations, evaluates evidence, publishes findings, and may eventually rate institutions needs consistent definitions, correction rights, anti-capture rules, confidence standards, participation safeguards, and transparent limits before it receives broad operational authority.
UXR published those foundations early so researchers, practitioners, critics, organizations, contributors, and affected people could challenge them before they hardened into software, policy, scoring, or institutional power. The current case pilot now tests parts of that architecture against real work.
The current stage is no longer only preparation for evidence. UXR is now using real cases to test how evidence should be bounded, preserved, interpreted, corrected, published, and followed through resolution. That still does not make a small pilot a validated universal instrument.
View the live UXR Cases registry · View the UXR Roadmap · Current Project Status · Complete Reviewer Packet
Document 45
Current stage: founder-led Architectural Build Publication Mode within Private Alpha. HXR accepts a limited number of real-world submissions and uses them to develop and inspect the canonical records, evidence graph, Evaluations, and real public frontend. HXR is still a one-person project, not a staffed agency or mature certification system.
Human Experience Reform is now the active public identity. The August 18, 2026 UXR-to-HXR cutover is complete. The current MAIN Shopify theme includes the verified HXR Home, Documentation, Cases, Incident, Evaluation, support, reviewer, development, and navigation presentation. Legacy UXR-... identifiers, /blogs/uxr routes, and internal uxr_* keys remain intentionally stable.
Intake is not automatic publication. A submission does not automatically become an Incident, Evaluation finding, vote, prevalence claim, or public record. When Sean explicitly authorizes publication of a bounded Case or Evaluation, the ordinary public projection may be completed with privacy, permitted-use, provenance, canonical-linkage, and write/readback safeguards.
UXR-EVAL-0001, UXR-EVAL-0002, and UXR-EVAL-0004, received an August 25 compatibility audit against current HXR field semantics and Evidence Graph rules. Their public/search framing, positive/negative or explicit non-findings, evidence ceilings, unresolved questions, agency dimensions, reform posture, privacy/controls where applicable, and contribution states were brought forward without renumbering legacy IDs or manufacturing new evidence. Their existing public projections were updated and independently read back within the current 40-field Evaluation projection rather than expanding that schema.Shopify Projection ID values were corrected; the mapped corpus now contains 73 unique Notion→Shopify documentation identities with no duplicate projection IDs. One newer document, How Your Contribution Can Matter, legitimately remains without a v2 Projection ID and must be created through the governed publication workflow rather than assigned a guessed ID.UXR-DEV-34 defines the fail-closed re-enable tests. Until those tests pass, governed manual projection with deterministic hashing, exact admin readback, live HTML inspection, legacy Article parity where applicable, and append-only sync logging is the active documentation synchronization path.The contribution pilot is deliberately small. The canonical and public Evaluation projections now contain:
The first two configured pilots are the DMHC timely-access remediation Evaluation and the California health-plan specialist-access Evaluation. Five Amazon bulk-listing Evaluations, HXR-EVAL-0042 through HXR-EVAL-0046, now run an additional bounded manual-email pilot on the live theme. Each exact-symptom Evaluation keeps one Add Your Experience doorway, offers a 10-second prefilled confirmation, and links back to the single Incident hub. The five Evaluations remain separate because their remedies and acceptance tests are independent.
Current intake is human-operated. The secure contribution flow and automated public-to-ledger bridge are not live. A person sends a story or bounded confirmation to Sean/HXR through the available human contact route. Sean or another expressly authorized operator then opens the current intake agent and manually creates or reconciles the private Intake Session, privacy/use state, candidate matches, evidence relationships, and plain-language summary. Intake Sessions now have fields for acknowledgment state, sent time, a private outbound-delivery reference, and the stable receipt reference communicated to the contributor. Those fields make receipt parity structurally available; no real contributor transaction had yet completed acknowledgment plus full canonical readback as of September 2, 2026. The existing Amazon email actions remain non-secure first contact only and should not carry identifiers, confidential material, or sensitive evidence. This manual process does not promise publication, automatic notifications, an organization response, or a particular outcome.
Organization responses use an adopted manual bridge with a separate ledger. A representative's message is transport until an authorized operator preserves the original received time and payload, creates or reconciles the private HXR-RESP-N record, applies private defaults, records authority and granular permissions, assigns append-only claim labels and dated dispositions, sends a separate stable-reference acknowledgment, and reads back the transaction. The necessary fields and procedure are structurally available, but a real organization-response transaction had not yet completed that acknowledgment and full canonical readback as of September 2, 2026. The public form is not a secure evidence portal or automatic receipt. All service times are capacity-qualified, good-faith, noncontractual targets. For target calculation, a business day is Monday through Friday excluding U.S. federal holidays, measured in Pacific Time; a message received after 5:00 p.m. Pacific Time is treated as received on the next business day.
The healthcare domain has completed a full canonical reconciliation against the current Workbench and Evidence Graph. The July 29–August 6 cardiology sequence is now represented as one active bounded Incident rather than several mechanism-level child Incidents. Three former cardiology mechanism slices are retired for historical continuity, while one distinct Covered California enrollment/remedy occurrence remains separate because its objective is different.
Seven healthcare Evaluations remain in Active Evidence Collection and receive evidence-specific contribution edges from those two bounded occurrences. This lets the same cardiology occurrence partially support, narrow, contextualize, or support different functional Evaluations without being counted as several independent incidents. Only the California health-plan timely-access Evaluation and the DMHC remediation Evaluation are configured as the two Phase 1 contribution pilots; the other five remain Not Configured.
The healthcare audit also formalized seven Evidence Items, controlled-function attribution, explicit non-findings, unresolved questions, and acceptance tests. Public healthcare projections were synchronized to the canonical model, including removal from public presentation of the retired cardiology mechanism slices. This domain pass did not change the shared Add Your Experience, intake, attachment, matching, portal, notification, or Impact Receipt architecture.
Shopify's public Evaluation definition is at its 40-field maximum. The three approved contribution fields fit. Material Unresolved Questions does not fit as an additional field without deleting or redesigning an existing projection field. For the two healthcare pilot records only, the theme projects the exact canonical unresolved-question text through a clearly marked mapping. The five Amazon manual-email pilots use only the three approved contribution fields and do not extend that fallback. The unresolved-question mapping must not be generalized without a separate reconciliation decision.
HXR-RESP-N acknowledgment, authority scope, granular permissions, append-only claim review, reconsideration, conflict controls, and readback.UXR-DEV-34 passes. Process any authorized canonical delta through governed manual projection with deterministic hashing, exact admin readback, live HTML inspection, legacy Article parity where applicable, and append-only sync logging. Do not infer full body synchronization from the earlier 17 title/summary-only corrections.The first 12-fixture manual regression baseline produced eight passes and four failures. It was single-grader, self-graded, sequential, and did not place an executable publication broker in the decision path. HXR froze v1 before remediation, added candidate/source-resolution records, adopted a no-manufactured-attribution invariant, made linked result rows authoritative, added idempotent write identity, and drafted successor coverage.
Broker enforcement, automated scoring, mature formal release control, broad public intake, automated matching, subscriptions, notifications, portals, and a persistent Contribution Impact Receipt remain development work. They are not prerequisites for ordinary founder-authorized frontend iterations, and none should be built merely because it sounds useful.
Document 46
Share a good, difficult or mixed experience, help HXR understand what enabled it, or add evidence to an Evaluation. HXR’s limited Private Alpha intake is manual, and publication requires a separate review.
HXR 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.
Share an Experience with HXR is the public starting point. Its button opens an external Jotform form that sends your account to an HXR operator by email for human review. A short account is enough; non-sensitive supporting files are optional. Sending the form does not automatically create an HXR record, publish anything, or contact the organization. You can add to an existing Evaluation or describe a new topic without deciding how HXR should classify it.
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 HXR also wants to identify practices that preserve agency and deserve replication.
Evaluations are the main analytical records these contributions can help build. A bounded Case may preserve what happened in one experience; an Evaluation brings relevant Cases and other evidence together to examine a practice or question over time. Your contribution may help recognize something worth preserving, explain an improvement, identify a limit, or change an earlier finding.
Outside sandboxed regression testing, HXR 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.
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.
You do not need to prepare a complete narrative or upload a folder of evidence before your experience can matter. Different contribution levels add different kinds of knowledge.
Current pilot: HXR uses one human doorway rather than asking people to choose from a menu of record types. Send your story to Sean/HXR in ordinary language. Sean or another expressly authorized operator will then open the current intake agent and manually create or reconcile the private Intake Session, privacy/use state, candidate record relationships, and any supported evidence links. The public contact step does not automate this handoff and is not a secure evidence portal. HXR should do the classification work behind the scenes and ask only the smallest useful follow-up. The public submission form provides access to this human review process; it does not automate the canonical intake handoff. Further automation should be added only when real use establishes a need.
Examples of what a contribution may contain:
A one-tap signal is not a vote. A screenshot does not prove every interpretation. A counterexample can be as valuable as a matching incident because it may prevent HXR from overstating the evidence.
A contribution should not become a one-way transfer of personal effort into an invisible queue. Depending on the evidence, authorization, relevance, and current Private Alpha capacity, a contribution may:
HXR cannot promise that submitting an incident will produce the person's immediate objective. It can build the structure that makes the effort cumulative, visible where authorized, and reusable instead of allowing it to disappear.
See how an HXR contribution differs from an ordinary complaint or grievance.
HXR's intended contributor experience includes a clear Contribution Impact Receipt. During the current manual pilot, HXR will use the existing Intake Session rather than build a separate receipt system. Intake Sessions now have fields for acknowledgment state, sent time, a private outbound-delivery reference, and the stable receipt reference communicated to the contributor. The adopted procedure requires the manual acknowledgment to state the stable Intake Session ID, original received time, privacy/use defaults, what HXR recorded, and the next step. This creates structural and intended parity with organization-response receipt handling, but no real contributor transaction had yet completed acknowledgment plus full canonical readback as of September 2, 2026. HXR's capacity-qualified target is to preserve and acknowledge contributor intake within 2 business days after receipt; it is a good-faith, noncontractual target, not a guarantee or a promise of publication, organization response, remedy, or outcome. For target calculation, a business day is Monday through Friday excluding U.S. federal holidays, measured in Pacific Time; a message received after 5:00 p.m. Pacific Time is treated as received on the next business day. The accompanying plain-language summary should show whether the material remains private or anonymized, which Incident Case or Evaluation it may connect to, what it may add, and what it cannot establish alone.
A separate persistent receipt, automatic updates, and contributor portal should be built only if real use shows that the simpler summary is insufficient. The purpose remains the same: demonstrate that the contribution entered a consequential pathway rather than an invisible queue.
After initial intake, a contributor may use the same human doorway to correct or clarify the account, supply later evidence or counterevidence, change a privacy or publication permission where the governing record permits, report whether a remedy was offered or completed, raise retaliation or unwanted-contact concerns, request reconsideration, and ask for an updated plain-language summary. You do not have to contact the organization, negotiate publicly, disclose sensitive information, or rebut every organization statement. When safety and privacy permit, HXR should give you reasonable notice before a material public change based on an organization response.
A documented organization response may add acknowledgment, correction, explanation, remedy, or reform. HXR reviews it claim by claim and preserves the contributor account, organization position, primary evidence, and HXR analysis as distinct sources. Neither the organization nor the contributor can buy or command a finding. A documented nonresponse after governed HXR notice, verified delivery, and the applicable response period is a response-state worth preserving, but silence does not automatically prove guilt, agreement, indifference, motive, or inability to reform.
HXR is unfinished. Categories, schemas, analytical methods, and intake behavior may change as testing finds defects. The first manual regression baseline failed overall, and HXR is publishing that fact while keeping the answer key private. The project does not claim that its executable broker has been validated.
HXR 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 HXR's governing center.
Document 47
Skepticism is appropriate for any project that proposes to collect evidence, publish findings, rate institutions, or influence public choices.
UXR should not ask for trust without inspection.
UXR is an early-stage public-interest framework under construction with a bounded public case pilot now operating. It has no employees, investors, managers, staffed broad public intake service, or operational Blue Score system.
Its published work now includes constitutional, governance, methodological, taxonomic, example, onboarding, and public case records. The live Cases registry provides a place to inspect how some of the framework behaves when applied to real incidents.
Independence and the One-Way Authority Rule
Evidence Validation and Confidence
Participation Integrity and Anti-Brigading
Identify contradictions, unsupported assumptions, hidden political commitments, governance weaknesses, excluded populations, measurement incentives, places where a public case overreaches its evidence, and ways UXR could reproduce the burdens it intends to examine.
The project is moving quickly. Reviewers are also invited to identify which missing capability, safeguard, test, or domain should receive priority next.
Document 48
There are no operational UXR Blue Scores or company rankings yet.
UXR is still building the evidence, methodology, governance, domain rubrics, and validation needed before a public score can responsibly influence decisions.
UXR has now published the first formal working draft of its scoring architecture. It explores candidate agency-balance dimensions, Constraint Provenance, partial reform recognition, score profiles, anti-gaming safeguards, and the questions that must be answered before any composite score can be treated as valid.
Read the UXR Scoring Architecture Working Draft
A responsible comparison system needs validated measures, current evidence, domain-specific interpretation, confidence and uncertainty, anti-gaming safeguards, correction rights, institutional response, verified reform history, affected-person review, pilot testing, and adversarial testing.
When UXR reaches that stage, a score should never stand alone. Readers should be able to inspect what was measured and why.
Current status: formal scoring architecture development and public review.
View Current Project Status · Read the Complete Reviewer Packet
Document 49
This roadmap explains what UXR is building, what is already operating in bounded form, what has been published for criticism, and what remains non-operational.
Status labels describe development state, not final truth. Published for Review means the material exists publicly and remains open to revision. Active Pilot means a bounded capability is being used in real case work without implying large-scale validation.
Status: Published for Review
Purpose, human agency, universal scope, civilizational stewardship, burden transfer, accountability, and independence.
Status: Under Active Revision
Taxonomy, examples, audience doorways, and plain-language explanations continue to change as reviewers and live cases expose ambiguity.
Status: Active
Invite criticism, domain knowledge, lived experience, organizational perspective, scientific review, governance analysis, and direct examination of the public case pilot.
Status: Exploration Required
Identify lawful and independence-preserving funding paths, governance structures, staffing needs, partnerships, and operational safeguards.
Status: Partially Operational / Under Development
A bounded contributor-to-case workflow now exists and has produced live public cases. Broad self-service public intake, staffing, mature privacy controls, and large-scale continuity infrastructure do not yet exist.
Status: Active Pilot
Bounded cases are now being developed and published with evidence boundaries, independent resolution layers, related-incident structure, case updates, and reform tracking. Institutional response, correction, escalation, verification, and long-duration monitoring still require broader testing.
Status: Research Stage
Develop category measures, anti-gaming safeguards, confidence display, appeals, versioning, and public comparison tools. No operational Blue Score is currently issued.
Status: Limited Pilot Underway
UXR is now testing real case architecture and publication through a bounded public case pilot. The purpose is to expose failures in the method, publication model, routing, status tracking, and reform lifecycle before broad deployment.
A working case registry does not establish that UXR has a validated universal scoring instrument, a representative evidence corpus, a mature intake institution, or a scientifically validated measurement system. The pilot proves that some previously planned machinery now exists and can be tested.
This roadmap is intended to change as the project changes. If a reviewer sees a capability, safeguard, test, or domain that should move forward sooner, UXR wants that criticism.
View the live UXR Cases registry · Contributing to UXR · Current Project Status
Document 50
Document status: Living historical record
First published: August 4, 2026
Substantively updated: August 10, 2026
Maintained by: UXR
This page preserves the public lineage of User Experience Reform. It records how the framework developed, which ideas entered the constitutional core, and when major public milestones occurred. It is not a marketing narrative and should not be rewritten to create a cleaner origin story than the evidence supports.
UXR did not begin with one incident. Its formal framework emerged in 2026, but the founder describes its roots as cumulative: decades of noticing unnecessary difficulty, helping people navigate software and institutions, reporting visible problems, and asking why correctable burdens can remain in place long after people recognize them.
One early question came from childhood observations of ordinary hazards and neglected public conditions: Everybody can see that this is broken. Why is it still broken? The long-term significance was not any one sidewalk, obstruction, or maintenance issue. It was the gap between noticing a problem, spending effort to report it, and having a credible reason to believe that the effort would produce correction.
In the 1990s, the founder developed another framing that later became important to UXR: games deliberately place obstacles between people and objectives because overcoming those obstacles is part of the experience. Tools should do the opposite.
“Games deliberately put obstacles between a person and their objective. Tools are supposed to do the opposite.”
That distinction shifted attention away from whether individual software features technically worked and toward whether a person could accomplish an ordinary goal without having to solve the architecture first.
The founder's account includes software development, documentation, training, telephone technical support, field support, internal support, network and software maintenance, and direct work with users and developers, including roles involving Phoenix Technologies, Hewlett-Packard, and Ralph M. Parsons.
Across those settings, a recurring problem appeared: users were often required to understand product structure, departmental boundaries, configuration details, or specialist vocabulary in order to accomplish goals that the tool or institution was supposed to support.
That observation later generalized beyond software. Healthcare, insurance, banking, government, transportation, commerce, property administration, customer support, physical infrastructure, and other systems can impose the same kind of architecture-learning burden.
The emerging idea did not require a theory of malicious institutions. A system can create a bad aggregate outcome from individually defensible local choices. One department optimizes a workflow. One policy reduces organizational risk. One vendor selects a specialized standard. One team builds a boundary around its own function. The resulting time, coordination, compatibility work, uncertainty, or correction burden may then be transferred to the person trying to accomplish a goal.
This became a foundational UXR habit: do not stop at “this was frustrating.” Ask what the person was trying to accomplish, what the system did, which burdens were necessary, which were transferred, who controlled them, who bore them, what evidence supports each explanation, and what a durable correction would need to demonstrate.
Repeated reporting experiences produced another concern: systems can teach people not to participate even without intending to do so. A person notices a problem, believes reporting might matter, spends effort, sees the effort disappear without visible learning or correction, and becomes less willing to spend the same effort next time.
UXR began distinguishing formal agency from practical agency. A complaint form, phone number, or appeal route does not by itself establish meaningful agency. The person needs a credible relationship between action and consequential outcome.
This also created a requirement for UXR itself: reporting unnecessary burden should not itself require unnecessary burden. Case records, matching experiences, preserved evidence, subscriptions, organization responses, workarounds, reform criteria, and verification are intended to carry institutional memory forward so that each person does not have to restart the problem from zero.
The founder summarized his reason for continuing to pursue problems even when the individual return on time is poor:
“I don’t view my fight as an individual fight. I view it as a fight for everyone.”
This moved UXR toward a public-goods model. One person may bear the cost of discovering and reporting a failure while many people could benefit from the eventual reform. UXR therefore aims to convert isolated effort into shared infrastructure: one experience can become a case; matching experiences can accumulate; evidence and organization responses can persist; a workaround can become reusable; and a demonstrated reform can help future users and other institutions.
During the formal development period, UXR identified recurring patterns in which institutions reduced their own visible costs without necessarily removing those costs from the world. Time and coordination could move downstream. So could recordkeeping, interpretation, uncertainty, risk, and error correction.
Those observations developed into concepts including Human Externalities, Invisible Taxes, Burden Transfer, and Extractive Burden Transfer. The project also formalized the contributor's objective, system component, failure mechanism, causal sequence, responsible function, resulting harm, corrective path, and evidence supporting each claim. This moved UXR from a collection of complaints toward a case-based diagnostic discipline.
UXR increasingly centered Human Agency as a governing outcome. Earlier language described the practical ability to understand, choose, act, recover, and contest within a system. Later development clarified the causal relationship underneath those capabilities: agency concerns whether a person's will, choices, evidence, or actions have a meaningful possibility of affecting what happens next. Understanding, choice, action, contestability, correction, recovery, and alternatives support agency because they preserve consequential participation; they do not guarantee the preferred outcome.
Civilizational Stewardship followed from the recognition that human resources are finite. Time, attention, understanding, dignity, health, safety, opportunity, fuel, battery life, physical effort, memory, and emotional capacity do not become free inputs merely because conventional organizational accounting does not record them.
The developing research now proposes that reform may return multiple forms of human capacity, including Human Time, Capacity, Agency, Attention, Emotional, Memory, Trust, Care, Resource, Economic, Public Revenue, Health, Civic, Dignity, Reform, and Propagation dividends. These remain research hypotheses rather than assumed findings. UXR's intended method is to publish the proposal, explain the mechanism, identify measures and confounders, invite academic and practitioner criticism, and state what would strengthen, weaken, or falsify it.
UXR developed around an unequal starting position. Institutions generally possess continuity, records, staff, procedures, automation, legal resources, and accumulated knowledge. Individuals usually have one problem and finite time, health, attention, money, patience, and emotional capacity.
The project therefore aims to provide leverage rather than demand that people fight harder. At the same time, it rejects the idea that every institution must become an enemy. Organizations should be able to use UXR findings to discover recurring friction, improve systems, demonstrate reform, receive deserved credit, and give other organizations successful patterns to copy.
The desired incentive structure is one in which the most advantageous way to improve a UXR result is to improve the human outcome.
As UXR developed toward scoring, certification, consulting, and institutional adoption, the project identified a central danger: the organizations being measured could attempt to influence what the standards mean.
The One-Way Authority Rule was created to prevent that reversal. Information, standards, and public findings may flow downstream into services that help organizations improve. Money, access, or commercial relationships may not flow upstream to change definitions, scores, evidence, case outcomes, priorities, or public standards.
This makes institutional participation compatible with independence. An institution may change its result by changing what it does. It may not purchase control over the ruler.
UXR's documentation was published publicly before live scoring, automated intake, or certification existed. This created a period in which constitutional and scientific architecture could receive scrutiny before operational incentives hardened around it.
The public site established project-status boundaries. UXR did not claim that unfinished scoring models, intake automation, certification, or broad validation already existed merely because they appeared on the roadmap.
Public and perspective-based reviews repeatedly revealed that readers associated “user experience” with software, websites, applications, and machine interfaces.
The documentation was revised to state explicitly that UXR studies every form of human interaction with human-made systems. Those systems may be physical, legal, administrative, organizational, economic, institutional, digital, or combinations of several forms.
UXR developed a clearer sequence separating observation, explanation, inference, hypothesis, and evaluation. The framework committed to evidence validation, confidence statements, causal humility, human-readable inference trails, and explicit unresolved questions.
UXR also clarified that it is scientific in method and ambition while remaining a developing framework. A public commitment to measurement does not make an unfinished method scientifically validated.
The framework formalized the principle that responsibility should scale with capability. Institutions commonly possess greater information and continuity than the individuals who depend on them. They also command more staffing, authority, automation, legal support, and redesign capacity.
One continuing design direction is information symmetry. If an institution records a call, chat, email, decision trail, or account interaction, giving the person meaningful access to that record can reduce avoidable memory and evidence asymmetry. Future systems could allow user-side AI to extract appointments, commitments, next steps, disputed statements, and preparation requirements from shared records, reducing the need for people to take defensive notes or reconstruct institutional memory by hand.
UXR began testing its documentation through deliberately varied interpretive lenses. The method became known as Interpretive Stress Testing.
The purpose is not to treat any perspective as gospel. A lens may recover a principle accurately, expose an ambiguity, import a prior ideology, or mistake every object for the kind of object it already knows how to strike. UXR records those differences instead of automatically rewriting the framework around each reaction.
On August 4, 2026, UXR published a formal provenance and project-protection structure. It established founder attribution, copyright and reuse guidance, brand and canonical-source rules, a constitutional integrity pledge, a research notebook and central changelog, and public roadmaps for archival repositories, licensing, trademarks, certification marks, registries, and future stewardship.
UXR moved from planning case architecture to operating a bounded case system. Structured Shopify records were created for intake, case-boundary decisions, case records, evidence, assessments, activities, resolutions, public records, taxonomy assignments, routing, publication composition, and related operational functions.
The project then published its first public case registry. The cardiology incident became an important architectural test because UXR did not compress an entire contributor narrative into one complaint. It separated distinct failure mechanisms into independently trackable cases while preserving their relationship to one shared incident. This allowed one responsible function to resolve its own failure without requiring unrelated failures elsewhere in the incident to close at the same time.
Public case records also began exposing separate resolution layers for immediate remediation, individual remedy, system reform, verification, and monitoring. The Cases index gained search, filtering, failure-domain and agency-dimension presentation, related-incident context, and mobile-specific refinement.
UXR increasingly separated stable documentation from mutable project state. Public documents were linked to canonical Feature records, and meaningful changes could be recorded as Development Events. The intended architecture became Document → Feature → Development Events so that status, authority, current functionality, limitations, and development history did not need to be duplicated inconsistently across multiple pages.
On August 8, UXR launched a public Development hub and searchable Feature registry with feature detail pages, changelog access, roadmap and current-status surfaces, and direct access to project support. This made the project's unfinished state more inspectable rather than hiding development behind finished-sounding documentation.
UXR added Goal-Oriented Documentation as a proposed design and evaluation principle. The distinction is simple: a feature manual explains how a function works; a goals manual explains how a person accomplishes an objective.
Writing the goals manual can become an architectural friction test. If the path to an ordinary goal requires unnecessary handoffs, duplicated actions, workarounds, prerequisite knowledge, or navigation across internal product boundaries, the documentation exposes that burden. The proposed reform cycle is: identify the human goal, document the current path, identify unnecessary friction, reform the system, document the improved path, and repeat.
The project's working “Blue Zone” terminology for future positive-system recognition remains provisional and is expected to be renamed. The underlying principles are intentionally stored independently of that label so terminology can change without changing the method.
UXR opened a public case after an originating Zelle experience in which the sender reportedly lost access to transferred funds immediately while the recipient still lacked usable funds and pending visibility days later. Rather than generalize one experience into a claim about all banking, UXR preserved the narrow transfer case and created a broader internal research inquiry: Asymmetric Control of Consumer Funds Availability.
The parent inquiry can connect future cases involving refund restoration, authorization holds and releases, ACH pathways, deposit availability, and other mechanisms. Those mechanisms should remain separate cases when their causal sequence, responsible function, evidence, harm, or acceptance test differs. Substantially similar transfer experiences can attach to the existing case; materially different mechanisms can support or challenge the larger theory without inflating the original case's recurrence count.
The case also formalized a distinction between comparative capability evidence and direct recurrence evidence. A weekend debit-card transaction that promptly reduces available purchasing power can motivate the question of why incoming restoration follows different timing rules, but it does not by itself prove that the same technical rail could have produced an instant incoming credit.
To preserve that reasoning across future project threads, UXR created internal Case Stewardship Notes and Case Family / Research Inquiry records. These records communicate case boundaries, matching rules, related-case rules, evidence guardrails, hypothesis guardrails, and explicit “do not” instructions without consuming public case fields or exposing internal continuity notes as public findings.
Founder review during this period surfaced another requirement: UXR could remain ethical, rigorous, and technically sound yet still fail if ordinary people do not understand it or use it.
UXR therefore treats comprehensibility as more than presentation polish. A person should be able to recognize a case, say that the same thing happened to them, learn a workaround, follow reform, or understand what is being requested without first mastering the entire UXR taxonomy or governance model. The rigor belongs underneath the interaction.
UXR's intended future is not a complaint engine. Necessary friction should remain when it serves legitimate purposes. Excellent systems and successful reforms should also become visible, preservable, and reusable.
The emerging long-term cycle is: burden → understand → reform → verify → preserve what worked → propagate → reduce recurrence. A mature UXR record should contain not only what failed, but what demonstrably worked and what other institutions can learn from it.
Further founder review sharpened UXR's definition of Human Agency. Earlier language emphasized the practical ability to understand, choose, act, recover, and contest. The framework now places the causal relationship underneath those capabilities at the center: human agency concerns whether a person's will, choices, evidence, or actions have a meaningful possibility of affecting what happens next. The revision explicitly distinguishes agency from control or guaranteed success and identifies formal participation without consequential effect as a possible agency failure.
This clarification also strengthened the concept of learned nonparticipation. Repeated opportunities to report, appeal, or act can still teach people that participation is futile when those actions repeatedly enter causal dead ends. UXR's continuity architecture therefore gained a deeper purpose: preserve the consequential potential of human action so reports, evidence, responses, responsibility changes, reforms, and verification do not simply disappear.
The framework also developed a clearer distinction between physical constraint and human contingency. Human-made systems may impose necessary limits, but their laws, policies, workflows, architectures, contracts, and conventions remain eligible for evidence, explanation, reconsideration, and reform through legitimate human processes. A developing Constraint Provenance method asks what actually produces a claimed “cannot” and at what layer corrective authority exists.
Responsibility analysis expanded from asking which organization should receive a case to resolving which responsibilities belong where. Multi-party systems may distribute mechanism, control, policy, coordination, disclosure, remedy, and governance responsibilities across different actors. An organization's claim that a failure is “not us” should therefore become a testable attribution claim. Supported reattribution can remove unsupported blame while preserving separate responsibilities for handoff, disclosure, coordination, or remedy.
This work also identified responsibility navigation as a human burden in its own right. A patient, customer, worker, or resident should not have to reconstruct institutional architecture merely to locate the part of the system capable of acting. If multiple sophisticated institutions cannot identify where corrective authority lies, the gap may itself indicate a governance defect.
UXR's developing comparison philosophy also became clearer. Benchmarking is not being adopted as an identity objective. It is expected to emerge as a consequence of rigorous, comparable public evidence and verified reform. Public comparisons should be contestable through evidence rather than consent-dependent, and institutions should receive a meaningful right of evidentiary response without a right to approve the measurement. Peer comparison and cross-domain comparative capability were distinguished, with the explicit rule that analogy can generate a question without proving technical equivalence.
Finally, reform propagation moved closer to a stewardship obligation. If UXR possesses validated knowledge of a better method, the project should try to make that knowledge discoverable, understandable, comparable, reproducible, citable, and reusable. As UXR's own capability and consequential influence grow, its responsibilities must scale by the same principle it applies to other institutions.
A live consumer funds-transfer case became an operational stress test of UXR's ability to document actual harm. As the contributor supplied additional chronology, corrections, screenshots, institutional explanations, and review feedback, the case exposed weaknesses not only in the financial system being studied but in UXR's own evidence language and publication habits.
One correction clarified that a later interpersonal loan was not unrelated background assistance: it was provided specifically because the expected transfer had not arrived and the recipient account remained negative. Correcting that causal relationship strengthened the harm analysis and demonstrated why case records must remain corrigible as contributors add information.
The same work exposed a methodological problem in how evidentiary provenance was being described. Repeated phrases such as “unverified” or “awaiting verification” could make contributor testimony sound presumptively suspect even when UXR had no actual reason to doubt it. UXR revised its evidence and intake guidance around a simpler rule: testimony is evidence, and provenance should add information without subtracting dignity. “The contributor reports…” identifies the source. Screenshots, forwarded messages, transcripts, and other artifacts add support when available.
Casework also clarified that the public case and the internal audit trail should not serve the same purpose. UXR now distinguishes three layers: the original contributor account, preserved faithfully; an internal evidentiary working record that preserves provenance, supplements, superseded details, and material conflicts; and a public case that is continuously rewritten to present the strongest current evidentiary account. When later evidence establishes a better-supported ordinary detail, the public case should normally use that fact and remove the obsolete version rather than publicly catalog the contributor's memory error. A discrepancy remains public when the discrepancy itself materially affects the finding or fair interpretation of the evidence.
This produced a broader operational principle: the public case should read as though the case manager had all current evidence available when writing it from scratch. Evidence can strengthen or weaken a case, and UXR should follow it in either direction without making contributors pay a reputational penalty for helping improve the record.
The development process itself is now part of UXR's public record. Real casework is not merely using the framework; it is testing whether the framework can actually document harm with enough accuracy, dignity, causal discipline, privacy, and usefulness to support later research and reform. When a case exposes a durable methodological weakness, UXR intends to record the resulting change in its documentation and Development Events. The changelog can therefore show how the system matures through contact with real cases instead of presenting a polished fiction that the method arrived fully formed.
UXR moved from documenting the framework in public, to engineering and testing it in public, to accepting a limited number of real-world submissions in Private Alpha. Submissions may be serious or casual, positive or negative. Private intake remains separate from public publication, which continues to require privacy, provenance, release, and human-review controls.
The first 12-fixture manual baseline produced eight passes and four failures, so the suite failed overall. The run was manual, single-grader, self-graded, and sequential. It tested prompt-layer model compliance with production schemas and instructions; no executable publication broker was in the decision path. UXR therefore does not claim that broker enforcement has been validated.
The baseline exposed a repeated attribution defect. UXR froze the exact v1 specification before remediation, recovered two transcript-only results into the authoritative ledger with their limitations recorded, added a fail-closed candidate/source-resolution stage, adopted a no-manufactured-attribution invariant, made linked countable result rows authoritative over stored count snapshots, added idempotent attempt/write identity, and drafted successor coverage without changing frozen v1.
Detailed scenarios, acceptance criteria, prohibited constructions, and document-to-test mappings remain internal. The public milestone is the existence of a versioned integrity-testing process that records failures and drives architecture changes, not disclosure of the answer key or a claim of validation.
This work has been carried out without a formal programming team, board of directors, or dedicated UXR domain. The constraint is part of the development record, while the invitation is practical: programmers, reviewers, journalists, researchers, designers, privacy specialists, domain experts, and other applicable contributors can help test and build the next stage.
Future history entries will document substantive changes rather than every copy edit. Major releases should eventually receive external archival timestamps, repository history, and permanent identifiers. Research proposals should become easier for academics, practitioners, institutions, and the public to challenge with sources, measurement methods, counterexamples, and falsification tests. When a public versioning system exists, this history will link to it rather than replace it.
Copyright © 2026 Sean Arenas. User Experience Reform (UXR). All rights reserved. This historical record may be cited with attribution.
Document 51
Document status: Living development notebook
First published: August 4, 2026
Current identity: Human Experience Reform (HXR)
Authority level: Development record, not constitutional authority
The HXR Research Notebook records significant discoveries, questions, rejected assumptions, and methodological changes while the framework develops.
Notebook entries do not become official HXR doctrine merely because they appear here. A notebook entry may describe a hypothesis, working term, communication discovery, unresolved conflict, or proposal that later changes or is rejected. Formal authority remains with the current constitutional and methodological documents.
Entries dated before August 18, 2026 may use User Experience Reform (UXR) because that was the project's public name when those discoveries were recorded. Those references are preserved as historical language rather than silently rewritten.
Different people recognize system burden differently. One person may spend hours challenging an outcome. Another may accept the first result because prior experience makes correction appear exhausting, uncertain, or pointless.
Discovery: complaint volume and self-reported frustration do not directly measure burden. A system may appear frictionless because people have learned not to ask it for outcomes they expect will be difficult to obtain.
Working concepts: Anticipated Burden, Burden Avoidance, Adaptive Acceptance, and Unexpressed Objective Loss.
People who actively resist a system recognize themselves in stories about long phone calls, repeated escalation, and administrative struggle. Other people recognize delayed care, an unrepaired device, a missed appointment, or an accepted answer that should never have been final.
Decision: UXR onboarding should include active resistance, passive constraint, hidden failure, and proxy burden.
“One minute per person per day” can be misunderstood as one minute taken from every person every day.
Decision: describe population-level estimates as averages across people and time. Publish the distribution, concentration, population, period, baseline, assumptions, and uncertainty whenever possible.
A broken workflow can consume customer time and paid institutional labor simultaneously through repeat contacts, transfers, rework, queue pressure, and unresolved outcomes.
Discovery: Shared Inefficiency is a necessary companion to Shared Efficiency and Extractive Burden Transfer.
Working measures: Contact Time, Total Resolution Time, Repeat-Contact Burden, and Resolution Yield.
Traffic signal timing demonstrated that one delay can produce additional fuel use, emissions, braking, acceleration, vehicle wear, road wear, attention demands, maintenance costs, and reliability effects.
Working concept: Burden Cascade.
Decision: UXR should examine repetition scale and cascading scale separately.
Time is intuitive, finite, measurable, and aggregatable. It cannot replace health, safety, dignity, access, opportunity, environmental effects, recovery, or practical agency.
Decision: pair Human Time with Human Outcome in public onboarding.
Perspective reviews and public-documentation work showed that different audiences recognize UXR through different values and professional habits. Researchers look for truth and testability. Journalists look for provable public evidence. Auditors look for repeatable failure detection. Operations specialists see transferred work. Clinicians see delayed care and administrative harm. Public-interest readers see practical freedom and dignity.
Discovery: UXR should remain one framework while offering multiple accurate entrance ramps. Communication may adapt to the audience without changing the underlying standard.
Multiple independent reviews initially described UXR as a framework for software, technology, applications, or machine interfaces, even when their later analysis covered healthcare, government, courts, organizations, and physical systems.
Decision: revise the opening documentation to state immediately that UXR examines all human-made systems.
A recurring principle emerged across very different perspectives: institutions are stronger than individuals in the dimensions that matter for administration. They possess records, continuity, staff, automation, legal resources, authority, and redesign capacity.
Decision: formalize the principle that responsibility should scale with capability.
Character and perspective reviews became useful only when UXR stopped treating them as endorsements or authoritative readings. A perspective may identify a real defect, reveal a communication problem, or simply impose its existing worldview.
Decision: distinguish correctly recovered principles, communication discoveries, reasonable misunderstandings, documentation ambiguities, framework proposals, lens-imposed conclusions, and character-specific rhetoric.
Live cardiology-referral analysis demonstrated that one contributor narrative can contain multiple failure mechanisms with different responsible functions, harms, corrective paths, and resolution timelines.
Decision: case boundaries should preserve independent accountability. Related cases may remain grouped under one incident without forcing every failure to stay open until every other failure resolves.
UXR created structured operational records for intake, boundary decisions, work orders, cases, evidence, assessment, activity, resolution, public publication, taxonomy, routing, and related functions.
Decision: describe this capability as a bounded operational case pilot. Do not continue describing case architecture and publication as merely planned, but do not confuse a working pilot with broad public intake or validated large-scale operations.
Interpretive stress tests continued to criticize UXR for lacking live cases even after public cases existed. The criticism was no longer primarily about missing capability; it revealed that project-status documents had fallen behind the actual implementation.
Decision: current-status, roadmap, maturity, and reviewer-facing materials should draw from live operational data where practical. A project that changes quickly needs status surfaces designed to change with it.
Repeated interpretive reviews naturally centered the Human Time Dividend because time is intuitive and measurable. That created a risk that readers would misread UXR as a time-and-motion or efficiency framework.
Discovery: time can function as observable evidence of a deeper loss without becoming the purpose of reform. Agency, dignity, safety, understanding, opportunity, and human capacity remain core outcomes.
Working framing: time is one visible footprint of what a system consumed; the framework must preserve the distinction between measurable cost and human outcome.
Copyright © 2026 Sean Arenas. Human Experience Reform (HXR). All rights reserved. Notebook entries may be cited with attribution but should not be represented as final HXR standards unless incorporated into an authoritative document.
Document 52
Document status: Official UXR provenance and founder narrative
First published: August 4, 2026
Substantively expanded: August 9, 2026
Founder and creator: Sean Arenas
Founder attribution establishes provenance, but a name and résumé do not explain why User Experience Reform exists. UXR grew from a much older question about human-made systems: why do obvious, correctable burdens remain in place even when the people experiencing them and the institutions operating them can see that something is wrong?
There is no single dramatic origin story. Arenas describes UXR as the cumulative result of decades spent noticing unnecessary difficulty, helping people navigate systems, reporting problems, watching some problems persist, and asking what would let one person's effort become useful to everyone who encounters the same burden later.
Long before UXR had a name, Arenas recalls noticing ordinary problems that remained visible for days, months, or years: a sidewalk hazard, vegetation narrowing a path, a vehicle blocking a pedestrian route, or public equipment left in a visibly deteriorated state. The important observation was not that every example caused major harm. It was that people could notice a correctable problem and still lack a practical path by which noticing it reliably caused correction.
The question became: Everybody can see that this is broken. Why is it still broken?
That question eventually grew into a distinction UXR now treats as central: a formal complaint channel is not the same thing as practical agency. Practical agency requires a credible relationship between a person's action and a consequential outcome.
In the 1990s, another distinction sharpened the idea. Games deliberately create obstacles, puzzles, and constraints between a player and an objective. That difficulty is part of the product. A tool has the opposite job.
“Games deliberately put obstacles between a person and their objective. Tools are supposed to do the opposite.”
If software exists to help a person accomplish something, why should an ordinary goal feel like solving a puzzle? That question became one of the earliest conceptual roots of UXR's goal-centered approach.
It also explains a later UXR proposal, Goal-Oriented Documentation. A feature manual explains what a function does. A goals manual asks how a person actually achieves an objective from beginning to end. Writing the second kind of manual can expose friction that the first kind leaves invisible: handoffs, duplicated steps, prerequisite knowledge, workarounds, subsystem boundaries, and recovery burdens.
Arenas's account of his professional background spans software development, documentation, training, telephone technical support, field support, internal support, network and software maintenance, and direct work with users and developers. That work included roles involving Phoenix Technologies, Hewlett-Packard, and Ralph M. Parsons, along with years of teaching people how to use software and writing instructional material.
The recurring lesson was not that users were incapable of learning systems. It was that ordinary people were repeatedly required to learn system architecture in order to accomplish goals that should not have required that knowledge.
UXR later generalized that lesson beyond software. The same burden can appear in healthcare, banking, insurance, government, transportation, commerce, property administration, physical infrastructure, and other human-made systems.
UXR was not built on the assumption that every bad experience results from malicious intent. Many burdens can emerge from locally defensible decisions. One department optimizes its workflow. One vendor adopts a specialized standard. One policy reduces one organization's risk. One software team builds a boundary around its own component. Each choice may have an explanation while their combined effect transfers time, coordination, uncertainty, compatibility work, or error recovery onto the person trying to accomplish a goal.
This matters because reform becomes harder when criticism depends on proving that somebody intended harm. UXR instead asks what the system does, which burdens are necessary, who controls them, who bears them, what evidence supports the explanation, and what correction would demonstrate improvement.
Another part of the founder's experience involved the cost of trying to correct systems. A person notices something wrong, believes action may matter, spends time reporting it, and then watches the effort disappear into a process that produces no visible learning or correction. Repetition can change future behavior.
UXR treats this as a potential form of learned nonparticipation at the system level. No institution needs to intend to teach helplessness. A system can nevertheless teach people that participation is ineffective when effort repeatedly fails to produce a credible relationship to outcome.
That leads to a design requirement for UXR itself: reporting unnecessary burden should not itself require unnecessary burden.
Arenas describes a different calculation when deciding whether to spend personal time pursuing a problem:
“I don’t view my fight as an individual fight. I view it as a fight for everyone.”
Thirty minutes spent correcting a problem may not make economic sense for one person if the only result is one individual remedy. The equation changes when the effort can become a durable case, attract matching experiences, preserve evidence, produce a reusable workaround, help an institution identify a failure, and eventually document a reform that improves future interactions for many people.
That is one of UXR's core purposes: build infrastructure that allows one person's finite effort to become useful to other people instead of vanishing when the interaction ends.
Institutions usually enter an interaction with continuity, records, staff, procedures, automation, legal resources, and accumulated knowledge. An individual usually enters with one problem and a finite amount of time, attention, money, health, patience, and emotional capacity.
UXR is intended to change that leverage relationship. The objective is not to make people become better bureaucratic combatants. It is to multiply the effect of the effort they can reasonably give by preserving evidence, matching recurrence, carrying institutional memory forward, identifying responsibility, publishing reform criteria, and verifying what changes.
Arenas has repeatedly rejected a model in which UXR succeeds only by becoming an adversary of every institution it measures. The project should be useful to institutions that genuinely want to improve. A company should be able to study recurring cases, identify expensive friction, improve a process, demonstrate the reform, receive credit for it, and give other organizations a model worth copying.
This is also why UXR's anti-capture rules matter. Institutions should be able to change their results by changing human outcomes. They should not be able to change the ruler by funding, pressuring, or privately negotiating the standard. The One-Way Authority Rule preserves that direction of influence.
A healthy UXR system should make genuine improvement the most advantageous way for an institution to respond strategically.
UXR's developing research proposes that unnecessary friction consumes more than clock time. It can consume attention, memory, emotional endurance, physical effort, money, fuel, battery life, trust, care capacity, and practical agency. Removing the friction can return several forms of human capacity at once.
The founder's interest in these effects is civilizational as well as individual. A receptionist who has spent less of her own day fighting unnecessary systems may have more attention and patience available for the next person she helps. A worker who recovers an hour may use some of it for paid work, family care, exercise, study, sleep, creation, civic participation, or leisure. A reform that saves minutes across millions of future interactions can continue producing value long after the original case closes.
UXR therefore treats proposed Human Time, Capacity, Agency, Attention, Emotional, Memory, Trust, Care, Resource, Economic, Public Revenue, Health, Civic, Dignity, Reform, and Propagation dividends as research hypotheses to define, publish, challenge, measure, and revise. They are not assumed findings. The project intends to state the proposed mechanisms, invite academic and practitioner commentary, identify possible measures and confounders, and describe what evidence would strengthen, weaken, or falsify each proposal.
The point is not that every returned minute must become economically productive. Part of the dignity returned by reform is that the time belongs to the person again.
One of the founder's strongest concerns is not only that UXR could be captured or misused. It is that UXR could become rigorous, ethical, and technically sound while remaining too difficult for ordinary people to understand or use.
A lever nobody can pick up has little practical leverage. UXR therefore cannot require someone to study its entire taxonomy, governance model, evidence architecture, or scoring theory before saying, “This happened to me too,” learning a workaround, following a case, or understanding what reform is being requested.
The rigor belongs underneath the interaction. Comprehensibility is not decoration. For a project intended to restore practical agency, comprehensibility is part of the architecture.
The objective is not a frictionless utopia. Necessary friction exists: safety checks, diagnosis, due process, learning, maintenance, fraud prevention, and other legitimate constraints can require time and effort. UXR asks whether a burden is necessary, proportionate, well designed, and borne by the appropriate party.
It also does not exist only to catalog failure. UXR should be able to document excellent experiences, preserve successful reforms, give institutions deserved credit, help other organizations copy what works, and gradually shift its public record from a library of recurring burdens toward a library of demonstrated better practice.
The underlying proposition remains simple: Life does not have to stay harder than it needs to be.
Arenas currently serves as UXR's founder, primary author, and framework-development lead. That includes developing the constitutional core, taxonomy, evidence model, governance safeguards, case architecture, public documentation, research proposals, and future operational standards.
Founder attribution establishes provenance and responsibility for the work. It does not place the founder above UXR's safeguards. The One-Way Authority Rule, evidence discipline, causal humility, versioning, public criticism, and anti-capture architecture are intended to constrain future service organizations, funders, advisors, leadership, and the founder alike.
UXR welcomes criticism, research, counterevidence, and public review. Agreement with the founder is not a condition of participation.
Copyright © 2026 Sean Arenas. User Experience Reform (UXR). All rights reserved. See the UXR Copyright, Attribution, and Reuse Notice for permitted uses and limitations.
Document 53
Document status: Foundational governance commitment
First published: August 4, 2026 under the name User Experience Reform
Current identity: Human Experience Reform (HXR)
Substantively revised: August 18, 2026
This pledge establishes a governing commitment. It does not prove that capture is impossible. Its practical strength will depend on the safeguards HXR can actually implement as its capability and influence grow.
Human Experience Reform must be able to develop without quietly surrendering the principles that make the project worth developing.
This pledge establishes a public commitment to constitutional lineage, transparent revision, scientific correction, evidentiary dignity, and resistance to commercial, political, institutional, or personal capture.
HXR may expand, clarify, test, correct, and improve its constitutional and methodological documents. It will not quietly reverse its governing principles, conceal material changes, or permit money, access, institutional pressure, private influence, or routine skepticism toward contributors to redefine public standards.
Future revisions may clarify language, add evidence, improve accessibility, refine taxonomy, replace weak methods, correct mistakes openly, and add safeguards discovered through testing.
A change requires explicit, versioned public rationale when it would materially alter the One-Way Authority Rule, independence, human agency, civilizational stewardship, uncertainty, causal inference, public access, purchased influence prohibitions, the commercial boundary, contributor evidence treatment, or official status.
No future service company, consulting arm, funder, client, board, advisor, founder, executive, or partner may privately redefine what HXR standards mean.
Operational organizations may contribute evidence, criticism, implementation knowledge, explanations of constraint, responsibility claims, and reform proposals through transparent processes. They may not purchase authority over definitions, findings, comparisons, or scores.
Anti-capture does not mean that HXR becomes immune to influence from evidence. A contributor, measured institution, researcher, regulator, critic, or other participant may provide facts or reasoning that require HXR to correct a case, reassign responsibility, revise a comparison, refine a method, or change a conclusion.
A right of evidentiary response is not a right of approval. An institution may challenge evidence, comparability, attribution, measurement, inference, constraints, or uncertainty. If the challenge is supported, HXR should change. If it is unsupported, institutional status, money, displeasure, access, or refusal to participate must not determine the result.
This distinction preserves both independence and corrigibility. HXR should remain difficult to capture and easy to correct with sufficiently strong evidence.
HXR will not treat contributor testimony as a defective version of an artifact. A contributor's account stands as testimony at full strength for what it is. Provenance identifies the source; it does not impose a credibility penalty. Additional evidence may add support, precision, context, challenge, contradiction, or correction, but its absence must not be used as a routine reason to weaken the contributor's report.
HXR may separately qualify causal mechanism, organizational attribution, prevalence, motive, precision, durability, interpretation, or genuine evidentiary conflict. It must not relocate those uncertainties onto the person's report merely because stronger evidence could theoretically exist.
When HXR makes a transcription, extraction, summary, classification, or analytical error, HXR must own that correction explicitly. It must not mislabel its own mistake as a contributor correction or silently rewrite the historical record.
Protecting constitutional integrity does not mean freezing every early draft. HXR must remain capable of admitting error. A transparent correction supported by evidence strengthens the framework. A concealed reversal made for convenience or influence weakens it.
HXR applies the principle that responsibility should scale with capability and consequential power to itself. A small founder-led project has different practical obligations from a future institution relied upon by large populations, journalists, researchers, regulators, or organizations.
As HXR acquires greater reach, data, authority, reputation, financial resources, or capacity to affect human and institutional outcomes, its duties of accuracy, transparency, security, correction, response, accessibility, governance, and stewardship must grow accordingly.
This pledge is currently a public governance commitment rather than a complete legal enforcement instrument. HXR is a one-person founder-led project, not yet a staffed agency, certification authority, or mature standards institution. Stronger organizational controls should be designed when actual operations create a demonstrated need for them.
The project began in 2026 under the name User Experience Reform (UXR) and adopted Human Experience Reform (HXR) as its public identity on August 18, 2026. The rename clarified scope; it did not replace the constitutional lineage or erase the UXR period from the record.
Copyright © 2026 Sean Arenas. Human Experience Reform (HXR). All rights reserved.
Document 54
Document status: Canonical-source declaration
Original effective date: August 4, 2026
HXR naming effective date: August 18, 2026
The official HXR Documentation publication on the project-controlled website is the current public source of truth for Human Experience Reform.
Copies, quotations, screenshots, archived pages, third-party summaries, AI-generated descriptions, and derivative publications may be useful, but they do not replace the current canonical text.
Official material should be traceable to the canonical HXR Documentation publication or to another repository expressly listed here in the future.
The canonical source will identify:
The public documentation includes HXR's current constitutional principles, taxonomy, scientific-development statements, governance safeguards, audience architecture, research notes, and project roadmaps.
These documents are public review materials from a developing framework. Their official status does not imply that unfinished scoring systems have been scientifically validated.
As of August 4, 2026, HXR does not operate:
Any contrary claim should be treated as unverified unless this page later identifies the relevant official program.
Independent projects may discuss or apply HXR ideas under the published reuse and brand guidelines. They do not become the canonical HXR framework merely by using similar terminology.
Official lineage depends on transparent continuity with HXR's constitutional core, public version history, and authorized governance structure.
HXR intends to add third-party archival repositories, signed version history, and permanent identifiers for major releases. Once established, those locations will be listed here with exact links and status descriptions.
When a third-party copy conflicts with the current canonical source, the canonical source controls for present HXR policy. Historical copies remain evidence of what the project stated at the time they were published.
Copyright © 2026 Sean Arenas. Human Experience Reform (HXR). All rights reserved.
Document 55
Effective date: August 4, 2026
Current identity: Human Experience Reform (HXR)
Historical identity: User Experience Reform (UXR) until August 18, 2026
Copyright holder: Sean Arenas
Copyright © 2026 Sean Arenas. Human Experience Reform (HXR). All rights reserved unless a specific page states otherwise.
The original HXR written documentation, framework architecture, taxonomy, methodology, governance design, case structure, explanatory text, and original compilations are protected works to the extent provided by applicable law.
Materials created while the project was named User Experience Reform remain part of the same documented HXR lineage. Preserving a historical UXR title, identifier, quotation, or citation does not create a separate successor project or transfer ownership.
Human Experience Reform was conceived and created by Sean Arenas, initially under the name User Experience Reform. Current discussion, teaching, reviewing, and citation should ordinarily identify the project as Human Experience Reform (HXR) and attribute the work to Sean Arenas.
A suggested current attribution is:
Human Experience Reform (HXR), created by Sean Arenas, official public documentation, 2026.
When citing a document as it appeared before August 18, 2026, a historically precise attribution may say:
User Experience Reform (UXR), now Human Experience Reform (HXR), created by Sean Arenas, 2026.
HXR welcomes good-faith public discussion. Without additional permission, readers may:
Unless another license is later published, permission is required to:
Copyright does not create ownership over every general idea discussed by HXR. It protects original expression and compilations, while trademark, certification, contract, unfair-competition, and other laws may protect names, marks, official identity, and representations of authorization.
HXR therefore distinguishes between:
HXR does not currently operate Blue Scores, Blue Zone certification, accredited audits, or an authorized assessor registry. No person or organization may truthfully claim current official HXR certification or authorization.
HXR is evaluating whether some documents or tools should later receive standardized public licenses. No Creative Commons or open-source license should be inferred unless a specific work expressly displays one.
This notice documents the project's current attribution and reuse policy. It does not replace formal copyright registration, trademark registration, certification-mark registration, contracts, or advice from qualified intellectual-property counsel.
Canonical source: the official HXR Documentation publication. Material copied elsewhere may be outdated, incomplete, or unauthorized.
Document 56
Document status: Current public usage guidance
Effective date: August 4, 2026
Current identity: Human Experience Reform (HXR) since August 18, 2026
These guidelines help readers distinguish official Human Experience Reform work from independent discussion, adaptation, criticism, or commercial services.
HXR is intended to be studied, criticized, taught, cited, and applied. That openness does not authorize others to imply that their project, score, audit, certification, or commercial offering is official HXR.
The project began under the name User Experience Reform (UXR) and adopted Human Experience Reform (HXR) as its public identity on August 18, 2026.
Use Human Experience Reform (HXR) for current references. Preserve User Experience Reform (UXR) when quoting or citing historical material from the UXR period, legacy identifiers, technical namespaces, or records whose original wording matters. Historical accuracy does not authorize a separate project to claim the UXR identity as an official successor.
Appropriate uses include:
For historical material, an accurate formulation is “User Experience Reform, now Human Experience Reform.”
Do not use the HXR name, initials, marks, or future certification language to imply that a person, organization, service, assessment, or publication is:
The same restriction applies to misleading use of the historical UXR name when it would imply present official status or continuity.
An independent derivative or localized project should use its own distinct primary name. It may accurately state that it is “based on,” “informed by,” or “in dialogue with” HXR, provided the statement includes clear attribution and no implication of official status.
A derivative project should not use HXR, Human Experience Reform, Official HXR, HXR Certified, HXR Compliant, Blue Zone Certified, or a confusingly similar term as its primary brand without written authorization.
A project that removes or reverses HXR's core safeguards, such as the One-Way Authority Rule, evidence independence, causal humility, public traceability, or prohibition on purchased scoring influence, must not represent itself as the official continuation of HXR.
No current public license authorizes commercial entities to sell official HXR audits, compliance services, accreditation, certification, or score improvement under the HXR name.
Independent consultants may discuss HXR or help organizations improve human experience, but they must describe their work accurately and avoid implying official authorization.
HXR is currently an independent founder-led project. It does not yet operate a public certification program, authorized assessor network, licensing system, or official partner registry. A future system should be described as operational only after the corresponding controls and public records actually exist.
As the project develops, HXR intends to provide a contact path for reporting false certification claims, copied materials, misleading branding, or unauthorized assertions of official partnership.
Copyright © 2026 Sean Arenas. These guidelines may be linked and quoted with attribution. They do not constitute a final trademark license or legal opinion.
Document 57
Roadmap status: Active development plan
Published: August 4, 2026
Current reality: No canonical public repository, signed release system, external archival deposit, or DOI currently exists.
What exists now: Website publication history, founder attribution, public notices, a history, research notebook, source-of-truth declaration, changelog, and constitutional integrity pledge.
What would count as completion: A designated public repository, durable version history, signed or otherwise verifiable releases where practical, third-party deposit records, and persistent identifiers for major releases.
UXR needs a public record that establishes authorship, preserves exact historical versions, supports academic citation, and allows readers to verify whether a document existed in a particular form at a particular time.
The current website publication history contributes to that record, but website dates alone should not become the project's only provenance system.
UXR plans to maintain a public repository containing canonical text in a durable, portable format such as Markdown.
The repository should include stable document identifiers, version numbers, dated commits, release notes, diffs, superseded versions, machine-readable metadata, and a clear statement identifying official releases.
Status: Planned. No public repository is yet designated as canonical.
Major UXR releases should be deposited in a reputable third-party preservation service. Candidate repositories include Zenodo and the Open Science Framework.
Major milestone releases may receive Digital Object Identifiers, allowing stable academic and public citation.
Status: Planned for a sufficiently stable milestone release. No DOI has yet been issued.
UXR plans to standardize document title and ID, authority level, version, dates, canonical URL, responsible editor, lineage, change summary, copyright, and licensing status.
Status: Initial metadata exists on several pages. Full normalization remains in progress.
The future versioning policy should distinguish editorial corrections, clarifying revisions, methodological revisions, constitutional revisions, and major public releases.
A public canonical case or document should present the strongest current account rather than force readers through every superseded detail that appeared while evidence was still developing. Exact provenance and public clarity are compatible because they can live in different layers.
For case work, UXR should preserve the contributor's original account and the evidentiary working history privately or in controlled archival records as appropriate. The current public case may then be rewritten around better-supported facts as evidence improves. An ordinary difference between remembered wording, timing, or another detail and a later artifact does not need to become a public credibility event merely to prove that UXR kept an audit trail.
A discrepancy should remain visible publicly when the discrepancy itself materially affects the finding, causation, responsibility, credibility analysis, or fair interpretation of conflicting evidence. Otherwise, the archive preserves how the record changed while the canonical public case preserves what the evidence currently supports.
The UXR changelog should make substantive project maturation inspectable: framework revisions, methodological discoveries, operational milestones, case-architecture changes, material public-case developments, and corrections that alter the meaning of a finding. It should not become a duplicate of the private evidence audit trail or a catalog of ordinary contributor memory refinements.
When live casework exposes a weakness in UXR's own evidence language, correction handling, publication practice, privacy, routing, or case architecture, the resulting methodological change should be recorded. This allows journalists, academics, contributors, institutions, and future UXR maintainers to see how the system matured through contact with actual cases rather than presenting the framework as if it arrived fully formed.
Where a document change follows a major review, case analysis, or methodological discovery, the changelog should identify the trigger without exposing confidential contributor information or turning ordinary contributor corrections into public credibility events. Future repositories and archives should preserve exact historical versions where appropriate, while the public canonical surface remains optimized for the strongest current account.
Copyright © 2026 Sean Arenas. This roadmap documents intended work and does not claim that planned repositories, signatures, deposits, or DOIs already exist.
Document 58
Document status: Current project record
First published: August 4, 2026
Current identity: Human Experience Reform (HXR) since August 18, 2026
Current role: Canonical public development-history surface
This registry records meaningful changes to HXR itself. It covers public documents, framework elements, governance mechanisms, case infrastructure, publication systems, research mechanisms, and other first-class HXR features without treating every copy edit as a development event.
HXR Development Item records hold current development truth for registered features and processes. Development Event and documentation-revision records preserve dated history: what changed, why it changed, the resulting state, the affected object, and the evidence supporting the date. Legacy UXR-... identifiers and uxr_* technical keys remain where continuity requires them; their names do not make them separate from HXR.
This page remains the public change-history surface. Other HXR objects may display recent entries from the same development records and link here or to a fuller history view. The complete reviewer packet automatically includes published HXR Documentation, so this registry is part of the packet rather than a separate untracked appendix.
The project adopted Human Experience Reform (HXR) as its active public identity. User Experience Reform (UXR) remains the documented historical name and a legacy identifier or technical namespace where changing it would damage continuity without providing public value.
Public result: Shopify now presents HXR Documentation, HXR Cases, Human Experience Reform navigation and landing pages, and HXR-facing Case and Evaluation language while preserving established /blogs/uxr, /blogs/uxr-cases, UXR-... record identifiers, and internal uxr_* implementation keys.
Theme result: the unified theme HXR UNIFIED PROJECTION-NATIVE - AUG 18 became the live theme. It combines the HXR identity work with the projection-native Case Library and native public Case and Evaluation templates.
Verification result: the post-publish structural test confirmed the live theme, HXR navigation and core pages, 75 HXR documentation articles, and 34 published Case or Evaluation routes. The test found and repaired 10 documentation articles and five public-record articles that were still assigned to generic Shopify templates.
Contribution-pilot alignment: the canonical Evaluation schema gained Contribution Intake State, Public Contribution Prompt, and Minimum Matching Context. Two healthcare Evaluations were configured as the first deliberately narrow pilots. The controlling interface contract requires one Add Your Experience doorway, ordinary-language intake, behind-the-scenes classification, no automatic Incident creation, and a plain-language contribution summary before any richer contributor system is justified. The public contribution panel, secure intake route, and end-to-end submission flow are not yet operational.
Current boundary: the public HXR cutover and structural verification are complete. Remaining work is controlled cleanup, visual review, contribution-pilot staging, and later monitoring, not another decision about whether the project should be renamed.
UXR completed the migration of its core structured data, documentation, intake workbench, evidence and evaluation graph, governance controls, and publication workflow to the new canonical architecture.
Operational result: canonical editing and public presentation are now separated by a controlled projection boundary. Public-facing material is derived only from records approved for release, while private evidence, contributor-sensitive material, internal workbench records, and non-public governance data remain outside that projection.
Validation result: the documentation projection passed count, active-state, stable-identity, change-hash, synchronization-time, and live-renderer checks. Post-migration tests also confirmed permanent identifiers and core graph relations across migrated Incident Cases, Evaluations, Evidence Items, and contribution/subject links. One legacy case-scope surface was found to have broader public-read access than intended; that access was removed during the acceptance test.
Current boundary: structural migration is complete, but imported records are not silently promoted to final canonical verification. Record-by-record semantic reconciliation continues where the migration state still says Imported. Private Alpha, release gating, provenance rules, and human approval requirements remain in force.
UXR moved from documenting the framework in public, to engineering and testing it in public, to accepting a limited number of real-world submissions in Private Alpha. Submissions may be serious or casual, positive or negative. Private intake remains separate from public publication, which continues to require privacy, provenance, release, and human-review controls.
The first 12-fixture manual baseline produced eight passes and four failures, so the suite failed overall. The run was manual, single-grader, self-graded, and sequential. It tested prompt-layer model compliance with production schemas and instructions; no executable publication broker was in the decision path. UXR therefore does not claim that broker enforcement has been validated.
The baseline exposed a repeated attribution defect. UXR froze the exact v1 specification before remediation, recovered two transcript-only results into the authoritative ledger with their limitations recorded, added a fail-closed candidate/source-resolution stage, adopted a no-manufactured-attribution invariant, made linked countable result rows authoritative over stored count snapshots, added idempotent attempt/write identity, and drafted successor coverage without changing frozen v1.
Detailed scenarios, acceptance criteria, prohibited constructions, and document-to-test mappings remain internal. The public milestone is the existence of a versioned integrity-testing process that records failures and drives architecture changes, not disclosure of the answer key or a claim of validation.
This work has been carried out without a formal programming team, board of directors, or dedicated UXR domain. The constraint is part of the development record, while the invitation is practical: programmers, reviewers, journalists, researchers, designers, privacy specialists, domain experts, and other applicable contributors can help test and build the next stage.
Implemented:
Current migration state: Canonical Feature linking is now complete across all 61 current UXR Document records. Records whose old structured status was only a migration placeholder remain explicitly marked for authority, version, and substantive-history reconciliation before legacy fields are retired.
Migration rule: Legacy fields remain available as source evidence until their supported state and history have been transferred and every dependent display has been verified against the new canonical records. They are not treated as authoritative merely because they still exist during migration.
Date discipline: Exact dates are used when a source document, publication timestamp, Shopify record, or other direct record supports them. Approximate or unknown dates remain visibly uncertain rather than being converted into invented precision.
Added:
Expanded:
Preserved as development findings:
Status: The new terms and models remain development findings or framework proposals unless a controlling document expressly adopts them. No scoring system, legal conclusion, intervention rule, or automatic authorization of workarounds was created.
Added:
Purpose: establish public authorship, canonical lineage, reuse boundaries, anti-forking guidance, and visible plans for stronger archival and legal protection.
Added or expanded:
Revised across the framework:
The public UXR Documentation collection established the constitutional framework, universal scope, Human Agency, Civilizational Stewardship, taxonomy, evidence and confidence model, One-Way Authority Rule, accountability structure, audience architecture, roadmap, and explicit current-project limitations.
Historical migration will identify earlier publication dates and versions only where reliable records support them. This registry will not invent precision that the historical record does not establish.
A mature history entry can identify the feature, event type, date or timestamp, previous and resulting state, previous and resulting version when applicable, what changed, why it changed, the affected object, source basis, date confidence when uncertainty exists, and a public-safe note.
Copyright © 2026 Sean Arenas. Human Experience Reform (HXR). All rights reserved.
Document 59
Roadmap status: Legal and operational planning
Published: August 4, 2026
Current reality: No UXR certification mark, certification program, licensed assessor network, or formal public registry currently operates.
What exists now: Public authorship, copyright and brand-use notices, the Official Source of Truth page, and explicit warnings against false official status.
What would count as completion: Qualified clearance review, filings or registrations where appropriate, published operating rules, an authorized verification process, and a public registry.
Copyright protects original expression. It does not, by itself, establish exclusive control over project names, certification claims, seals, or confusing representations of official authorization.
UXR therefore plans a separate trademark and certification-mark strategy.
Potential marks for professional legal review include User Experience Reform, UXR, official logos and seals, Blue Score if retained, Blue Zone terms subject to clearance, and names of future assessor programs.
Listing a candidate here does not claim registration, availability, or exclusive legal rights.
A future certification mark could allow qualified organizations to display an official UXR designation only after meeting publicly defined criteria through an authorized process.
A certification system would require objective public standards, independent governance, consistent verification, anti-influence rules, appeals, correction, suspension, revocation, authorized use rules, a public registry, and legal review.
Status: No UXR certification mark or certification program currently operates.
UXR plans a public registry that may eventually list official standards, authorized assessors, verified pilots, valid certifications, licensed marks, recognized partnerships, and suspended or revoked authorizations.
Status: The current Official Source of Truth page serves as a preliminary verification point. A formal registry has not yet been built.
An official UXR seal must never become a decorative badge purchased by an organization while harmful practices continue behind it.
No organization currently holds official UXR certification, Blue Zone status, licensed assessor authority, or permission to issue official UXR scores.
Copyright © 2026 Sean Arenas. This roadmap is not a claim of current trademark registration and does not replace legal advice.
Document 60
Roadmap status: License strategy under review
Published: August 4, 2026
Current reality: UXR has not adopted a general Creative Commons, open-source, public commercial, certification, or assessor license.
What exists now: Public copyright, attribution, reuse, and brand-use notices.
What would count as completion: A published license matrix, qualified legal review, document-specific licenses, effective dates, and preserved prior terms.
Unless a specific work says otherwise, the current copyright and reuse notice applies. Public access does not automatically place a work in the public domain or grant permission to publish modified official versions.
UXR wants to support public reading, linking, citation, criticism, teaching, research replication, responsible public-interest application, localized education, and open improvement where openness does not compromise official identity or certification integrity.
Licensing must also reduce false official forks, corporate enclosure, altered constitutional texts presented as authentic, unauthorized certification claims, loss of control over official scoring and marks, and conflicts with future governance.
Different layers may require different approaches. Constitutional documents may need integrity-preserving terms. Research and educational documents may support broad attributed reuse. Operational tools may benefit from share-alike or open-source terms. Official assessment, scoring, certification, or consulting rights may require separate agreements.
UXR combines publications, methodology, taxonomy, software plans, data architecture, scoring, certification, governance, and possible service organizations. A license appropriate for one layer may damage another.
Professional intellectual-property review should occur before the project commits its constitutional core or operational methods to an irreversible licensing structure.
Copyright © 2026 Sean Arenas. No license listed as a possibility on this page is currently granted.
Document 61
Roadmap status: Future governance structure
Published: August 4, 2026
Current reality: No UXR Stewardship Council currently exists. No person holds membership or authority on its behalf.
What exists now: Public constitutional commitments, the One-Way Authority Rule, and a documented governance design problem.
What would count as completion: A published charter, appointment and removal rules, named members, conflict controls, transparent authority, succession provisions, and enforceable procedures.
UXR may eventually need trusted public stewards who can defend constitutional continuity, review conflicts, and strengthen credibility beyond any single founder or operating organization.
The council should guard the framework. It should not become an unaccountable authority that privately rewrites it.
A future council may review constitutional change processes, identify conflicts, verify revision history, advise on evidence and independence, support succession, and issue public dissent when procedures fail.
A stewardship council should not sell scores, privately alter findings, grant nonpublic standards, represent donors for influence, replace methodology with discretion, or govern ordinary operations without published authority.
Selection should prioritize independence, integrity, competence, lived-experience representation, and conflict disclosure. Before formation, UXR should publish appointment, removal, term, recusal, transparency, compensation, dissent, authority, and relationship rules.
The council should form when UXR has sufficient methodological maturity, public responsibility, and operational exposure to need institutional continuity. It should not be assembled prematurely merely to display impressive names.
Copyright © 2026 Sean Arenas. This roadmap creates no current appointments or governance authority.
Packet body check: 61 documents rendered. Status, authority, and version labels are generated from canonical Feature records.