Skip to main content

← Governance

Document hierarchy and precedence register

Every instrument the programme has made, by tier — including the annexes and amendments to a standard, and the policies and counterparty terms adopted alongside them. Where two instruments conflict, the lower tier number prevails. This register records, for each: the version in force, the function that owns it, and the signed instrument that adopted it.

What this register did not carry until 4 September 2026

It listed the standards and nothing annexed to them. One of the instruments it omitted was the MCC-100 Annex — Definitions Register, in force since 24 August 2026 and published in the served corpus. Two successive reviews then recorded that instrument as never having existed, because this page is the shelf a reader checks. Sixteen annexes, amendments, policies and terms are added here, and an annex now says which instrument it hangs from. The finding is at MIR-2026-001 rev 2 §7.

12 of 28 instruments the Programme asserts as adopted cannot be shown to have been adopted

An instrument in force is normally adopted by a signed decision, and a register cites it. For every standard in this corpus no such decision is in the programme record: those versions were advanced editorially. The annexes, policies and terms adopted by founder decision on 24 August 2026 do cite one. Of the standards, four rest on an instrument and eight on nothing. Two of the four — MCC-400 v1.1 and MCC-700 v3.1 — rest on an instrument that is unsigned; the other two — MCC-100 v2.2 and MCC-850 v1.2 — rest on an instrument that adopts an earlier version number than the one recorded here, so no instrument creates the version served. Three of the four cite MCC-BDR-2026-002, an unsigned reconstruction of a meeting of a board not then constituted, which is itself before the Board. 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. That is a finding of the evidence review of 3 September 2026, not a gap in this page, and it is published because a reader is entitled to know what a version number here does and does not mean. The rewritten suite resets every document to a new major version adopted by one instrument, which is what ends it.

Item D5 of founder decision FD-2026-09-03 reclassifies every one of these instruments out of “in force” for exactly this reason. Updated 7 September 2026: that decision is now attested by the founder, and D5 is scheduled rather than executed in one act — each version is reclassified when its successor is adopted, and not before. The reason is on the register row of each instrument, and the decisive one is that the twelve include MCC-001 v2.0, the Charter itself. Withdrawing the constitution while its successor is a consultation draft would leave the Programme with none, and would dissolve clause 0084 (tier precedence), clause 0081 (credit types reserved to Tier 3) and clause 0093 (the amendment threshold) — which are the grounds of the determinations adopted by the same decision, and the instrument under which the Governing Board exists. An instrument cannot be repealed into a vacuum, and MCC-700 v4.0-draft clause 22.4 states the principle the Programme has already accepted: no amendment takes effect before its normative dependencies exist. This count therefore keys on a provenance state recorded against each row rather than on its status, so that executing D5 corrects the register without removing the finding from this page. An instrument reclassified to draft is still an instrument nobody can show was enacted. Two earlier versions of this count keyed on status and would each have fallen silently to zero; that is recorded here because the failure is the same one the count exists to report.

Thirteen of the twenty-five documents in force say something about themselves that the record does not bear out

The count above asks whether an instrument put a document in force. This one asks a different question, answered on 8 September 2026 by opening each served file rather than reading this register: does the document, on its own cover, say something the record contradicts. Six do, and seven print “Status: APPROVED” with no approver, no date of approval and no instrument anywhere.

MCC-700 v3.1 carries “Status: DRAFT — For Foundational Review” on its cover. It is served as the Tier 2 governance instrument in force, and founder decision FD-2026-08-24 item D11 designates it as the Programme’s sole governance architecture. MCC-400 v1.1 states that Section 18 enters into force on 17 September 2026, which item D8 of FD-2026-09-03 stayed; the file still announces the date, and nothing in Section 18 applies on it or after it. MCC-800 v1.1 carries the document control table of v1.0. MCC-100 v2.2 and MCC-850 v1.2 state an entry into force of 17 August 2026, the date of a board meeting nine days before that board existed, and carry version numbers no instrument creates. MCC-100 Amendment 1 recites a two-thirds majority that no record contains — and it is the case that made this a separate question, because its adopting instrument is recorded, so the older count passed it.

Correction notices are served on all six on the documents page. The texts are unchanged, because amending an adopted instrument is not an administrative act. What the corrected face should say is a determination for the Governing Board on 23 September 2026; recording what it says today is not.

Tier 1 — Charter and Constitution

InstrumentVersionStatusOwnerAdopted by
MCC-001
Charter and Constitution
No signed approval instrument for v2.0 is in the programme record (evidence gap E01, ER-2026-001 §B3). FD-2026-09-03 item D5 reclassifies this version. Executed on adoption of its successor, not before: withdrawing it while the successor is a consultation draft would leave the rules it carries with no carrier (MCC-700 v4.0-draft cl. 22.4). Recorded 7 September 2026 under FD-2026-09-07 item A8. Until then this version remains the controlled text, and its provenance_state continues to record what is and is not known about how it came to be in force. AND SPECIFICALLY FOR THIS INSTRUMENT: MCC-001 v3.0-draft states that v2.0 "is meanwhile reclassified DRAFT per FD-2026-09-03 item D5". That cannot take effect while v3.0 is a consultation draft. It would leave the Programme with no constitution, and would dissolve cl. 0084 (tier precedence), cl. 0081 (credit types reserved to Tier 3), cl. 0093 (the amendment threshold) and cll. 0090-0097 (the amendment procedure) — the grounds of MCC-F04-2026-001, MCC-WDR-2026-002 and Gates 1 and 4 of MCC-BP-2026-001, all adopted by the same decision that contains D5. It is also the instrument under which the Governing Board exists. Referred to the Board on 23 September 2026.
2.0In forceGoverning BoardNo adopting instrument in the programme record
Successor draft: MCC-001 v3.0-draft
MCC-MRC-2026-001
Resolution constituting the Methodology Review Committee
Drafted 8 September 2026. A resolution in discharge of a standing duty under MCC-001 v2.0 cl. 0045, which directs the Board to delegate operational authority to a Methodology Review Committee. NOT an amendment: no tier changes, no consultation is required and no notice period runs. It is the shortest instrument on the shelf because there is nothing to argue - the duty is unconditional, the composition is specified at cl. 0047, and no other instrument has to move first. Until it is taken, no Tier 4 instrument can lawfully be amended by anyone, MCC-200 cl. 0120 cannot be corrected, no methodology can be approved or retired, and MCC-CR-2026-001 cannot commence because its commencement is tied to MCC-CR-2026-002. Recorded at tier 1 because its authority is the Charter, not because it amends it.
1.0-draftDraftBOARDNo adopting instrument in the programme record

Tier 2 — Governance

InstrumentVersionStatusOwnerAdopted by
MCC-700
Governance and Appeals
No controlled text or adoption record for v2.0 is in the programme record. FD-2026-09-03 item D5 reclassifies this version. Executed on adoption of its successor, not before: withdrawing it while the successor is a consultation draft would leave the rules it carries with no carrier (MCC-700 v4.0-draft cl. 22.4). Recorded 7 September 2026 under FD-2026-09-07 item A8. Until then this version remains the controlled text, and its provenance_state continues to record what is and is not known about how it came to be in force.
3.1In forceProgramme AdministratorNo adopting instrument in the programme record
Successor draft: MCC-700 v4.0-draft

Tier 3 — Programme rules

InstrumentVersionStatusOwnerAdopted by
MCC-100
Programme Standard
No Governing Board adoption record for v2.0; no instrument creates the "v2.2" designation. The Board was constituted 26 August 2026. FD-2026-09-03 item D5 reclassifies this version. Executed on adoption of its successor, not before: withdrawing it while the successor is a consultation draft would leave the rules it carries with no carrier (MCC-700 v4.0-draft cl. 22.4). Recorded 7 September 2026 under FD-2026-09-07 item A8. Until then this version remains the controlled text, and its provenance_state continues to record what is and is not known about how it came to be in force.
2.2 (consolidated)In forceProgramme AdministratorNo adopting instrument in the programme record
Successor draft: MCC-100 v3.0-draft
MCC-100 Annex — Definitions Register
Definitions Register
Annexed to MCC-100
The programme's single definition source: where a programme document conflicts with it, it prevails. Adopted to close rulebook-audit finding K12. It settles units, taxonomy, quantification, registry terms, actors and claims discipline; it does not register the names of governance bodies or of instruments, which Amendment 1 adds.
1.0In forceProgramme AdministratorFD-2026-08-24 item D12
Successor draft: MCC-100 Annex — Definitions Register, Amendment 1 (v2.0-draft)
MCC-100 Am.1
Amendment 1 — Revision loop and workflow stages
Annexed to MCC-100
Adopted by a board decision record that is an unsigned reconstruction of a meeting of a board not then constituted. That record is item 1 of the board meeting of 23 September 2026; see the decision book.
1.0In forceProgramme AdministratorMCC-BDR-2026-002
MCC-800
Registry Operations Standard
No approval instrument for v1.0 and no instrument creating v1.1. FD-2026-09-03 item D5 reclassifies this version. Executed on adoption of its successor, not before: withdrawing it while the successor is a consultation draft would leave the rules it carries with no carrier (MCC-700 v4.0-draft cl. 22.4). Recorded 7 September 2026 under FD-2026-09-07 item A8. Until then this version remains the controlled text, and its provenance_state continues to record what is and is not known about how it came to be in force.
1.1In forceProgramme AdministratorNo adopting instrument in the programme record
Successor draft: MCC-800 v2.0-draft
MCC-800 Re-issue Note
Re-issue note for MCC-800 v1.1
Annexed to MCC-800
Records what the v1.1 designation covers. It does not itself create v1.1: no instrument does.
1.0In forceProgramme AdministratorFD-2026-08-24
MCC-600
Claims Code
Referred to across the corpus as though it existed. It did not. First drafted 3 September 2026.
—Not yet madeProgramme AdministratorNo adopting instrument in the programme record
Successor draft: MCC-600 v1.0-draft
MCC-ROI
Register of Interests and Conflict of Interest Screening Procedure
Required by MCC-001 v2.0 cl. 0055 (adopted) and MCC-700 cl. 13.4 (never in force — cl. 18.1 leaves the commencement date blank), and by the Conflict of Interest Screening Procedure referred to in the External Institutional Launch Pack. Drafted 4 September 2026 and not opened for consultation. The platform does hold a store for governance-body declarations — interest_disclosures, keyed to governance_appointments — and one declaration has been filed: the Founder's, on 26 August 2026. The Chair has filed none. The draft states no VVB impartiality rule, which MCC-400 cl. 1.4 reserves to that Standard, and fixes declaration content to MCC-FORM-013 rather than restating it. Code and tier proposed, not yet confirmed by decision.
1.0-draftDraftProgramme AdministratorNo adopting instrument in the programme record
MCC-APP
Appeals Procedure
Drafted 4 September 2026 and not opened for consultation. Five instruments confer a right of appeal and name five different forums — the Review and Appeals Authority, the Appeals Body, the Appeal Officer, the Appeals Panel and the Independent Appeals Panel — and none of the five has a single appointee. The public accreditation page, the KYC procedure and the Applicant Terms all state an appeal route under MCC-700 section 15, which has never commenced. Nothing has been filed. The draft supplies the machinery and states the consequence rather than pretending the body exists: an appeal today is registered, acknowledged and held open, and the decision under appeal is not implemented further. Code and tier proposed, not yet confirmed by decision.
1.0-draftDraftProgramme AdministratorNo adopting instrument in the programme record
MCC-CR-2026-001
Determination adopting one code register — Part A: the family taxonomy, the instrument dictionary and buffer scope (Tier 3)
Drafted 8 September 2026 and split on the day it was drafted, before issue. It was first written as a single act covering families, instruments and methodology codes together, on MCC-TAX-2026-001 s.B.7's reasoning that all three axes must be settled at once. It could not lawfully have been taken in that form: the family taxonomy is Tier 3 (Board or delegated committee, cl. 0081) and the methodology codes are Tier 4 (Methodology Review Committee with peer review, cl. 0082), and one instrument cannot carry two approval procedures. What s.B.7 protects against is preserved by tying commencement to MCC-CR-2026-002 rather than by a single signature. A second error is corrected with it: the first draft said unblocking Tier 4 needed a Tier 2 amendment aligning MCC-700's body names to MCC-001's. It does not - cl. 0045 already directs the Board to create the committee, so constituting it is compliance with a standing duty, not an amendment.
1.0-draftDraftADMINISTRATIONNo adopting instrument in the programme record

Tier 4 — Technical standards

InstrumentVersionStatusOwnerAdopted by
MCC-200
Methodology Framework
No signed approval instrument for v2.0. FD-2026-09-03 item D5 reclassifies this version. Executed on adoption of its successor, not before: withdrawing it while the successor is a consultation draft would leave the rules it carries with no carrier (MCC-700 v4.0-draft cl. 22.4). Recorded 7 September 2026 under FD-2026-09-07 item A8. Until then this version remains the controlled text, and its provenance_state continues to record what is and is not known about how it came to be in force.
2.0In forceProgramme AdministratorNo adopting instrument in the programme record
Successor draft: MCC-200 v3.0-draft
MCC-400
VVB Accreditation and Performance Standard
No approval record for v1.0. Addendum 1 entry into force stayed by FD-2026-09-03 D8. FD-2026-09-03 item D5 reclassifies this version. Executed on adoption of its successor, not before: withdrawing it while the successor is a consultation draft would leave the rules it carries with no carrier (MCC-700 v4.0-draft cl. 22.4). Recorded 7 September 2026 under FD-2026-09-07 item A8. Until then this version remains the controlled text, and its provenance_state continues to record what is and is not known about how it came to be in force.
1.1 (consolidated)In forceProgramme AdministratorNo adopting instrument in the programme record
Successor draft: MCC-400 v2.0-draft
MCC-400 Add.1
Addendum 1 — AI-augmented validation and verification
Annexed to MCC-400
Entry into force, printed as 17 September 2026, is stayed by FD-2026-09-03 item D8. It has never been in force and nothing in it applies. Its adopting record is the unsigned reconstruction above.
1.0StayedProgramme AdministratorMCC-BDR-2026-002
MCC-850
AI Governance Standard
No approval record by the body named in Article 43; no instrument creates the "v1.2" designation. Amendments 1 and 2 stayed by FD-2026-09-03 D8. FD-2026-09-03 item D5 reclassifies this version. Executed on adoption of its successor, not before: withdrawing it while the successor is a consultation draft would leave the rules it carries with no carrier (MCC-700 v4.0-draft cl. 22.4). Recorded 7 September 2026 under FD-2026-09-07 item A8. Until then this version remains the controlled text, and its provenance_state continues to record what is and is not known about how it came to be in force.
1.2 (consolidated)In forceProgramme AdministratorNo adopting instrument in the programme record
Successor draft: MCC-850 v2.0-draft
MCC-850 Am.1
Amendment 1 — Repeal of Article 28
Annexed to MCC-850
Entry into force, printed as 17 September 2026, is stayed by FD-2026-09-03 item D8. Its operative regime has never taken effect.
1.0StayedProgramme AdministratorMCC-BDR-2026-002
MCC-850 Am.2
Amendment 2 — Automated completeness and degraded mode
Annexed to MCC-850
Further effect stayed by FD-2026-09-03 item D8. Its own effective date is recorded inconsistently across the programme record; the stay applies on either reading.
1.0StayedProgramme AdministratorMCC-BDR-2026-002
MCC-850 Am.3
Amendment 3 — Confidence scale 0–100
Annexed to MCC-850
Settles the confidence score as an integer 0–100 with the escalation bands, against the 0–1 scale the platform had implemented.
1.0In forceProgramme AdministratorFD-2026-08-24 item D16(d)
MCC-M008 Am.1
Amendment 1 — Provenance of credited gear, and the prevention limb
Annexed to MCC-M008
Drafted 4 September 2026 following PAR-2026-001 findings F2 and F3, revised 6 September 2026 following PAR-2026-002, and not opened for consultation. MCC-M008 is the Programme's only approved methodology and both projects in the register sit in its family. It contains no provenance requirement: the eligibility conditions require a legal right to operate, a chain of custody running forward from the recovery event, an additionality test and a boundary, but not that the gear was in the sea before the project or that it was lost by anyone other than the proponent. Separately, the applicability module brings prevented gear loss into scope while the methodology's unit is defined for recovered mass, with no quantification, monitoring or evidence rule for prevention anywhere in the methodology. The draft first said no prevention rule existed to adopt; that premise was false and is retracted. The F04 Applicant Guidance v1.1, in force since 24 August 2026, supplies a mass-denominated rule — baseline loss rate multiplied by a measured, not assumed, reduction — and credits prevented tonnes in its own worked example, so two adopted instruments give a verifier opposite answers on the same issuance. The amendment inserts provenance as an eligibility condition, bars placed gear outright, excludes the proponent's own recent losses, requires evidence of submersion, and makes provenance a distinct assertion the VVB must test. On the second limb it no longer suspends: it lifts the adopted F04 rule into MOD-03 where MCC-200 cl. 0026 requires the calculation method to sit, and adds the rules that rule lacks — what makes a baseline loss rate measured rather than assumed, attribution against a control rather than to a fall in fishing effort, a bar on crediting the same gear twice across the two limbs, an annual monitoring obligation, and what the VVB must decline. It corrects two citations in the claims module. Every provision narrows eligibility, subjects existing crediting to an evidence standard, or corrects a reference; none widens the unit, and no unit has ever been issued under M008.
1.0-draftDraftProgramme AdministratorNo adopting instrument in the programme record
MCC-F01 M001-M003 v0.2
Blue Carbon Sequestration — Methodologies M001, M002, M003 (CANDIDATE v0.2)
Drafted 5 September 2026 following PAR-2026-001 and its workpapers F, G, I and J, and NOT opened for consultation. The v0.1 candidate is open for consultation until 30 September 2026 and this text does not replace it; the served v0.1 text is hash-pinned and was left untouched. v0.2 adds MOD-03A, the soil organic carbon equation the texts credited a pool without having: stock as bulk density times carbon fraction times thickness, the compaction correction that gives "depth-corrected" a meaning, a site-specific LOI calibration requirement, mandatory separation of live roots from the soil pool so that below-ground biomass is not credited twice, a fixed benchmark datum, and four admissible rate estimators of which the surface-referenced stock difference is not one. MOD-03.6 is rewritten to name a single interval, to require at least 100,000 draws or a stated convergence criterion, to draw every multiplicative correction inside the propagation, and to bar issuance on a verification that fails its own adequacy test. The leakage citation is corrected and the absence of any programme-level leakage requirement disclosed. The code conflict at MCC-200 cl. 0120 is disclosed rather than resolved. Both worked examples were recomputed: the seagrass example survives execution at 50.8 tonnes against 50 asserted, and the salt marsh example falls from 79 to 39 tonnes a year once the autochthonous correction that sheet already required is applied. Three defects are outside this text to fix and are named in its schedule of changes. M001-M003 remain UNDER REVIEW and no project may be registered against them.
0.2-draftDraftProgramme AdministratorNo adopting instrument in the programme record
MCC-CR-2026-002
Determination adopting one code register — Part B: the methodology codes (Tier 4)
Drafted 8 September 2026. Allocates M101-M104 to the four methodologies that exist, conforms MCC-200 cl. 0120, and retires M001-M010 as codes without deleting them from the code register. Cannot presently be taken by anyone: cl. 0082 reserves Tier 4 to the Methodology Review Committee with peer review, and that committee has never been constituted. Published in that state deliberately - an instrument nobody can lawfully adopt is a fact about the Programme's governance, and holding it back until the committee exists would conceal the one dependency that matters. Commencement is tied to MCC-CR-2026-001.
1.0-draftDraftADMINISTRATIONNo adopting instrument in the programme record

Tier 5 — Policies, procedures, templates and guidance

InstrumentVersionStatusOwnerAdopted by
MCC-BPM
Buffer Pool Management Policy
No signed approval instrument in the programme record. FD-2026-09-03 item D5 reclassifies this version. Executed on adoption of its successor, not before: withdrawing it while the successor is a consultation draft would leave the rules it carries with no carrier (MCC-700 v4.0-draft cl. 22.4). Recorded 7 September 2026 under FD-2026-09-07 item A8. Until then this version remains the controlled text, and its provenance_state continues to record what is and is not known about how it came to be in force.
1.0In forceProgramme AdministratorNo adopting instrument in the programme record
Successor draft: MCC-BPM v2.0-draft
MCC-CADCP
Corresponding Adjustment and Double Counting Prevention Policy
No approval instrument in the programme record. FD-2026-09-03 item D5 reclassifies this version. Executed on adoption of its successor, not before: withdrawing it while the successor is a consultation draft would leave the rules it carries with no carrier (MCC-700 v4.0-draft cl. 22.4). Recorded 7 September 2026 under FD-2026-09-07 item A8. Until then this version remains the controlled text, and its provenance_state continues to record what is and is not known about how it came to be in force.
1.0In forceProgramme AdministratorNo adopting instrument in the programme record
Successor draft: MCC-CADCP v2.0-draft
Claims Policy
Claims and Use of Credits Policy
Section 4 is the legal basis of the programme's claims prohibition — not MCC-800, which the platform cited in error until 31 August 2026 — and it is enforced in the registry by a database trigger. Designating it as MCC-600 is proposed in MCC-800 Amendment 1, whose consultation is stayed.
1.1In forceProgramme AdministratorFD-2026-08-24
Successor draft: MCC-600 Claims Code v1.0-draft
Transparency Policy
Transparency and Public Disclosure Policy
1.1In forceProgramme AdministratorFD-2026-08-24
AI Human Oversight Policy
AI and Human Oversight Policy
Escalates to a "Technical Committee" that no instrument constitutes or defines (MIR-2026-001 rev 2 section 3.8).
1.1In forceProgramme AdministratorFD-2026-08-24
Applicant Terms
Applicant Terms
1.1In forceProgramme AdministratorFD-2026-08-24
Registry Terms
Registry Terms
1.1In forceProgramme AdministratorFD-2026-08-24
VVB Terms
VVB Accreditation and Engagement Terms
Article 11.1 carries the professional indemnity requirement set by FD-2026-08-24 item D7 (USD 2m per claim / USD 5m aggregate).
1.1In forceProgramme AdministratorFD-2026-08-24
PDD Template
Project Design Document template
1.1In forceProgramme AdministratorFD-2026-08-24
F04 Guidance
F04 Marine Pollution Prevention — Applicant Guidance
The four sibling family guidance documents (F01, F02, F03, F05) are published in the served corpus at v1.0 and are being reissued with the rewritten suite. PAR-2026-002: this Guidance, and not the methodology it guides, carries the calculation rule for the prevention limb of the MCC-MCU (delivery is verified mass removed or prevented; prevented mass is the baseline loss rate multiplied by a measured, not assumed, reduction). MCC-200 cl. 0026 requires the calculation method to sit in the methodology's MOD-03, and MCC-M008 MOD-03 item 1 defines the unit for recovered mass only, so the two instruments give a verifier opposite answers on the same issuance. MCC-M008 Amendment 1 proposes to lift this rule into MOD-03 and to add the evidence, attribution and monitoring rules it lacks. Until that is adopted, the Guidance's worked example, which applies the same 10 per cent buffer to prevented as to recovered mass, is not to be relied on for an issuance.
1.1In forceProgramme AdministratorFD-2026-08-24
MCC-M008
Marine Gear Loss Prevention — methodology
Annexed to MCC-200
The programme's only approved methodology. One MCU represents 100 kg of gear recovered or prevented, with a 10 per cent uncertainty buffer (FD-2026-08-24 item D6).
1.1In forceProgramme AdministratorFD-2026-09-01
MCC-ESS
Environmental and Social Safeguards Policy
No signed approval instrument in the programme record. FD-2026-09-03 item D5 reclassifies this version. Executed on adoption of its successor, not before: withdrawing it while the successor is a consultation draft would leave the rules it carries with no carrier (MCC-700 v4.0-draft cl. 22.4). Recorded 7 September 2026 under FD-2026-09-07 item A8. Until then this version remains the controlled text, and its provenance_state continues to record what is and is not known about how it came to be in force.
1.0In forceProgramme AdministratorNo adopting instrument in the programme record
Successor draft: MCC-ESS v2.0-draft
MCC-HCA
Host Country Authorisation Procedure
No approval instrument in the programme record. FD-2026-09-03 item D5 reclassifies this version. Executed on adoption of its successor, not before: withdrawing it while the successor is a consultation draft would leave the rules it carries with no carrier (MCC-700 v4.0-draft cl. 22.4). Recorded 7 September 2026 under FD-2026-09-07 item A8. Until then this version remains the controlled text, and its provenance_state continues to record what is and is not known about how it came to be in force.
1.0In forceProgramme AdministratorNo adopting instrument in the programme record
Successor draft: MCC-HCA v2.0-draft
MCC-SDCF
Sustainable Development Contribution Framework
Published as the current text. Conformity review CR-2026-001 of 3 September 2026 finds it NON-CONFORMING against the rewritten suite, with five blocking findings: the family taxonomy contradicts the adopted one and allocates three methodologies (M007, M009, M010) that have never existed; every methodology-specific requirement is written against instruments FD-2026-09-03 D6 reclassifies as CONCEPT; it asserts an issuance prerequisite MCC-100 cl. 0162 does not contain and the platform does not enforce; the SD Gold criterion is defined two incompatible ways and cannot be computed deterministically; and it makes price and market-value claims about the programme's own credits. A successor, MCC-SDCF v2.0-draft, was drafted on 3 September 2026 on the eight points of that review and is loaded for consultation with the rest of the suite. Pending Board disposal, no sustainable-development label is awarded and no SD claim is made. A review is a finding, not a decision: the status of this instrument is for the Governing Board. No project is prejudiced — no SD assessment has ever been performed and no label has ever been awarded. FD-2026-09-03 item D5 reclassifies this version. Executed on adoption of its successor, not before: withdrawing it while the successor is a consultation draft would leave the rules it carries with no carrier (MCC-700 v4.0-draft cl. 22.4). Recorded 7 September 2026 under FD-2026-09-07 item A8. Until then this version remains the controlled text, and its provenance_state continues to record what is and is not known about how it came to be in force.
1.0In forceProgramme AdministratorNo adopting instrument in the programme record
Successor draft: MCC-SDCF v2.0-draft
MCC-810
Record Retention Schedule
Code proposed in FDP-2026-001 Q22; not yet confirmed in this register by decision.
1.0-draftDraftProgramme AdministratorNo adopting instrument in the programme record
MCC-820
Information Security Standard
Code proposed in FDP-2026-001 Q22; not yet confirmed in this register by decision.
1.0-draftDraftProgramme AdministratorNo adopting instrument in the programme record
MCC-FEES
Fee Schedule
Required by MCC-800 art. 99 and MCC-400 art. 84, which cite "the MCC Fee Schedule". Drafted 4 September 2026 and not opened for consultation. It sets no fee: two positions are decided, the rest is reserved to the Board or has never been priced by anyone. Code proposed, not yet confirmed by decision.
1.0-draftDraftProgramme AdministratorNo adopting instrument in the programme record
MCC-PRIV
Privacy Policy
Required by MCC-800 art. 90, which has directed personal data to be processed "in accordance with the MCC Privacy Policy" since 1 April 2026. None was ever adopted. What is served at /privacy is an interim notice, corrected on 4 September 2026 and in no register. Code proposed, not yet confirmed by decision.
1.0-draftDraftProgramme AdministratorNo adopting instrument in the programme record
MCC-DRBC
Disaster Recovery and Business Continuity Plan
Required by MCC-800 art. 91, which requires annual failover testing of a plan that has never existed. The recovery objectives published at art. 21 (RPO 1 hour, RTO 4 hours) are not met: the deployed system has no daily backup, no point-in-time recovery and no export. Code proposed, not yet confirmed by decision.
1.0-draftDraftProgramme AdministratorNo adopting instrument in the programme record
MCC-FORMS
Operational Forms Suite (MCC-FORM-001 to 013)
The ten forms the MCC Programme Bible names as the authoritative reference and none of which had ever been written. Drafted 3 September 2026. The Bible skips 009, 011 and 012 without explanation; the suite records the gap rather than inventing three forms. Code proposed, not yet confirmed by decision.
1.0-draftDraftProgramme AdministratorNo adopting instrument in the programme record
MCC-REST
Restatement and Correction Policy
Required by the Transparency and Public Disclosure Policy v1.1 art. 6, headed "Corrections and Restatements", adopted and in force since FD-2026-08-24, which points to a corrections process that was never written. Drafted 4 September 2026 and not opened for consultation. It classifies a published error and fixes the remedy — R0 silent fix, R1 correction note, R2 erratum, R3 amendment, R4 withdrawal — by what a reader who relied on the wrong text would have done differently, and hands over to the Rule Change Procedure where the remedy becomes an amendment. It creates no power over the ledger: registry corrections run a separate track on the immutability rules already in force (MCC-800 art. 65, art. 48, arts. 51–52). Code proposed, not yet confirmed by decision.
1.0-draftDraftProgramme AdministratorNo adopting instrument in the programme record
MCC-IRC
Instrument Review Cycle Policy
Drafted 4 September 2026 and not opened for consultation. No instrument requires it: it is a proposal, not the discharge of a promise, and the draft says so in its first paragraph. Thirty-five review provisions are in force across fifteen instruments on five different periods, and no review has ever been performed under any of them — the four reviews done this fortnight were done under none of their clauses, on none of their schedules, by none of the bodies they name. This register has no column capable of holding a review date. MCC-100 and MCC-700 contain no self-review clause in any version. Code proposed, not yet confirmed by decision.
1.0-draftDraftProgramme AdministratorNo adopting instrument in the programme record

The instruments themselves, with their SHA-256 hashes, are at the document register. The decisions that made them are in the decision book. What the programme has and has not evidenced is at the evidence register.