2026 (Jan 2026 - Dec 2026) · GRI-NG-2026
Reporting cycle detail
Edit
409 CYCLE_IMMUTABLE · identity fields are editable only in draft. After activation the escape hatch is archive plus a new cycle.
Change lock
Archive
active provisional
Annotationtabs are Overview and Events on every cycle detail · this page draws the Usage card that now sits inside Overview (page 8 of this set)
Annotation · not proposed UIPM ruling 2026-08-23: the Usage tab is folded into Overview for I1; two counts do not earn a tab. A dedicated tab returns when later specs add usage classes worth listing (computed figures in spec iii, report provenance in spec vi). This page now draws the folded card up close.
Close-up · the Usage card inside the Overview tab · annotation · not proposed UI
The white card below is the exact rendering added to the Overview tab (page 8 of this set). The amber frame is scaffolding.
The folded Usage card · as rendered in Overview
Usage
Rows stamped with this cycle's id
Stamped assignments · esgmasterdatas128counts of rows stamped with this cycle's id; stamps are written once at write time
Stamped entries · dataentries946nonzero usage means archiving asks for explicit confirmation, 409 CYCLE_IN_USE otherwise
Two definition rows, value next to its label, one condensed muted line each, per the density ruling. The card replaces the former Usage tab's two stat tiles and two helper cards.
First condensed line, expanded · what a count means
Each count is the number of rows carrying this cycle's reportingCycleId. Stamps are written once, at write time, by the assignment resolver and the entry resolver (single-write stamping). For a backfilled cycle the counts are attribution metadata in I1: legacy resolution is unchanged until each surface's cutover, so a count does not mean any live surface reads through the cycle yet.
On the backfilled detail (page 11 of this set) the card carries the attribution-metadata caveat as an extra muted line.
Second condensed line, expanded · archive interaction
Nonzero usage means archiving requires explicit confirmation (confirmUsage: true), otherwise the server refuses with 409 CYCLE_IN_USE. Archiving never orphans rows: stamped rows keep pointing at the archived cycle, and an archived cycle is never a resolution candidate for new rows.
The archive confirmation dialog itself is drawn on the cycle list page's gallery.
Annotation · not proposed UICounts only, by design. The spec defines the two counts and no endpoint lists the individual stamped rows, so a row-level table here would be invention. Its absence is deliberate, not an omission.