Supported local and trusted-device workflows
Destination rules, collision checks, verification, and receipts follow the exact transfer path in use.
Transfer
Choose the files, establish the supported destination, preserve the source, and keep success tied to the result the transfer workflow can prove.
The transfer path
LogicHauler treats selection, destination authority, copy progress, and result evidence as separate facts. A queued job is not a completed transfer.
The job begins with explicit file selection, not background access to a device.
Supported device workflows use pairing and receiver-approved destination authority before a transfer can proceed.
Selected files copy to the approved destination. Existing destination files are not silently replaced.
The supported workflow verifies completed destination data and separates verified, partial, and failed outcomes.
Result language
Supported transfer receipts preserve the difference between intent, progress, incomplete work, and a verified result.
Trust boundary
Transfer acts only on chosen files and approved destinations. Completion is reported from verification and receipt state; source files remain preserved for copy workflows.
Destination rules, collision checks, verification, and receipts follow the exact transfer path in use.
Android, iPhone, and iPad access remains limited to the files, folders, or app-visible data their supported picker flows expose.
After the copy
See how LogicHauler represents verified and incomplete operations, or return to the full product map.