Sample kye.report.v1
Partner QBR Report™ — Pipeline · co-sell hygiene · certification status.
A representative kye.report.v1 envelope for a Partner QBR. The bytes you see are signature-covered — anyone with the published assembler_kid public key can verify the report locally, with no portal log-in and no vendor cooperation.
Partner stakeholder report, step by step
Demo dataYou learn: What happens at each step. You can: Step through it.
-
Step 1 of 5
KYE Protocol™
Pipeline
7 active pilots · 4 advanced to PoC · 1 closed-won · $612k attributed ARR.
-
Step 2 of 5
KYE Protocol™
Certification
12 consultants L2+ certified · 3 currently in L3 training · 2 certification renewals due this quarter.
-
Step 3 of 5
KYE Protocol™
Co-sell hygiene
3 accounts properly registered · 0 deal-collision findings · 0 attribution disputes.
-
Step 4 of 5
KYE Protocol™
MSA compliance
0 findings · all engagements scoped via signed SoW envelopes · subprocessor list current.
-
Step 5 of 5
KYE Protocol™
Portal posture
MFA 100% · 0 stale credentials · 0 unauthorised access attempts.
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
- /stakeholders/example-reports/partner/: On this page, after its opening.
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.
Executive verdict
Partner X's KYE™ practice is on-plan for Q2 2026. 7 active pilots (target 5); 12 certified consultants (target 10); 3 co-sell-eligible accounts with KYE™ attribution; zero MSA compliance findings; partner-portal MFA at 100%.
Supporting findings
- Pipeline · 7 active pilots · 4 advanced to PoC · 1 closed-won · $612k attributed ARR.
- Certification · 12 consultants L2+ certified · 3 currently in L3 training · 2 certification renewals due this quarter.
- Co-sell hygiene · 3 accounts properly registered · 0 deal-collision findings · 0 attribution disputes.
- MSA compliance · 0 findings · all engagements scoped via signed SoW envelopes · subprocessor list current.
- Portal posture · MFA 100% · 0 stale credentials · 0 unauthorised access attempts.
Framework binding
| Clause | KYE™ artefact that binds it |
|---|---|
| KYE™ Partner Program™ | Active-pilot threshold via signed kye.partner.pipeline_attribution. |
| KYE™ Partner Program™ | Certification level via signed kye.partner.certification_status. |
| KYE™ Partner Program™ | MSA compliance via kye.partner.msa_compliance evidence pack. |
| KYE™ Co-sell | Attribution chain bound to KYE™ Authority Graph™. |
| KYE™ Partner Portal.2 | MFA-enforced; access events audit-chained. |
Signature
The bytes of this page are the canonical artefact; the signature fragment below binds them.
{
"schema_id": "kye.report.v1",
"report_id": "kye:report:partner_quarterly_qbr:sample-partner-x:2026Q2",
"tenant_id": "kye:tenant:sample",
"report_kind": "partner_quarterly_qbr",
"framework": "soc_2",
"period_start": "2026-04-01T00:00:00Z",
"period_end": "2026-07-01T00:00:00Z",
"sealed_at": "2026-07-01T00:00:00Z",
"assembler_kid": "kye:kid:sample-partner-x:qbr-q2-2026",
"signature_b64": "MEUCIQDxRy…(truncated; sample)…"
}
Canonical KYE™ surfaces referenced on this page: Authority Graph™ · Evidence Pack™ · KYE Protocol™.