NAOMS · building block

Import & packs

Bring data in from services like Dropbox, Google Drive and iCloud, and move it in tamper-proof packs.

What a person notices

Moving years of files over from a cloud drive doesn’t mean re-uploading everything by hand.
Sharing a memory, a backup, or a whole feature with someone else arrives as one file that proves where it came from, not a folder of loose pieces they have to trust blindly.
Calendar events, email and local files can be brought in the same way, not just cloud storage.

Import brings outside data in; packs are how anything, data, a memory, a feature, moves back out verifiably.

Real adapters exist for Dropbox, Google Drive and iCloud, plus separate adapters for calendar, email, local files and search, so importing isn’t one generic connector that half-works for everything.
A pack is a content-addressed, signed collection of graph nodes or chain events, checked against a Merkle root, so a recipient can verify nothing inside was altered without contacting anyone.
The same pack format carries every kind of thing that leaves a device: a backup, a shared memory, a hive snapshot, a file, even a model. One format and one verification path, whatever is inside.
Packs move over signed friendship or hive channels with their own sharing bookkeeping, so a pack a person receives is tied to who actually sent it, not an anonymous download link.
The pack format is built on Aqua Protocol, in partnership with inblockio, so the same tamper-proof exchange format works outside NAOMS too.