Governing Board and Governance Model
Status: Draft Governance Charter (Open for Founding Steward and Advisory Nominations)
Domain:riosz.org
Mandate: Vendor-neutral stewardship, steward accreditation, and 20-year verification continuity
Governance of the Riosz Confidential Wrapper Open Standard (where Riosz stands for Resilient Independent Open Standard for Zero-knowledge) is separated into three distinct bodies to maintain neutrality, ensure evidentiary admissibility, and prevent single-vendor capture.
1. The Governing Board
The Governing Board serves as the fiduciary and legal custodian of the Riosz Confidential Wrapper Open Standard and the broader Riosz standards family.
Responsibilities
- Asset and Trademark Custody: Holds and defends the Riosz name, conformance marks, and
riosz.orgdomain infrastructure on behalf of the community. - Steward Accreditation: Establishes and audits accreditation standards for commercial and institutional key stewards—enforcing threshold separation ($\max \lvert B_j \rvert < 3$), air-gapped or HSM private key isolation, single-use key compartmentalization, and 10–20+ year recoverability.
- Operational Independence: Ensures long-term financial and organizational independence so no single software vendor, cloud provider, or steward coalition can capture the standard.
- Conformance Enforcement: Administers the “Riosz Standard Compliant” certification program based on 100% pass rates against the official automated Conformance Test Suite.
Provisional Board Structure (Draft)
| Seat / Role | Constituency | Status |
|---|---|---|
| Chair | Independent / Founding Stewardship | Provisional (Draft) |
| Accredited Steward Representatives | Independent Key Custody Institutions | Open for Founding Nominations |
| Technical Steering Liaison | Elected TSC Representative | Pending TSC Formation |
| Legal and Forensic Liaison | Appointed Council Representative | Pending Council Formation |
| Enterprise / Ecosystem Seats | Adopters and Reference Implementers | Open for Founding Nominations |
2. Technical Steering Committee (TSC)
The TSC oversees technical architecture, cryptographic agility, and specification releases.
- Core Specifications and Codebase: Reviews and approves changes to the
.rioszcontainer format,manifest.jsonschema, reference verifiers, andreconstruct_payload.py. - RIP Lifecycle Management: Administers the Riosz Improvement Proposal (RIP) process.
- Cryptographic Agility and Deprecation: Monitors post-quantum standardization (NIST, ISO, BSI, ANSSI) and issues immediate issuance cutoffs when a
vault-3of5slot algorithm is deprecated. - Composition: Core contributors, cryptographers, and systems engineers elected on merit and sustained contribution.
3. Legal and Forensic Advisory Council
The Legal and Forensic Advisory Council ensures that Riosz artifacts remain admissible and defensible in judicial and regulatory proceedings worldwide.
- Statutory Evidence Alignment: Audits proposed manifest and container changes against US Federal Rules of Evidence 902(13)/(14), the EU eIDAS regulation (RFC 3161 Qualified Trust Service Providers), and international trade secret preservation directives.
- Fiduciary Steward Guidelines: Advises the Governing Board on legal release authorization workflows, cross-border custody, and blind-release verification.
- Composition: Intellectual property litigators, patent attorneys, digital forensic examiners, and archival scientists.
4. The 20-Year Verification Continuity Mandate
Because Riosz containers and receipts are created to defend trade secrets and prior art across the 20-year statutory lifespan of utility patents worldwide:
- No Breaking Changes to
v1Verification: Future versions of the reference verifier MUST always remain capable of validatingv1.rioszcontainers and JSON manifests. - Forward-Only Deprecation: Cryptographic suites that become vulnerable in future epochs are retired from new container issuance, while future verifiers retain full support for validating historic
v1commitments anchored at valid historical ledger or RFC 3161 timestamps. - Prior-Existence Continuity: When high-sensitivity containers are re-sealed under a successor algorithm suite, the original receipt or
manifest.jsonis retained alongside the re-sealed container to preserve the original proof-of-existence date.