---
title: "KYE™ Authority Pulse™ — what changed in the canon this week — 2026-W26 · KYE™ Research Library™ · KYE Protocol™"
description: "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…"
url: https://kyeprotocol.com/library/kye-authority-pulse-2026-w26/
lang: en
source: "KYE Protocol"
---

> 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…

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

seriesRoadmap to AI Governance formatTrends sectorcross-sector audienceGeneral cadenceWeekly Free edition

[How verification works](https://kyeprotocol.com/trust-self-audit/#verify) [Evidence Pack™](https://kyeprotocol.com/evidence-pack/) [KYE Protocol™](https://kyeprotocol.com/)

**Ed25519-sealed** · fingerprint `0e0907173e7e8385` · verify it yourself ↓

KYE Protocol™ governs actions and authorities, not outcomes, diagnoses, or results. This report synthesises public sources under the evidence / no-hallucination gate — every claim below is pinned to a cited source.

Share this report [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fkyeprotocol.com%2Flibrary%2Fkye-authority-pulse-2026-w26.html) [X](https://twitter.com/intent/tweet?url=https%3A%2F%2Fkyeprotocol.com%2Flibrary%2Fkye-authority-pulse-2026-w26.html&text=KYE%20Authority%20Pulse%E2%84%A2%20%E2%80%94%20what%20changed%20in%20the%20canon%20this%20week%20%E2%80%94%202026-W26&via=kyeprotocol) [Telegram](https://t.me/share/url?url=https%3A%2F%2Fkyeprotocol.com%2Flibrary%2Fkye-authority-pulse-2026-w26.html&text=KYE%20Authority%20Pulse%E2%84%A2%20%E2%80%94%20what%20changed%20in%20the%20canon%20this%20week%20%E2%80%94%202026-W26) [WhatsApp](https://wa.me/?text=KYE%20Authority%20Pulse%E2%84%A2%20%E2%80%94%20what%20changed%20in%20the%20canon%20this%20week%20%E2%80%94%202026-W26%20https%3A%2F%2Fkyeprotocol.com%2Flibrary%2Fkye-authority-pulse-2026-w26.html) [Facebook](https://www.facebook.com/sharer/sharer.php?u=https%3A%2F%2Fkyeprotocol.com%2Flibrary%2Fkye-authority-pulse-2026-w26.html) [Email](mailto:?subject=KYE%20Authority%20Pulse%E2%84%A2%20%E2%80%94%20what%20changed%20in%20the%20canon%20this%20week%20%E2%80%94%202026-W26&body=KYE%20Authority%20Pulse%E2%84%A2%20%E2%80%94%20what%20changed%20in%20the%20canon%20this%20week%20%E2%80%94%202026-W26%0A%0Ahttps%3A%2F%2Fkyeprotocol.com%2Flibrary%2Fkye-authority-pulse-2026-w26.html)

## 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.

## Claims → sources — every claim mapped to a pinned source

This is the claims→source map: no claim ships without a cited, pinned public source (evidence gate). Each numbered claim below is pinned into this edition's sealed evidence pack `kye:evidence-pack:kye-authority-pulse-2026-w26`.

1. Constitution chapter §72 (KYE™ Jurisdiction & Data-Sovereignty Authority) carries a structured header Adopted date of 2026-06-19, making geography a first-class dimension of admissibility evaluated at the moment of use. https://kyeprotocol.com/constitution/72-jurisdiction-data-sovereignty — _KYE Protocol™ Constitution — chapter 72 (locked, Adopted 2026-06-19)_ (retrieved 2026-06-22T00:00:00Z)
2. Constitution chapter §71 (KYE™ Document Intelligence Rail™) carries a structured header Adopted date of 2026-06-19, bringing navigating, retrieving and citing unstructured documents under one governed, replay-verifiable contract with every cited extract pinned to its source. https://kyeprotocol.com/constitution/71-document-intelligence-rail — _KYE Protocol™ Constitution — chapter 71 (locked, Adopted 2026-06-19)_ (retrieved 2026-06-22T00:00:00Z)
3. The canonical KYE™ framework registry (the §70 source-of-truth root) tracks 202 frameworks, regimes and standards under mapping, with a mapping counted as enforced only when backed by a cited KYE™ artefact. [https://kyeprotocol.com/frameworks.html](https://kyeprotocol.com/frameworks/) — _KYE Protocol™ Framework Registry (kye:registry — §70 Framework Mapping Rail)_ (retrieved 2026-06-22T00:00:00Z)
4. The canonical KYE™ product registry declares 59 commercial products, each a kye.product.v1 entry that fans out across the platform layers. https://kyeprotocol.com/products.html — _KYE Protocol™ Product Registry (kye.product.v1 — §68 Total Productisation Fan-Out)_ (retrieved 2026-06-22T00:00:00Z)
5. The KYE™ Governed Research Rail™ library holds 12 published research editions, each a sealed kye.research\_report.v1 instance whose claims are pinned to cited public sources. [https://kyeprotocol.com/reports.html](https://kyeprotocol.com/reports/) — _KYE Protocol™ Governed Research Library (§62 Governed Research Rail)_ (retrieved 2026-06-22T00:00:00Z)
6. Every KYE™ Governed Research Rail™ edition is Ed25519-sealed over the published JWKS, so any reader can verify the seal offline from the published keys alone without any KYE™ service in the loop. https://kyeprotocol.com/trust/self-audit-jwks.json — _KYE Protocol™ published JWKS (/trust/self-audit-jwks.json — §0.4 Replay-Proof™)_ (retrieved 2026-06-22T00:00:00Z)

## Replay-verifiable

This edition is sealed and **Ed25519-signed** over the published keys. Any reader can confirm the seal offline — no KYE™ service required.

**Signature algorithm**

`EdDSA`

**Key id**

`kye:key:self-audit-fixture-2026-06`

**Seal fingerprint**

`0e0907173e7e8385` (sha256 of the signature, first 16 hex)

**Published keys (JWKS)**

`/trust/self-audit-jwks.json`

**Report envelope**

`kye:research-report:kye-authority-pulse-2026-w26` · schema `kye.research_report.v1`

Verify it yourself: fetch the published JWKS, recompute the Ed25519 signature over this edition's canonicalised envelope (minus `seal`) bound to the body hash, and confirm it matches the key id above — from public keys alone, no KYE™ service in the loop.
