This walks through the smallest working integration: requesting an upload slot from your backend and handing it to the client SDK.
A slot is a short-lived, scoped target for one upload. Your server creates it after checking whatever auth and quota rules apply to that user.
The SDK handles chunking and retries. Pass it the token from step one and a progress callback if you want one.
Once every chunk is confirmed and checksummed, Vaultframe calls your webhook with the final object reference.
Slot creation accepts an optional idempotencyKey. Retrying a slot request with the same key returns the original slot instead of minting a new one, which matters for flaky client networks retrying the initial handshake.