SKYE-OPS // private client intake

SkyeVault-Drop

A secure vault for every project package.

The surface beside this copy is the actual intake room: add context, send the package, and keep the proof receipts clean. I route files through routing gates into Cloudflare R2, write the ledger receipt, and review the archive from the operator side.

Open secure intake See what belongs here
Cloudflare R2 direct upload Multipart large-file handling Receipt-backed ledger Sanitized repo snapshots Operator review route
R2direct storage route
Receiptproof after completion
Ledgeroperator review trail
Zipsafe repo snapshot lane

Manifest

I need the full production signal, not fragments.

A useful upload tells me what the file is, where it belongs, who approved it, and what deadline it supports. That context turns a stored file into a route I can actually move.

Website content

Page copy, service descriptions, pricing sheets, bios, menus, policies, FAQs, and location details.

Brand evidence

Logos, brand guides, font notes, color references, screenshots, mockups, and inspiration links.

Media assets

Photos, raw images, 4K footage, edited videos, reels, banners, product shots, and gallery folders.

Project records

Contracts, approvals, intake worksheets, sitemap notes, revision lists, launch notes, and handoff files.

Source packages

Sanitized repo snapshots, deploy bundles, static exports, dependency manifests, and handoff archives.

Operator rule

Name the file like it may become proof.

Rename giant assets before upload when possible. home-hero-video-final-4k.mp4 tells me more than IMG_9041.mov.

  • Put related files into a zip when sending a large folder.
  • Send code repositories as one sanitized zip instead of loose source files.
  • Use the notes box for deadlines, target pages, and revision context.
  • Confirm you have permission to send and use the uploaded assets.

Proof Route

I route the upload into proof.

1Add client context

Tell me who the files belong to, what project they support, and how urgent the asset is.

2Upload directly

The browser sends file data straight to Cloudflare R2 using signed multipart upload URLs.

3Keep receipt proof

Completed uploads are verified, written to the ledger, and ready for operator review.

Repo Snapshot Lane

I can archive a whole codebase without dragging the wrong files with it.

The repo snapshot command builds one vault-ready archive, runs a local secret scan, uploads through the same R2 receipt flow, and keeps the proof in the ledger.

npm run vault:dry-run npm run vault:push

Safety behavior

The snapshot route refuses the usual leak paths.

The package skips local secrets, generated dependency folders, backup data, database files, private keys, old archives, and text files flagged by the credential scanner.

  • Use dry run first to create and inspect the sanitized archive.
  • Use push when the archive is ready for the vault ledger.
  • Save the receipt ID with the project or release notes.

Command Input

Send files

No files selected
Drop files into the vault

Docs, images, videos, zips, brand packages, repo snapshots, exports, and production assets.

0 B selected

Client Vault

Find and download your stored files.

Locked
Can I upload large videos?

Yes. Keep the tab open until completion. Very large uploads depend on your connection and browser stability.

Should I email files too?

No. Use this vault as the source of truth for production assets. Email or text is better for notes, not large files.

Can I send a repo?

Yes. Use a sanitized zip or the repo snapshot command so secrets and generated junk stay out of the vault package.

What happens after upload?

I review the intake ledger, confirm the files landed, and route them into the active project workflow.