Status · what is and isn’t live
Honest status — spec, implementation, and the service that doesn’t exist yet.
KYE Protocol™ has two halves: an open contract (specs, schemas, OpenAPI, conformance pack) and a reference implementation (Gateway, SDKs, runtime libs). Both are real and verifiable today. A hosted service — the KYE™ Cloud Gateway™ — is on the v1.1 commercial track and does not run today.
Status: side by side
Demo dataYou learn: How the options differ, criterion by criterion. You can: Pick a column to light it.
| v1.0 contract (spec) | frozen · 10 canonical profiles + 70 rule packs + 61 sector packs + 501 dictionaries | published in the public mirror repos |
|---|---|---|
| JSON Schemas | 1165 / 1165 validate against 1449 example payloads | curl -fsSL https://kyeprotocol.com/schemas/ | head |
| OpenAPI | 174 operations across Core / Payments / Extensions, redocly-clean | curl -fsSL https://kyeprotocol.com/openapi/core.openapi.yaml | grep -c 'operationId:' |
| Conformance pack | 133 / 133 black-box fixtures pass | curl -fsSL https://kyeprotocol.com/schemas/ | head |
| KYE™ Data Governance Pack™ (§31) | V1 build complete · 18 / 18 artefacts shipped 2026-05-16 · SKU KYE-DGP-001 | see data-governance.html + dsar.html |
| KYE™ Reference Gateway™ | 217 / 217 unit + integration tests pass | commercial reference implementation — procurement pack |
| SDK (TypeScript) | 67 / 67 tests | runs in the platform CI on every change; public SDK mirror pending first governed publication — see trust |
| SDK (Python) | 51 passed , 2 skipped (async/network) | runs in the platform CI on every change; public SDK mirror pending first governed publication — see trust |
| SDK (Go) | core surface pass | runs in the platform CI on every change; public SDK mirror pending first governed publication — see trust |
| Control mappings | 289 across 13 horizontal frameworks | published in the conformance mirror; full register in the procurement pack |
| Trademark audit | 0 gaps across 53 pages × 40 marks | node scripts/audit-trademarks.mjs |
| IP-safety scan | clean (no positive-form mechanism in public/ ) | bash scripts/ip-safety-scan.sh |
How this widget is built
- Demonstrates
- Comparison
- Components
- The options this page compares
- The criteria it compares them on
- Flow
- Each criterion across the options, as the page sets it out. Architecture diagram
- Used on
- /status/sla/: On this page, after its opening.
What’s actually live and verifiable today
The contract and the reference build — measured, not aspirational.
These numbers are real. Run npx @kye/conformance-pack-verifier run against the reference Gateway to reproduce them on your own machine. The public mirror packages live under the KYE-Protocol GitHub organisation.
| Component | Status | Reproduce (public mirror) |
|---|---|---|
| v1.0 contract (spec) | frozen · 10 canonical profiles + 70 rule packs + 61 sector packs + 501 dictionaries | published in the public mirror repos |
| JSON Schemas | 1165 / 1165 validate against 1449 example payloads | curl -fsSL https://kyeprotocol.com/schemas/ | head |
| OpenAPI | 174 operations across Core / Payments / Extensions, redocly-clean | curl -fsSL https://kyeprotocol.com/openapi/core.openapi.yaml | grep -c 'operationId:' |
| Conformance pack | 133 / 133 black-box fixtures pass | curl -fsSL https://kyeprotocol.com/schemas/ | head |
| KYE™ Data Governance Pack™ (§31) | V1 build complete · 18 / 18 artefacts shipped 2026-05-16 · SKU KYE-DGP-001 | see data-governance.html + dsar.html |
| KYE™ Reference Gateway™ | 217 / 217 unit + integration tests pass | commercial reference implementation — procurement pack |
| SDK (TypeScript) | 67 / 67 tests | runs in the platform CI on every change; public SDK mirror pending first governed publication — see trust |
| SDK (Python) | 51 passed, 2 skipped (async/network) | runs in the platform CI on every change; public SDK mirror pending first governed publication — see trust |
| SDK (Go) | core surface pass | runs in the platform CI on every change; public SDK mirror pending first governed publication — see trust |
| Control mappings | 289 across 13 horizontal frameworks | published in the conformance mirror; full register in the procurement pack |
| Trademark audit | 0 gaps across 53 pages × 40 marks | node scripts/audit-trademarks.mjs |
| IP-safety scan | clean (no positive-form mechanism in public/) | bash scripts/ip-safety-scan.sh |
| Consistency audit | 0 drifts across 53 pages | node scripts/audit-consistency.mjs |
The contract is bank-grade and frozen. The reference implementation is pilot-grade — correctness-first, not throughput-tuned. Production deployments substitute a hardened build behind the same contract.
What is NOT live today
No hosted service. No measured uptime. No production deployments.
- Hosted KYE™ Cloud Gateway™ service — not running. The reference Gateway runs on your machine via
npx wrangler dev(ininternal). The hosted commercial offering is on the v1.1 track. - Live measured uptime / latency / throughput — none. The targets in the SLA tier table below are the commitments a KYE™-bearing service operates under once deployed; they are not historical performance.
- Tier-1 bank deployments — none yet. “Tier-1 readiness hardening” is the v1.0.x roadmap track (CI supply-chain, governance docs, Gateway runtime hardening, signing-suite construction) — not a present-tense claim. See roadmap →
- Public adopter logos / customer references — none yet. References will land here when each Customer publishes their own. See the engagement model.
- L3 KYE™ Conformant™ / L4 KYE™ Certified™ programs — in development; open with v1.1. L1 KYE™ Self-Tested™ + L2 KYE™ Self-Attested™ available today.
- KYE™ Authority Wallet Pro™ (the production Wallet with real Gateway integration + push approvals) — v1.1 commercial track. The Authority Wallet Demo™ source is built; APK build pending Google Play Console access.
SLA targets · apply once a deployment is live
Availability targets per tier (future commitments).
| Tier | Availability target | Eligibility | Service credit on miss |
|---|---|---|---|
| Standard | 99.9% per calendar month | Default tier | 10% → 50% scaling with miss size |
| Enterprise | 99.95% per calendar month | Deployments operating regulated profiles (payments high-assurance, federation, healthcare, treasury) | 15% → 50% |
| Mission-critical | 99.99% per calendar month | Direct-engagement deployments with named scope, dedicated capacity, quarterly drill cadence | 20% → 75% |
These are the SLA tiers defined in the customer-SLA template that ships with the procurement pack under NDA. Once a deployment runs in production for KYE Protocol™ Ltd., availability will be measured at the Customer’s nearest region by a synthetic monitor and published here. No measured uptime to publish yet — these are the contractual targets, not historical performance.
Recovery commitments
RTO / RPO per component.
| Component | Tier | RTO | RPO |
|---|---|---|---|
| Gateway / PDP | 1 (Critical) | 5 min | 0 |
| Entity / delegation registry | 1 (Critical) | 15 min | ≤ 5 min |
| Audit ledger | 1 (Critical) | 60 min | 0 (synchronous replication) |
| Signal stream | 2 (High) | 15 min | ≤ 5 min |
| Transparency service | 2 (High) | 4 h | 0 (rebuildable from audit) |
| ePDP cache distribution | 3 (Standard) | 8 h | 0 (rebuildable) |
| Conformance reporting | 3 (Standard) | 24 h | 24 h |
Quarterly tabletop + annual live failover exercise required by the disaster-recovery runbook (delivered with the procurement pack under NDA).
Incident severity
Sev-0 to Sev-3.
| Severity | Trigger | Customer notify | Status updates | Resolution target |
|---|---|---|---|---|
| Sev-0 | Full outage / data breach | ≤ 30 min | Every 60 min | 4 h mitigation, 7 d permanent fix |
| Sev-1 | Major component degraded / regulator-notifiable | ≤ 60 min | Every 2 h | 8 h mitigation, 14 d permanent fix |
| Sev-2 | Single tenant or feature impacted | ≤ 4 h | Every 4 business hours | 24 h mitigation, 30 d permanent fix |
| Sev-3 | Cosmetic / minor | ≤ 1 business day | Daily | Best effort |
Sev-0 and Sev-1 trigger the regulatory notification path defined in the incident-response runbook (DORA Art. 19, GDPR Art. 33, PSD2 Art. 96, HIPAA §164.408). Full incident-response runbook is delivered with the procurement pack under NDA.
Customer notifications
When and how Customers hear about an incident.
- Initial declaration. Within the per-severity window above, the Comms lead posts to the public status page (this page, when live) and emails the named technical contacts on the Customer's account.
- Status updates. Posted on the published cadence until resolution; every update carries a current state, an explicit ETA when known, and any required Customer action.
- Resolution. Marked “resolved” when synthetic monitors return to within SLA bounds for the dwell window; a post-mortem is published within 14 days for Sev-0 / Sev-1 events.
- Service credits. Customers claim credits within 30 days of month-end per the SLA §5 in the procurement pack; credit is applied to the next invoice.
Ready to see your AI agents flagged?
Start in shadow mode. We’ll deliver your first Evidence Pack™ in 4–8 weeks.
Canonical KYE™ surfaces referenced on this page: Evidence Pack™ · KYE™ Cloud™ · KYE™ Conformance Pack™ · KYE Protocol™.