---
title: "Updates — what's new across KYE Protocol™ · KYE Protocol™"
description: "The KYE Protocol™ updates feed: every rail adopted, event scheduled, certificate program launched, and report published — one canonical feed, generated from the registries, never hand-curated. The notification bell on every page links here."
url: https://kyeprotocol.com/updates/
lang: en
source: "KYE Protocol"
---

> The KYE Protocol™ updates feed: every rail adopted, event scheduled, certificate program launched, and report published — one canonical feed, generated from the registries, never hand-curated. The notification bell on every page links here.

# Updates

This is where you see what is new across KYE Protocol™. Every rail we adopt, event we schedule, certificate we launch, and report we publish lands here — on one feed.

The notification bell in the top bar links to this page. Its badge shows you how many updates arrived since your last visit.

[Browse the research library](https://kyeprotocol.com/library/)

## What lands on the feed

Each entry is one dated change you can act on. The feed mixes several kinds, and every kind comes from a registry the protocol already maintains.

- **Rail** — a constitution chapter is adopted and a capability ships.
- **Event** — a conference, workshop, or report launch is scheduled.
- **Certificate** — a certificate program opens, such as the Builder Certificate.
- **Report** — a governed research report is published.
- **Obligation** — an obligation set changes in the obligation registry.

## Generated, never hand-written

No one edits this feed by hand. A builder reads the canonical registries and writes the feed, so an entry appears the moment its source changes.

- Add an event to the calendar, and it shows up here on the next build.
- Open a certificate program, and the bell badge counts it for every visitor.
- Each entry carries a real date and links straight to its canonical source.
- The feed is deterministic: the same registries always produce the same bytes.

## Watch surfaces served here

The public-plane pull endpoint of the [KYE™ Regulator Watch™](https://kyeprotocol.com/regulator-watch/) follow surface over the estate root: constitution adoptions, releases and emitted attestations are the state classes a follower is entitled to see.

1 watch surface names this page as the pull endpoint. Each lists the state classes a follower is entitled to see and every sealed transition recorded so far: a decision id, an Evidence Pack™ reference and the public verify link, nothing from the watched entity's data plane. Generated from the followability and engagement registries; it changes only when they do.

### Kye Protocol, estate root (public plane)

`kye:follow-surface:business:kye-protocol` · watches `kye:ent:kye-self:business:kye-protocol` · operating boundary: public plane · visibility overt · follow-grant decided under `kye:rule:follow-grant:public-plane-default`

Push delivery **deferred**: Pull-only today. Constitution amendments, releases and emitted attestations are read at /updates.html. This is the public plane, where an email-digest channel is the intended shape rather than a webhook, and neither exists yet, so a reader who wants to know when the constitution changes must come and look.

- `constitution:amendment-adopted`: declared on the surface. No canonical record carries a sealed item of this class yet, so nothing is shown rather than something invented.
- `release:published`: declared on the surface. No canonical record carries a sealed item of this class yet, so nothing is shown rather than something invented.
- `attestation:emitted`: declared on the surface. No canonical record carries a sealed item of this class yet, so nothing is shown rather than something invented.

## The feed

Here is the live feed, newest first. Pick any entry to jump to the page it announces.

Loading the updates feed…

Canonical KYE™ surfaces referenced on this page: [Evidence Pack™](https://kyeprotocol.com/evidence-pack/) · [KYE Protocol™](https://kyeprotocol.com/).