Document hierarchy and precedence register
Every instrument the programme has made, by tier. 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.
12 of 12 instruments in force have no adopting instrument
An instrument in force is normally adopted by a signed decision, and a register cites it. For most of this corpus no such decision is in the programme record: the versions were advanced editorially. 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.
Tier 1 — Charter and Constitution
| Instrument | Version | Status | Owner | Adopted 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). | 2.0 | In force | Governing Board | No adopting instrument in the programme record Successor draft: MCC-001 v3.0-draft |
Tier 2 — Governance
| Instrument | Version | Status | Owner | Adopted by |
|---|---|---|---|---|
| MCC-700 Governance and Appeals No controlled text or adoption record for v2.0 is in the programme record. | 3.1 | In force | Programme Administrator | No adopting instrument in the programme record Successor draft: MCC-700 v4.0-draft |
Tier 3 — Programme rules
| Instrument | Version | Status | Owner | Adopted 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. | 2.2 (consolidated) | In force | Programme Administrator | No adopting instrument in the programme record Successor draft: MCC-100 v3.0-draft |
| MCC-800 Registry Operations Standard No approval instrument for v1.0 and no instrument creating v1.1. | 1.1 | In force | Programme Administrator | No adopting instrument in the programme record Successor draft: MCC-800 v2.0-draft |
| MCC-600 Claims Code Referred to across the corpus as though it existed. It did not. First drafted 3 September 2026. | — | Not yet made | Programme Administrator | No adopting instrument in the programme record Successor draft: MCC-600 v1.0-draft |
Tier 4 — Technical standards
| Instrument | Version | Status | Owner | Adopted by |
|---|---|---|---|---|
| MCC-200 Methodology Framework No signed approval instrument for v2.0. | 2.0 | In force | Programme Administrator | No 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. | 1.1 (consolidated) | In force | Programme Administrator | No adopting instrument in the programme record Successor draft: MCC-400 v2.0-draft |
| 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. | 1.2 (consolidated) | In force | Programme Administrator | No adopting instrument in the programme record Successor draft: MCC-850 v2.0-draft |
Tier 5 — Policies, procedures, templates and guidance
| Instrument | Version | Status | Owner | Adopted by |
|---|---|---|---|---|
| MCC-BPM Buffer Pool Management Policy No signed approval instrument in the programme record. | 1.0 | In force | Programme Administrator | No 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. | 1.0 | In force | Programme Administrator | No adopting instrument in the programme record Successor draft: MCC-CADCP v2.0-draft |
| MCC-ESS Environmental and Social Safeguards Policy No signed approval instrument in the programme record. | 1.0 | In force | Programme Administrator | No 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. | 1.0 | In force | Programme Administrator | No 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. 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. | 1.0 | In force | Programme Administrator | No adopting instrument in the programme record Successor draft: MCC-SDCF v2.0 — rewrite recommended (CR-2026-001) |
| MCC-810 Record Retention Schedule Code proposed in FDP-2026-001 Q22; not yet confirmed in this register by decision. | 1.0-draft | Draft | Programme Administrator | No 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-draft | Draft | Programme Administrator | No 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.