# VortX documentation

## Using VortX

- [Install and update](INSTALLING.md): device requirements, Full/Lite, signing and Mac setup.
- [Help and diagnostics](SUPPORT.md): profile/sync failures, playback reports and safe log sharing.
- [Release artifacts](RELEASE-ARTIFACTS.md): package names, Android variants, checksums and provenance.
- [Changelog](../CHANGELOG.md): released changes and historical candidates.
- [Roadmap](../ROADMAP.md): available features, remaining work and future priorities.

## Developing and contributing

- [Build and source boundaries](BUILDING.md): native release generation and dependency access.
- [Native release packaging](native-release-packaging.md): source, SDK, player and package acceptance gates.
- [Contributing](../CONTRIBUTING.md): focused changes, testing, generated projects and licensing.
- [Browser client](../webapp/README.md) and [LG/Samsung TV projects](../platforms/README.md).
- [Security reporting](../SECURITY.md), [third-party notices](../THIRD-PARTY-NOTICES.md), [legal policy](LEGAL.md) and [trademark policy](../TRADEMARK.md).

Dated audit documents and old release plans record their own source/build baseline. They are not a current platform-support matrix or a promise that every finding has shipped. For a specific download, its release page and provenance take precedence over a historical plan.