Documentation map
Start here
Section titled “Start here”- Understand FTMS: protocol bytes, units, and what the libraries do.
- Choose a language: install and decode using any of the nine ports. Installation and upgrades distinguishes latest selection from reproducible pins.
- Check current releases and prerelease status before choosing a dependency.
- Find your API reference, then consult the TypeScript and C cookbook or your package’s examples.
- Keep the consumer adapter seam explicit, then use the JavaScript/C transport recipes where applicable. Consult troubleshooting for diagnostics.
Keep Bluetooth discovery, timing, permissions, session ownership and physical control safety in your application. A valid request or capability report is not authorization to execute a command.
Reference and compatibility
Section titled “Reference and compatibility”- API references by language
- Support profiles: definitions of wire roles and optional modules
- Protocol coverage: implementation and verification scope
- Versioning: package compatibility, protocol and corpus identities
- Capability evidence contract
- Wire compatibility and numeric inputs
Releases
Section titled “Releases”- Current public packages and exact release evidence
- Package-owned changelogs describe changes; publication records establish artifact identity.
- Planned 1.0 milestone: preparation status, not a published release
Migration guidance will be based on reviewed interface differences, not inferred from the target version. Current installation commands remain valid until a new public artifact is verified.
Historical records are indexed in Audits and evidence; they are not current installation instructions.
Contributors and maintainers
Section titled “Contributors and maintainers”- Contributing, architecture, roadmap, security
- Conformance runner and corpus accounting
- Release process and per-port runbooks
- Equipment testing and simulation
- Historical audits and evidence
- Documentation site development and deployment
Public integration does not require a repository checkout or private specification context. Exported declarations and public headers remain package-owned references; the site also publishes generated TypeScript API documentation.