Demo helperGRI guidance UX roundPage 3 of 7 · About this page, and the two new hooksInvented data · Bluefin Foods Group (fictional tenant)
GRI guidance UX roundAbout this page, and the two new hooksWhere the control that reopens a page's intro overlay lives (DECISION U-3, placement only), and the two new places that gain a Help entry point.PROPOSAL2026-08-25
Annotation · what U-3 decidesThe About-this-page control reopens the page's intro overlay on demand. Mechanics are already decided (spec 7.2): a reopen NEVER counts against the three auto-showings (the reopen fetch is read-only and counts nothing), and it works even after the user picked "don't show this again". U-3 decides ONLY where the control sits in the page header. Both options are drawn on the same base: a simplified header of the stakeholder groups page (catalog admin set, page 08). Whichever placement is picked applies to every page that carries the control.
Option A · Icon-only circled question button at the right end of the title row · PROPOSAL
Stakeholder groups
About this pageAnnotationtooltip drawn open for this exhibit; it appears on hover and focus
Bluefin Foods Group · the workspace registry, and what each reporting cycle recorded from it
New stakeholder group
Pro: compact, costs no header line, and sits in the same spot at any title length, so the eye learns one place across every page that has the control. Con: it relies on icon recognition; a user who does not read a circled question mark as "explain this page" may never find it, and the tooltip only helps a user who already hovered.
Option B · Quiet text link in the header meta row under the title · PROPOSAL
Stakeholder groups
Bluefin Foods Group · the workspace registry, and what each reporting cycle recorded from itAbout this page
New stakeholder group
Pro: self-describing; the words literally name the action, so nothing has to be learned or hovered, and screen readers announce it plainly. Con: it adds a line's worth of header text on every page that carries the control, and a link sitting inside the meta row competes with the description text around it.
Annotation · decided mechanics, common to both optionsReopening never counts: the three-showing counter moves only when the overlay auto-opens on page entry and that showing is acknowledged after rendering (spec 7.2). The reopened overlay is the same authored record the auto-showing uses, at its current published version. If the overlay record is missing or fails to load, the control does nothing visibly harmful: no error, no blocked page.
Annotation · the two new hooks · drawn at half scaleSpec 13 item 3 adds two Help entry points beyond the three existing overlay pages. Both drawings below use Option A as a stand-in only; the U-3 pick above applies to all pages carrying the control, these two included.
New hook 1 · The cycle-list introduction · drawn at 50 percent scale
Reporting cycles
AnnotationOption A drawn as stand-in; the U-3 pick applies here too
One durable period identity per framework and period. Cycles stamp assignments and entries and carry the methodology lock.
Reporting Boundaries adminNew cycle
Cycles10Quarantine313
The cycle list header (base: cycle admin set, page 01) gains the About-this-page control. The overlay it opens is the cycles-area introduction, an authored record explaining what reporting cycles are (spec 7.3 item 3, seeded from the why-reporting-cycles supplement). This is a fourth surface for the same overlay pattern, not a new pattern: same frame, same counting, same reopen rule.
New hook 2 · The lock-dialog explainer link · drawn at 50 percent scale, one state only
Replace methodology lock
2026 (Jan 2026 - Dec 2026) · GRI-NG-2026 · replacing a provisional lock on an active cycle
What the lock is. The lock controls whether this cycle's methodology and figures are frozen.
none
Open. Entries flow normally.
provisional
Methodology pinned while the report is drafted. Figures stop moving.
complete
Year closed. Numbers frozen; the report stays reproducible.
A change here is allowed and stays reversible through further changes; it is never a one-way street. Every change is recorded with who, when, and what changed on the Events tab, so repeated lock and unlock activity is visible to auditors.
More about the lock
Annotationthe new hook: a quiet link at the foot of the always-rendered block, opening the fuller lock explainer (authored Help content on the methodology-lock fields, spec 7.3 item 2)Annotationthe block above never collapses and never moves: it is functional by fiat (never-hide rule, spec 7.4 collision 1, pinned by ruling R-w-7). The link only ever ADDS depth on request
Form area condensed for this exhibit: the current-lock column, the proposed-lock fields, and the what-happens-if-you-continue block are unchanged from the reviewed drawing. Full dialog: cycle admin set, page 11, state A.
CancelReplace lock
The lock-change dialog (base: cycle admin set, page 11, state A) keeps its plain-language "What the lock is" block exactly as reviewed. The hook adds one quiet "More about the lock" link opening the fuller explainer. The link is drawn as a text link rather than the circled button because it opens a field-level explainer, not a page introduction; if the PM prefers one visual for every Help entry point, the U-3 pick can be applied here as well.