---
title: "KYE™ Regulator Watch™ — a continuous, replay-verifiable witness feed for supervisors · KYE Protocol™"
description: "KYE™ Regulator Watch™ productises the standing-witness follow-edge of the KYE Protocol™ Followability Rail™: a supervisor holds a live, governed watch over the entities it oversees, and every governed action arrives on the feed as a replay-verifiable Evidence Pack™ reference — with nothing asked of the watched entity (n=1)."
url: https://kyeprotocol.com/regulator-watch/
lang: en
source: "KYE Protocol"
---

> KYE™ Regulator Watch™ productises the standing-witness follow-edge of the KYE Protocol™ Followability Rail™: a supervisor holds a live, governed watch over the entities it oversees, and every governed action arrives on the feed as a replay-verifiable Evidence Pack™ reference — with nothing asked of the watched entity (n=1).

# Watch every governed action on the entities you supervise — as evidence

KYE™ Regulator Watch™ is the standing-witness surface of the KYE Protocol™ Followability Rail™, productised. A supervisor holds a live, governed watch over the entities it oversees. That supervisor may be a regulator, a central function, or an external auditor. Every governed action on a watched entity arrives on the feed as a Replay-Proof™ Evidence Pack™ reference. The supervisor verifies it from public keys alone.

Nothing is asked of the watched entity. The watch is unilateral. It delivers full supervisory value for one supervisor with zero integration on the other side. Evidence-gathering stops being a scheduled, after-the-fact file-pull. It becomes a continuous feed you read the day an action happens.

[Start a supervisory pilot](https://kyeprotocol.com/poc/) [See the served feed surface](https://kyeprotocol.com/directory/)

## One question a supervisor keeps asking

One question recurs for every supervisor. What did the entities I oversee actually do, and was each act authorised? You may be a financial regulator, a data-protection authority, or a firm's own second line. Today you answer in arrears — a data request, a sampled file, weeks of reconstruction. KYE™ Regulator Watch™ answers continuously, because KYE Protocol™ seals every governed act as evidence at the moment it happens.

- The watch rides events KYE Protocol™ already emits — it adds **no** second feed engine, event system or catalogue; it is the standing-witness edge of the Followability Rail™ turned into a product.
- Each item on the feed is a _governed action_ plus its Evidence Pack™ reference — a decision id and a public verify link, patent-safe by construction (no internal audit paths are ever shown).
- The feed is served through the KYE™ Directory Search™ (the [Directory](https://kyeprotocol.com/directory/)), the same pull surface the rail already ships — so there is one place to look, not a separate portal per regulator.

## Two live watch surfaces at launch

KYE™ Regulator Watch™ does not ship against a hypothetical. Two engagements are active today, each carrying a live follow-surface a supervisor can hold a standing-witness watch on — and each honest about its operating boundary.

### IoDE Armenia — agentic finance

Active · synthetic-data-only The Institute of Digital Economy (IoDE) Armenia pilot governs SME payment-authority workflows. Its watch surface emits engagement status transitions and obligation-review completions; the operating boundary is Phase One synthetic data only, and the feed says so.

### Open Bank Project — connector co-design

Active · sandbox-only The TESOBE / Open Bank Project design-partner engagement co-designs the open-banking connector. Its watch surface adds a connector contract-version-published transition, so a supervisor sees each governed change to the connector contract as it lands. Sandbox-only, per the obligation manifest.

Both surfaces are declared in the one Followability Rail™ registry with `participation_dependency: none` — the n=1 guarantee is a schema fact, not a promise: each surface yields complete value with a single follower and no counterparty anywhere.

## How a watch is granted — and revoked

A standing-witness watch is authority-bearing, never a subscription toggle. Granting one is a governed decision through the one KYE Protocol™ decision engine, under the [Purpose Permission™](https://kyeprotocol.com/glossary/) consent rule the watched surface names — the same discipline that makes it defensible in an examination.

| Field | What Regulator Watch™ binds |
| --- | --- |
| Grant | A typed `standing-witness` follow edge, admitted by a governed decision with sealed evidence — who authorised the watch, under which rule, is itself on the record. |
| Scope | The watched entity's declared state classes only (status transitions, obligation reviews, contract-version publishes) — never the entity's private data plane, which stays tenant-isolated. |
| Visibility | Overt by default. A covert supervisory watch seals the follower's _identity_ to tenant admin and auditor standing while the _fact_ that covert followers exist stays visible — sealed identity, never sealed existence. |
| Evidence | Every feed item carries an Evidence Pack™ reference and a public verify link, aligned with EU AI Act™ Article 12 record-keeping and ISO/IEC 42001 audit-trail expectations. |
| Revocation | An edge lifecycle event, not a deletion — the watch can be revoked with a reason code, and the history of the watch itself remains replay-verifiable. |

The evidence chain behind each item is the standard KYE Protocol™ governance family, made durable by the [Resilience Loop™](https://kyeprotocol.com/glossary/) — replay-provable from published keys alone, no privileged access to KYE™ required to check it.

## What Regulator Watch™ does not claim

Credibility for a supervisor comes from stating where the system stops. KYE™ Regulator Watch™ is deliberately narrow, and the boundary is the product.

- **Followable is not monitored.** KYE™ surfaces the governed actions its own estate emits. It does not claim a watched entity's _other_ systems emit events they do not, and it makes no assertion about activity outside the governed boundary.
- **Evidence, not a verdict on the entity.** The feed proves what was authorised and evidenced; the supervisor forms its own regulatory conclusions. KYE™ never scores or rates the watched firm.
- **A watch reaches an external counterparty only through a signed boundary.** A party outside KYE™'s estate becomes watchable only via an explicit identity class, a credential record, and a signed binding — never by assuming reach KYE™ does not have.

This is the honesty bar the whole protocol is held to: a supervisor can adopt KYE™ Regulator Watch™ precisely because it claims only verifiable facts, in line with [Authority Finality™](https://kyeprotocol.com/authority-finality/).

## Bring a watch to your supervised population

Start with one entity you already oversee. You get a live standing-witness feed. That entity is asked for no integration at all. The governed grant sits on the record, and every item is independently verifiable against EU AI Act™ Article 12 record-keeping. Most control functions spend days assembling that posture after the fact. Here it is continuous.

[Start a supervisory pilot](https://kyeprotocol.com/poc/) [How KYE™ delegates audit](https://kyeprotocol.com/ai-agent-auditability/)

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