What Current Development Status helps you decide
This page explains what is available now, what is in development, what is planned, and what remains compatibility validation.
Use it before interpreting any product page as a promise that a workflow can already write to files, update servers, or control devices.
Review Current Development Status evidence
Use the smallest evidence set that can answer the question: the relevant source, intended outcome, and any target identity or permission that would matter before a later action.
MMW reads only the Current Development Status evidence listed here and keeps its origin visible.
Safety and availability for Current Development Status
Controlled Current Development Status outputs remain narrower than inspection and preview, with authorization at the point of action.
Status language is part of the safety model. It prevents a planned path from sounding like a finished operation.
A Current Development Status scenario
A user interested in NetMD can see that sequence and title preparation are represented, while direct device transfer is not promised as available.
When Current Development Status needs attention
Start with the Current Development Status inputs, then verify identity, paths, permissions, and the selected destination profile.
Provider and device matrices
Provider status distinguishes local evidence, guarded preview clients, profile-only providers, and research leads. Device status distinguishes planning models, discovery work, routing research, and direct hardware control.
- Plex read-only integration does not imply writeback
- AcoustID manual preview does not imply automatic tagging
- Jellyfin and Emby remain planned-gated
- casting, Bluetooth, mixers, controllers, S/PDIF, and broad I/O remain research or discovery work