Ultra PatternsAI interface patterns with receiptsULTRA project

Pattern 14 · Chat or assistant · Interaction pattern

View

Paraphrase before you advise

Seen in a case Built for a real case and observed with its users, or built for a case whose user test is still to come. No controlled comparison yet.

Practice view. What to build, the words on screen and how to measure it. Switch to Research for why it should work, the framework properties and the references.Research view. The research side is shown below the card: why it should work, the properties it targets and the references. Switch to Practice to hide it.

Before any advice, the assistant restates the situation and the feelings the person expressed: 'I hear that you...'. Things it inferred but was not told are held back, or offered as a question to confirm.

WhyParaphrasing what the person said ('I hear that you...') was strongly valued in the test of Goose version 3 and gave participants trust; it made the tool feel like searching together rather than being lectured. The reverse showed up too: when Goose assumed feelings or priorities the person had not voiced, two participants felt they lost control.
WhenCoaching, support and intake conversations, and anywhere the person's own words carry the meaning.
Not whenTransactional bots where mirroring feels like padding. Keep it to one line or skip it.

The right amount of trustThe user stays in chargeCase: Goose conversation guide

Done right, done wrong

Schematic screens, not real products. Click a screen to enlarge it.
Right. The assistant mirrors what was said, then asks. What it inferred is shown as a question to confirm.
Wrong. The assistant jumps to advice and states feelings the person never mentioned.

In practice

Goose opens its analysis with observations in the person’s own terms before it offers the steps of connecting communication. In the version 3 round participants had been sceptical beforehand and were pleasantly surprised; the mirroring was one of the things that gave them trust. In the version 4 round a new problem appeared, which the team calls over-eager inference. Goose named feelings and priorities the person had not mentioned yet. Two participants, independently, said this undermined their sense of control.

The team’s fix is worth copying: an explicit list of inferred facts in the answer format, shown to the person as something to confirm or correct before the guide builds on it. That turns a silent assumption into a question, which is what a good listener does anyway. It is on our list as the candidate “Confirm what the AI assumed”; vote for it if you want it tested.

Words on screen

"I hear that you want to bring this up without it turning into a fight.""Did I get that right?""You mentioned feeling ignored. Is that the main thing?"

Obligations to keep in mind (AI Act, GDPR)

  • Assumptions about a person's feelings or intentions are theirs to confirm. Show them as questions, not as facts. (O4, Goose v4)
  • Mirroring sensitive statements makes the storage question urgent. Say what is kept and for how long. (O3, IUI 2026, Table 1)

Design considerations, not legal advice or a conformity assessment. What O1 to O5 mean.

Build it

Illustrative signatures, not a published library: the names below are suggestions to adapt to your stack. Thresholds are examples to tune on your own data.

States: reflecting, confirming, confirmed, corrected

Component: <Reflection said={quote} inferred={facts} onConfirm={fn} />

Prompt snippet: Restate the person's situation in one sentence using only what they wrote. Put anything you inferred in inferred_facts and ask before using it.

Output schema: { "reflection": "string", "inferred_facts": ["string"], "question": "string" }

Measure it

Users rely on it the right amount · 10 minUsers feel in control · 8 minPlan your testTen minutes per participant is the usual budget: pick the two or three cards that fit.

Same idea, other names

Google PAIR: Explainability + TrustNonviolent communication: Observation before evaluation

All the libraries we build on

Applied by: nobody yet · Replicated by: nobody yet · Used this pattern? Tell us and get listed

Research side · why it should work

Why it should work

The mechanism, notes and references for this card are written together with the science editor at KU Leuven Augment. Until then this side lists the properties the pattern targets and the contexts in which it was seen.

Properties targeted

Trust · Controllability · Axes: type: reflection, format: text, interaction: every turn · Vocabulary bridge

Across contexts

ContextUsersStateResult
Goose conversation guide, v3adults, desktopSeen in a caseparaphrasing ('I hear that you...') strongly valued and gave trust
Goose conversation guide, v4adults, mobileSeen in a caseover-eager inference undermined the feeling of control for 2 of 4
Your contextBring your case

Editors

Practice: Rutger De Wilde (Odisee UX Lab) · Science: to be assigned by KU Leuven Augment · card v1.0 · 2026-09-03