> For the complete documentation index, see [llms.txt](https://docs.ontorium.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ontorium.io/trust-transparency/user-facing-trust-at-the-application-layer.md).

# User Facing Trust at the Application Layer

Trust must ultimately be experienced by end users.

Even where underlying asset structures and financial controls are robust, users still require interfaces and access layers that make the system understandable and usable in practice. Clear presentation of product logic, transparent communication of user actions, and accessible financial flows are essential to making the stack practical.

For this reason, trust at the Application Layer is partly a matter of user experience. It depends on whether future user-facing products can present the underlying infrastructure in ways that users can navigate with confidence.

This means that user-facing trust is not separate from system trust. It is the form in which system trust becomes visible and actionable to end users.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.ontorium.io/trust-transparency/user-facing-trust-at-the-application-layer.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.