Development Documentation
System documentation organised by "which part you need to touch": it describes what is true now. How it became that way, and what was rejected, lives in the development records.
Reading path:
- Server — core architecture first, then the pipeline and dialogue flow, then protocol and model deployment as needed.
- Clients — shared semantics live in one place; everything else is per platform.
- IoT Firmware — layers first, then feature criteria, then flashing and each path's semantics.
As needed:
- Debugging — ASR benchmarks and debugging entry points, TTS audio quality evaluation
- Model Downloader — manifests, downloads, verification
- Related Projects — call chains in upstream implementations worth comparing against
- Resources — measured properties of the test samples
Multilingual Documentation
After editing a Chinese page under docs/, translate it to .en.md and run git hash-object <source.md> to update the source_file_hash and translated_at in its front matter.