Reference
Lookup rather than reading: environment variables, platform support, feature maturity, known limitations, and the glossary.
Nothing in this section is meant to be read front to back. These are the pages you arrive at with a specific question, usually while something is not working or before you commit to depending on something.
Before you rely on a feature
Two pages exist to be honest about maturity, and they are the ones to check first. Both are more useful than a version number.
| Page | Use it to find out |
|---|---|
| Feature status | What ships, what is preview, what is designed but unproven, and what is only planned |
| Known limitations | What does not work, what is not built, and what not to rely on yet |
IMPORTANT
A feature appearing in these docs is not a promise that it is finished. Feature status is the page that distinguishes the two, and it is kept deliberately blunt.
Configuration and environment
| Page | Use it to find out |
|---|---|
| Configuration and data | Where Harmony keeps its files, and the config CLI |
| Environment variables | What each variable changes, and which are validated rather than trusted |
| Environment variable index | Every variable read by the application, extracted from source |
The index is generated from the application source rather than written by hand, so it is complete but terse. The prose page explains which of them are load-bearing.
Platform, versions, and terms
| Page | Use it to find out |
|---|---|
| Platform support | The platform contract, native build requirements, and live download availability |
| Changelog | Where release notes live, how channels work, and how to verify what you are running |
| Glossary | Canonical definitions, with the distinctions kept sharp |
Where to go next
- For the model these references describe, read Concepts.
- For something failing right now, start at Troubleshooting.