Demo helperGRI guidance UX roundPage 5 of 7 · The extended-context consent dialogInvented data · Bluefin Foods Group (fictional tenant)
GRI guidance UX roundThe extended-context consent dialogWhat a Standard user sees after "Request extended context" on the settings tab (DECISION U-4b: the presentation; the consent mechanics behind it are decided).PROPOSAL2026-08-25
Annotation · what U-4b decides, and what is already decidedDecided and not up for restyling (spec 8.3): accepting writes an append-only consent record with the dialog version and the envelope-constant version, both server-derived; declining changes nothing; if the what-is-sent constants ever change, existing consent goes stale and this dialog is shown again, regenerated; any level change closes the current helper session; returning to Standard is always available. The dialog body is itself authored, versioned, human-reviewed content, so it carries no AI-generated label. U-4b decides the PRESENTATION drawn here: the ordering of benefit, caution, and list; the two-column what-is-sent layout; and the button and microline placement.
User Settings
AI assistance · the settings tab from page 04, dimmed behind the dialog
Extended context for the AI helper
Bluefin Foods Group · your account only
With extended context the helper can answer about the cycle and the data you are working on, not only about how pages work.
Your questions and the context listed below are sent to an AI service. Answers are AI-generated and can be wrong. The helper explains; it never decides anything for you.
What is sent
Already sent at Standard
Page and field identifiers, and the option sets the platform defines
Published Help content for the page you are on
What the page already shows you: current selections, disabled states, framework and edition identifiers, lock state, reason codes
Your questions, and this session's earlier turns
Added with Extended
The cycle name and reporting period
Organization unit names in your active scope
Values and omission reasons entered on the surface you are viewing
The quarantine row summary you are viewing
Value chain facts, on their pages
Never sent at any level: your name or email, other users' data, whole records or documents.
Annotationtruth-coupled: both lists are generated from the same envelope constants the server enforces (spec 6, 8.2), so the dialog cannot drift from behavior; if the constants change, consent goes stale and this dialog regeneratesExhibit onlythe drawn items are illustrative of the real generated list; the exact field names come from the envelope constants at build time. The structure, two groups plus the never line, is the proposal
Your agreement is recorded with the date and this dialog's version. You can return to Standard at any time on this tab.
Not nowAgree and use extended context
Annotation · what each button does"Not now" closes the dialog and changes nothing: no record is written, the user stays at Standard, and the button can be pressed any number of times without consequence. "Agree and use extended context" writes the consent record, sets the level to Extended, and closes the current helper session so no Standard session ever continues with Extended context in it. Both paths land back on the settings tab, which then shows the current level.