How the choice is written · spec ii 6.1, ruling D-ii-8(a)This panel writes through its own endpoint, PUT /v1/reporting-cycles/:id/early-adoption, admin role, draft cycles only, executed inside the cycle critical section. It is deliberately not part of ordinary cycle editing: spec i's generic edit route has a closed field whitelist that this spec does not reopen, so early adoption cannot appear as one more field on the edit form and cannot be changed by accident while someone is fixing a typo. The PM's recorded reasoning on 2026-08-24: early adoption is a deliberate business decision, not an ordinary field edit, so it deserves explicit permissions, validation, and audit history. That is why this is a two-step panel with a named confirmation rather than a dropdown.

What the server accepts and refuses · spec ii 3.6An override may select a newer edition before its window opens only if that edition is published. Unpublished, withdrawn, and unknown targets are refused with VERSION_NOT_ADOPTABLE, which is the constant behind the greyed row above; the screen states the reason in words and shows the constant only in small muted text. Two choices naming the same standard are refused with OVERRIDE_INVALID. Choices are canonicalized before they are stored, so the order they were made in cannot produce two different edition sets from the same decisions. When an override pulls in an edition that replaces its predecessor only partly, the predecessor stays with its replaced disclosures excluded, which is exactly what the effect block draws.

The from and to strip · the PM's ruling R2-5The two boxes with the arrow between them answer the PM's request to show that adopting an edition moves the report from something to something, not just adds a choice. The from side is real, not decorative: for the selected GRI 102 2027 edition the from-edition is the GRI 305 2016 edition, which is what 30 Nov 2026 resolves emissions to today, and it is read from the same selection function that draws the preview on page 2 of this wireframe set. The qualifier under the strip is there because this particular move is a PARTIAL replacement: the from-edition survives in the edition set for 305-6 and 305-7, so a strip that read as a clean swap would be a lie. The disabled GRI 103 row carries the same relation in one clause, where the move would be complete and the from-edition would leave. When the strip is NOT drawn: a standard that joins a report purely by date has no from-edition at all, GRI 101 entering on 1 Jan 2026 being the case in this build, and nothing would be gained by drawing an empty left box with an arrow pointing out of it. Early adoption is never offered for that case in the first place, because there is no earlier edition to move off.

Where the exclusion list comes from · spec ii 3.3 and 3.4aThe five excluded codes are not typed by anyone; they come from the transition calendar's partial map for standard 305 moving to 102, which records 305-1 to 305-5 as replaced and 305-6 and 305-7 as carrying on. The same map drives the Excluded column on page 2 of this wireframe set. When a newer edition replaces a standard completely, as GRI 103 does for GRI 302, there is no partial map and the older edition leaves the edition set entirely, so the effect block for that case would read "the GRI 302 2016 edition leaves your edition set" with no exclusion list. Only the partial case is drawn here, because it is the case that surprises people.

Forward content, drawn on purpose · spec ii scope and 3.4aThe eligible row above needs the GRI 102 2027 edition to be published in the platform catalog. Authoring that content is an I2 workstream and is out of scope for this build, so in this build the "Available to adopt now" list is normally empty and the empty state in the tile above is what an admin actually meets. The control is still an I1 surface named in the spec's section 8 list, and the data model carries the transition without a schema change, so it is drawn and reviewed now rather than designed later under time pressure. Counts, publication dates, and the 3 Feb 2026 catalog publication of the newer edition are invented.

Availability and vocabulary · proposal, PM can vetoThe panel exists only while the cycle is a draft. On an active cycle it is gone from the screen rather than shown disabled, because the edition set is frozen and there is no version of this decision left to make; the frozen set is shown instead. Two things to confirm. Entry point: drawn as a link under the edition set card on the review step, reachable from the cycle detail as well. Wording: "edition set" and "edition" per the wireframe set index, and "adopt early" for the action itself, which is the phrase sustainability teams already use. The internal form of a stored choice is the string 305=gri-102-2027, which never appears on a screen.