# Introduction — The State of Connected Devices

There are, by conservative counts, more than 18 billion connected devices in operation today. They sit in homes, in factories, in fields, on bodies, on roads. Almost without exception, the capabilities of those devices are gated by the company that manufactured them. A camera streams to one cloud. A thermostat speaks one protocol. A tractor reports back to one OEM. When the manufacturer raises a subscription price, deprecates a feature, or simply goes out of business, the hardware in the user's hand quietly degrades — sometimes overnight — into something less than what was paid for.

This is not a marginal pattern. It is the default architecture of the IoT industry. And it produces three durable harms:

* **Tenant capture.** The end-user owns the device but rents its features.
* **Innovation tax.** Independent developers cannot build for these devices, because the capability surface is locked behind proprietary clouds.
* **Silent obsolescence.** When a vendor disappears, so do the devices.

The Taτsu thesis has always been that centralized control over the technology stack is incompatible with long-lived, community-aligned innovation. TaτsuOS applies that thesis to the lifetime of every connected device — turning the TATSU token into the unit of account for a category of digital scarcity that has, until now, been the sole property of vendor cloud accounts.


---

# Agent Instructions: 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:

```
GET https://tatsu.gitbook.io/tatsu-whitepaper/introduction-the-state-of-connected-devices.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.