GRI guidance UX round
The UX decision round for the guidance layer, run on the PM's go (2026-08-25). Each page carries one decision as drawn options with honest pro and cons, or styles an already-decided element for confirmation. Spec reference: project-docs/requirements/gri-i1-guidance-layer-spec.md section 13; the prose options live in the round record project-docs/reviews/2026-08-25-gri-guidance-ux-round.md.
Already decided, binding on every page here
Help content renders SHOWN by default in I1 (D-g-4). The word in user-facing copy is Help, never Guidance. The hidden-help region indicator is the one-line collapsed strip with a count (D-g-4, Option C; styled on page 07). The AI helper streams its answers server-side with every block validated before it reaches the browser (D-g-10). The AI helper is anchored to its surface, never a global chat bubble. Answers explain and never recommend; every AI answer carries the AI-generated label; every refusal names its exits.
Pages and the decision each carries
- 01The helper surface (U-1)
The same blocked page drawn twice: an anchored expandable panel against a slide-over drawer, each with starter prompts, the question input, and one example answer. The container pick applies to every helper surface.
- 02The single-slot reveal interaction (U-2)
How one collapsed field explainer opens in clean density: info icon expanding in place, dotted-underline term with popover, or a mini strip matched to the decided region strip. Decided once, harness-proven in I1, user-reachable post-I1.
- 03About this page, and the two new hooks (U-3)
Two placements for the reopen control (icon button against text link), plus the cycle-list introduction hook and the lock-dialog explainer hook drawn in place.
- 04The AI settings tab (U-4a)
The third settings tab in two states: the regular user's view with the context-level section, and the super admin's view adding the organization toggles the PM ruled in D-g-3.
- 05The extended-context consent dialog (U-4b)
The truth-coupled dialog: benefit, caution, the generated what-is-sent list at field level, and the never-sent line. Structure is the proposal; the drawn list is illustrative.
- 06The streamed answer (U-5)
The showpiece storyboard: generating, blocks arriving, complete, a mid-stream refusal, and the budget-exhausted refusal. The streaming mechanics are decided; this page is the look.
- 07The region strip, styled (decided)
The D-g-4 Option C strip in product styling with the decided Help wording: collapsed, expanded, single-item, and in context. Confirmation, not a new decision.
Back to the lab root. Companion sets: the density comparison exhibit this round's decided items came from, and the reviewed catalog and cycle admin wireframe sets whose pages these drawings reuse.
How to read these pages
Same conventions as the reviewed GRI wireframe sets. Anything in plain product styling is proposed UI. Anything amber-tinted with a dashed border is review scaffolding and would never ship:
Annotation · not proposed UIBlocks like this one carry the spec citation behind a drawn behavior and the open questions for you. Notes to the reviewer, not screen copy.
Demo helperBlocks tagged this way are navigation aids and stand-ins: the dark bar at the top, cross-page links, state labels, and any half-scale framing.
The tenant is Bluefin Foods Group, the same fictional multi-entity food producer the reviewed sets use. Every organization, person, count, date, and identifier is invented. Help wording and AI answers on these pages are composed placeholder copy written under the explain-never-recommend rules; review the surfaces and interactions, not the sentences.
What is and is not decided here
- Decided here (yours): U-1 the helper container, U-2 the single-slot reveal, U-3 the About-this-page placement, U-4 the settings tab and consent dialog presentation, U-5 the streamed-answer look.
- Not decided here: the production AI provider arming (waits on the terms verification), authored content wording (the editorial chain owns it), and anything already ruled in the spec's section 15 ledger.
- Build scope: the wireframe gate on the guidance-layer UI build is satisfied only when the PM's U picks are recorded in the round record and applied to this set.