Six-Month Roadmap

The roadmap is expressed at the level of observable outcomes: what an external reviewer should be able to see at the end of each month. The starting point is the working prototype already in repository: a tested contract suite, a Next.js cloud with chain listener and signer, a working burn portal, and Zephyr firmware scaffolding with WiFi, MQTT, BLE, and a crypto module.

Month 1 — Hardening and Testnet Deployment. A complete end-to-end burn → BLE → unlock flow runs against a public testnet, on real ESP32 hardware, with the production signing key held in a KMS rather than an environment variable. Contracts are frozen and fuzz-tested; CI runs the full suite on every change.

Month 2 — BLE Provisioning and Closed Pilot. Ten real devices are deployed to five external pilot users drawn from the Taτsu community. Each user completes burn-to-unlock flows under guided observation. Receipt-delivery success rate on first attempt is the headline metric; the target is ≥ 90%.

Month 3 — Multi-Board Support and Telemetry SDK. Firmware builds and passes the verification test suite on at least two additional MCU families beyond ESP32 (nRF52 and STM32). A first-cut Telemetry SDK is published as a standalone Zephyr module, with reference application templates for agriculture, industrial, and consumer scenarios.

Month 4 — Public Beta and Developer SDK. A JS/TS SDK is published to npm. A public dashboard goes live with self-service sign-up, and a documentation site brings a new developer from "clone a template" to "burn TATSU and watch a feature unlock" in under 30 minutes.

Month 5 — Audit and Mainnet Preparation. Two independent third-party audits — one for contracts, one for firmware — complete, with all critical and high findings remediated and reports published. A feature-marketplace alpha opens to a curated set of third-party developers. Mainnet deployment dry-runs complete on a forked production environment.

Month 6 — Mainnet Launch and First Commercial OEM. Contracts deploy to a production EVM chain under multi-sig governance. The 1.0 release of the firmware and SDK is published. At least one OEM partner ships a small commercial production run of TaτsuOS-enabled devices, and the first quarterly state-of-TaτsuOS report — total devices, total unlocks, total TATSU burned — is published.