> For the complete documentation index, see [llms.txt](https://consumer-trust-initiative.gitbook.io/consumer-trust-initiative-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://consumer-trust-initiative.gitbook.io/consumer-trust-initiative-docs/1.2-our-mission.md).

# 1.2 Our Mission

The TDUX Framework was developed to address this critical gap. Our mission is to move the evaluation of digital consumer platforms from the realm of the subjective to the objective. We believe that trust can, and should, be quantified through the systematic analysis of verifiable data points.

This document serves as the official white paper for the TDUX model. It details the architecture, metrics, and scoring logic, providing a transparent, open-source methodology for any researcher, analyst, or consumer to use.

Our goal is twofold:

1. To empower consumers with a robust mental model for evaluating platforms themselves.
2. To establish a new standard of accountability for review platforms by demonstrating what a truly data-driven analysis entails.


---

# 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://consumer-trust-initiative.gitbook.io/consumer-trust-initiative-docs/1.2-our-mission.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.