Skip to main content
Reviewer onboarding · Demonstration mode

Welcome, MCC reviewer. Thank you for your time.

This page is your single entry point to the Marine Conservation Credits platform. It points you at five demo projects worth your attention first, names the six lenses we want your eye on, and gives you a way to leave structured feedback that lands directly with the team.

What MCC is, in three paragraphs

Marine Conservation Credits (MCC) is an AI-native, contribution-first crediting programme for ocean and coastal ecosystems. Where legacy carbon registries optimise for offsetting tonnage, MCC is built around marine conservation outcomes — biodiversity recovery, habitat integrity, community stewardship — with carbon as one signal among many. The programme is contribution-first by design and is not positioned as a compliance offset instrument.

Activity is grouped under a stable taxonomy of five families: F01 Mangrove, F02 Seagrass, F03 Macroalgae / kelp, F04 Marine debris and ghost gear, and F05 Reef and MPA. The methodology library, validation flow, monitoring stack and registry all derive from this taxonomy. You will see family codes (F01-F05) on every project card and methodology page; understanding the family makes the rest of the platform legible.

We are running a structured academic review of MCC methodology documents. Your job is not to bless the platform — it is to stress-test it. Walk through demo projects as if you were a methodology committee member or a buyer doing due diligence. Where the audit trail is thin, where the additionality argument wobbles, where the safeguards are aspirational rather than evidenced — please tell us. Use the feedback form below; every entry is timestamped, attributed to your name and (optionally) your institution, and carries a severity tag we use to triage.

Start here: 5 demo projects to evaluate

These five span the F01-F05 taxonomy and surface the most interesting edge cases in the data — reversal events, illegal-harvesting alerts, high-latitude kelp, and community-based work. Each link opens the project with reviewer mode enabled.

The complete catalogue of 17 demo projects is available at /projects. Add ?reviewer=1 to any project URL to enable the reviewer banner.

What to evaluate

Six lenses. You don't need to apply all six to every project — but try to cover each lens at least once across the projects you review.

  1. PDD completeness

    Is the Project Design Document scoped clearly? Does the methodology fit the proposed activity? Are project boundaries (geographic, temporal, ecological) well defined?

  2. Additionality argument

    Is the case for additionality credible? Is there a defensible counterfactual baseline? Do regulatory / financial / common-practice tests pass?

  3. FPIC and safeguards

    Is Free, Prior and Informed Consent documented for affected communities? Are environmental and social safeguards screened? Are grievance channels visible?

  4. Monitoring frequency and methods

    Are monitoring intervals fit for the ecosystem (mangrove vs reef vs kelp)? Are methods (remote sensing, in-situ, eDNA) appropriate and reproducible?

  5. SD contributions

    Are the Sustainable Development Goal mappings credible and evidence-backed — or aspirational claims? Are co-benefits to communities and biodiversity quantified?

  6. Validation / verification audit trail

    Is the chain VVB to validation to registration to issuance to retirement traceable end-to-end? Are decisions, reviewers, and timestamps captured?

Submit feedback

Use the form below for anything that doesn't fit a comment thread on a specific consultation. Tag a project (or "General"), pick a severity, and write as much as you need — up to 5,000 characters.

Up to 5,000 characters
5,000 left
By submitting, you agree your name, email and (optional) institution may be retained for follow-up. We do not publish your contact details.

Recent feedback

Last five entries (anonymised — first name and institution only). Visible to reassure reviewers that submissions are being received; full content is reviewed by the team in the admin console.

No public entries yet — your submission may be the first the cohort sees.