In law and administration, the framework’s claim becomes: a right is failing when ordinary people cannot invoke it without exceptional time, money, literacy, or risk.
Judge legal systems by how hard rights are to use and how fast harm gets repaired.
Common misdescription in this field
Rights listed = rights protected
Paper protections are treated as operative without measuring access burden.
- Appeal exists but demands expert intermediation.
- Deadlines punish people for institutional delay.
- Pending review leaves harm active.
Procedure is neutral by default
Design choices in timelines, evidence rules, and notices are treated as impartial.
- Complexity filters out low-resource claimants.
- Silence is read as consent.
- Delay functions as denial.
What to measure instead
Measure what it takes to use a right and whether people can survive the remedy.
Burden of invocation: what does it take to use the right?
Count cost, time, literacy, and retaliation exposure.
Time in harm: who bears losses while review is pending?
Track interim harm, not just final outcomes.
Remedy efficacy: can ordinary users reach correction?
A remedy exists only on paper if you effectively need an expert to use it.
Typical failure pathway (how people fall out)
Nominal right
Right is declared and publicly cited as legitimacy evidence.
Invocation friction
Costs, deadlines, and documentation filter claims before merits review.
Attrition by process
Dropout is recorded as abandonment, preserving formal legitimacy.
Design/legal/operational fixes
Fixes must make invocation something an ordinary person can manage.
Design fix: default-readable procedure
Simplify notice architecture and reduce process branching.
Legal fix: tolling and delay penalties
Stop penalizing claimants for institutional non-response.
Operational fix: tracked recourse outcomes
Publish completion, reversal, and unresolved-case metrics.