Check a storage export without moving it into Empire storage
LOCAL EXPORT COMPATIBILITY · NOT A MANAGED CONNECTOR
A downloaded object can lose its context when copied between folders or systems.
Try it
Use your existing authorized storage tool to download the object first. Package those bytes through storage-export and keep the verification bundle alongside the original. If you implement the customer-owned storage callback, run it on infrastructure you control, explicitly obtain consent and review the provider account’s terms and caps. The shipped adapter has no default upload endpoint or credentials.
node packages/udify/src/cli.mjs import storage-export source-file result.uds UDS node packages/udify/src/cli.mjs verify result.uds
Limits
Storage ownership is not inferred from a callback flag. This workflow does not prove bucket history, retention policy or chain of custody.
Is there an active S3, R2 or Drive connector?
No. This is local export compatibility plus an opt-in callback interface, not an authenticated vendor connector.