# Open Source Posture

TaτsuOS is, and will remain, open source under permissive licenses (MIT for the cloud and SDK, Apache 2.0 for the firmware to align with the broader Zephyr ecosystem). The contracts will be released under MIT and verified on-chain on every supported network.

The production signing keys are held under a multi-party multi-sig structure, ensuring no single individual can unilaterally rotate or compromise the key that devices trust. Subscription pricing and the registered feature catalog are maintained and published transparently with each platform release.

Device longevity is a first-class commitment of TaτsuOS. An operator change, a pricing change, or even the operating company ceasing to exist should not affect devices already in the field. Receipts minted against a subscription period remain valid for that period, regardless of what happens to the platform after they are issued. The open-source firmware and the published contract ABIs mean that any party — including the user themselves — can run a compatible signing service independently.

TaτsuOS launches with a subscription-based model, but the long-term vision is to open source the full platform so that broader communities and developers can build on it freely. The timeline for this transition will be decided and communicated as the project matures.


---

# 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/open-source-posture.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.
