The gap is who the team tested the concept with. Red line A3. Points 1 and 2 are Not Met. The team saw six confident applicants and three caseworkers. They did not recruit people with low digital skill, people with low literacy, or people who cannot get to a photo point.

These points should be Met: 3, 4, 6, 7, 8, 9, 11.

Point 5 is not a fail at Alpha. Leave 10, 12, 13, and 14 Not assessed. A recommendation on GOV.UK Notify and GOV.UK Pay is fair. It does not change the result.

What would clear the fail

The user researcher recruits and concept-tests with people the online photo upload puts at risk. Include people who cannot leave home, people applying for someone else, people with low digital skill, and people with low literacy. Record how they were recruited, the task, where they stopped, and what the team dropped. Do not treat the prototypes as ready for a private beta until that evidence is in this pack. No date is set.

Run it

create-example.py, next to the how-to skill, writes this folder into a project. The default path is docs/examples/apply-for-a-blue-badge. Assess the alpha folder there. The orchestrator asks in the chat about the people the team did not see, one question at a time, and waits. The result above is what scoring finds after that dialogue. A reply that only tells the story, or a skip, leaves the evidence outstanding and points 1 and 2 Not Met. Do not score this readme. It is the answer key.

Run an Alpha assessment of docs/examples/apply-for-a-blue-badge/alpha. Use assessment-panel-orchestrator, then the four Alpha assessor skills, then assessment-report-synthesis. Cite past assessments through the gds-assessment-reports tools. Do not read docs/examples/apply-for-a-blue-badge/README.md while scoring.