2025 (Apr 2025 - Mar 2026) · BFG-Group [backfilled]
Reporting cycle detail
active none stale source read-only
OverviewEvents
Annotationtabs are Overview and Events per the PM ruling 2026-08-23; the Usage card sits in Overview below · only Overview is drawn for the backfilled sample · the greyed Events pill is a wireframe stub with no page behind it, not a proposal to disable that tabRead-only · server-enforced. This cycle was created by the backfill. Lock, archive, and PATCH requests return 409 CYCLE_BACKFILLED_READONLY. Only the backfill runner mutates backfilled cycles, through re-runs and rollback. The refusal comes from the server, not from a disabled button.
Stale source. A source boundary changed after attribution. The marker is advisory: the authoritative reconciliation is the company backfill re-run, which re-derives from current boundaries, reconciles sourceBoundaryIds, archives now-sourceless backfilled cycles, and clears this marker.
Identity
Cycle identity fields (spec 4.1)
FrameworkBFG-Group
PeriodApr 2025 to Mar 2026month precision · UTC
Rendered period2025 (Apr 2025 - Mar 2026)
Start year2025
Org scopeAll organizationsderived from the collapsed source boundaries
Statusactive
Created bynot setcreatedBy is required only when the source is user
Created2026-08-24 02:05 UTC
Updated2026-08-30 11:22 UTC
Provenance
Where this cycle came from · shown for every backfilled cycle
Sourcebackfill
Source boundaries68a4c3aa1b2c3d4e5f607701 open in boundary admin ↗
68a4c3aa1b2c3d4e5f607702 open in boundary admin ↗every boundary collapsed into this cycle
68a4c3aa1b2c3d4e5f607702 open in boundary admin ↗every boundary collapsed into this cycle
Backfill runrun-2026-08-24-a1
Mapping rule versionv1
Stale sourcetrueset 2026-08-30 by a source-boundary-mutated event
Methodology lock
Lock statenone
All backfilled cycles stay lockState: none for the whole of I1. Lock writes are refused 409 CYCLE_BACKFILLED_READONLY.
Usage
Rows stamped with this cycle's id · drawn up close on page 9 of this set
Stamped assignments · esgmasterdatas1,204counts of rows stamped with this cycle's id; stamps are written once at write time
Stamped entries · dataentries8,769nonzero usage means archiving asks for explicit confirmation, 409 CYCLE_IN_USE otherwise; moot here, since every mutation on a backfilled cycle is already refused 409 CYCLE_BACKFILLED_READONLY
Attribution metadata in I1: legacy resolution is unchanged until each surface's cutover, so these counts do not mean any live surface reads through this cycle yet.
Annotation · not proposed UIUsage shows counts only, by design: no endpoint lists the individual stamped rows. The card sits in Overview per the PM ruling 2026-08-23.
Annotation · not proposed UIThe link above is proposed UI, not a helper: it opens the area-level Quarantine tab pre-filtered by
run-2026-08-24-a1, and is the drawn resolution of the quarantine-placement question (see the set index).Annotation · not proposed UINo Edit, Change lock, Archive, or Delete control appears anywhere on this page, and no copy suggests an operator override path. Nothing here may imply a backfilled cycle is editable.