> For the complete documentation index, see [llms.txt](https://tatsu.gitbook.io/tatsu-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tatsu.gitbook.io/tatsu-whitepaper/risks-and-mitigations.md).

# Risks and Mitigations

| Risk                                                          | Likelihood | Impact   | Mitigation                                                                                                                                 |
| ------------------------------------------------------------- | ---------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------ |
| Cryptographic flaw in firmware                                | Low        | Critical | External audit; mainstream curve and library; conservative receipt format                                                                  |
| Signer-key compromise                                         | Low        | Critical | KMS/HSM with multi-region access controls; multi-signer firmware support; rotation procedure with overlapping validity                     |
| Hardware partner slippage                                     | Medium     | High     | Maintain at least two qualified launch partners; treat OEM dates as soft until contracts signed                                            |
| BLE UX too painful for non-technical users                    | Medium     | High     | Pilot specifically tests this; fall back to QR-coded receipts as a secondary path if BLE adoption disappoints                              |
| Token-price volatility makes subscription pricing impractical | High       | Medium   | Subscription tiers priced in USD-denominated reference amount and converted to TATSU at burn time using a published exchange-rate schedule |
| Regulatory uncertainty (token + IoT)                          | Medium     | Medium   | Conservative jurisdictional choice; legal review before mainnet; clear separation between TATSU utility and any speculative claims         |
| Competing approach gains traction first                       | Medium     | Low      | The architecture is a moat in itself; first-mover advantage is real but not decisive                                                       |


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://tatsu.gitbook.io/tatsu-whitepaper/risks-and-mitigations.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.