UXR Scoring Architecture: Blue Score Working Draft

Development boundary. Blue Score remains a working name. UXR has begun formal scoring-method development, but no operational score, validated universal instrument, settled weighting model, threshold, or cross-domain equivalence exists yet.

Case-driven development. Scoring development now grows from structured cases that document objectives, system behavior, evidence, burden, benefit, agency effects, reform, verification, and comparison. The score must emerge from observed human-system performance rather than force future cases into a formula invented first.

Three Distinct Forms of Credit

Future comparison should distinguish improvement credit, current performance, and best demonstrated benchmark. An institution deserves evidence-based credit for becoming better than it was. Its current experience should still be evaluated on present performance. A strong current implementation may later be surpassed by a better demonstrated implementation without erasing the earlier improvement.

Cases Are Living Evidence Records

A UXR case is a persistent evidence-bearing record, not a terminal complaint ticket. An individual objective may be achieved, an institution may close its own ticket, a reform may be verified, or operational attention may become quiescent without making the UXR record permanently complete. Later evidence, regression, broader implementation, stronger reform, or superior comparison may still change what the case teaches.

Reform Can Turn a Negative History Into Positive Evidence

UXR does not reward an institution for having started with a harmful or burdensome system, but it should visibly reward verified improvement. A case can become evidence that an organization recognized a burden, accepted responsibility where supported, changed the system, passed an observable test, and continued improving. The history remains visible because reform earns credibility by changing reality, not by erasing the starting point.

A verified reform is not automatically the best achievable reform. UXR should preserve room for later superior practices, new technology, stronger accessibility, lower burden, better contestability, or more agency-preserving design. Benchmark leadership is a current evidence state, not permanent closure.

Reusable Feature Benchmarking

UXR now distinguishes reusable benchmark features from system-specific implementations. A feature describes a capability that can exist across many systems. An implementation record describes how one system provides it, the evidence that it exists, its user-visible behavior, its limitations, the organizations that can reasonably receive credit or responsibility, and its comparative state. Feature presence alone is not proof of quality.

Candidate Measurement Architecture

The developing score should examine agency preservation, agency restoration, burden distribution, visibility, contestability, temporal fairness, risk allocation, compensation or restitution, alternative pathways, outcome reliability, responsibility-to-capability alignment, verified reform, safe explorability, downstream externalities, and feature implementation quality.

Downstream externalities. Institutional processing time does not suspend human obligations. When a system delay causes people to build compensatory pathways, UXR should examine the human time, additional transactions, borrowing, travel, fuel, material wear, infrastructure use, environmental effects, coordination, and other costs created downstream. Costs do not become zero merely because they occur outside the institution's own accounting. Causal attribution and motive remain separate questions.

Safe explorability. In consequential systems, users should be able to understand likely outcomes or test uncertain behavior at sufficiently low cost or reversibility before making a materially larger commitment.

Constraint provenance and institutional response. “That is just how it works” cannot end the inquiry. An institution may respond by demonstrating a genuinely necessary constraint, by showing that the burden is proportionate and well allocated, or by reforming the system. UXR should distinguish explanation from evidence, evidence from adequacy, and adequacy from best demonstrated practice.

Public Development

The architecture is being published before formulas are frozen so affected people, institutions, researchers, domain experts, regulators, designers, and skeptical readers can identify missing dimensions, gaming risks, false precision, and better ways to measure agency-preserving and agency-restoring performance.