Transparency dashboard

The registry holds 20,000 credit units, 17 projects, 6 issuance batches and 5 retirement records. Of those, 20,000 units, 17 projects, 6 batches and 5 retirements are demonstration records — seeded data used for showcases and testing, which are not verified credits and may not be cited in compliance, contribution or third-party reporting.

The remainder is nil. First verified-credit issuance is subject to institutional formation and multi-methodology derisking. Every figure below therefore describes a pipeline and a demonstration dataset, not an issued stock of credits.

The adopted rulebook is published in full text at /transparency/documents: the Programme Factsheet, the seven counterparty policies (v1.1), the PDD template, methodology family guidance, the Definitions Register, and the governance decision record that adopted them (FD-2026-08-24), and the standards series as the adopted files with their SHA-256. The Transparency Policy that requires this publication is itself one of the documents served. The public consultation register is at /consultations, the grievance channel at /grievances, the register of accredited validation and verification bodies at /transparency/vvbs, and the public API is described at /transparency/api (OpenAPI 3.1).

This list is part of the dashboard, not a disclaimer under it. Each item below is something a reader could reasonably expect to find here and which this registry does not currently hold. Publishing an estimate in any of these places would make the page look more complete and be less true.

• Conservation outcomes in physical units. No programme-level figure for tonnes of CO₂e, hectares of habitat or species outcomes is published, because the registry counts credit units and holds no verified aggregate of that kind. Per-project area and monitoring figures are on each project's own record.
• Trends over time. Every figure above is the state of the registry at the moment this page was requested. No historical series of these totals is stored or published, so there is no issuance or retirement trend line to show and none is drawn.
• Why credits were retired. The purpose text held against the retirement records names third parties as making claims they have not made and has not been cleared for publication. It is withheld on every surface until those records are corrected.
• Who holds unretired units, and transfers between accounts. Unit-level holdings and the transfer journal are restricted to the counterparties and registry staff by database policy. There is no public transfer journal, and this page does not work around one.
• Buffer pool composition and reversals. Buffer units are counted in the ledger table above as a status. The pool's composition sits at /registry/buffer; no reversal event has been aggregated here.
• Service and analysis-layer status. Operational status is published separately at /transparency/system-status (MCC-400 art. 95.1) and /api/public/v1/status, which also carries the Art. 20 registry-read SLA measurement.

Each request reads the credit unit ledger, the issuance batches, the projects, the methodologies and the retirement records directly from the registry database and counts the rows returned. There is no cache in front of these figures and no pre-computed summary table behind them, so a number on this page cannot be older than the request that produced it.

Demonstration records are identified by the rule shared with the public API (is_demonstration on the record, its batch or its project, or a serial beginning MCC-DEMO-). Because the rows are read rather than counted in the database, both halves of that rule apply here — the demonstration figures above are totals rather than the lower bounds a row-free count is limited to.

Scan truncated. At least one table exceeded this page's read limit on this request. Every figure above is therefore a floor rather than a total, and should be read as “at least”. This needs a grouped count in the database rather than a larger limit here.

Machine-readable equivalents: /api/public/v1/status, /projects, /batches, /retirements. Those endpoints exclude demonstration rows by default — a machine consumer sees no badge — so their counts will not match this page unless ?includeDemo=1 is passed.

Position statement. Credits are issued and retired under the programme's contribution-first framework (MCC-800). Retirements support verified marine conservation outcomes; they do not represent carbon offsets, neutrality, or emissions reduction claims.