Skip to main content

Review material. This is exploratory research, not an authoritative service or released data product.

# Explore OKF public-review authorisation

Status: authorised for manual GitHub Pages publication

Decision date: 13 August 2026

Owner: `owner:chris-page-gov`

## Decision

The owner authorised publication of the exploratory interface and its detailed learning documentation on the existing GitHub Pages site so that the concept can be shared publicly for review.

The authorised review surface is:

- a provider-neutral review hub at the Pages root;
- the secure standalone Explore OKF journey interface;
- a beginner-readable learning plan and curated detailed documentation;
- a deterministic HTML-first AI catalogue and one small complete retrieval record per governed family, generated from the same projection;
- the additive machine-readable descriptor, projection, labels, schema and manifest; and
- links to the unchanged full OKF Explorer and evidence-bearing publication.

## Boundaries retained

This authorisation does not:

- make the corpus or interface release grade;
- record specialist acceptance for any service family;
- claim coverage of every UK public service or local variation;
- turn AI-evaluation calibration evidence into a performance claim;
- authorise automatic deployment on push or merge;
- authorise a corpus, relationship-runtime or source-acquisition rebuild; or
- label any URL verified before exact deployed-byte and real-browser checks pass.

The deployment must retain the explicit exploratory warning, noindex policy, zero-source-snapshot boundary and manual `EXPLORATORY-NOT-RELEASE-GRADE` acknowledgement.

The AI-retrieval pages are a transport projection only. They do not create a second semantic authority, acquire source bodies, permit personalised data or relax the official-source and specialist-review boundaries.

The owner's follow-up request to make the review site and its beginner documentation publicly usable also authorises a documentation-only re-freeze of the browser handoffs for `CHANGELOG.md`, `README.md`, `REPOSITORY_STATUS.md` and `TRACKING.md`. The new base manifest may change only those four permitted transport targets. Every corpus, descriptor, graph, assurance and source-evidence target must retain its previously frozen bytes.

## Publication shape

The frozen base Pages publication remains the source for every existing target except `index.html`. The additive overlay may replace that one target only when its previous SHA-256 matches the frozen manifest. All other public-review files must be non-colliding, hash-pinned additions.

The root replacement exists only to make the already authorised review routes discoverable. It does not modify the preserved base bundle descriptor or any corpus, search, semantic, assurance or relationship-runtime byte.

## Completion gate

After the exact protected-main commit is deployed, verify at least:

1. the root review hub and its coverage wording;
2. the `/learn/` learning route and local documentation links;
3. the `/explore/` page identity and projection digest;
4. `missed bin` and `find NHS dentist` alias searches;
5. nation-route emphasis, ordinary and exception ordering, provenance and an official-source handoff;
6. keyboard access and visible focus;
7. absence of unexpected active network requests; and
8. the deployed base and overlay manifest identities.

Only after these checks pass may the exact URLs be described as verified.