# Cross-Cutting Workstreams

**Security.** Continuous threat-model review. Every new firmware module ships with a written threat statement. No code reaches mainnet without external review.

**Community.** Weekly office hours from Month 2 onward. A public roadmap board updated at the close of every month. Visible response on community-reported issues within 48 hours.

**Pricing.** The TaτsuOS team publishes the final subscription tier burn requirements ahead of mainnet. Pricing is updated via published platform releases. Target: announced at end of Month 5 alongside the mainnet date.

> **A Note on Realism.** Each of the milestones above carries known risk — in particular, first-time-user BLE pairing UX (Month 2), STM32 BLE-stack maturity (Month 3), and the routine over-run of third-party audits (Month 5). Slippage in any one month is expected to push subsequent months by a comparable amount; the roadmap is a plan, not a contract.


---

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

```
GET https://tatsu.gitbook.io/tatsu-whitepaper/cross-cutting-workstreams.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.