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.