Personas and OKF pack stories
For a first useful AI experience, start with an existing bundle. Use the maintained example catalogue and audience journeys before this deeper reference.
These provisional personas help test different needs and limits. They do not replace research with real people. The catalogue distinguishes registered bundles, an external application, a starter and conditional collections; historical lineages remain in the evolution review.
| Persona and pack | User story | Exercise and limit |
|---|---|---|
| Junior knowledge engineer — review and AI infrastructure | I need to trace why an assertion exists so that I distinguish practice from an idea. | Move from Reader to evidence and Inspect; research does not authorise production. |
| Data journalist — ONS | I need the exact product, geography and vintage so that I do not cite a near-neighbour. | Resolve identity and publisher; metadata does not calculate the statistic. |
| Open-data analyst — GOV.UK CKAN | I need to compare publishers, licences and resources so that I can shortlist data. | Inspect gaps and live resources; catalogue presence does not guarantee quality. |
| Integration architect — government APIs | I need the provider's real contract so that software does not invent methods. | Follow to provider documentation; OKF is not the executable contract. |
| Legal researcher — legislation | I need the correct work, jurisdiction and version so that I reach official provisions. | Resolve source and version; the pack is not legal advice. |
| Policy researcher — whole-law federation | I need governed fallback routes so that I retain authority. | Inspect coverage and conflicts; federation does not make sources equivalent. |
| Heritage teacher — Coventry and Warwickshire | I need a source-backed trail so that learners separate evidence from illustration. | Expose fixture status; synthetic evidence is not history. |
| Education data developer — ELS APIs | I need to find a capability and verify access so that I can plan integration. | Check the live contract; a hackathon pack is not a service guarantee. |
| Planning officer — planning | I need exact application, place and authority identities so that I can explain a trail. | Test dates and authority; the statutory register remains authoritative. |
| Content designer — GOV.UK content | I need the exact guidance family so that I avoid a near-neighbour. | Retain canonical links; retrieval does not determine eligibility. |
| Property researcher — HM Land Registry | I need source, rights and observation evidence so that I understand a product. | Trace publisher and provenance; the bundle cannot prove ownership. |
| Citizen adviser — A Life in the UK | I need services connected to life events without losing jurisdiction. | Explore rich links; an editorial journey does not determine entitlement. |
| Research developer — API-MCP-Wiki and LLM-Wiki | I need comparable retrieval results so that infrastructure proves its value. | Compare full, link and MCP context; retrieval does not prove answer correctness. |
The ELS and planning rows are requirements prompts. No verified public entry route is supplied for them in this documentation set. Establish producer ownership, licence and access before using a collection in an exercise.
Turn each relevant story into normal, near-neighbour, missing, stale and unauthorised journeys. Record observed evidence rather than judging appearance.