Regulatory posture Standards. Sovereign deployment. Governance

Built to operate inside the rule sets the market is converging on.

Carbon infrastructure that does not respect the standards regulators and assurers work in is a liability. The TerraQura platform is engineered against the frameworks that institutional buyers, sovereigns and external auditors already align with. The list below is what we hold ourselves to.

Standards alignment

Frameworks the platform is being engineered against.

These are the frameworks the platform's verification, settlement and reporting layers are designed to comply with. Compatibility is a product input, not a marketing claim.

Compliance markets

Paris Agreement Article 6.2 and 6.4

Authorisation, tracking and corresponding adjustment records for internationally transferred mitigation outcomes. The settlement layer is designed to support sovereign registries operating under Article 6.

Voluntary markets

ICVCM Core Carbon Principles

The CCP framework defines what high integrity looks like in the voluntary market. Verification, additionality, permanence and governance are encoded in how methodologies are implemented on the platform.

GHG accounting

ISO 14064-2 and ISO 14065

Project-level quantification structured to ISO 14064-2. Verification workflows shaped to be assurance-ready under ISO 14065. External assurers can operate without bespoke integration.

Disclosure

ISSB IFRS S2 and ESRS E1

Reporting outputs map into the IFRS S2 climate disclosures and the ESRS E1 European standard. Verified retirements carry forward into the formats sustainability reporting actually requires.

MRV

VCM Integrity Council methodology assessment

Methodology approvals follow the VCMI and ICVCM assessment lineage. Categories not yet at threshold are out of scope on the platform until the methodology assessment lands.

Data

SOC 2 and ISO 27001 oriented

The platform's data architecture is built toward SOC 2 Type II and ISO 27001 controls from day one. Evidence is sensitive. Treating it that way is non-negotiable.

Sovereign deployment

A registry stack national authorities can actually run.

Sovereign registries have ambition but limited operating infrastructure. The platform is designed so that an authority can adopt the settlement and verification layers with the controls a national registry requires.

Authority controls

The registry remains under sovereign authority.

Issuance authorisation, transfer approval and retirement are governed by the host authority's policy. The platform provides the operating system. The authority remains the regulator.

Data residency

Evidence stays where the law requires it.

Architecture supports in-country data residency, sovereign hosting and key management arrangements. Cross-border evidence sharing is governed, not assumed.

Interoperability

Compatibility with international registry infrastructure.

Article 6 transfers, ITMO authorisation records and corresponding adjustment exports are first class. The registry talks to the international system the way the international system expects.

Supervision

External auditors can do their job.

Independent assurers and supervisory bodies have read access to the evidence trail in a structured form. Supervision is designed in, not retrofitted.

Governance principles

Operating commitments we hold regardless of who is asking.

Independence

The platform is not a counterparty

TerraQura does not buy, sell or hold credits issued on the platform. Settlement infrastructure should not have positions in the assets it settles.

Methodology

No bespoke methodologies

The platform implements published methodologies from recognised standard setters. We do not write our own to fit a buyer or operator.

Privacy

Counterparty privacy preserved

The audit trail of the unit is shared. The identities of counterparties are governed by access controls aligned to host authority policy.

Disclosure

Material concerns are reported

If verification surfaces material integrity concerns, the platform reports them through governed channels. Quiet workarounds are not in the operating model.

For regulators and authorities

If your authority is exploring registry infrastructure, we would welcome the conversation.

Open a conversation