Sample kye.report.v1 envelopes · one per stakeholder

Example reports by stakeholder.

Every stakeholder reads a different slice of the same governed evidence. The ten samples below are representative kye.report.v1 envelopes — one per persona — rendered for a synthetic tenant. The bytes you see are signature-covered: anyone holding the published assembler_kid public key can verify each report locally, with no portal log-in and no vendor cooperation. Pick the reader whose view you need.

Synthetic tenant. Real reports carry tenant-PII and are scoped to the customer's admin console. Mechanism details are part of the patent track and not disclosed in this repository.

Looking for published research instead?

These per-stakeholder samples are illustrative compliance reports — one synthetic envelope per reader, to show the shape of the evidence. They are a different concept from KYE Protocol's published research reports, which are governed, cited, replay-verifiable market research synthesised from external public sources. If you came looking for the research shelf, it lives on the Reports page.

menu_book Browse published reports

How every sample is governed

  • Signature-covered bytes — the page itself is the canonical artefact; a signature fragment binds it to the published assembler_kid.
  • Verifiable offline — any reader confirms the seal locally; see how on the evidence-pack demo.
  • Honest scope — these are synthetic-tenant samples for illustration; real reports are tenant-scoped and PII-bearing inside the customer's admin console.