Meridian Verity Group — /downloads (v53)

This folder is intentionally structured to stay **web-only friendly** for GitHub UI uploads.

Why
- The GitHub web uploader commonly hits practical limits around ~100 files per folder / per upload action.
- MVG keeps each high-churn artifact family inside predictable buckets (<= 90 files each).
- v53 adds a **no-commands inbox** + **bucketize status evidence** so operators can publish safely
  even when using only the GitHub web UI.

Folder split (v53)
- /downloads/                (root: stable public URLs for packs + control files; keep <= 90 files)
  - index.html
  - README_DOWNLOADS.txt
  - SHA256SUMS.txt
  - *.zip   (Ticket Packs, Pilot-in-a-Box, conformance packs, evidence bundles)
- /downloads/docs/           PDFs (1-pagers, decks, reports, counsel-friendly policy pages)
- /downloads/specs/          Specs (.md / .yaml)
- /downloads/snapshots/      Snapshots index + monthly buckets + _inbox dropzone (see README_SNAPSHOTS.txt)

Web-only “no command” publish rule (snapshots)
- Upload new snapshot files into:
    /downloads/snapshots/_inbox/
  Then the repo automation bucketizes + updates indexes.

Evidence rail (v53)
- Each bucketize run can be evidenced via:
    /trust/deployments/prod/MVG_BUCKETIZE_STATUS_LATEST.json
  (Signed under the deploy_transaction role when keys are configured in CI.)

DoD (operational)
- No folder exceeds 90 files (guarded by CI gate)
- The published site keeps /downloads/snapshots/_inbox/ empty
- Status artifact exists (200) even in READY-TO-SIGN mode (no 404s)