Rights, disputes & disclosure — one rail for the right to know, to contest, to have it investigated, and to be told.

One rail, four grafted slices

Four obligations, one coherent rail.

A regulated buyer does not experience DSAR handling, decision contestability, investigation, and disclosure as four products. They are one obligation surface. This rail declares them as one rail. It grafts each slice onto the canonical capability that already runs it.

Each slice keeps its own canonical home. This rail links them and gives counsel a single answer to point at. The evidence and replay backbone underneath every slice is the same Evidence Pack™ envelope that runs the rest of the protocol.

1 · Rights requests

The right to know.

A data subject exercises access, rectification, or erasure rights. The request resolves into a signed, replay-derivable rights pack. This slice grafts onto the KYE™ Data Governance Pack™. The DSAR Evidence Pack™ and rule pack already carry the lifecycle, the framework mapping, and the audit chain.

Data Governance Pack

2 · Disputes & contestability

The right to contest.

When a governed party contests a decision, the contest is recorded with its appeal lifecycle. It is bound to the jurisdiction whose appeal rights apply. Alongside it sits the Decision Rationale — the citizen-readable WHY record mapped to EU AI Act™ Articles 13, 14 and 86. Evidence Pack™ answers what and who. Decision Rationale answers why. The dispute is the opened contest.

Contestability stage

3 · Investigation & chain-of-custody

The right to have it investigated.

A contest or a flagged Authority Gap opens an investigation. The observed action, the shadow evaluation, and the authority gap are already canonical evidence. The chain-of-custody is held in tamper-evident WORM storage with object-store immutability. Nothing is re-created. The investigation reads the same sealed evidence every other rail produces. Every step is replayable from public keys alone.

Evidence Pack™

4 · Disclosure notifications

The right to be told.

When an outcome must be disclosed, the notification rides the KYE™ Comms Engine™. It uses the same templated, audited, multi-channel dispatch that sends every other communication. There is no separate disclosure dispatch system. Disclosure is a comms template family bound to the rail. Every notification carries the same evidence and the same delivery audit.

Data Governance Pack

The honest boundary

We enable contestability. We do not adjudicate.

This is the hard boundary of the rail. KYE™ produces the rationale of the governance decision. It seals it into a replay-derivable Evidence Pack™, records the opened contest, and routes it to whatever appeal body, regulator, or tribunal holds jurisdiction. KYE™ does not decide the outcome. It does not produce post-hoc interpretability of a third-party model. An upstream model’s output is consumed as a governed signal, not interpreted.

• Rationale, not verdict. KYE™ explains which rule fired and on whose authority. The verdict belongs to the body with jurisdiction.
• Replay-derivable, not asserted. Every contested outcome references its Replay-Proof™. The disputed decision is reproducible from public keys alone.
• Jurisdiction travels with the dispute. The appeal rights that apply are canonical and bound to the contest. The routing target is unambiguous.

Need a single answer for your rights-and-disputes process?

Start in shadow mode. We’ll deliver your first Evidence Pack™ in 4–8 weeks, with the rights, disputes & disclosure rail live across it.

Canonical KYE™ surfaces referenced on this page: Contestability stage · Decision Rationale · KYE™ Comms Engine · KYE Protocol™.