Programme documents
The adopted rulebook, published in full text. Every policy, template, guidance and annex below was adopted on 24 August 2026 by founder decision FD-2026-08-24 (one methodology text on 1 September by FD-2026-09-01). The decision records themselves — that founder decision, the draft minutes of the Board’s constituting meeting of 26 August, the founder decisions of 1, 3, 4 and 7 September and the founder direction of 1 October — are published at the bottom of this page, each as the programme record holds it, with a notice where something on its face has since been overtaken. Whether each is signed is kept in the decision book, not on this page.
The standards series is under full revision
An independent programme-integrity desk review of the rulebook, dated 3 September 2026, found the adopted corpus internally inconsistent on points that matter — among them the unit definitions, the family taxonomy, the Article 6 language, and who is competent to take which decision. Founder decision FD-2026-09-03 accepted the review in full and ordered a rewrite of the whole normative suite. That 3 September decision has no recorded Board ratification. This is a different footing from the 24 August rulebook decision (FD-2026-08-24): that one was taken up at Governing Board meeting GB-2026-001, item 2, on 26 August 2026, and recorded as ratified as to substance — though the resolution itself remains attested, not signed.
Every document on this page is the instrument the Programme applies, and stays so until a replacement is adopted — with the two qualifications stated below. The rewritten texts exist as consultation drafts, not as rules: none of them is in force, none may be relied on, and each is published here when its consultation opens.
What “in force” can and cannot be shown to mean here. Twelve of the standards on this page carry no adopting instrument in the programme record — no signed decision put them in force. They are not in the same position, and the register now separates them. Eight have no instrument anywhere: MCC-001, MCC-200, MCC-800, MCC-BPM, MCC-CADCP, MCC-ESS, MCC-HCA and MCC-SDCF. Two — MCC-400 v1.1 and MCC-700 v3.1 — rest on an instrument that is unsigned. Two — MCC-100 v2.2 and MCC-850 v1.2 — rest on an instrument that adopts an earlier version number than the one served here, v2.1 and v1.1 respectively, so no instrument creates the version on the file. An earlier version of this paragraph said three and nine; the register column says four and eight, about the same twelve rows, and the column is right. The instrument register states this and counts them. The Programme applies these texts and publishes them because applying an unevidenced rule openly is better than applying it silently; it does not assert that any of the twelve can be shown to have been enacted.
A decision on this point has been taken and not carried out. Item D5 of founder decision FD-2026-09-03 reclassifies every suite document carrying an unevidenced APPROVED status to draft, consultation or pilot, and withdraws the prior PDFs as controlled copies. Thirteen passages in the rewritten suite recite it as done. It has not been done: the register still records the twelve as in force and this page still serves them. One sibling item — D1, abolishing an instrument type — has been carried out in full. A second, D8, staying two entry-into-force dates, has been carried out here and not on the files: the served text of MCC-400 v1.1 still states in its document control block that Section 18 enters into force on 17 September 2026. It does not, on that date or any other until the stay is lifted. Correction notices were served on that file and on five others on 8 September 2026. An earlier version of this paragraph said both items had been carried out in full; that was wrong, and it was wrong because the stay had been recorded on this page without anyone opening the document the page serves. The Programme records the inconsistency rather than resolving it here, because FD-2026-09-03 is unsigned and scheduled for signature on 23 September 2026, and giving effect to an unsigned decision is the practice this review exists to end. Either D5 is executed with its siblings or the different treatment is recorded with reasons.
The consultations. Five rule-change consultations were open on 3 September and every one of them amends a document this rewrite replaces. All five are stayed: they no longer accept comment, they have not been decided, and each says on its own page why it stopped. They are listed under “Stayed” on the consultation register. The consultations closing on 8 and 9 September concern procedures and templates the rewrite does not replace, and run to their published dates.
The second qualification. The entry into force of MCC-400 Addendum 1 and of MCC-850 Amendments 1 and 2, each printed as taking effect on 17 September 2026, is stayed by item D8 of that decision. Those instruments will not come into force on that date. Nothing in them applies, and nothing elsewhere on this site should be read as giving them effect.
Two consequences are worth stating plainly. A Claims Code has been drafted for the first time; once adopted it is a precondition for any public claim about credits issued under this programme. And the methodologies previously listed as active are reclassified as concepts: no methodology in this programme has completed the dossier, peer review, consultation and signed approval that its own framework requires.
Counterparty policies
The default-public disclosure commitment: what MCC publishes for every project, credit, retirement and governance decision — and the narrow set of things it withholds. This page exists because this policy requires it.
Correction noticeCorrection notice, 4 September 2026 (revised the same day). The Programme publishes contact details at two domains that do not exist: mcc-credits.org and mcc-registry.org. Both return NXDOMAIN, neither has a mail exchanger, and neither has ever been… Full notice on the document page.
How AI is and is not used in the programme: AI-assisted screening with mandatory human review, and the boundaries that keep verification a human, third-party responsibility. Companion to the MCC-850 AI Governance Standard.
Correction noticeCorrection notice, 4 September 2026 (revised the same day). The Programme publishes contact details at two domains that do not exist: mcc-credits.org and mcc-registry.org. Both return NXDOMAIN, neither has a mail exchanger, and neither has ever been… Full notice on the document page.
The contribution-first claims framework: what buyers may and may not say when retiring MCC credits. No offsetting, neutrality or net-zero claims; permitted language is enforced at the point of retirement.
Correction noticeCorrection notice, 4 September 2026 (revised the same day). The Programme publishes contact details at two domains that do not exist: mcc-credits.org and mcc-registry.org. Both return NXDOMAIN, neither has a mail exchanger, and neither has ever been… Full notice on the document page.
Terms of use for registry account holders: accounts, transfers, retirements, data handling and the registry operator’s obligations.
Correction noticeCorrection notice, 4 September 2026 (revised the same day). The Programme publishes contact details at two domains that do not exist: mcc-credits.org and mcc-registry.org. Both return NXDOMAIN, neither has a mail exchanger, and neither has ever been… Full notice on the document page.
Terms for project proponents applying to the programme: eligibility, submission obligations, fees, and what applicants can expect from the review pipeline.
Correction noticeCorrection notice, 4 September 2026 (revised the same day). The Programme publishes contact details at two domains that do not exist: mcc-credits.org and mcc-registry.org. Both return NXDOMAIN, neither has a mail exchanger, and neither has ever been… Full notice on the document page.
Terms for validation and verification bodies, including the professional indemnity requirement of USD 2,000,000 per claim / USD 5,000,000 in aggregate (art. 11.1, aligned across the corpus by FD-2026-08-24 item D7).
Correction noticeCorrection notice, 6 September 2026. The section of these Terms describing the registration decision says the Board 'Confirms VVB decision (usually rubber-stamp for competent VVBs; rare overrule)'. Both halves of that sentence are wrong, and the Programme… Full notice on the document page.
How the programme positions its units legally: not securities, not financial instruments, not offsets — and the regulatory perimeter the programme operates within.
Correction noticeCorrection notice, 6 September 2026. The full-corpus audit (PAR-2026-002) found more in this instrument than in any other, and the reason matters: this is the document a host-country ministry, a verification body, an insurer or a funder would actually rely on… Full notice on the document page.
Methodology and templates
The eleven-section template (A–K) every project must complete for independent validation, written credit-type-neutrally across the five methodology families.
Correction noticeCorrection notice, 10 September 2026. Three things on the face of this template are wrong. Two sections refer to "the nine safeguard principles" and a "Safeguards self-assessment checklist (nine principles)"; the MCC Environmental and Social Safeguards Policy… Full notice on the document page.
Family guidance for pollution-prevention projects: flow-basis quantification, 1 MCU = 100 kg verified mass, 10% uncertainty buffer (FD-2026-08-24 item D6).
Correction noticeCorrection notice, 10 September 2026. This Guidance's Year 1 worked example ("62 tonn hevet ... + 6 tonn forebygget ... Usikkerhetsbuffer 10 %: 68 t × 0,90 = 61,2 t ... 612 MCU") applies the same 10% uncertainty buffer, and the same unit, to prevented mass as… Full notice on the document page.
The consolidated ten-module methodology text for MCC-M008 (ghost gear recovery, MCC-MCU). It introduces no new normative choices: every provision codifies substance adopted with the 24 August 2026 approval, with the source stated per module.
Correction noticeCorrection notice, 10 September 2026. Two things on the face of this methodology are wrong. First, its adoption line promises "board ratification 23 September 2026" of this methodology text. Methodology approval and amendment is a Tier 4 act reserved to the… Full notice on the document page.
Standards annexes and amendments
The programme’s single source of definitions. Where a programme document conflicts with this register, the register prevails.
Correction noticeCorrection notice, 10 September 2026. Three entries in this Register, the Programme's single source of definitions, are wrong on their face. First, the entry for MCC-HYB ("Hybrid-enhet utstedt under F02/F05-metodologier med 30-års permanenshorisont (Option… Full notice on the document page.
Amendment instrument converting the AI confidence canon to a 0–100 integer scale; consolidated into MCC-850 v1.2.
Correction noticeCorrection notice, 10 September 2026. This instrument's adoption line reads "v1.0 — ADOPTED (FD-2026-08-24, sak D16 d; styreratifisering utestående)" — stating board ratification as outstanding. It is not: the decision register records FD-2026-08-24 as… Full notice on the document page.
Regularises Article 27 of the Registry Operations Standard (the canonical serial-number format) in the v1.1 re-issue.
Correction noticeCorrection notice, 10 September 2026. This note's adoption line reads "v1.0 — ADOPTED (FD-2026-08-24, sak D13/D16 e; styreratifisering utestående)" — stating board ratification as outstanding. It is not: the decision register records FD-2026-08-24 as ratified… Full notice on the document page.
Governance decisions
The adopting instrument for the consolidated rulebook. It is explicit about its own basis: a founder decision, made while the programme board is not yet constituted; formal board ratification is the first item of business when it is.
Correction noticeCorrection notice, 10 September 2026. This decision record's item D11 states "MCC-700 som eneste styringsarkitektur (⅔ av avgitte stemmer; quorum 50 % + 1)" — a flat two-thirds-of-votes-cast threshold. MCC-700 v3.1, the instrument this item purports to… Full notice on the document page.
The draft minutes of 26 August 2026: constitution of the Board, election of the Chair, ratification of FD-2026-08-24, the two amendment intentions, the F03 deadline and SC-2026-001. Served verbatim from the archived draft, with the administration note of 31 August recording what the founder confirmed on 27 August.
Correction noticeNotice, 1 October 2026. This is the draft as archived in 00_Styring_og_Vedtak. Its times, form, attendance, secretary, chair-of-meeting, conflict-of-interest and vote fields are blank, and so is its signature block; the completion sheet of 6 September… Full notice on the document page.
Six items of 1 September 2026: MCC-M008 v1.1 adopted as editorial codification (D1); F02 kelp quantification position C as a drafting direction (D2); MCC-200 Am1 process alternative (a) (D3); M012 held (D4); F03 guidance batched with v1.1 (D5); a ratification list in place of a board pack (D6). Ratification tabled for 23 September 2026.
Correction noticeNotice, 1 October 2026. Three things this record expected have since gone differently, and the text is unchanged because a decision record is not amended after the fact. (1) It counts thirteen open consultations to be decided at their closings, including… Full notice on the document page.
The decision that accepted the programme-integrity review of 3 September 2026 and ordered the rewrite of the normative suite: unit architecture (D1), the canonical family map (D2), Article 6 voluntary-first (D3), the governance model (D4), the five-tier hierarchy (D5), methodology status and the GFS pilot (D6), the Claims Code as a hard gate (D7), and the stay of the 17 September entries into force (D8).
Correction noticeNotice, 1 October 2026. This is the summary protocol of the decision, as archived in 00_Styring_og_Vedtak, and it is the text an in-platform signature of FD-2026-09-03 binds to. It names two full-text decision documents ("FD-2026-09-03_decisions_1-7.md, 31… Full notice on the document page.
Adoption of six consultation texts at their close (item 1), the consultation calendar for the rewritten suite — opening 1 October 2026 (item 2), external peer review of M001–M003 by 30 November with the 30 September adoption abandoned (item 3), the §2.9 fee example marked as an illustration (item 4), recovery of the registry database (item 5), and the matters reserved to the Board (item 6).
Correction noticeNotice, 1 October 2026. Served as archived in 00_Styring_og_Vedtak: the draft prepared for signature, which the register records as ATTESTED by the founder on 4 September 2026 with the executed copy not received. Four things on its face are overtaken or… Full notice on the document page.
The omnibus statement of 7 September 2026, transcribed from the decision register, which records seven determinations as adopted by founder decision under the transitional regime (A1–A7), item D5 of FD-2026-09-03 as scheduled instrument by instrument rather than executed (A8), and the board appointments as not carried because they are the Board's to make (A9, recorded as a nomination).
Correction noticeNotice, 1 October 2026. The programme record holds no separate document of the founder's statement of 7 September 2026; the decision register entry is its record, and the text below transcribes that entry so that the decision has a text to be signed against.… Full notice on the document page.
The founder's written instructions of 29 September and 1 October 2026, recorded as a direction to the programme administration: the acts they authorise without further instruction, the statement that no legal entity has yet been incorporated, how the working markers in the 28 suite texts are resolved into cited statements and consultation questions, and the opening of the rewritten suite. It adopts no instrument, and everything an instrument in force reserves to the Governing Board is listed and left undecided.
Standards series and adopted policies
Version discipline. Adopted documents change only by amendment with a version bump (FD-2026-08-24, item D16). Superseded versions are retained in the programme archive. Corrections to anything published here follow the correction procedure in the Transparency Policy — republished with a dated correction notation, never silently.