var img = document.createElement('img'); img.src = "https://analytics.zks-standard.org/matomo.php?idsite=1&rec=1&url=https://zks-standard.org" + location.pathname; img.style = "border:0"; img.alt = "tracker"; var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(img,s);
Skip to main content

Public Conformance Statements

This section hosts detailed conformance statements and architectural proofs for systems adopting the ZKS Standard Adopters Registry.

Available Statements​

QuodArca - EISST International Ltd​

  • Profile: ZKS-Core (preliminary self-attestation; full evidence pack pending)
  • Additional Properties: PSDA (Provider-Side Data Absence), documented
  • Assessment Level: Self-Attestation
  • Statement Date: January 2026

View Conformance Statement →

Assessment Levels​

LevelDescription
Self-AttestationVendor-produced statement following ZKS Section 7 evidence requirements
Peer ReviewAssessment reviewed by ZKS Working Group members
Third-Party AuditIndependent audit by qualified security assessor

Submit a Statement​

To submit your product's conformance statement:

  1. Complete the statement following ZKS Section 7 requirements
  2. Prepare evidence per the Conformance Test Catalog (procedures) and Appendix D (normative test table)
  3. Submit via GitHub Pull Request

Before publication, statements are checked by the Working Group for completeness against the Section 7/8 requirements - not for technical truth, which remains the submitting party's responsibility at the declared assessment level.

Challenges and Disputes​

Anyone may challenge a listed statement by opening a public GitHub issue identifying the specific assertion(s) disputed and the supporting evidence. The Working Group will: (1) notify the listed party, who has 30 days to respond publicly; (2) record the challenge and response alongside the listing; and (3) annotate the listing as Disputed if the response does not address the challenge, or remove it if the statement is shown to be incomplete or materially inaccurate. Challenge threads remain public. Re-listing after removal requires a new statement addressing the identified defects.