Dispute Resolution & Framework Evolution
Dispute Resolution & Framework Evolution
How contested data is handled. How the framework itself grows.
Constitutional Layer · C-03Dispute Resolution
Two types of disputes require different arbitration tracks.
🔬 Technical Disputes
Example: Is a satellite imagery dataset authoritative for the 2020 deforestation baseline? Is methodology X equivalent to GHG Protocol?
Arbitrator: Scientific Council. Typical resolution: 30 days. During review, contested data is suspended from compliance exports.
🌿 Consent Disputes
Example: A company claims consent was given; the community says it was not. An FPIC credential was issued but the community says the signing process was coerced.
Arbitrator: Community Sovereignty Panel. External mediator (COICA-designated) if unresolved in 30 days.
DISPUTE_OPEN status. It continues to appear in asset history but is excluded from
all compliance exports (EUDR, CSRD, CBAM, ISSB S2) until the dispute is resolved.
In-progress regulatory submissions using the disputed data are suspended and EU operators notified.
Framework Evolution — Semantic Versioning
| Version type | Example | Process | Lead time |
|---|---|---|---|
| Patch (1.0.x) | Typo fix, language clarification | CTH Operator. 48h board notification. | Immediate after notification |
| Minor (1.x.0) | New accepted methodology, new optional field | 14-day public comment. CTH Operator decision. Board notification. | 30 days from proposal |
| Major (x.0.0) | New principle, breaking schema change, new mandatory field | 30-day public comment. Full board vote (⅔ + quorum). Community Panel veto if FPIC-adjacent. | 90 days minimum from proposal to implementation |
Backward Compatibility
All prior major versions remain valid for 24 months after a new major version is released. Data submitted under version 1.0 continues to be verifiable after version 2.0 is released. Credential schemas are versioned — a version 1.0 DTE credential does not become invalid when the version 2.0 schema is published.
Framework Versioning in the Ledger
Each framework version is itself a signed Verifiable Credential issued by the CTH Data Steward DID. The credential contains: version number, release date, changelog URI, schema diff hash, and the board vote record (for major versions). This means framework version history is itself tamper-evident and auditable — not stored in a mutable database or git repository alone.
No hay comentarios para mostrar
No hay comentarios para mostrar