Validators
Each validator takes three inputs about a user journey. It returns a red, yellow, or green status, the clauses at risk in STD-01, the temporal rights standard, and a mechanism to review.
Every validator, in one table
The standard each one checks against, the inputs it takes, and the clauses and mechanisms it points to.
| Validator | Standard | Inputs | Clauses | Mechanisms |
|---|---|---|---|---|
| VAL-01 Journey burden check Scores how much time a user journey takes from people, and whether it is heavy enough to keep them from the service, from its duration, its step count, and whether every screen has an exit. | STD-01 | Estimated time to completion (minutes); Number of required steps; Exit available on every screen | STD-01.3.1, STD-01.3.2, STD-01.7.1 | MEC-04 |
| VAL-02 Risk radar Scores the friction a journey adds up to, from the number of hard steps, the average wait, and whether each step can be challenged. | STD-01 | Number of high-friction touchpoints; Average wait time (minutes); Appeal path available for every touchpoint | STD-01.5.1, STD-01.5.3, STD-01.6.1 | MEC-06 |
| VAL-03 Latency audit Checks observed latency against the declared timeout and whether a human escalation path exists. | STD-01 | Declared timeout (seconds); Observed max latency (seconds); Human escalation path in place | STD-01.3.1, STD-01.3.2, STD-01.3.3 | MEC-04 |
Method
How validators score systems
Each validator turns STD-01 clauses into input fields. It returns a report card that names a mechanism to fix what it finds.
- Collect three inputs from the system's operators or QA team.
- Compare the inputs with the published thresholds.
- Generate a report card with a red, yellow, or green status.
Each output names the STD-01 rights it checks, in the rights matrix and the standard, and the mechanisms that fix a failing result.