Demo helper GRI Catalog Admin · Admin wireframes (spec ii) Rejected baseline · preserved copy Invented data · Bluefin Foods Group (fictional tenant)
Demo helper · what this supplement drawsDrawing 1, below: the Stakeholder groups page exactly as page 08 of this wireframe set draws it, dimmed, with the first-visit intro overlay open over it. Drawing 2, in the amber gallery further down: the page header with the reopen control. Ordered by the PM in his part 2 review of 2026-08-24, after this round closed.

Stakeholder groups

Bluefin Foods Group · the workspace registry, and what each reporting cycle recorded from it
About this page
Workspace registry
The current list of groups this workspace engages with
New group
GroupCategoryEngagement modeStatus
Employees and contractors
Group-wide, 2,140 people
workforcesurvey
Annual engagement survey
active
Contract growers
Renamed from Contract farmers on 02 Jun 2026
suppliersmeeting
Grower meetings, three regions
active
Retail customers
SG, TH, MY retail accounts
customerssurvey
Consumer panel and service line
active
Food safety regulators
Three jurisdictions
regulatorswritten-submission
Filings and inspection responses
active
Neighboring communities
Johor and Rayong plant catchments
communitiesgrievance-channel
Community liaison meetings
active
Regional wholesalers panel
2024 pilot, no longer convened
customersmeetinginactive
Deactivated 04 Jan 2026
Groups are deactivated, never deleted, so every snapshot and every later consultation record still resolves to the group it was written against. An empty registry is valid: nothing in the reporting flow waits on the stakeholder group registry.
Cycle snapshots · FY2025 GRI report
Jan 2025 to Dec 2025 · active · what this cycle recorded, version by version
Refresh snapshot
Refresh takes a new version. It never edits or replaces an existing one. This cycle is active and its methodology lock is provisional, so the latest version can still be refreshed: pressing Refresh snapshot records the registry as it stands today as version 3, and versions 1 and 2 stay exactly as they were taken.
Version 2 latest can be refreshed View recorded groups
Taken15 Jun 2026, 09:24 UTCrefreshed while the cycle was active
Taken byPriya NairSustainability Admin
Groups recorded5
Version 1 superseded by version 2 View recorded groups
Taken12 May 2026, 06:11 UTCtaken when the cycle was activated
Taken byMei TanSustainability Admin
Groups recorded5
About stakeholder groups
A short introduction, shown on your first visits to this page

This page keeps your workspace's stakeholder groups: the kinds of people Bluefin Foods Group engages and listens to, such as employees, contract growers, neighboring communities, food safety regulators, and retail customers. Sustainability reporting calls them stakeholders, and the workspace registry panel on the left names who they are for this company.

It exists because a GRI report is expected to say who the company engaged and how. You record each group once here, and every reporting cycle takes its own dated copy of the registry at activation, so the finished report always shows who was engaged at the time, even if a group is later renamed or deactivated.

Most weeks there is nothing to do here. A Sustainability Admin typically opens this page while setting up a reporting cycle, or when the company starts or stops engaging a group. An empty registry never blocks a cycle, and reading happens far more often than editing.

To work with it, press New group to add a group with its name, category, and how it is engaged, and rename or deactivate a group from its row menu. In the Cycle snapshots panel on the right, Refresh snapshot records a fresh dated copy when the report should reflect a registry change.

Do not show this when I visit this page This introduction stops appearing by itself after your third visit. You can reopen it any time from About this page in the page header.
Got it
Annotation · where this page comes from, and what it isOne overlay pattern, drawn once. This supplement was ordered by the PM in his part 2 wireframe review of 2026-08-24, after this round closed. It draws the first-entry introduction ONCE, on the Stakeholder groups surface, as the pattern: the same overlay, each with its own authored content, appears on first entry to Value Chain and to Frameworks and Access. One authored content record per page, three records total; nothing about the overlay's frame, mechanics, or dismissal varies between the three. No spec ii section covers this surface, because it postdates the spec; the mechanics stated in these annotations are the proposal that a spec addition has to pin down before any build.
Annotation · content provenanceAuthored guidance, no AI label. The introduction text is authored, versioned, human-reviewed guidance content. It carries no AI-generated label, per the PM's provenance ruling of 2026-08-24: a model may draft guidance text, but a human reviews, edits, and owns what ships, so what the user reads is the product speaking. The overlay therefore has no AI badge, no regenerate control, and no model attribution anywhere.
Annotation · where the state livesPer user, server-side. The showing count and the do-not-show choice persist per user on the server, as a small addition to user settings; never in browser storage. A user who signs in from a second machine, clears a browser, or works at a shared terminal must not be greeted as brand new, and an introduction that resurfaces after every cache clear would train people to ignore guidance. Per user, not per workspace: Mei Tan dismissing the introduction hides nothing from Priya Nair. Counting proposal: a showing is counted each time the overlay opens on page entry, however it is then closed; after the third counted showing it no longer opens by itself.
Annotation · failure postureNever on the critical path. The Stakeholder groups page renders and works identically with the introduction dismissed, exhausted, toggled off, or its content record missing entirely. A missing or failing content record means no overlay and no error, never a blocked page. Nothing in the reporting flow reads or waits on introduction state.
Annotation · copy ownershipThe words above are placeholders. The overlay copy on this page is placeholder authoring, written to show shape, length, and tone: a gentle wave, not a tsunami, with no literal topic headings. The guidance workstream owns the final copy for all three introductions, and that work starts only on the PM's GO.