The build plan, in phases.
TerraQura is being built deliberately. The platform spans verification, settlement and reporting. Delivering all three with the rigour the market requires is a multi-year program. The plan below is how we sequence the work, what each phase produces, and the methodology categories we are engineering against in each one.
Four streams of work, delivered in concert.
The platform is one product. It is delivered as four coordinated engineering streams. Each stream has its own specialists, its own roadmap and its own quality bar.
Edge capture
Sensor protocols, satellite ingestion, document pipelines. The signed evidence stream that feeds every downstream layer.
Verification engine
Methodology implementations as code. The AI evidence engine that reconciles streams against bounds and produces inspectable findings.
Settlement layer
The permissioned ledger, validator governance, key management and counterparty privacy controls institutional registries require.
Reporting and assurance
ISSB and ESRS exports, Article 6 records, external assurance packages. Disclosure as a first class output, not a downstream consultancy.
Phased delivery, methodology first.
Each phase below produces a defensible product, not a demo. We do not move to the next phase until the current one is verifiable end to end.
Methodology engine and evidence pipeline.
The first phase ships the verification engine for a focused set of methodologies, the signed evidence pipeline that feeds it, and the inspector that lets reviewers replay any finding. Settlement is internal at this stage. Disclosure exports are produced for a single buyer working group.
Permissioned ledger with institutional counterparties.
Settlement moves onto the permissioned blockchain. Issuance, transfer and retirement are recorded with full lineage. Counterparty privacy controls are introduced. External assurers are given structured read access to the audit trail. Article 6 record formats are first wired in this phase.
Reporting layer for institutional buyers.
The disclosure layer ships IFRS S2 and ESRS E1 exports as native outputs. Verified retirements are translated into the formats sustainability reports require, with full evidence references. Buyer onboarding moves from the working group to a managed cohort.
Sovereign registry deployment readiness.
The platform reaches the configuration where a sovereign authority can adopt the settlement and verification layers as their national registry stack. Data residency, supervisory access and ITMO interoperability are productionised.
Methodology breadth and continuous improvement.
With the foundation, settlement, disclosure and sovereign capabilities in production, the platform scales into additional methodology categories. Quality, not breadth, governs the order in which categories are added.
The first methodology categories the platform is being engineered for.
Each pilot track represents a methodology family the verification engine is implementing first. Selection is driven by methodology maturity, evidence availability and the integrity questions buyers and regulators are asking.

Biomass carbon removal and storage
Engineered biomass pathways with durable storage. Continuous operational data, mass balance and storage monitoring map cleanly onto the evidence engine.

Biochar production and application
Pyrolysis economics with measurable feedstock provenance, production telemetry and end use records. A category where continuous capture changes the integrity ceiling.

Restoration with rigorous baselines
Restoration projects with satellite measurable outcomes and durable governance. Permanence and additionality are first class in the verification design.

Industrial reduction with operational data
Reduction methodologies where the underlying activity is metered. Richer operational data produces a more credible counterfactual baseline and a more defensible tonne.
Discipline is a feature of the build.
Methodology before throughput
We will not enable a methodology category until the verification can be replayed end to end. The roadmap orders categories by integrity readiness, not by addressable volume.
Settlement before scale
The settlement layer reaches institutional readiness before the platform onboards more than a controlled cohort. Volume that arrives before settlement is liability, not progress.
Disclosure before marketing
External reporting is wired before any volume claim is made publicly. The platform's outputs are the first place anyone hears how it is performing.
