# Implementation vs. Docs Status One of the most important research findings is that upstream documentation status in `docs_status.yaml` is not the same thing as implementation depth. Some domains that look weak from the docs are actually well implemented in source, while others are genuinely thin.[^docs-status] ## Clear examples ### Docker / Container Manager The upstream tracker marks Docker as `finished`, and the source header explicitly says it provides full coverage of all 12 `SYNO.Docker.*` namespaces, including container lifecycle, image management, network management, registry management, and compose project create/update/start/stop/delete/build flows.[^docs-status][^docker-source] This means Docker should be treated as an implemented control domain, not as a direct-DSM gap. ### FileStation and Surveillance Station Both are marked `partial` in the upstream tracker, but that label is about documentation state, not usefulness. FileStation is already a broad day-two operations surface, and Surveillance Station is a huge implementation area despite lagging docs.[^docs-status][^filestation][^surveillance] ### Virtualization / VMM Virtualization is marked `not_started` in the docs tracker, yet the upstream source file exists and describes methods for managing tasks, networks, storage, hosts, virtual machines, and images.[^docs-status][^virtualization] That makes it underdocumented, not absent. ## Why this matters If the report over-indexes on docs warnings alone, it will understate some of the most useful control surfaces. The correct split is: 1. **Implemented and documented enough to trust from docs** 2. **Implemented but source-driven because docs lag** 3. **Actually thin or read-only in the wrapper** The first two are both capability; only the third is a true wrapper limitation. [^docs-status]: Upstream documentation status tracker: https://github.com/N4S4/synology-api/blob/master/docs_status.yaml [^docker-source]: Docker source entrypoint: https://github.com/N4S4/synology-api/blob/master/synology_api/docker_api.py [^filestation]: FileStation docs: https://n4s4.github.io/synology-api/docs/apis/classes/filestation [^surveillance]: Surveillance Station docs: https://n4s4.github.io/synology-api/docs/apis/classes/surveillancestation [^virtualization]: Virtualization source entrypoint: https://github.com/N4S4/synology-api/blob/master/synology_api/virtualization.py