Living Incidents, Living Evaluations, Reform Credit, and Continuous Benchmarking

Nothing important disappears when an external ticket closes

UXR records are durable evidence artifacts, not customer-service tickets. An Incident Case remains available after the contributor receives an individual outcome, after an organization marks its own request closed, after active work becomes quiescent, and after years of later developments. An Evaluation likewise remains active as an analytical record through improvement, reform, regression, stronger comparison evidence, and later superior practice.

Incident outcome is not Evaluation reform

An Incident records the state of the bounded human objective: unresolved, workaround only, partial individual outcome, individual outcome achieved, outcome disputed, monitoring, or another incident-level state. That is different from whether a system, institution, mechanism, feature, or practice has been reformed.

System reform belongs to the Evaluation. This lets UXR say both: the contributor eventually got what they needed and the underlying system remains unchanged; or the reverse: the contributor's historical burden remains part of the record and the organization later changed the system for everyone.

A case can become a trophy

An organization should be able to point proudly to a UXR history that began badly and later demonstrates meaningful reform. UXR does not erase the original burden to manufacture praise, and it does not erase verified improvement to preserve blame. A strong reform can become evidence worth displaying precisely because the historical record shows what changed.

A positive Incident can also be a trophy from the beginning. Dignity-preserving infrastructure, clear status, low-burden correction, safe exploration, reliable routing, or successful human outcomes can become evidence for a positive Evaluation and future comparison.

Reform events remain nonterminal

Outcome / Reform / Benchmark Events can record individual remedies, verified positive performance, reported implementation, verified systemic reform, reform maintenance, reform expansion, regression, benchmark performance, or a later superior benchmark. A new event does not close the Incident or Evaluation. It adds to the chronology.

Ownership rule

Incident-owned pathways, steps, and events describe individual outcome, remedy, evidence verification, or incident monitoring. Evaluation-owned pathways, steps, and events describe system reform, positive-practice preservation, benchmark verification, regression, comparative development, and broader responsibility.

Independent evolution

One Incident achieving its objective does not resolve another Incident. Reform by one organization does not establish reform by another. A department can improve while the app regresses. An underlying platform can provide an excellent capability while a local deployment configures it poorly. These states evolve independently and are connected only by evidence-supported graph relationships.

Continuous benchmarking

Later superior practice does not invalidate an earlier positive finding. It changes the benchmark. UXR should be able to show that a system once represented the best observed implementation, was later surpassed, responded by improving again, or regressed. This is why Evaluations and Feature Implementations are permanent records rather than one-time verdicts.

Blue Score

Future Blue Score work belongs at the durable evaluable-subject layer, not the Incident layer. Features, implementations, systems, institutions, departments, and other subjects can accumulate score-relevant evidence through Evaluations and later score snapshots. UXR has not adopted a rule that more features, more cases, fewer complaints, or a single positive outcome automatically produces a higher score.