The working A prototype: use its controls to test the build question.
Compare what a rule says with what people actually experience navigating it.
RN conceived the question, structured the evidence boundaries, designed the experience, implemented the prototype and documented its limits.
This independent prototype demonstrates an approach; it is not a deployed client system, professional advice or proof of real-world outcomes.
Work through the controls with a situation of your own rather than the sample values. The tool responds to what you put in, so the useful output comes from real input, and everything is processed in your browser as you go. Any sample content you find already loaded is there to show the shape of a filled-in state, and you can clear it and start again at any point.
The build overview sets out the question, the purpose, the role and the evidence status in one place, and the public record behind it states what changed, what another person can reuse and what supports the system. If you want to judge how far this build should be trusted, the record is the page to read, not this one.
What Does This Rule Feel Like in Real Life?
Place procedural text beside the lived path it creates.
BURDENSOME
LANGUAGE ACCESS · MOBILITY · DIGITAL ACCESS · TIME CONSTRAINT
Synthetic Rule v1
READ NOTICE → SUBMIT FORM → PROVIDE RECORDS → WAIT → RECEIVE DECISION
30 modeled days · 2 documents
5 steps · burden 146
LANGUAGE ACCESS, MOBILITY, DIGITAL ACCESS, TIME CONSTRAINT
Recourse: REQUEST REASONS, CORRECT RECORD, APPEAL
Boundary: A modeled burden is not a finding about legality, discrimination, compliance, harm, or any real person. It shows questions that must be investigated with affected people and authoritative sources.