Intro overlay designs · three candidates beside the rejected baseline
The PM rejected the presentation of the first-entry introduction overlay drawn on page 8b of the GRI Catalog Admin wireframe set (part 2 review, 2026-08-24): four paragraphs of prose, about 210 words, on one surface. Three designers were then briefed blind, each against the same bundle (the rejected page 8b drawing and the page 08 Stakeholder groups drawing it sits on), and each proposed one replacement. This exhibit draws all three at full scale on the Stakeholder groups surface so they can be compared in one place. Nothing on this page was decided when it was drawn; the PM's ruling, recorded in the banner below, followed the same day.
Decided · 2026-08-24The PM picked Concept C, the page in miniature (Workspace designer, Fable), as the base, with two grafts from Candidate A (Codex): the headline and the stacked connector labels. The final blended drawing is live on page 8b; the rejected baseline it replaced is preserved as a copy in this directory. Nothing else in this exhibit changed; the three candidate drawings below stand unaltered as the round record.
Annotation · what is being decided, and what is notPresentation only. The decision on this page is how the first-entry introduction looks and reads. The mechanics were not rejected and are identical in every candidate, per the decided mechanics recorded at the guidance intake of 2026-08-24: the showing state lives per user on the server, never in the browser; the overlay stops opening by itself after the third counted showing; a do-not-show checkbox is offered in the overlay; and the About this page control in the page header reopens the introduction on demand, whatever the count or the checkbox says. Each candidate carries those mechanics in its own footer wording, drawn verbatim below. Whichever candidate wins, page 8b is redrawn to it, and the same pattern is reused on first entry to Value Chain and to Frameworks and Access.
Annotation · how to read the drawingsEach candidate section draws the concept's default state at full scale, at the exact width its designer specified, over a simplified ghost of the page 08 workarea: two dimmed stand-in panels for Workspace registry and Cycle snapshots, kept because two of the three concepts deliberately mirror those panels through the veil. The ghost is a demo helper, not the full page drawing; the real page is page 08 of the wireframe set. The concept's second state is drawn below each stage at reduced scale, in an amber tile. Amber blocks like this one are review scaffolding and never ship; no annotation scaffolding appears inside any drawn candidate dialog. Keyboard and click-on-veil dismissal cannot be drawn in a static page; each section's annotation records them.
Section 0 · rejected baselineThe rejected page 8b overlay, for reference only. Not redrawn here; sketched in miniature below, with a link to the preserved copy. Rejected 2026-08-24 for its presentation, not its mechanics.
Thumbnail sketch · demo-helper stand-in, not a redraw
About stakeholder groups
A short introduction, shown on your first visits to this page
Got it
The gray bars stand for the four paragraphs; only the real title, subtitle, and button are lettered. Open the preserved drawing: rejected baseline, preserved copy. The live page 8b now carries the final blended version.
Annotation · what was rejected, and why it still mattersThe page 8b overlay delivers its orientation as one surface of prose: four paragraphs, about 210 words, covering what the page is, why it exists, when anyone visits, and how to work it, in that order. The PM rejected that presentation in his part 2 review of 2026-08-24 and asked for a gentler first layer, in keeping with his standing "gentle wave, not a tsunami" ruling on guidance tone. Everything else about page 8b stands: its dialog framing, its footer checkbox wording, the third-visit stop, the About this page reopen control, and the server-side per-user state all carry into the three candidates below. All three designers worked from this overlay and the page 08 drawing as their shared bundle, without seeing each other's proposals.
Candidate A · External reviewer A (Codex)The current-list-to-dated-record visual map. State 1 below at full scale, 960 by 704 px as specified, full-window veil at 44 percent black. State 2, the expanded example, follows at half scale.
Workspace registry
Cycle snapshots
Stakeholder groups
Keep today's list. Preserve what each report saw.
This page connects the groups Bluefin Foods Group engages with to the dated record behind each ESG reporting cycle.
Current list
Your workspace now
Keep each stakeholder group's name, category, and engagement mode in one workspace registry.
Contract growerssuppliersmeeting
Cycle activated
Snapshot taken
Dated history
Each cycle keeps its own view
The snapshot preserves what was recorded at the time, even if a group is renamed or deactivated later.
Version 1Recorded 12 May 2026
Come back when something changes
Start or stop engaging a group
Use New group, or choose Rename or Deactivate from its row menu.
Update an active report
Use Refresh snapshot to add a new dated version.
Check what was recorded
Open any version to see the groups and names it captured.
An empty registry is valid. Nothing here blocks a reporting cycle.
See one change across timeContract farmers is renamed, while the older report stays intact
Do not show this when I visit this page
This intro stops opening automatically after your third visit. Reopen it anytime with About this page.
Explore the page
State 2 · expanded example open · 960 by 838 px, drawn at half scale
Stakeholder groups
Keep today's list. Preserve what each report saw.
This page connects the groups Bluefin Foods Group engages with to the dated record behind each ESG reporting cycle.
Current list
Your workspace now
Keep each stakeholder group's name, category, and engagement mode in one workspace registry.
Contract growerssuppliersmeeting
Cycle activated
Snapshot taken
Dated history
Each cycle keeps its own view
The snapshot preserves what was recorded at the time, even if a group is renamed or deactivated later.
Version 1Recorded 12 May 2026
Come back when something changes
Start or stop engaging a group
Use New group, or choose Rename or Deactivate from its row menu.
Update an active report
Use Refresh snapshot to add a new dated version.
Check what was recorded
Open any version to see the groups and names it captured.
An empty registry is valid. Nothing here blocks a reporting cycle.
See one change across timeContract farmers is renamed, while the older report stays intact
One change, two truthful records
12 May: Cycle activated
Version 1 records Contract farmers.
2 Jun: Registry renamed
The current list now shows Contract growers.
15 Jun: Snapshot refreshed
Version 2 records Contract growers. Version 1 stays unchanged.
Do not show this when I visit this page
This intro stops opening automatically after your third visit. Reopen it anytime with About this page.
Explore the page
Selecting the See one change across time row inserts a 134 px pale-gray example panel with a three-step timeline; the footer moves down and nothing else changes. Card grows from 704 to 838 px tall.
Annotation · candidate A, fidelity notesDrawn to the concept's spec: 960 px wide, regions 120 + 202 + 148 + 46 + 100 px, verbatim copy throughout. Dismissal as specified: the close control (accessible label "Close introduction"), the Explore the page button, the Escape key, and a click on the dimmed backdrop all close it; the checkbox preference applies on any close; a manual reopen from About this page never increments the visit count. Details the concept left open, resolved conservatively by the builder: the title is drawn in the product's dialog indigo, the miniature row chips use the product's neutral outline chip shape, and the "file-history icon" is drawn as the set's document icon (the Cycle snapshots panel icon). The concept's stated rationale: the first layer is a spatial relationship, not a reading assignment, and the reassurance line is visible before any detail. It rejected a carousel and a spotlight tour as stronger interruptions than one card.
Candidate B · External reviewer B (Grok)The page-map intro card. State 1 below at full scale, 820 by 488 px as specified. State 2, the controls view, follows at 60 percent scale. Same 488 px height in both states.
Workspace registry
Cycle snapshots
Who this company engages
A live registry on the left, a dated copy per reporting cycle on the right
This page keeps the kinds of people Bluefin Foods Group engages and listens to, so a GRI report can say who was engaged and how.
Left of this page
The live list
Employees, contract growers, neighboring communities, food safety regulators, and retail customers. One row per group: a name, a category, and how they are engaged.
v2v1
Right of this page
A dated copy per cycle
Each reporting cycle takes its own dated copy of the registry at activation. The finished report shows who was engaged then, 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.
The controls, in brief
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.
Show me the page
State 2 · the controls, in brief · same 820 by 488 px, drawn at 60 percent scale
Who this company engages
A live registry on the left, a dated copy per reporting cycle on the right
This page keeps the kinds of people Bluefin Foods Group engages and listens to, so a GRI report can say who was engaged and how.
New group
Adds a group with its name, category, and how it is engaged. Rename or deactivate from the row menu. Groups are deactivated, never deleted, so every snapshot still resolves to the group it was written against.
Refresh snapshot
Records a fresh dated copy when the report should reflect a registry change. It never edits or replaces an existing version. Reading this page happens far more often than pressing it.
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.
Back to the two sides
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.
Show me the page
The depth link swaps only the middle 168 px region: the two tiles give way to two control rows named for the page's real buttons. No height change, no scroll, no step 2 of a tour; the link becomes the way back.
Annotation · candidate B, fidelity notesDrawn to the concept's spec: 820 by 488 px in both states, verbatim copy, amber nowhere on the overlay. Veil note honored here rather than in the ghost: this concept dims the workarea only; the product sidebar and top navbar stay fully visible and undimmed, and the dialog centers in the workarea, not the window. The exhibit's simplified stage omits the sidebar for all three candidates, so that difference is recorded in this annotation. Dismissal as specified: the Show me the page button, the header X, a click on the veil, and the Escape key all close it the same way; the checkbox is independent of the close action; no "visit 2 of 3" counter is drawn, deliberately. Builder notes, flagged: the two verbatim tile bodies run to four and five lines at the specified type sizes where the concept's anatomy allows "two short lines max", and the footer's verbatim help line wraps to two, so the drawn footer stands 90 px against the anatomy's nominal 76. Both are verbatim copy kept over the concept's own pixel estimates, inside the same fixed 488 px card with no internal scroll.
Candidate C · Workspace designer (Fable)chosen as baseThe page in miniature. State 1 below at full scale, 880 px wide as specified; drawn height 527 px against the concept's estimate of about 555. State 2, the report note open, follows at 55 percent scale.
Workspace registry
Cycle snapshots
Stakeholder groups, at a glance
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.
each cycle takes a dated copy when it starts
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 upthe company starts engaging a groupa group is renamed or retiredAn empty registry never blocks a cycle.
How this shows up in the finished report
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
State 2 · report note open · drawn height 626 px against the concept's estimate of about 655, at 55 percent scale
Stakeholder groups, at a glance
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.
each cycle takes a dated copy when it starts
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 upthe company starts engaging a groupa group is renamed or retiredAn 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 moves. There is no third state.
Annotation · candidate C, fidelity notesDrawn to the concept's spec: 880 px wide, verbatim copy, the miniature reusing the page's exact panel titles, button colors, and chip colors. That last requirement is why this candidate, alone, carries the page's real warn-toned chips ("can be refreshed", "superseded") inside the dialog: they are replica UI, copied from the page 08 drawing so the miniature visibly rhymes with the panels behind the glass, not annotation scaffolding. Dismissal as specified: the X, the Got it button, the Escape key, and a click on the veil all count as the same close; the About this page control reopens state 1 regardless of count or checkbox. Builder notes, flagged: the arrow label is drawn verbatim at nine words where the concept's anatomy says eight, and it wraps to five short lines in the 60 px center column where the anatomy asks for two, because two 11 px lines of this label need about 130 px and the concept's own 370 + 60 + 370 split does not leave it; the 370 px replicas were kept exact and the label allowed to wrap. The moments row likewise wraps to two lines, a little over the concept's "about 44 px", because its verbatim strings do not fit one 832 px line. All three are the concept's own copy, kept over its own pixel estimates.
Comparison · even-handedOne card per candidate: its signature idea, its first-three-seconds claim, its first-layer reading load, and its main risk. Drawn from each concept's own stated rationale and rejections. The exhibit recommends none of them.
Candidate A · External reviewer A (Codex)
Signature idea. One spatial map: the current list on the left flows into the dated record on the right, with three practical return moments beneath and one optional worked example behind a disclosure row.
First three seconds, as claimed. The eye lands on the title, follows the left-to-right relationship from list to record, and meets the reassurance that an empty registry is valid before any detail.
First layer. About 95 words of running prose, about 190 counting every label and string, by the builder's count; the concept states no count of its own.
Main risk. The largest card of the three, 960 by 704 px, and the most on-screen strings; the map must be read as a picture for the first layer to stay light.
Candidate B · External reviewer B (Grok)
Signature idea. A card that maps the real two-panel page: two schematic tiles matched to the panels behind the veil, a "most weeks there is nothing to do" band, and the controls kept behind one quiet text link.
First three seconds, as claimed. Title and subtitle split the page in two, the two schematics land before any sentence, and every exit is visible on the first frame.
First layer. About 115 words of running text by the concept's own count (the lead, two tile bodies, and the when band).
Main risk. The schematics are glyphs, gray bars and a v1/v2 stack, not a replica, so the match to the page behind is carried by the eyebrow and title words; and its verbatim tile bodies overrun the anatomy's own two-line allowance.
Candidate C · Workspace designer (Fable)
Signature idea. The page itself at postcard size: two shrunken replicas of the real panels joined by one labeled arrow, so the overlay teaches the exact screen it covers and familiarity transfers when it closes.
First three seconds, as claimed. One bold sentence, two panel names, one arrow label, roughly thirty words; the miniature visibly rhymes with the dimmed page behind.
First layer. About 150 words including captions and chips, by the concept's own count; the claimed first pass is about thirty.
Main risk. The replica couples the overlay to the current page drawing, so a page change means redrawing the miniature; and it is the only candidate that reproduces the page's warn-toned chips inside the overlay, which the other two deliberately avoid.
Annotation · provenance and neutralityThree designers, blind, same brief, same bundle. External reviewer A (Codex), external reviewer B (Grok), and the workspace designer (Fable) each received the identical brief and the identical bundle (the rejected page 8b drawing and the page 08 Stakeholder groups drawing) and proposed independently, without seeing each other's work. The rejected baseline is included above as the reference point, not as a fourth option. One builder drew all three candidates faithfully from their written specifications, at their specified sizes, with their verbatim copy; where a specification left a detail open or contradicted its own pixel estimate, the resolution is flagged in that candidate's annotation, never silently improved. No candidate is decided, none is recommended, and the two designer-stated word counts above are theirs, not the builder's.
Annotation · what survives the decisionWhichever candidate the PM picks, the decided mechanics from the guidance intake of 2026-08-24 stay exactly as drawn on page 8b: showing state per user on the server, automatic stop after the third counted showing, the do-not-show checkbox, and the About this page reopen control in the page header of this page, of Value Chain, and of Frameworks and Access. The winning presentation replaces the four-paragraph body of page 8b; the guidance workstream then owns the final authored copy, starting on the PM's GO. The introduction stays off the critical path in every candidate: a missing content record means no overlay and no error, and nothing in the reporting flow reads or waits on introduction state.