16. Roadmap

Trail Mate Roadmap: Maintaining a Frozen MCU Product

Language: 中文版：16. Roadmap (中文)

The MCU product feature set is defined and frozen. This roadmap no longer asks which major feature should be added next. It defines how to preserve the product while making its existing capabilities more reliable, secure, deployable, and understandable.

Product Position

Trail Mate is an independent MCU-class handheld terminal that is close to a decentralized phone. “Phone” does not mean cellular service, an app store, or broadband media. It means the device itself owns:

• local identity and contacts;
• direct and group messaging;
• positioning, offline maps, tracks, markers, and team awareness;
• communication that does not require a cloud service;
• on-device input, viewing, configuration, and diagnosis.

Phones, cloud services, and desktop tools may connect, but they are not prerequisites for the core loop.

Four Core Capabilities

Anonymous operation

Users control identity exposure and position-sharing boundaries. Anonymous operation does not mean having no identity; identity remains local while unnecessary public announces, discovery, and position exposure can be suppressed. Team position data belongs to an authorized collaboration relationship.

Decentralization

Identity, contacts, messages, paths, and awareness do not require one cloud service or central account system. Meshtastic, MeshCore, and Reticulum are selectable network paths serving the product; they do not define the product.

Offline operation

Without cellular service, Internet access, or a phone, the device must still provide local operation, LoRa communication, GPS, offline maps, tracks, and Team collaboration. Wi-Fi, MQTT, BLE, HostLink, and Trail Mate Center are optional enhancements, never hidden core dependencies.

TAK

TAK means the team/tactical awareness loop provided on the device: member identity, position, maps, tracks, waypoints or markers, assembly points, messages, and operational state combine into shared situational awareness.

This does not claim ATAK, WinTAK, or Cursor-on-Target interoperability. Any external TAK ecosystem adapter belongs to interoperability or tooling and may not expand or redefine the frozen MCU product.

What Feature Freeze Means

The following MCU product domains are defined and are not waiting for major expansion:

• device identity, contacts, chat, and groups;
• single-protocol operation through Meshtastic, MeshCore, or Reticulum;
• GPS, offline maps, routes, tracks, and position markers;
• Team/TAK awareness and controlled position sharing;
• device UI, input methods, settings, and maintenance;
• HostLink, Trail Mate Center, and offline resource preparation;
• existing hardware-gated audio, SSTV, and radio/energy-view capabilities.

Feature freeze does not mean development stops. It means future changes improve the established product without silently redefining it.

Work That Remains In Scope

• bug, crash, corruption, deadlock, and security fixes;
• more correct protocol interoperability without adding a fourth MCU product protocol;
• power, memory, storage, radio arbitration, and weak-link recovery improvements;
• usability, input efficiency, accessibility, and screen adaptation for existing UI;
• new suitable hardware carrying a capability-gated form of the existing product;
• better map preparation, configuration, backup, diagnostics, logging, build, and release tools;
• automated, interoperability, and regression tests plus documentation and migration guidance;
• clearer privacy, authorization, anonymous-operation, and local-data ownership boundaries.

These may improve implementation quality or hardware coverage, but they must not turn Trail Mate into a different product.

Explicitly Out of Scope

• adding new major feature domains to MCU firmware;
• adding a fourth peer product protocol or running multiple product protocols concurrently;
• changing position transmission into default-public broadcasting or continuous cloud reporting outside Team/TAK authorization;
• reducing anonymous mode to a cosmetic hidden name while identity or position remains exposed;
• making a phone app, cloud account, online map, MQTT, or Center mandatory for the core loop;
• becoming a broadband social platform, app-store phone, or generic IoT controller;
• sacrificing the independent-terminal experience merely to increase board count;
• claiming ATAK, WinTAK, CoT, or another external ecosystem without implementation and validation.

Non-Negotiable Position-Sharing Rules

1. Users can tell whether position is being shared, with whom, and over which protocol path.
2. Public discovery, contact position, Team position, and local tracks remain distinct data and controls.
3. Team position serves authorized members and shared awareness; it must not silently become public broadcast.
4. Anonymous operation suppresses unnecessary public discovery and position exposure.
5. Position, maps, and local tracks remain useful offline; cloud reachability is never a condition for positioning.
6. A protocol adapter projects these semantics and may not redefine the product privacy model.

Desktop and MCU Boundary

Trail Mate Center can prepare maps, provide a larger awareness view, export or replay data, and diagnose devices. It is a companion tool, not the owner of the product core. The MCU device continues to own identity, communicate, show essential awareness, and support field operation independently.

Center may grow tools that deploy, maintain, or explain existing MCU capabilities. Desktop additions must not force the MCU product away from its established position.

Five Questions for Future Changes

1. Does the change strengthen anonymity, decentralization, offline operation, or TAK?
2. Does it improve an established capability, or quietly create a new product domain?
3. Does it add a phone, cloud, central-server, or desktop dependency?
4. Does it change ownership or exposure of identity, contacts, messages, or position?
5. Is it sustainable within MCU memory, storage, power, and radio budgets?

A major change that cannot pass these questions is outside this roadmap.

How Progress Is Measured

Progress is no longer measured by feature count. It is measured by:

• a more stable core loop on primary hardware;
• less data loss and corruption;
• deterministic weak-link, offline, and reboot recovery;
• more accurate interoperability;
• privacy and position authorization that users can understand and verify;
• first use and configuration without a phone or cloud dependency;
• documentation, logs, and tools that accurately explain device behavior.

That is the long-term roadmap for Trail Mate after the MCU feature set has been defined.