Japan

Runtime authority for Japanese sovereign AI.

When the PPC asks how personal information was handled by an automated system under the APPI, when the FSA asks who was accountable for an AI-driven financial decision and how it was reached, when the PMDA asks for the change-control and post-market evidence behind AI-enabled medical-device software — KYE Protocol™ answers from a record sealed at the moment of action. Replayable from the publishing tenant's JWKS alone. No vendor dependency in the audit path.

KYE Protocol™ for Japan, step by step

Demo data

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

  1. Step 1 of 4

    KYE Protocol™

    Data residency

    deploy to Japanese-region edge runtime resources; per-tenant configurable; structured datastore + object store pinned to Japan.

  2. Step 2 of 4

    KYE Protocol™

    Customer KMS

    signing keys live in the customer's HSM or sovereign-cloud KMS; KYE™ never has access to the private key material.

  3. Step 3 of 4

    KYE Protocol™

    Open verifier

    the PPC, the FSA, the PMDA and the customer's own auditors can replay an Evidence Pack™ using only the publisher's JWKS. No vendor dependency in the audit path.

  4. Step 4 of 4

    KYE Protocol™

    Apache 2.0 schemas + vocabulary

    the contracts the customer relies on are open. The patent-track runtime construction is paid; the proof formats are not.

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

Japan-sovereign deployment

Japanese data, Japanese keys, Japanese control.

  • Data residency — deploy to Japanese-region edge runtime resources; per-tenant configurable; structured datastore + object store pinned to Japan.
  • Customer KMS — signing keys live in the customer's HSM or sovereign-cloud KMS; KYE™ never has access to the private key material.
  • Open verifier — the PPC, the FSA, the PMDA and the customer's own auditors can replay an Evidence Pack™ using only the publisher's JWKS. No vendor dependency in the audit path.
  • Apache 2.0 schemas + vocabulary — the contracts the customer relies on are open. The patent-track runtime construction is paid; the proof formats are not.

Japanese pilot · 6 weeks

KYE™ Japanese Readiness Pilot™.

Japanese banks, insurers, asset managers, medical-device manufacturers and AI-deploying enterprises: a 6-week shadow-mode engagement producing APPI personal-data handling evidence per assertion, FSA AI-governance and model-risk coverage, PMDA SaMD change-control and post-market evidence where applicable, signed Evidence Packs™ per decision, and a regulator-ready executive summary with a residual-risk register.

Independent — no government affiliation. KYE Protocol™ is an independent protocol and is not affiliated with, endorsed by, or part of any government, regulator, or official “Sovereign AI” programme. References to regulators and frameworks describe the requirements KYE™ helps you evidence — not any official relationship.

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