Local-first
Library paths, credentials, and working data stay on the user's workstation unless the user chooses to share them.
Safety and trust
Understand every important library action.
MMW is built around local files, private credentials, visible targets, deliberate approval, backup, verification, and recovery.
The safest change is one you can explain and reverse.
Review and recovery
MMW separates discovery, proposal, authorization, output, verification, and recovery so users can see where they are in the process.
Source files and credentials remain under the user's control, and consequential actions are designed to identify their exact target and scope.
Core principles
How MMW earns trust.
Safety is part of the workflow rather than a warning added at the end.
Visible targets
Important actions identify the file, folder, setting, server, package, or device they concern.
Deliberate approval
Consequential work remains separate from inspection and preview.
Backup and verification
A recovery point and a clear verification step accompany controlled changes.
Private credentials
Authorization is presented as connection state, not raw secret handling.