MCC-100 Annex — Definitions Register, Amendment 1 (v2.0-draft)

Document control

Field	Value
Document code	MCC-100 Annex — Definitions Register (Amendment 1)
Title	Definitions Register — Amendment 1: governance bodies, instrument names and lifecycle terms
Version	2.0-draft (amending v1.0)
Status	DRAFT — FOR CONSULTATION
Date of this draft	4 September 2026
Tier	As the annex it amends: annexed to MCC-100 (Tier 3). (Consultation question 1.)
Effective date	None. This amendment is not in force. The annex it amends is in force and is unaffected until the Board decides.
Document owner	Programme Administrator (transitional, until a Secretariat is staffed — FD-2026-10-01 Schedule 1, C3)
Approved by	Not approved. Prepared for public consultation.
Decision basis	Audit findings SYS-01 (unit and product dictionary), SYS-03 (body names and divergent definitions) and SYS-15 (multiple-statement defect); MIR-2026-001 rev 2 §2, §3.8 and §7; FD-2026-08-24 item D12 (recorded in the decision register as attested by the founder, with no executed copy filed), which adopted the annex this amendment extends.
Amends	MCC-100 Annex — Definitions Register v1.0, adopted by FD-2026-08-24 item D12 (closing rulebook-audit finding K12) and served in the public document manifest since 31 August 2026. Nothing in v1.0 is repealed by this amendment; Parts A–F below are added to it.
Language convention	British English; RFC-style normative verbs; one requirement per numbered clause. The annex's v1.0 text is Norwegian and stays as adopted; a consolidated bilingual text follows adoption.
Classification	Public — consultation draft
Consultation period	30 days (FD-2026-10-01 Schedule 1, C4), from the opening recorded on the consultation register (FD-2026-09-04 item 2; FD-2026-10-01 item 5)

NOTE (non-normative). The Definitions Register exists. It was adopted on 24 August 2026 as an annex to MCC-100 by FD-2026-08-24 item D12, it states that it is the programme's single definition source and prevails over a conflicting programme document, and it has been published in the served corpus since 31 August. It settles units, taxonomy, quantification, registry terms, actors and claims discipline.

It does not register the names of governance bodies or of instruments, which is what audit findings SYS-03 and SYS-15 concern. That is what this amendment adds.

The first draft of this text asserted that the Register "has never existed". That was wrong, and the reason it was wrong is itself a finding: the review corpus holds the standards but not MCC-100's annexes, and document_register — the programme's own published register of instruments — did not carry the annex either until 4 September 2026. Two independent reviews reached the same false conclusion from the same incomplete shelf (MIR-2026-001 rev 2 §0 C1 and §7).

Nothing in this Register asserts that any body, instrument or unit exists; where a registered term names something that has never been constituted or issued, the entry says so, because a definitions register that quietly implies existence is worse than none.

Consultation questions

Each point below is open for comment. A proposal is the administration's proposal, put to consultation under founder direction FD-2026-10-01; it is not a rule in force. The suite is to be adopted as one instrument once its longest consultation period has closed (FD-2026-10-01 Schedule 1, C4). Because it includes the Constitution, whose amendment is within the competence of the constituted Governing Board (FD-2026-08-24 item D11, recorded in the decision register as attested by the founder, with no executed copy filed), each point below is decided by the Governing Board on adoption of the suite; a clause of this text that provides another route for adopting it alone is itself open to comment.

1. Document control, Tier — where the Register sits. Proposed: the Register remains annexed to MCC-100 (Tier 3), as the annex it amends. The alternative is to re-enact it as a free-standing Tier 2 instrument, on the ground that a register which can void a definition in MCC-100 should not sit inside MCC-100. Basis: the open decision recorded in this draft (Annex — Summary of open decisions, item 7); FDP-2026-001 Part 3; FD-2026-10-01 item 4. Decided by: the Governing Board on adoption of the suite. Comments are invited on whether the Register should remain an annex or become a free-standing Tier 2 instrument.

2. Entry 3.1 — "MCC". Proposed: "MCC" means Marine Conservation Credits, the programme. The variants "Methodological Carbon Credits" (Buffer Pool Management Policy v1.0 cl. 0001) and "Mitigation Credit Company" (Host Country Authorisation Procedure v1.0 cl. 0001) each appear once and are almost certainly drafting accidents. Because "Mitigation Credit Company" describes a corporate entity, the entry is decided together with the Legal Entity's name; no name is proposed, as the Legal Entity has not yet been incorporated (founder, 1 October 2026; FD-2026-10-01 item 3). Basis: the recommendation in entry 3.1; FD-2026-10-01 Schedule 1 (C1); FDP-2026-001 Part 3. Decided by: the Governing Board on adoption of the suite; the Legal Entity's name and jurisdiction are reserved to it (FD-2026-09-04 item 6). Comments are invited on the canonical expansion of "MCC".

3. Entries 4.1 and 4.3 — the expansion of "MCC-CC" and the name of MCC-MCU. Proposed: "MCC-CC" expands to Carbon Credit, the expansion used by the flagship standard, the methodology framework and the family guidance; "Conservation Credits" collides with MCC-MCU, and "Carbon Capture & Storage Credits" would mislead a buyer. MCC-MCU remains registered as Marine Conservation Unit in the Register in force. Its rename to MCC-MOU (Marine Outcome Unit) was decided by FD-2026-09-03 item D1 (recorded in the decision register as attested by the founder, with no executed copy filed) and is carried by MCC-001 v3.0-draft cl. 6.5 and MCC-100 v3.0-draft cl. 4.8; the Register records the rename on adoption of this amendment, and the entries ask that these points be settled in one decision. No MCC-MCU unit has ever been issued (Evidence Register ER-2026-001 §A3), and this consultation re-codes no project registered under MCC-M008 (FD-2026-10-01 Schedule 1, Q10). Basis: the open decisions recorded in entries 4.1 and 4.3; FDP-2026-001 Part 3; FD-2026-10-01 item 4. Decided by: the Governing Board on adoption of the suite. Comments are invited on the expansion of "MCC-CC" and on the rename of MCC-MCU to MCC-MOU.

4. Entry 5.2 — Standards Committee. Proposed: the canonical term Standards Committee, as the entry registers it. No proposal is made on whether the Standards Committee of MCC-700 v4.0 is the Methodology Review Committee of MCC-200 and MCC-001 under a new name or a different body, because the entry leaves that to the Board without a recommendation: if it is the same body, one term is registered and the others are void; if it is a different body, one of the two assignments of methodology approval must go. Neither body is constituted. Basis: the open decision recorded in entry 5.2; FDP-2026-001 Part 3. Decided by: the Governing Board on adoption of the suite; constituting the Standards Committee is reserved to it (FD-2026-09-04 item 6). Comments are invited on whether the two names denote one body.

5. Entry 5.3 — Registry Oversight Committee. Proposed: the canonical term Registry Oversight Committee, as the entry registers it. No proposal is made on whether it is the same body as the "Registry Oversight Authority" named in MCC-700 and the Launch Pack, because the entry makes no recommendation on it. The body is not constituted. Basis: the open decision recorded in entry 5.3 (Annex — Summary of open decisions, item 4); FDP-2026-001 Part 3. Decided by: the Governing Board on adoption of the suite; no body is constituted by this consultation (FD-2026-10-01 item 6). Comments are invited on whether the two names denote one body.

6. Clause 5.4.5 — the Technical Committee, the MCC AI Governance Committee and the Independent Review Panel. Proposed: no proposal is made — the clause sets out three readings without recommending one, and no instrument in the record constitutes or defines any of the three bodies: each may be (a) the Standards Committee under another name, (b) a distinct body that MCC-700 omitted, or (c) drafting residue from an earlier governance model. Until this is answered, every escalation MCC-850 provides for terminates nowhere. Basis: the open decision recorded in clause 5.4.5 (Annex — Summary of open decisions, item 5); FDP-2026-001 Part 3. Decided by: the Governing Board on adoption of the suite; no body is constituted by this consultation (FD-2026-10-01 item 6). Comments are invited on which reading is right for each of the three bodies.

---

1. Purpose, scope and application

1.1 This Register is the single canonical source of defined terms for the MCC Programme. No other Programme document SHALL define a registered term, and a definition of a registered term appearing in a document of a lower tier is void to the extent of the divergence once this Register is in force. That rule is v1.0's, not this amendment's; this amendment extends the set of registered terms to governance bodies (Part C), instrument names (Part D) and lifecycle terms (Part F), which v1.0 does not cover.

1.1a Where a term is registered in v1.0, v1.0 governs its meaning and this amendment adds only the variants found in the corpus and, where the variants disclose a substantive question, the OPEN DECISION marking. This amendment does not restate, narrow or reopen a definition v1.0 has settled.

1.2 A conflict between this Register and MCC-001 is resolved in favour of MCC-001, and this Register is read down to conform; the document owner SHALL record the conflict and propose an amendment within 30 days.

1.3 Every instrument SHALL, on its next revision, delete its local definitions of registered terms and cite this Register instead. Definitions of terms not registered here MAY remain local, and SHALL be proposed for registration when they are used in more than one instrument.

1.4 This Register does not create, constitute or authorise anything. Registering the term "Standards Committee" does not constitute a Standards Committee.

1.5 Reserved matters. Where a term's canonical form depends on a decision reserved to the Governing Board, this Register records the divergence, states the recommendation, and marks the entry OPEN DECISION. Such entries take effect only on the Board's decision, and until then every listed variant remains in use — the Register does not resolve them by publication.

---

2. How to read an entry

Each entry gives: the canonical term; the definition; the variants found in the in-force corpus with the instruments that use them; and the status of the entry.

Status	Meaning
SETTLED	The canonical form follows from an instrument in force or a decision already taken; the variants are drafting errors and are void on entry into force.
OPEN DECISION	The variants reflect a substantive disagreement the Board must resolve.
NOT CONSTITUTED	The term is registered, but the thing it names does not exist.
NEVER ISSUED	The unit type is registered, but no unit of it has ever existed.

---

3. Part A — Programme identity

3.1 MCC

Canonical: MCC means Marine Conservation Credits, the programme. OPEN DECISION (Consultation question 2.)

Variants in force:

Expansion	Where
Marine Conservation Credits	MCC Programme Bible v2.0; MCC Foundational Decisions v1.0; and the great majority of the corpus
Methodological Carbon Credits	Buffer Pool Management Policy v1.0 cl. 0001
Mitigation Credit Company	Host Country Authorisation Procedure v1.0 cl. 0001

Recommendation: Marine Conservation Credits. The other two appear once each, in the opening clause of a Tier 5 policy, and are almost certainly drafting accidents rather than intentions — but they are in the opening clause, which is where a reader looks first, and one of them ("Mitigation Credit Company") describes a corporate entity rather than a programme, which is a category error the Register should not resolve silently.

Marked OPEN DECISION rather than SETTLED because "Mitigation Credit Company" may reflect an earlier intention about the legal entity, and the entity's name and jurisdiction are reserved to the Governing Board (FD-2026-09-04 item 6) and put to consultation as a question (FD-2026-10-01 item 3). The two should be decided together. (Consultation question 2.)

3.2 The Programme; the Legal Entity

3.2.1 The Programme means the MCC crediting programme constituted by MCC-001. SETTLED

3.2.2 The Legal Entity means the body corporate that operates the Programme. No separate legal entity has yet been incorporated for the Programme (FD-2026-10-01 item 3). NOT CONSTITUTED

The administration proposes a Norwegian aksjeselskap (AS); the entity's name and jurisdiction are reserved to the Governing Board (FD-2026-10-01 item 3 and Schedule 1, C1; FD-2026-09-04 item 6). The name "Marine Conservation Credits Limited" at MCC-700 v3.1 cl. 3.1 has no corporate particulars anywhere in the record and is not an AS. Until incorporation, every instrument SHALL state the pre-incorporation position rather than name an entity that does not exist.

---

4. Part B — The unit dictionary (SYS-01)

This Part is the direct answer to audit finding SYS-01. The corpus carries three expansions of MCC-CC and two of MCC-HYB, counting singular and plural as one form.

What each unit type means is already settled by v1.0 — MCC-CC is a removal unit (1 tCO₂e net uptake, F01 methodologies, 100-year permanence horizon), MCC-HYB a hybrid unit under F02/F05 with a 30-year horizon, MCC-MCU the contribution-basis unit carrying no climate claim. This Part does not touch those definitions. It registers what the code letters expand to in prose, which v1.0 does not state and on which the corpus disagrees with itself.

4.1 MCC-CC

Canonical: OPEN DECISION — Carbon Credit is recommended below. (Consultation question 3.)

Variants in force:

Expansion	Where
Carbon Credit / Carbon Credits	MCC-100 v2.1; MCC-200 v2.0; Claims Policy v1.0; F01 Blue Carbon Guidance v1.0; External Institutional Launch Pack v1.0
Conservation Credits	MCC-800 Registry Operations Standard v1.0
Carbon Capture & Storage Credits	Buffer Pool Management Policy v1.0

Recommendation: Carbon Credit, being the expansion used by the flagship standard, the methodology framework and the family guidance. "Conservation Credits" collides with MCC-MCU, which is the conservation unit; "Carbon Capture & Storage Credits" imports a term of art from geological CCS that does not describe blue carbon sequestration and would be actively misleading to a buyer.

Definition: unchanged — the meaning of MCC-CC is that given by v1.0 (a removal unit of one tonne CO₂e net uptake, issued under F01 methodologies with a 100-year permanence horizon and subsequent monitoring period, Option C). What is registered here is only the expansion of the code letters. Note that "sequestered or avoided" would not be a drafting variant but a change of substance: v1.0 makes MCC-CC a removal unit, and avoided emissions are not the unit basis.

OPEN DECISION — because the choice interacts with the MCC-MCU rename at 4.3, and the three should be settled in one decision. (Consultation question 3.)

4.2 MCC-HYB

Canonical: MCC-HYB means a hybrid unit carrying both a quantified carbon component and a quantified ecosystem-outcome component. SETTLED

Variants: "Hybrid Credit" (MCC-100; MCC-800, in the plural) and "Hybrid Ecosystem-Carbon Credit" (MCC-200; External Institutional Launch Pack). These are the same definition under two labels; MCC-200's is the fuller and is adopted. Singular form throughout, as the unit is counted.

4.3 MCC-MCU

Canonical: MCC-MCU means Marine Conservation Unit — a unit representing a quantified marine conservation outcome without a carbon claim. OPEN DECISION NEVER ISSUED (Consultation question 3.)

No MCC-MCU unit has ever been issued. The live registry holds no units of any type; the demo archive holds 28,769 units, all carrying the MCC-DEMO- prefix. The rename of MCC-MCU to MCC-MOU (Marine Outcome Unit), decided by FD-2026-09-03 item D1, is therefore a rename over zero rows — a pure documentation change with no registry migration, no reissuance and no holder to notify.

It is nonetheless held for the Board's decision. The register holds two project submissions, both recorded under MCC-M008, and no project registered under MCC-M008 is re-coded by this consultation (FD-2026-10-01 Schedule 1, Q10). Neither submission has passed an issuance gate and neither holds units. The Register records the term as MCC-MCU and will be amended on the Board's decision.

4.4 Terms that are not unit types

4.4.1 Credit, unit and outcome SHALL NOT be used interchangeably. A unit is the registry object; a credit is a unit of a carbon-bearing type (MCC-CC or the carbon component of MCC-HYB); an outcome is the underlying environmental result, which is not itself tradeable.

4.4.2 The corpus uses "credit" for all three throughout. This is the single most common terminological defect in the suite and is the reason a reader cannot tell, from MCC-800 alone, whether an MCC-MCU is a carbon credit. It is not.

---

5. Part C — Governance bodies (SYS-03)

The apex body carries four distinct names in this corpus. The body that approves methodologies carries four. A further body — the "Technical Committee" — is escalated to in seven instruments and defined in none.

Every count in this Part was produced by extraction over the 34 in-force texts of the review corpus on 4 September 2026 and is reproducible from them. Counts are of instruments, not occurrences.

5.1 Governing Board

Canonical: Governing Board. SETTLED

Variant	Instruments
Governing Board	14
MCC Board	13
Governance Board	9
Board of Directors	2 (MCC-001; MCC-850)

Governing Board is the term used by GB-2026-001, the instrument that actually constituted the body, and it is therefore the only one with a constitutive act behind it. "Board of Directors" is reserved: it means the board of the Legal Entity once incorporated, which is a different body from the Governing Board and must not be conflated. Where an instrument says "Board of Directors" and means the Governing Board, that is a drafting error and is void on entry into force.

5.2 Standards Committee

Canonical: Standards Committee. NOT CONSTITUTED OPEN DECISION (Consultation question 4.)

Variant	Instruments
Standards Committee	5
Methodology Review Committee	2 (MCC-001; MCC-200)
Methodology Committee	1
"the approval committee" (undefined)	MCC-200 cl. 0045

This is not merely a naming defect. MCC-200 cl. 0039 and cl. 0109 assign methodology approval to the "MCC Board or delegated Methodology Review Committee", at a 75% supermajority. The MCC-700 v4.0 draft — not in force — assigns it to a Standards Committee, and MCC-700 v3.1, which the document register records as in force (FD-2026-08-24 item D11), names the Standards Committee fifteen times. Neither body is constituted. Until one is, no methodology can be approved by anybody, at any majority (MCC-001 v2.0 cl. 0082).

OPEN DECISION: the Board must say whether the Standards Committee of MCC-700 v4.0 is the Methodology Review Committee of MCC-200 and MCC-001 under a new name, or a different body. If it is the same body, one term is registered and the others are void. If it is a different body, the corpus assigns the same function to two bodies and one of the assignments must go. (Consultation question 4.)

5.3 The remaining bodies

Canonical term	Variants in the corpus	Status
Registry Oversight Committee	Registry Oversight Authority (MCC-700; Launch Pack)	NOT CONSTITUTED OPEN DECISION (Consultation question 5.)
Registry Operator	—	SETTLED — distinct role: the operator of the registry system, which may be the Programme itself or a contracted party. Not an oversight body. Must not be conflated with the preceding entry.
VVB Oversight Committee	— (MCC-100; Foundational Decisions)	NOT CONSTITUTED
Appeals Panel	— (MCC-850; Programme Bible)	NOT CONSTITUTED — the corpus also names the appeals forum the Review and Appeals Authority, the Appeals Body, the Appeal Officer and the Independent Appeals Panel (document register, MCC-APP entry). MCC-700 states the right of appeal; no instrument constitutes the panel and no operational appeals procedure exists (MIR-2026-001 rev 2 §3.6).
Safeguards Panel	— (MCC-700; Launch Pack)	NOT CONSTITUTED
Independent Review Panel	— (Programme Bible only)	NOT CONSTITUTED — the Bible makes it the technical assessor at project application. No instrument constitutes it and MCC-700 does not list it.
Programme Administrator	—	SETTLED — the executive function; 15 instruments, no variant.
Programme Secretariat	Secretariat	NOT CONSTITUTED — the Delegated Authority Matrix put to consultation proposes it as the first-instance project registration body (MCC-700 v4.0-draft Annex A row 7; FD-2026-10-01 Schedule 1, C2 and Q3).
Technical Committee	—	NOT CONSTITUTED and undefined. See 5.4.
MCC AI Governance Committee	—	NOT CONSTITUTED and undefined. See 5.4.

5.4 Bodies that are used but never defined

5.4.1 Technical Committee. MCC-850 AI Governance Standard v1.1 escalates to a "Technical Committee" repeatedly and materially: it is named as an authorised human reviewer in the definition of "Human Decision" (Art. 2); it reviews amendments for impact assessment (Art. 6); recurring service-level failures are escalated to it (Art. 9); minor model tuning within approved ranges is delegated to it (Art. 10); and it is the escalation point for LOW and VERY_LOW confidence bands in the completeness-score table. The term appears in seven instruments in all: MCC-850 (15 occurrences), the AI Human Oversight Policy (10), the Foundational Decisions, the Legal and Regulatory Positioning paper, the Registry Terms, the Transparency Policy and the VVB Terms (one each).

5.4.2 No instrument in the corpus constitutes a Technical Committee, states its composition, or defines what it is. MCC-700 does not list it among the governance bodies. It is therefore a body to which the AI governance regime delegates model-tuning authority and escalates low-confidence decisions, and which does not exist.

5.4.3 MCC AI Governance Committee. MCC-850 Art. 6 requires a proposed amendment to be "submitted to the MCC AI Governance Committee". The term appears in two instruments — MCC-850 and the AI Human Oversight Policy — and is defined in neither.

5.4.4 Independent Review Panel. The Programme Bible makes it the body that "conducts the technical assessment" at project application, between AI pre-screening and listing. No instrument constitutes it, MCC-700 does not list it, and no other text in the corpus mentions it.

5.4.5 OPEN DECISION: whether the Technical Committee, the MCC AI Governance Committee and the Independent Review Panel are (a) the Standards Committee under other names, (b) distinct bodies that MCC-700 omitted, or (c) drafting residue from an earlier governance model. Until this is answered, every escalation MCC-850 provides for terminates nowhere, and the AI governance regime's human-oversight guarantee is unenforceable against any named body. MCC-850 v2.0 should not enter into force carrying these terms unresolved. (Consultation question 6.)

Of the ten governance bodies named across the corpus, one is constituted: the Governing Board, by GB-2026-001 of 26 August 2026. The Programme Administrator is an executive function rather than a body and is exercised. Every other — Standards Committee, Registry Oversight Committee, VVB Oversight Committee, Appeals Panel, Safeguards Panel, Programme Secretariat, Technical Committee, MCC AI Governance Committee, Independent Review Panel — does not exist, and every instrument that assigns a function to one of them is, today, assigning it to nothing. The MCC-700 v4.0 draft proposes a transitional appointments schedule for this at clause 4.5.5 (FD-2026-10-01 Schedule 1, C5), while its clause 23.2, as it stands, places the functions of a body not yet constituted with the founder; this Register records the position so that no reader mistakes a registered term for a constituted body.

---

6. Part D — Instrument names (SYS-15)

6.1 Ten instruments are referred to by thirty names across the corpus — twenty canonical-plus-variant forms beyond the ten correct ones. The canonical name is the one on the instrument's own cover; every other form listed is void on entry into force.

Canonical instrument	Void variants
Environmental and Social Safeguards Policy	Social Safeguards Standard; Social Safeguards Framework; Do-No-Harm Assessment Framework
Host Country Authorisation Procedure	Host Country Authorisation Framework; Host Country Authorisation Standard
Corresponding Adjustment and Double Counting Prevention Policy	Double Counting Prevention Framework; Double Counting Prevention Standard
MCC-700 Governance and Appeals	Appeals Framework; Appeals Standard; Governance Framework; MCC Governance Framework
MCC-850 AI Governance Standard	AI Governance Framework
AI Human Oversight Policy	Human Oversight Standard
Buffer Pool Management Policy	Buffer Pool Management Standard
MCC-400 VVB Accreditation and Performance Standard	VVB Accreditation Framework
MCC-800 Registry Operations Standard	Registry Standard
Claims and Use of Credits Policy	Claims Code; Disclosure Code; Claims Framework; Position Claims and Policy Language

6.2 The final row is not a pure naming matter: MCC-600 Claims Code v1.0 is a new instrument in the rewritten suite, not a rename of the Claims and Use of Credits Policy. On MCC-600's entry into force, "Claims Code" ceases to be a void variant and becomes the canonical name of a different instrument. Until then it is void.

6.3 Applicant Guidance means the five family guidance documents (F01–F05) collectively, and is registered as a collective term rather than voided.

---

7. Part E — Methodology families

7.1 The corpus carries four incompatible F01–F05 taxonomies: MCC-100; MCC-200 §2 as against MCC-200 cl. 0031; MCC-400 Art. 32; and the BPM/SDCF alignments.

7.2 The canonical taxonomy is already registered. v1.0 §2 records it as settled by FD-2026-08-24 item D5: F01 Blue Carbon · F02 Restoration (kelp classified here) · F03 Fisheries · F04 Pollution Prevention · F05 MPA Management. Every divergent taxonomy in the corpus is void against it, and this amendment adds nothing to that entry.

7.3 What remains open is not which taxonomy is canonical but the alignment of the instrument texts to it, which is substantive drafting reserved to MCC-200 v3.0 and to FD-2026-09-03 item D2. Until those texts are aligned, an instrument citing a family SHALL cite v1.0 §2 rather than its own local list.

---

8. Part F — Lifecycle terms

8.1 The following are registered with the meanings given, which are those of MCC-100 and MCC-800 read together. No variant is recorded because the corpus is consistent on these; they are registered to keep them so. Retirement and transfer are already registered in v1.0 §4 and are restated here unchanged, for the sake of a single lifecycle sequence; the remaining seven are new.

Term	Meaning
Listing	Publication of a project on the register before validation. Confers no entitlement.
Registration	Acceptance of a project into the Programme following a positive validation opinion.
Validation	Independent assessment, before crediting, that a project conforms to the applicable methodology.
Verification	Independent assessment, after a monitoring period, of the outcomes actually achieved.
Issuance	Creation of units in the registry. Requires a POSITIVE verification opinion, recorded as a typed value.
Transfer	Change of the holder of a unit.
Retirement	Permanent removal of a unit from circulation against a stated claim. Irreversible.
Cancellation	Permanent removal of a unit without a claim, including for error correction. Irreversible.
Reversal	Loss of a previously credited outcome, triggering buffer compensation.

8.2 Retirement and cancellation are not synonyms and SHALL NOT be used interchangeably. The distinction is the claim: a retirement supports one, a cancellation supports none.

---

9. Maintenance

9.1 A term is added to, amended in, or removed from this Register only by the procedure for a Tier 3 instrument, and every change is published with its reason.

9.2 Where a new instrument introduces a term used in more than one instrument, the drafter SHALL propose its registration in the same consultation, and the Register is amended on the same decision.

9.3 The document owner SHALL review this Register on the entry into force of each of MCC-001, MCC-100, MCC-200, MCC-700 and MCC-800, and within 30 days of any Board decision marked OPEN DECISION above.

9.4 Every entry marked NOT CONSTITUTED or NEVER ISSUED SHALL be reviewed whenever the underlying thing comes into existence, and the marking removed by amendment rather than silently.

---

Annex — Summary of open decisions

#	Entry	What the Board must decide
1	3.1 MCC	Whether "MCC" expands to Marine Conservation Credits; taken together with the Legal Entity's name (reserved to the Board, FD-2026-09-04 item 6). (Consultation question 2.)
2	4.1 / 4.3	The canonical expansion of MCC-CC, and the Register's recording of the rename of MCC-MCU to MCC-MOU decided by FD-2026-09-03 item D1 — one decision, three terms. No project registered under MCC-M008 is re-coded by this consultation (FD-2026-10-01 Schedule 1, Q10). (Consultation question 3.)
3	5.2	Whether the Standards Committee and the Methodology Review Committee are the same body. (Consultation question 4.)
4	5.3	Whether the Registry Oversight Committee and the Registry Oversight Authority are the same body. (Consultation question 5.)
5	5.4	What the "Technical Committee", the "MCC AI Governance Committee" and the "Independent Review Panel" are. MCC-850 delegates model-tuning authority to the first and escalates low-confidence decisions to it; none of the three is constituted or defined anywhere. Until this is answered every escalation the AI governance regime provides for terminates nowhere. (Consultation question 6.)
6	7.3	Deferred to MCC-200 v3.0: aligning the instrument texts to the family taxonomy v1.0 §2 already registers. Not a choice between taxonomies — that choice was made at FD-2026-08-24 item D5. Not put to this consultation.
7	Document control	Whether the Register stays an annex to MCC-100 or is re-enacted as a free-standing Tier 2 instrument. (Consultation question 1.)

Seven decisions. Registering the answers retires twenty divergent names, closes the concrete part of SYS-01, SYS-03 and SYS-15, and gives every later instrument one place to cite.

---

Prepared 3 September 2026, revised 4 September 2026 for public consultation as Amendment 1 to the MCC-100 Annex — Definitions Register v1.0 (adopted FD-2026-08-24 item D12). Evidence: extraction over the 34 in-force texts of the review corpus and the served document manifest, 4 September 2026; MIR-2026-001 rev 2 §2, §3.8 and §7; ACR-2026-001 §2. The first draft treated the Register as non-existent; that error and its cause are recorded in the note above and at MIR-2026-001 rev 2 §0 C1. No decision in this draft has been taken.