HM Land Registry — Registration & Digital Identity Standard (Safe Harbour)

HM Land Registry — Registration & Digital Identity Standard (Safe Harbour) — 50% of in-scope requirements covered.

4 requirements · 3 in scope (3 designed) · 1 out-of-scope (outside KYE™’s authority layer). The 50% is weighted over the in-scope base.

HM Land Registry: requirement → the KYE™ artefact that enforces it

Demo data

You learn: Which requirements KYE™ enforces at runtime and with which artefact. You can: Walk the requirements.

  1. digital-identity-admissibility · designed

    Digital-identity verification action admissibility (Safe Harbour)

    Rule packs: kye:rule-pack:property-transaction-authority · Audit events: kye.evidence.pack.v1 · Constitution: 12 purpose permission

  2. application-submission-authority · designed

    Application-submission authority

    Rule packs: kye:rule-pack:property-transaction-authority · Constitution: 12 purpose permission, 21 delegated auditability

  3. replay-submission-record · designed

    Replay-derivable submission record

    Rule packs: kye:rule-pack:property-transaction-authority · Audit events: kye.evidence.pack.v1, kye.replay.context_seal.v1 · Constitution: 13 resilience loop

  4. identity-check-determination · out-of-scope

    The conveyancer's identity-check determination — out of scope

    (no enforcement cited)

How this widget is built
Demonstrates
KYE™ Compliance Mapping Rail™
Components
  • Framework requirement (clause)
  • Coverage status
  • KYE™ enforcement artefact (event, decision-record field, Evidence Pack™ entry)
Flow
Clause → status → the KYE™ artefact that enforces it, enforced requirements first. Architecture diagram
Used on

Source: HM Land Registry — registration requirements and the Digital Identity Standard (Safe Harbour) for verifying the identity of parties to a registrable disposition in England & Wales. KYE Protocol™ governs the AUTHORITY of an AI agent to take a digital-identity-verification or application-submission action and the Safe Harbour EVIDENCE / replay boundary; KYE™ does NOT perform the identity check determination, run the verification technology, or determine HMLR registration correctness. Bound to the property-transaction sector pilot. Paraphrased for mapping purposes only — see the official HM Land Registry guidance for the authoritative text. · License: HM Land Registry guidance is Crown copyright; KYE™ registry paraphrases each requirement's intent and cites the official standard for mapping purposes only.

By category

CategoryReqsEnforcedDesignedAdvisoryDeferredCoverage
Digital identity (Safe Harbour) — admissibility & evidence2020050%
Application submission — authority & record1010050%
Identity-check determination100000%

Every requirement → the KYE™ artefact that enforces it

IDTitleStatusKYE™ enforcement
hm-land-registry.digital-identity-admissibilityDigital-identity verification action admissibility (Safe Harbour)designedrule_packs: kye:rule-pack:property-transaction-authority
dictionaries: internal
audit_events: kye.evidence.pack.v1
constitution_refs: constitution/12-PURPOSE-PERMISSION.md
hm-land-registry.application-submission-authorityApplication-submission authoritydesignedrule_packs: kye:rule-pack:property-transaction-authority
constitution_refs: constitution/12-PURPOSE-PERMISSION.md, constitution/21-DELEGATED-AUDITABILITY.md
hm-land-registry.replay-submission-recordReplay-derivable submission recorddesignedrule_packs: kye:rule-pack:property-transaction-authority
audit_events: kye.evidence.pack.v1, kye.replay.context_seal.v1
constitution_refs: constitution/13-RESILIENCE-LOOP.md
hm-land-registry.identity-check-determinationThe conveyancer's identity-check determination — out of scopeout-of-scope(no enforcement cited)

Canonical KYE™ surfaces referenced on this page: KYE Protocol™.