Experience & Interaction

• Channels: web, mobile, chat platforms, voice and public API
• Streaming and partial-result rendering so long tasks stay legible
• Session and conversation state at the edge
• Clarification prompts when the task is under-specified
• Approval and review surfaces for human-in-the-loop checkpoints
• Provenance display: what the answer was based on and how confident it is
• Multimodal input and output, and accessibility

Accountable owner

Product Engineering / Digital Channels, with UX

• Product lead — accountable owner
• Frontend engineer — streaming, sessions, channel adapters
• UX designer — approval, clarification and provenance patterns
• Content designer — the words in the interface
• Accessibility specialist

Ownership and phase are architectural recommendations, not assessed results.

Pilot can ship one channel with streaming. Approval and clarification surfaces become mandatory the moment agents can write to production systems.

Signals to watch

• Task completion and abandonment rate
• Clarification rate and its effect on success
• Approval latency and reviewer override rate
• Accessibility conformance
• User-reported trust or satisfaction

Presentation and clarification prompts can improve. Consent, accessibility and explicit approval meaning must remain intact.

Failure modes

1. No clarification path, so the agent invents assumptions instead of asking
2. Approval fatigue: too many low-stakes confirmations and reviewers stop reading
3. Provenance hidden, so users cannot calibrate trust
4. Disclosure obligations missed for chatbots regardless of risk tier

Existing tool and standards snapshot · approximately mid-2026. Examples, not required dependencies; verify current versions before adoption.

This is the harness most often skipped in an architecture diagram and most often blamed in a post-mortem. Autonomy policy is only real if there is a surface where a human can actually intervene in time.