Public participation

Public consultations

Every project design document goes to public consultation for at least 30 calendar days before the programme decides on it (MCC-100, clause 0054), and every change to the programme’s rules is published for comment for the notice period its tier requires — 90, 60, 30 or 14 days (Charter, clauses 0079–0083). Comments become part of the public record, each receives a written response, and a closing protocol is published when the consultation ends.

Rule changes open for comment

No programme rule, procedure or template is under consultation today.

Projects open for comment

No project consultation is open today. The first project to reach its consultation stage will appear here for its full 30-day period.

Stayed 3

A stayed consultation has stopped accepting comment but has not been decided. Each of these amends an instrument that founder decision FD-2026-09-03 replaces, so the clauses under consultation will not exist in the text that succeeds them; asking for comment the programme could not act on would be worse than stopping. No closing protocol is owed, because no decision has been taken. Each is either resumed against the successor instrument or formally withdrawn, and that is a decision for the Governing Board. The proposal text and its SHA-256 stay published on every one.

RULE CHANGE · Tier 3 — Programme rules (MCC-100 series)STAYED

MCC-800 Registry Operations — Amendment 1: Claims Policy incorporation and MCC-600 designation (v1.1 → v1.2)

MCC-800 Registry Operations Standard v1.1 → v1.2 (Amendment 1), with consequential amendment to MCC-100 v2.2 cl. 0233(a) and editorial corrections to MCC-850 v1.2

Opened 31 August 2026Stayed 3 September 2026 — would have closed 30 September 20260 public comments

RULE CHANGE · Tier 1 — Charter and ConstitutionSTAYED

MCC-001 Charter and Constitution — Amendment 1: governance architecture and host-country rule (v2.0 → v2.1)

MCC-001 Charter and Constitution v2.0 → v2.1 (Amendment 1)

Opened 27 August 2026Stayed 3 September 2026 — would have closed 25 November 20260 public comments

RULE CHANGE · Tier 2 — Governance (MCC-700)STAYED

MCC-700 Governance and Appeals — Amendment 1: alignment with FD-2026-08-24 (v3.1 → v3.2)

MCC-700 Governance and Appeals v3.1 → v3.2 (Amendment 1, A1.1–A1.10)

Opened 27 August 2026Stayed 3 September 2026 — would have closed 26 October 20260 public comments

Withdrawn 2

A withdrawn proposal is gone, and not because it lost on its merits. Each of these was drafted against clauses the revised suite deletes, for instrument codes founder decision FD-2026-09-03 item D1 retires — MCC-HYB abolished with no successor code, MCC-MCU renamed and re-scoped as MCC-MOU; adopting either today would write a retired code into the framework it was meant to correct. No closing protocol is owed, because none was decided. The proposal text and its SHA-256 stay published on every one, and each carries a notice saying what the proposal would have delivered and which instrument must now deliver it — a withdrawal that leaves a gap without naming who fills it is how a programme loses a rule by tidying up.

RULE CHANGE · Tier 3 — Programme rules (MCC-100 series)WITHDRAWN

MCC-100 Programme Standard — Amendment 2: reversal-risk management period for MCC-HYB units (v2.2 → v2.3), with Buffer Pool Management Policy Amendment 1

MCC-100 Programme Standard v2.2 cl. 0183.1 and 0191 → v2.3; Buffer Pool Management Policy v1.0 → v1.1

Opened 27 August 2026Withdrawn 7 September 2026, stayed 3 September 20260 public comments

RULE CHANGE · Tier 4 — Technical standards (MCC-200, methodologies)WITHDRAWN

MCC-200 Methodology Framework — Amendment 1: alignment with the canonical taxonomy and the registry portfolio (v2.0 → v2.1)

MCC-200 Methodology Framework v2.0 → v2.1 (Amendment 1)

Opened 26 August 2026Withdrawn 7 September 2026, stayed 3 September 20260 public comments