OKF Explorer v0.7.0

OKF Explorer v0.7.0

OKF Explorer v0.7.0 turns the Land Registry delivery retrospective into a
governed Explore OKF authoring and review method. It supports readable,
semantically linked research snapshots that can be shared for feedback while
remaining visibly exploratory rather than being mistaken for an authoritative
service or released data product.

Highlights

• PR #96 adds the
  versioned Explore OKF profile, strict JSON Schemas, producer tooling, worked
  examples and authoring guidance. Semantic-link coverage is measured against
  an identity-bound eligible-entity denominator, with evidence, authority,
  namespace and dereference checks that fail closed.
• Explorer now consumes integrity-bound endpoint labels across route-based
  views, presents missing governed labels as a visible quality defect, retains
  raw routes and IRIs for inspection, and preserves source-native routes and
  selected relationships in copied links, reloads and browser history.
• A persistent exploratory banner, noindex policy and exact-view feedback
  link remain available across Reader, Graph, Links, Timeline, Type, Resources,
  Map and Narrative. Malformed or mismatched exploratory contracts produce an
  explicit warning rather than an ordinary release presentation.
• The beginner learning path now scrolls independently, can collapse to an
  accessible current-chapter rail, supports hover, keyboard and persistent pin
  behaviour, and restores exact section fragments after reload.
• PR #98 preserves
  hidden publication files, including .nojekyll, in the unchanged Pages
  artefact so its complete Site tree can match the candidate receipt.
• PR #99 separates
  the editable bundle-URL draft from the accepted descriptor identity. The
  accepted remote response URL or selected local-file identity is bound before
  later validation or subordinate hydration can fail, so feedback always names
  the material actually under review. Delayed start-up, URL loads and local
  file reads are request-ordered: stale work cannot replace a later choice,
  clear its loading state or leak unsubmitted URL text into shared links.
• The governed Python baseline uses CPython 3.12.11, uv 0.12.2 and the
  committed uv.lock for Explorer development and CI. The legacy Heritage
  requirements file remains only at its explicit compatibility boundary.

Verification

• Exact merge commit: bc40b05fe3ab350ce6cf764c9e37f63187509d86
• Exact-head CI: run 31631037948
• Exact-merge Pages deployment: run 31632362417
• Pages artefact SHA-256: 13ddbd1102e6099207fe24c7034ea6e948309630b3c1d0d1d25bbddc4c3c769b
• Pages candidate-receipt ZIP SHA-256: 96ff9786445aca7929beac141343e560593ed6bf81fb65bf824b8a82d0d5ca1f
• Extracted candidate-receipt SHA-256: bc4142e0dfc6a54022ca349afadf69314b659f79a50ca01dfec9ccf2a0c8dcd8
• Deployed application-manifest SHA-256: bc602cb3f189fbe9ccc10779061396e2c77f925668cb3115446a1646fc45ed69
• Deployed application tree SHA-256: 0489fddd63a953a952eaad49f9e79aed1ddd4cb76538545b1e83976eb9737bd7
• Complete Site tree SHA-256: aefdf756871e3ada9a2567a1ef8b1a0e1df1d564cd01394f255965702a176788
• Public-verification receipt SHA-256: 49e20168347aac8d91ac845840187d3ba537a445c4c00838095c33160811dc4c
• Public Google Chrome journeys: 21/21 Explorer tests and 5/5 learning-path tests passed in Google Chrome 151.0.7922.137 with no recorded page or browser-console errors.

The final evidence must bind these values to one exact merge, prove that the
downloaded Pages artefact and deployed files are byte-identical where required,
and record passing genuine-Chrome journeys with no page or browser-console
errors.

Boundaries and limitations

• An Explore OKF snapshot is incomplete research evidence, not official advice,
  a complete service inventory or a release approval. Promotion requires a
  newly reviewed candidate; exploratory bytes are not silently relabelled.
• Mechanical coverage and dereference checks cannot prove that a domain review
  identified every eligible entity or chose the best semantic predicate.
• Loading a bundle does not make it an ontology. Explorer does not fetch
  arbitrary remote contexts or perform unbounded OWL inference in the browser;
  richer hierarchy, SKOS, provenance, validation and asserted-versus-inferred
  views remain future work.
• This release does not rebuild Land Registry or republish the independently
  governed Heritage and live UK Government API producer inventories.

Release assets

The immutable release must contain exactly these three assets:

1. okf-explorer-v0.7.0-pages-artifact.zip — the unchanged exact-merge
   github-pages Actions artefact.
2. okf-explorer-v0.7.0-sbom.cdx.json — the checked CycloneDX SBOM, renamed
   without changing its bytes.
3. okf-explorer-v0.7.0-public-verification.json — the digest-bound public
   deployment and genuine-Chrome verification receipt.

OKF Explorer v0.6.3

OKF Explorer v0.6.3 corrects large-corpus record presentation without changing
producer data or weakening legacy bundle compatibility.

Highlights

• Reader overview metrics now prefer a producer's declared counts.records
  before the legacy counts.datasets fallback.
• The unloaded Timeline heading applies the same distinction, so dataset
  groupings are not labelled as records.
• Zero remains a valid declared count, and older bundles that publish only a
  dataset count retain their established fallback.
• Cross-browser tests use genuinely divergent counts and cover Reader,
  Timeline and the legacy fallback.

Verification

• Merged through PR #91
  as c6c8ccd9daaab7600ce8261d0eca587acabf917b; its Git tree is
  76a7215da9592207c8769a0db437113ef80810cf and is identical to the fully
  tested branch head.
• Annotated tag object 3ccddb8a40ca509a4219623b55fd8409341a6111
  peels to that exact merge.
• Exact-head CI run
  31548806154
  passed every selected gate: 342 Vitest checks, 78 Node contract checks, 356
  Python checks and the full Chrome, Firefox and WebKit terminal suite.
• The final 30 targeted large-corpus browser cases passed across all three
  engines. Heritage evidence also passed 100/100 governed questions at or
  above 80, with a 92.7 average, and all three local journeys.
• Deterministic application tree:
  03b482117351213a1eecb405e8542365bd7693b55e58b46ace85921c5a975e53;
  build-manifest SHA-256:
  681498b253d1c1aba7749d8fc942bdc74a5fc412c897ab9bc13e0369ac558652;
  deterministic Site candidate tree:
  80903987badc77f24b93ac305f1f8ccf4cf88c89d6b229df2b56b15b163853cf.

Deployment and public verification

• Pages run
  31549668889
  deployed the exact merge successfully.
• A fresh, service-worker-blocked Chromium session loaded the published HM Land
  Registry v0.3.0 descriptor and rendered 2,203 records, 2,203 official
  sources and 22,267 relationships. Timeline also rendered 2,203 records,
  rather than the 14 dataset groupings.
• The governed exact boundary search result was present, and the separate
  semantic deep link rendered 15 relationships including translation of
  through the runtime manifest, governed route locator and relationship shard,
  without adjacency fallback. Console and network checks were clean.
• The scoped public receipt SHA-256 is
  3511e132a6b3b6d8348f750e977addbccacd5b0b16ba610a2b7c7102b95ce53c;
  its verifier SHA-256 is
  6fcf8f80f213f4a5d5b0ac827a118733bf800136fbe9163b617c7ba0cc98aa66.

No manually attached runtime-evidence asset is required for this source and
presentation-correction release.

OKF Explorer v0.6.2

OKF Explorer v0.6.2 adds an exact, opt-in producer query policy and settled-search acceptance without weakening legacy strict-AND bundles.

Highlights:

• OKF static-search v2 producers can declare component tokenisation, bounded stopwords and integer-rational minimum-should-match;
• unresolved query groups remain unmatched and no unbounded OR fallback is introduced;
• external journeys can wait for and assert a ranked result by credential-free canonical URL after the exact query settles;
• local Heritage evidence now binds the exact served Explorer build manifest and evaluator executable;
• legacy manifests without query_policy retain their established search behaviour.

Verification:

• merged through PR #88 as 9430b3931f96bd9e6e06165c15b522742611f3e9;
• annotated tag object 43e53f36d869ba7ca2420990191a0834a969dcd2 peels to that merge;
• PR CI run 31521815001 passed every selected gate, including 356 Python checks, 342 Vitest checks, 78 Node checks and the full Chrome, Firefox and WebKit terminal suite;
• deterministic application tree: 85c8fd14f085e888670edc05980f6ae355fabd5d1d73579007c5c968dac4585e;
• local Heritage evidence: 100/100 questions at or above 80 with a 92.7 average, plus 3/3 governed interaction journeys;
• deterministic Site candidate tree: ec402ba42b8f69b72c14e9c3555f23bb1b80746dc03bc5eaf866c8840baa2ade.

Deployment and public verification:

• Pages run 31522807598 deployed the exact merge successfully;
• the live build manifest SHA-256 is 30e41e79cbd3dba525fafdd42979a227b88d85328a7ae3bdd200456c7b629c83 and declares the exact application tree above;
• a post-deployment Chromium journey loaded the public UK Government APIs bundle, searched for osdatahub.os.uk, opened OS Maps API, selected Graph, selected the published by relationship and resized its relationship drawer; all actions and assertions passed;
• the public journey result was generated at 2026-08-11T18:41:35.135000Z by evaluator SHA-256 72cabd844d29c441aa9ac1e42748eb38c1a8ec803b2c7f0479a4da89fcca98dc; its local receipt SHA-256 is a8f41ea8066bd98426f8d79f49a60e4eac08daddc375de39c7bed545b5b81b01.

No manually attached runtime-evidence asset is required for this source and contract release.

OKF Explorer v0.6.1

OKF Explorer v0.6.1 releases the additive Predicate Registry v2 profile, hardened external-bundle acceptance and richer ranked-result evidence without changing the frozen Bundle Wiki v1 profile.

Highlights:

• Predicate Registry v2 distinguishes active-emitted from authorised-zero-evidence, reconciles exact assertion counts and rejects undeclared emissions;
• generic and legislation acceptance use checkout-scoped single-writer execution, deterministic build attestation, immutable snapshots, finite limits and durable write-once evidence;
• ranked canonical-URL observations, natural-language organisation recognition, accurate capped-result uncertainty and rich review-status preservation;
• complete Heritage producer-material provenance and rebound faithful, tiny and synthetic evaluation evidence;
• the historical 26 July v1 runtime receipt is preserved byte-for-byte as explicitly non-authoritative archive material.

Verification:

• merged through PR #85 as 839d4ba4c2d02abc6ef02b3ca1dcbf6a4008e7c8;
• annotated tag object b5918192b1e3969ca2b069a4d56b3d26884ea96c peels to that merge;
• PR CI run 31489615021 passed every selected gate, including 355 Python checks, 317 Vitest checks, 74 Node checks and 171 Chrome/Firefox/WebKit journeys;
• Pages run 31490655161 deployed the exact merge commit;
• deployed Predicate Registry v2 lock SHA-256: 3d1f7cdbb423628f3938e5aef299ae09013f56be515ff2155475c5325ffd0110;
• deployed Predicate Registry v2 schema SHA-256: 037151379a1ec0cbfe0666d41592585a891a63929f1fcf2845d1eb3de8dd5069;
• a post-deployment real-browser journey loaded the public tiny Heritage bundle, searched and opened a ranked record, rendered its directed located in graph and produced no console errors or warnings.

Release boundary:

This is deliberately a source/profile release with no manually attached runtime-evidence asset. The current legislation semantic projection is not yet a clean, frozen Git candidate, so an exact tag-bound Predicate Registry v2 legislation receipt cannot honestly be produced yet. That receipt and its complete adjacent evidence tree belong to the legislation producer's later independent release evidence; a partial JSON file is not attached here. The release does not claim that the current UI visibly presents all authorised-zero-evidence capabilities or that every loaded bundle is an ontology.

OKF Explorer v0.6.0

What's Changed

• Wait for the tiny fixture record ready state by @chris-page-gov in #63
• Explain Foundry release gates for beginners by @chris-page-gov in #64
• Build Coventry and Warwickshire heritage Evaluation Foundry by @chris-page-gov in #67
• Complete Coventry and Warwickshire heritage Evaluation Foundry by @chris-page-gov in #68
• Promote verified heritage Evaluation Foundry exemplar by @chris-page-gov in #69
• Implement modular heritage Evaluation Foundry publication by @chris-page-gov in #70
• Improve Explorer graph navigation and responsive controls by @chris-page-gov in #71
• build(deps-dev): bump the okf-explorer-stack group across 1 directory with 2 updates by @dependabot[bot] in #65
• build(deps-dev): bump @playwright/test from 1.62.0 to 1.62.1 in /apps/okf-explorer by @dependabot[bot] in #66
• Add large-record narratives and typed source access by @chris-page-gov in #72
• Publish OKF 0.2 semantic relationship contract by @chris-page-gov in #75
• Release Explorer v0.6.0 by @chris-page-gov in #78

Full Changelog: v0.5.7...v0.6.0

Coventry and Warwickshire Heritage Evaluation Exemplar

Immutable publication and evidence home for the Coventry and Warwickshire OKF Explorer Evaluation Foundry exemplar.

Frozen identity

• Promoted commit: 0b5d748
• Successful GitHub Pages run: 30819232224
• Faithful corpus: 7,640 records (6,556 NHLE and 1,084 Heritage at Risk), 22,200 resources, 9,566 relations
• Descriptor SHA-256: 2b06dc70e8d1943e18617d4edcb09bd5041ff8f7b7611828d1c9d24070b37149
• Plane-roots SHA-256: 21b38c4c0ed48ecba11f5dc5629e798fed52ed11ddd130d6ae2ade05121808f3
• Release root SHA-256: 83b6be80cc009a23142ca946b2bad515fa14c149ea4222b4b2bf1035a3ea2e7e

Terminal public gate

Observed 2026-08-03T13:47:21.278Z against the exact deployed descriptor and release root: 1/1 journey, 32/32 actions and 2/2 assertions passed. Evidence comprises 21 live-browser actions and 11 identity-bound genuine-browser receipt actions, including the release page, faithful/tiny/synthetic Explorer entries, rendered Markdown-to-HTML routes, all report-authored external and rich pages, and cited GitHub run/commit identities.

• Terminal JSON SHA-256: 9083035ceb13cfda74d7134d77b424704c6c14a0982d756b34700a04d06661a6
• Initial candidate JSON SHA-256: 36bcc3f2e31a7dcc73c793d4a44a12492a717d321f30926685341e45ea3ee1f4
• Local candidate receipt SHA-256: 2173bfcbadd4b6cecbc4165b70ec1974ba5fb99420495df374df136ab865c3ab
• Protected-source receipt SHA-256: 32c5ad4b1465c136f0955a12001011e3116eed8b9e2e801bee82ad37bcdaa786

The attached receipts are outside the verified Site tree, so recording terminal evidence does not mutate the publication it verifies. The tag source archives freeze the Explorer, corpus, OKF bundle, compatibility viewer, documentation, and producer/validation code at the promoted commit.

OKF Explorer v0.5.7

What's Changed

• Fail closed on malformed large-corpus descriptors by @chris-page-gov in #62

Full Changelog: v0.5.6...v0.5.7

OKF Explorer v0.5.6

Consumer-proof Foundry hardening release.

• Adds a stable real-browser external bundle acceptance harness.
• Records bundle identity, requests, console output, restored state and terminal outcome.
• Adds fail-safe new-repository bootstrap tooling and profile lifecycle controls.
• Requires concrete dependency-graph test paths and a 60-second tool-first public URL gate.

The release tag points to merged commit 3581703. PR and post-merge Pages workflows passed, followed by a real-browser deployed identity, search-state and zero-console-error check.

OKF Explorer v0.5.5

Bounded relationship navigation and AI-readable UK Legislation guidance.

• Replaces the misleading full-relationship action on large facet cards with exact match totals, bounded previews, and derived Graph/Links projections.
• Loads a selected record through route-scoped core adjacency and governed model-assisted enrichment while retaining the browser memory guard.
• Adds copy-ready AI traversal guidance and records the current effects-index and semantic-publication limitations honestly.
• Publishes synchronized release metadata and a 136-component CycloneDX SBOM.

Validated by the protected CI gate across Chrome, Firefox and WebKit, semantic and fixture generators, OKF conformance, deterministic builds, documentation link crawling, and Foundry Pages tests.

Known publication limitation: official-effects assertions remain release-wide rather than source-and-target route-indexed. The UK Legislation operational descriptor reports 0.3.0 while root YAML-LD and JSON-LD representations still carry stale 0.2.0 bundle metadata; this release documents that inconsistency rather than masking it.

OKF Explorer v0.5.4 — Pages artefact closure

Corrective release for the independently observed v0.5.3 Pages packaging mismatch.

• Preserves the deterministic Svelte fallback during final site assembly.
• Rehashes every manifest-declared application material after assembly and before Pages upload.
• Rejects missing, changed, linked, and undeclared application namespace files.
• Synchronizes the release-bound runtime and SBOM with v0.5.4.

Protected CI run 30228300676 passed the deterministic build, 244 unit tests, 20 Node contract tests, 82 Python tests, YAML-LD/OKF checks, and 141 Chrome/Firefox/WebKit journeys. Pages run 30228627196 passed and deployed commit a23dfde.

The exact 185,023,908-byte Pages artifact is attached as okf-explorer-v0.5.4-pages-artifact.zip with SHA-256 357c2fcfbdb4fda34a830d933feb290dd8980cc61b0a82f51cd5e0e5a226c1c0. Independent archive verification reconciled its 9,980-member TAR, 16-file application manifest, root index, and preserved 1,122-byte fallback without mismatch.