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-emittedfromauthorised-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
b5918192b1e3969ca2b069a4d56b3d26884ea96cpeels 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 ingraph 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.