Sample kye.report.v1 envelopes

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.

Example reports by role, step by step

Demo data

You learn: What happens at each step. You can: Step through it.

  1. Step 1 of 3

    KYE Protocol™

    Signature-covered bytes

    the page itself is the canonical artefact; a signature fragment binds it to the published assembler_kid .

  2. Step 2 of 3

    KYE Protocol™

    Verifiable offline

    any reader confirms the seal locally; see how on the evidence-pack demo .

  3. Step 3 of 3

    KYE Protocol™

    Honest scope

    these are synthetic-tenant samples for illustration; real reports are tenant-scoped and PII-bearing inside the customer's admin console.

How this widget is built
Demonstrates
KYE Protocol™
Components
  • The steps this page describes
Flow
Each step in order, as the page sets it out. Architecture diagram
Used on

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.

Pick a stakeholder view

Each card opens a full signed sample report for that reader — the same evidence base, projected for the question that reader actually asks.

Auditor report Control-by-control assurance with a replay-verifiable evidence pack per finding.Board report Posture and residual-risk summary at the altitude a board needs to sign off.CISO report Security posture and ISO 27001 Statement of Applicability evidence.Consultant report Engagement-scoped readiness view a consultant hands to the client.Customer report The trust evidence a customer requests before they adopt a vendor.Dispute report Decision-trail and admissibility evidence assembled for a dispute.DPO report Data-protection posture, lawful-basis coverage and DSAR evidence.General counsel report Liability-relevant evidence and contractual-obligation coverage.Partner report The conformance evidence a partner shares across a trust boundary.Regulator report Framework-clause-bound evidence in the form a regulator examines.

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.

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.

Canonical KYE™ surfaces referenced on this page: Evidence Pack™ · KYE Protocol™.