English 
Tiếng ViệtRequired fields
- Environment manifest
- Algorithm and parameter set
- Operation and object size
- Warm-up and sample count
- P50/P95/P99 and raw output
- Known constraints
INTEROPERABILITY REGISTRY
Compatibility is a versioned evidence record.
Public evidence state and publication gates for exact product, firmware, provider, platform, application and algorithm combinations.
PUBLICATION STATE
Evidence visibility is explicit.
Rows marked project-controlled are not public pass claims. They define what must be published before a production compatibility statement can be made.
| Capability | Version boundary | Maturity | Evidence visibility | Publication requirement |
|---|---|---|---|---|
| Trusted Key Token | Firmware V1.3.02 / CMVP #5331 | Public certification boundary | Public | NIST CMVP record and Security Policy |
| Windows CNG/KSP | Release-specific | Pilot publication gate | Project-controlled | OS/provider/application manifest required |
| PKCS#11 + Java JCA/JCE | Release-specific | Pilot publication gate | Project-controlled | Mechanism/provider/JDK/token matrix required |
| PAdES/CAdES/XAdES Hybrid | Profile-specific | Pilot publication gate | Project-controlled | Signed corpus and verifier matrix required |
| PQC-aware CA/TSA | Policy/profile-specific | Pilot publication gate | Project-controlled | Policy, certificate, status and timestamp corpus required |
| Benchmark Center | Environment-specific | Available assessment service | Method public / results scoped | Reproducible manifest and raw measurements required |
BENCHMARK METHOD
Publish method before numbers.
Every benchmark must state hardware, firmware, operating system, provider, parameter set, sample size and P50/P95/P99. Results must not be generalized beyond the recorded manifest.