KYE Authority Pulse™ — what changed in the canon this week — 2026-W26

Executive tear-sheet

The KYE Authority Pulse™ is the weekly bulletin of what changed inside the KYE Protocol™ canon — new governance chapters, new frameworks under mapping, new commercial products, and new governed research editions. This is a mechanical digest: every item below traces to a canonical KYE™ artefact (a constitution chapter, a registry, or a sealed report), never to outside commentary. For the week of 16–22 June 2026 (edition 2026-W26), the headline is jurisdiction: two new constitutional chapters landed in the same window — one making where an action happens a first-class admissibility dimension, the other making unstructured-document citation a governed, replay-verifiable capability. Reporting on canonical KYE™ artefacts; not investment or compliance advice.

Key findings

• Two governance chapters adopted this week. §71 Document Intelligence Rail™ and §72 Jurisdiction & Data-Sovereignty Authority both carry an Adopted date of 2026-06-19 in their structured headers — the canon grew by two locked chapters in one week.
• Geography is now an admissibility dimension. §72 makes the jurisdiction of an action a first-class input to the moment-of-use decision, not a downstream compliance review — the same shape KYE Protocol™ already applies to purpose and authority.
• Citation became a governed capability. §71 brings navigating, retrieving and citing unstructured regulatory and policy documents under one governed, replay-verifiable contract — every extract pinned to a source, never a free-text paraphrase.
• The canonical registries keep their depth. The framework registry tracks 202 frameworks under mapping, the product registry declares 59 commercial products, and the Governed Research Rail library holds 12 published editions — the numbers a buyer can verify against the live registries.

What changed in the canon this week

TL;DR This section relays the canonical deltas for edition 2026-W26 as recorded in the source-of-truth registries; it does not characterise anything beyond what those artefacts state.

This section relays the canonical deltas for edition 2026-W26 as recorded in the source-of-truth registries; it does not characterise anything beyond what those artefacts state.

• §72 Jurisdiction & Data-Sovereignty Authority — Adopted 2026-06-19. The chapter makes geography a first-class dimension of admissibility: which jurisdiction an action touches, and which data-sovereignty regime governs it, become inputs to the <a href="/knowledge-graph.html">Action Admissibility™</a> decision at the moment it happens — rather than a separate, later jurisdiction review. The structured header records the lock and the adoption date.
• §71 Document Intelligence Rail™ — Adopted 2026-06-19. The chapter brings navigating, retrieving and citing unstructured documents (long regulatory prose, standards, policy PDFs) under one tenant-scoped, governed contract. Every cited extract is pinned to its source, so a claim drawn from a 400-page regulation is replay-verifiable rather than an unattributed paraphrase. It explicitly does not re-index KYE™'s own structured canon — that already has a deterministic index.
• Framework registry — 202 frameworks under mapping. The canonical framework registry continues to be the one source-of-truth root for every regime, framework and standard KYE™ maps to. The honesty bar holds: a mapping counts as enforced only with a cited KYE™ artefact, so the coverage number is never inflated.

What KYE Protocol™ reads into it (interpretation, not advice)

TL;DR This section is KYE Protocol™'s interpretation of the week's canonical deltas, clearly separated from the recorded facts above, and is not investment or compliance advice.

This section is KYE Protocol™'s interpretation of the week's canonical deltas, clearly separated from the recorded facts above, and is not investment or compliance advice.

• The admissibility surface is widening on purpose. Purpose, authority, and now jurisdiction are each becoming first-class inputs to the same moment-of-use decision. The pattern is consistent: governance is discharged when the action happens, not reconstructed afterwards — which is exactly what higher-risk regimes increasingly require of the deployer.
• Citation is a governance primitive, not a convenience. §71 treats "where did this claim come from" as a control, not a footnote. A governed answer that cannot name its pinned source is not a governed answer — the same no-hallucination discipline the Governed Research Rail applies to every <a href="/reports.html">published edition</a>.
• The registries are the receipts. A buyer evaluating KYE Protocol™ does not have to take a number on faith — the framework count, the product count, and the research-library count are each a query over a canonical registry the protocol governs itself against. The Pulse simply relays them.

How to verify this edition

TL;DR Every claim above is pinned to a canonical KYE™ artefact and listed in the sources below.

Every claim above is pinned to a canonical KYE™ artefact and listed in the sources below. This edition is Ed25519-sealed over the published keys: fetch the published JWKS, recompute the signature over the canonicalised envelope bound to this body's hash, and confirm it matches — from public keys alone, no KYE™ service in the loop. The KYE Authority Pulse™ ships weekly; whether and how any canonical delta applies to a given organisation is a matter for that organisation's own advisers.