Copying is not the same as verifying.
A completed transfer does not prove that the destination contains the exact same bytes as the source. MENELAO treats that gap as the actual problem: the goal is not simply to move files, but to leave evidence that the original source and two independent copies match.
The software never formats, deletes or modifies source media. A successful verification informs the operator; it does not replace human judgment.
An X/A/B verification triangle.
Each ingest has three locations: X is the source, A is the local/master copy and B is an independent external backup. Verification succeeds only when X↔A, X↔B and A↔B all match.
Content-based comparison rather than filenames or sizes alone.
Master and backup are both verified against the source.
Human-readable evidence for review and troubleshooting.
No formatting, deletion or source-media modification.
Reduce risk before adding convenience.
Local verification
Cloud sync is intentionally outside the X/A/B safety model. It may happen later, but it does not replace immediate local verification.
Desktop workflow
Tkinter and native folder pickers keep source and destination selection explicit without requiring command-line operation during ingest.
Tests and documentation
The repository includes pytest coverage plus separate user, safety-model, technical-overview, roadmap and changelog documentation.
Engineering applied to an operational risk.
MENELAO shows a practical pattern: identify the failure mode, define a verifiable success condition, limit the software's responsibilities and document the handoff so another operator can understand what happened.