MCC TRANSPARENCY AND PUBLIC DISCLOSURE POLICY

Version 1.1 | 24 August 2026

v1.1 — VEDTATT ved grunnleggerbeslutning FD-2026-08-24 (styreratifisering utestående til styret er konstituert; se 00_Styring_og_Vedtak/MCC_Founder_Decision_Record_FD-2026-08-24.md). Korrigert etter regelverksrevisjonen 24.08.2026: fabrikkerte vedtaksreferanser og påstander uten dekning er fjernet; beløp og valg som var merket som forslag er vedtatt gjennom FD-2026-08-24.

Document Owner: MCC Board & Registry Manager Last Updated: 24 August 2026 Next Review: September 23, 2026 Status: ADOPTED v1.1 — FD-2026-08-24 (board ratification pending)

ARTICLE 1: PURPOSE

This Policy establishes MCC's transparency commitment: default-public data disclosure. MCC believes stakeholder trust is earned through radical transparency on projects, credits, governance, AI, fees, and performance.

Guiding Principle: Except where legitimate confidentiality applies, MCC publishes.

ARTICLE 2: WHAT MCC PUBLISHES

2.1 Project Data (Public Registry)

MCC publishes for every registered project:

A. Project Identification

Project name
Host country and region (geographic coordinates)
Ecosystem type (F01-F05 methodology family)
Project status (DRAFT, SUBMITTED, REGISTERED, ACTIVE, COMPLETED, SUSPENDED)
Crediting period (start year, end year, expected credit issuance duration)

B. Baseline and Quantification

Baseline scenario (business-as-usual quantification)
Estimated annual carbon sequestration (tCO₂e/year)
Total estimated credits (over crediting period)
Quantification methodology (formulae, emission factors cited)
Uncertainty assessment (confidence level)

C. Permanence and Buffer

Permanence period (e.g., "150-year sequestration")
Permanence risk factors (erosion rate, storm frequency, disease history, climate change, human pressure)
Buffer pool size (%)
Permanence mechanisms (legal protection, monitoring, endowment)

D. Co-Benefits and Sustainability

Fisheries impact (hectares, fish species benefited, protein production)
Biodiversity (species counts, habitat type, conservation status)
Community impact (jobs created, livelihood support, training programs)
Coastal resilience (wave energy reduction %, storm surge buffering)
SDG alignment (which goals, quantified)
Safeguards compliance (9-principle assessment, pass/fail per principle)

E. Validation and Verification Status

VVB name and ISO 14065 accreditation status
Validation report (public; findings summary)
Verification reports (annual; public)
Major findings history (if any material issues resolved)

F. Project Developer Information

Organization name and country of incorporation
Project sector (public or private conservation, government agency, etc.)
Website (if applicable)
Contact (project lead name, email, phone)

2.2 Credit Data (Public Registry)

MCC publishes for every credit:

Credit Identification

Serial number (MCC-TYPE-METH-PROJECT-VINTAGE-SEQUENCE)
Credit type (CC, HYB, MCU)
Vintage year
Status (ISSUED, ACTIVE, RETIRED, CANCELLED)

Ownership (Organizational Level)

Current owner (organization name; NOT individual names for privacy)
Issuance date
Transfer history (who owned when; at organization level)

Retirement (if applicable)

Retiring organization
Retirement date
Claim basis (climate contribution, VCMI tier, regulatory, conservation focus)
CA status (corresponding adjustment: YES/NO)

Example Public Record:

DEMONSTRATION RECORD — no real credit has been issued
Serial: MCC-DEMO-CC-F01-IDN0001-2026-00000001-7
Type: Carbon Credit | Vintage: 2026 | Status: RETIRED (demonstration)
Issued to: Demonstration Developer A
Transferred to: Demonstration Holder A
Retired by: Demonstration Buyer A
Project: Demonstration Mangrove Project, Indonesia (F01)
CA Status: NOT_APPLICABLE (demonstration data)

2.3 Retirement Data (Public Registry)

MCC publishes for every retirement:

Retirement Certificate

Serial number(s) retired
Retiring organization
Retirement date
Quantity (tCO₂e)
Project name and location
Claim basis (VCMI tier, ISO 14068 compliance, other)
CA status (host country authorization, international transfer)
Hash signature (SHA-256 verification)

Example:

DEMONSTRATION CERTIFICATE — format illustration only
Retirement Certificate: MCC-DEMO-CERT-2026-0001-RET
Retiring Party: Demonstration Buyer A
Quantity: 500 credits
Credits: MCC-DEMO-CC-F01-IDN0001-2026-00000001-7 … 00000500-1
Project: Demonstration Mangrove Project, Indonesia
Claim: Marine Conservation Contribution (contribution-first; no offsetting claim)
CA: NOT_APPLICABLE (demonstration data)

2.4 Methodology Data (Public Library)

MCC publishes:

Methodology Module Documents (F01-F05)

Full technical description (scope, activities, ecosystem type)
Baseline establishment procedures (step-by-step)
Quantification formulas (equations, emission factors, uncertainty)
Monitoring plan requirements (frequency, methods, quality assurance)
Additionality assessment (3-part test: financial, regulatory, common practice)
Permanence assessment (risks, mechanisms, buffer sizing formula)
Safeguards requirements (9-principle checklist)
Co-benefits quantification (methods for fisheries, biodiversity, resilience)

Version History

Methodology version number
Approval date
Change log (if amendments post-launch)
Related standards (Gold Standard, Verra, CRCF references)

Applicability

Applicable geographic regions
Applicable project scales
Ecosystem conditions (salinity, coastal type, water depth)
Exclusions (what types of projects NOT eligible)

2.5 Governance Data (Public Dashboard)

MCC publishes:

Board Decisions

Meeting date and attendees (Board member names)
Agenda items (what was discussed)
Decisions voted on
Decision rationale (why was this decision made? what evidence considered?)
Vote count (if not unanimous, how split)
Dissenting opinions (if any Board member formally objected)
Public notice (major decisions announced)

Committee Reports

Technical Committee monthly meeting summaries
Methodology Working Group (F01-F05) activities and updates
Safeguards Review Panel decisions

Governance Policies

All policies (MCC-850 AI, claims, transparency, etc.) published
Version history and amendments
Rationale for major policy changes

Example:

FORMAT ILLUSTRATION — no board decision has yet been published.
BOARD DECISION: [meeting date]
Decision: [approve/reject project or policy item]
Rationale: [summary of the evidentiary basis]
Vote: [for–against–abstain, with quorum recorded]
Published: [date]

2.6 AI Data (Transparency Layer)

MCC publishes:

AI Involvement Metrics (Quarterly)

Total projects reviewed by AI
AI recommendations by confidence tier (HIGH, MEDIUM, LOW, VERY LOW)
Human override rate (% of AI recommendations overridden by humans)
Override rationale summary (common reasons for overrides)
Accuracy metrics (if measured; post-issuance audit results)

AI Model Information

Current model version (MCC AI v1.0, deployed March 2026)
Model training data (composition, sources)
Model capabilities (completeness scoring, risk flagging, cross-reference)
Model limitations (confidence bounds, known biases)

AI Performance Audit Results (Annual)

Independent auditor assessment (accuracy, fairness, bias)
Calibration audit findings (per VVB; published with VVB consent)
Bias analysis (geographic, sectoral, language bias testing)

Example Dashboard:

FORMAT ILLUSTRATION — the first real report will be published after the
first full quarter of live operation.
[QUARTER] AI PERFORMANCE
Projects Reviewed: [n]
Recommendations by confidence tier: [HIGH/MEDIUM/LOW/VERY LOW counts]
Human Overrides: [n, with anonymised rationale categories]
Model Accuracy (Post-Issuance Audit): [%]
Bias Audit: [findings]

2.7 Timeline Data (SLA Transparency)

MCC publishes (Monthly):

Project Review Timelines

Average completeness check time (actual vs. 4-hour target)
Average validation time (actual vs. 120-150-day target)
Verification time (actual vs. 60-90-day target)
% of projects meeting SLA (target: ≥95%)

Example:

FORMAT ILLUSTRATION — the first real report will be published after the
first month of live operation.
[MONTH] SLA COMPLIANCE
Completeness Checks: [n] | Average [h] (target: <4h) | [%] on-time
Validations in Progress: [n] | [status vs. 120–150 business days]
Verifications Completed: [n] | Average [d] (target: 60–90 days)
Overall Compliance: [%] (target: ≥95%)

2.8 VVB Data (Performance Dashboard)

MCC publishes (After Year 1 calibration audit):

Per-VVB Performance Metrics

Number of projects validated/verified
Accuracy tier (A, B, or C per calibration audit)
Timeliness compliance (% on-time delivery)
Major findings rate (baseline, common issues found)
Applicant satisfaction (average star rating if surveyed)

Example:

FORMAT ILLUSTRATION — no VVB is yet accredited under MCC-400; the first
dashboard will be published after the first annual calibration audit.
VVB PERFORMANCE DASHBOARD ([period])
Organization: [accredited VVB]
Accreditation: [standard, validity]
Scope: [families]
Projects Completed: [n validations, n verifications]
Accuracy Tier: [A/B/C per calibration audit]
Timeliness: [% on-time]
Major Findings Rate: [%]

2.9 Fee Data (Transparent Schedule)

MCC publishes:

Fee Schedule (Public)

Registration fee (€500 SIDS/LDCs, €1,000 others)
Annual monitoring fee (€1,000-€2,000 per project)
Issuance fee (€0.15-€0.25 per credit)
Any transaction fees (if applicable)

Cost Justification

How registration fee used (intake review, completeness check, staff)
How monitoring fee used (annual governance, registry maintenance)
How issuance fee used (Board oversight, credit generation, programme operations)

Worked Examples (Detailed Calculations)

EXAMPLE PROJECT: 50,000-credit mangrove restoration in Indonesia
────────────────────────────────────────────────────────────────
Registration Fee: €1,000 (standard rate)
Year 1 Annual Fee: €1,000 (monitoring)
Credit Issuance (50,000 × €0.15): €7,500
Total MCC Fees Year 1: €9,500

VVB Fees (Market Rate): ~€10,000-€15,000 (applicant negotiates; MCC does not set)
Government LoA Fee: ~€500-€2,000 (varies by country)

Total Cost to Applicant (Est.): €19,500-€26,500 Year 1
Cost per Credit (Est.): €0.39-€0.53

Note: Prices may differ based on project complexity, VVB selection, geographic factors.
This is an estimate; obtain quotes from VVBs directly.

2.10 Consultation Data (Stakeholder Transparency)

MCC publishes (Upon project registration):

Stakeholder Consultation Records

Consultation dates and locations
Attendee list (names, organizations; with attendee consent)
Key questions raised and project responses
FPIC documentation (for indigenous communities; with community consent)
Comments received during 30-day written period (anonymized)
Project responses to comments

ARTICLE 3: WHAT MCC DOES NOT PUBLISH

MCC withholds from public:

Personal Data (PII)
- Individual names (unless public figure or community leader consenting)
- National ID numbers, passport numbers, family relationships
- Personal contact info (phone, home address)
- Email addresses (project contact shared if permitted; staff emails generally not public)
Commercial-In-Confidence Information
- Applicant financial details (project cost, budget, revenue projections)
- Proprietary baseline methodologies (if confidentiality requested + justified)
- Competitive information (if applicant claims genuine business harm)
Internal AI Model Details
- Model weights and parameters (training details)
- Code repository and technical architecture
- Internal confidence thresholds (only published tiers published, not raw scores)
Security Information
- System vulnerabilities (until patched)
- Account security procedures (to prevent exploitation)
- Backup and disaster recovery procedures
Sensitive Government Relations
- Diplomatic discussions (if related to host country negotiations)
- Confidential government compliance discussions
- Law enforcement requests (unless public, per legal requirement)

ARTICLE 4: PUBLICATION TIMING

4.1 Real-Time Publication

Published within 2 business hours:

Credit issuance (new serials)
Credit retirement (certificates)
Credit cancellation (public notice if fraud/major error)
Project status changes (SUBMITTED → REGISTERED)

4.2 Event-Driven Publication

Published within 1 business day:

Project registration (new project listed)
VVB assignment (public notice)
Validation/Verification report completion

4.3 Periodic Publication (Business Days)

Published within 5 business days:

Board meeting minutes
Governance decisions
Policy amendments

4.4 Aggregate Publication (Scheduled)

Published monthly:

Credit statistics (total issued, retired, cancelled; aggregate buffer)
Application pipeline (projects in completeness check, validation, etc.)

Published quarterly:

AI performance metrics
VVB performance (after initial calibration audits)
Override rates and trends
Claims monitoring (compliant claims, violations)

Published annually:

VVB calibration audit results
Independent AI assessment report
Aggregate impact report (total credits, total credits retired, estimated CO₂ removal, co-benefits)

ARTICLE 5: PUBLIC API

5.1 API Endpoints (Free, Public)

GET /credits/{serial-number}
  → Credit status, owner, vintage, project, retirement info

GET /projects/{project-code}
  → Project details, location, methodology, permanence, co-benefits

GET /registry/stats
  → Aggregate statistics (total issued, active, retired, cancelled)

GET /registry/search?location=&ecosystem=&methodology=
  → Search and filter projects/credits

GET /projects/{id}/validation-report
  → Public validation report (PDF download)

GET /projects/{id}/verification-reports
  → Annual verification reports (PDF download)

5.2 Rate Limiting

Public API: 1,000 requests/day per IP (sufficient for most uses)

Authenticated API: 10,000 requests/day per API key

5.3 Documentation

Comprehensive API documentation at: mcc-registry.org/api-docs

Endpoint descriptions
Parameter options
Response formats (JSON, CSV, XML)
Code examples (Python, JavaScript, R)
Rate limit handling

ARTICLE 6: CORRECTIONS AND RESTATEMENTS

6.1 Data Error Correction Process

If published data incorrect:

Error identified (by MCC, stakeholder, or auditor)
Correction assessed (is this truly an error? documentation review)
Correction approved (MCC Board or technical staff, per significance)
Corrected data republished (with notation: "Corrected [date]")
Original data archived (for audit trail; not deleted)
Stakeholder notification (if material; email to affected parties)

Example:

Original Data: Project MCC-DEMO-XXX0001 issued 50,000 credits (demonstration example)
Error Found: Quantification arithmetic error; should be 48,000 credits
Correction: 2,000 credits cancelled; certificates notified
Republished: April 20, 2026
Archive: Original data preserved with correction note
Notification: Retirement certificate updated; buyers/sellers informed

6.2 Restatement Policy

Material restatement (if major historical data wrong):

Public announcement (press release)
Comprehensive explanation (what was wrong, why, how corrected)
Impact assessment (if restatement affects market price/confidence)
Remediation plan (how to restore trust)

ARTICLE 7: COMPARISON WITH INDUSTRY STANDARD

7.1 Transparency Commitments (Summary)

MCC commits to publishing, by default: project locations and boundaries; baseline and quantification detail; VVB validation and verification reports; permanence assessments; the buffer-pool methodology and formulas; co-benefit quantification; VVB performance data after the first annual calibration audit; board decision rationales; quarterly AI-use metrics; and the fee schedule with its rationale. Applicant financial data is withheld as confidential.

(A comparative table against other programmes was removed in v1.1: unverified claims about third parties' disclosure practices sit poorly with this programme's own prohibition on comparative disparagement. Comparisons, if ever published, must cite each programme's own current documentation.)

ARTICLE 8: STAKEHOLDER FEEDBACK AND TRANSPARENCY AMENDMENTS

8.1 Feedback Mechanism

Stakeholders may request transparency changes:

Email: transparency@mcc-credits.org
Request: "Please publish [data] because [reason]"
Example: "Please publish VVB performance ratings; stakeholders need this to assess credit quality"

MCC Review Process:

Board considers request (quarterly)
Determines: publish, publish with redactions, or decline + rationale
Response provided to requester (within 30 days)
Decision published (if policy change)

ARTICLE 9: POLICY EFFECTIVENESS AND AMENDMENT

9.1 Review Cycle

Policy reviewed semi-annually (March & September). Amendments proposed quarterly; Board approval required.

9.2 Regulatory Alignment

MCC continuously tracks regulatory evolution (CRCF, ICVCM, VCMI) and updates transparency policy to maintain compliance.

Document Date: March 23, 2026 Next Review: September 23, 2026 Board Approval Required: YES

ENDRINGSLOGG v1.1 (24.08.2026)

Fjernet: fabrikkert innløsning (Maersk/ABC Trading/PT Mangrove), fabrikkert sertifikat, fabrikkert styrevedtak (PT-2026-001, 7-0), fabrikkerte AI-/SLA-driftstall, TÜV SÜD-dashboard med rating og anbefaling, sammenligningstabell mot Verra/Gold Standard, «exceeding industry standard»-påstanden. Alle eksempler er nå demonstrasjonsmerket eller formatskjeletter, med serialformat etter MCC-800 art. 27. Grunnlag: regelverksrevisjonen 24.08.2026 (vedlegg 6).

Vedtatt 24.08.2026 ved FD-2026-08-24. Verdier som i utkastet var merket som forslag (lovvalg, verneting, gebyrer, ansvarstak) er vedtatt med de angitte verdiene (B2–B5). Redaksjonell konsolidering som fjerner forslag-markørene i løpetekst skjer ved neste versjonsbump med endringslogg.