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.
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.
State gallery · drawing 2 · annotation frame only, the white card is the proposal
Where the introduction lives after it stops appearing: the reopen control in the page header.
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, 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.