Technical guides and historical reference

Start with the task documentation. This index retains specialist guides, contracts and dated research. A historical report is not current user instructions or proof of a present deployment.

Technical guides

• Build and publish OKF bundles consistently defines the estate lifecycle standard; its implementation tracker records repository adoption, validation and publication. The generated OKF estate registry provides the current machine-backed repository view and optimisation backlog.
• OKF Explorer from the beginning is the contextual beginner reference. It introduces the web application, Markdown and OKF bundles, large-corpus loading, search, graphs, semantic-web standards, provenance, Explorer views, geospatial and legislation data, AI infrastructure, v0.2 trust, federation, Foundry authoring, governed enrichment, release gates, evidence receipts, owner review, release assurance, safety, testing and contribution workflow before routing into the advanced specifications.
• Repository guide explains where the important files live and how the publication pipeline fits together.
• Use the OKF Explorer remains the short path from a bundle URL to the hosted Explorer.
• UK Legislation documentation spine routes legal researchers, counsel, data engineers, curators and AI evaluators to task-specific guidance.
• Illustrated UK Legislation manual follows legislation-specific personas and user journeys from overview to selected-passage provenance.
• Illustrated Explorer manual describes the UI through user stories and screenshots.
• Geospatial Map personas and user stories explains who needs spatial discovery, what can go wrong and how each need is covered by browser tests.
• Illustrated Geospatial Map manual walks through evidence, place reductions, locator precision, record selection, bounded previews and progressive recovery.
• Static search and filtering manual illustrates deterministic search, multi-value filters, sorting, match explanations and durable retrieval URLs against the GOV.UK CKAN corpus.
• GOV.UK CKAN personas and user journeys links CKAN-specific user needs to all 100 questions and the executable interaction journeys.
• Use an AI with an OKF pack gives prompts and data-access rules for asking questions over a pack without losing provenance.
• SharePoint and Microsoft 365 Copilot trial reports a complete 293-family governed-retrieval development run: all 293 responses stayed inside the safety boundary and 292 selected the exact expected family. It also records the one near-neighbour exception, service protection, charging assumptions and the remaining independent-holdout and OneNote questions.
• Create OKF bundles explains how to build bundles that take full advantage of Explorer facets, search, graph, timeline, resources and right-card metadata.
• OKF Foundry prompt kit provides a general two-stage domain-research and build protocol, a versioned machine handoff and reusable assurance gates for any document or record collection.
• OKF authoring methodology review uses the Land Registry retrospective without reopening that pack, then adds human-readable graph labels, denominator-based semantic linking and a shareable Explore OKF feedback stage before candidate freeze.
• From LLM-Wiki to governed OKF bundle wikis reconstructs the complete evidence-backed journey through OKF 0.1, OKF 0.2, YAML-LD, Explorer, grounding, MCP and bundle discovery, and links to the inspectable review bundle and empirical context-retrieval receipt.
• Walk through the AI Infrastructure knowledge graph gives a no-code route through the best compact semantic example in GitHub and Explorer, then explains how to download the frozen bundle and open it as an Obsidian vault.
• OKF learner hub specification defines the researched 18-year-old learner persona, evidence-led pedagogy, cross-bundle information-worker stories, root-site architecture, performance contract and publication acceptance journeys.
• Project studio is an optional eight-stage course. A sourced answer or a reusable bundle is a useful outcome; the learning app stage is optional.
• Explore OKF profile is the strict, machine-tested contract for a snapshot-bound compact endpoint-label index and persistent exploratory-publication banner.
• Evaluation Foundry and YAML-LD adapts that process for functionality evaluation, explains additive semantic identity and assertions for beginners, and keeps source-backed, tiny and synthetic products visibly separate.
• Coventry and Warwickshire heritage fixture family links the evaluation profile, reversible mappings, executable journeys, question suite and three generated corpus roles.
• Facet presentation experiment defines provider and user control, compact distributions, hierarchy tabs and the optional presentation sidecar.
• Provider datapacks define how governed bundle snapshots, bounded reviewed upstream references, known drift and external provider actions remain visibly distinct.
• Federated OKF bundles define the overview-first control plane, child discovery and fallback routes, relationship authority classes and generator acceptance checks.
• Federated bundle wiki architecture defines independently published bundle wikis, YAML-LD/JSON-LD semantics, registry discovery, compatibility projections and the extraction plan.
• Ontology and semantic graph architecture separates RDF instances, RDFS/SKOS vocabularies, bounded OWL inference, SHACL validation, PROV/DCAT evidence and Explorer presentation, and records the predicate-aware graph delivery roadmap.
• YAML-LD relationship assertion mapping records how evidence-bearing semantic assertions project into the current Explorer relationship runtime and federation control-plane rows.
• YAML-LD default semantic layer implementation plan stages the move from semantic authoring to runtime-default loading without breaking existing JSON publication contracts.
• OKF 0.2 and YAML-LD semantic authoring is the executable cross-repository contract: one semantic source, rich directed assertions, generated projections, safe routes and Reader behaviour.
• OKF repository agent-guidance review explains the portable guidance design and the complementary roles of the nine reviewed repositories; the validated plugin source is under plugins/okf-repositories/.
• Source constraint ledger records fair-use, access-control, licensing and context-loading concerns for internal escalation without silently reducing prototype functionality.
• OKF standards crosswalk describes alignment for API and data-catalogue fields; it does not claim universal OKF fields or DCAT-AP conformance.
• 20 minute demo script is the prepared run of show-and-tell for the 2026-07-09 demonstration.

Quality And Review

• HM Land Registry v0.3.0 delivery retrospective records all 14 numbered producer attempts, the agent-created late defects, partial build and validation timings, unavailable token evidence, final publication and enforceable delivery improvements.
• OKF Explorer evaluation harness defines the 100-question scoring suite, accessibility checks, GOV.UK-aligned publication rubric and visual-regression evidence.
• Coventry and Warwickshire heritage evaluation report records the source scope, feature evidence, limitations, link checks, consumer journeys and the extra value provided by the YAML-LD extension.
• Heritage Evaluation Foundry engineering postmortem reconstructs the complete prompt-response, local-build, pull-request, deployment and release process; it identifies late-discovery amplification and proposes a dependency-planned, selective-rerun architecture.
• UK Legislation architecture documents the complete work catalogue, legal ontology, progressive provision resolver, official access methods and barrister-oriented AI evaluation contract.
• OKF pack parity keeps the UK Government APIs and GOV.UK CKAN packs aligned as paired exemplars.
• OKF conformance records the v0.2 core boundary, v0.1 compatibility fallbacks and additive Explorer profile.
• Explorer overview context specifies the generated overview/analysis contract consumed by the Explorer.
• Viewer capability parity inventories the LLM-Wiki and OKF viewer lineages, records the complete feature matrix, and makes every retained, ported, equivalent, conflicting or remaining capability explicit.
• Geospatial Map exploration specifies the deterministic Map canvas, spatial evidence levels, reduction state and progressive external-preview design; use the current Map manual for operational instructions.

Dated Review Records

• Code review, 2026-07-07 is the original review report. It is preserved as historical evidence and is superseded for current pack status.
• Code review follow-up, 2026-07-08 records the remediation, publication checks and current pack checkpoint.

Research Basis

The documentation and evaluation rubric are deliberately aligned with current public service guidance rather than only internal engineering preferences:

• GOV.UK Service Standard: understand users and their needs; solve a whole problem; make the service simple to use; make sure everyone can use it; use open standards and common platforms; protect privacy and security; define success measures; and operate a reliable service.
• GOV.UK accessibility guidance: services should meet WCAG 2.2 level AA, account for common assistive technologies, and use both automated and manual testing.

Useful references:

• GOV.UK Service Standard
• GOV.UK accessibility introduction
• GOV.UK Design System accessibility strategy
• Open data for the Explore OKF pilot recommends a bounded Coventry everyday-services slice for testing labels, official links, CPSV-AP/SKOS mappings and multi-resolution boundaries before the full okf-uk-living review.

Public URLs

Use the maintained example catalogue.