OAF-001
The OverUX Assurance Framework v0.1. A non-certifying research model for structured pre-release review without a composite UX score.
Preserve dimensions. Preserve evidence.
A composite score can hide the thing that matters: which requirement failed, which evidence exists and which uncertainty remains. OAF keeps each dimension visible and records the release decision separately.
Six non-compensating lenses.
| Code | Dimension | Review question | Example evidence |
|---|---|---|---|
| C1 | Clarity | Can the user understand current state, available action and likely consequence? | Task walkthroughs, content review, state labels, user testing observations. |
| C2 | Continuity | Does context and system state remain coherent across transitions, devices or interruptions? | State-transition review, journey traces, persistence tests, navigation behavior. |
| F1 | Friction | Is interaction effort proportionate to the user's task and necessary constraints? | Task-step analysis, redundant-entry checks, completion testing, workflow comparison. |
| A1 | Accessibility | Are applicable accessibility requirements and assistive-technology interactions addressed? | WCAG testing, keyboard review, screen-reader checks, automated checks plus human verification. |
| T1 | Trust | Are consequences, consent, reversibility and persuasion represented without avoidable deception or ambiguity? | Consent-flow review, dark-pattern inspection, disclosure review, reversal path testing. |
| R1 | Recovery | Can errors be prevented, diagnosed and recovered from without disproportionate loss? | Error-state inventory, validation behavior, undo/retry paths, support and recovery flows. |
Outcome is not a score.
A release state is attached to a defined review scope and evidence set. It does not transfer automatically to future builds, routes or contexts.
Unknown
Required evidence has not been collected or is stale.
Escalate
Contextual judgment is required before a release decision.
Hold
A blocking requirement or unresolved critical finding is present.
Proceed
Applicable preflight conditions are evidenced for this scope.
Minimum review record.
- Scope: identify build, route/flow, user context and release boundary.
- Requirements: list applicable internal constraints and external standards.
- Evidence: attach observations, tests and source references by dimension.
- Findings: record defects, uncertainty and non-applicable dimensions explicitly.
- Decision: assign Not assessed, Review, Block or Release with rationale.
- Freshness: invalidate or revisit evidence when material interface drift occurs.
What v0.1 deliberately does not define
No universal numeric thresholds, no cross-product ranking, no weighted average, no claim that six dimensions exhaust UX quality, and no automated release authority.