# `okf-domain-profile.v1` review handoff

This handoff accompanies the machine-readable
[`okf-domain-profile.v1.yaml`](okf-domain-profile.v1.yaml). The repository owner
approved the profile and three fixture contracts on 2026-08-07, and later that
day explicitly authorized the exhaustive link-only reference-family inventory
and the governed 293-family corpus-acquisition policy.
Neither decision creates a production ontology or an authority claim.

## Approval record

Approved by `owner:chris-page-gov` on 2026-08-07 as the boundary for the first
three vertical slices. A second explicit owner instruction on the same date
authorized exhaustive discovery of external reference families with URLs,
owners, jurisdictions, dates, licence evidence, original summaries and a gap
analysis. It does not authorize snapshots, source-content redistribution,
unbounded or unstaged leaf acquisition, public publication, personalized decisions or
unsupported four-nation equivalence.

## Fixed scope

The first denominator is three slices:

1. missed rubbish collection;
2. learning to drive through one enforcement exception; and
3. death and bereavement through Tell Us Once and estate administration.

Each must exercise ordinary and exception paths, jurisdiction, provider,
authority, evidence, governing rules, time, outcome, redress, provenance and
any necessary private-sector dependency. The broader reference-family layer is
now inventoried across all 24 domains and five reference jurisdictions. The
owner-approved [293-family denominator](../source/service-family-denominator.v1.yaml)
defines three staged reference-acquisition waves. It authorizes link
registration and coverage research against those names, not source snapshots,
copied content or unbounded acquisition.

## Semantic and authority boundary

The central model is life event or situation → user need → public service →
service episode → outcome. Person roles, providers, jurisdictions, rules,
evidence, channels, costs, artefacts, time and redress provide context.

The bundle explains and navigates. It does not make an individual eligibility,
medical or legal decision. Similar labels do not establish shared identity,
and a GOV.UK route does not establish that a process applies uniformly in all
four nations.

## Standards decision

- OKF 0.2 is selected for the authored bundle conventions.
- CPSV-AP 3.2.0 and Open Referral UK are mapping references; conformance is not
  yet claimed.
- SKOS, OWL/RDFS, PROV-O and SHACL have planned, distinct roles.
- The current Explorer small-bundle compatibility contract remains
  provisional until actual consumers are inventoried.

## Assertion and provenance decision

Every material assertion is one of `official`, `normalized`, `inferred` or
`editorial-example`. Official status requires direct support from an identified
authority within its scope. Generated relationships remain inferred and are
never presented as official. Unknown is not false.

Source identity, jurisdiction and observation time are required. Each source
family declares its update cadence, rights, coverage and limitations. The
[rights register](../source/rights-decisions.v1.yaml) records the dated licence
evidence for all 25 registered source hosts plus the standards and Explorer
references. The [exhaustive inventory](../source/exhaustive-reference-inventory.v1.yaml)
contains 89 new references and includes the 53 implemented-slice references.

## Remaining gates

The repository and current source-family licensing gate is complete:

- repository-authored code, documentation and ontology terms use MIT;
- source content remains linked and summarized rather than redistributed;
- no snapshots have been acquired or approved for redistribution; and
- eligible repository-authored generated projections use MIT without
  relicensing embedded upstream expression.

The [gap analysis](../research/exhaustive-reference-gap-analysis.md) accounts
for all 120 domain/reference-jurisdiction cells: 96 national cells have an
authoritative discovery family and 24 local cells remain partial. These
implementation gates remain open:

- the governed predicate registry and SHACL shapes; and
- the approved authority, service-family, regulator and redress mappings;
- named legal and clinical reviewer acceptance for affected production-grade
  claims.

The OKF Explorer 0.5.7 consumer contract is locked for local evaluation. The
three-slice remediation review and the 293-family colour-facet review pass;
neither result authorizes candidate freezing or publication.

The [corpus acquisition policy](corpus-acquisition-policy.v1.yaml) closes the
local-coverage, identifier, health-permission, regulator-first and redress
policy questions. It records role-based review nominations without inventing
individual legal or clinical reviewers. The exhaustive current-authority
registry, service-family responsibility and regulator/redress mappings remain
implementation work; named legal and clinical reviewers must accept affected
production-grade claims. Licensing completion does not authorize publication;
that remains a separate explicit owner decision.

## Review checklist

- [x] Scope and denominators are acceptable.
- [x] Users, tasks and authority boundary are acceptable.
- [x] Jurisdiction and assertion-status rules are acceptable.
- [x] Standards roles do not overclaim conformance.
- [x] Rights, privacy and freshness gates are acceptable.
- [x] Explorer consumer-lock assumptions are acceptable as provisional.
- [x] The dependency graph orders implementation and publication correctly.
- [x] The three [fixture contracts](../evaluation/fixtures/README.md) are an
      adequate acceptance boundary.

All three bounded linked-reference registers and vertical slices are now
implemented for review, and the exhaustive external reference-family inventory
is complete against its declared denominator. This does not authorize source
snapshots, unbounded or unstaged leaf acquisition, broad corpus assertion
publication or public deployment, which remain disabled by the profile.

## Full-population authorization

On 2026-08-08 the owner authorized the implementation plan for all 293 named
families. The machine-readable
[`life-course-population-contract.v1`](life-course-population-contract.v1.yaml)
now permits staged dossiers, linked-reference registration, governed semantic
projections and local Explorer evaluation. It retains zero snapshots, no
source-content redistribution, no personalised decision logic, no remote CI
and no publication. Population-complete may include visible specialist-review
warnings; release grade remains gated on named reviewer acceptance.
