Reporting Cycles wireframes · 06 Wizard Review and activate

New reporting cycle

Follow the steps below to create a reporting cycle for Bluefin Foods Group. Creation produces a draft; activation is a separate action on the final step.

Basics

Framework and period

Scope

Organizations in scope

Methodology lock

GWP, approach, conventions

Review and activate

Verify and activate

Basics

FrameworkGRI-NG-2026

PeriodJan 2029 to Dec 2029month precision · UTC

Start year2029start-year invariant is per company and framework

Label preview2029 (Jan 2029 - Dec 2029) · GRI-NG-2026[draft] until activation

Scope

ModeSpecific organizations

Organizations22 of 45 units in scopeProcessing and Canning (all), Cold Chain Logistics (partial), Corporate Services (all) · ids stored sorted and deduplicated

Company level selectedYes

Methodology lock

GWP familyAR6

Boundary approachoperational-control

NCV / GCV conventionNCV

Rule setghgp-corporate-2004+ghgp-scope2-guidance-2015

Rule set version2015-01server-defaulted from the registry, never client-writable

Factor library vintagenull · pending factor library (spec iii)

Intended publication date2030-05-29

Provisional lock: this lock will be written as provisional because the factor library vintage is pending.

Activation re-verifies every precondition regardless of history. For a GRI cycle that means: a lock is present (provisional only while the factor library is unavailable, otherwise complete), the intended publication date is set, and the framework is the GRI new-generation code.

Back

Cancel Save as draft Activate cycle

Annotation · not proposed UIPM ruling 2026-08-23, applied set-wide: values sit next to their labels (no cross-screen eye travel) and a step should fit a typical desktop viewport without scrolling. Density raised across all label-value surfaces.

State gallery · Review and activate step · annotation · not proposed UI

Activation failures come in two distinct shapes: one 422 with the full codes[] list for all non-409 failures at once, and separate 409s for invariant and concurrency failures.

422 with the full codes[] list · all non-409 failures at once

Activation refused · 422

codes: ["NATIVE_FRAMEWORK_INVALID", "PUBLICATION_DATE_REQUIRED"]

NATIVE_FRAMEWORK_INVALID · framework BFG-Group is not the GRI new-generation code; the native engine is legal only with that code
PUBLICATION_DATE_REQUIRED · no intended publication date set on the cycle

Every non-409 failure is enumerated in one response, so the operator fixes the whole list rather than one error per attempt.

409 invariant refusals raced · CYCLE_OVERLAP and CYCLE_STARTYEAR_TAKEN · plus the retryable CYCLE_BUSY case

409 CYCLE_OVERLAP

While this draft was being reviewed, another GRI-NG-2026 cycle covering Apr 2029 - Mar 2030 was activated; its months overlap this draft's Jan 2029 - Dec 2029 period. Invariant failures return separately from the 422 list.

409 CYCLE_STARTYEAR_TAKEN

While this draft was being reviewed, another draft or active GRI-NG-2026 cycle claimed start year 2029. The start-year invariant is per company and framework and is re-verified at activation; sub-year siblings sharing a start year are unsupported in I1.

409 CYCLE_BUSY

Another create, activate, or identity-changing PATCH holds the per-company-per-framework critical section. Retryable, never blocking.

Retry activation

422 LOCK_INCOMPLETE · native cycle with missing lock fields

Activation refused · 422

codes: ["LOCK_INCOMPLETE"] · this GRI cycle has no usable lock; complete the Methodology lock step, then activate.

Go to Methodology lock