OKF bundle and lineage inventory

The machine scan selected 26 of 138 repositories. This human classification is essential because a keyword hit may be a source capture, a fixture, a viewer, a compatibility copy or a passing mention.

Published or substantial bundle producers

Repository Earliest located OKF marker Role at the review snapshot
api-mcp-wiki 23 June Early publication-ready OKF bundle and MCP/wikis bridge.
okf-explorer 4 July Canonical Explorer, AI-infrastructure sample bundle, Bundle Wiki profile, evaluation method and this review.
okf-uk-legislation 11 July Legislation bundle wiki and later whole-law federation work.
okf-uk-government-apis 11 July API catalogue bundle with DCAT/OpenAPI crosswalk and large-corpus projection.
okf-ai-infrastructure 11 July Independently published AI-infrastructure bundle.
okf-ons 17 July ONS discovery demonstrator and large-corpus exemplar.
20260720-hackathon 20 July Bounded ELS API discovery OKF.
okg-planning 25 July Planning bundle v0.2.0. The okg name is retained as repository history.
okf-govuk-content 25 July GOV.UK content bundle migrated to v0.2 and later bounded public demonstrator.
okf-LandRegistry 29 July HM Land Registry bundle and the main delivery-retrospective evidence.
okf-uk-living 7 August Citizen-journey/life-course corpus under a richer relationship-runtime contract.

Historical LLM-Wiki or pre-OKF lineage

ai-engineering-lab-hackathon-london-2026, mcp-geo, assertion-seelinks, Awesome-Code-as-Agent-Harness-Papers, cfte-discourse-corpus, wcc-mapping and wcc-domesday-map preserve the pre-OKF method: immutable or source-linked inputs, Markdown knowledge pages, indexes, provenance, human navigation and progressively better evaluation. Some later acquired OKF exports or viewers, but their historical value is the lineage rather than a present conformance claim.

Compatibility, export and access layers

Standards, research, fixtures and mentions

Important absences and limits

The scan only used tracked files in direct and one-level nested repositories under /Users/crpage/repos. It did not treat _site, build output, dependency trees or untracked documents as separate products. Remote-only branches, deleted repositories and private conversations may contain additional history. The JSON evidence preserves the exact selected paths and commit identities so another reviewer can challenge this classification.