Skip to main contentSkip to footer
Principle 8trust

Make hand-offs, approvals, and blockers explicit

When the system cannot proceed, the reason should be immediately visible, along with any action required from the user or another dependency.

Key Facts

Cluster
trust
Primary risk
Tasks stall silently, creating confusion and eroding confidence.
Related examples
6 library examples
Doctrine library
Internal doctrine reference
Why does this principle matter?

In agentic systems, failure frequently arises not from incorrect reasoning but from unclear responsibility. Users must know when a task is paused, why it is paused, and what will resume progress.

Surface waiting states clearly.
Explain whether the dependency is user action, system access, policy constraint, or tool failure.
Make required actions specific and minimal.
Distinguish between interruption, failure, and approval gating.
What failure does this principle prevent?

Tasks stall silently, creating confusion and eroding confidence.

AI as interface embellishment: A conventional product is given a text input and labelled intelligent, without any meaningful change in operational model.
Simulated autonomy: The system appears autonomous in language or presentation but cannot act with meaningful independence.
Opaque execution: Work occurs in the background without adequate status, accountability, or recoverability.

Related examples