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 final first-visit intro overlay open over it in state 1. Drawings 2 and 3, in the amber gallery further down: state 2 with the report note open, and the page header with the reopen control. Ordered by the PM in his part 2 review of 2026-08-24; redrawn the same day to the blended design he picked after the three-concept decision round.
Annotation · the decision behind this drawingBlended on the PM's pick of 2026-08-24. The first drawing of this overlay, four paragraphs of prose at about 210 words, was rejected for its presentation in the PM's part 2 review. Three designers then proposed replacements blind against the same bundle, and the PM picked the page-in-miniature concept, the workspace designer's, as the base, with the best pieces of the competing two blended in. From the competing Codex concept: the headline ("Keep today's list. Preserve what each report saw.") and the two stacked connector labels ("Cycle activated", "Snapshot taken"), which replace the miniature's own nine-word arrow label that wrapped badly. The moments line already carried the competing Grok concept's permission-first move ("Most weeks there is nothing to do here"). Everything else on this card is the miniature concept as written. The rejected drawing is preserved as a copy beside the exhibit, and the full round history lives in the decision exhibit.
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 · replica fidelity, and one consequenceThe miniature is replica UI, warn-toned chips included. The two small panels inside the dialog reuse the page's exact panel titles, button styling, and chip colors, so the miniature visibly rhymes with the dimmed panels behind the glass, and the page already looks familiar when the overlay closes. That is why the dialog carries the page's warn-toned "can be refreshed" and "superseded" chips: they are copied page UI, not annotation scaffolding, and the PM decided replica fidelity stays. The cost, recorded in the round: the replica couples this overlay to the page 08 drawing, so a change to that page means redrawing the miniature.
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.
State gallery · drawings 2 and 3 · annotation frame only, the white cards are the proposal
The overlay's second state, and where the introduction lives after it stops appearing.
State 2 · report note open · same dialog, drawn at 55 percent scale
Keep today's list. Preserve what each report saw.
A short welcome for your first visits · the page works the same without it
One list of everyone Bluefin Foods Group listens to, and a dated copy of that list kept for every GRI report.
The page below, in miniature
Workspace registryNew group
Employees and contractorsactive
Contract growersactive
The living list: employees, growers, communities, regulators, customers. Add a group here, or rename and deactivate one from its row menu.
Cycle activated
Snapshot taken
Cycle snapshotsRefresh snapshot
Version 2latestcan be refreshed
Version 1superseded
The record your report cites: who was engaged at the time, kept exactly as recorded even if a group changes later.
Most weeks there is nothing to do here. You would drop in when:
a reporting cycle is being set up
the company starts engaging a group
a group is renamed or retired
An empty registry never blocks a cycle.
How this shows up in the finished report
A GRI report is expected to name who the company engaged and how. Because every cycle keeps its own dated copy, the FY2025 report can truthfully say it engaged Contract farmers, the name that group carried at the time, even though the registry now reads Contract growers. Nothing done here today rewrites what an earlier report recorded.
Do not show this when I visit this page
This introduction stops appearing by itself after your third visit. Bring it back any time from About this page, in the page header.
Got it
The one depth link opens a single soft gray strip holding one authored note of at most 60 words; the footer slides down about 100 px and nothing else in the dialog moves. There is no third state. The note answers the one question the miniature raises but cannot settle in a label: what the bookkeeping buys at report time, told through the Contract farmers rename.
After dismissal · the page header with the reopen control
Stakeholder groups
Bluefin Foods Group · the workspace registry, and what each reporting cycle recorded from it
About this page
The About this page control reopens the same introduction on demand, in state 1, whatever the showing count or the do-not-show choice says, so dismissing the overlay never makes its content unreachable. It is a quiet outline control, present for whoever wants it and invisible to the routine; the same control, with the same wording, sits in the page header of Value Chain and of Frameworks and Access. It is also drawn in the dimmed page behind the overlay above, because the proposed page always carries it. Not drawn, because a static page cannot: the X, the Got it button, the Escape key, and a click on the dimmed veil all count as the same close.