You've spent five modules learning the rules: what regulations require, what your role is, how to design identity flows, how to write compliant copy, how to design failure states. All of that is essential. But there's a layer above it that this Bonus Module addresses.

Trust is the outcome all of that work is trying to produce. Compliance creates the conditions for trust. Honest copy contributes to trust. Well-designed error states preserve trust. But trust itself is something more — it's a feeling a user has about a product, built over time through consistent, honest, capable interactions.

And unlike most feelings, trust can be deliberately designed. It can be analysed, decomposed into specific signals, deployed strategically across specific screens, and measured against a user's actual experience of the product.

This lesson: a three-dimensional trust model, six signal categories with placement guidance, a four-screen placement matrix, a six-screen audit exercise, and a 12-template signal library.

Let's start with what trust actually is — because the design implications follow directly from the definition.