OKF Explorer documentation
Start with a question, inspect the evidence, then make a small bundle of your own. These guides serve consumers, domain experts, students and knowledge workers as well as contributors.
New to the project? Read the beginner guide in HTML, with chapter contents on the left on wider screens. The website home page links directly to this guide, worked examples and the GitHub repository.
Start here
- Start with knowledge you can inspect: choose a useful first task.
- Try a bundle with AI: a worked evidence question with a human fallback.
- Choose an example: one catalogue, grouped by purpose.
- Choose an AI access route: files, public links, local agents, Copilot and experimental page tools.
- Find a public bundle: exact Pages descriptors, semantic entrypoints, pinned GitHub fallbacks and a Voice prompt.
- Choose your journey: different tasks and successful stopping points.
- Make your first bundle: a complete fictional starter, exact commands and expected checks.
Use and learn
- Use Explorer: current search, facets, highlighting, keeping sets, panels and evidence.
- Read DfE CSV and metadata: inspect an EES data/sidecar pair, exact values, field meanings and scope.
- Inspect a retained evidence example: a seven-step demonstration of a fixed package, its source links and its limits.
- AI Infrastructure walkthrough: one concept across Markdown and Explorer.
- Beginner reference: explanations when you need them, without required sequential reading.
- Reading help for source passages: check exact source wording and open help at declared occurrences.
- Optional project studio: research and create a larger bundle; app creation is optional.
- Map manual and legislation guide: specialist journeys and their limits.
Author and maintain
-
Architecture and implementation plan: current capability states, delivery priorities, acceptance criteria and the whole-implementation review scope.
-
Learning presentation: design goal-led journeys and conceptual filters.
-
Analytical Data profile v1 and estate rollout cover versioned CSV packages, identifier declarations and validation.
-
Warwickshire and NDL compatibility trial captures all 333 real observations, conversion evidence, denied catalogue access and the Explorer application boundary.
-
NDL curation and DEFRA review assesses collection selection, currency, ownership and versioned service access, with a labelled local review proposal.
-
Live Defra API and NDL link scope covers real Warwick stations and readings, pagination, timestamps, spatial metadata and the public catalogue host census.
-
Bundle authoring: core fields, optional domain profiles and richer publication.
-
Foundry prompt kit: governed production authoring after the small starter.
-
Build and publication method: impact planning, source intake and release gates.
-
Development guide and repository guide: maintain Explorer itself.
-
Technical reference map: contracts, domain specifications, evaluations and history.
Quality and review
The P0 whole-implementation review records the October baseline, validated findings, corrections and coverage limits.
Use conformance, the evaluation harness and the technical reference map. A passing structure or integrity check is not proof of correctness, freshness or official endorsement.
Dated review records
Historical reviews and postmortems retain the evidence and decisions at their stated dates. Follow current task guides for today's interface.
Research basis
Sources index and central bibliography records source identities, versioned citations and retained-copy fingerprints. Follow each entry's review links for analysis and its source links for retrieval.
Corpus Map implications for OKF+ and Microsoft reviews entity navigation, the existing bundle design, Microsoft integration routes and a bounded evaluation before adoption.
Curated bounded evidence package research retains the research briefs, reports and reconstructed examples with their provenance and limits. The BEP implementation status separates existing code from research proposals and remaining gaps.
Research and public-service references explain the method. The documentation style guide sets British English and plain-language conventions.
Public URLs
Use the example catalogue for named experiences,
readiness, limits and the date of verified journeys. govuk-webmcp remains an
external frozen competition candidate.
Review on 14 November 2026
Feature, plan and acceptance status distinguishes shipped code, experimental profiles, proposed functionality and independent acceptance. Standards/source consolidation is producer-compatible; typed datetime, richer spatial rules and CSV previews need a separately versioned optional contract. WCC follow-up remains parked.
The unreleased v2 candidate and local CSV preview add bounded datetime/spatial checks on a separate versioned route. Frozen RC.1 and its historical trial evidence remain unchanged; no automatic estate migration or WCC follow-up is performed.