Manifest

Send production signal, not fragments.

A useful upload says what the file is, where it belongs, who approved it, and what deadline it supports.

Website content

Copy, pricing, bios, menus, policies, FAQs, and location details.

Brand evidence

Logos, brand guides, font notes, colors, screenshots, mockups, and references.

Media assets

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

Project records

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

Source packages

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

Operator Rule

Name the file like it may become proof.

home-hero-video-final-4k.mp4 tells the vault more than IMG_9041.mov.

  • Put related files into a zip when sending a large folder.
  • Send repositories as sanitized zips or through the repo workspace lane.
  • Use notes for deadlines, target pages, and revision context.
  • Confirm permission before sending client or third-party assets.

Proof Route

Upload becomes proof.

1Add client context

Who owns it, what project it supports, and how urgent it is.

2Upload directly

The browser sends file data to Cloudflare R2 through signed upload URLs.

3Keep receipt proof

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

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 the vault as the source of truth for production assets. Email or text is better for notes.

Can I send a repo?

Yes. Use a sanitized zip or the repo workspace lane so secrets and generated junk stay out.

What happens after upload?

The intake ledger gets reviewed, files get confirmed, and assets route into the active project workflow.